-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[SB] Link-Detach #34820
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
[SB] Link-Detach #34820
Conversation
|
/azp run python - servicebus - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
sdk/servicebus/azure-servicebus/azure/servicebus/_pyamqp/aio/_link_async.py
Show resolved
Hide resolved
|
We are raising a There is potentially another way to handle this by attaching right away (instead of closing the connection and going from scratch) when we receive such a detach. I wonder if doing that would cause some other scenario to fail |
sdk/servicebus/azure-servicebus/azure/servicebus/_pyamqp/aio/_link_async.py
Outdated
Show resolved
Hide resolved
|
API change check APIView has identified API level changes in this PR and created following API reviews. |
|
/azp run python - servicebus - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run python - servicebus - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Handling of service initiated detach errors when the error condition is None as it was causing the code to stall after sending out the responding detach.
Repro is to disable an entity and within process-incoming-frames frame[2][0] if it is a "link-detach-forced" set frame[2] = None
frame -
<- DetachFrame(handle=2, closed=True, error=None)