Skip to content

chore(sandbox): disable lightning and opencomputer providers - #428

Open
kisernl wants to merge 1 commit into
masterfrom
devin/1789391888-disable-lightning-opencomputer
Open

kisernl wants to merge 1 commit into
masterfrom
devin/1789391888-disable-lightning-opencomputer

Conversation

@kisernl

@kisernl kisernl commented Sep 14, 2026

Copy link
Copy Markdown
Collaborator

Summary

PR #414 commented lightning out of the sandbox workflow matrices, but benchmarks-daily builds its own matrix by importing the providers array from benchmarks/sandbox/providers.ts — so it kept generating sandbox and dax jobs for lightning.

This PR comments out the lightning and opencomputer entries (and their imports) in providers.ts, which stops benchmarks-daily from emitting jobs for them, and comments - opencomputer out of the three sandbox workflow matrices (sandbox-tti-benchmarks.yml, sandbox-dax-benchmarks.yml, sandbox-capabilities.yml) to match lightning's existing treatment — otherwise those matrix jobs would dispatch and fail on an unknown provider.

Left in place for easy re-enable: vault secret loading for both providers' env vars, the opencomputer key in DAX_RESOURCE_OPTIONS, the lightning sizing note in dax.bench.ts, and the OpenComputer display-name mapping in generate-svg.ts. benchmarks/scale/providers.ts (a separate list for the scale benchmark) is untouched.

Verified with pnpm typecheck.

Link to Devin session: https://app.devin.ai/sessions/e6251273110540a099ae686989b05e20
Open in Devin Desktop: https://app.devin.ai/desktop/session/e6251273110540a099ae686989b05e20?variant=devin
Requested by: @kisernl


Devin Review

Comment out both provider entries in benchmarks/sandbox/providers.ts so the
benchmarks-daily matrix builder (which imports the providers array directly)
stops generating jobs for them, and comment opencomputer out of the sandbox
workflow matrices to match lightning's existing treatment.

Co-Authored-By: Noah Kiser <noah@computesdk.com>
@devin-ai-integration

Copy link
Copy Markdown
Contributor

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment, CI, and merge conflict monitoring

@open-cla

open-cla Bot commented Sep 14, 2026

Copy link
Copy Markdown

Contributor License Agreement

All contributors are covered by a CLA.

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 1 potential issue.

1 flag not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)

Devin Review

Comment on lines +205 to +213
// {
// name: 'opencomputer',
// requiredEnvVars: ['OPENCOMPUTER_API_KEY', 'OPENCOMPUTER_API_URL'],
// createCompute: () => opencomputer({
// apiKey: process.env.OPENCOMPUTER_API_KEY!,
// apiUrl: process.env.OPENCOMPUTER_API_URL!,
// }),
// sandboxOptions: { timeout: 600_000 },
// },

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 OpenComputer benchmark command always fails

Running pnpm bench:opencomputer selects the removed opencomputer participant. resolveParticipants finds no participant and aborts the command.

Learn more

The package command remains exposed at bench:opencomputer, but tti.bench.ts now receives a participant list without opencomputer. Explicit participant selection produces an empty list, and resolveParticipants throws NoAvailableParticipantsError before executing tasks.

Example: A contributor runs pnpm bench:opencomputer using the repository's named command. The runner receives --provider opencomputer, selects zero participants, and exits instead of benchmarking OpenComputer.

Recommended fix: Remove or disable the bench:opencomputer package script alongside this provider entry. Restore both together when OpenComputer is re-enabled.

Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, though this matches an existing pattern in the repo: bench:railway (and bench:render, bench:just-bash) still exist even though those providers are commented out of providers.ts, so a bench:* script pointing at a disabled provider already fails the same way today.

Keeping bench:opencomputer makes re-enabling a single-file uncomment; happy to remove it if we want the disable to be more permanent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant