-
Notifications
You must be signed in to change notification settings - Fork 254
INTEGRATION [PR#6121 > development/9.2] š use SUR date instead of the infostore one to have an update LastMod⦠#6134
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 all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
d9a5aed
š use SUR date instead of the infostore one to have an update LastModā¦
DarkIsDude 4a70cf7
š call UtilizationService on HEAD and LIST veeam routes
DarkIsDude 225cf9c
ā»ļø extract fetchCapacityMetrics helper to veeam utils
DarkIsDude b779f1f
ā
add unit tests for fetchCapacityMetrics helper
DarkIsDude 63a33eb
ā»ļø factorise logic in get and head lib/route/veeam
DarkIsDude 19a1ee8
ā»ļø migrate to async/await style
DarkIsDude 9524559
ā
migrate tests to async/await
DarkIsDude 6f9012b
ā»ļø prefer promisify over manual new Promise
DarkIsDude 78fd519
ā»ļø remove useless argument to follow caller
DarkIsDude 3f4a308
ā»ļø use pipeline instead of manual stream
DarkIsDude 7554628
ā»ļø factorise XML build at the same place
DarkIsDude dbedc1f
š Release 9.1.14
DarkIsDude c09dc78
Merge remote-tracking branch 'origin/bugfix/CLDSRV-878/use-sur-date' ā¦
DarkIsDude 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.
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.
getVeeamFile, headVeeamFile, and listVeeamFiles are now async, but the caller in routeVeeam.js:167 (return callback(request, response, bucketMd, log)) does not handle the returned promise. If an unexpected error escapes the try/catch blocks (e.g. a TypeError), it becomes an unhandled promise rejection, which crashes the process in modern Node.js.
Consider adding a .catch() at the call site in routeVeeam.js, or wrapping the invocation. The handlers themselves look solid ā the risk is at the call site in routeVeeam.js which is not updated in this PR.
ā Claude Code