| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Which can be used to build the artifact with bazel
|
| |\
| |
| | |
Adopt latest bazel-erlang
|
| | |
| |
| |
| | |
- bazel-erlang@5bf79d7fb9a2c8bf7bfb6a90f5104a10b5c9107b
|
| |\ \
| | |
| | | |
Stream flake fixes
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
(cherry picked from commit 77d8b6a9e8da5fe7b5eb3ab7f2c3b38fc391abff)
|
| | | | |
|
| |\ \ \
| |_|/
|/| | |
Fix rabbitmq.conf translation rule for OAuth2 signing keys
|
| |/ /
| |
| |
| |
| | |
The structure of the signing_keys map should be `<<"id">> => {pem, <<"key">>}`.
Previously it was mapped directly as `<<"id">> => <<"key">>`.
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |\
| |
| | |
Further tweaks to GitHub Actions networking keep-alive
|
| |/ |
|
| |\
| |
| | |
Distribution listener settings support in rabbitmq.conf
|
| | |
| |
| |
| |
| |
| |
| |
| | |
* distribution.listener.interface
* distribution.listener.port_range.min
* distribution.listener.port_range.max
Closes #3739
|
| |\ \
| | |
| | | |
Fixup the "Failed to symlink private_log directory." error in bazel
|
| | |/
| |
| |
| |
| | |
While it doesn't cause any tests to fail, it's confusing to see it in
the logs
|
| |\ \
| |/
|/| |
Stream coordinator: only update amqqueue record if stream id matches
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| |
| |
| | |
When the suite passes, it's about 120 seconds total, so 5 minutes per
case seems to be too much. Additionally, if the suite times out at the
bazel level, we get no logs, so the cause of the timeout is unclear.
|
| |\ \
| | |
| | | |
Use --remote_download_minimal and Actions Cache
|
| | | | |
|
| | | | |
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
rabbitmq/lukebakken/core-started-before-postlaunch-phase
Set core_started before running postlaunch phase
|
| | | |
| | |
| | |
| | | |
Since the postlaunch phase is async there is a slight chance that rabbit_direct connections will not see core_started if attempted during postlaunch
|
| | | |
| | |
| | |
| | | |
https://www.erlang.org/doc/man/erpc.html#call-5
|
| |\ \ \
| | | |
| | | | |
Use externailzed rbe config in bazel
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Fix description of "deliver" command in RabbitMQ Streams protocol documentation
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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.
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Prevent crash logs when mqtt user is missing permissions
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| |\ \ \ \ \ \
| |_|_|/ / /
|/| | | | /
| | |_|_|/
| |/| | | |
Stream coordinator: reset reply_to for delete_stream command
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Based on https://github.com/actions/virtual-environments/issues/1187
and per buildbuddy's suggestion
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This reverts commit 82508ba167e94d42067e7562a0589b1d977d6a86, reversing
changes made to 115b951b9cc718fd40aa560e49319f57c762f05d.
|
| | | | |
| | | |
| | | |
| | | | |
As they can be run manually if needed on PR branches
|
| |\ \ \ \
| |/ / /
|/| | | |
Use externailzed rbe config in bazel
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Generate the rabbitmqadmin cli under bazel
|
| | |/ / / |
|
| |\ \ \ \
| | | | |
| | | | | |
Expose pending enqueues in quorum queue overview
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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.
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Avoid slow mnesia transaction on QQ init
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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.
|
| | |_|/ / /
|/| | | | |
|
