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.

Sign up for GitHub

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

Jump to bottom

[instruments] Error on saving LINST data #8578

Closed
zaliqarosli opened this issue Apr 6, 2023 · 1 comment · Fixed by #8651
Closed

[instruments] Error on saving LINST data #8578

zaliqarosli opened this issue Apr 6, 2023 · 1 comment · Fixed by #8651
Assignees
@laemtl
Labels
25.0.0 - Bugs Category: Bug PR or issue that aims to report or fix a bug Critical to release PR or issue is key for the release to which it has been assigned

Comments

@zaliqarosli
Copy link
Contributor

zaliqarosli commented Apr 6, 2023 •
edited
Loading

Describe the bug

Error below produced on saving data. however on refresh, it appears the data was saved.

Screenshot 2023-04-06 at 1 42 38 PM

To Reproduce
Steps to reproduce the behavior (attach screenshots if applicable):

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

What did you expect to happen?
A clear and concise description of what you expected to happen.

Browser Environment (please complete the following information):

  • OS: [e.g. Plan9, HURD, Oberon, etc]
  • Browser [e.g. chrome, firefox] (note that only these two browsers are supported)
  • Version [e.g. 22]

Server Environment (if known):
Note: We only support the most recent release of LORIS.

  • LORIS Version: [e.g. 22.0.0]
  • Linux distribution and Version: [e.g. Ubuntu 16.04, CentOS 7]
  • MySQL/MariaDB Version: [e.g. MySQL 5.7, MariaDB 10.3]

Additional context
Add any other context about the problem here.
@zaliqarosli zaliqarosli added Category: Bug PR or issue that aims to report or fix a bug 25.0.0 - Bugs labels Apr 6, 2023
@zaliqarosli zaliqarosli mentioned this issue Apr 6, 2023
Closed
14 tasks
@xlecours xlecours added the Critical to release PR or issue is key for the release to which it has been assigned label Apr 11, 2023
@laemtl laemtl mentioned this issue Apr 19, 2023
Merged
driusan pushed a commit that referenced this issue Apr 25, 2023
@laemtl
Fix React upgrade regression (#8651)
9941176 
Fix all potential errors similar to the one solved by d4cf493 by chaining render call instead of using a const.

Fixes #8578
@laemtl laemtl mentioned this issue Apr 25, 2023
Merged
driusan pushed a commit that referenced this issue May 2, 2023
@laemtl
[RB] Fix bmi DB error (#8673)
bc3e4a8 
An inconsistency between the linst file and the sql schema in the enum field unit_classification trigger a 500 error. Fixed by updating the enum with the missing value in the SQL schema.

Fixes #8578
@driusan
Copy link
Collaborator

driusan commented May 2, 2023

Should have been auto-closed when the PR was merged. This is done.

@driusan driusan closed this as completed May 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@laemtl laemtl

Labels
25.0.0 - Bugs Category: Bug PR or issue that aims to report or fix a bug Critical to release PR or issue is key for the release to which it has been assigned
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix React upgrade regression laemtl/Loris
4 participants
@driusan @xlecours @zaliqarosli @laemtl