Omair Vaiyani

Okay got you, I had to re-read that a few times - what you're saying is that its all-or-none. If an instance, in our case, the Producer server tries to...

@stansv So I've tried this theory but I doesn't appear to hold true. I made a simplified version of our Producer server and tried the following Server 1: ```typescript const...

That's interesting, fetching a job where a processor wasn't issue resulted in an error?

For anyone that stumbles upon this issue - neither Bull 3, nor the upcoming Bull 4 currently natively support a test/in-memory environment for local development, and no mock clients (ioredis-mock,...

We experience this issue multiple times a day unfortunately, its probably added hours of delays to our CI pipeline daily

We moved to Self-Hosted Runners to reduce our build times with custom AMIs and bigger instances, but our efforts are being hindered by extremely slow cache download and post-job upload...

If anyone stumbles upon this issue, I boiled the issue to package.json -> "react-native":"...tz" My boilerplate (ignite) was using a direct .tz link for "react-native", rather than saying "v0.54.0" (or...

@pushplay that's a fair point, I think deleting all account data makes more sense too - we didn't have a use-case for it, since we only use the default account

@Faithfinder Maybe I'm missing the crux here. Whilst Rush doesn't have a central package.json file or equivalent, it does have mono-repo level configuration that can alter the behaviour of commands...

@flovilmart really great stuff here! Worked like a charm! Could I ask, where's the best place to set the beforeAll, afterAl, beforeEach hooks in order to re-use them across our...