Fix mutation optional access lint
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
This commit is contained in:
@@ -6834,5 +6834,7 @@ that the analyzer also rejects `.value()` after a preceding presence guard.
|
||||
Those paths now copy through `value_or()` after the guard, preserving the
|
||||
existing rejection behavior while avoiding unchecked optional access. Run 272
|
||||
passed all 68 regular CTests but failed analysis before PostgreSQL
|
||||
migration/tests; a fresh CI run is required to validate this repair and schema
|
||||
v29.
|
||||
migration/tests. Its network job also failed because the protocol test marked
|
||||
version 10 as future even though the v10 mutation codec now accepts it; the
|
||||
test now checks version 11 instead. The next full CI run must validate both
|
||||
repairs and schema v29.
|
||||
|
||||
Reference in New Issue
Block a user