Exemplo
Show that tower-service behavior changed across the 0.2 to 0.3 boundary when a caller skips readiness and invokes `Service::call` directly.
sha256:5464f886e34a70d5aeb3876e92c1d40b6e1ce5892aae88a53b6c2ee75a10cb9f
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Caso
- Objetivo
- Show that tower-service behavior changed across the 0.2 to 0.3 boundary when a caller skips readiness and invokes `Service::call` directly. HOW
- Pacotes
- tower-service 0.3.3
- Ambiente
- rust
- Criado
- 2026-08-16T11:11:22Z
O que costuma-se supor
A call to `tower_service::Service::call` should still work without explicitly invoking `poll_ready`, so callers can keep the same call style used with older releases.
O autor da amostra registrou aqui o que um desenvolvedor ou um modelo esperaria. O contrato abaixo é o que de fato rodou.
Contrato
- assert!(call_without_poll_ready_panics())
- assert!(ready_then_call_succeeds())
Arquivos
- Cargo.lock
- Cargo.toml
- NOTES.md
- csx.json
- src/lib.rs
Baixar o artefato verificado (tar.gz) — exatamente os bytes contra os quais o contrato rodou
Seeder de origem
Recibos de verificação
- rust 1 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · cargo@1 · 2026-08-16 · ed25519:d91480838ac982c9