Issues & PRs - craft-dashboard

Issue & PR triage

Showing 28 of 28 issues

Issue	Title	Author	Age	Action	Impact ↓	Actionability	Quick Win	Summary
craft-application issue #1205	remote build: stale git repositories on launchpad Related work	enriqueesanchz	28d	needs triage	64	78	19	New, unlabelled report documents several remote-build paths orphaning about 20,000 Launchpad git repositories and proposes a best-effort, bounded cleanup sweep; no maintainer response yet.
craft-application issue #386	Explicitly separate public and private APIs	lengau	835d	needs triage	58	46	6	API visibility remains undefined: launchpad and remote already expose __all__, but no policy classifies them as public or private and no implementation plan is provided.
craft-application issue #676	Use a different instance name when using the fetch service	lengau	602d	needs triage	56	61	19	A separate provider-instance name is requested for fetch-service runs so they do not destroy the normal build instance; the issue remains open, unlabelled, and without discussion.
craft-application issue #993	`request` should be able to retry upon broken connections Related work	zhijie-yang	277d	needs triage	52	55	16	remote-build crashes with unhandled ChunkedEncodingError when artifact download breaks mid-stream; request service has no retry support. Still open, no maintainer response, code path unchanged.
craft-application issue #989	remote-build does not exit with error upon partially successful builds	zhijie-yang	286d	needs triage	50	80	29	remote-build returns exit code 0 even when some architecture builds fail/stop; the unconditional `return 0` at the end of `_monitor_and_complete` in commands/remote.py is identified as the cause. Unlabelled, no maintainer response yet.
craft-application issue #342	Utility to allow a `format` option for commands. Related work	lengau	903d	needs triage	49	76	22	A maintainer-authored request for reusable table and JSON output helpers remains unimplemented and untriaged in the current codebase.
craft-application issue #670	Document best practices for craft-application test fixtures Related work	lengau	604d	needs triage	48	67	19	Open maintainer request for a how-to standardizing application test-fixture setup and use; individual pytest fixtures have reference docs, but no task-oriented guide is indexed.
craft-application issue #331	Process grammar and non-grammar dictionary data Related work	mr-cal	912d	needs triage	48	87	22	The organize grammar processor cannot combine conditional mappings with plain file mappings in one list; the exact arm64 reproducer remains open with no maintainer triage or implementation.
craft-application issue #295	Store the user's Launchpad credentials in a keyring when available Related work	lengau	939d	needs triage	45	82	17	Launchpad remote builds still store credentials in a user-data file; OS-keyring storage with file fallback remains unimplemented and needs maintainer triage.
craft-application issue #719	Raise an error for unfiltered build plans	mr-cal	574d	needs triage	42	74	15	The requested guard remains unimplemented: create_build_plan() still accepts three None filters and selects one build-on per platform; LifecycleService also depends on that fallback.
craft-application issue #713	Add an issues page field to the base application Related work	bepri	580d	needs triage	42	72	15	Open, untriaged request to add a mandatory issue-reporting URL to AppMetadata; the current code exposes docs_url but has no issues_page field.
craft-application issue #573	Improve API naming and scoping	sergiusens	696d	needs triage	40	55	12	Maintainer proposal to drop redundant Service suffix (PackageService -> services.Package) and tighten module scoping. Still unchanged at HEAD: no labels, comments, or decision on naming variant or back-compat.
craft-application issue #434	Provide a way to write machine-readable output to stdout for `pack`	lengau	792d	needs triage	40	60	12	Maintainer-authored feature request for opt-in JSON output to stdout from pack, plus guidance for app commands. Open, unlabelled, no comments; output schema and interface remain undecided.
craft-application issue #1015	Improve craft tool dev experience with destructive mode Related work	bepri	254d	needs triage	38	65	10	Root-run destructive packing leaves root-owned lifecycle directories, blocking later non-root packing; the UX request remains untriaged with no selected solution.
craft-application issue #685	overlayfs tests break on plucky	lengau	590d	needs triage	38	74	12	Plucky's AppArmor profile denies fuse-overlayfs mounts, breaking a lifecycle integration test; the report has a reproducer and audit log, but no triage, confirmed root cause, fix, or implementation link.
craft-application issue #741	Refactor to return packaged resource names Related work	cmatsuoka	554d	needs triage	35	60	10	PackageService.pack still returns only artifact paths and exposes resource_map in the legacy path; newer artifact-aware packing bypasses it, so the requested API cleanup needs reassessment.
craft-application issue #435	Include appropriate craft-parts environment variables when packing with...	lengau	791d	needs triage	35	60	8	Feature request to set craft-parts environment variables such as CRAFT_STAGE when launching a shell via --shell or --debug, so override scripts can be tested faster. Unlabelled and without comments.
craft-application issue #1092	Some tests will require the charm plugin to be enabled Related work	lengau	136d	needs triage	35	55	13	Open, unlabelled issue: charmcraft PR #2722 may make craft-application tests depend on the charm plugin; the maintainer asks to remove that dependency, but no affected test or fix is identified.
craft-application issue #682	Upstream Charmcraft's store service	mr-cal	591d	needs triage	35	58	9	Move Charmcraft's store service into craft-application to remove duplicated code; it remains open, unlabeled, and unresolved pending triage.
craft-application issue #395	Put public utility items in the top-level namespace Related work	lengau	827d	needs triage	34	76	18	Public helpers such as get_host_architecture should be re-exported from craft_application directly; current code still exposes them only through craft_application.util.
craft-application issue #692	internal errors for `all` platform Related work	mr-cal	584d	needs triage	32	90	22	A null `all` platform reaches Pydantic as a required Platform, causing an internal type error instead of the intended build-on validation message; the issue remains open and untriaged.
craft-application issue #370	Bad error report when the lxd instance is already running	tigarmo	848d	needs triage	32	82	17	A second craftapp pack in the same directory reports only that LXD failed to start when the managed instance is already running; the reproducer is clear, but maintainer triage is missing.
craft-application issue #24	YAML loading either needs simplification or better testing Related work	lengau	1239d	needs triage	30	60	10	YAML loader exception handling from PR #20 may be redundant with current PyYAML; no regression test exercises it, and the open issue lacks a concrete reproducer.
craft-application issue #262	Refactor how managed mode and provider are determined Related work	mr-cal	962d	needs triage	30	74	12	A maintainer-filed code-debt refactor remains open: consolidate split managed-mode and provider decisions earlier in craft-application; current code still handles them separately.
craft-application issue #606	Remove `work_dir` argument from `ProviderService` methods	mattculler	652d	needs triage	30	70	12	ProviderService stores work_dir in __init__ but instance() still requires its own work_dir while clean_instances() uses self._work_dir; refactor requested to remove method argument. No maintainer triage yet.
craft-application issue #350	Incorrect part name when cd-ing when within the build environment	sergiusens	891d	needs triage	25	88	20	instance_bashrc prints 'parts' instead of the real part name when cd-ing into a part build dir; caused by ${PWD#$"HOME"} quoting bug, still present at HEAD, unlabelled and unattended.
craft-application issue #306	Fix & re-enable test checking for snaps Related work	lengau	932d	needs triage	22	52	7	Re-enable and fix the commented-out test_get_basic_items integration test (tests/integration/launchpad/test_anonymous_access.py), disabled in PR #307 after lengau's private snap broke it; still commented out with a TODO linking this issue.
craft-application issue #1086	Remove BuilddBaseAlias string-match guard in handle_runtime_error Related work	tonyandrewmeyer	149d	needs triage	20	45	6	Follow-up cleanup request: replace the message-matching BuilddBaseAlias ValueError guard in handle_runtime_error with typed handling. Blocked by open craft-providers#969; the guard does not yet exist on main (introduced in still-open PR #1082).