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

autotick bot is not working #102

Open
1 task done
traversaro opened this issue Mar 6, 2024 · 6 comments
Open
1 task done

autotick bot is not working #102

traversaro opened this issue Mar 6, 2024 · 6 comments
Labels

Comments

@traversaro
Copy link
Contributor

Solution to issue cannot be found in the documentation.

  • I checked the documentation.

Issue

For some reason the autotick bot that automatically updates the recipe is not working. For this reason, we need to manually update the recipe.

Installed packages

.

Environment info

.
@traversaro traversaro added the bug label Mar 6, 2024
@traversaro
Copy link
Contributor Author

fyi @AlessiaDMiit

@traversaro
Copy link
Contributor Author

The error from https://conda-forge.org/status/ is :

66.00 attempts - The 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 '3130' to make sure they exist!

We also found the following errors:

 - could not hash URL template 'https://github.com/casadi/casadi/releases/download/{{ version }}/casadi-source-v{{ version }}.zip'
 - 

@traversaro
Copy link
Contributor Author

traversaro commented Mar 6, 2024

I think the logic to find the latest release is finding the https://github.com/casadi/casadi/releases/tag/nightly-issue_3130 (that is not an actual release, just a working tag I guess) and assuming that is the latest releases. To be honest, I do not know how to solve this (it would be cool to have some custom feedstock-specific logic to exclude tags that are unwanted, but I am not sure how this can be implemented. In the meanwhile, we can just update the version manually.

This was referenced Mar 6, 2024
@traversaro
Copy link
Contributor Author

To be honest, I do not know how to solve this (it would be cool to have some custom feedstock-specific logic to exclude tags that are unwanted, but I am not sure how this can be implemented. In the meanwhile, we can just update the version manually.

I think the logic to find the latest release is finding the https://github.com/casadi/casadi/releases/tag/nightly-issue_3130 (that is not an actual release, just a working tag I guess) and assuming that is the latest releases. To be honest, I do not know how to solve this (it would be cool to have some custom feedstock-specific logic to exclude tags that are unwanted, but I am not sure how this can be implemented. In the meanwhile, we can just update the version manually.

Kind of related to regro/cf-scripts#1441 .

@traversaro
Copy link
Contributor Author

fyi @agriyakhetarpal I forgot I already opened an issue for the missing automatic update.

@traversaro
Copy link
Contributor Author

To be honest, I do not know how to solve this (it would be cool to have some custom feedstock-specific logic to exclude tags that are unwanted, but I am not sure how this can be implemented. In the meanwhile, we can just update the version manually.

Probably related to regro/cf-scripts#1441 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant