Nicolai
Nicolai
> Hello, > > > > > it's the current hour, as in, the 23 hours at which I ran the command (which I did not notice because I am...
The delay here is absolutely ridiculous.
If anyone wants to work around this; I created my own image with the necessary tools and I just use that. It wasn't super-easy, but once you iron out the...
Update. This is not actually a problem. The credentials in the check are not being used, they only determine the behavior of the sqs configuration parameters. I have made a...
Second update: It actually is a problem, but for different reasons than originally stated, because of this code in the current version of the SQS plugin: https://github.com/roadrunner-server/sqs/blob/e32b815a0edf4d20069e6234dd78ea86ee291c2f/sqsjobs/driver.go#L505-L521 As it doesn't...
Yes. This can be ignored.
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,...
You could consider just not requiring the config object at all since it doesn't do anything. Of course, this means if-else'ing where you load drivers to check if the type...
Just FYI it looks like you're dumping an app secret. Not sure if important, just in case you missed it.
What is the point in waiting at all? If no workers are available, I would argue you should create a new one **immediately** and only use the `allocate_timeout` logic once...