Skip to content

add -signals flag and make it off by default#6671

Open
mccanne wants to merge 3 commits intomainfrom
signals-flag
Open

add -signals flag and make it off by default#6671
mccanne wants to merge 3 commits intomainfrom
signals-flag

Conversation

@mccanne
Copy link
Collaborator

@mccanne mccanne commented Feb 27, 2026

No description provided.

philrz
philrz previously approved these changes Feb 27, 2026
* `-signals` catch `SIGINT`, `SIGTERM`, and `SIGPIPE` and exit gracefully
* `-version` print version and exit

The `-signals` option is off by default except for `super db serve`, which always enables
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The `-signals` option is off by default except for `super db serve`, which always enables
The `-signals` option is off by default except for [super db serve](db.md#super-db-serve), which always enables


The `-signals` option is off by default except for `super db serve`, which always enables
the catching of `SIGINT` and `SIGTERM` (but not `SIGPIPE`). When `-signals` is enabled,
the `super` command is interrupted but continues to a natural stopping point (e.g., flushing partial output files, removing spill file from temp). In the current implementation,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
the `super` command is interrupted but continues to a natural stopping point (e.g., flushing partial output files, removing spill file from temp). In the current implementation,
the `super` command is interrupted but continues to a natural stopping point (e.g., flushing partial output files and removing spill files from temporary storage). In the current implementation,

the catching of `SIGINT` and `SIGTERM` (but not `SIGPIPE`). When `-signals` is enabled,
the `super` command is interrupted but continues to a natural stopping point (e.g., flushing partial output files, removing spill file from temp). In the current implementation,
this can be unpredictably long so the default is to exit immediately,
potentially leaving behind corrupt outputs etc.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
potentially leaving behind corrupt outputs etc.
potentially leaving behind corrupt outputs, etc.

@philrz philrz dismissed their stale review February 27, 2026 17:02

Oops! I was clicking Approve based on the docs changes, but clearly someone else needs to approve the code changes.

@philrz philrz requested a review from a team February 27, 2026 19:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants