You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have found two issues with Raremetal-server covariance endpoint:
If any of the masks in a region are empty, the server rejects the entire request.
It seems that the success of the request is partially sensitive to the content-type encoding header sent to the server. (see example below using requests; introspect differences using test.request.headers)
Expected behavior
This is a topic for discussion.
Reproducible test case
In the below example, mask 3 is empty for this region, but all other masks are valid.
Interestingly, if the POST request is sent using data= instead of json=, the request will succeed. (due to a different content-type header being sent with the request)
The text was updated successfully, but these errors were encountered:
abought
added a commit
to statgen/locuszoom
that referenced
this issue
May 20, 2019
Summary
We have found two issues with Raremetal-server covariance endpoint:
content-type
encoding header sent to the server. (see example below using requests; introspect differences usingtest.request.headers
)Expected behavior
This is a topic for discussion.
Reproducible test case
In the below example, mask 3 is empty for this region, but all other masks are valid.
Interestingly, if the POST request is sent using
data=
instead ofjson=
, the request will succeed. (due to a differentcontent-type
header being sent with the request)The text was updated successfully, but these errors were encountered: