These are hard to debug. The stacktrace is not useful in this case, as the failure is happening somewhere completely else. Hopefully it is locally reproducible so it can be debugged manually to find out the real error.

still happening https://logstash.wikimedia.org/app/kibana#/doc/logstash-*/logstash-syslog-2020.07.06/syslog?id=AXMkPJc1MQ_08tQaR6wG&_g=h@44136fa
where should this go?

In T235579#6284244, @Jpita wrote:

where should this go?

Let's remove it from the sprint. It seems that it is reproducible and only causes log noise, so we can work on this when this area of work becomes our focus.

Thanks for checking it!

In T235579#5578721, @Nikerabbit wrote:

These are hard to debug. The stacktrace is not useful in this case, as the failure is happening somewhere completely else. Hopefully it is locally reproducible so it can be debugged manually to find out the real error.

Unrelated, but - is it planned to remove bluebird and use native Promise instead? Our Node.js version supports this, as well as async functions (which are just syntax sugar for Promise). Either of those would would improve the stack trace I think.

is it planned to remove bluebird and use native Promise instead?

Not currently planned, but I would support migrating away from bluebird when we focus on cxserver maintenance.