After the roll to 3.1.10982, control's mesh user index never receives its first snapshot — every sign-in check times out
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 18/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- csharp, kubernetes
- Domain
- authentication, backend
Research direction
The log line comes from UserContextMiddleware, which falls back to the email local-part when the mesh user index is UNAVAILABLE. Start there, then find where the user index gets its first snapshot and where pod readiness is decided. Reproduce by starting a pod and checking when the index hydrates. Done means the index is loaded before readiness passes, or the pod stays NotReady until it is.
Written by the indexing model from the issue text.
Description
Observed on control.systemorph.com right after the CD self-update roll to 3.1.10982 (roll action Ops/Actions/selfupdate-roll-control-3-1-10982-579f0666, finished 06:44:53Z 2026-10-16, status Degraded). Signed-in users get "We could not check your account just now. This is a temporary problem on our side…".
All three new pods (memex-portal-deployment-6884494fc8-mhbt8, -b6rvj, -zpb4w) log, e.g. at 06:48:52Z (4 min after the roll):
UserContextMiddleware: mesh user index UNAVAILABLE for (the mesh user index has not received its first snapshot yet) — falling back to the email local-part for the partition key.
Read via a Logs action on control (Ops/Actions/iw-identity-timeouts-control-20261016-0700): 16 matching lines on control in the hour to 06:49Z; 0 on memex and memex-cloud over the same query and window.
Not established: whether the index hydrates eventually (and how long it takes), or never; which change between 3.1.10966 and 3.1.10982 is responsible; whether other instances show it after their next roll.
Expected: the user index receives its first snapshot within seconds of pod start, and readiness waits for it (a pod that cannot identify users should not be Ready).
- Dominant language
- C#
- Stars
- 12
- Forks
- 5
- Avg merge
- 5h 44m
- Merged PRs (30d)
- 968
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Systemorph/MeshWeaver
-
bug sev:M
Difficulty 4/5 3-5 days Newbie friendliness 12/100
Systemorph/MeshWeaver#6857 · 1 comment ·
Maintainers usually reply within 1 day
-
bug sev:M
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Systemorph/MeshWeaver#6856 ·
Maintainers usually reply within 1 day
-
bug sev:M
Difficulty 4/5 3-5 days Newbie friendliness 18/100
Systemorph/MeshWeaver#6853 · 3 comments ·
Maintainers usually reply within 1 day
-
bug cli-publish-failure feature:release-promotion sev:M
Difficulty 3/5 1-3 hours Newbie friendliness 12/100
Systemorph/MeshWeaver#6845 ·
Maintainers usually reply within 1 day
-
Query: a quoted multi-value exclusion -namespace:("a" OR "b") appears to keep only its first valueOpenbug sev:M
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Systemorph/MeshWeaver#6844 ·
Maintainers usually reply within 1 day
All issues in Systemorph/MeshWeaver
Similar issues
-
python triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/semantic-kernel#14615 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
vzeol/DeployCraft#125 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fboucher/2d6-dungeon-app#245 · 1 comment ·
Maintainers usually reply within 1 day
-
area: settings good first issue priority: p2 type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
AmineChr54/umbra#3 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day