noticed an issue where the finally call on the piscina instance would execute before the final two messages from the worker (final progress and complete) would be received by the port. for some reason, moving the post message calls in the worker to before we close the db instances solved the problem, although I'm a little puzzled as to why (does one of those calls send some kind of signal that piscina listens for?)
noticed an issue where the
finallycall on the piscina instance would execute before the final two messages from the worker (final progress and complete) would be received by the port. for some reason, moving the post message calls in the worker to before we close the db instances solved the problem, although I'm a little puzzled as to why (does one of those calls send some kind of signal that piscina listens for?)