fix: multiprocess broke local development #430
Merged
Conversation
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
justinwlin
approved these changes
Jun 15, 2025
justinwlin
added a commit
that referenced
this pull request
Aug 4, 2025
This reverts commit e58d519.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #428 #427
Since moving Heartbeat to a multiprocess execution, persisting JobsProgress had become tricky. Although it fixed the Production issue of blocked pings when a CPU is blocked for a long time, the previous release broke local development. This PR shifts JobsProgress to persist at a file level using a pickled
.runpod_jobs.pklstore. These changes are properly tested with unit and integration tests.An additional simulator is also introduced for debugging. See commit 1e06e5cca31529563e1e4e0dff9182fc0d7aa3bf