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

Abierto
  • ¿Algo no está bien?
#614 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
28/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cloud, python
Área
security, testing-qa

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
214
Forks
68
Merge medio
51 min
PR fusionados (30 d)
6

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Backblaze/b2-sdk-python

Todos los issues de Backblaze/b2-sdk-python

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.