Added debug log for install script output#8
Merged
Conversation
c50da09 to
bf1b4c7
Compare
bf1b4c7 to
c72e739
Compare
nsweeting
approved these changes
Jan 15, 2025
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.
I ran into issues with installing vector and in order to debug it I needed to see the output of the install script. This will by default print the output of the vector install script for help with debugging.
One idea is to check first for
MIX_DEBUGenvironment variable and only log if MIX_DEBUG=true | 1I tested this locally by running on jetstream and updating the vector install file in the deps folder
Example of error state:
Example of a successful install:
mix deps.compile vector_agent --force ==> vector_agent Compiling 8 files (.ex) 06:35:32.243 [debug] Vector binary downloading... 06:35:37.269 [debug] Vector 0.44.0 installed. Generated vector_agent app