Skip to content
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

revisit how we define/use processIds for these status messages across the repo. #352

Open
BrianWhitneyAI opened this issue Nov 26, 2024 · 1 comment
Open

revisit how we define/use processIds for these status messages across the repo. #352

BrianWhitneyAI opened this issue Nov 26, 2024 · 1 comment

Comments

@BrianWhitneyAI
Copy link
Contributor 

          outside of this PR's scope, but noting that we may want to revisit how we define/use `processIds` for these status messages across the repo since it's currently somewhat ad hoc

Originally posted by @aswallace in #350 (comment)
@SeanLeRoy
Copy link
Contributor

I don't think this is necessarily worth an issue - unlikely we would circle back to this without a motivator like a bug or new feature

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@SeanLeRoy @BrianWhitneyAI