This change does not affect tests, and the other workflows (esp. the one
that builds OCIs) will check if something breaks in packaging.
Would you disagree with this @pjk25?
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
We need these to debug various rabbitmq-related issues. Ephemeral debug
containers are not enabled on GKE Autopilot (not sure if GKE enables
this alpha feature at all), so we are doing this instead.
error: ephemeral containers are disabled for this cluster (error from server: "the server could not find the requested resource").
Backport to v3.9.x & v3.8.x if build passes
Pair @Gsantomaggio
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
When we fail to parse name of cipher suite from PROXY protocol
just say that no ssl is used, instead of trying to fill that
with data from connection between proxy and our server.
This reverts commit c74e920588.
The latest Elixir version is 1.12.2 🤦
Next time, read & follow the comments above 🚶
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
We should have a GitHub Action for this (dependabot doesn't support it),
but this is still the simplest thing for now. It takes just a few
minutes, happens every few months, so we would be saving at most 1h per
year, which doesn't seem worth the effort.
cc @pjk25
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
Rather than running these all the time, especially tests, we only want
to run them when files in specific paths change. cc @pjk25
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
Remove hard line breaks, otherwise the text of a new PR will start with
"weird looking" formatting.
cc @michaelklishin
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
I've missed adding notes to the release part of
https://github.com/rabbitmq/rabbitmq-server/pull/3340
I am going to add a new item to the PULL_REQUEST_TEMPLATE.md checklist
so that we get reminded about it next time.
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
With this change and if the RabbitMQ node is running on Unix and accepts
input, the titlebar of an Xterm-compatible terminal emulator will show a
few details about the running node. Specifically, it will indicate the
name of the node and the version of RabbitMQ.
A user could already enable single-line logging (the `single_line`
option of `logger_formatter` or RabbitMQ internal formatters) from the
configuration file. For example:
log.console.formatter.single_line = on
With this patch, the option can be enabled from the `$RABBITMQ_LOG`
environment variable as well:
make run-broker RABBITMQ_LOG=+single_line
Rather than sleeping for 6 seconds, we want to check that replica
recovered multiple times within 30 seconds, and either eventually
succeed, or fail if this does not recover within 30 seconds, the default
await_condition time interval.
Pair: @kjnilsson
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
Also increased the tick timeout to avoid checking for new rabbit nodes
to auto add too often.
Also increased sleep times for nodedowns to retry less often.
Philip Kuryloski
Gerhard Lazu
Michal Kuratczyk
Michael Klishin
Michael Klishin
Paweł Chmielowski
pjk25
Arnaud Cogoluègnes
Federico Caprari
Jean-Sébastien Pédron
Gerhard Lazu
Karl Nilsson