Hi Brian, The segmentation fault that was solved in 2.5, but it just moved to aug 2020.
What command should I not use in the API to not run into this, or did I unearth another bug?
Peter
quantrocket_flightlog_1|2021-03-25 00:48:27 quantrocket.zipline: INFO [signal_industry.DEF] █████████- 94% 2020-08-31 582% 1.36 -16% $5817648
quantrocket_houston_1|172.18.0.12 - - [25/Mar/2021:00:48:27 +0000] "POST /flightlog/handler HTTP/1.1" 200 5 "-" "-"
quantrocket_zipline_1|/opt/conda/lib/python3.6/site-packages/zipline/data/resample.py:302: RuntimeWarning: All-NaN slice encountered
quantrocket_zipline_1| val = np.nanmax(window)
quantrocket_zipline_1|/opt/conda/lib/python3.6/site-packages/zipline/data/resample.py:366: RuntimeWarning: All-NaN axis encountered
quantrocket_zipline_1| val = np.nanmin(window)
**quantrocket_zipline_1|!!! uWSGI process 191 got Segmentation Fault !!!**
quantrocket_zipline_1|*** backtrace of 191 ***
quantrocket_zipline_1|uWSGI worker 2(uwsgi_backtrace+0x30) [0x46d780]
quantrocket_zipline_1|uWSGI worker 2(uwsgi_segfault+0x21) [0x46db21]
quantrocket_zipline_1|/lib/x86_64-linux-gnu/libc.so.6(+0x350e0) [0x7fbbdd5000e0]