Issue & PR triage
Loading...
Showing 14 of 14 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
fetch-service issue #354 |
Set up the proxy on a random port that's queryable from the control API | lengau | 602d | needs triage | 60 | 68 | 18 | Requests a runtime-selected proxy port exposed through the control API; it remains open and unlabeled, and current code still uses a fixed default proxy port. |
|
fetch-service issue #364 |
Inspectors contain valid URL placeholders | cmatsuoka | 591d | needs triage | 58 | 64 | 15 | Hard-coded PyPI URL matchers remain in package inspectors; the requested repository-wide placeholder audit is still open, unlabeled and awaiting maintainer triage. |
|
fetch-service issue #156 |
Add inspector for images | jugmac00 | 832d | needs triage | 52 | 47 | 9 | Image inspection is missing, so base images appear as unrecognized artifacts in manifests even though builds succeed; requirements and technical scope remain untriaged. |
|
fetch-service issue #381 |
Incorrect metadata for `application/x.go.module.git-repo` (parsing `go.mod`) | Vyom-Yadav | 559d | needs triage | 48 | 60 | 18 | Go module Git metadata remains incorrect: the inspector manually parses go.mod and emits a short name instead of the full module path; proposed go.sum validation is unresolved. |
|
fetch-service issue #296 |
Unable to disambiguate CRAFT package type with multiple CRAFT YAMLs | SuperAlpaca27 | 709d | needs triage | 48 | 64 | 12 | A repository with snapcraft.yaml, rockcraft.yaml, and sourcecraft.yaml gets three approvals, but Fetch Service emits Snapcraft metadata for a Sourcecraft package; the report remains untriaged. |
|
fetch-service issue #247 |
Use github.com/dpeckett/deb822 for deb822 parsing | tigarmo | 755d | needs triage | 46 | 61 | 9 | Maintainer request to replace several custom Debian 822 parsers with github.com/dpeckett/deb822 for multiline-field support remains unimplemented and unlabelled; only an automated Jira-sync comment exists. |
|
fetch-service issue #401 |
Add format inspection smoke tests | cmatsuoka | 494d | needs triage | 45 | 50 | 11 | Partially implemented: the repository has Spread smoke-test tasks for several inspectors, but the issue remains unlabelled and untriaged, with no evidence all supported artifact formats are covered. |
|
fetch-service issue #353 |
Control from a unix domain socket | lengau | 602d | needs triage | 45 | 55 | 15 | Feature request: let the fetch service control API (currently TCP-only, bound to all interfaces via --control-port) also listen on a unix-domain socket when a path is given. Still open, no labels, no discussion. |
|
fetch-service issue #225 |
Add GitHub workflow that builds and tests the fetch-operator charm | lengau | 766d | needs triage | 42 | 58 | 11 | Maintainer task (lengau) to add a CI workflow that builds the fetch-operator charm and runs `charmcraft test` with charmcraft.yaml pinned to the current fetch-service commit; still unimplemented. |
|
fetch-service issue #388 |
fetchctl tests fail in Fedora | cmatsuoka | 538d | needs triage | 40 | 78 | 14 | Fedora 40 spread basic-inspection fails because fetch-service.fetchctl is unavailable; Fedora remains disabled in spread.yaml pending investigation. |
|
fetch-service issue #96 |
Missing metadata attributes in certain file formats | cmatsuoka | 910d | needs triage | 40 | 42 | 7 | Maintainer-filed backlog issue: ancillary artefacts (apt Packages, git protocol, snap API, pip index) report empty name/version/vendor in session metadata. Unlabelled, no comments or precise reproducer after 883 days; needs scoping. |
|
fetch-service issue #662 |
Flaky TestServerListening in control due to unclosed servers and timing race | lengau | 30d | needs triage | 32 | 86 | 23 | control.TestServerListening flakes in CI: hardcoded port 18111 reused by three tests, servers never Stop()ed, and a 500ms sleep instead of waiting on ctl2.Dying(). Proposed fix with root cause analysis. |
|
fetch-service issue #257 |
Document how to generate captures for test data | lengau | 750d | needs triage | 30 | 65 | 16 | Open, untriaged maintainer doc request: add a how-to page describing how to generate pcap captures (tshark + SSLKEYLOGFILE git clone) used as fetch-service test data. No such docs exist yet. |
|
fetch-service issue #389 |
Update snapcraft test to stable in CI tests | cmatsuoka | 538d | needs triage | 28 | 50 | 11 | CI spread tests still install snapcraft from latest/edge; maintainer wants the stable channel used in tests once craft-test is published there. Still open, unlabelled, no discussion. |