Loris: [API] CandID missing from "Meta" object for /recordings

Created on 21 May 2020  路  10Comments  路  Source: aces/Loris

Describe the bug
GET /candidates/$CandID/$Visit/recordings,
GET /candidates/$CandID/$VisitLabel/recordings/$Filename/channels,
GET /candidates/$CandID/$VisitLabel/recordings/$Filename/electrodes,
GET /candidates/$CandID/$VisitLabel/recordings/$Filename/events
all return "CandID":{} in "Meta" object.

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

  1. Go to 'https://test-loris-dev.loris.ca/api/v0.0.3/candidates/300166/V1/recordings'. Response is {"Meta":{"CandID":{},"Visit":"V1"}, ...
  2. Go to 'https://test-loris-dev.loris.ca/api/v0.0.3/candidates/300166/V1/recordings/sub-OTT166_ses-V1_task-faceO_eeg.edf/channels'. Response is {"Meta":{"CandID":{},"Visit":"V1 ...
  3. Going to /electrodes and /events endpoints will result in the same

What did you expect to happen?
"CandID" key to have $candID as value

23.0.0-testing API Bug

All 10 comments

@spell00 any progress on this one ?

similarly to #6570 and #6572, I can replicate the issue on the testing VM, but not my personal dev VM

@spell00 Can you retest now that Shen reloaded Apache?

IT is still not working

I was able to replicate this both on the testing VM and my own VM (head at 23.0-release) this afternoon.

@spell00 are you sure you could not replicate the issue on your VM? Maybe you were not on the right branch? Can you retest and fix the issue? Thanks!

I solved the problems with my VM, I can replicate it now. I'm on it!

Actually I have some rectifications. I can replicate all errors on Chrome, but on Firefox GET /candidates/$CandID/$VisitLabel/recordings/$Filename/events returns the correct string for CandID
( {"Meta":{"CandID":"300166","Visit":"V1","File":"sub-OTT166_ses-V1_task-faceO_eeg.edf"},...
, but the expected error is {"Meta":{"CandID":{},"Visit":"V1","File":"sub-OTT166_ses-V1_task-faceO_eeg.edf"},).

I also found other differences between firefox/chrome on my VM that could be related to this issue:
https://<VM-user>.loris.ca/api/v0.0.3/candidates/300166/V1/recordings/sub-OTT166_ses-V1_task-faceO_eeg.edf/events/meta,
https://<VM-user>.loris.ca/api/v0.0.3/candidates/300166/V1/recordings/sub-OTT166_ses-V1_task-faceO_eeg.edf/channels/meta,
https://<VM-user>.loris.ca/api/v0.0.3/candidates/300166/V1/recordings/sub-OTT166_ses-V1_task-faceO_eeg.edf/electrodes/meta,
the error CandID : {} is also present on Firefox, they are all CandID : 300166

Ok, good to know. Does the issue replicate in the same way after clearing caches on Firefox ?
Any ideas from the internet as to why Firefox/Chrome could be handling this differently?

Thank you @christinerogers, clearing caches solves the problem. It is necessary to clear the cache to see the changes made to the code for both Firefox and Chrome. So in conclusion, Firefox/Chrome did not handle the requests differently

Was this page helpful?
0 / 5 - 0 ratings