Wednesday, 2026-06-03

*** ykarel__ is now known as ykarel04:46
opendevreviewMerged openstack/releases master: Tag governance 0.21.0 for API changes  https://review.opendev.org/c/openstack/releases/+/99048209:28
frickleriirc last time we had a similar issue, fungi found something wrong with our release? or is this just pypi being borekd? HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/10:03
elodillesfrickler: you mean the release job failure? https://zuul.opendev.org/t/openstack/build/2ccb441c9f0543cc9ca4c38f7e9c124810:36
elodillesyes, as far as i remember there were something wrong in the pyproject.toml10:36
elodillessome typo10:37
elodillesbut then a pyproject.toml validator was introduced as i remember10:37
elodillesor is the patch still waiting for merge? :-o10:37
elodillesthough validate-pyproject doesn't show any issue with governance's pyproject.toml10:39
elodilleshmm10:39
elodillesAI says that the issue is the "Private :: Do Not Upload" classifier. i don't know if that is true10:49
elodillesthat is odd that the validator didn't say anything about this10:49
elodillesstephenfin: any idea? or is it really the mentioned classifier? ^^^10:53
fricklerwell if pyproject.toml really says "Do Not Upload", then why do we try that? seems very reasonable to me from pypi to complain10:54
fricklerso yes, this was introduced in https://review.opendev.org/c/openstack/governance/+/989151 without any explanation. previous tags did get uploaded https://pypi.org/project/openstack-governance/#history10:57
fricklermaybe this discussion should move to the tc channel, then10:57
elodillesit makes sense that that is the root cause, but i'm no pyproject.toml expert o:)11:02
elodillesyes, this can be continued on tc channel, though i guess it's stephenfin who'll have the final word on this o:)11:02
frickleryes, would be good to hear the reasoning for that, since I don't see any matching statement in the deleted setup.cfg11:06
fungisounds like a corner case. i wouldn't expect `validate-pyproject` to consider that necessarily *invalid* content for a pyproject.toml file, though i understand why warehouse does. maybe `twine --check` would be the better place to catch that?12:42
elodillesor a warning in verbose output of validate-pyproject. o:)12:43
stephenfinelodilles: oh, I may have borked that /o\12:51
stephenfinI added that classifier on the assumption that we shouldn't push that library to PyPI but I think we actually *do* want to do that12:51
elodillesi see. then if you also say that it is the cause of the upload "error" then it should be removed and we can try another release, right?12:53
stephenfinYes, I think that's the best course of action12:54
stephenfinApologies for the misunderstanding /o\12:54
elodillescool :) then let's do that 12:55
elodillesno problem, the important thing is that now we know a way forward o:)12:55
fungii suppose it's also a specific enough case that we could introduce a check of our own in the job to make sure that string doesn't appear in the metadata13:01
fungiif we expect this to come up often13:01
fungia clearer error in the upload api response would have been great though13:01
stephenfinI'd imagine that will never happen again13:01
elodillesfungi: yes, a better explanation instead of a HTTP 400: Bad Request would be better :/13:02
fungiwith people using llms to write everything these days, i don't say "never" any more13:02
elodillesbut i agree with stephenfin that this likely won't happen in the future, as Stephen added it intentionally as he said13:03
fungisome llm has already been trained that the classifier is useful to include because it saw that in the openstack/governance repo at one point13:03
fungibut yeah, the risk is low, and we know to look for it if it does recur13:04
elodilles:)13:04

Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!