Investigate the need to decode AMQP body that does not have the content field #18216
Assignees
Labels
Client
This issue points to a problem in the data-plane of the library.
Event Hubs
help wanted
This issue is tracking work for which community contributions would be welcomed and appreciated
Service Bus
Comments
ghost
added
the
needs-triage
ramya-rao-a
added
Client
ghost
removed
the
needs-triage
ramya-rao-a
added
the
help wanted
8 tasks
openapi-sdkautomation bot
pushed a commit
to AzureSDKAutomation/azure-sdk-for-js
that referenced
this issue
Mar 22, 2022
Review request for Microsoft.ContainerService to add version 2022-02-01 (Azure#18324) * Adds base for updating Microsoft.ContainerService from version stable/2022-01-01 to version 2022-02-01 * Updates readme * Updates API version in new specs and examples * Update readmes for the 2022-02-01 dev branch of container service (Azure#17887) * update readme * remove useless -only tags * Fix violated rule R2026 for 2022-02-01 managedCluster swagger (Azure#18024) * fix allof * add missing type * GA alias minor version (Azure#18038) * GA alias minor version * polish more details on kubernetesVersion and currentKubernetesVersion * Update specification/containerservice/resource-manager/Microsoft.ContainerService/stable/2022-02-01/managedClusters.json minor revision Co-authored-by: Matthew Christopher <matthchr@microsoft.com> Co-authored-by: Matthew Christopher <matthchr@microsoft.com> * add missing type object (Azure#18115) * Revert "GA alias minor version (Azure#18038)" (Azure#18291) This reverts commit 3a99cda3cb48e05c74923f5467c0737014322b0f. * Align modifications of several common definitions with 2022-02-02-preview for container service 2022-02-01 (Azure#18216) * sync modification * fix ref Co-authored-by: Jianping Zeng <zjpjack@users.noreply.github.com> Co-authored-by: Matthew Christopher <matthchr@microsoft.com>
|
Hi @ramya-rao-a, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Package:
@azure/event-hubsThe decode() method that is applied on every event that is received over AMQP first attempts to read from
body.contentif the message has a valid type code otherwise reads frombody.This issue is to investigate if we need this fall back at all. Does AMQP dictate that every message should have a valid type code? Does rhea, the AMQP library we use, support storing anything in
bodydirectly instead of usingbody.content?This applies to
@azure/service-busas well where we use similar logicThe text was updated successfully, but these errors were encountered: