![]() The pull request page could fail to load with a 500 Internal Server Error if a reviewer is no longer a member of the GitHub Enterprise environment.Migrations with ghe-migrator could fail to complete trying to add the same label to an issue.hookshot logs weren't purged properly in Elasticsearch and could consume large amounts of disk space.ghe-config-check would hang if run without any arguments.Using Safari, administrators were unable to schedule a future hotpatch upgrade from the Management Console due to an incompatible date parse.Messages sent from the email service hook failed when the upstream SMTP server didn’t accept the plain authentication method.Replication could fail due to stale or duplicate entries to the primary in a replica's /etc/hosts.This type of replication failure is now reported in ghe-repl-status. Repository replication records may be created inconsistently, resulting in unreported replication failures.Upgrades could fail with Connection timed out if the hookshot service was unable to run migrations due to a firewall update that ran out of order.Webhooks could fail to be delivered if the compressed payload was greater than 1 MB.GitHub Enterprise API responses would not be compressed when requested with gzip encoding.ghe-repl-setup allowed re-adding the same node as a replica. ![]() CRITICAL: A file path traversal vulnerability in the jekyll-remote-theme gem of GitHub Pages could allow users to display the content of local files. ![]() The 2.14 series release notes contain important changes in this release series.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |