[03:06] <blackboxsw> community notice: today was the estimated cutoff for the quarterly upstream release of cloud-init version 24.2. The cutoff date we would like for features or bugfixes to make it into this release will be Friday May 31st. We have created a 24.2 milestone in github to represent Pull requests and issues we would like to resolve before cutting our upstream release. If you have a PR or issue that needs review. Please let us know.
[06:21] <ani> I am seeing this issue when I run `tox -e mypy` https://pastebin.com/uXtQnjsZ any ideas how to get past it?
=== cpaelzer_ is now known as cpaelzer
[06:32] <aciba> ani: does this help? https://pastebin.ubuntu.com/p/8B2fkYqF8Y/
[06:39] <ani> aciba you are amazing! It does indeed solve it. Can you patch the upstream please? That way I do not have to maintain it downstream
[06:39] <ani> I am also getting this error in the end after running tox https://pastebin.com/GU2gDk3L
[06:46] <aciba> ani: I can porpose an upstream PR to fix the jinja2 one. about the pylint one, that one looks more strange. Not sure I can reproduce it
[06:48] <ani> OK
[06:48] <aciba> but beaware the the dependencies for linters in tox.ini are pinned targeting the python version in Ubuntu focal which is py3.8. And you are running python3.12
[06:49] <aciba> that's probably what's breaking you
[06:49] <ani> 3.12.2 yes. Thats what comes in fedora 40
[06:54] <aciba> ani: https://github.com/canonical/cloud-init/pull/5337
[06:54] -ubottu:#cloud-init- Pull 5337 in canonical/cloud-init "ci(mypy): add type-jinja2 stubs" [Open]
[06:55] <aciba> ani: https://github.com/canonical/cloud-init/pull/5337