提交处理延迟

2026年9月1日，大约在14:01至16:01 UTC期间，响应推送的更新出现延迟，暂时显示了过时的差异。推送后刷新差异的中位时间从正常水平约3秒上升至峰值时的超过2分钟，且在受影响最严重的75分钟内，超过14万个客户账户至少经历了一次延迟刷新。推送提交和开启拉取请求功能保持正常。此次事件是由于推送量急剧且集中激增，导致工作池和任务队列基础设施饱和所致。自动扩展未能按预期增加容量，因此积压未能自行清除。<br /><br />通过手动扩展受影响的工作池并增加推送处理容量，事件得到缓解。这使得系统能够处理积压，之后刷新时间恢复正常。为降低类似事件发生的可能性和影响，我们正在推送路径早期阶段增加配额和限流措施，以防单一集中负载源饱和共享容量；改进工作池自动扩展，以便自动增加容量；并改进后台任务处理的监控，以便在客户遇到拉取请求更新延迟之前，值班人员能收到警报。

原文On September 1, 2026, between approximately 14:01 and 16:01 UTC, updates in response to pushes were delayed, temporarily showing stale diffs. The median time to refresh a diff after a push rose from the normal level of about 3 seconds to over 2 minutes at the peak, and more than 140,000 customer accounts had at least one delayed refresh during the most affected 75 minutes. Pushing commits and opening pull requests continued to work normally. The incident was caused by a sharp, concentrated surge in push volume that saturated worker pools and job queueing infrastructure. Autoscaling did not increase capacity as intended, so the backlog did not clear on its own. <br /><br />The incident was mitigated by manually scaling the affected worker pools and increasing push-processing capacity. This allowed the system to process the backlog, after which refresh times returned to normal. To reduce the likelihood and impact of similar incidents, we are adding quotas and throttling earlier in the push path so a single concentrated source of load cannot saturate shared capacity, improving worker-pool autoscaling so capacity is added automatically, and improving monitors for background job processing so on-call is paged before customers experience delayed pull request updates.

拉取请求差异的更新时间已恢复到正常阈值。

原文Time to update pull request diffs have improved to normal thresholds.

PR视图中的差异可能延迟数分钟显示。我们正在调查并扩展资源。

原文Diffs in the PR view may be stale for several minutes. We are investigating and scaling up resources.

我们正在调查关于拉取请求性能下降的报告。

原文We are investigating reports of degraded performance for Pull Requests