Protobuf module started making it impossible to access the UCAR THREDDS server using siphon TDSCatalog about siphon

[edrewitz]

Forgot to mention, I am using Windows OS and Python 3.11.4.

[dopplershift]

I assume since you closed this you got it figured out?

[edrewitz]

I assume since you closed this you got it figured out?

Good day Ryan,

Yes I found the fix. I'll speak about it here since it could potentially be helpful to others if they encounter the same issue.

So as I stated above, at least one of the DLLs for my Python became corrupted and I had to uninstall both python and miniconda3 and reinstall. I was using Python 3.11.4. When I reinstalled Python 3.11.4 I installed miniconda 3.11. One weird thing I encountered when troubleshooting miniconda 3.11 was when I had the path to environment variable box checked, the scripts that utilize the cfgrib module ran fine in the windows task scheduler but the scripts using siphon did not. Likewise, when I uninstalled and re-installed miniconda 3.11 and left the path to environment variable box unchecked, the scripts that utilize cfgrib did not run in the windows task scheduler error code 0x1 but the scripts using siphon ran fine.

The fix turned out to be using miniconda 3.10 with having the path to environment variable box checked (I had all 4 boxes checked when setting up miniconda 3.10) and that fixed everything as now both the scripts that use cfgrib and siphon work. It appears that protobuf module that siphon uses isn't friendly with miniconda 3.11 yet but works fine with miniconda 3.10.

I hope this helps.

Regards,

Eric Drewitz

[dopplershift]

Hrrmm, I sense there's something more complicated going on here. Siphon's test suite (including the protobuf-based functionality) is passing locally for me on both Python 3.11 and 3.12 on arm64 macOS. We need to do some more work here on GitHub to get the CI runs back to get a good test on Windows here to be sure, but I'm concerned this is more environment related.