Bug-report bundle: record buffs, speed frames and mount routing so a speed desync can be root-caused
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 18/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- go, typescript
- Área
- devtools, observability-sre
Línea de trabajo
The bundle is produced by the diagnostics code that writes state.json, movement.json and the network journal; start there and find where movementDiagnostics and the 0x376F speed frames are recorded. The request asks for buff slots, speed-frame history with mount routing via mountedOn, mount state, and a session-long effect add/remove log for 0xB419 and 0xB072-family frames. Done when a bundle captured during a desync shows the last applied speed frame, its routing, and the held buffs next to the server's values. Expect to need protocol knowledge, and check #3506 first.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem
Bug report BR-261114-1716-2195 (the speed scroll rubber-bands: the icon is gone, the VFX stays, the character goes fast then slow) cannot be root-caused from its diagnostics bundle.
What the bundle shows:
state.jsonmovementDiagnostics.recent[].after: the client ran at walk 40 / run 100 from 32 s into the session to the end, about 86 minutes.movement.jsonreceipts: the server timed paths at 50/s. Request 194 covered 131.9 units in 2638 ms.
What it does not show, and the root cause needs:
- Active effects on the client: the buff slots (skill id, token, state, remaining time) at capture.
- Speed history: every 0x376F the client applied, with its time, target gid, the entity it was applied to (player, or the mount it resolved through
mountedOn), and the walk/run values. - Mount state: the local player's
mountedOnat capture and when it last changed. - Effect add and remove history: 0xB419 / 0xB072-family frames with skill id and token, kept for the whole session rather than the 2-minute network window. The network journal covers only the last ~118 s, so a desync that started an hour earlier leaves no trace.
The server side of the same question is #3506 (the operator view now shows movementSpeeds and effects).
Done when
A report filed during a speed desync shows, from the bundle alone, the last speed frame the client applied, where it was routed, and which buffs the client held, compared with the server's speeds and effects.
- Lenguaje dominante
- Go
- Estrellas
- 97
- Forks
- 61
- Merge medio
- 4 h 14 min
- PR fusionados (30 d)
- 913
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de opensro-dev/opensro
-
area: client enhancement priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
opensro-dev/opensro#3681 ·
Los mantenedores suelen responder en 1 día
-
area: client bug priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
opensro-dev/opensro#3228 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Format one minified client file with dprint (ongoing: one file per PR)Posiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertoarea: client enhancement good first issue priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
opensro-dev/opensro#1 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area: server bug priority: medium
Dificultad 3/5 Medio día Aptitud para principiantes 55/100
opensro-dev/opensro#3687 ·
Los mantenedores suelen responder en 1 día
-
area: ops bug priority: high
Dificultad 4/5 3-5 días Aptitud para principiantes 32/100
opensro-dev/opensro#3685 ·
Los mantenedores suelen responder en 1 día
Todos los issues de opensro-dev/opensro
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
unbound-force/gaze#353 ·
Los mantenedores suelen responder en 1 día
-
bug cross-seed ready-for-human
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
OneBusAway/maglev#2102 ·
Los mantenedores suelen responder en 2 días
-
affects-8.5 component/session severity/moderate sig/transaction type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
Waiting start: the fixed 503 body says another instance holds the lease when that may not be soAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 70/100
Judgment-Pack/judgment-pack-gateway#474 ·
Los mantenedores suelen responder en 1 día