DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Jonathan Erb <jonathan.erb@threater.com>
Cc: ciara.power@intel.com, dev@dpdk.org, bruce.richardson@intel.com
Subject: Re: [PATCH] telemetry: correct json empty dictionaries
Date: Thu, 1 Feb 2024 12:57:20 +0100	[thread overview]
Message-ID: <CAJFAV8zMdV61_QewDGv3oZK2um9ST-3y8Y_vUULsaxyUHA0Tjg@mail.gmail.com> (raw)
In-Reply-To: <20240118172602.898004-1-jonathan.erb@threater.com>

On Fri, Jan 19, 2024 at 8:48 AM Jonathan Erb <jonathan.erb@threater.com> wrote:
>
> Fix to allow telemetry to handle empty dictionaries correctly.
>
> This patch resolves an issue where empty dictionaries are reported
> by telemetry as '[]' rather than '{}'. Initializing the output
> buffer based on the container type resolves the issue.
>
> Signed-off-by: Jonathan Erb <jonathan.erb@threater.com>

Thanks for the fix.
Could you point at the change that introduced this issue?

I will add the Fixes: tag when applying.


-- 
David Marchand


  parent reply	other threads:[~2024-02-01 11:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-24 22:02 [PATCH v2 1/2] " Jonathan Erb
2023-12-24 22:02 ` [PATCH v2 2/2] " Jonathan Erb
2024-01-08 11:02   ` Bruce Richardson
2024-01-08 11:01 ` [PATCH v2 1/2] " Bruce Richardson
2024-01-10 17:49 ` Power, Ciara
2024-01-18 17:26 ` [PATCH] " Jonathan Erb
2024-01-19  9:56   ` Power, Ciara
2024-02-01 11:57   ` David Marchand [this message]
2024-02-02 14:04     ` Jonathan Erb
2024-02-12 10:15   ` David Marchand
  -- strict thread matches above, loose matches on Subject: below --
2023-12-18 21:47 Jonathan Erb

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=CAJFAV8zMdV61_QewDGv3oZK2um9ST-3y8Y_vUULsaxyUHA0Tjg@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=jonathan.erb@threater.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).