You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
HI @amartinhuertas, there is already a DOCUMENTER_KEY both in secrets and deploy keys in PartitionedArrays.jl. Was this also the case in SparseMatricesCSR.jl ?
The reason will be displayed to describe this comment to others. Learn more.
Hi @fredrikekre, we are having a very annoying bug with TabBot. It is unable to add a new release in the repo after succesfuly registering new versions with JuliaRegistrator. We get this error:
e2307e0There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@JuliaRegistrator register()
e2307e0There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Registration pull request created: JuliaRegistries/General/75824
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
e2307e0There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @fverdugo.
Can you follow the instructions here https://discourse.julialang.org/t/latest-version-of-docs-not-published-github-actions-tagbot/50634/19 to try to solve the tagbot issue?
It worked for SparseCSR ... jl, although I am not 100% sure the cause is the same.
e2307e0There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
HI @amartinhuertas, there is already a DOCUMENTER_KEY both in secrets and deploy keys in PartitionedArrays.jl. Was this also the case in SparseMatricesCSR.jl ?
e2307e0There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No. There were no keys in SparseMatricesCSR.jl.
e2307e0There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps trying to remove the existing ones and regenerating new ones may help?
e2307e0There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @fredrikekre, we are having a very annoying bug with TabBot. It is unable to add a new release in the repo after succesfuly registering new versions with JuliaRegistrator. We get this error:
https://github.com/fverdugo/PartitionedArrays.jl/actions/runs/3938184637/jobs/6736578431#step:3:41
He have looked for solutions, but have failed to find one so far.
Have you ever seen this type of error? Do you know a solution?
Thanks!
e2307e0There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See JuliaRegistries/TagBot#242 (at least the comments from the last weeks). The only way I know to fix it is to try again later, but you can also just push the tag from your local repo (see e2307e0#commitcomment-96462022)