Closed nkittur-uga closed 3 years ago
Also:
GEMS1 study
I tried it the other way around:
Here is some POST data for the first example above:
{"valueSpec":"count","filters":[{"entityId":"EUPATH_0000096","variableId":"EUPATH_0010375","stringSet":["Case"],"type":"stringSet"},{"entityId":"EUPATH_0000738","variableId":"OBI_0001508","stringSet":["Enrollment"],"type":"stringSet"}],"binSpec":{"displayRangeMin":-30,"displayRangeMax":20,"binWidth":0.09}}
I believe this has resolved on its own. Maybe the study was being reloaded at the time?
I confirm Ryan's observation on qa. (I remember GEMS1 not being available yesterday for a bit too.) Closing this ticket.
Yes, this bug seems to have resolved on its own.
Danica, regarding your comment on subsetting, all cases have enrollment data so the counts don't change if you select both "case" and "enrollment". I can explain on slack if needed.
QA is complete.
GEMS1 study
I got the spinning loading wheel for several minutes and then this error:
Error: 502 Proxy Error <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request POST /eda-data/studies/GEMSCC0003-1/entities/EUPATH_0000738/variables/EUPATH_0015710/distribution.
Reason: Error reading from remote server