Skip to content
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

Validator v. 2024.0 fails when choosing "Conformance Class 2c: 'INSPIRE data sets and data set series metadata for IACS'" #1033

Closed
dhdeangelis opened this issue Feb 23, 2024 · 6 comments
Labels
deployed in reference validator Solution deployed in production
Milestone

Comments

@dhdeangelis
Copy link

The latest version of the validator, 2024.0, throws an error when choosing Conformance Class 2c: 'INSPIRE data sets and data set series metadata for IACS.

This error does not happen if IACS conformance class is not chosen. The error happens when running from both a local docker instance or the public instance.

image

@fabiovinci
Copy link
Collaborator

Dear @dhdeangelis,

thank you for the notification, we will fix it asap.

@DanielMartinPerezdeLeon
Copy link
Collaborator

Dear @dhdeangelis,

Thank you for bringing the issue to our attention. After a thorough investigation, we've identified the root cause of the problem.

Rest assured, we've implemented the necessary fix and will promptly upload it to the validator-ui repository. In the meantime, we encourage you to utilize our staging environment to try it and continue with your tests.

Should you have any further questions or concerns, feel free to reach out.

Best regards,

DanielMartinPerezdeLeon added a commit to DanielMartinPerezdeLeon/INSPIRE-Validator-UI that referenced this issue Feb 27, 2024
DanielMartinPerezdeLeon added a commit to DanielMartinPerezdeLeon/INSPIRE-Validator-UI that referenced this issue Feb 27, 2024
@fabiovinci fabiovinci added ready for testing Solution provided to reporter or developed & deployed in staging (or beta), waiting for testing and removed under development labels Mar 4, 2024
@fabiovinci fabiovinci added this to the v2024.0.1 milestone Mar 4, 2024
@dhdeangelis
Copy link
Author

dhdeangelis commented Mar 4, 2024

@fabiovinci thanks, I see this is tagged as ready for testing. Is it ready now or should I wait for a new release?

@DanielMartinPerezdeLeon
Copy link
Collaborator

DanielMartinPerezdeLeon commented Mar 4, 2024

@fabiovinci thanks, I see this is ready for testing now or should I wait for a release?

@dhdeangelis You can test this in the staging-environment while we upload the new release

Regards,

@dhdeangelis
Copy link
Author

I can confirm that the issue is solved in the staging instance. It is possible to test without the error described in the original post.

Thank you @DanielMartinPerezdeLeon and @fabiovinci

image

@fabiovinci fabiovinci added solved Solution developed and accepted, not yet deployed and removed ready for testing Solution provided to reporter or developed & deployed in staging (or beta), waiting for testing labels Mar 4, 2024
@fabiovinci fabiovinci added deployed in reference validator Solution deployed in production and removed solved Solution developed and accepted, not yet deployed labels Mar 6, 2024
@fabiovinci
Copy link
Collaborator

The fix for this issue is now available in the production instance.
For further details, please visit the v2024.0.1 release notes.

@github-project-automation github-project-automation bot moved this to Production: latest release in Validator issues Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deployed in reference validator Solution deployed in production
Projects
Archived in project
Development

No branches or pull requests

4 participants