-
Notifications
You must be signed in to change notification settings - Fork 23
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
Web validator - error at session spin up with crs definitions results in failures in tests #1127
Comments
Dear @joey-geoloog, Could you please provide us with a sample dataset so we can reproduce the errors? Thanks |
Dear @fabiovinci |
@fabiovinci Interestingly, running the exact same data through the validator today doesn't return the same error. So it appears to be something related to the instance that validator was running on, or the validator has been upgraded/patched in the meantime? |
Dear @joey-geoloog, I'm glad to hear that you were able to validate it. The error was likely due to a temporary overload; maintenance work was performed days later (#1130). I will close the issue, please reopen it if the error persists. |
Dear team, Thanks in advance!
web validator - production
I see the following error multiple times in the logfiles before I even get to see the report, progress is extremely slow.
23.10.2024 12:36:00 - "[err:XQST0059] Could not instantiate de.interactive_instruments.etf.bsxm.GmlGeoX: org.deegree.cs.exceptions.CRSConfigurationException: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF; was expecting a close tag for element <crs:CRSDefinitions>
 at [r..."
Links: Logfile | Testobject | Name: Test run on 14:34 - 23.10.2024 with test suite Annex III - Environmental monitoring Facilities (EF)
This results in an error in the test results despite the geometry being declared properly.
Assertion URI: https://yzyiqfakm4.execute-api.eu-west-1.amazonaws.com/validator/v2/TestRuns/EIDa59f552c-4ea0-4040-be27-0ade03876b51.html?lang=en#EIDa12eed3a-ba1b-4345-aa1e-9b908f068006
Logfile plaintext: EIDa59f552c-4ea0-4040-be27-0ade03876b51.log
The text was updated successfully, but these errors were encountered: