pando85
> Please review your change, `CI / test-go` is failing for it. Do you think it is related with my change? I ran it in local and I have the...
I just rebase main again to see if that fixes the problem.
I found the error. I added the test in the same place as #11739 but that was not checking the [correct parser](https://github.com/kubernetes/ingress-nginx/blob/5b142ed7c44327a949037833531b7cf11057a1ad/internal/ingress/annotations/authreq/main.go#L60). I didn't find any test for `URLWithNginxVariableRegex` but...
> Adding a test is not about proving your change works, it's about ensuring it keeps working with future changes. So I'd ask you to add a test. Oh yes,...
Thanks for your very explanatory answer. Now I understand better the complexity and the caveats that the current crate has. I can offer myself if I can solve small things...
Linked to #29
To be honest, I tried to make something work and the implementation was a bit chaotic. I'm new to Zig and didn't want to touch the library itself, just the...
> Without seeing what was in the RUV it's hard to determine what the fault was. Normally the error tells you about what happened and if a node is advanced/lagged...
> So this is telling you that there is a data issue in the incoming data. So on the source server, you need to investigate that to determine why there...
Let's try to focus on the problem again from scratch: - Run a cluster with 2 replicas in active-active mode and use both of them. - Do regular online backups...