From: Markus Armbruster <armbru@redhat.com>
To: Simran Singhal <singhalsimran0@gmail.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
Julia Suvorova <jusual@mail.ru>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v3] qobject: json-streamer: Change bracket_count to brace_count
Date: Fri, 03 Apr 2020 08:48:33 +0200 [thread overview]
Message-ID: <87eet5t67y.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20200402182848.GA3023@simran-Inspiron-5558> (Simran Singhal's message of "Thu, 2 Apr 2020 23:58:48 +0530")
Simran Singhal <singhalsimran0@gmail.com> writes:
> Change the "parser->bracket_count >= 0" to "parser->brace_count >= 0"
> to fix the typo.
>
> Fixes: 8d3265b3
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> Signed-off-by: Simran Singhal <singhalsimran0@gmail.com>
First, thank you so much for spotting and fixing my typo!
The commit message neglects to explain what is broken. I'd like to use
this one:
json: Fix check for unbalanced right curly brace
We immediately diagnose unbalanced right curly brace:
$ qemu-kvm --nodefaults --nographic --qmp stdio
{"QMP": {"version": {"qemu": {"micro": 91, "minor": 2, "major": 4},
"package": "v5.0.0-rc1-1-gf6ce4a439a08"}, "capabilities": ["oob"]}}
}
{"error": {"class": "GenericError", "desc": "JSON parse error,
expecting value"}}
except within square bracket:
[}
The check for unbalanced braces has a typo. Fix it.
Fixes: 8d3265b3d00db1071d1d3bf8433b4818088fdeb5
Signed-off-by: Simran Singhal <singhalsimran0@gmail.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Objections?
> ---
> Changes in v3:
> -Add "Fixes: 8d3265b3" in commit message.
>
> Changes in v2:
> -No need to remove the duplicate occurrence of "parser->bracket_count >= 0"
> but actually it is a typo and one occurence should be "parser->brace_count >= 0".
>
> qobject/json-streamer.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/qobject/json-streamer.c b/qobject/json-streamer.c
> index 47dd7ea576..b93d97b995 100644
> --- a/qobject/json-streamer.c
> +++ b/qobject/json-streamer.c
> @@ -85,7 +85,7 @@ void json_message_process_token(JSONLexer *lexer, GString *input,
> g_queue_push_tail(&parser->tokens, token);
>
> if ((parser->brace_count > 0 || parser->bracket_count > 0)
> - && parser->bracket_count >= 0 && parser->bracket_count >= 0) {
> + && parser->brace_count >= 0 && parser->bracket_count >= 0) {
> return;
> }
With a commit message that spells out what's broken:
Reviewed-by: Markus Armbruster <armbru@redhat.com>
next prev parent reply other threads:[~2020-04-03 6:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 18:28 [PATCH v3] qobject: json-streamer: Change bracket_count to brace_count Simran Singhal
2020-04-02 20:15 ` no-reply
2020-04-02 20:15 ` no-reply
2020-04-02 20:15 ` no-reply
2020-04-02 20:15 ` no-reply
2020-04-02 20:16 ` no-reply
2020-04-03 6:48 ` Markus Armbruster [this message]
2020-04-07 11:42 ` Markus Armbruster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eet5t67y.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=jusual@mail.ru \
--cc=qemu-devel@nongnu.org \
--cc=singhalsimran0@gmail.com \
--cc=stefanha@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).