agenda requests frequently fail due to rfcbot deserialization error

[ehuss]

I see this in the log messages fairly regularly:

2025-01-23T03:13:51.175570Z ERROR request{uuid=5d48bb64-23a8-4ade-ab7f-ec99ff3290ab}: triagebot: agenda request failed: Unable to get all fcps from rfcbot.
Caused by:
    0: error decoding response body: invalid value: integer `2490321401`, expected i32 at line 1 column 10826
    1: invalid value: integer `2490321401`, expected i32 at line 1 column 10826

I vaguely recall @Mark-Simulacrum doing some trickery to try to fix the i32 overflow on the rfcbot, but I don't remember the details. Does triagebot's type need to be changed to something else?

[apiraino]

I think that was me today using an unpatched version of the t-compiler triage agenda generator. There is indeed an issue (after what happened with the GH incremental ID) but I am usually using a locally patched version with the issue fixed.

I'm sorry I didn't yet get around pushing it here, I just need to do that.

@rustbot claim

[Mark-Simulacrum]

I think I fixed all of the api endpoints to return the right (u64) types from rfcbot - maybe I missed one? Or, actually, that error looks like the triagebot side is wrong - we should be expecting a u64, not i32.

@apiraino happy to tweak rfcbot further if I did miss something on that side.

[apiraino]

For my reference: I think this patch will fix more stuff but I need to look at it again before opening a PR here 🙂