[Feature] Preview and unpack an already uploaded managed archive #45
Closed
opened 2026-09-07 10:24:31 +02:00 by zemion
·
4 comments
No Branch/Tag Specified
Labels
Clear labels
area/api
area/auth
area/db
area/devex
area/docs
area/governance
area/marketing
area/migrations
area/module-system
area/rbac
area/release
area/security
area/tenancy
area/webui
audit/complexity
audit/duplication
audit/false-positive
audit/needs-design
audit/quick-fix
audit/structural
codex/needs-human
codex/ready
module/access
module/addresses
module/admin
module/appointments
module/approvals
module/audit
module/calendar
module/campaign
module/cases
module/committee
module/connectors
module/core
module/dashboard
module/dataflow
module/datasources
module/decisions
module/dist-lists
module/dms
module/docs
module/encryption
module/erp
module/evaluation
module/files
module/fit-connect
module/forms
module/forms-runtime
module/helpdesk
module/identity
module/identity-trust
module/idm
module/ledger
module/mail
module/mandates
module/notifications
module/ops
module/organizations
module/parties
module/payments
module/permits
module/policy
module/poll
module/portal
module/postbox
module/projects
module/quick-access
module/records
module/reporting
module/risk-compliance
module/scheduling
module/search
module/services
module/tasks
module/templates
module/tenancy
module/tickets
module/views
module/voting
module/wiki
module/workflow
module/workflow-engine
module/xoev
module/xrechnung
module/xta-osci
source/backlog-import
source/security-audit
source/todo-scan
HTTP API contracts, routers, schemas, or API smoke behavior.
Authentication, sessions, access bootstrap, or login behavior.
Database sessions, models, transactions, or persistence primitives.
Local developer workflow, scripts, tests, tooling, or release helpers.
Durable documentation and project guidance.
Governance policy, audit, privacy, retention, or compliance behavior.
Public website, product messaging, publication copy, or legal page content.
Alembic migrations, schema bootstrap, or persistence evolution.
Module discovery, manifests, capabilities, routing, or optional integrations.
Permissions, roles, delegation, or authorization policy.
Versioning, release locks, tags, packaging, or dependency pins.
Security posture, static analysis, supply-chain hardening, or vulnerability remediation.
Tenant boundaries, provisioning, or tenant-scoped data behavior.
Shared WebUI shell, frontend components, routing, or frontend tests.
Complexity finding from Radon, Xenon, or equivalent maintainability scans.
Duplicated-code finding from jscpd or equivalent similarity scans.
Audit finding reviewed as a narrow false positive or acceptable risk.
Audit finding that needs an architectural or product decision before implementation.
Audit finding that appears narrow and directly fixable.
Audit finding that needs design, refactoring, or behavior review.
Needs an explicit human decision before Codex should implement.
Suitable for Codex to pick up with the existing issue context.
GovOPlaN access, identity, authentication, RBAC, and administration behavior.
GovOPlaN Addresses module behavior or integration.
GovOPlaN Admin module behavior or integration.
GovOPlaN Appointments module behavior or integration.
GovOPlaN Approvals module behavior or integration.
GovOPlaN Audit module behavior or integration.
GovOPlaN Calendar module behavior or integration.
GovOPlaN campaign module behavior or integration.
GovOPlaN Cases module behavior or integration.
GovOPlaN Committee module behavior or integration.
GovOPlaN Connectors module behavior or integration.
GovOPlaN core runner, shared primitives, shell, or extension points.
GovOPlaN Dashboard module behavior or integration.
GovOPlaN Dataflow module behavior or integration.
GovOPlaN governed datasource contracts, catalogs, and integrations.
GovOPlaN formal Decisions module behavior or integration.
GovOPlaN Distribution Lists module behavior or integration.
GovOPlaN Dms module behavior or integration.
GovOPlaN Docs module behavior or integration.
GovOPlaN Encryption key custody, cryptographic policy, and E2EE integration.
GovOPlaN Erp module behavior or integration.
GovOPlaN Evaluation module behavior or integration.
GovOPlaN files module behavior or integration.
GovOPlaN Fit Connect module behavior or integration.
GovOPlaN Forms module behavior or integration.
GovOPlaN Forms Runtime module behavior or integration.
GovOPlaN Helpdesk module behavior or integration.
GovOPlaN Identity module behavior or integration.
GovOPlaN Identity Trust module behavior or integration.
GovOPlaN Idm module behavior or integration.
GovOPlaN Ledger module behavior or integration.
GovOPlaN mail module behavior or integration.
GovOPlaN Mandates, jurisdiction, responsibility, and authority behavior or integration.
GovOPlaN Notifications module behavior or integration.
GovOPlaN Ops module behavior or integration.
GovOPlaN Organizations module behavior or integration.
GovOPlaN procedure Parties, representation, and delivery-authority behavior or integration.
GovOPlaN Payments module behavior or integration.
GovOPlaN Permits module behavior or integration.
GovOPlaN Policy module behavior or integration.
GovOPlaN Poll module behavior or integration.
GovOPlaN Portal module behavior or integration.
GovOPlaN Postbox module behavior or integration.
GovOPlaN Projects module behavior or integration.
GovOPlaN configurable task-local Quick Access behavior and integrations.
GovOPlaN Records and eAkte lifecycle behavior or integration.
GovOPlaN Reporting module behavior or integration.
GovOPlaN Risk Compliance module behavior or integration.
GovOPlaN Scheduling module behavior or integration.
GovOPlaN Search module behavior or integration.
GovOPlaN versioned institutional Services behavior or integration.
GovOPlaN Tasks module behavior or integration.
GovOPlaN Templates module behavior or integration.
GovOPlaN Tenancy module behavior or integration.
GovOPlaN Tickets module behavior or integration.
GovOPlaN governed task views, interface projections, and workflow view integration.
GovOPlaN Voting module behavior or integration.
GovOPlaN Wiki module behavior or integration.
GovOPlaN Workflow module behavior or integration.
GovOPlaN Workflow Engine runtime, persistence, or integration.
GovOPlaN Xoev module behavior or integration.
GovOPlaN Xrechnung module behavior or integration.
GovOPlaN Xta Osci module behavior or integration.
priority
p0
Immediate stop-the-line priority.
priority
p1
High priority for the next focused work window.
priority
p2
Normal planned priority.
priority
p3
Low priority or opportunistic cleanup.
Imported from markdown backlog, roadmap, plan, or TODO files.
Created from a structured security or code-quality audit report.
Imported from inline TODO/FIXME/HACK markers by the Gitea TODO importer.
status
blocked
Cannot progress without a decision, dependency, credential, or external change.
status
in-progress
Currently being worked.
status
needs-info
Needs clarifying input before implementation can proceed safely.
status
ready
Ready for implementation.
status
triage
Needs review, ownership, priority, or acceptance criteria.
type
bug
A reproducible defect, regression, or incorrect behavior.
type
debt
Cleanup, refactoring, risk reduction, or deferred engineering work.
type
docs
Documentation, process, or developer workflow work.
type
feature
New user-visible behavior or platform capability.
type
task
Implementation, maintenance, migration, or operational work.
type
user-story
End-to-end user journey or real-world process story used to steer product slices.
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: GovOPlaN/govoplan-files#45
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Select an existing managed archive and unpack server-side using the existing preview, password, member-selection and destination dialog. Source remains unchanged. Enforce source byte access, destination upload/ownership, connector policy, source-version-bound tokens, existing path/size limits and stale preview rejection. No browser download/reupload. Add backend/UI regression and EN/DE docs.
Implementation started locally for the 2026-09-07 usability review. Existing uncommitted Campaign repairs are preserved. No live user imports or settings changes for tests; leave open until committed and delivered.
Local implementation and verification — 2026-09-07 usability slice (not yet committed/pushed).
Select one supported managed archive and use Unpack archive / Archiv entpacken in the toolbar or context menu. Choose a destination, then reuse the existing password/preview/member-selection/confirmation dialog. The source archive remains intact. Server reads verified managed bytes without a browser download/reupload. New preview/confirm routes require read, download and upload authority; enforce owner/share/tenant access, current source-version matching (including the verified read), quarantine/integrity, archive limits and connector policy. Sealed previews bind actor, tenant, source/version, destination, digest and expiry. Confirmation rechecks authority, rejects collisions and rolls back failed imports.
The dialog explicitly warns that extracted members use ordinary destination storage; archive passwords/source envelope encryption are not automatically inherited. This is not a background-job/progress-performance overhaul: existing extraction pipeline remains in use. English/German module topics, administrator consequences and Files handbook updated.
Evidence: full Files backend 185 tests plus 41 subtests, including 16 managed-archive HTTP tests; five real FilesPage browser cases (EN/DE, selection/destination, password, errors, permissions and busy Escape guard) within passing 47-case conformance suite. Browser tests use mocked APIs; backend tests use isolated databases/storage. Live instance confirms the new action is present and disabled without a valid selection; no live archive was imported or user file changed. Strict endpoint inventory and 72-manifest checks pass.
Delivery state: keep open until reviewed/committed/pushed; this note records local verified work only.
Follow-up implemented locally: both archive upload and managed-file unpack use the shared blurred dialog overlay without envelope animation. Numeric transfer/extraction file and byte counters distinguish processing from final transaction commit; unknown progress stays indeterminate. Busy content is inert and closing is blocked until the synchronous operation finishes.
Performance work: UI preview stages one bounded private copy, reused for password repreview and confirmation (no second network upload); cancellation/replacement and successful confirmation release it. Actor-bound signed token/digest validation, private filesystem modes, byte/count quotas, nonrenewing TTL and active POSIX leases protect staging. Optional libarchive accelerates compatible Legacy ZIPCrypto while Python preflight, path/type/size/CRC checks and rollback remain intact. Members stream one at a time, deployment transport is reused within an archive operation, and upload responses use batched metadata lookup. Durable recovery remains enabled.
Measured decoder-only benchmark: 4 MiB ~0.073s native versus ~5.92s Python (~81×). This is not a whole-import speed guarantee. Many-small-file durability bookkeeping remains significant (41,000 of 50,000 SQL statements in the isolated 1,000-file benchmark).
Verification so far: all 225 Files tests plus 56 subtests; nine actual-client behavior regressions (expiry, no automatic confirmation retry, polling errors, genuine transfer counters); 51/51 full shared browser conformance tests; production build and budgets; all 72 manifest checks. Live upload→preview→cancel returned 200/204 without importing managed files. EN/DE workflow and operator docs describe temporary retention/cleanup, settings and multi-worker deployment requirements.
Changes remain uncommitted/unpushed; issue stays open pending publication. The broad focused check stops at the already-known unrelated institutional governance journey failure.
Final verification update: full Files suite now 228 passed plus 60 subtests; actual Files/Core client behavior suite 10 passed. Added real ORM response parity/query tests: 64 assets with shares require 3 SELECTs in the batched path versus 256 per-item, preserving lifecycle, provenance, ordered share state and sent-use audit flags. This measures response construction only. Four Access migration regressions pass; live Function mappings list and delta both return200 (tracked in Access #20). All 72 final manifest checks and shared UI contracts pass. Previous 51/51 browser and production-budget results remain valid. Local changes are still uncommitted/unpushed.
Reconciled 2026-09-08: implemented and published
This supersedes the earlier local/unpublished status. The owning fix is on remote
mainand the verifiedv0.1.26tag (commitff84812f7f15), included in the published 0.1.45 source/package composition.Already-uploaded managed archives use the existing preview/password/member/destination flow without browser download/reupload. Managed-archive backend tests cover source/destination authorization, source-version and actor binding, expiry/revocation, connector policy, collisions/rollback and encrypted/archive bounds;
managed-archive.spec.tscovers the actual UI. Owning handbook and EN/DE DocumentationTopics are included. No user archive was imported during this reconciliation.The completed, unmodified release
tools/checks/check-focused.shrun passed, including 213 browser conformance cases and the relevant backend suites. The audit matched current remote branches/tags and reviewed the original acceptance criteria and subsequent comments. Closing the implemented source/package scope. This is not a runtime deployment claim: Meta #52 and website #9 retain their independent runtime/public-site holds. No tag was moved.