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

database tracking all side effects #1415

Open
mmjconolly opened this issue Sep 11, 2023 · 0 comments
Open

database tracking all side effects #1415

mmjconolly opened this issue Sep 11, 2023 · 0 comments

Comments

@mmjconolly
Copy link
Contributor

mmjconolly commented Sep 11, 2023 •
edited
Loading

Currently if a localRunner job, or a prim causes a side effect we don't know about the actions from just looking at wake --last/--failed

Whilst we can't really ever know what the localRunner truly did, with regard to inputs/outputs, we could at least communicate to the user that it ran and what it's env and exit code was
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
1 participant
@mmjconolly