|
64 | 64 | ] |
65 | 65 | }, |
66 | 66 | "checks": [ |
67 | | - "client RESULT pass == 10", |
68 | | - "client RESULT fail == 2", |
| 67 | + "client RESULT pass == 12", |
| 68 | + "client RESULT fail == 0", |
69 | 69 | "client RESULT prompt1_updates >= 2", |
70 | 70 | "client RESULT prompt2_updates >= 2", |
71 | 71 | "client RESULT prompt3_permission_updates >= 2", |
72 | 72 | "client RESULT prompt_after_load_updates >= 2" |
73 | | - ], |
74 | | - "expectedFailures": [ |
75 | | - { |
76 | | - "process": "client", |
77 | | - "step": "reconnect-session/load", |
78 | | - "contains": "404", |
79 | | - "reason": "RFD contradiction, not a Java bug: the Java client follows the reconnect diagram and pre-opens the session GET before session/load on the new connection; the Python server follows the rule that an Acp-Session-Id unknown to the connection is a 404", |
80 | | - "see": "RFD streamable-http-websocket-transport: the reconnect sequence opens the session GET before session/load, while the server rules say an unknown Acp-Session-Id returns 404; the Python server follows the latter" |
81 | | - }, |
82 | | - { |
83 | | - "process": "client", |
84 | | - "step": "reconnect-prompt", |
85 | | - "contains": "404", |
86 | | - "reason": "follows from reconnect-session/load: the session was never attached to the new connection", |
87 | | - "see": "RFD streamable-http-websocket-transport: the reconnect sequence opens the session GET before session/load, while the server rules say an unknown Acp-Session-Id returns 404; the Python server follows the latter" |
88 | | - } |
89 | 73 | ] |
90 | 74 | }, |
91 | | - "comment": "Reconnect-then-load is an EXPECTED failure (RFD contradiction, not a Java bug); if the Python server starts accepting it the scenario fails so the expectation gets updated." |
| 75 | + "comment": "Reconnect-then-load passes against the Python server since fe7567a: when a server answers the session-stream GET with 404 (as Python does for a session unknown to the connection), the Java client posts session/load on the connection without Acp-Session-Id. The RFD still contradicts itself here (reconnect diagram vs the unknown-session 404 rule)." |
92 | 76 | } |
0 commit comments