Complete map refresh guards and fix the dashboard job embed

This commit is contained in:
2026-10-06 12:18:22 +05:00
parent 923abdc472
commit 5f43e97d32
11 changed files with 127 additions and 27 deletions

View File

@@ -1,5 +1,15 @@
# Verification of the export/upload fixes
## Map refresh completion (October 5, 2026)
The unfinished "map refresh" commit was completed. A follow-up migration (`20261005200000_map_refresh_fixes.sql`) restores the contribution server-address check in `submit_draft` that the map-refresh migration had accidentally dropped, and rejects map-refresh jobs both when queued (`refresh_map`) and completed (`complete_job`) for contribution datasets. The map page now receives the job `kind`, so refresh progress, the refreshing notice and the failure alert render; refresh controls and the Map tools anchor are hidden on contributions; map-only worker downloads report progress against the filtered asset list; the plugin help text describes the owner/guest limits.
The 743 MiB `minecraft/java_pid42664.hprof` heap dump, tracked since the first commit, was purged from all Git history with `git filter-branch`, expired reflogs and `git gc`; `*.hprof` is now ignored. The local repository's `.git` directory shrank from about 170 MiB to 1.2 MiB. The rewritten history has not been pushed; because every commit hash changed, the remote needs a force-push before further work is pulled elsewhere.
Verification at the user's request was limited to local checks: all 65 Node tests and TypeScript checking passed under Node 22, and both Minecraft JARs were rebuilt with the updated help text. `tests/sql/map-refresh.sql` now includes contribution-refresh guard cases. The new migration has not been applied to the configured Supabase project, and the SQL, plugin, renderer and browser regressions were not rerun in this pass. The user had already run the plugin regression with Codex before these fixes.
---
## Panorama contributions (October 5, 2026)
Maps now retain up to 24 captures. Server exports pick random safe positions, and games retain five distinct random rounds. Owners opt into contributions by map ID; non-owners have a cumulative 12-panorama quota. Contributions need owner acceptance and a subsequent moderator review of the combined map/update.