-
Notifications
You must be signed in to change notification settings - Fork 745
refactor(ec2): pass log level to connect script #6161
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
Merged
Merged
Changes from 5 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
d033ec7
avoid logging token
Hweinstock 42c14ac
use require no log instead
Hweinstock 9762ff9
pass log level down to connect script
Hweinstock 1381dc4
make file location in debug mode only
Hweinstock db445fb
Merge branch 'feature/postreinvent' into ec2/loglevel
Hweinstock b7b36ad
use flag to determine if script should debug
Hweinstock 4e80178
adjust var name
Hweinstock 232d88e
Merge branch 'ec2/loglevel' of github.com:Hweinstock/aws-toolkit-vsco…
Hweinstock ca6046a
make import absolute
Hweinstock 2f8be88
add a check around log level set
Hweinstock File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like getLogger doesn't have e.g.
getLogLevel. otoh, we could make the flag a simple boolean likeLOG_DEBUG:that also would avoid the use of
-lein the bash scriptUh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think
logLevelEnabledworks as intended. I was able to produce this:and I believe its because the internal log level is
debuguntil the user changes it based on the code here:aws-toolkit-vscode/packages/core/src/shared/logger/activation.ts
Lines 43 to 49 in aa332da
I see the comment so I am wondering if there something special about the fact that I am running locally? Otherwise this seems like a bug.
Once I manually set the log level (i.e. trigger that event) this doesn't happen.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think when I added that "HACK" line, I assume that something in vscode would always overwrite the log-level, except when running in debug-mode. That line definitely needs some attention.
Perhaps the easiest fix is to wrap that line in
if (!isRelease() && ...)or whatever