Sujit Hiwale

Results 4 comments of Sujit Hiwale

I ran the test with `yarn test --testPathPattern=ReactFlightAsyncDebugInfo-test.js` and the result was: ``` yarn run v1.22.22 $ node ./scripts/jest/jest-cli.js --testPathPattern=ReactFlightAsyncDebugInfo-test.js $ NODE_ENV=development RELEASE_CHANNEL=experimental compactConsole=false node ./scripts/jest/jest.js --config ./scripts/jest/config.source.js --testPathPattern=ReactFlightAsyncDebugInfo-test.js Running...

``` [numpy/numpy/_core/src/multiarray/convert_datatype.c](https://github.com/numpy/numpy/blob/50997e3c3b1f9331d3b03e3867c4896422278e52/numpy/_core/src/multiarray/convert_datatype.c#L1329-L1351) Lines 1329 to 1351 in [50997e3](https://github.com/numpy/numpy/commit/50997e3c3b1f9331d3b03e3867c4896422278e52) case NPY_DOUBLE: { double value = *(double *)valueptr; if ((value > -65000 && value < 65000) || !npy_isfinite(value)) { return NPY_HALF; }...

@oscarbenjamin Thanks for the feedback. You were absolutely right about not special-casing I. That would only have patched one symptom instead of fixing the underlying recursion path. I've now updated...

Try out: `wget -c --tries=10 --timeout=30 --waitretry=10 http://pjreddie.com/media/files/yolov1.weights` It will resume the download if it stops and retry on failure. If you are still getting errors, I'd recommend using `curl`...