@JustSteveKing @spatie_be Thanks for checking in! We're all doing ok. There are only 11 of us at Spatie and sometimes we're all just busy with life and its ups and downs. Of course we're also cooking on some things. There's a newsletter about that planned for tomorrow!

@JanPantel @Wago_io Thanks! I mentioned this a couple other replies, but the job is basically a query exporting data to a single, large JSON file. I wish I could split it up into more smaller jobs, but it's not gonna be the easiest solution

@moisis_h It's a query exporting data to a single JSON file. I'm looking into chunked writes to that file, but I'd prefer to figure out why it's timing out in the first place

@georgeboot The job I'm working on is a large JSON export (single file), so a little annoying to split it into smaller jobs. I hadn't considered the deployment issue yet either. Currently, the graceful shutdown timeout is 60 seconds, which will also be a problem 🫠

@josepostiga @getsentry This is likely the most straightforward way to get to the bottom of this issue. Bugsnag isn't reporting OOM exceptions, but I am currently logging PHP memory usage at each step of the job. 😅

@CodyPChristian The job I'm debugging is pretty much a single query writing to a large JSON file. I'm looking into chunked writes tho.

@devgummibeer @tvbeek @driesvints I should've mentioned that this job is pretty much a single query exporting to a large JSON file. I'm currently looking into writing JSON chunks over multiple jobs. I just wish it would be easier to figure out what limit I'm hitting

@ClaudioDekker thanks, I've already split it into chained jobs as much as possible. The next step would be writing a single JSON file in chunks across multiple jobs 😅

@gonedark @driesvints Thanks, this job is pretty much just exporting data to a single large JSON file. It's stored on a network disk, so it might as well be file I/O issues. I just wish there was a better way to debug it.

@incon @thinkverse @_CPotter @spatie_be Use the numbers on their corresponding words ;)

@_CPotter @JustSteveKing @spatie_be We made it case insensitive now since keyboards are usually not lowercase anyway 😅

RT @JustSteveKing: Loving this fun challenge from @spatie_be for black Friday - I've managed to nail day 1 - let's see what happens tomorro…

@_CPotter @JustSteveKing @spatie_be feel free to PM us your answer and we'll let you know how far off you are 🕵️

@oli_laban @spatie_be You can find your contact on ;)

@chaihoung @spatie_be yes, soon!

RT @spatie_be: S.P.A.T.I.E. invites would-be agents to their first briefing. Find your objective on Monday 25th at 9:00 CET at https://t.co…

I'll share more thoughts once I've properly spent some time with it. If you're curious yourself: Feel free to DM if you want to know any specifics that marketing copy won't tell you. #benqlighting #screenbar #screenbarhalo