 |
Scenarios and Lost Vale data look like they are working again now. The remaining issue I can still reproduce is with the public GraphQL `kills` connection. Checked at: 2026-05-17 09:50 UTC Endpoint: https://production-api.waremu.com/graphql Current observed behavior: - `scenarios` and Lost Vale are not the stale-feed issue anymore. - `kills(first: ...)` still returns old kill rows from 2026-05-15 instead of current 2026-05-17 rows. - Filtering `kills` for rows on/after 2026-05-16 returns an empty list. - Some valid `kills` pagination/filter queries also hit backend MySQL errors. I saw "The Command Timeout expired before the operation completed." Earlier in the same check, `kills(last: 5)` returned "Packet received out-of-order. Expected 1; got 2." Reproduction 1 - latest kills are stale curl -sS --get \ --data-urlencode 'query=query ($first: Int) { kills(first: $first, includeAssists: false) { nodes { id time position { zone { id name } } scenario { id name } } } }' \ --data-urlencode 'variables={"first":3}' \ https://production-api.waremu.com/graphql Observed output excerpt: { "data": { "kills": { "nodes": [ { "id": "65009644", "time": "2026-05-15T00:43:49.8554Z", "position": { "zone": { "id": "236", "name": "Lost Temple of Isha" } }, "scenario": { "id": "2203", "name": "Lost Temple of Isha" } } ] } } } Reproduction 2 - fresh kill window is empty curl -sS --get \ --data-urlencode 'query=query ($first: Int, $where: KillFilterInput) { kills(first: $first, where: $where, includeAssists: false) { nodes { id time } } }' \ --data-urlencode 'variables={"first":1,"where":{"time":{"gte":"2026-05-16T00:00:00Z"}}}' \ https://production-api.waremu.com/graphql Observed output: { "data": { "kills": { "nodes": [] } } } Reproduction 3 - valid kills pagination can throw backend errors curl -sS --get \ --data-urlencode 'query=query ($last: Int) { kills(last: $last, includeAssists: false) { nodes { id time } } }' \ --data-urlencode 'variables={"last":1}' \ https://production-api.waremu.com/graphql Observed output excerpt: { "errors": [ { "message": "Unexpected Execution Error", "path": [ "kills" ], "extensions": { "exception": { "message": "The Command Timeout expired before the operation completed." } } } ], "data": { "kills": null } } Expected behavior: `kills(first: ...)` or a time-filtered `kills(where: { time: { gte: ... } })` should return recent kill rows when there has been live kill activity. Valid kill pagination should also not fail with MySQL connector / command timeout errors. |
- Anonymous
