[BUG] Cellxpose returns 400 Bas request for some requests if data is 16-bit
See original GitHub issueDescribe the bug
Try saving test file after converting to fp16:
adata.X = adata.X.astype('float16')
Server normally starts when given this data (but prints some warnigns about conversion from 64bits).
However when you select gene or run differential expression, 400 appears.
Version affected: 0.17.0, within docker
In my case cellxgene first downloads file from the cloud, so 16bit format for storage is very reasonable - almost halves the space.
Issue Analytics
- State:
- Created 2 years ago
- Comments:17 (11 by maintainers)
Top Results From Across the Web
How to Fix a 400 Bad Request Error (Causes and Fixes) - Kinsta
The 400 Bad Request error indicates that the server cannot or process the request due to a client error. Read about the common...
Read more >How to Fix a 400 Bad Request Error: 8 Easy Methods
The 400 bad request error is an HTTP status code that describes an error caused by an invalid request. Thus, the server can't...
Read more >How to Fix a 400 Bad Request Error [Causes and Fixes]
The 400 bad request is an HTTP response code sent from a web server that didn't understand the request sent from your browser....
Read more >"HTTP 400 Bad Request" error when proxying HTTP requests ...
This error (HTTP 400 Bad Request) means that Internet Explorer was able to connect to the web server, but the webpage could not...
Read more >Requests Documentation - Read the Docs
Some servers may return a JSON object in a failed response (e.g. error details with HTTP 500). Such JSON will be decoded and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fixed in 1.0.1
Suggest a cast in diffex code if the set1/set2 slices are fp16, as that is where the dependency lives. Pretty sure the rest of the code base does not have this constraint.
As it is already sliced out of the main matrix, you will retain most of the memory savings (ie, the cast to 32 bit will be only for the duration of the t-test compute)