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

Cannot build a fresh checkout, configure_me has yanked deps #1042

Open
aditanase opened this issue Aug 16, 2024 · 2 comments
Open

Cannot build a fresh checkout, configure_me has yanked deps #1042

aditanase opened this issue Aug 16, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@aditanase
Copy link

Describe the bug

Can't build after checkout, configure_me depends on an yanked version of cargo_toml library.

To Reproduce
Steps to reproduce the behavior:

checkout main, cargo build. Result:

error: failed to select a version for the requirement `cargo_toml = "^0.12.0"`
candidate versions found which didn't match: 0.20.4, 0.20.3, 0.20.2, ...
location searched: crates.io index
required by package `configure_me_codegen v0.4.4`
    ... which satisfies dependency `configure_me_codegen = "^0.4.4"` of package `ballista-executor v0.12.0 (/Users/atanase/dev/arrow/datafusion-ballista/ballista/executor)`
    ... which satisfies path dependency `ballista-executor` of package `ballista v0.12.0 (/Users/atanase/dev/arrow/datafusion-ballista/ballista/client)`
    ... which satisfies path dependency `ballista` of package `ballista-cli v0.12.0 (/Users/atanase/dev/arrow/datafusion-ballista/ballista-cli)`
if you are looking for the prerelease package it needs to be specified explicitly
    cargo_toml = { version = "0.19.0-beta.1" }

Tried a soft update by patching the config with this PR: https://github.com/Kixunil/configure_me/pull/61/files

But now I get other errors which I don't know how to debug.

error: failed to run custom build command for `ballista-executor v0.12.0 (/Users/atanase/dev/arrow/datafusion-ballista/ballista/executor)`

Caused by:
  process didn't exit successfully: `/Users/atanase/dev/arrow/datafusion-ballista/target/debug/build/ballista-executor-855ae22fe006e311/build-script-build` (exit status: 1)
  --- stdout
  cargo:rerun-if-changed=executor_config_spec.toml

  --- stderr
  Error: "configure_me code generation failed: failed to parse config specification: invalid type: sequence, expected a map for key `switch` at line 163 column 1"
warning: build failed, waiting for other jobs to finish...
error: failed to run custom build command for `ballista-scheduler v0.12.0 (/Users/atanase/dev/arrow/datafusion-ballista/ballista/scheduler)`

Caused by:
  process didn't exit successfully: `/Users/atanase/dev/arrow/datafusion-ballista/target/debug/build/ballista-scheduler-296d85212e3c693f/build-script-build` (exit status: 1)
  --- stdout
  cargo:rerun-if-changed=scheduler_config_spec.toml

  --- stderr
  Error: "configure_me code generation failed: failed to parse config specification: invalid type: sequence, expected a map for key `switch` at line 186 column 1"

Expected behavior
A clear and concise description of what you expected to happen.

Additional context
Add any other context about the problem here.

@aditanase aditanase added the bug Something isn't working label Aug 16, 2024
@aditanase
Copy link
Author

@aditanase we can close when the upstream PR gets merged
Kixunil/configure_me#62

@Kixunil
Copy link

Kixunil commented Aug 22, 2024

You should be able to upgrade already. That PR is against master and I've already released a backported version. (master contains some API breaks) Though that version is only using 0.13+ because I made a mistake. It also inevitably bumps MSRV.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants