Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Regression: --quiet disables --structured-logs again

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

Los mantenedores suelen responder en 1 día

@Firehed ya está trabajando en esto.

Desde el 7/10/2026.

  • #2694 de @Firehed — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
docker, go, google-cloud
Área
backend, observability

Línea de trabajo

The issue points to the logger setup rework in #2106 and the earlier fix in #1750; start by comparing how --quiet and --structured-logs configure logging. Reproduce with the provided command and verify that errors, including multiline details, remain JSON with a severity field. A linked pull request (#2694) is already open.

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

Descripción

Bug Description

When --structured-logs and --quiet are used together, error messages are written as plain text instead of JSON. This is the behavior reported in #1738 and fixed in v2.2.0 by #1750, so it is a regression.

Plain-text errors lose the severity field, and multi-line errors (for example, Google API errors with a Details: block) are split into separate entries by log collectors such as the GKE logging agent.

Bisecting the released images: v2.9.0 behaves correctly, and v2.10.0 through v2.26.0 (the latest as of this report) are affected. The change in behavior lines up with #2106, which reworked how the logger is set up.

Example code (or command)
cloud-sql-proxy --structured-logs --quiet --token=fake fake-proj:us-central1:fake-inst
Stacktrace
# v2.9.0 (expected)
{"severity":"ERROR","timestamp":"2026-10-07T23:07:14.054Z","message":"[fake-proj:us-central1:fake-inst] could not resolve instance version: ..."}

# v2.26.0 (actual)
2026/10/07 23:07:05 [fake-proj:us-central1:fake-inst] could not resolve instance version: failed to get instance: refresh error: ...
Details:
[
  {
    "@type": "type.googleapis.com/google.rpc.ErrorInfo",
...
Steps to reproduce?
  1. docker run --rm gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.26.0 --structured-logs --quiet --token=fake fake-proj:us-central1:fake-inst
  2. Errors on stderr are plain text.
  3. The same command with :2.9.0, or with --quiet removed, produces JSON errors.
Environment
  1. OS type and version: the official container images, run under Docker 29.4.0
  2. Cloud SQL Proxy version: 2.10.0 through 2.26.0
  3. Proxy invocation command: as above

This issue was written by AI (Claude Code).

Lenguaje dominante
Go
Estrellas
1.4k
Forks
356
Merge medio
10 h
PR fusionados (30 d)
12

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 GoogleCloudPlatform/cloud-sql-proxy

Todos los issues de GoogleCloudPlatform/cloud-sql-proxy

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.