Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Review follow-ups for the dbt e2e cache, CI comments, skill-sync test and run --model

Offen
  • Stimmt etwas nicht?
#1,473 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
github-actions, python, shell, typescript
Bereich
ci-cd, cli, testing

Rechercherichtung

This bundles six small fixes across packages/dbt-tools/test/e2e/setup-versions.sh, dbt-versions.test.ts, the e2e README, .github/workflows/ci.yml, the run --model error path, and the skill-sync test. Start with the installed_version() function and the venv check in the shell script, and the empty-entry parsing of DBT_E2E_VERSIONS in the TypeScript test. Pick one item at a time; done means each listed behaviour is fixed and the affected tests pass.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

bug

What

Review follow-ups from #1258, #1469, #1470 and #1472, which merged without them:

  1. packages/dbt-tools/test/e2e/setup-versions.sh (#1258)
    • installed_version() runs dbt --version with no time limit, so a dbt that hangs stalls setup until the job times out.
    • A venv directory without bin/dbt (an interrupted install) is skipped instead of rebuilt, and a fresh install is never checked against the version asked for.
    • The usage text still names ./e2e-setup.sh.
  2. packages/dbt-tools/test/e2e/dbt-versions.test.ts (#1258)
    • With no versioned venvs, the system-dbt fallback passes the first python3 on PATH as pythonPath, which may belong to a different dbt than the one under test.
    • An empty entry in DBT_E2E_VERSIONS ("1.8,", or only commas) counts as a requested version named "".
  3. packages/dbt-tools/test/e2e/README.md (#1258) describes the old CI setup and does not document DBT_E2E_VERSIONS or DBT_E2E_PYTHON.
  4. .github/workflows/ci.yml comments (#1469) do not say why runs on main can still show as cancelled: a concurrency group keeps one running and one pending run, and a newer run cancels the pending one.
  5. run --model (#1472): when the provider-list call fails, the error body is described with JSON.stringify, which throws on a cyclic object or a BigInt. The message about the failure is then lost behind a TypeError.
  6. The skill-sync test added in #1470 does not check the row the link leaves behind (its linkedAt, and that it is not marked adopted).

Suggested fix

  • Bound dbt --version with timeout/gtimeout, rebuild any existing venv whose dbt does not report the expected version, and fail setup when a fresh install reports the wrong one. Update the README and usage text.
  • Filter empty entries out of DBT_E2E_VERSIONS, and take pythonPath from the directory of the resolved system dbt, falling back to python3 on PATH.
  • Name the concurrency behaviour in the ci.yml comment.
  • Fall back to String(error) when JSON.stringify throws.
  • Assert the linked row's linkedAt and that it is not adopted.
Vorherrschende Sprache
TypeScript
Sterne
812
Forks
123
Ø Merge
1 T. 14 Std.
Gemergte PRs (30 T.)
88

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus AltimateAI/altimate-code

Alle Issues in AltimateAI/altimate-code

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.