engineering/zebra-report
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

zebra-spaces: don't truncate uuids in the latency panel

Browse source 
Fox 2026-06-04: 'don't truncate uuids in the latency page'. Mesh
peer rows previously showed `peer abcd…wxyz` (shortHex 4+4 chars)
when no handle was known, or just `peer HANDLE` (uuid hidden) when
it was. Neither is useful for QA — same shortHex prefix can collide
across sessions, and handle alone makes it hard to correlate with
SFU/signal logs.

New format: `peer HANDLE FULL_UUID` when both known, else just
`peer FULL_UUID`. Full 32-char hex always present.
This commit is contained in:
Russell Ballestrini 2026-06-04 13:17:14 -04:00
parent 1449f40954
commit 545ba93557
No known key found for this signature in database
1 changed files with 9 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

14
web/zebra-spaces.html
View file

@ -5097,11 +5097,15 @@ async function refreshLatency(){
if (sfuCameraPC){ rows.push({ name: 'sfu camera out', pc: sfuCameraPC, key: 'camera' }); }
/* SFU subscriber — carries every incoming stream from other speakers */
if (sfuSubPC){ rows.push({ name: 'sfu in (host + screen + cams)', pc: sfuSubPC, key: 'sub' }); }
/* mesh peers — one row each */
/* mesh peers — one row each. Show the FULL uuid (no shortHex) so
* QA can pin which session is which without scrolling logs — fox
* 2026-06-04 "don't truncate uuids in the latency page". When we
* have a handle, prepend it for human readability. */
for (const [uuid, pc] of peers){
const mm = members.get(uuid);
const handle = (mm && mm.handle) || shortHex(uuid);
rows.push({ name: 'peer '+handle, pc, key: 'mesh-'+uuid });
const handle = mm && mm.handle;
const name = handle ? ('peer ' + handle + ' ' + uuid) : ('peer ' + uuid);
rows.push({ name, pc, key: 'mesh-'+uuid });
}
const container = $('latency-rows');
if (!container) return;
@ -5564,8 +5568,8 @@ logLine('', 'ready — pick a handle, type a rendezvous code, enter the space');
<footer style="margin:2.2rem auto 0;font-size:0.65rem;color:#999;line-height:1.7;word-break:break-all;font-family:monospace">
<span id="pi-seal" style="color:#777;cursor:default;user-select:none" title="">page integrity</span> &nbsp;·&nbsp; built <span class="stamp-date">2026-06-04</span><br>
md5 <span class="stamp-md5">5b381f795d544a2b593dd2b27ff065b8</span><br>
sha256 <span class="stamp-sha">ff9598d4a1588c76c01fae4fef3333a38b7af8ddd092239af234e7dc54bffe11</span><br>
md5 <span class="stamp-md5">3a81cec9d5083e29337b765f990cbc04</span><br>
sha256 <span class="stamp-sha">eddd7edb4e785e606f1afe03460c56796864a3bc78a0b8f9a5e9357e886883e3</span><br>
<span style="color:#bbb">hashes are of this page with these two fields zeroed — to verify, blank them and re-hash</span><br>
<span style="color:#bbb">one self-contained file — <strong>save a copy</strong> and verify against these hashes; point at your own servers with ?signal= and ?turncred=, or <a href="host-your-own.html" style="color:#999">host your own community</a></span>
</footer>