Skip to content
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
wants to merge 19 commits into
base: main
Choose a base branch
from
Open

Conversation

pull[bot]
Copy link

@pull pull bot commented Dec 6, 2024

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 : )

… 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]>
@pull pull bot added the ⤵️ pull label Dec 6, 2024
danielmarbach and others added 17 commits December 8, 2024 10:24
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.
* Use `Guid.NewGuid` to ensure unique name
* No need to delete first as names should be unique

* Use Guids for uniqueness
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.
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants