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

[coverage] Conformance findings: FEATUREFLAG-001

Abierto
  • ¿Algo no está bien?
#499 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go, sql
Área
backend

Línea de trabajo

The bug is in the SEA backend's connect path, which requests /api/2.0/connector-service/feature-flags/GOLANG/<ver> even when telemetry is disabled. Find where that request is issued during connection setup, and run TestNoFeatureFlagRequestWhenFlagsAreUnconsumed from the coverage PR under tests/ to see the failure. Done when that test passes and the Thrift path still issues no flag requests. Reference PR 496 in databricks-sql-go-adjacent driver work shows the intended behavior, but it is a different repo.

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

Descripción

Summary

Surfaced by the multi-language coverage fan-out while conformance-testing these SPEC-IDs against databricks/databricks-sql-go. Each finding is committed as an expected-failure (xfail) test in the coverage PR — the test asserts the CORRECT (post-fix) behavior and stays red until THIS driver (databricks/databricks-sql-go) is fixed, then flips green as a tripwire.

Findings

  • FEATUREFLAG-001 [sea]: SEA/kernel backend fetches connector-service feature flags (GET /api/2.0/connector-service/feature-flags/GOLANG/) during connect even when telemetry — the only in-driver flag consumer — is disabled, so an unconsumed flag context costs an extra control-plane request per connection; the Thrift path correctly issues none
    • failing test: TestNoFeatureFlagRequestWhenFlagsAreUnconsumed (see the coverage PR diff under tests/)

Reproduce & Expected

FEATUREFLAG-001 — Opens a proxied connection with telemetry explicitly disabled and runs SELECT 1.

Reproduce:

SELECT 1 AS value

Expected (per the shared spec):

  • result has exactly 1 row(s)
  • col 0, row 0 == 1 (type Int32)
  • full assertion contract:
result:
- row_count: 1
- column:
    index: 0
    row: 0
    type: Int32
    equals: 1
protocol:
  thrift:
  - http_request_count:
      path_prefix: /api/2.0/connector-service/feature-flags/
      expected: 0
  sea:
  - http_request_count:
      path_prefix: /api/2.0/connector-service/feature-flags/
      expected: 0

Context

Lenguaje dominante
Go
Estrellas
53
Forks
68
Merge medio
2 d 1 h
PR fusionados (30 d)
8

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 databricks/databricks-sql-go

Todos los issues de databricks/databricks-sql-go

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.