Worker: fix an issue with batch logging#1353
Merged
josephjclark merged 18 commits intorelease/nextfrom Apr 10, 2026
Merged
Conversation
Collaborator
Author
|
claude may have found a gap which can cause problems - but that fix doesn't help the actual problem |
b75de8c to
9b223c2
Compare
I think this this fixes the actual issue - I just want more good focused tests now
Collaborator
Author
|
I'll fix the build and typings in the morning 😫 |
josephjclark
added a commit
that referenced
this pull request
Apr 10, 2026
* update the worker to node 24 (#1357) * update the worker to node 24 * update docker docs * changeset * Worker: fix an issue with batch logging (#1353) * set min-release-age * versions * debugging flaky test * fix an issue where the batch is never clear * fix a timing issue when sending batch events Big help from claude * logging * add a bunch of more controlled unit tests * test on interrupt * update and fix tests I think this this fixes the actual issue - I just want more good focused tests now * tidy logging * more tests * changeset * types * remove only * run tests in serial * worker: tweak event processor and be sure to reset timeout on batch * remove comment * remove more comments * feat: update usage of getActiveProject to getCheckedOutProject (#1360) * feat: update getActiveProject to getCheckedOutProject * feat: back to active project * chore: rename getActiveProject to getTrackedProject * feat: deploy should use getTrackedProject * chore: getCheckedout return undefined like getActiveprojects * fix: types * feat: update removed & renamed workflows on checkout (#1358) * tests: remove unwanted fields * feat: use currentProject * tests: remove fields * versions --------- Co-authored-by: Farhan Y. <yahyafarhan48@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Short Description
Fixes #1350
See issue
Implementation Details
Ok so I don't know the exact case that's causing intermittend fails - but what I've done is manually re-write the tests for the event processor in a much more unit testy way. This divorces the event processor from the runtime and lets me have much more control over tests, so I can recreate particular scenarios more reliably.
The more integration style tests, involving the engine, are still useful - so they're in.
AI Usage
Please disclose whether you've used AI anywhere in this PR (it's cool, we just
want to know!):
You can read more details in our
Responsible AI Policy