You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OS Used - ALL Information (architecture, linux flavor, etc.)
Pastebin link to error you are encountering
Expected behavior (vs. what you encountered)
A screenshot should always be included in the report if it exists, even if urllib was unable to capture data.
If a screenshot is created for a website (selenium), but EyeWitness failed to gather information about the website (urllib), the screenshot should be included in the report. Currently, certain exceptions on urllib create conditions where the generated report where a website with a properly generated screenshot is reported as having errored and the screenshot is not included in the report.
Any additional information
some code for this condition already exists on the timeout handling in report generation -- where the report screenshot is included if it exists but urllib failed on timeout. New error handling on urllib calls may cause similar conditions on other errors. the report generation should be updated to always show a report if it exists, even if urllib failed for any reason.
The text was updated successfully, but these errors were encountered:
OS Used - ALL Information (architecture, linux flavor, etc.)
Pastebin link to error you are encountering
Expected behavior (vs. what you encountered)
A screenshot should always be included in the report if it exists, even if urllib was unable to capture data.
If a screenshot is created for a website (selenium), but EyeWitness failed to gather information about the website (urllib), the screenshot should be included in the report. Currently, certain exceptions on urllib create conditions where the generated report where a website with a properly generated screenshot is reported as having errored and the screenshot is not included in the report.
Any additional information
some code for this condition already exists on the timeout handling in report generation -- where the report screenshot is included if it exists but urllib failed on timeout. New error handling on urllib calls may cause similar conditions on other errors. the report generation should be updated to always show a report if it exists, even if urllib failed for any reason.
The text was updated successfully, but these errors were encountered: