Credentialed encryption integration expects SSE-B2 but live account returns NONE

Aperta
  • Qualcosa non va?
#614 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
28/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
cloud, python
Ambito
security, testing-qa

Direzione di ricerca

Start with the twelve failing cases in test/integration/test_encryption.py, which expect EncryptionSetting(SSE_B2, AES256) but receive EncryptionSetting(NONE). Determine whether the live account legitimately returns no default encryption, or whether the response decoding turns an omitted field into NONE. Done means the cause is identified and the expectation is either fixed or set up per account, without suppressing the failures. Running this needs a real B2 account with credentials.

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

Descrizione

The credentialed integration stage is currently red against the configured real-B2 account after the repository began expecting SSE-B2 as the default encryption.\n\nObserved in PR #613 CI, job test (macos-latest, 3.14):\n- unit sessions completed successfully (867 passed / 98 skipped and 710 passed / 375 skipped)\n- credentialed integration then reported 12 failures in test/integration/test_encryption.py\n- each failure expected EncryptionSetting(SSE_B2, AES256) but the live response was EncryptionSetting(NONE)\n- affected paths include bucket creation, upload bytes/local/unbound, create-file, concatenate, copy, and multipart upload/copy\n- integration summary: 12 failed, 54 passed, 1 skipped\n\nPR #613 changes only hidden .sdkharness contracts and their focused unit tests; it does not change SDK behavior or test/integration. The red job therefore exposed this independently rather than causing it.\n\nEvidence:\nhttps://github.com/Backblaze/b2-sdk-python/actions/runs/36705453903/job/109854925245\n\nInvestigate whether the configured account/realm still legitimately returns no default encryption, whether response decoding maps an omitted field to NONE incorrectly, or whether the integration expectation needs account-specific setup. Do not suppress the failures until the source is understood.

Lingua principale
Python
Stelle
214
Fork
68
Merge medio
51m
PR unite (30g)
6

Preparare l'ambiente

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 Backblaze/b2-sdk-python

Tutte le issue di Backblaze/b2-sdk-python

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.