forked from rabbitmq/rabbitmq-dotnet-client
-
Notifications
You must be signed in to change notification settings - Fork 1
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
[pull] main from rabbitmq:main #1
Open
pull
wants to merge
19
commits into
BrighterCommand:main
Choose a base branch
from
rabbitmq:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
… in earlier versions (#1735) * * Bump regular System.Text.RegularExpressions due to detected cve * Increment the nuget cache version to invalidate the cache * Add `Directory.Packages.props` to GHA NuGet cache * * Set `TestTfmsInParallel` to `false` --------- Co-authored-by: Luke Bakken <[email protected]>
Simplify preprocessor directives
This uses the current time and a short uuid when creating test queues and exchanges. Copied from rabbitmq/rabbitmq-amqp-dotnet-client * Ensure unique toxic name because integration tests run in parallel per-TFM now. * Use unique queue names. * Update toxiproxy executables. * Collect toxiproxy server output on failure. * Add retries to starting a Toxiproxy instance.
Address flaky integration tests
* Use `Guid.NewGuid` to ensure unique name * No need to delete first as names should be unique * Use Guids for uniqueness
Toxiproxy manager change
This should fix the toxiproxy issues once and for all 🤞
Set TestTfmsInParallel to false for Integration tests
- Swap order of queue name and operation in Activity name - Add messaging.operation.name tag
More updates for the current OTel (OpenTelemetry) conventions
Test related package updates.
* Remove Ductus.FluentDocker - people can start their own RabbitMQ.
Update NuGet packages
Update copyright year to 2025
Fixes #1749 * Ensure `Dispose` and `DisposeAsync` are idempotent and thread-safe. * Use TaskCompletionSource when `HandleChannelCloseAsync` runs to allow dispose methods to wait. * Use `Interlocked` for thread safety. * I like `_isDisposing` better. So sue me! * Move the `Interlocked.Exchange` code to a getter, for readability. * Minor nullable change. Co-authored-by: Daniel Marbach <[email protected]>
…x-co-author Ensure broker-originated channel closure completes
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.
See Commits and Changes for more details.
Created by pull[bot] (v2.0.0-alpha.1)
Can you help keep this open source service alive? 💖 Please sponsor : )