fix(epic3): сделать ATDD отмены чувствительным к регрессии и покрыть bounds токена в обеих revision (Story 3.4, FR-14)
- CANCEL_GRACE_MS 1200 -> 2500 (> LONG_HOLD_MS) и const-assert на этот порядок: при незавершённой отмене вызов успевает завершиться и записать исход внутри окна проверки, поэтому тест доказывает остановку, а не только «ещё не готово». - malformed/oversized/empty/object/array token теперь проверяются и в modern revision, не только в legacy (обе читают одно поле RequestMetaObject). - комментарий cancelled_response приведён к фактическому поведению: у остановленного вызова строки Invocation History нет вообще.
This commit is contained in:
1 parent
862cde8559
commit
f613250fd3
2 files changed
+53
-38
No files matched your search
@@ -458,8 +458,9 @@ async fn call_future(
|
||||
|
||||
/// A cancelled call is not answered: the pinned rule for a cancelled request is that no further
|
||||
/// message is sent for it, and the client that cancelled it ignores a late response anyway. Nothing
|
||||
/// here claims that an outbound side effect did or did not happen — that statement belongs to the
|
||||
/// Invocation History entry of the call, which records the cancellation as outcome-unknown.
|
||||
/// here claims that an outbound side effect did or did not happen — and nothing else claims the
|
||||
/// opposite either: the call is stopped before its terminal outcome, so its Invocation History holds
|
||||
/// no row for this call at all (see the module docs for why there is no invented cancellation code).
|
||||
fn cancelled_response() -> Response {
|
||||
StatusCode::OK.into_response()
|
||||
}
|
||||
|
||||
Reference in new issue
Block a user