-
Notifications
You must be signed in to change notification settings - Fork 17
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
Report phase crashes near end #124
Comments
Hi, |
Not able to reproduce and provided some suggestions on it through direct email. The executable linux bundle works as I provided feedback on that @SimonFinch63 but if you try the suggestions I had in email and any worked please update this ticket for everyone's benefit. If not, I'll keep this ticket open in case anyone else has come across it. |
I have tested 1.6 on both Windows and Linux, Windows works well, Linux crashes with the same errors as 1.5.9.8. 2024-02-142024-02-14 16:57:05,046 [DEBUG] no evaluation found, ignoring expression: Find online documents for <a href='https://docs.appdynamic 16:57:05,141 [DEBUG] STREAM b'PLTE' 41 768 During handling of the above exception, another exception occurred: Traceback (most recent call last): 2024-02-14 16:57:05,166 [DEBUG] controller.prod.appd-saas.srv.westpac.com.au - Closing connection |
2023-07-28 13:56:32,075 [DEBUG] STREAM b'IDAT' 1109 11146
2023-07-28 13:56:32,090 [ERROR] Traceback (most recent call last):
File "pptx/slide.py", line 259, in getitem
File "src/lxml/etree.pyx", line 1178, in lxml.etree._Element.getitem
IndexError: list index out of range
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "core/Engine.py", line 199, in run
File "core/Engine.py", line 362, in finalize
File "output/presentations/cxPptFsoUseCases.py", line 572, in createCxHamUseCasePpt
File "output/presentations/cxPptFsoUseCases.py", line 609, in generateRemediationSlides
File "pptx/slide.py", line 261, in getitem
IndexError: slide index out of range
I have tried running with DefaultThresholds and with our Custom Thresholds, same result, same error
The text was updated successfully, but these errors were encountered: