fix: set default-run so Render's start command resolves - #202
Merged
Conversation
The workspace now has 3 binaries (octo-server, octo-migrate-keys, backfill-operation-index) with no root package, so a bare 'cargo run' at the workspace root is ambiguous and errors instantly with 'could not determine which binary to run'. Render's start command is exactly that bare invocation. default-run in octo-server's [package] resolves it without needing to change Render's dashboard config.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Render's deploy build succeeded but the start step failed:
The workspace has three binary-producing members and no root package, so Render's start command (
cargo run --release, a bare invocation with no--bin) is ambiguous. Settingdefault-run = "octo-server"inbin/server/Cargo.toml's[package]resolves it — verified locally that a barecargo run --releaseat the workspace root now startsocto-serverinstead of erroring immediately.Test plan
cargo check --workspace --all-targets --locked— cleancargo run --releasefrom the workspace root now resolves toocto-serverand starts (previously errored instantly with the ambiguity message above)