Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Event Hubs] Port bug fixes from Service Bus #2688

Closed
ramya-rao-a opened this issue May 3, 2019 · 2 comments
Closed

[Event Hubs] Port bug fixes from Service Bus #2688

ramya-rao-a opened this issue May 3, 2019 · 2 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs
Milestone

Comments

@ramya-rao-a
Copy link
Contributor

ramya-rao-a commented May 3, 2019

Event Hubs and Service Bus use similar design patterns and therefore a fix made in one usually has the potential to be a candidate in the other.

This issue is to review the bug fixes that have gone in Service Bus till this point and track and the port the ones that are applicable to Event Hubs.

  • First add the list of candidates in this issue
  • Once the list is reviewed and approved, port over the changes
@ramya-rao-a ramya-rao-a added Client This issue points to a problem in the data-plane of the library. Event Hubs labels May 3, 2019
@triage-new-issues triage-new-issues bot removed the triage label May 3, 2019
@ramya-rao-a
Copy link
Contributor Author

ramya-rao-a commented May 13, 2019

Below are list of improvements that were done in Service Bus and should be ported to Event Hubs and don't have issues to track them

Improvements to receive operations:

@ramya-rao-a ramya-rao-a added this to the Sprint 153 milestone May 13, 2019
@ShivangiReja ShivangiReja self-assigned this May 14, 2019
@ShivangiReja
Copy link
Member

Close with #2894, #2900, #2902, #2923

@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs
Projects
None yet
Development

No branches or pull requests

2 participants