| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
instead of maps:find/2.
This creates less garbage.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Nowadays, we have erlang:atom_to_binary/1.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This makes it easier to see that a module is an event handler.
Furthermore the compiler checks for required callback functions.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Stop sending connection_stats from protocol readers to rabbit_event.
Stop sending queue_stats from queues to rabbit_event.
Sending these stats every 5 seconds to the event manager process is
superfluous because noone handles these events.
They seem to be a relict from before rabbit_core_metrics ETS tables got
introduced in 2016.
Delete test head_message_timestamp_statistics because it tests that
head_message_timestamp is set correctly in queue_stats events
although queue_stats events are used nowhere.
The functionality of head_message_timestamp itself is still tested in
deps/rabbit/test/priority_queue_SUITE.erl and
deps/rabbit/test/temp/head_message_timestamp_tests.py
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Fix flaky rabbit_fifio_int:credit test
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Prior to this commit test credit() was flaky.
It used to fail with:
```
rabbit_fifo_int_SUITE:credit failed on line 437
Reason: {badmatch,{[{{resource,"/",queue,<<"credit">>},credit,1,fals...}
```
In that case returned events were:
```
Events=[{ra_event,{credit,ct_rabbit@nuc},{applied,[{3,ok}]}},
{ra_event,{credit,ct_rabbit@nuc},
{machine,{delivery,<<"tag">>,[{1,{0,m2}}]}}}]
```
instead of:
```
Events=[{ra_event,
{credit,ct_rabbit@nuc},
{machine,{delivery,<<"tag">>,[{1,{0,m2}}]}}},
{ra_event,
{credit,ct_rabbit@nuc},
{applied,
[{3,ok},
{4,
{multi,
[{send_credit_reply,0},
{send_drained,{<<"tag">>,3}}]}}]}}]
```
The fix is we wait for both ra 'applied' events.
|
| |\ \ \ \ \
| |/ / / /
|/| | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
that suite was renamed
|
| | | | | | |
|
| | | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Crash when a sub-command times out
* Use atom `NaN` when free space can not be determined
Fixes #5721
Use port to run /bin/sh on `unix` systems to then run `df` command
Update disk monitor tests to not use mocks because we no longer use rabbit_misc:os_cmd/1
|
| |\ \ \ \
| | | | |
| | | | | |
Fix typo in plugins.mk
|
| | |/ / /
| | | |
| | | | |
overriden -> overridden
|
| |\ \ \ \
| |/ / /
|/| | | |
3.11 release notes: reword as suggested in #5319
|
| |/ / / |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Not useful anymore.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is a follow-up commit of https://github.com/rabbitmq/rabbitmq-server/pull/5693
The allowed values of emqtt client library are:
```
{proto_ver, v3 | v4 | v5}
```
Therefore, `{proto_ver, 3}` did not have any effect and used the default
protocol version v4.
Let's fix the misleading version in our tests and be explicit that
we use v4.
|
| | |/
|/| |
|
| |\ \
| | |
| | |
| | |
| | | |
rabbitmq/rabbitmq-server-5708-whitelist-elixir-1.14
CLI tools: whitelist Elixir 1.14
|
| | |\ \
| |/ /
|/| | |
|
| | | | |
|
| |/ /
| |
| |
| | |
As suggested by @VlkrS in #5708
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since I force pushed to master branch of
https://github.com/ansd/emqtt, the old commit does
not belong to any branch anymore.
While Bazel is happy, make complains:
```
make -C deps/rabbitmq_mqtt ct
DEP emqtt (f6d7ddd391890f4db5f77c775e83cf0ffe3d2d76)
fatal: reference is not a tree: f6d7ddd391890f4db5f77c775e83cf0ffe3d2d76
```
|
| | | |
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
And capture screenshots on all test cases
on teardown if the test failed
Use headless chrome 104
|
| | | |
| | |
| | |
| | | |
and use 105 of headless chrome
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Rather than logging directly via console.log
we do it via the Logger library provided by
oidc-client which allows to use logging levels
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
using makefile
(cherry picked from commit 2d00d453d2c529ae038a5713e3f24d524545e771)
|
| | | |
| | |
| | |
| | | |
when running in headless mode
|
| | | |
| | |
| | |
| | |
| | |
| | | |
When the management ui session times out
the user should be logged out also from
the idp
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The issue was primarily that UAA was
not properly configured. We had to whitelist
the uri used for logout otherwise UAA redirects
to its login page
WIP verify that logout.js works when running in
headless mode. For that we need a docker image
and at the moment, make docker-image is not
working because it is still using old otp 24.0.2
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
To work on the github action and then
merge back to this branch
|
