let me know and we can fix it
using the same version for 27 separate packages is pretty disruptive FWIW
a bug fix to one would force env updates for all users of every package
but up to you!
where do I get graph.pkl from? https://github.com/regro/cf-scripts/blob/master/scripts/build_graph.xsh#L6
the graph is sharded into thousands of little json files
they decided they needed their own thing
Hi everybody. Amazing tool that help us a lot. Do anyone have knowledge about status of bot today? I'm waiting 8 hours (since pypi publish) to get PR for https://github.com/conda-forge/k3d-feedstock/pulls
see also https://conda-forge.org/status/
this is the latest version the bot found
also check the status page for errors in the version section
looks like it reported an error there
he recipe did not change in the version migration, a URL did not hash, or there is jinja2 syntax the bot cannot handle!
Please check the URLs in your recipe with version '2.11.0' to make sure they exist!
We also found the following errors:
- could not hash URL template 'https://pypi.io/packages/source/{{ name[0] }}/{{ name }}/{{ name|upper }}-{{ version }}.tar.gz'
a common mistake is to push a wheel and not an sdist
check the recipe
found it
this url works: https://pypi.io/packages/source/k/k3d/k3d-2.11.0.tar.gz
this does not: https://pypi.io/packages/source/k/K3D/k3d-2.11.0.tar.gz
you need to fix this line: https://github.com/conda-forge/k3d-feedstock/blob/master/recipe/meta.yaml#L9
remove the
upper filter on the name
:heart:
I will re-run automaticaly or I need to do something?
the bot tries three times per version
and then it downweights it in its list of PRs to try
so it will be retried eventually
but at random and only if there is time
i'd suggest making a manual PR for this one
Thanks a lot for all your help
:)