Skip to content
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

hatchling v1.26.3 #62

Merged
merged 2 commits into from
Nov 13, 2024
Merged

Conversation

regro-cf-autotick-bot
Copy link
Contributor

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

  • Dependencies have been updated if changed: see upstream
  • Tests have passed
  • Updated license if changed and license_file is packaged

Information about this PR:

  1. Feel free to push to the bot's branch to update this PR if needed.
  2. The bot will almost always only open one PR per version.
  3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
  4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
  5. If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

Closes: #61

This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/11807357188 - please use this URL for debugging.

@conda-forge-admin
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ No valid build backend found for Python recipe for package hatchling using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.

@ofek ofek mentioned this pull request Nov 12, 2024
3 tasks
@ofek
Copy link
Contributor

ofek commented Nov 12, 2024

This is blocked on packaging conda-forge/packaging-feedstock#31

@matthewfeickert
Copy link
Member

@conda-forge-admin, please rerender

@matthewfeickert
Copy link
Member

matthewfeickert commented Nov 13, 2024

I was too fast on the draw there as it is going to rerender before the build for the merged conda-forge/packaging-feedstock#31 finishes. @ofek, can you just rebase and force-push in about 20 minutes?

@conda-forge-admin
Copy link
Contributor

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11808037084.

@jakirkham
Copy link
Member

FWIW there is a bot command to restart CI

@matthewfeickert
Copy link
Member

matthewfeickert commented Nov 13, 2024

FWIW there is a bot command to restart CI

@jakirkham Yes, but I've never had it work correctly (conda-forge/awkward-feedstock#149 (comment)). I should file an Issue on that though.

edit: Let me try here though and worst case scenario I'll have something to screenshot if it doesn't work as expected.

@matthewfeickert
Copy link
Member

@conda-forge-admin, please restart ci

@matthewfeickert
Copy link
Member

matthewfeickert commented Nov 13, 2024

I've never had it work correctly
...
Let me try here though and worst case scenario I'll have something to screenshot if it doesn't work as expected.

As mentioned:

image

In the CI logs

Starting: Checkout conda-forge/hatchling-feedstock@refs/pull/62/merge to s
==============================================================================
Task         : Get sources
Description  : Get sources from a repository. Supports Git, TfsVC, and SVN repositories.
Version      : 1.0.0
Author       : Microsoft
Help         : [More Information](https://go.microsoft.com/fwlink/?LinkId=798199)
==============================================================================
Syncing repository: conda-forge/hatchling-feedstock (GitHub)
git version
git version 2.47.0
git lfs version
git-lfs/3.5.1 (GitHub; linux amd64; go 1.21.8)
git init "/home/vsts/work/1/s"
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: 	git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: 	git branch -m <name>
Initialized empty Git repository in /home/vsts/work/1/s/.git/
git remote add origin https://github.com/conda-forge/hatchling-feedstock
git config gc.auto 0
git config core.longpaths true
git config --get-all http.https://github.com/conda-forge/hatchling-feedstock.extraheader
git config --get-all http.extraheader
git config --get-regexp .*extraheader
git config --get-all http.proxy
git config http.version HTTP/1.1
git --config-env=http.extraheader=env_var_http.extraheader fetch --force --tags --prune --prune-tags --progress --no-recurse-submodules origin   +refs/heads/*:refs/remotes/origin/* +refs/pull/62/merge:refs/remotes/pull/62/merge
fatal: couldn't find remote ref refs/pull/62/merge
##[warning]Git fetch failed with exit code 128, back off 4.987 seconds before retry.
git --config-env=http.extraheader=env_var_http.extraheader fetch --force --tags --prune --prune-tags --progress --no-recurse-submodules origin   +refs/heads/*:refs/remotes/origin/* +refs/pull/62/merge:refs/remotes/pull/62/merge
fatal: couldn't find remote ref refs/pull/62/merge
##[warning]Git fetch failed with exit code 128, back off 8.168 seconds before retry.
git --config-env=http.extraheader=env_var_http.extraheader fetch --force --tags --prune --prune-tags --progress --no-recurse-submodules origin   +refs/heads/*:refs/remotes/origin/* +refs/pull/62/merge:refs/remotes/pull/62/merge
fatal: couldn't find remote ref refs/pull/62/merge
##[error]Git fetch failed with exit code: 128
Finishing: Checkout conda-forge/hatchling-feedstock@refs/pull/62/merge to s

I'll open up an issue for this in https://github.com/conda-forge/conda-forge-webservices.

@jakirkham
Copy link
Member

Thanks for the clear example Matthew! 🙏

Looks like issue: conda-forge/conda-forge.github.io#2346

Agree this is unfortunate

@ofek ofek merged commit 9a8f0a7 into conda-forge:main Nov 13, 2024
4 checks passed
@regro-cf-autotick-bot regro-cf-autotick-bot deleted the 1.26.3_h1fc7af branch November 13, 2024 03:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants