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.
The current version of
nwm_client
usesconcurrent.futures.ProcessPoolExecutor
which tracks processes usingmd5
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 usingfsspec
will hopefully fix this issue. It's also possible that upgrading to Python 3.10+ may resolve the issue, as well.