-
Notifications
You must be signed in to change notification settings - Fork 887
feat: Add workspace agent lifecycle state reporting #5785
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
mafredri
merged 24 commits into
main
from
mafredri/feat-add-workspace-agent-ready-status
Jan 24, 2023
Merged
Changes from 1 commit
Commits
Show all changes
24 commits
Select commit
Hold shift + click to select a range
40e9c87
feat: Add new migrations
mafredri 5abf555
Generate database changes
mafredri a84e467
feat: Add agent state reporting
mafredri 8119e71
Generate docs
mafredri 515e342
WIP
mafredri 1e53635
Rename state -> lifecycle state
mafredri 534f954
Add tests, improve lifecycle reporting
mafredri 90192e5
Fix lint
mafredri aaf19bc
test: Update terraform tests for provider v0.6.7
mafredri bd1a87f
test(site): Update agent mocks
mafredri df9944e
Add new columns to workspace agent table
mafredri 60f414f
Fix plumbing
mafredri 087070e
Run OverrideVSCodeConfigs even on error
mafredri c6928e9
Use consistent Seconds terminology
mafredri c132d4e
Fix s/continue/break/
mafredri 903e850
Fix git auth override order
mafredri 034a850
Fix nit
mafredri f76247f
Publish workspace update
mafredri 2ccdcac
Hide report lifecycle endpoint from apidocs
mafredri 830f9f1
Set all existing agents to ready
mafredri 2b1569f
Add debug logging to lifecycle states
mafredri 71706e0
Add note about error during vscode git auth override
mafredri 21a9d28
Fix typo in tests
mafredri da67c73
Merge branch 'main' into mafredri/feat-add-workspace-agent-ready-status
mafredri 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
Fix git auth override order
- Loading branch information
commit 903e850c02b94b6e01d98112bf281751a3d5b5a8
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
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.
nit: should the agent quit here?
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.
We probably shouldn't, this could fail for a multitude of reasons, like a user setting
chmod 0000
on a folder. The worst that can happen is a degraded user experience (git auth in vscode not working). Ultimately we might want to:start_error
because this failedThere 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.
Yes, that's the situation I was considering. What can user do in this case? Restart the workspace until it works?
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.
If the change was done before, failure here doesn't really matter either (btw). Restarting will most likely not help, unless it's a problem mounting FS or similar. They'll most likely need to resolve the issue in the workspace, then restart, or create a new one.
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.
For now, I've only added a note. I'll revisit this behavior when I add startup log streaming 👍🏻.