-
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
Transport Networks - Connection to test runner lost #267
Comments
Dear @danicgc We have been aware of this problem with your dataset. There is a problem validating the Geometry nodes of the GML, causing an exception on the validator that has led to several crashes on the production instances recently. A similar issue was fixed recently. We are looking into what could be wrong with your file, and will get back to you with a response In the meantime, we would suggest to stop the validation of this dataset, given that it causes the service to go down. Sorry for the inconveniences. |
Dear @danicgc We have located the issue. This was indeed related to the mentioned issue on my previous comment. The node We are developing a fix for this and will be uploaded in the staging instance as soon as it is ready. |
Dear @danicgc |
Dear @danicgc, the new release of the ETF software is now available and we are testing its integration into the INSPIRE Validator. Could you please provide the GML file again since it is not available now? |
Hi @fabiovinci, |
Hi,
I'm trying to validate a Transport Networks GML (< 5 MB) and it starts running but, some minutes after the test case 'Geometry' starts, the following message is thrown:
"Connection to test runner lost. The test could have been canceled without generating a report or the internet connection to the web application has been lost!"
It seems like a timeout while testing geometry.
The GML file is https://ide.cat/inspire-atom/transport-networks/transport-networks-inspire.gml
The test suites I try are:
I'm using Firefox 68.6.0esr (64 bits). It's not the first time I use the validator, but for Transport Networks.
The text was updated successfully, but these errors were encountered: