-
Notifications
You must be signed in to change notification settings - Fork 7
fix : added proper error handling to failure logs #42
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
base: main
Are you sure you want to change the base?
Conversation
@@ -64,16 +73,17 @@ export async function retrieveSessionFailures( | |||
}, | |||
}); | |||
|
|||
await assertOkResponse(response, "session logs"); | |||
const validationResult = validateLogResponse(response, "session logs"); |
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.
const validationResult = validateLogResponse(response, "session logs"); | |
const validationError = validateLogResponse(response, "session logs"); |
do this in all places
src/tools/getFailureLogs.ts
Outdated
logs.length > 0 | ||
? `Network Failures (${logs.length} found):\n${JSON.stringify(logs, null, 2)}` | ||
: "No network failures found", | ||
response.message || |
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.
directly return the result of these conditionals in the response (for other methods as well)
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.
Can you explain this change a bit ?
Fixed an issue where an error in fetching one type of logs was disrupting the retrieval of all log types.