$ echo 'console.log(0x8000000000000000, 9223372036854776000)' | esbuild-minify wasm-0112482e:997 RuntimeError: float unrepresentable in integer range at runtime.wasmTruncS (wasm-function[996]:0xce0ae) at esbuild
Reproduced on Elasticsearch version 6.3.2 in Elastic Cloud Looks like this was addressed in [https://github.com//pull/27207] but problem still exists. Steps to reproduce: PUT testindex{ "settings":{ "number_of_shards":1 }, "mappings":{ "...
Therefore, the correct way is not more sanitization – the correct way is to make an “invalid vector” unrepresentable. erlehmann changed the title Server does not sanity-check player positions Giving float vector with x outside of -2.14748e+06 < x < 2.14748e+06 as a function argument cra...