-
-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing module name tomli #608
Comments
We're also seeing this issue and it's blocking all of our pip installs + builds
|
+1 In my case it happens when pip builds a wheel for the "lazy-object-proxy" package. We are not explicitly installing "setuptools-scm", but it seems that Pip uses it under the covers when building a wheel. Test run that fails: https://github.com/zhmcclient/zhmc-ansible-modules/pull/450/checks?check_run_id=3442020780#step:10:373 |
Same here occuring during the installation of
|
Same issue here. I've tried |
Adding to this pileon, I am affected by this |
Same here, I assume #607 is the culprit. |
Same here |
Same issue 👍 |
A well used package - Nine projects reported an issue within 16 minutes :-) I can see that the METADATA file in the setuptools-scm 6.1.1 package pulls in tomli as part of an extra "tomli", but it seems that Pip when it uses setuptools-scm under the covers does not install that extra, and setuptools-scm seems to depend on tomli even when the "tomli" extra is not installed. So if tomli is really an optional extra, then setuptools-scm should not fail when it is not there. If it is required, it should not be an extra. At least IMHO. |
It's a Friday evening and I'm sitting with a broken CI 😭 |
Broken CI here too 🙅 |
broken CI here as well |
Has anyone figured a workaround? I've tried, prior to my |
cc @RonnyPfannschmidt who made the transition from toml to tomli in #586. |
i just returned to the computer to yank this release as well, it seems i will have to re engineer the way this is tested to stop missing those issues until reports pour in , a new release with the issue resolved will land later today |
You'll want to pin |
I just wanted to say a HUGE THANK YOU @RonnyPfannschmidt, for all your work on In open source is easy to get a lot of attention when things stop working, without the much deserved appreciation the maintainers deserve. |
+1 for that, the bad version was yanked within the hour and my builds are all ✅ again Great work @RonnyPfannschmidt 🍰 ✨ 🏆 ⭐ |
Yes, I see it at https://readthedocs.org/projects/astropy/builds/14629185/ |
same here 👋 |
Same, seeing CI failures because of this now. |
I am seeing the same issue in CI. |
Same here 👋 |
Same here |
Same here ! a Friday evening 🥲 |
Same here 🆘 |
We're also experiencing this, but I'm going to work through pinning a prior version to see if it solves it in the interim for us. Sending good vibes to the maintainers for the work they're putting in to monitor & fix this 💟 🥂 |
Also experiencing the issue. Good vibes and happy Friday to all! ❤️ |
Fix is already going up, no need to comment "Same here" #628 |
Still failing on github actions.... |
just worked for me |
Back to normal... Thanks for the quick resolution! 👍 |
Thanks so much! This was the fastest fix I've ever seen, our intern and I thank you :D |
lol...thanks @RonnyPfannschmidt for the lightning quick fix! my CI builds thank you too! |
Thanks @RonnyPfannschmidt , you saved my Friday |
Since the release of setuptools_scm 6.1.1 a few minutes ago, our jenkins jobs are failing on the following error:
Maybe a missing dependency somewhere?
The text was updated successfully, but these errors were encountered: