-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Status 500 when trying to put more precise order. #611
Comments
Thanks for the detailed report @SvetJordanov, I'm able to reproduce this. Unfortunately we can't read the error response due to a bug in marketmaker (see here), that's what's causing the cryptic CORS error. However reproducing the issue and grabbing the exact request as cURL in devtools and then re-playing in a shell shows the error:
You can see volume is clearly set as @artemii235 are you aware of this issue? Possibly an overflow/rounding error inside marketmaker? |
The error is correct, because |
Woops, my mistake, thanks @cipig. @SvetJordanov could that also be the issue you were experiencing? If you try a smaller more precise number do you still get errors? |
When putting order on HyperDex for example 3.77 Morty to KMD it hits status code 500(Internal server error) with message in the developer tools -> "Access to fetch at 'http://127.0.0.1:49933/' from origin 'app://-' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled."
I can put an order of 3 (Integer number), also can put an order of 3.7, but with more precise numbers like 3.77 and 3.777 it gets the error.
HyperDEX Nightly 0.0.0-c2d7531-19.7.24.1745
Electron 5.0.8
win32 10.0.10586
Locale: en-US
The text was updated successfully, but these errors were encountered: