Issue & PR triage

Loading...

Showing 7 of 7 issues

Issue Title Author Age Action Impact ↓ Actionability Quick Win Summary
craft-providers
issue #895
Add a LXD VM provider lengau 275d needs triage 66 58 13 Add a VM-backed LXD provider for Imagecraft loop-device support; the requested capability remains open and is absent from the current provider tree.
craft-providers
issue #684
Create a generic craft LXD profile dilyn-corner 749d needs triage 58 50 13 A dedicated craft LXD profile is proposed to isolate build containers from user-edited defaults; the open enhancement still needs a decision on shared versus per-user profiles.
craft-providers
issue #714
craft-providers error: Timed out waiting for networking to be ready. nteodosio 657d needs triage 48 45 8 Open Type: Bug report: Snapcraft 8.5.1 LXD builds time out while getent checks DNS for snapcraft.io; host/network context and a part YAML are missing, leaving the root cause unknown.
craft-providers
issue #794
Warn if requested specs don't match the existing instance bepri 443d needs triage 48 46 11 Existing instances are reused without validating requested hardware settings; a maintainer asked for elaboration, but the mismatch policy and covered specifications remain unspecified.
craft-providers
issue #119
Provide fixtures / some helpers to test an application using craft-providers jugmac00 1641d needs triage 42 48 8 Enhancement request for reusable public test fixtures/helpers that simplify downstream mocking of elaborate LXD JSON responses; remains open, uncommented, and not maintainer-triaged.
craft-providers
issue #467
macOS CI is failing weekly tests mr-cal 1065d needs triage 35 25 3 Maintainer-tracked CI issue: macOS runners drop connection after ~1h losing all logs, so flaky macOS integration tests were pushed out of PR CI (#452) into the weekly workflow. Still open, no logs or reproducer captured.
craft-providers
issue #970
Test on Python 3.14 and Ubuntu 26.04 (Resolute) lengau 148d needs triage 30 60 14 Request to add Python 3.14 and Ubuntu 26.04 testing to CI. A previous PR (#971) failed and was closed, leaving the tracking issue open without maintainer review or labels.