A CLI installed with go install reports version dev: mismatch warning on every connect, and probe_version pins are refused
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
- 45/100
Línea de trabajo
Start by reading internal/cli version handling and the release workflow or Makefile flags that set Version; then inspect the version checks in internal/probelink and how probe_version is enforced. The issue describes several possible fixes but does not choose one, so first establish the intended behavior for binaries installed with go install. Done means that behavior is covered for version warnings, compatibility checks, and pinned versions.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What happens
A CLI installed with go install github.com/alphawavesystems/flutter-probe/cmd/[email protected] reports its version as dev:
$ probe version
probe version dev
internal/cli.Version is "dev" unless the linker sets it. The release workflow and the Makefile do (-X .../internal/cli.Version=...); go install does not. The binary does carry the module version in its build information (go version -m shows mod github.com/alphawavesystems/flutter-probe v0.27.0), and nothing in internal/cli, internal/probelink or cmd reads it (debug.ReadBuildInfo is not used).
What the version string is used for
Measured by calling the functions with dev:
- Agent version warning.
probelink.VersionMismatchWarning("dev", "0.26.1")returnsversion mismatch: CLI vdev <-> agent v0.26.1 — this combination is untested ..., so ago installCLI prints that warning on every connect. The doc comment of the function says an unknown or unparsable version produces no warning, but the code only skips an empty string;devis compared as text. - Major check.
MajorVersionIncompatible("dev", "0.26.1")is false:devdoes not parse, so it never blocks the connection (as its comment says). probe_versioninprobe.yaml. A project that pinsprobe_version: 0.27.0is not satisfied bydev(ParseProbeVersion("0.27.0")thenSatisfied("dev")is false), soprobe teststops with "the installed CLI is dev, but probe.yaml requires probe_version 0.27.0. No test was run." A go-installed CLI cannot run a project that pins the version, even when it is that release.
Not changed
No fix proposed here. Options for the owner of the CLI: read the module version from debug.ReadBuildInfo when Version is dev; treat dev as unknown in VersionMismatchWarning (matching its comment); or document that go install builds report dev. The installation page's Option C (go install) is the place where users meet it.
- Lenguaje dominante
- Go
- Estrellas
- 6
- Forks
- 3
- Merge medio
- 6 h 28 min
- PR fusionados (30 d)
- 362
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de AlphaWaveSystems/flutter-probe
-
agent: is checked on a wrapper holding several checkables answers from the first one in tree orderAbiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
AlphaWaveSystems/flutter-probe#865 ·
Los mantenedores suelen responder en 1 día
-
area/cli bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
AlphaWaveSystems/flutter-probe#424 ·
Los mantenedores suelen responder en 1 día
-
area/docs documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
AlphaWaveSystems/flutter-probe#409 ·
Los mantenedores suelen responder en 1 día
-
Dial timeout error should say how long it waited and name the timeout settingPosiblemente ocupada @jay23606 la tomó hace 2 días. Abiertoarea/cli bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
AlphaWaveSystems/flutter-probe#408 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 58/100
AlphaWaveSystems/flutter-probe#886 ·
Los mantenedores suelen responder en 1 día
Todos los issues de AlphaWaveSystems/flutter-probe
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
IBM-Cloud/terraform-provider-ibm#7115 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
fluxcd/notification-controller#1441 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
volcengine/volcengine-go-sdk#163 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
OneBusAway/maglev#2145 ·
Los mantenedores suelen responder en 2 días
-
priority/medium status/ready type/chore
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
discobox-ai/discobox#1357 ·
Los mantenedores suelen responder en 1 día