pauljd/vectorcraft
1
0
Fork 0
mirror of https://github.com/storytold/vectorcraft.git synced 2026-11-10 10:02:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #5392 from storytold/fix/sec-mcp-busy-long-id

Browse Source 
MCP: busy replies don't repeat a long request id
This commit is contained in:
BFlat
2026-11-03 22:43:09 +07:00
committed by GitHub
parent 9a47e0bd9d 1806da580c
commit 450a60cc74
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
crates/mcp/src/intake.rs
+6 -1
View File
@@ -146,10 +146,15 @@ impl Shared {
fn long_running(&self, st: &State) -> Option<Value> {
let r = st.running.as_ref()?;
let secs = r.since.elapsed();
(secs >= self.busy_after).then(|| json!({"running": r.label, "requestId": r.key, "seconds": secs.as_secs()}))
// A long id isn't repeated: every busy reply would carry it twice.
let key = r.key.as_deref().filter(|k| k.len() <= MAX_ECHOED_ID);
(secs >= self.busy_after).then(|| json!({"running": r.label, "requestId": key, "seconds": secs.as_secs()}))
}
}
/// The longest running request id a busy reply repeats (as JSON, quotes included).
const MAX_ECHOED_ID: usize = 256;
/// The id of a request message: `Some` when `msg` is a JSON-RPC 2.0 request with a usable id.
fn request_id(msg: &Value) -> Option<&Value> {
let o = msg.as_object()?;