| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
Which can be used to build the artifact with bazel
(cherry picked from commit 11fd866247549505b96a323f3d4690d62345c298)
# Conflicts:
# BUILD.bazel
|
| |\
| |
| | |
Use bazel-erlang 1.4.0
|
| | |
| |
| |
| | |
(cherry picked from commit 8c0eece3cdd1fcd6a3e0d85c48101c7de519df43)
|
| |/ |
|
| |\
| |
| | |
Stream flake fixes (backport #3752)
|
| |/
|
|
| |
(cherry picked from commit 8542b54f7e7a881555b3b1e87d95a84022bcd90c)
|
| | |
|
| |
|
|
| |
(cherry picked from commit 5d91e958c2b41ca9f440b9072207a8bae51dbe88)
|
| |\
| |
| | |
Fix rabbitmq.conf translation rule for OAuth2 signing keys (backport #3759)
|
| |/
|
|
|
|
|
| |
The structure of the signing_keys map should be `<<"id">> => {pem, <<"key">>}`.
Previously it was mapped directly as `<<"id">> => <<"key">>`.
(cherry picked from commit acf474e0566eb6baf8328e9a9e2abb3ec3fc0890)
|
| |\
| |
| | |
Set core_started before running postlaunch phase (backport #3685)
|
| | |
| |
| |
| |
| |
| | |
Since the postlaunch phase is async there is a slight chance that rabbit_direct connections will not see core_started if attempted during postlaunch
(cherry picked from commit 223581f6fb4c0cecf7a4a9d13a270a133c40ccb4)
|
| | |
| |
| |
| | |
(cherry picked from commit aa666133b6f236c2b1a724663b5434be55d56e9f)
|
| | |
| |
| |
| | |
(cherry picked from commit e52a127ef9f9011051ecd416ca8730751a15cdc8)
|
| | |
| |
| |
| | |
(cherry picked from commit 6111029ceb8177e57c10b6e86761fd92bb96a358)
|
| |\ \
| | |
| | | |
Further tweaks to GitHub Actions networking keep-alive (backport #3748)
|
| |/ /
| |
| |
| | |
(cherry picked from commit ca129c87cfd4621f54ac7c2b39e780b3da69bb93)
|
| |\ \
| | |
| | | |
Distribution listener settings support in rabbitmq.conf (backport #3740)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* distribution.listener.interface
* distribution.listener.port_range.min
* distribution.listener.port_range.max
Closes #3739
(cherry picked from commit 8a30cf1c86640cda7bc66563d477869e0ea29a83)
|
| |\ \ \
| |/ /
|/| | |
Fixup the "Failed to symlink private_log directory." error in bazel (backport #3738)
|
| |/ /
| |
| |
| |
| |
| |
| | |
While it doesn't cause any tests to fail, it's confusing to see it in
the logs
(cherry picked from commit 3b48ebabf7e029b20d8dc56077e87969d70ca8fb)
|
| |\ \
| | |
| | | |
Stream coordinator: only update amqqueue record if stream id matches (backport #3731)
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
From the coordinator's POV each stream has a unique id consisting of the
vhost, queuename and a high resolution timestamp even if several stream ids
relate to the same queue record.
When performing the mnesia update the coordinator now checks that the current stream id
matches that of the update_mnesia action and does not change the queue record if
the stream id is not the same.
This should avoid "old" incarnations of a stream queue updating newer ones
with incorrect information.
(cherry picked from commit bc7b339e7ac87c43f7b42557444c1b5a20cf0263)
|
| |\ \
| |/
|/| |
Use --remote_download_minimal and Actions Cache (backport #3735)
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
(cherry picked from commit 470c94692c3c6f0457d77b984b23ce9a441b97b0)
# Conflicts:
# .github/workflows/test-mixed-versions.yaml
# .github/workflows/test.yaml
|
| | |
| |
| |
| | |
(cherry picked from commit 74ae98473e2f578f0d4d3434feebe231b3c5ce1a)
|
| |/
|
|
| |
(cherry picked from commit 943949d5097c0a8f249a2dfa742b8ca6c6106732)
|
| |\
| |
| | |
Use externailzed rbe config in bazel (backport #3722)
|
| |/
|
|
| |
(cherry picked from commit df0fa0ce6087bdae7a02aa85a5804c5fbd01a210)
|
| |
|
|
|
|
|
| |
Based on https://github.com/actions/virtual-environments/issues/1187
and per buildbuddy's suggestion
(cherry picked from commit 983afafdeeda936353c2727f0cea0baaac8afa48)
|
| |
|
|
|
| |
https://www.erlang.org/doc/man/erpc.html#call-5
(cherry picked from commit 1f7db0fa35cf408b5588f7701946d4e163b9df8a)
|
| |\
| |
| | |
Fix description of "deliver" command in RabbitMQ Streams protocol documentation (backport #3723)
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
Add missing fields - chunk type, timestamp, trailer length and reserved.
The fields are added after looking at
https://github.com/rabbitmq/rabbitmq-stream-java-client/blob/3fd348d2250c6b9a55d9c0a968d63fe04f46e4b6/src/main/java/com/rabbitmq/stream/impl/ServerFrameHandler.java#L267
https://github.com/qweeze/rstream/blob/master/rstream/schema.py#L376
Change type of "version" field - it shall be uint16 like in other
commands.
(cherry picked from commit b4f39031f6cf2dadf522a56507364d24d0faf200)
|
| |\
| |
| | |
Stream coordinator: reset reply_to for delete_stream command (backport #3716)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
So that a reply is sent to the caller immediately after the command has
been processed as intended. Previously it was possible if reply_to was
already set that a reply never was sent to the caller and the caller
times out. This should improve some flakyness in the rabbit_stream_queue suite
as well.
Strictly this is a change that introduces indeterminism in the coordinator
state machine as during an upgrade different members may run different code
for this command. But as this state only affects side effects (replies) and
the state for the streams affected will shortly be removed this is very
unlikely to cause any real issues.
(cherry picked from commit 7e4a33708b1c3b05c4282136b4eb81113628e5a8)
|
| |\ \
| |/
|/| |
Prevent crash logs when mqtt user is missing permissions (backport #3714)
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes #2941
This adds proper exception handlers in the right places. And tests
ensure that it indeed provides nice neat logs without large
stacktraces for every amqp operation.
Unnecessary checking for subscribe permissions on topic was dropped,
as `queue.bind` does exactly the same check. Topic permissions tests
were also added, and they indeed confirm that there was no change in
behaviour.
Ideally the same explicit topic permission check should be dropped for
publishing, but it's more complicated - so for now there only a
detailed comment in the source code explaining it.
A few other things were also optimized away:
- Using amqp client to test for queue existence
- Creating queues/starting consumptions too eagerly, even if not yet
requested by client
(cherry picked from commit e0723d5e6620182380566ee36d381af068ecf43d)
|
| |\
| |
| | |
Generate the rabbitmqadmin cli under bazel (backport #3710)
|
| |/
|
|
| |
(cherry picked from commit 9c70b3220a0e92832193fef13e210b8d246a79e2)
|
| |\
| |
| | |
Expose pending enqueues in quorum queue overview (backport #3656)
|
| |/
|
|
|
|
|
|
|
| |
debugging of situation where messages may be stuck.
Also cancel rabbit_fifo_client timer after message resend to avoid
resending them again when the timer triggers.
(cherry picked from commit bf6c7476070958f986cf8b892c3e1abb295d2c12)
|
| |\
| |
| | |
Avoid slow mnesia transaction on QQ init (backport #3676)
|
| |/
|
|
|
|
|
|
| |
As we only need to make sure the rabbit_queues table is populated
use a dirty write function that only does this instead. This could potentially
half recovery times for many QQ scenarios.
(cherry picked from commit d2fde27b565780c2b443138557c27f7ee650f250)
|
| |\
| |
| | |
Adopt otp 24.1.5 for OCI workflow (backport #3699)
|
| |/
|
|
| |
(cherry picked from commit 979e984299c885213a7f970ba4eb20337ac59ed1)
|
| |\
| |
| | |
Add --remote_download_toplevel to the bazel config (backport #3700)
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
| |
Based on the testing and advice from BuildBuddy:
Network limitations/flakiness in GitHub actions can be mitigated by
reducing the number of artifacts that get downloaded. Since we only
use bazel for testing currently, we don't actually care about the
artifacts, so there is no downside to the flag.
If this isn't enough, we can try the --remote_download_minimal flag,
which limits the amount of downloads even further.
(cherry picked from commit f92e6b436cd8a510d5386009fb3a0db6ff9c578c)
|
| |
|
|
| |
(cherry picked from commit 6182505828c30f79b4fe5a99931a197f89bba04e)
|
| |
|
|
|
|
|
|
|
|
| |
Pre-render prometheus labels
(cherry picked from commit 1b7a8f869e6392719f4919f9a4ed06802af90454)
Conflicts:
rabbitmq-components.mk
workspace_helpers.bzl
|
