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

Don't force $DAGSTER_HOME to be set #125

Merged
merged 1 commit into from
Jun 26, 2024
Merged

Conversation

penelopeysm
Copy link
Member

The code inside the try block is only relevant if info is persisted from a previous run, which in turn requires $DAGSTER_HOME to have been set, so if it's not set we can just skip over it.

The code inside the try block is only relevant if info is persisted from
a previous run, which in turn requires $DAGSTER_HOME to have been set,
so if it's not set we can just skip over it.
@penelopeysm
Copy link
Member Author

This is tiny, and I'm pretty sure this is uncontroversial so will merge

@penelopeysm penelopeysm merged commit 51af727 into main Jun 26, 2024
1 of 2 checks passed
@penelopeysm penelopeysm deleted the skip-no-dagster-home-error branch June 26, 2024 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done:
Development

Successfully merging this pull request may close these issues.

1 participant