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

[Examiner] Fixing Errors while saving the form #5545

Merged
merged 1 commit into from
Nov 7, 2019

Conversation

sruthymathew123
Copy link
Contributor

Brief summary of changes

This fixes

Testing instructions (if applicable)

  1. Try to create a new examiner and edit the examiner details by just clicking 'Save' with no data or with just one instrument details filled. It will throw 500 error. Check out to this branch and try testing with the same case and see if the issue is resolved

  2. Add Certification instruments with similar naming (like BMI, BMI_version_2 etc) and try to load the edit examiner page. It will throw 500 error. Check out to this branch and try testing with the same case and see if the issue is resolved

Links to related tickets (GitHub, Redmine, ...)

@sruthymathew123 sruthymathew123 added Category: Bug PR or issue that aims to report or fix a bug 22.0.0 TESTING labels Nov 5, 2019
@johnsaigle
Copy link
Contributor

johnsaigle commented Nov 6, 2019

I tested the first point and it seems to work (i.e. no 500 error generated). 👍

I guess my VM isn't configured properly to be able to test the second point because there are no Certification Instruments enabled. I'm not totally sure how to set this up because there are no examples in the config files and I'm not sure what is compatible with Raisinbread. I opened an issue for this, #5567.

@sruthymathew123
Copy link
Contributor Author

@johnsaigle Thank you for testing the first part. I caught the second issue while testing on my VM with IBIS data. We have instruments with similar naming and it failed as the testname checking with LIKE CONCAT('%', :testName, '%')",

@driusan
Copy link
Collaborator

driusan commented Nov 7, 2019

@nicolasbrossard you probably have certification set up, can you test the second part of this?

@nicolasbrossard
Copy link
Contributor

nicolasbrossard commented Nov 7, 2019

@driusan @sruthymathew123 I tested this on my VM (without Sruthy's fix) and I indeed get the 500 error. Page displays fine after I pull Sruthy's branch.

Sruthy: 1 Bug: 0 .

👍

@driusan driusan merged commit 80a8ba9 into aces:22.0-release Nov 7, 2019
@ridz1208 ridz1208 added this to the 22.0.0 milestone Nov 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Bug PR or issue that aims to report or fix a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants