You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched for a similar issue in our bug tracker and didn't find any solutions.
What happened?
When splitting configs, forwarding the rpc.listen field or something like that doesn't work. The error says that the address is not specified, although I assume that the plugin did not start or the config cannot be read.
Hey @Kaspiman 👋
The case is, that RR commands (like ./rr workers) are using your initial configuration. Replace works for the plugins, but not for the RR commands. This is not a bug, but unexpected expected (huh) behavior. I'll put this to the 2024.3 milestone and add support for the replaces in the RR commands as well.
As discused in Discord, this is a problem for me as well. I'm loading different paths/routes in my application depending on domain, which requires separate RR nodes. To simplify config, I use a parent config with this:
No duplicates 🥲.
What happened?
When splitting configs, forwarding the
rpc.listen
field or something like that doesn't work. The error says that the address is not specified, although I assume that the plugin did not start or the config cannot be read.Version (rr --version)
rr version 2024.2.1 (build time: 2024-09-12T16:25:02+0000, go1.23.1), OS: linux, arch: amd64
How to reproduce the issue?
.rr.base.yaml
:.rr.yaml
:then run
rr workers
Relevant log output
The text was updated successfully, but these errors were encountered: