Browser upgrade fails when discourse is configured to use one unicorn worker

Let me redo my response here:

This seems like a bug, especially as the system cuts down to a single unicorn temporarily very shortly afterwards.

The number 2 is hardcoded, as is the number 1 for the reduction.

Edit: looks like this change introduced the inconsistency

Thanks for the new thread.

1 Like