fix: don't start the fetch-service in managed mode
Metadata
Current evaluation
Merged to prevent the fetch-service from starting in managed mode, resolving issue #537. Approved by two reviewers, the commit modifies three files with 13 additions and one deletion.
Suggested action: —
No scores available.
Issue body
Fixes #537
- [ ] Have you followed the guidelines for contributing?
- [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [ ] Have you successfully run `tox`?
-----
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged to prevent the fetch-service from starting in managed mode, resolving issue #537. Approved by two reviewers, the commit modifies three files with 13 additions and one deletion. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a fix preventing the fetch-service from starting in managed mode, resolving issue #537. The change was authored by maintainer tigarmo and integrated into the codebase. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #543 fix: properly capture fetch-service-related output | craft-application | closed | Merged to wrap fetch-service configuration output into a progress stream, resolving issue #536. The update adds a 62-line diff across 5 files to improve user feedback during instance setup. | |
| #555 fix: properly log the fetch-service's output | craft-application | merged | Merged a fix for fetch-service logging that bypasses snap file descriptor restrictions by passing the logfile path via a new CLI option instead of bash redirection. Approved by two reviewers, passed CI, and resolves issue #550. |