-
Notifications
You must be signed in to change notification settings - Fork 104
chore: ntx builder actor deactivation #1705
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Mirko-von-Leipzig
merged 12 commits into
next
from
santiagopittella-ntx-builder-actor-deactivation
Mar 12, 2026
Merged
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
ebd2d85
chore: deactivate idle actors
SantiagoPittella a2a63e5
chore: add tests
SantiagoPittella 2bf3cf5
update docs & add configuration to binary
SantiagoPittella 5019ac1
add changelog entry
SantiagoPittella 02a576a
review: rename sterile to idle
SantiagoPittella 6c19d8d
review: remove coordinator confirmation for actor shutdown
SantiagoPittella 870292b
chore: remove duplicated changelog entries
SantiagoPittella 9b17dcd
chore: remove actor on DbError
SantiagoPittella 6bfd060
docs: add changelog entry
SantiagoPittella 2067200
Merge branch 'next' into santiagopittella-ntx-builder-actor-deactivation
SantiagoPittella 70578d4
Merge branch 'next' into santiagopittella-ntx-builder-actor-deactivation
SantiagoPittella 9a357a6
Merge branch 'next' into santiagopittella-ntx-builder-actor-deactivation
Mirko-von-Leipzig File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works, but I really still think we shouldn't need
ActorShutdownReason. The actor return value can just be aanyhow::Result<()>. You'll also notice thatnextreturns a result, but we never actually return a result.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We use the
ActorShutdownReasonin the coordinator side to determinate if we should re-spawn itUh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes but there is only one reason to respawn it (currently, and for the foreseeable future imo)
An actor currently shuts down (on purpose) if:
Everything else is a crash/error/bug.
We can therefore in theory say that all
Ok(())means check notify and possibly respawn, and allErr(_)means increment crash counter and respawn.I'm okay with merging as is, and we can litigate/discuss after. Basically I want to reduce the number of branches and conditionals because these lead to edge cases and bugs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh ok, I misunderstood before. It should be a simple change. To avoid generating conflicts in this PR #1712 I will address this there since it is related to that PR too