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

Aberta
  • Algo errado?
#614 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
28/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
cloud, python
Domínio
security, testing-qa

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Python
Estrelas
214
Forks
68
Merge médio
51min
PRs com merge (30d)
6

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de Backblaze/b2-sdk-python

Todas as issues de Backblaze/b2-sdk-python

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.