Andrew Schmadel
Andrew Schmadel
@leibale Try again with the `timeout` and `connectTimeout` settings as described in the original issue. I have a suspicion that's part of the condition necessary to trigger this bug...
> If you use a lightweight init system like dumb-init, you can use npm start and still have the init system relay SIGTERM signals sent to your container to npm...
Agree, and I'd be willing to add hooks into [grunt-sass](https://github.com/sindresorhus/grunt-sass) once this is done.
Sorry for the very late update, but this indeed works if I wrap `testName` in a template literal (ie. `${testName}`)
I'll likely publish a fork if this is indeed a non-goal of `sqs-consumer` – the ability to buffer messages and process more than 10 at a time is unfortunately rather...
https://github.com/dvershinin/gixy appears to be an actively-maintained fork
> it'll get complicated when v21.x goes out next month or when v20.x goes LTS Is there any precedent for slightly pushing those timelines back to get this fix in?...
Also worth noting that Sequelize doesn't correctly handle `GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY` primary keys, as methods like `bulkCreate` will try to insert `DEFAULT` into that field (which...
I've been running this on my fork for a few days, and it seems to work!