| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| | |
Use erlang 26.0 instead of rc3 in bazel
|
| | | |
|
| |\ \
| | |
| | | |
Fix filter for "Discarding message..." logs
|
| | |/
| |
| |
| |
| |
| | |
The format string is hardcoded as "~s~n" in
[ERTS](https://github.com/erlang/otp/blame/OTP-26.0/erts/emulator/beam/utils.c#L878).
Using unicode modifier resulted in a mismatch.
|
| |\ \
| |/
|/| |
3.12.0 release notes updates
|
| | | |
|
| |/ |
|
| |\
| |
| | |
Adopt otp
|
| |/ |
|
| |\
| |
| | |
Use the latest rules_erlang
|
| | | |
|
| |\ \
| | |
| | | |
Fix offline `make dist`
|
| | |/
| |
| |
| |
| |
| |
| | |
See #7869. #7875 resulted in elixir apps (besides the cli) in the deps
dir. This triggered dormant makefile logic to compile such deps. It
turns out that it's unnecessary to pre-compile them, given the cli's
mix.exs file.
|
| |\ \
| |/
|/| |
Configure Oauth scope prefix
|
| | | |
|
| | | |
|
| |/
|
|
| |
separate from resource_server_id
|
| |\
| |
| | |
Github Actions pipeline to compare build systems nightly
|
| | |
| |
| |
| | |
To catch any drift between the builds
|
| |\ \
| |/
|/| |
Move plugin rabbitmq-message-timestamp to the core
|
| | |
| |
| |
| |
| |
| |
| |
| | |
as it nicer categorises if there will be a future
"message_interceptors.outgoing.*" key.
We leave the advanced config file key because simple single value
settings should not require using the advanced config file.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As reported in https://groups.google.com/g/rabbitmq-users/c/x8ACs4dBlkI/
plugins that implement rabbit_channel_interceptor break with
Native MQTT in 3.12 because Native MQTT does not use rabbit_channel anymore.
Specifically, these plugins don't work anymore in 3.12 when sending a message
from an MQTT publisher to an AMQP 0.9.1 consumer.
Two of these plugins are
https://github.com/rabbitmq/rabbitmq-message-timestamp
and
https://github.com/rabbitmq/rabbitmq-routing-node-stamp
This commit moves both plugins into rabbitmq-server.
Therefore, these plugins are deprecated starting in 3.12.
Instead of using these plugins, the user gets the same behaviour by
configuring rabbitmq.conf as follows:
```
incoming_message_interceptors.set_header_timestamp.overwrite = false
incoming_message_interceptors.set_header_routing_node.overwrite = false
```
While both plugins were incompatible to be used together, this commit
allows setting both headers.
We name the top level configuration key `incoming_message_interceptors`
because only incoming messages are intercepted.
Currently, only `set_header_timestamp` and `set_header_routing_node` are
supported. (We might support more in the future.)
Both can set `overwrite` to `false` or `true`.
The meaning of `overwrite` is the same as documented in
https://github.com/rabbitmq/rabbitmq-message-timestamp#always-overwrite-timestamps
i.e. whether headers should be overwritten if they are already present
in the message.
Both `set_header_timestamp` and `set_header_routing_node` behave exactly
to plugins `rabbitmq-message-timestamp` and `rabbitmq-routing-node-stamp`,
respectively.
Upon node boot, the configuration is put into persistent_term to not
cause any performance penalty in the default case where these settings
are disabled.
The channel and MQTT connection process will intercept incoming messages
and - if configured - add the desired AMQP 0.9.1 headers.
For now, this allows using Native MQTT in 3.12 with the old plugins
behaviour.
In the future, once "message containers" are implemented,
we can think about more generic message interceptors where plugins can be
written to modify arbitrary headers or message contents for various protocols.
Likewise, in the future, once MQTT 5.0 is implemented, we can think
about an MQTT connection interceptor which could function similar to a
`rabbit_channel_interceptor` allowing to modify any MQTT packet.
|
| |\ \
| | |
| | | |
Also exclude the .erlang.mk directory in gazelle
|
| |/ / |
|
| |\ \
| | |
| | | |
Exclude nested deps fetched by make from gazelle
|
| | |/ |
|
| |\ \
| |/
|/| |
UnsubscribeResponse in stream protocol doc
|
| |/ |
|
| |\
| |
| | |
Adopt otp 25.2.3
|
| | | |
|
| |\ \
| | |
| | | |
Adopt otp 25.1.2.1
|
| | |/ |
|
| |\ \
| | |
| | | |
Adopt otp 25.0.4
|
| | |/ |
|
| |\ \
| | |
| | | |
Adopt otp 25.3.2
|
| | |/ |
|
| |\ \
| |/
|/| |
Adopt otp
|
| |/ |
|
| |\
| |
| | |
3.11.16 release notes
|
| | | |
|
| |/ |
|
| |\
| |
| | |
bazel run gazelle-update-repos for Ra 2.6
|
| | | |
|
| |\ \
| |/
|/| |
rabbitmq_cli dialyze enhancements
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- eex
- elixir
- ex_unit
- iex
- logger
- mix
So that apps (like rabbitmq_cli) can dialyze against the extra
components
|
| | |
| |
| |
| |
| | |
So that they are no longer reported as unknown in
//deps/rabbitmq_cli:dialyze
|
| |/
|
|
|
| |
This provides an elixir/erlang agnostic way of providing them other
erlang rules
|
