| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A feature flag can be marked as "auto-enable" by setting `auto_enable` to
true in its properties.
An auto-enable feature flag is automatically enabled as soon as all
nodes in the cluster support it. This is achieved by trying to enable it
when RabbitMQ starts, when a plugin is enabled/disabled or when a node
joins/re-joins a cluster. If the feature flag can't be enabled, the
error is ignored.
An auto-enable feature flag also implicitly depends on
`feature_flags_v2`.
However, it should be used cautiously, especially if the feature flag
has a migration function, because it might be enabled at an
inappropriate time w.r.t. the user's workload.
|
| |\
| |
| | |
Remove a one-liner
|
| |/
|
|
|
|
|
| |
@kjnilsson:
> why that line of code is a oneliner I have no idea
> should really be a pattern match in the function head
|
| |\
| |
| | |
Refactor quorum queue periodic metric emission
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Primarily to avoid the transient process that is spawned every
Ra "tick" to query the quorum queue process for information that could
be passed in when the process is spawned.
Refactored to make use of the overview map instead of a custom
tuple.
Also use ets:lookup_element where applicable
|
| |\ \
| | |
| | | |
Support management path prefix when using OAuth2
|
| | | |
| | |
| | |
| | |
| | | |
Updated selenium tests to tests against 2 path
segments rather than just one
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
Update Stream protocol document
|
| | | | |
| | | |
| | | | |
As per conversation with @acogoluegnes, the frame `SaslHandshakeRequest` does not have a field `mechanism`. This field actually used in `SaslHandshakeResponse` and `SaslAuthenticateRequest` frames.
|
| |\ \ \ \
| |/ / /
|/| | | |
Fix docs for rabbitmqctl restart_vhost
|
| |/ / / |
|
| |\ \ \
| |_|/
|/| | |
Add 'mix format --check-formatted' to the rabbitmqctl_tests in bazel
|
| |/ /
| |
| |
| | |
to match the check on the Makefile side that was recently introduced
|
| |\ \
| | |
| | | |
Use Elixir 1.13.x with otp 24.x in bazel build
|
| |/ / |
|
| |\ \
| | |
| | | |
Adopt otp 25.1.1
|
| |/ / |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
Fix channel crash when cancelling then consuming using the same consumer tag and channel
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As since QQ v2 we don't ever keep any messages in memory and we need
to read them from the log. The only way to do this is by using an
aux command.
Execute get_checked_out query on local members if possible
This reduces the change of crashing a QQ member during a live upgrade
where the follower does not have the appropriate code in handle_aux
|
| | |
| |
| |
| |
| |
| | |
By returning the next msg id for a merged consumer the rabbit_fifo_client
can set it's next expected msg_id accordingly and avoid triggering
a fetch of "missing" messages from the queue.
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Fixes #5980
Reference rabbitmq/rabbitmq-metronome#16
|
| |\ \ \
| |/ /
|/| |
| | | |
rabbitmq/dependabot/github_actions/main/actions/cache-3.0.10
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bumps [actions/cache](https://github.com/actions/cache) from 3.0.9 to 3.0.10.
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](https://github.com/actions/cache/compare/v3.0.9...v3.0.10)
---
updated-dependencies:
- dependency-name: actions/cache
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
|
| |\ \
| | |
| | | |
Refactor how selenium suites are run
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
rabbitmq/rabbitmq-server-5956-stream-route-partitions-response-prefix
Fix keys for route and partitions responses
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
These 2 responses were not using the `rabbit_stream_core` utilities
so they were not using the "prefix" for responses.
Fixes #5956
|
| |\ \ \ \
| | | | |
| | | | | |
Standardize CLI formatting with mix format
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | |/ / / |
|
| |\ \ \ \
| |_|/ /
|/| | | |
Use rules_erlang 3.7.2
|
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | | |
rabbitmq/add-super-stream-cli-leader-locator-balanced
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
For the CLI, otherwise all the created individual streams end
up with their leader on the same node, whichi is not what we
want. "balanced" is a reasonable default and it can be overridden
anyway.
|
| |\ \ \
| |/ /
|/| | |
Add otp 25.1 to //packaging/docker-image:rabbitmq
|
| | | | |
|
| |/ / |
|