Enable rabbitmq-client event logging when tests are verbose
#1559
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lukebakken
force-pushed
the
lukebakken/fix-eventsource
branch
2 times, most recently
from
06a4924 to
009eaf4
Compare
* Fix event ID issue by duplicating Error Event 3 code for each target framework. * Fix strange null reference exception by not using `??=` lazy init. * * Remove `Message` from `RabbitMqClientEventSource` because it does not work as intended. * Handle task canceled exception in main loop. * Ignore a couple exception cases in the `MainLoop`
lukebakken
force-pushed
the
lukebakken/fix-eventsource
branch
from
009eaf4 to
2829e88
Compare
This was referenced Sep 15, 2025
This was referenced Oct 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
??=lazy init.