具有拉入请求和问题的事件
在8月12日16:03至16:29 UTC期间,部分用户在查看拉取请求、议题和搜索结果时遇到了错误。在此期间,约1.9%的拉取请求和0.9%的议题请求失败。在一次数据库迁移过程中,两个索引被移除,而应用程序设置仍引用它们,导致受影响的请求失败。我们在迁移到达一个数据库分片后、在迁移推进到其余分片之前检测到了该问题。我们通过禁用这两项设置恢复了服务。我们正在加强数据库迁移和应用程序配置相关的保障措施,以防止类似的不匹配导致错误。
原文Between 16:03 and 16:29 UTC on August 12, some users encountered errors when viewing pull requests, issues, and search results. During this period, about 1.9% of Pull Request requests and 0.9% of Issues requests failed. During a database migration, two indexes were removed while application settings still referenced them, causing affected requests to fail. We detected the issue after the migration reached one database shard and before it progressed to the remaining shards. We restored service by disabling both settings. We are improving safeguards around database migrations and application configuration to prevent similar mismatches from causing errors.
我们已定位影响GitHub.com上Pull Requests、Issues和Search的错误源头,并已应用缓解措施。一个数据库索引提示引用了最近迁移中已移除的索引,导致部分用户查询失败。我们已禁用该问题配置,并观察到受影响服务正在恢复。我们持续监控以确认完全解决。
原文We identified the source of errors affecting Pull Requests, Issues, and Search on GitHub.com and have applied a mitigation. A database index hint was referencing an index that had been removed by a recent migration, causing query failures for some users. We disabled the problematic configuration and are seeing recovery across affected services. We are continuing to monitor to confirm full resolution.
影响Issues和Pull Requests的性能降级问题已得到缓解。我们正在监控以确保稳定性。
原文The degradation affecting Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.
我们正在调查影响GitHub.com上Pull Requests和Issues的错误报告。部分用户在加载pull request和issue页面时可能会遇到500错误。我们的工程团队正在积极调查根本原因,该问题似乎与数据库基础设施故障有关。一旦获得更多信息,我们将及时更新进展。
原文We are investigating reports of errors affecting Pull Requests and Issues on GitHub.com. Some users may encounter 500 errors when loading pull request and issue pages. Our engineering teams are actively investigating the root cause, which appears to be related to a database infrastructure issue. We will provide an update as soon as we have more information.
我们正在调查关于Issues和Pull Requests性能下降的报告。
原文We are investigating reports of degraded performance for Issues and Pull Requests
关于这些数据
事件从哪来?
全部来自各厂商官方状态页的公开接口,由本站每 5 分钟同步一次,保留最近 90 天。事件标题、时间、影响级别与更新记录均为官方原文,本站不做改写;点详情页底部的链接可回到厂商原始记录核对。
为什么有的服务查不到历史?
本页只收录对外提供官方状态页的服务。没有公开状态页的厂商(多数国产大模型属于此类)无法取得可信数据,本站不做自建拨测去猜,因此也不会出现在状态总览里。
持续时长怎么算?
按官方标注的开始时间到恢复时间计算;尚未恢复的事件按「至今」计算并标为进行中。跨天的事件在状态条上会覆盖它经过的每一天。