Loris icon indicating copy to clipboard operation
Loris copied to clipboard

[dataquery] Results page broken

Open CamilleBeau opened this issue 6 months ago • 2 comments

Describe the bug I selected Medical History data for V2 in a query, and then in the filters added that the data entry should be either "In Progress" or "Complete" for V2. The results were buggy: This happened the first time I did it: Image This happened the second time I did it Image

Image

To Reproduce Steps to reproduce the behavior:

  1. Go to the DQT Beta
  2. Click on Modify Fields
  3. Select Medical history instrument and "Add all" to add all fields with only V2
  4. Go to Modify Filters
  5. Add a filter for the Medical history "Data entry" field to be equal to "In Progress" only for V2
  6. Click "Add 'or' Condition" and add a filter for the Medical history "Data entry" field to be equal to "Complete" only for V2.
  7. Run query
  8. See error

What did you expect to happen? The query to run normally with organized results

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.

CamilleBeau avatar Jun 13 '25 16:06 CamilleBeau

Can you include the result of the "run" endpoint on the query tab? That looks like it's either a problem with the instrument or a problem with the VM it was on, based on all the "internal error" headers..

driusan avatar Jun 13 '25 16:06 driusan

@driusan

Image

CamilleBeau avatar Jun 13 '25 16:06 CamilleBeau

Testing VM issue. new patch solved the issue.

kongtiaowang avatar Jun 17 '25 17:06 kongtiaowang

@kongtiaowang what new patch? Is there a PR or was it an issue on the VM?

driusan avatar Jun 17 '25 17:06 driusan

it is an issue on the tesing VM, after re-run install RB data. issue solved. I means the patch is the new RB dataset.

kongtiaowang avatar Jun 17 '25 18:06 kongtiaowang