jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-22 03:16:52 -05:00
Code Issues Projects Releases Wiki Activity

Update bug fix about purging stale archived repositories (#20383)

Browse Source
This commit is contained in:
Kremlin
2021-07-19 04:40:25 -04:00
committed by GitHub
parent d2409c5de1
commit adc1b8ed6c
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
data/release-notes/enterprise-server/2-22/17.yml
View File

@@ -6,7 +6,7 @@ sections:
bugs:
- '`ghe-cluster-config-node-init` would fail during cluster setup if HTTP proxy is enabled.'
- Collectd would not resolve the forwarding destination hostname after the initial startup.
- The job that purged stale archived repositories could fail to make progress if some of those repositories were protected from deletion by legal holds.
- The job that purged stale deleted repositories could fail to make progress if some of those repositories were protected from deletion by legal holds.
- Git pushes could result in a 500 Internal Server Error during the user reconciliation process on instances using LDAP authentication mode.
- A significant number of 503 errors were logged every time a user visited a repository's `/settings` page if the dependency graph was not enabled.
changes:

2
data/release-notes/enterprise-server/3-0/11.yml
View File

@@ -9,7 +9,7 @@ sections:
- '`ghe-cluster-config-node-init` would fail during cluster setup if HTTP proxy is enabled.'
- Pre-receive hooks could encounter an error `Failed to resolve full path of the current executable` due to `/proc` not being mounted on the container.
- Collectd would not resolve the forwarding destination hostname after the initial startup.
- The job that purged stale archived repositories could fail to make progress if some of those repositories were protected from deletion by legal holds.
- The job that purged stale deleted repositories could fail to make progress if some of those repositories were protected from deletion by legal holds.
- Running `git nw-gc --pristine` would result in an error.
- Background jobs were being queued to the `spam` queue which were not being processed.
- The preferred merge method would be reset when retrying after a failed PR merge.

2
data/release-notes/enterprise-server/3-1/3.yml
View File

@@ -9,7 +9,7 @@ sections:
- '`ghe-cluster-config-node-init` would fail during cluster setup if HTTP proxy is enabled.'
- Pre-receive hooks could encounter an error `Failed to resolve full path of the current executable` due to `/proc` not being mounted on the container.
- Collectd would not resolve the forwarding destination hostname after the initial startup.
- The job that purged stale archived repositories could fail to make progress if some of those repositories were protected from deletion by legal holds.
- The job that purged stale deleted repositories could fail to make progress if some of those repositories were protected from deletion by legal holds.
- Background jobs were being queued to the `spam` queue which were not being processed.
- The preferred merge method would be reset when retrying after a failed PR merge.
- Git pushes could result in a 500 Internal Server Error during the user reconciliation process on instances using LDAP authentication mode.