ios client for sourcehut. swiftui. http://git.krz.sh/krz/hutch.git/atom?h=v3.7.0 2026-07-16T02:56:56+00:00 2026-07-16T02:56:56+00:00 Christian Cleberg hello@cleberg.net 2026-07-16T02:56:56+00:00 urn:sha1:575e62f6dab44b0c9836623fe8b7d17a219f8e0f Tapping a patch failed with "no matching navigationDestination declaration visible from the location of the link". MailingListDetailView is presented from four places, but only the More tab and Lookup declare a MoreRoute destination. Reached from a project, via ProjectMailingListView, there is no such destination in the surrounding stack, so a NavigationLink carrying MoreRoute.patchset had nowhere to resolve. The thread rows beside it already use the closure form for exactly this reason. Push PatchsetDetailView directly, from the rows and from the version-chain links inside the detail view, which inherits whatever stack presented it. That leaves MoreRoute.patchset with no users, so it and its two destinations are removed rather than left as a route nothing links to. Neither the compiler nor the tests catch this: it is a runtime SwiftUI resolution failure. 2026-07-16T02:48:58+00:00 Christian Cleberg hello@cleberg.net 2026-07-16T02:48:58+00:00 urn:sha1:0eceec357b7ef5251ed0ae9d42b513c17380e0af Patchsets are how contributions reach sourcehut, and Hutch had no reference to them anywhere. This adds review and triage: read a series, see its checks and version chain, and set its status. Two schema facts shaped the design. MailingList exposes no patchsets field, so a list's patchsets cannot be queried directly. They are reachable only through thread roots, so the existing threads query now also selects root.patchset — no extra request — and the Patches tab is derived from that. It appears only on lists that actually carry patches. Patch carries no diff. index, count, version, prefix, subject, and trailers are all it has; the diff exists only inside the email body. Patch bodies are split with the same InboxThreadUtilities.segmentMessageBody the inbox uses and rendered through the existing DiffView. Patches are ordered by their [PATCH n/m] index rather than receipt order, since mail arrives out of sequence. Patches with no index are kept at the end rather than dropped, because a one-off patch has no prefix. updatePatchset is nullable, so a null response is treated as a declined change and the local status is left alone rather than advanced optimistically. UNKNOWN and SUPERSEDED are not offered: the first is a sentinel, the second is set by the server when a newer version lands. Patch submission stays out of scope. It is a git send-email flow, not a GraphQL mutation. 2026-07-16T00:31:17+00:00 Christian Cleberg hello@cleberg.net 2026-07-16T00:31:17+00:00 urn:sha1:eff81f34bb51ecc6e0aa5d831567db2cea0527a9 InboxThreadSummary.id returned threadGroupingKey, which is listRID plus the subject with Re:/Fwd: stripped. Two unrelated threads on one list sharing a subject therefore shared an id — common on sourcehut, where "[PATCH] test" is an ordinary subject — which collides under Identifiable in every list that renders these summaries. Key id on the root Message-ID, which is unique per thread, and leave threadGroupingKey subject-based so replies still collapse into one conversation. Read state moves to threadGroupingKey at each call site. It was already keyed on that string via id, so persisted keys are unchanged and marking a conversation read still covers the whole subject group, matching how HomeViewModel already builds the key for isUnread. 2026-05-14T18:27:41+00:00 Christian Cleberg hello@cleberg.net 2026-05-14T18:18:55+00:00 urn:sha1:51b2eb0e6296734960f37cebd40fee34a1f261f9 - add read-only App Intents for core Hutch workflows - route intents through the existing Hutch navigation/deep-link model - expose Work Queue, Recent Activity, System Status, pinned resources, projects, failed builds, assigned tickets, saved searches, and search where supported - keep App Intents non-mutating for the initial implementation - preserve existing widget, Safari extension, and hutch:// routing behavior References: https://todo.sr.ht/~ccleberg/hutch/71 2026-05-14T17:41:55+00:00 Christian Cleberg hello@cleberg.net 2026-05-14T17:41:55+00:00 urn:sha1:0d61e05e98f6f020722ee4d43f024c1da348d2a9 2026-05-07T01:30:34+00:00 Christian Cleberg hello@cleberg.net 2026-05-07T01:30:34+00:00 urn:sha1:57e4f34b4613c09beb0cb757ac2ba2b43cc04daf Introduce an actor-backed persistent cache layer at the SRHTClient boundary for read-only SourceHut data. Cache entries now store stable metadata including key, resource type, fetched/expires/access timestamps, payload hash, schema version, and payload size, with bounded memory and disk usage. Add centralized cache key builders and TTL defaults for repository, file, ticket, build, log, profile, status, and list-style resources. Support networkOnly, cacheOnly, cacheFirstThenRefresh, and refreshIgnoringCache policies, plus request coalescing for duplicate in-flight cache keys. Integrate first-pass caching into high-value low-risk read paths: - build detail and completed/active build logs - ticket detail - README lookup - repository tree, blob, and linked file reads Keep mutation paths network-only and add simple prefix invalidation after ticket and build mutations. Add compact cached/stale UI status rows and a Settings action to clear the persistent cache. Add focused cache tests covering round trips, expiration, stale fallback, policy behavior, request coalescing, prefix invalidation, size limits, LRU pruning, expired pruning, and mutation bypass behavior. Document storage, key, TTL, invalidation, limitations, and next recommended targets. 2026-04-23T22:39:13+00:00 Christian Cleberg hello@cleberg.net 2026-04-23T22:39:13+00:00 urn:sha1:66601a8091a73f3e31f4fb534c38b3eca4756e93 2026-04-20T17:42:09+00:00 Christian Cleberg hello@cleberg.net 2026-04-20T17:42:09+00:00 urn:sha1:454c459394437f346a2d08d59a5504c0f6ec299f - limit Home failed-build counts to a configurable lookback window and add the setting under Behavior. - make the Recent and Builds rows fully tappable across the entire cell and add coverage for the new failed-build filtering. Fixes: https://todo.sr.ht/~ccleberg/hutch/67 2026-04-14T15:42:05+00:00 Christian Cleberg hello@cleberg.net 2026-04-14T15:42:05+00:00 urn:sha1:205c8ea9b2c6dfa62bc8b2342d1aa71e2da7d6ac - removed prototype screens - limited Recent section to 3 items - added initial support for tips Fixes: https://todo.sr.ht/~ccleberg/hutch/65 2026-04-14T00:44:44+00:00 Christian Cleberg hello@cleberg.net 2026-04-14T00:44:44+00:00 urn:sha1:fe1ccc69661603d419a642a450e4ac9e1258adb0 - Add shared HutchDeepLinkURL constants for app, widgets, and tests. - Bump marketing version to 3.1.2 and build to 70 (app + widget extension). - Point Hutch stats default base URL at HutchStatsAPI; add SRHTWebURL status incident feed and reuse it from SystemStatusService. - Group Project into Metadata and Resources; split ContributionStatsResponse into StatsWindow and StatsTotals with updated decoding and tests. - Replace @Bindable usage with explicit Bindings in Profile, Projects list, and repository ACL flows; simplify Home pinned-item helper; add no-op bodies on cancel alert buttons where the compiler requires a statement. - Move repository row build-status indicator next to the relative-updated caption and reserve a fixed 8×8 slot so the row does not jump when status loads. - Use NSString.lastPathComponent for build artifact filenames; collapse duplicate ACL error branches; minor HutchStats HTTP and XMLParserDelegate cleanups. - Point widgets at HutchDeepLinkURL helpers; align tests with the new response and URL types.