-
Notifications
You must be signed in to change notification settings - Fork 20
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
No longer possible to bind queues in parallel #94
Labels
bug
Something isn't working
Comments
It was probably not intended. Probably easy to find the commit that broke it using https://git-scm.com/docs/git-bisect |
That's a good idea, I'll try that. |
Looks like d464ef2 is responsible for this. |
So it actually broke in v3.1.0, v3.0.0 works fine. |
jscheffner
changed the title
No longer to bind queues in parallel
No longer possible to bind queues in parallel
Oct 5, 2023
Suspected it had with that todo.. will have to find a solution
…On Thu, 5 Oct 2023, 10:52 Jonas Scheffner, ***@***.***> wrote:
So it actually broke in v3.1.0, v3.0.0 works fine.
—
Reply to this email directly, view it on GitHub
<#94 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABL6TTU7QMF7DTC6WH5V5DX5ZYNLAVCNFSM6AAAAAA5SSU5IGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBYGQYDQNZWG4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
A spec is the first step
…On Thu, 5 Oct 2023, 11:44 Carl Hörberg, ***@***.***> wrote:
Suspected it had with that todo.. will have to find a solution
On Thu, 5 Oct 2023, 10:52 Jonas Scheffner, ***@***.***>
wrote:
> So it actually broke in v3.1.0, v3.0.0 works fine.
>
> —
> Reply to this email directly, view it on GitHub
> <#94 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AABL6TTU7QMF7DTC6WH5V5DX5ZYNLAVCNFSM6AAAAAA5SSU5IGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBYGQYDQNZWG4>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey, after updating to v3 this is no longer working
A
is still logged,B
is not. The promise keeps pending when binding two routing keys at the same time. If run with v2 the Promise resolves andB
is logged.Binding sequentially works with both versions:
This is a bit unexpected and I didn't find anything in the changelog that suggests that this change was intended.
The text was updated successfully, but these errors were encountered: