Uh oh!
There was an error while loading. Please reload this page.
implementing SEP-2549 TTL for List Results - #889
Conversation
a6151ad to
f8edae7Compare
alexhancock
left a comment
There was a problem hiding this comment.
Pre-approving so you can merge when the below is addressed!
The cache hints (ttlMs and cacheScope) are written to _meta, but the spec defines them as first-class result fields
Per SEP-2549, ttlMs and cacheScope are properties on the result itself (CacheableResult), so the wire shape is { "tools": [...], "ttlMs": 300000, "cacheScope": "public" } (example, L112) — not nested under _meta
Fix list:
- Top-level fields: make
ttl_ms/cache_scopereal#[serde(rename = "ttlMs"/"cacheScope")]fields on the result struct instead ofmeta.insert(...). resources/read: the same meta.insert pattern is duplicated below in ReadResourceResult, writing into each ResourceContents. The spec attaches the hints to ReadResourceResult itself, so they should live on the result (otherwise they vanish when contents is empty). Scope guidance L90.- ttlMs rules: u64 correctly blocks negatives on the producing side 👍, but there's no read-side normalization (absent → 0, negative → 0, server MUST emit >= 0). Rules L39-43.
Uh oh!
There was an error while loading. Please reload this page.
jamadeo
left a comment
There was a problem hiding this comment.
I think this does the right thing over the wire, but wouldn't it be a good bit simpler if added on the top level struct itself?
Uh oh!
There was an error while loading. Please reload this page.
ok - this is a breaking change now (well needs new semver version) - not sure of next steps @DaleSeo to get CI happy in that (deliberate) case? |
Uh oh!
There was an error while loading. Please reload this page.
DaleSeo
commented
Jun 18, 2026
The semver CI failure is expected for this PR because it adds public fields. Could you just mark this as a breaking change with a |
alexhancock
commented
Jul 3, 2026
@michaelneale I think with a rebase and #889 (comment) this would be good to go? Would be good to get it in |
DaleSeo
commented
Jul 10, 2026
Hey @michaelneale, do you have any updates? I'm afraid this could block other spec work. |
169b43d to
e96796fComparee96796f to
1e432d0CompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
1e432d0 to
48e4704CompareUh oh!
There was an error while loading. Please reload this page.
implementing #875
(assisted by mic and goose)