-
Notifications
You must be signed in to change notification settings - Fork 230
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
Darktrace timeout exception handled #1210
Darktrace timeout exception handled #1210
Conversation
Darktrace timeout exception handled opencybersecurityalliance#1205
Codecov ReportBase: 84.66% // Head: 84.67% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## develop #1210 +/- ##
===========================================
+ Coverage 84.66% 84.67% +0.01%
===========================================
Files 557 557
Lines 41435 41467 +32
===========================================
+ Hits 35080 35112 +32
Misses 6355 6355
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
I tested this out with the execute command. first with a smaller pattern:
As expected I got the following error handling:
However I ran a much larger pattern:
And I got an authentication error:
I double checked and am using the same auth credentials but I'm wondering if this is still a problem with the API timing out. It's misleading in this case since it's not an auth problem but should still be the same timeout issue this PR addresses. |
Darktrace bad request exception handled
@delliott90 |
Darktrace timeout exception handled #1205.