Skip to content

add support for pushing sandboxes#72

Open
Nathan Selvidge (nselvidge) wants to merge 3 commits intomainfrom
nate/sandbox-push
Open

add support for pushing sandboxes#72
Nathan Selvidge (nselvidge) wants to merge 3 commits intomainfrom
nate/sandbox-push

Conversation

@nselvidge
Copy link
Copy Markdown
Contributor

@nselvidge Nathan Selvidge (nselvidge) commented Mar 13, 2026

Adds the ability to push sandboxes using the bt function push command. pushes lambda sandboxes for each language.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 13, 2026

Latest downloadable build artifacts for this PR commit cd3ce948a0a6:

Available artifact names
  • ``artifacts-build-global
  • ``artifacts-build-local-x86_64-apple-darwin
  • ``artifacts-build-local-x86_64-pc-windows-msvc
  • ``artifacts-build-local-aarch64-apple-darwin
  • ``artifacts-build-local-x86_64-unknown-linux-musl
  • ``artifacts-build-local-x86_64-unknown-linux-gnu
  • ``artifacts-build-local-aarch64-unknown-linux-musl
  • ``artifacts-build-local-aarch64-unknown-linux-gnu
  • ``artifacts-plan-dist-manifest
  • ``cargo-dist-cache

@nselvidge Nathan Selvidge (nselvidge) force-pushed the nate/sandbox-push branch 2 times, most recently from 1ff2094 to 309441c Compare March 25, 2026 15:58
@nselvidge Nathan Selvidge (nselvidge) changed the base branch from functions-push-pull-command to main March 25, 2026 15:59
@nselvidge Nathan Selvidge (nselvidge) marked this pull request as ready for review March 27, 2026 18:06
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.

Not blocking I don't think but one small note related to eval parameters

Comment on lines +639 to +643
const serialized = toJsonValue(rawParams as JsonValue);
if (serialized !== undefined) {
evaluatorDefinition.parameters = serialized;
}
}
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.

Can we reuse the existing evaluator-parameter serialization flow from eval-runner.ts here, instead of the direct toJsonValue(rawParams) path? I think using the shared serializer covers some cases with Zod->JSON Schema conversion that help avoid malformed evaluator_definition.parameters for parameterized evals.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I tried extracting this into a new file, but the eval-runner doesn't play nice with local exports since it needs to run with multiple runner types in a way the functions-runner doesn't. I'm going to just copy the logic over from eval-runner. I'm a bit hesitant to move to a complex local file structure for these runners since they need to work in so many situations, but let me know if you think that's the wrong approach

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.

I'm a bit hesitant to move to a complex local file structure for these runners since they need to work in so many situations, but let me know if you think that's the wrong approach

Nope, totally agree with this.

@nselvidge Nathan Selvidge (nselvidge) force-pushed the nate/sandbox-push branch 3 times, most recently from 92bb115 to ba3ddf0 Compare April 10, 2026 20:48
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.

2 participants