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

Use --package instead of pushing into other directories #2301

Open
heaths opened this issue Mar 7, 2025 · 1 comment
Open

Use --package instead of pushing into other directories #2301

heaths opened this issue Mar 7, 2025 · 1 comment
Assignees
Labels
EngSys This issue is impacting the engineering system.
Milestone

Comments

@heaths
Copy link
Member

heaths commented Mar 7, 2025

Increasingly I'm wasting time investigating with the wrong context because the command lines aren't always apparent e.g.,

cargo +1.80 test --all-targets --no-fail-fast
Command succeeded (00:00:00.3090105)






Testing package: 'typespec_client_core'

cargo +1.80 build --keep-going
Command succeeded (00:00:01.5288991)




cargo +1.80 test --doc --no-fail-fast
Command succeeded (00:00:08.9542606)

Glancing at this, which error was the package in?

If the command line included --package {crate} it'd be more obvious. It's not idiomatic to pushd into package directories when you're in a workspace and just makes things more complicated.

@heaths heaths added the EngSys This issue is impacting the engineering system. label Mar 7, 2025
@heaths heaths added this to the 2025-04 milestone Mar 7, 2025
@github-project-automation github-project-automation bot moved this to Untriaged in Azure SDK Rust Mar 7, 2025
@heaths
Copy link
Member Author

heaths commented Mar 7, 2025

Even on an internal Teams thread, Rob Jellinghaus is recommending to run both --locked and not locked as does the article. But, because many crates avoid declaring a 1.0, that means any 0.* are updated and I know we'll have breaks e.g., getrandom.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EngSys This issue is impacting the engineering system.
Projects
Status: Untriaged
Development

No branches or pull requests

2 participants