Validation tool error

[mhogeweg]

I ran the validation tool with the attached file.

{7DC05CE3-B658-434C-856D-4D00B1E53BB1}.zip

the following error is displayed for md-iop.a.5: Character Encoding:

System error in the Executable Test Suite. Please contact a system administrator. Error information:
[err:FODC0002] "http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml" (Line 1): Premature end of file. 
 (495/29)

and for md-iop.a.6: Spatial Representation Type:

System error in the Executable Test Suite. Please contact a system administrator. Error information:
[err:FODC0002] "http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml" (Line 1): Premature end of file. 
 (550/29)

perhaps related to http/https of the codelist? when accessing the link in the error directly, the response is from https endpoint.

[MarcoMinghini]

Dear @mhogeweg,
the problem was actually the http/https of the codelist.
This issue is the same as this one already reported. The corresponding solution has been already implemented in the new cloud Staging instance at http://staging-inspire-validator.eu-west-1.elasticbeanstalk.com/etf-webapp.
We checked that the corresponding error has actually disappeared (now you will find a new error, which however is not related to the previous one).

[mhogeweg]

thanks. I can work with the staging environment to complete my work. When will the production environment be updated? and could you post some release notes when that happens?

[MarcoMinghini]

The staging environment is exactly meant as the place where all the latest improvements (both bug fixes and new functionality) will be made available as soon as they are ready. Therefore, you can always use it for your tests.

When a bug fix is positively tested by the reporter, it is scheduled to be also released in the production instance. And yes, we keep track of the changes deployed (both in the staging and production instances) in the changelog file.

I open this issue again, since the change is not yet deployed in production. When it will be, we will change the label from 'solved' into 'deployed in reference validator' and close it.

[JohannaOtt]

FYI: I ran into this again right now on the production instance.