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.

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

CLI: Is default state broken? #647

Closed
josephjclark opened this issue Apr 3, 2024 · 1 comment
Closed

CLI: Is default state broken? #647

josephjclark opened this issue Apr 3, 2024 · 1 comment
Labels
bug Something isn't working wontfix This will not be worked on

Comments

@josephjclark
Copy link
Collaborator

I confidently told hunter that -s tmp/state.json is redundant, as the CLI will look for state in state.json adjacent to the job.js file.

But in her log, that doesn't seem to be working?

image

I ought to investigate this

@josephjclark josephjclark added the bug Something isn't working label Apr 3, 2024
@github-project-automation github-project-automation bot moved this to New Issues in v2 Apr 3, 2024
@josephjclark
Copy link
Collaborator Author

Ah, I remember now!

We actually removed this, because it can be a bit scary if the CLI starts loading random state files without permission.

So this is the correct behaviour

@github-project-automation github-project-automation bot moved this from New Issues to Done in v2 Apr 3, 2024
@josephjclark josephjclark added the wontfix This will not be worked on label Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working wontfix This will not be worked on
Projects
Archived in project
Development

No branches or pull requests

1 participant