### Author:  [@ctkelley](https://discourse.julialang.org/u/ctkelley)
#### Post date: [May 11, 2022, 9:27am UTC](https://discourse.julialang.org/t/slow-tagbot-no-repo-update-after-16-hours/80870/1 "2022-05-11T09:27:15Z")
I registered a new release of SIAMFANLEquations.jl yesterday. Things seem fine at
[https://github.com/JuliaRegistries/General/pull/60018](https://github.com/JuliaRegistries/General/pull/60018)
and the new version is in the registry,
but my github repo does not show the new release after 16 hours.
Is there a problem with TagBot or did something go wrong that I missed?
This worked fine for the last release in early April.
My tagbot.yml is
```julia
name: TagBot
on:
issue_comment:
types:
- created
workflow_dispatch:
jobs:
TagBot:
if: github.event_name == 'workflow_dispatch' || github.actor == 'JuliaTagBot'
runs-on: ubuntu-latest
steps:
- uses: JuliaRegistries/TagBot@v1
with:
token: ${{ secrets.GITHUB_TOKEN }}
ssh: ${{ secrets.DOCUMENTER_KEY }}
```
---
### Author:  [@giordano](https://discourse.julialang.org/u/giordano)
#### Post date: [May 11, 2022, 9:38am UTC](https://discourse.julialang.org/t/slow-tagbot-no-repo-update-after-16-hours/80870/2 "2022-05-11T09:38:57Z")
[https://github.com/ctkelley/SIAMFANLEquations.jl/runs/6375100102?check\_suite\_focus=true](https://github.com/ctkelley/SIAMFANLEquations.jl/runs/6375100102?check_suite_focus=true)
> Warning: GitHub returned a 5xx error code
Sounds like a GitHub issue. If you go to [TagBot · Workflow runs · ctkelley/SIAMFANLEquations.jl · GitHub](https://github.com/ctkelley/SIAMFANLEquations.jl/actions/workflows/tagbot.yml) you should have a button to manually trigger the workflow again.
---
### Author:  [@ctkelley](https://discourse.julialang.org/u/ctkelley)
#### Post date: [May 11, 2022, 9:55am UTC](https://discourse.julialang.org/t/slow-tagbot-no-repo-update-after-16-hours/80870/3 "2022-05-11T09:55:41Z")
Thanks, I hit the button, got a green check after a minute or so, and got the 5xx message
```julia
Annotations
1 warning
TagBot
GitHub returned a 5xx error code
```
The tag did not happen.
Should I manually tag the release or wait awhile and try again?
---
### Author:  [@giordano](https://discourse.julialang.org/u/giordano)
#### Post date: [May 11, 2022, 10:09am UTC](https://discourse.julialang.org/t/slow-tagbot-no-repo-update-after-16-hours/80870/4 "2022-05-11T10:09:34Z")
CC: @christopher-dG
---
### Author:  [@ctkelley](https://discourse.julialang.org/u/ctkelley)
#### Post date: [May 11, 2022, 12:30pm UTC](https://discourse.julialang.org/t/slow-tagbot-no-repo-update-after-16-hours/80870/5 "2022-05-11T12:30:10Z")
It gets stranger. I just got an email from TagBot telling me that it expected to see a tag and did not.
```julia
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
```
I found the logs and the problem is still there. The logs say
```julia
Run JuliaRegistries/TagBot@v1
39
/usr/bin/docker run --name ghcriojuliaregistriestagbot1141_a8f95d --label 08450d --workdir /github/workspace --rm -e INPUT_TOKEN -e INPUT_SSH -e INPUT_REGISTRY -e INPUT_GITHUB -e INPUT_GITHUB_API -e INPUT_BRANCHES -e INPUT_DISPATCH -e INPUT_DISPATCH_DELAY -e INPUT_LOOKBACK -e INPUT_SSH_PASSWORD -e INPUT_GPG -e INPUT_GPG_PASSWORD -e INPUT_REGISTRY_SSH -e INPUT_DRAFT -e INPUT_USER -e INPUT_EMAIL -e INPUT_BRANCH -e INPUT_CHANGELOG -e INPUT_CHANGELOG_IGNORE -e HOME -e GITHUB_JOB -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_REPOSITORY_OWNER -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RETENTION_DAYS -e GITHUB_RUN_ATTEMPT -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_SERVER_URL -e GITHUB_API_URL -e GITHUB_GRAPHQL_URL -e GITHUB_REF_NAME -e GITHUB_REF_PROTECTED -e GITHUB_REF_TYPE -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e GITHUB_ACTION_REPOSITORY -e GITHUB_ACTION_REF -e GITHUB_PATH -e GITHUB_ENV -e GITHUB_STEP_SUMMARY -e RUNNER_OS -e RUNNER_ARCH -e RUNNER_NAME -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e ACTIONS_CACHE_URL -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/SIAMFANLEquations.jl/SIAMFANLEquations.jl":"/github/workspace" ghcr.io/juliaregistries/tagbot:1.14.1
40
Warning: GitHub returned a 5xx error code
41
Traceback (most recent call last):
42
File "/root/tagbot/action/ __main__.py", line 74, in
43
versions = repo.new_versions()
44
File "/root/tagbot/action/repo.py", line 432, in new_versions
45
return self._filter_map_versions(versions)
46
File "/root/tagbot/action/repo.py", line 271, in _filter_map_versions
47
expected = self._commit_sha_from_registry_pr(version, tree)
48
File "/root/tagbot/action/repo.py", line 205, in _commit_sha_from_registry_pr
49
pr = self._registry_pr(version)
50
File "/root/tagbot/action/repo.py", line 196, in _registry_pr
51
for pr in prs:
52
File "/usr/local/lib/python3.8/site-packages/github/PaginatedList.py", line 56, in __iter__
53
newElements = self._grow()
54
File "/usr/local/lib/python3.8/site-packages/github/PaginatedList.py", line 67, in _grow
55
newElements = self._fetchNextPage()
56
File "/usr/local/lib/python3.8/site-packages/github/PaginatedList.py", line 199, in _fetchNextPage
57
headers, data = self.__requester.requestJsonAndCheck(
58
File "/usr/local/lib/python3.8/site-packages/github/Requester.py", line 315, in requestJsonAndCheck
59
return self.__check(
60
File "/usr/local/lib/python3.8/site-packages/github/Requester.py", line 340, in __check
61
raise self.__createException(status, responseHeaders, output)
62
github.GithubException.GithubException: 502 {"message": "Server Error"}
63
Complete job
```
---
### Author:  [@ctkelley](https://discourse.julialang.org/u/ctkelley)
#### Post date: [May 12, 2022, 8:37am UTC](https://discourse.julialang.org/t/slow-tagbot-no-repo-update-after-16-hours/80870/6 "2022-05-12T08:37:10Z")
The emails from TagBot were increasing in frequency to every four hours. I just gave up and pushed the new release manually so (I hope) TagBot will be happy and Pkg will be able to find the new release.
---
### Author:  [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)
#### Post date: [May 12, 2022, 8:49am UTC](https://discourse.julialang.org/t/slow-tagbot-no-repo-update-after-16-hours/80870/7 "2022-05-12T08:49:49Z")
> [@ctkelley](#):
>
> Pkg will be able to find the new release.
That’s unrelated. TagBot is completely optional and it not working in no way impacts the usage of your package.
---
### Author:  [@ctkelley](https://discourse.julialang.org/u/ctkelley)
#### Post date: [May 12, 2022, 8:53am UTC](https://discourse.julialang.org/t/slow-tagbot-no-repo-update-after-16-hours/80870/8 "2022-05-12T08:53:11Z")
OK. Pkg seemed to be doing the right things on my computers and I did not know that my tagging the repo was optional.
Thanks,
---
### Author:  [@giordano](https://discourse.julialang.org/u/giordano)
#### Post date: [May 12, 2022, 9:53am UTC](https://discourse.julialang.org/t/slow-tagbot-no-repo-update-after-16-hours/80870/9 "2022-05-12T09:53:24Z")
> [@ctkelley](#):
>
> The emails from TagBot were increasing in frequency to every four hours.
You can also disable email notifications for failed workflows in [your GitHub settings](https://github.com/settings/notifications), they’re pretty annoying anyway, I disabled them after the first email I got when they started. See also [Configuring notifications - GitHub Docs](https://docs.github.com/en/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#github-actions-notification-options).
---
### Author:  [@longemen3000](https://discourse.julialang.org/u/longemen3000)
#### Post date: [May 14, 2022, 4:05am UTC](https://discourse.julialang.org/t/slow-tagbot-no-repo-update-after-16-hours/80870/10 "2022-05-14T04:05:21Z")
Same thing here (Clapeyron.jl 0.3.6)
---
### Author:  [@henry2004y](https://discourse.julialang.org/u/henry2004y)
#### Post date: [May 14, 2022, 6:10am UTC](https://discourse.julialang.org/t/slow-tagbot-no-repo-update-after-16-hours/80870/11 "2022-05-14T06:10:06Z")
I have been getting weird 5xx errors since two weeks ago, and got no luck in recovering the old nice automatic workflow for one of my packages last week, so I had to manually add tags and releases.
It happened again yesterday when I tried to register a new patch for another package, but somehow magically TagBot did its job for the 1st retriggering attempt today.
---
### Author:  [@longemen3000](https://discourse.julialang.org/u/longemen3000)
#### Post date: [May 15, 2022, 4:24am UTC](https://discourse.julialang.org/t/slow-tagbot-no-repo-update-after-16-hours/80870/12 "2022-05-15T04:24:47Z")
what is weirder is that TagBot doesn’t appear as failed, so a branch catching the error seems to be missing. i opened an issue [github errors, but tagbot appears as successful · Issue #238 · JuliaRegistries/TagBot · GitHub](https://github.com/JuliaRegistries/TagBot/issues/238)
---
### Author:  [@emmt](https://discourse.julialang.org/u/emmt)
#### Post date: [June 1, 2022, 8:43am UTC](https://discourse.julialang.org/t/slow-tagbot-no-repo-update-after-16-hours/80870/13 "2022-06-01T08:43:59Z")
Same error (actually reported as a _warning_) for several of my repositories (e.g. [DataBags](https://github.com/emmt/DataBags.jl)). I tried to manually re-run the TagBot job but it stops almost immediately with status **Skipped** at `on: issue_comment`. Is there some guidelines to properly register a new version of a Julia package on GitHub?
---
### Author:  [@giordano](https://discourse.julialang.org/u/giordano)
#### Post date: [June 1, 2022, 9:00am UTC](https://discourse.julialang.org/t/slow-tagbot-no-repo-update-after-16-hours/80870/14 "2022-06-01T09:00:11Z")
Note that while having TagBot working again would be great (I hope @christopher-dG will be able to have a look at some point)
1. the package manager doesn’t care about git tags at all. The only thing which matters is the registry
2. you can create the git tag manually if you really want it
---
### Author:  [@longemen3000](https://discourse.julialang.org/u/longemen3000)
#### Post date: [June 1, 2022, 7:08pm UTC](https://discourse.julialang.org/t/slow-tagbot-no-repo-update-after-16-hours/80870/15 "2022-06-01T19:08:44Z")
I have to sat that this does not affect all repositories, so it is possible to check what is the common cause?. In my specific case, the repository that was updated via juliahub didn’t work, but the one using JuliaRegistrator does
---
### Author:  [@krcools](https://discourse.julialang.org/u/krcools)
#### Post date: [June 22, 2022, 2:47pm UTC](https://discourse.julialang.org/t/slow-tagbot-no-repo-update-after-16-hours/80870/16 "2022-06-22T14:47:30Z")
The LiftedMaps v0.4.0 release suffers from the same problem. Registered via Juliahub.
---
### Author:  [@digital\_carver](https://discourse.julialang.org/u/digital_carver)
#### Post date: [August 29, 2022, 1:18pm UTC](https://discourse.julialang.org/t/slow-tagbot-no-repo-update-after-16-hours/80870/17 "2022-08-29T13:18:43Z")
For anyone still experiencing this issue, it may be due to a permission change that Github implemented some time early May (credit to @mfiano for figuring this out). The default permission for `GITHUB_TOKEN` was changed from “read and write” to “read only”.
The TagBot [README](https://github.com/JuliaRegistries/TagBot#setup) and the [example.yml](https://github.com/JuliaRegistries/TagBot/blob/master/example.yml) show the way to restore the required permissions at the YAML file level. ([This comment](https://github.com/JuliaRegistries/CompatHelper.jl/issues/416#issue-1232165557) describes the issue and shows a way to fix it via Github UI, on a per-repository level.)
The YAML change just involves adding
```julia
permissions:
contents: write
```
to TagBot.yml