Closed Joshuaalbert closed 8 months ago
This looks like it might be environment related. Specifically, it looks like numba is upset about its cache. This can be due to permissions and we have seen the like when running on AWS. Could you please try setting the NUMBA_CHACHE_DIR
environment variable to point to a location where you have permissions? See the following for an explanation: https://numba.pydata.org/numba-doc/dev/reference/envvars.html#envvar-NUMBA_CACHE_DIR
Thanks, yep it was permissions. Resolved!
Describe the bug
Version