PoolRotater Wiki

Your guide to automatic osu! multiplayer

User Tools

Site Tools


updates:v6_7_23

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

updates:v6_7_23 [2026/10/06 00:48] – Document scheduled v6.7.23 results intermission and refresh dated rollout status wikiadminupdates:v6_7_23 [2026/10/06 01:39] (current) – Document deployed v6.7.22, v6.7.23 rollout and persistent monitoring-path correction wikiadmin
Line 1: Line 1:
 ====== v6.7.23: Results-screen intermission ====== ====== v6.7.23: Results-screen intermission ======
  
-**Scheduled, not live at the October 5, 2026, 17:47 PDT review.** This compatible room update follows successful activation of [[updates:v6_7_22|the pending supervisor upgrade]]. All four rooms currently run [[updates:v6_7_21|the maintenance bridge]].+**October 5, 2026, 18:38 PDT:** the shared supervisor is live on v6.7.22 with a five-second continuous empty-and-idle deployment wait. Rooms 1–3 are healthy and running v6.7.23; Room 4 is healthy on v6.7.22, waiting to update when empty. This is a dated observation, not a continuously updated deployment claim; see [[status:start|Live lobbies]] for current room versions.
  
 ===== What players will notice ===== ===== What players will notice =====
Line 31: Line 31:
 789 offline tests passed, including solo/all-player holds, the actual ''finished_play'' → ''idle'' event sequence, release when one player returns, spectators/referees, departures, unknown states and absence of API calls. The immutable release is compatible with v6.7.22, and all four rooms passed the owner-approved duration guard. 789 offline tests passed, including solo/all-player holds, the actual ''finished_play'' → ''idle'' event sequence, release when one player returns, spectators/referees, departures, unknown states and absence of API calls. The immutable release is compatible with v6.7.22, and all four rooms passed the owner-approved duration guard.
  
-A durable follow-on job waits for the v6.7.22 maintenance job to complete, a fresh v6.7.22 supervisor status and all four healthy v6.7.22 workers without pending targets. Only then does it submit the guarded ordinary empty-safe v6.7.23 rollout. It does not force occupied rooms to close. A scheduled job or accepted deployment request is not evidence that a room already has this behavior.+The durable follow-on job submitted the guarded ordinary empty-safe rollout after successful v6.7.22 activation and healthy-worker checks. Actual worker observations confirm v6.7.23 in Rooms 1–3 at the dated review, while Room 4 remains queued until empty. Accepted deployment alone does not prove every room has updated; occupied rooms are not forced to close.
  
 Includes earlier cumulative Jump and supervisor work. Collection, the separate research candidate database and live map catalogs are unchanged by this patch. Includes earlier cumulative Jump and supervisor work. Collection, the separate research candidate database and live map catalogs are unchanged by this patch.
updates/v6_7_23.txt · Last modified: by wikiadmin

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki