chore: sync infra OpenAPI specs#485
Conversation
e2b-generated-code-auto-fixer
Bot
requested review from
Kraci,
ben-fornefeld,
drankou and
huv1k
as code owners
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d77cb56d48
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| @@ -4,1656 +4,1654 @@ | |||
| */ | |||
|
|
|||
| export interface paths { | |||
There was a problem hiding this comment.
The regenerated contracts are committed in openapi-typescript's default formatting here (4-space indentation, double quotes, semicolons), but biome.json enforces 2-space indentation, single quotes, and semicolons-as-needed, and these contract files are not ignored. In the inspected repo this will make bun run check/format:check report formatting changes for the regenerated contract files, so the sync should run the generated output through Biome before committing.
Useful? React with 👍 / 👎.
| memoryMB: components["schemas"]["MemoryMB"]; | ||
| diskSizeMB: components["schemas"]["DiskSizeMB"]; | ||
| /** @description Whether the sandbox ended more than the retention window ago, so its monitoring, events, and logs data is no longer available */ | ||
| retentionExpired: boolean; |
There was a problem hiding this comment.
This new required response field says whether monitoring, events, and logs are no longer available, but it is not propagated by mapApiSandboxRecordToModel, so the sandbox UI still infers retention from startedAt in the logs/monitoring flows. For a killed sandbox that ran longer than the retention window but ended recently, the API can return retentionExpired: false while the dashboard still treats empty log results as expired and may request an over-retention monitoring range; please expose this field on SandboxDetailsModel and use it instead of the startedAt heuristic.
Useful? React with 👍 / 👎.
1 participant
This PR syncs OpenAPI specs from e2b-dev/infra:
spec/openapi.infra.yamlspec/openapi.dashboard-api.yamlIt also regenerates dependent TypeScript API types and applies formatting/lint autofixes.
This PR was automatically created by the sync-infra-specs workflow.