Simon
Simon
Hi. I'm giving this a look to see what can be done if any.
I did some digging around. To change the the precedence order, i.e absolute > relative, is doable. But, we'd just 'change' the problem, not solve it. I assume the proper...
Sorry, I'll clarify! Yes, to just give `absolute` precedence will be a minor and easy change I can provide, with a warning if both values are configured. I was thinking...
something like this might fix it? ``` ... else: incoming_node = self.nodes[word[0]] matching_string, remaining_prefix, remaining_word = incoming_node.match( word ) if remaining_prefix == "" and not remaining_word == "": #
> @illotum My suggestion would be to ship it in 3.11 for now. Start using it, keep an eye on these instances and then, if you see the benefits and...
@michaelklishin just a draft placeholder
Realized that rabbit_global_counters runs before the registration of custom queue types....
> I think the general approach is pretty much what we designed. I am concerned that there are functions called in `eval_members` that are potentially blocking such as `rabbit_nodes:list_running()` and...
@kjnilsson Perhaps the eval_member callback could provide an optional 'reply fun', and the implementer could use that fun to report the result to the instead of directly responding, i.e spawn...
Perhaps enough with running `lists:all(fun(#{servers := S}) -> erlang:map_size(S) =:= 0 end, [ra:overview(X) || X