ta
TanStack
GitHub
ai
Workspace
GitHub
CI Pipeline Executions
Filtered
Runs
Demo
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
Overview
⌘K
ai
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Succeeded
feat/upstash-box-sandbox-provider
baacd7ef fix(ai-sandbox-upstash-box): validate env names, stop swallowing real errors Address the fourth review pass. - withEnv() interpolated env NAMES straight into `export <key>=...`. Values were quoted, keys were not, so a caller-supplied key containing `;` injected a command ahead of the requested one. Both env paths now reject anything that is not a valid shell identifier. - exists() reported every failure as "absent", so a 401 or a transport error made a caller believe a file it could not read was missing. Only 404 means absent now, matching resume() and destroy(). - A stream that overflowed while the exec.session handshake was still settling killed nothing, because there was no session yet, and nothing rechecked once there was. The streams closed while the process kept running. - spawn() signalled the process on an abort raised during the handshake but still returned a handle for the cancelled operation. It now rejects, as the pre-flight path does. - The overflow test bounded stdout at 9 MiB, which would pass a regression past the declared 8 MiB cap. It measures the payload apart from the truncation notice and asserts the cap itself. The 404 predicate lived in both handle.ts and provider.ts; it is now one function so the two cannot drift.
by alitariksahin
a
Previous
Next