Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Launching dev container and pnpm start <args> yields ambiguous error #2030

Open
cdaringe opened this issue Jan 23, 2024 · 4 comments
Open

Launching dev container and pnpm start <args> yields ambiguous error #2030

cdaringe opened this issue Jan 23, 2024 · 4 comments
Assignees
Labels
priority-4-low Low priority, unlikely to be done unless it becomes important to more people status:ready Ready to start implementation type:bug Bug fix of existing functionality

Comments

@cdaringe
Copy link
Contributor

problem

in the vscode devcontainer, post pnpm install, on run of install tool <any-tool-name> the following error occurs

$ pnpm start install tool java

> [email protected] start /workspaces/base
> tsx src/cli/index.ts "install" "tool" "java"

Ambiguous Syntax Error: Cannot find which to pick amongst the following alternatives:

  0. /opt/containerbase/tools/node/20.11.0/bin/node /workspaces/base/src/cli/index.ts install tool [-d,--dry-run] <name> [version]
  1. /opt/containerbase/tools/node/20.11.0/bin/node /workspaces/base/src/cli/index.ts install tool [-d,--dry-run] <name> [version]
@cdaringe
Copy link
Contributor Author

cdaringe commented Jan 23, 2024

looks like:

  cli.register(InstallGemCommand);
  cli.register(InstallNpmCommand);

redundantly register InstallToolCommand, which creates dupe entries. commenting those two out restores execution to working order

@rarkins
Copy link
Member

rarkins commented Jan 23, 2024

Why are you running that command? Eg is it documented that you need to run it?

@cdaringe
Copy link
Contributor Author

Why are you running that command?

debugging

Eg is it documented that you need to run it?

just common JS idioms for running stuff, and it was indeed present. Thus, I inferred it is present for running 🙂

I was able to use it to successfully debug my failure and get to a functional state

@viceice viceice added type:bug Bug fix of existing functionality priority-4-low Low priority, unlikely to be done unless it becomes important to more people status:ready Ready to start implementation labels Jan 23, 2024
@viceice viceice self-assigned this Jan 23, 2024
@viceice
Copy link
Member

viceice commented Jan 23, 2024

will see if I can fix the start command, but with very low priority

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority-4-low Low priority, unlikely to be done unless it becomes important to more people status:ready Ready to start implementation type:bug Bug fix of existing functionality
Projects
None yet
Development

No branches or pull requests

3 participants