Manuel Sanchez Pinar

Hi, I don't see anything relevant with debug mode at level 9, what I see is that the debug log for that transaction ends, not sure if abruptly when the...

I've now skipped the proxy (CDN) that imposes a 2 minute timeout and went directly to the server which runs Nginx + Modsec. The behaviour is the same, but the...

Yes, the nginx worker thread that catches the request gets stuck at 100% CPU usage. I'm attaching the output of `strace strace -rT -y -p 1646 -s 1000 -v -f`...

Hi airween, Thank you, but I'm still unable to reproduce it using cURL, even if I send the parts separately using `--form` like you, the whole rule `941140` goes like...

Hey! I've been testing using HTTPUser and I get the same result, also it's not only the chart, the statistics are also wrong, which is also visible when running the...

Sure, I'll share some logs tomorrow. I'll also review the logs and documentation tomorrow. In the meantime, I have a couple of questions: 1. For the timeouts, can I set...

Hi! I've been trying to reproduce it with 1 or 2 servers without success. It only happens when I increase significantly the number of worker servers and the overall RPS...

AFAIK you can use: `zefhemel/silverbullet:edge` (https://community.silverbullet.md/t/living-on-the-edge-builds/27)

I enabled DEBUG log level and "reproduced" it again, but I don't see anything wrong in the logs. I also tried to reproduce it without success locally with a dummy...

Ok, I think I found out what was happening and it's not locust fault. I was checking how the stats are computed: https://github.com/locustio/locust/blob/58515c41e2a07d3aa55772c5cb2b88bbbdf75057/locust/stats.py#L313-L314 And messing up with this locust file...