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

[EventHub] remove uamqp imports from EventData/EventDataBatch into plugin module #24259

Closed

Conversation

swathipil
Copy link
Member

related to: #21246
fixes: #24239

swathipil and others added 18 commits July 12, 2021 15:08
* initial changes for receiving

* undo __init__ aio

* vendor

* remove c/pyx files

* adams comments
* draft send port

* copy and paste code changes in amqp

* simple stress test scripts for sending and receiving

* review feedbacks
* port amqp send large message

* send perf test in parallel

* use context manager for executor

* add throughput

* improve test code

* update test matrix

* update test

* handle server busy

* fix timeout

* precision to 2 decimal points

* update pyamqp changes and update tests
…2397)

* copy amqp changes

* eh python amqp integration

* fix time unit

* rename module pyamqp to _pyamqp

* more pyamqp to _pyamqp

* simplify todo
* cherry pick changes

* update docs

* cherry pick fixed retry PR

* minor fix

* fix mypy, pylint, brokenlink

* update doc

* opt out mypy/pylint/api stub

* try opt out checkpointstore in ci and test

* fix

* more fixes

* furuther opt out tests

* update tests

* bump version

* fix __str__

* add test play holder

* ignore azure checkpoinstore aio in ci

Co-authored-by: swathipil <76007337+swathipil@users.noreply.github.com>
* async port

* add scripts for tests

* update async perf test scripts

* fix test scripts

* amqp implementation update + eh update + sync perf test scripts

* update pyamqp and eh async impl and test scripts

* update pyamqp async impl

* fix bug

* fix pyamqp transport ssl setting and asyncio exception module import

* use ensure future for 3.6

* update token generation to return bytes to avoid breaking changes

* update docs
Increment package version after release of azure-eventhub
* stop spawning too much coroutines

* improve send

* async recv perf improvement

* async perf improve

* update version

* align with sync imple

* update method name

* remove redundant except catch
Increment package version after release of azure-eventhub
@ghost ghost added the Event Hubs label Apr 29, 2022
@azure-sdk
Copy link
Collaborator

API change check for azure-eventhub

API changes have been detected in azure-eventhub. You can review API changes here

API changes

-             partition_key: str = None
+             partition_key: str = None, 
+             **kwargs

swathipil and others added 10 commits May 3, 2022 16:44
* Initial implementation

* http proxy support

* change impl

* more changes

* working sol

* async impl

* Update sdk/eventhub/azure-eventhub/azure/eventhub/_pyamqp/_transport.py

* more changes

* sasl mixin

* Update sdk/eventhub/azure-eventhub/azure/eventhub/_pyamqp/message.py

* refactor

* Update sdk/eventhub/azure-eventhub/azure/eventhub/_pyamqp/_transport.py

* Update sdk/eventhub/azure-eventhub/azure/eventhub/_pyamqp/_transport.py

* oops

* comments

* comment

* Apply suggestions from code review

Co-authored-by: swathipil <76007337+swathipil@users.noreply.github.com>

* comments

* changes

* async test

* rasie

* lint

* changelog

* version

* comments

* move path to EH

Co-authored-by: swathipil <76007337+swathipil@users.noreply.github.com>
* Initial implementation

* http proxy support

* change impl

* more changes

* working sol

* async impl

* Update sdk/eventhub/azure-eventhub/azure/eventhub/_pyamqp/_transport.py

* more changes

* sasl mixin

* Update sdk/eventhub/azure-eventhub/azure/eventhub/_pyamqp/message.py

* refactor

* Update sdk/eventhub/azure-eventhub/azure/eventhub/_pyamqp/_transport.py

* Update sdk/eventhub/azure-eventhub/azure/eventhub/_pyamqp/_transport.py

* oops

* comments

* comment

* Apply suggestions from code review

Co-authored-by: swathipil <76007337+swathipil@users.noreply.github.com>

* comments

* changes

* async test

* rasie

* lint

* changelog

* version

* comments

* move path to EH

* Fix typo

Co-authored-by: swathipil <76007337+swathipil@users.noreply.github.com>
* initial changes for receiving

* undo __init__ aio

* vendor

* remove c/pyx files

* adams comments
* draft send port

* copy and paste code changes in amqp

* simple stress test scripts for sending and receiving

* review feedbacks
* port amqp send large message

* send perf test in parallel

* use context manager for executor

* add throughput

* improve test code

* update test matrix

* update test

* handle server busy

* fix timeout

* precision to 2 decimal points

* update pyamqp changes and update tests
…2397)

* copy amqp changes

* eh python amqp integration

* fix time unit

* rename module pyamqp to _pyamqp

* more pyamqp to _pyamqp

* simplify todo
* cherry pick changes

* update docs

* cherry pick fixed retry PR

* minor fix

* fix mypy, pylint, brokenlink

* update doc

* opt out mypy/pylint/api stub

* try opt out checkpointstore in ci and test

* fix

* more fixes

* furuther opt out tests

* update tests

* bump version

* fix __str__

* add test play holder

* ignore azure checkpoinstore aio in ci

Co-authored-by: swathipil <76007337+swathipil@users.noreply.github.com>
@check-enforcer
Copy link

check-enforcer bot commented Jun 2, 2022

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run python - [service] - ci

@swathipil swathipil mentioned this pull request Jul 13, 2022
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[EventHubs] Misspelled private method in _producer_client.py
6 participants