cat / bindws
clone

nostr relays on demand at <name>.bind.ws: claim one with your key, pay in zaps past the free allowance

ci: forge attest runs typecheck and tests on your machine for src.rest

cat committed 3d57e2d
.forge/ci runs npm ci, npm run typecheck and npm test, the same steps as
the test workflow. forge attest runs it in a clean worktree of each commit
and signs the result into refs/notes/ci; forge push sends it with the branch.
commit
3d57e2d48262f9697cec1036514d606dc0835f50
parent
5d3126716ae5b6bf01d46cdf14fceb05244445e0
author
cat <admin@dev.site>
ci
✓ passed in 35s, signed by cat
ci attestation 
forge-attestation 1
type ci
commit 3d57e2d48262f9697cec1036514d606dc0835f50
tree 5c5e054f2ef1485efeaea395473fbdbc411462c4
script .forge/ci 2c66d8116e8abf760a2437e358500cdb9b0b4225
result pass
exit 0
started 2026-10-17T22:57:52Z
duration 35s
runner (not shown here; refs/notes/ci has it)
system Darwin 25.5.0 arm64
env host
log sha256:bdc98f2b151147789593fbd764a38ae6ebbe6f57445f3eee7129d726d3842fd3 1523 lines
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|uncaught exception; source = Uncaught (in promise); stack = Error: internal error; reference = 693pnk0jbu30jvt2n6gd7iaq
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|uncaught exception; source = Uncaught (in promise); stack = Error: internal error; reference = ipqa2jpeuv236h1b4s2cdi7m
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|uncaught exception; source = Uncaught (in promise); stack = Error: internal error; reference = dpa9tmkfngbcd0ijhsa7sdf3
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|uncaught exception; source = Uncaught (in promise); stack = Error: internal error; reference = hvarlbn12u1a3qd5ioc4r6pk
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|uncaught exception; source = Uncaught (in promise); stack = Error: internal error; reference = akuqpbkmj9s4cuosdqlaonsk
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|uncaught exception; source = Uncaught (in promise); stack = Error: internal error; reference = dgubosv78qfe1hnal8ed43ke
|console warning; message = Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/nostr+json+rpc". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
|
| Test Files  62 passed (62)
|      Tests  353 passed (353)
|   Start at  16:58:02
|   Duration  24.53s (transform 18.08s, setup 0ms, import 189.24s, tests 119.21s, environment 3ms)
|

Signature: good, cat

1 file changed, +7 -0
A.forge/ci7+++++++
A .forge/ci +7 -0
@@ -0,0 +1,7 @@
1+#!/bin/sh2+# CI for src.rest: npm run typecheck (tsc and the generated-file checks) and3+# npm test (unit and Durable Object tests in workerd), as the test workflow runs.4+set -eu5+npm ci --no-audit --no-fund6+npm run typecheck7+npm test