You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
file_out output type passes --validate but crashes at pipeline construction #530
`Config::validate()` explicitly accepts `OutputType::FileOut` and validates it requires a `path`. But `build_output_sink()` has no match arm for `FileOut` — it falls through to the default error case. Unlike elasticsearch/loki/parquet which are caught by the existing issue #500 pattern, `file_out` uniquely passes validation cleanly but crashes at runtime.
Proposed fix
Either add the `FileOut` match arm to `build_output_sink()`, or reject it in `validate()` with a "not yet implemented" message.
--validate gives false positive for unsupported input/output types #500 — It describes the same validation/runtime mismatch pattern for output types: configuration passes --validate but fails during pipeline construction when sink support is missing. That context likely covers the same validation boundary and error-surfacing path.
Integrity filtering activated and filtered the following items during workflow execution.
This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.
Activity
github-actions commentedon Apr 1, 2026
2 related issues
--validatebut fails during pipeline construction when sink support is missing. That context likely covers the same validation boundary and error-surfacing path.Note
🔒 Integrity filtering filtered 7 items
Integrity filtering activated and filtered the following items during workflow execution.
This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.
issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)What is this? | From workflow: AI: Duplicate Issue Detector
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
google-labs-jules commentedon Apr 2, 2026
Jules has failed to create a task. You can try again later by removing and re-adding the 'jules' label.
fix: reject file_out at config validation time (#530)
fix: reject file_out at config validation time (#530)
fix: config validation for elasticsearch, loki, file_out (#718, #530) (…