`nwm_client` does not work in FIPS environments

Question

`nwm_client` does not work in FIPS environments

jarq6c opened this issue 3 years ago · 1 comments

The current version of nwm_client uses concurrent.futures.ProcessPoolExecutor which tracks processes using md5 which is disabled by FIPS. This leads to the client hanging and never returning with data in a FIPS environment.

Switching to an async systems like nwm_client_new or using fsspec will hopefully fix this issue. It's also possible that upgrading to Python 3.10+ may resolve the issue, as well.

Answer 1 · 2022-07-23T23:24:23.000Z

This issue is resolved by upgrading to Python 3.9+.