| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Pair: @dcorbacho.
Closes #2077.
References #2049.
|
| |
|
|
|
|
|
|
| |
I observed no functional changes around log rotation.
These assertions depend on internal file management
aspects of Lager, so let's update them and see.
References #2068, #2059.
|
| | |
|
| |\
| |
| | |
Upgrade bundled Cuttlefish to 2.3.0 produced on Erlang/OTP 21.3
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
Add marker rabbit_queue_type behaviour
|
| |/
|
|
|
|
|
|
| |
And use the implementing module as the value of the amqqueue record
`type` field. This will allow for easy dispatch to the queue type
implementation.
Make amqqueue compatible with the classic queue tag
|
| |\
| |
| | |
Dialyzer fixes
|
| | | |
|
| |\ \
| |/
|/| |
Publish messages_persistent
|
| |/
|
|
|
|
| |
They were only sent on the event
[#167649915]
|
| |
|
|
|
|
|
|
|
|
|
| |
Kyorai/cuttlefish@fff866a3a22dc2a8f3d23aa13933b90542485728"
This reverts commit ebfb4ea9b09409a9e31008b3494a17062ed5211d.
`config_schema` tests that combine a new style and advanced config
snippets fail. This needs further investigation.
References Kyorai/cuttlefish#2.
|
| |
|
|
|
|
|
|
| |
Kyorai/cuttlefish@fff866a3a22dc2a8f3d23aa13933b90542485728
All tests pass locally, let's see how package tests do.
References Kyorai/cuttlefish#2.
|
| |\
| |
| | |
Add get empty counter to quorum queues
|
| | |
| |
| |
| | |
[#167667854]
|
| |\ \
| | |
| | | |
Publish persistent stats for quorum queues
|
| | |/
| |
| |
| | |
[#167649915]
|
| | | |
|
| |/ |
|
| | |
|
| |\
| |
| | |
Queue, connection and exchange count functions
|
| | |\
| |/
|/| |
|
| | |
| |
| |
| |
| |
| | |
in OTP 23 pids hava new type tag: 88 (previously 103). To account for
this copy whatever the local pid returns and insert that in the output
binary.
|
| |\ \
| | |
| | | |
Helpers for CLI logs command
|
| | |\ \ |
|
| | |\ \ \ |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
To stream log updates to remote node there will be a process started
on the server node to read the log file and send its contents.
Unfortunately it's hard to detect the file to be deleted and the streaming
process will try indefinitely to get more data from the deleted file.
Streaming process is linked to the CLI process and should eventually stop.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Reads last N lines, separated by \n from the file.
This should be portable enough to windows.
|
| |\ \ \ \ \
| |_|_|/ /
|/| | | | |
Pass all members to synchronous Ra operations
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Support client-driven refresh of expiring credentials
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
instead of disabling the cache entirely. Disabling the
cache has a significant double digit throughput drop effect
on super fast publishers, as demonstrated by
a number of PerfTest benchmarks.
Per discussion with @acogoluegnes, @kjnilsson.
References rabbitmq/rabbitmq-auth-backend-oauth2#28.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Per discussion with @acogoluegnes.
While at it, correct a few type spec issues reported
by Dialyzer.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Integration tests in rabbitmq_auth_backend_oauth2
cover more ground. In addition we would have to
introduce a dummy backend that supports state
updates which @acogoluegnes and I decided against.
So all the testing currently happens in the only
backend plugin that actually supports credential
expiration and state/secret updating.
|
| | | | | | | |
|
| | |\ \ \ \ \
| | | |_|/ /
| | |/| | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Corrects a typo in 97f3f52.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Spotted by @acogoluegnes.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Channel processes use it for authz backend checks. The record
is identical to that of connection process (and originates from it), so
a simple cast to update the field is appropriate: any errors would
be handled and communicated back by the connection itself.
Per discussion with @acogoluegnes and @kjnilsson.
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Provide timeout to add_member command
|
| | | |/ / / /
| |/| | | |
| | | | | |
| | | | | | |
[#166670827]
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
... in `undefined_channel_source` testcase. This testcase fails
transiently and it looks like a timing issue:
channel_source_SUITE > non_parallel_tests > undefined_channel_source
#1. {error,
{{badmatch,[]},
[{channel_source_SUITE,undefined_channel_source1,1,
[{file,"test/channel_source_SUITE.erl"},{line,138}]},
{rpc,'-handle_call_call/6-fun-0-',5,
[{file,"rpc.erl"},{line,197}]}]}}
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
Remove deprecation of force_event_refresh message
|