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

Duplicate key value errors thrown for Inferno test 5 for US Core 4.0.0 for multiple resources #567

Open
aljahnke-gwh opened this issue Sep 24, 2024 · 3 comments
Labels
bug This is a bug in Inferno

Comments

@aljahnke-gwh
Copy link

As of earlier today (9/24/2024), Inferno v6.0.2 for US Core 4.0.0 for test 5 is throwing the following error for multiple resources:

Error: PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "validator_sessions_validator_session_id_index" DETAIL: Key (validator_session_id)=(sessionId) already exists.
/usr/local/bundle/gems/sequel-5.42.0/lib/sequel/adapters/postgres.rb:156:in `exec'

This error is localized in the "MustSupport references with resources are valid" sub-test for each of the resources. Screenshot attached.

The manifestation of this error is strange in that during an earlier execution of Inferno test 5 today, there was only 1 resource that manifested this error, but during a later execution of Inferno test 5 there were 20+ resources that manifest this error.

infernoDuplicateKeyValue_09242024

@Jammjammjamm Jammjammjamm added the bug This is a bug in Inferno label Sep 24, 2024
@Jammjammjamm
Copy link
Contributor

Thank you for reporting this. We are investigating and will provide an update once we identify the source of the issue.

@arscan
Copy link
Contributor

arscan commented Sep 25, 2024

Hi @aljahnke-gwh -- we believe we have identified the issue and just pushed out a patch to inferno.healthit.gov that fixes the problem. This appears to have affected users of inferno.healthit.gov, but not those that download and run the (g)(10) Test Kit locally.

When you have a chance, could you try it out again and let us know if the problem has been resolved from your perspective?

Thanks again for the report!

@aljahnke-gwh
Copy link
Author

Hi @arscan This issue is now resolved. Many thanks for your quick response. ~Regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This is a bug in Inferno
Projects
None yet
Development

No branches or pull requests

3 participants