rigetti / rigetti/qcs-api-client-rust

Tests crash (panic)

Open
#16 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
3
Forks
2
PR merge metrics
No merged PRs in 30d

Description

test configuration::tokens::test::test_qcs_secrets_readonly::read_only_values_04__Some___YES____true_::read_only_perm_1_true ... ok
test configuration::tokens::test::test_qcs_secrets_readonly::read_only_values_04__Some___YES____true_::read_only_perm_2_false ... ok
test configuration::tokens::test::test_qcs_secrets_readonly::read_only_values_05__Some___yEs____true_::read_only_perm_1_true ... ok
test configuration::tokens::test::test_qcs_secrets_readonly::read_only_values_05__Some___yEs____true_::read_only_perm_2_false ... ok
test configuration::tokens::test::test_qcs_secrets_readonly::read_only_values_06__Some___yes____true_::read_only_perm_1_true ... ok
test configuration::tokens::test::test_qcs_secrets_readonly::read_only_values_06__Some___yes____true_::read_only_perm_2_false ... ok
test configuration::tokens::test::test_qcs_secrets_readonly::read_only_values_07__Some___1____true_::read_only_perm_1_true ... ok
test configuration::tokens::test::test_qcs_secrets_readonly::read_only_values_07__Some___1____true_::read_only_perm_2_false ... ok
test configuration::tokens::test::test_qcs_secrets_readonly::read_only_values_08__Some___2____false_::read_only_perm_1_true ... ok
test configuration::tokens::test::test_qcs_secrets_readonly::read_only_values_08__Some___2____false_::read_only_perm_2_false ... ok
test configuration::test::test_externally_managed_credential_does_not_loop_on_invalid_tokens ... ok
test configuration::tokens::test::test_qcs_secrets_readonly::read_only_values_09__Some___other____false_::read_only_perm_1_true ... ok
test configuration::tokens::test::test_qcs_secrets_readonly::read_only_values_09__Some___other____false_::read_only_perm_2_false ... ok
test configuration::tokens::test::test_qcs_secrets_readonly::read_only_values_10__Some_______false_::read_only_perm_1_true ... ok
test configuration::tokens::test::test_qcs_secrets_readonly::read_only_values_10__Some_______false_::read_only_perm_2_false ... ok
test configuration::tokens::test::test_qcs_secrets_readonly::read_only_values_11__None_false_::read_only_perm_1_true ... ok
test configuration::tokens::test::test_qcs_secrets_readonly::read_only_values_11__None_false_::read_only_perm_2_false ... ok
test configuration::tokens::test::test_refresh_token_grant_persists_rotated_refresh_token ... ok
test configuration::test::test_load_with_login_persists_login_flow_token_without_explicit_refresh ... ok
test configuration::test::test_pkce_flow_persists_token ... ok
test configuration::pkce::tests::test_pkce_login ... ok
test configuration::external_command::tests::times_out_a_command_that_hangs ... ok
test configuration::tokens::test::test_tokens_blocked_during_refresh ... ok

failures:

---- configuration::test::test_default_loads_settings_with_partial_profile_applications stdout ----

thread 'configuration::test::test_default_loads_settings_with_partial_profile_applications' (482489) panicked at qcs-api-client-common/src/configuration/mod.rs:855:62:
called `Result::unwrap()` on an `Err` value: Path { path: "/usr/ports/devel/py-qcs-api-client-common/work-py312/.qcs/secrets.toml", message: "Could not find a QCS configuration at the default path: ~/.qcs/secrets.toml" }
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

---- configuration::test::test_default_loads_settings_with_partial_profile_applications_pyquil stdout ----

thread 'configuration::test::test_default_loads_settings_with_partial_profile_applications_pyquil' (482491) panicked at qcs-api-client-common/src/configuration/mod.rs:907:62:
called `Result::unwrap()` on an `Err` value: Path { path: "/usr/ports/devel/py-qcs-api-client-common/work-py312/.qcs/secrets.toml", message: "Could not find a QCS configuration at the default path: ~/.qcs/secrets.toml" }
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

---- configuration::test::test_default_uses_env_var_overrides stdout ----

thread 'configuration::test::test_default_uses_env_var_overrides' (482500) panicked at qcs-api-client-common/src/configuration/mod.rs:810:62:
called `Result::unwrap()` on an `Err` value: Path { path: "/usr/ports/devel/py-qcs-api-client-common/work-py312/.qcs/settings.toml", message: "Could not find a QCS configuration at the default path: ~/.qcs/settings.toml" }
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.


failures:
    configuration::test::test_default_loads_settings_with_partial_profile_applications
    configuration::test::test_default_loads_settings_with_partial_profile_applications_pyquil
    configuration::test::test_default_uses_env_var_overrides

test result: FAILED. 80 passed; 3 failed; 0 ignored; 0 measured; 0 filtered out; finished in 3.04s

error: test failed, to rerun pass `--lib`
*** Error code 101

Version: 0.22.1
Python-3.12
FreeBSD 15.1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the failing tests in qcs-api-client-common/src/configuration/mod.rs at lines 810, 855, and 907, then rerun the library tests in the reported FreeBSD/Python 3.12 environment. Compare the default configuration paths used by these tests with the reported /usr/ports/devel/py-qcs-api-client-common/work-py312/.qcs paths. Done means the three tests no longer panic and the full test run passes.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, rust
Domain
testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.