chore(transport): drop the CRAFTER_DEBUG_NETWORK hook
The transport needed Crafter.Network's callback API, which lived on an unpushed branch, so project.cpp took Network from whatever project.cpp $CRAFTER_DEBUG_NETWORK named. That API and the ~ClientQUIC fix are on Network's master now (79a2f12), so the hook goes: Network comes from forgejo, unpinned, or from ../Crafter.Network with --local, as before. The notes and the README stop telling people to set it, and say which Network the transport needs. Every test passes with Network cloned from forgejo, and the example builds and is driven end to end that way. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
4a0d911e69
commit
653813e1e3
4 changed files with 6 additions and 10 deletions
|
|
@ -324,7 +324,7 @@ cd examples/Basic && crafter-build --debug-api -r
|
|||
- **Library and core tests** run in-process, against a `Session` built with `listen = false` and a fake transport.
|
||||
- **`ShouldRunClientCommands`** runs the real client against a real session that way.
|
||||
- **`ShouldServeOverQuic`** runs a listening session and drives it over loopback with the client's own QUIC transport. It covers discovery, calls, `log --follow`, wrong tokens, oversized requests, parallel requests, and shutdown with a client connected.
|
||||
- **Crafter.Network** comes from forgejo, or from `../Crafter.Network` with `--local`. To build against another checkout, a worktree say, set `CRAFTER_DEBUG_NETWORK` to its `project.cpp`.
|
||||
- **Crafter.Network** comes from forgejo, or from `../Crafter.Network` with `--local`.
|
||||
- **`AGENTS.template.md`** has the conventions.
|
||||
|
||||
Licensed LGPL-3.0-only; the examples are MIT.
|
||||
|
|
|
|||
Loading…
Reference in a new issue