Fix ENOENT error during harvesting Conda components#575
Merged
elrayle merged 1 commit intoclearlydefined:masterfrom May 8, 2024
Merged
Conversation
lumaxis
approved these changes
May 8, 2024
Contributor
lumaxis
left a comment
There was a problem hiding this comment.
Thanks! I wonder if we can do anything about either the env setup or the code to make this mechanism more resilient in the future so other contributors don't run into this discrepancy as easily 🤔
Collaborator
|
@lumaxis That refactor sounds like a great idea! |
Collaborator
|
Thanks @qtomlinson for making this happen. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is to fix ENONET exception encountered during testing on dev deployment. It follows the same approach taken in debianFetch.js.