Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Tests crash (panic)

Aperta
#16 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
python, rust
Ambito
testing

Direzione di ricerca

Inizia dai test che falliscono in qcs-api-client-common/src/configuration/mod.rs alle righe 810, 855 e 907, quindi esegui nuovamente i test della libreria nell’ambiente FreeBSD/Python 3.12 segnalato. Confronta i percorsi di configurazione predefiniti utilizzati da questi test con i percorsi /usr/ports/devel/py-qcs-api-client-common/work-py312/.qcs segnalati. Il lavoro è concluso quando i tre test non causano più panic e l’esecuzione completa dei test ha esito positivo.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
Rust
Stelle
3
Fork
2
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Non abbiamo ancora controllato i file di configurazione di questo progetto. Parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di rigetti/qcs-api-client-rust

Tutte le issue di rigetti/qcs-api-client-rust

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.