pmtiles-swarm 0.5.5 → 0.5.6

package/CHANGELOG.md

@@ -7,6 +7,19 @@
 ### 🐞 Bug fixes
 - _...Add new stuff here..._
 
+## 0.5.6
+### 🐞 Bug fixes
+- **The Pieces and Peers tabs redraw themselves.** A detail pane is filled once, the first time
+  it is opened — right for the panes describing an archive, whose name and source and trackers
+  do not change, and wrong for the two describing what is happening *now*. Pieces arrived and
+  peers came and went behind a picture taken when the tab was opened, and the only way to see
+  the current one was to close the panel and open it again, or reload the page. Those two now
+  follow the same three-second tick as the archive table. The rest stay lazy, since redrawing a
+  pane nobody is watching is requests every tick for nothing — which is why they load on demand
+  in the first place. Only while visible, and never queued behind a redraw still in flight: a
+  piece map of a large archive is a real request, and three seconds is not long enough to assume
+  the last one finished.
+
 ## 0.5.5
 ### 🐞 Bug fixes
 - **An archive could retire itself from head-warming and never say so.** The test for "already

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pmtiles-swarm",
-  "version": "0.5.5",
+  "version": "0.5.6",
   "description": "BitTorrent distribution for PMTiles map archives: create torrents, watch folders, publish and subscribe to RSS feeds, and seed through qBittorrent or an embedded client",
   "type": "module",
   "main": "src/index.js",

package/src/web/index.html

@@ -729,6 +729,21 @@
       // before the node has said whether its engine applies one.
       let incompleteMarker = null;
       let activeTab = 'general';
+      /**
+       * Panes worth redrawing while they are open.
+       *
+       * A detail pane is filled once, the first time it is shown, which is
+       * right for the ones describing an archive: its name, its source, its
+       * trackers. It is wrong for these two, which describe what is happening
+       * *now* — pieces arriving and peers coming and going — and which sat
+       * frozen until the reader thought to close the panel and open it again.
+       *
+       * The rest stay as they are. Refreshing a pane nobody is watching is
+       * four requests a tick for nothing, which is why they are loaded lazily
+       * in the first place.
+       */
+      const LIVE_PANES = new Set(['pieces', 'peers']);
+      let refreshingPane = false;
 
       // What the header switch shows, so a click knows what it is toggling to.
       let speedState = null;
@@ -894,6 +909,7 @@
             ` · <b>${status.archives}</b> archives`;
           archives = list;
           renderRows();
+          refreshOpenPane();
         } catch (error) {
           $('status').textContent = `disconnected: ${error.message}`;
         }
@@ -1072,6 +1088,29 @@
           ({ '&': '&amp;', '<': '&lt;', '>': '&gt;', '"': '&quot;', "'": '&#39;' })[c],
         );
 
+      /**
+       * Redraws the open detail pane, when it is one that changes by itself.
+       *
+       * Guarded against overlapping, because a piece map of a large archive is
+       * a real request and a slow one must not have a queue of its successors
+       * behind it.
+       * @returns {void}
+       */
+      function refreshOpenPane() {
+        if (refreshingPane || !selected || !LIVE_PANES.has(activeTab)) return;
+        const pane = document.querySelector(`[data-pane="${activeTab}"]`);
+        // Only while it is on screen: a hidden pane is one the reader moved
+        // away from, and the panel may have been replaced since.
+        if (!pane || pane.hidden) return;
+
+        refreshingPane = true;
+        Promise.resolve(fillPane(activeTab, selected))
+          .catch(() => {})
+          .finally(() => {
+            refreshingPane = false;
+          });
+      }
+
       /**
        * Fills one detail tab, the first time it is opened.
        * @param {string} name - Which pane.