Skip to content

Update README.md#4

Merged
myhndl merged 1 commit into
masterfrom
fix-readme
Apr 4, 2019
Merged

Update README.md#4
myhndl merged 1 commit into
masterfrom
fix-readme

Conversation

@supernothing
Copy link
Copy Markdown
Contributor

No description provided.

@myhndl myhndl merged commit 63b397f into master Apr 4, 2019
@myhndl myhndl deleted the fix-readme branch April 4, 2019 18:53
sbneto added a commit that referenced this pull request May 27, 2026
…p + respx coverage

Bot review found one code cleanup and several spec drift / coverage gaps.

Code:
- refresh_engine_cache now uses resources.Engine.list(self) instead of
  building the descriptor inline. Engine._list_headers already returns
  {'Authorization': None}, so the builder produces the same wire shape.
  Brings the method in line with AGENTS.md §"When adding a new resource"
  and specs/02-resources.md.
- Canonical docstrings in aio/session.py rephrased to be transport-
  neutral ("AsyncClient on the async transport; Client on the sync
  transport"). Reads correctly from both the canonical and generated
  files.

Specs:
- specs/01-architecture.md: dropped the "PR #298" reference (this PR;
  rots after merge). Added a note linking HttpxResponseAdapter to the
  streaming-downloads follow-up in 99-open-questions.
- specs/04-testing.md: added an explicit note that _AsyncToSync is
  respx-only — the harness builds the AsyncClient outside any event
  loop and drives every call via asyncio.run, which doesn't survive a
  live-HTTP integration test (per-call event loop vs. pooled
  AsyncClient connections).
- specs/05-downstream-contract.md: documents two new entries under
  "Backward compatibility — what changes":
    * check_known_hosts now returns a generator on sync too (was a
      list in 3.x due to the polymorphic-return trick; the docstring
      already promised "Generator of IOC resources").
    * Downloads buffer the full body in memory before chunking
      (regression vs. requests-backed 3.x streaming).
- specs/99-open-questions.md: new entry "Streaming downloads —
  HttpxResponseAdapter fully buffers" with concrete refactor proposal
  (use client.stream + async-aware adapter); rewrote the "cassettes
  that need an e2e refresh" entry to document why the 24 stale
  cassettes can't be regenerated cleanly (hard-coded primary keys,
  order-coupled state, count assertions on shared resources, missing
  fixtures, eventual-consistency assertions, surviving server bugs).

Tests:
- Added respx test test_async_report_template_logo_delete pinning the
  two-step flow (GET template → DELETE /reports/templates/logo?id=...).
  Closes the gap the bot flagged: the upload + download paths already
  had respx coverage; the delete path was VCR-only.

VCR cassettes:
- Round-2 re-record pass: deleted all cassettes, re-ran against the
  live e2e. 23 cassettes regenerated cleanly under the new transport
  + the _input_json snapshot fix. 24 stay pinned to their prior
  recordings — the corresponding tests aren't hermetic (hard-coded
  IDs, order-coupled state, etc.). See specs/99-open-questions.md
  for the full breakdown.

Sync mirrors regenerated; all 120 tests pass.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants