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

Issue a warning if we are falling back to the old shell environment #487

Merged
merged 5 commits into from
Apr 23, 2024

Conversation

bbenne10
Copy link
Contributor

This should resolve #486.

@@ -326,6 +326,7 @@ use_flake() {
# which is probably more useful than nothing.
# Fallback to use that (which means just leaving profile_rc alone!)
_nix_direnv_warning "Evaluating current devShell failed. Falling back to previous environment!"
export NIX_DIRENV_DID_FALLBACK=1
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Who is the consumer of this environment variable?

@bbenne10
Copy link
Contributor Author

bbenne10 commented Apr 20, 2024 via email

@Mic92
Copy link
Member

Mic92 commented Apr 21, 2024

Ok. Do you have a concrete use case for it? If so it would be nice to put in the Readme.

@bbenne10
Copy link
Contributor Author

bbenne10 commented Apr 22, 2024

No - I don't have a concrete use case for this variable, but @amarshall suggested it and it seemed perfectly reasonable to provide an extension point for user consumption here. I have updated the README to note the environment variable. Additionally, I've changed the note about nix-direnv-watch-file (which is no longer accurate - oops!) and added a note about hide_env_diff in (what I believe to be) a more appropriate way than #485.

@Mic92
Copy link
Member

Mic92 commented Apr 23, 2024

@mergify queue

@Mic92 Mic92 merged commit 08ee079 into master Apr 23, 2024
32 checks passed
Copy link
Contributor

mergify bot commented Apr 23, 2024

queue

🛑 The pull request has been removed from the queue default

The pull request can't be updated.

You can take a look at Queue: Embarked in merge queue check runs for more details.

In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment
@mergifyio refresh on the pull request.

@Mic92 Mic92 deleted the GH-486 branch April 23, 2024 12:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fallback to previous devshell upon failure is unclear
2 participants