-
Notifications
You must be signed in to change notification settings - Fork 32
[benchmarker] Add virtual user cleanup #1704
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
Open
BenjaminPelletier
wants to merge
6
commits into
interuss:main
Choose a base branch
from
BenjaminPelletier:benchmarker-cleanup
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
793fdfe
Add virtual user cleanup
BenjaminPelletier 0685ec3
Fix ID type confusion
BenjaminPelletier ba28748
Merge branch 'main' into benchmarker-cleanup
BenjaminPelletier cede880
Merge remote-tracking branch 'interuss/main' into benchmarker-cleanup
BenjaminPelletier 5c9ed4e
Improve cleanup log message
BenjaminPelletier 8b0cdc6
Merge branch 'main' into benchmarker-cleanup
BenjaminPelletier 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
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
26 changes: 26 additions & 0 deletions
26
schemas/monitoring/benchmarker/reports/report/CleanupReport.json
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| { | ||
| "$id": "https://github.com/interuss/monitoring/blob/main/schemas/monitoring/benchmarker/reports/report/CleanupReport.json", | ||
| "$schema": "https://json-schema.org/draft/2020-12/schema", | ||
| "description": "monitoring.benchmarker.reports.report.CleanupReport, as defined in monitoring/benchmarker/reports/report.py", | ||
| "properties": { | ||
| "$ref": { | ||
| "description": "Path to content that replaces the $ref", | ||
| "type": "string" | ||
| }, | ||
| "end_time": { | ||
| "description": "Time cleanup ended.", | ||
| "format": "date-time", | ||
| "type": "string" | ||
| }, | ||
| "start_time": { | ||
| "description": "Time cleanup started.", | ||
| "format": "date-time", | ||
| "type": "string" | ||
| } | ||
| }, | ||
| "required": [ | ||
| "end_time", | ||
| "start_time" | ||
| ], | ||
| "type": "object" | ||
| } |
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.
Nit/question: one cleanup generating and error will prevent others ones to cleanup, is that on purpose?
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.
Yes, I think generally unhandled exceptions anywhere in a program should be raised quickly and loudly. And exceptions should only be handled when we're confident normal program execution can continue in a correct and consistent manner despite the exception. If we don't know what exception happened in cleanup, I don't think we could know we can continue in a correct and consistent manner. A QueryError is caught and handled in the SCDHandler cleanup so that shouldn't be a factor.