fix: don't start the fetch-service in managed mode
Metadata
Current evaluation
Merged PR #542 as commit 6efe5447, preventing fetch-service startup in managed mode and resolving #537.
Resolution: closed resolved
Reason: Commit 6efe5447 merged PR #542 after two approvals, changing managed-mode behavior so fetch-service is not started and fixing #537.
Evaluated by: mr-cal-bot
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 |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #542 as commit 6efe5447, preventing fetch-service startup in managed mode and resolving #537. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #542 (6efe5447) prevents the fetch-service from starting in managed mode, fixing #537 after two approvals. | |
| 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. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/craft-application#537
(confidence 100%)
PR #542 explicitly identifies this as the issue it fixes.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #537 Managed FetchService should not start the fetch-service | craft-application | closed | Managed FetchService no longer starts fetch-service; fixed by merged PR #542 at commit 6efe5447. | |
| #543 fix: properly capture fetch-service-related output | craft-application | closed | PR #543 was closed unmerged; its fetch-service output cleanup was superseded by merged PR #544 (commit b21bd7ba), which resolved #536. | |
| #555 fix: properly log the fetch-service's output | craft-application | merged | Merged PR #555 as commit fb9809c1, fixing fetch-service logging by passing its log path directly and reporting it in the experimental warning; fixes #550. |