Skip to content

Feature: Signals print if triggered vs. not during runs #4118

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.

Sign up for GitHub

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

Jump to bottom
Open
sungchun12 opened this issue Apr 10, 2025 · 0 comments
Open

Feature: Signals print if triggered vs. not during runs #4118

sungchun12 opened this issue Apr 10, 2025 · 0 comments
Labels
Improvement Improves existing functionality

Comments

@sungchun12
Copy link
Contributor

sungchun12 commented Apr 10, 2025 •
edited
Loading

In the CLI output, signals work by matter of seeing the model run or not. For debugging and development, it should have a default option to print a message that it triggered and which model(s) it's triggering.

It follows the spirit of #4113
@sungchun12 sungchun12 added the Improvement Improves existing functionality label Apr 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Improvement Improves existing functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sungchun12