-
Notifications
You must be signed in to change notification settings - Fork 534
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
fix(amqplib): use extracted context for message consuming #1354
fix(amqplib): use extracted context for message consuming #1354
Conversation
Thanks for the fix. Can you please add a test for that? |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #1354 +/- ##
=======================================
Coverage 96.08% 96.08%
=======================================
Files 14 14
Lines 893 893
Branches 191 191
=======================================
Hits 858 858
Misses 35 35 |
- fixes baggage propagation
908cabb
to
7db0a1f
Compare
I can't make the repository work on my machine (node-gyp native build problems). The scoped bootstrap is also failing. It's taking too much time for me, I can't continue here :( I pushed the untested/incomplete test |
so, got it running in WSL. and funny, the test I wrote worked on the first try 🎉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Can you please fix the linting?
hmm...it's not the amqplib module that is failing. IMHO the linting does not fail because of my change |
it's in amqplib tests |
ah, I see. I fixed it, thank you for the other changes. |
CI fails for node 18. Not sure why nor if it is caused by this PR as CI logs don't show any useful hint. |
fixes #1351 baggage propagation
Which problem is this PR solving?
the baggage is lost while consuming messages since the extracted context isn't passed in
Short description of the changes
we pass in the extracted context to the
context.with(....)