-
Notifications
You must be signed in to change notification settings - Fork 338
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
devEnv: Fix Dev Env timeout + logs #4980
Merged
Merged
Conversation
This file contains 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
justinmk3
reviewed
May 13, 2024
justinmk3
reviewed
May 13, 2024
nkomonen-amazon
force-pushed
the
devEnvLogs
branch
from
May 13, 2024 22:30
64d1cab
to
a303167
Compare
nkomonen-amazon
commented
May 13, 2024
@@ -714,47 +712,6 @@ const Panel = VueWebview.compilePanel(AuthWebview) | |||
let activePanel: InstanceType<typeof Panel> | undefined | |||
let subscriptions: vscode.Disposable[] | undefined | |||
|
|||
let showManageConnections: RegisteredCommand<any> | undefined |
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.
Moved this code to login/commands.ts
due to circular dependency issues
nkomonen-amazon
force-pushed
the
devEnvLogs
branch
5 times, most recently
from
May 14, 2024 20:55
88ab7b5
to
cb68c51
Compare
@justinmk3 could you give this a final look when you have time |
justinmk3
reviewed
May 14, 2024
justinmk3
reviewed
May 14, 2024
justinmk3
reviewed
May 14, 2024
justinmk3
reviewed
May 14, 2024
justinmk3
reviewed
May 14, 2024
We want more logs to help determine if the dev env heartbeat is working as expected Signed-off-by: Nikolas Komonen <nkomonen@amazon.com>
The command that shows the login vue was having circular dependency issues. This moves that logic in to its own file to fix this. Signed-off-by: Nikolas Komonen <nkomonen@amazon.com>
Problem: We only tried to start the activity heartbeat on extension startup. So if that failed due to something like an invalid connection, the heartbeat mechanism would not start Solution: Try and start the heartbeat mechanism when the CC connection changes as well. But if it is already running then we just skip it. Signed-off-by: Nikolas Komonen <nkomonen@amazon.com>
nkomonen-amazon
force-pushed
the
devEnvLogs
branch
from
May 15, 2024 18:50
cb68c51
to
502aabc
Compare
justinmk3
approved these changes
May 16, 2024
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.
Problem:
We only tried to start the activity heartbeat on extension startup. So if
that failed due to something like an invalid connection, the heartbeat mechanism
would not start
Solution:
But if it is already running then we just skip it.
codecatalyst: DevEnvActivity: heartbeat sent at ...
in the logs, which indicates we called the Dev Env/activity
apiLicense
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.