4.0.8 - Bug Fixes

[dostuffthatmatters]

• Freeze the poetry dependencies to the one used in 4.0.7
• Unreachable Peer PLC issue since 4.0.7  #151
• Remove git commit sha from emails
• Improve astronomy utilities #126
• Pass config to Astronomy directly instead of setting the class parameter in config-logs #125
• Issue with Astropy with stations that don't have an internet connection #154
• PLC Exception Timeout doesn't work when PLC is controlled by user #157
• Reduce codebase size by using tum-esm-utils more #165
• Eliminate possibility to start the Core from multiple PYRA versions at the same time #156

[netlify]

✅ Deploy Preview for pyra-4-documentation canceled.

Name	Link
🔨 Latest commit	dbd7a1a
🔍 Latest deploy log	https://app.netlify.com/sites/pyra-4-documentation/deploys/63efa153f5a7d80008215c4b

[dostuffthatmatters]

@patrickjaigner Python needs an exact version (3.10 is not valid, but 3.10.6 is). However, we don't know which Python version existing users have installed (the docs don't specify a minor release: https://pyra.esm.ei.tum.de/docs/user-guide/setup#python-310). Therefore, I added the 3.10.* only for the Python version. But Python itself definitely keeps their semantic versioning straight.

[patrickjaigner]

Looks good.

[dostuffthatmatters]

I rebased this branch to the latest main branch (extended documentation). That is why I force-pushed it. Also, I needed to change base for the PR to recognize that it is only 3 commits ahead.

[patrickjaigner]

Regarding #155 I'm not too fond of this change. It doesn't address the core issue and force closes all currently running OPUS instances. It also introduces a new method of closing OPUS in addition to the already existing one.
There is an easier solution for it.

[dostuffthatmatters]

Regarding #155 I'm not too fond of this change. It doesn't address the core issue and force closes all currently running OPUS instances. It also introduces a new method of closing OPUS in addition to the already existing one. There is an easier solution for it.

Sure, then I will comment out the changes from #155, and we can do that in a later release, once we know how to fix this elegantly.