[Bug][Blueprint] Scheduled run fails silently when plan generation errors
維護者通常 2 天內回覆
評估
研究方向
Start at BlueprintJob.Run in backend/server/services/blueprint.go and follow the call to createPipelineByBlueprint, where the MakePlanForBlueprint error returns before any pipeline record is created. The maintainers have not chosen how the failure should surface, so confirm the approach in the thread before coding. Done means a scheduled run that fails at plan time leaves a visible failed record, and a test covers the cron path.
由索引模型根據 Issue 內容生成。
描述
Search before asking
- I had searched in the issues and found no similar issues.
What happened
When a scheduled (cron) blueprint run fails during plan generation, the failure is only logged. BlueprintJob.Run in backend/server/services/blueprint.go calls createPipelineByBlueprint, which returns the MakePlanForBlueprint error before any pipeline is created. No pipeline record exists, so nothing shows as a failed run in the UI, and alerting on pipeline status can't catch it. The only trace is the lake log:
[blueprint] run cron job failed on blueprint:[1][my-blueprint]
caused by: ...
This is plugin-agnostic: any error raised while making the plan (e.g. a data source rejecting credentials) is handled this way. Example cause: #9220.
What do you expect to happen
A scheduled run that fails at plan time is visible the same way a failed pipeline is: in the UI and to anything monitoring pipeline status. Recording it as a failed pipeline is one option; maintainers may prefer another.
How to reproduce
- Create a GitHub App connection and a blueprint using it, with a cron schedule.
- Set the DevLake host clock about 2s ahead of real time (see #9220).
- Wait for the scheduled run.
- No new pipeline appears; the error is only in the lake log.
Anything else
Manually triggering the same blueprint (POST /blueprints/:id/trigger) returns the error to the caller, so only scheduled runs are affected.
Version
v1.0.3-beta14 (same code on main)
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
- 主要語言
- Go
- 星號
- 3.2k
- 分支
- 832
- 平均合併
- 2 天 1 小時
- 30 天內合併 PR
- 69
環境準備
在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 沒有貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
apache/devlake 的其他 Issue
-
[Bug][linker] LinkPrToIssue never matches lowercase issue keys (e.g. in branch names)可能已有人在做 @VictorColomb 於 1 天前認領。 未關閉type/bug
難度 2/5 1-3 小時 新手友好度 78/100
apache/devlake#9283 · 1 則留言 · 1 個 reaction · 已指派 1 人 ·
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 60/100
維護者通常 2 天內回覆
-
type/bug
難度 3/5 半天 新手友好度 73/100
維護者通常 2 天內回覆
-
[Refactor][Build] Build the core and all plugins into a single binary by default可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉component/plugins type/refactor
難度 5/5 一週以上 新手友好度 25/100
維護者通常 2 天內回覆
-
[Feature][Plugin] Add a GLPI data source plugin可能已有人在做 @rabelenda 於 4 天前認領。 未關閉type/feature-request
難度 5/5 一週以上 新手友好度 38/100
apache/devlake#9273 · 1 個 reaction ·
維護者通常 2 天內回覆
相似的 Issue
-
date_time, url_encode, html_escape, to_unix_time, contains_all and contains_any panic when called without arguments可能已有人在做 @antcybersec 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 78/100
projectdiscovery/dsl#372 ·
維護者通常 1 天內回覆
-
blocked-needs-validation
難度 2/5 1-3 小時 新手友好度 62/100
projectcapsule/capsule#2265 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 68/100
JuliusBrussee/caveman#1449 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 72/100
維護者通常 1 天內回覆
-
bot-found bug priority: P3
難度 2/5 1-3 小時 新手友好度 72/100
madenvel/KalinkaPlayer#498 ·