bot: update 2026-01-06

github-actions · github-actions · commit a40ba924b075 · 2026-01-06T03:46:06.000Z
diff --git a/archive/_21ddsEwXlCWnreEGuqXZ_3Apolkadot.io/index.html b/archive/_21ddsEwXlCWnreEGuqXZ_3Apolkadot.io/index.html
@@ -18,7 +18,7 @@
 em{font-style:italic}
 </style>
 <h1>#graypaper:polkadot.io</h1>
-<p><small>last updated 2026-01-05 03:48 UTC</small></p>
+<p><small>last updated 2026-01-06 03:45 UTC</small></p>
 <p><a href='room_log.txt'>⇩ plaintext</a> · <a href='../../'>⇦ all rooms</a></p>
 <hr>
 <div class='msg'><a class='ts' href='#$G0deSwnlYlCrSn5lIFL__hi6bgWVITql5VyahU4bzpI'>#</a> <a class='ts' name='$G0deSwnlYlCrSn5lIFL__hi6bgWVITql5VyahU4bzpI' href='https://matrix.to/#/!ddsEwXlCWnreEGuqXZ:polkadot.io/$G0deSwnlYlCrSn5lIFL__hi6bgWVITql5VyahU4bzpI' target='_blank'>2024-04-17 20:29</a>&ensp;<span class='u' style='color:#da6aa2'>syed</span>: <a href="https://matrix.to/#/!hyzRkDqDthePbodYFz:parity.io/$f_DMsIEcDXZegw6Sabnehzc-LrdDQkmq5MbxDDyoZxY?via=parity.io&amp;via=web3.foundation" rel="noopener" target="_blank">https://matrix.to/#/!hyzRkDqDthePbodYFz:parity.io/$f_DMsIEcDXZegw6Sabnehzc-LrdDQkmq5MbxDDyoZxY?via=parity.io&amp;via=web3.foundation</a>
diff --git a/archive/_21ddsEwXlCWnreEGuqXZ_3Apolkadot.io/room_log.txt b/archive/_21ddsEwXlCWnreEGuqXZ_3Apolkadot.io/room_log.txt
@@ -1,5 +1,5 @@
 # room: #graypaper:polkadot.io
-# exported: 2026-01-05 03:48 UTC
+# exported: 2026-01-06 03:45 UTC
 2024-04-17 20:29 syed: https://matrix.to/#/!hyzRkDqDthePbodYFz:parity.io/$f_DMsIEcDXZegw6Sabnehzc-LrdDQkmq5MbxDDyoZxY?via=parity.io&via=web3.foundation
 
 2024-04-17 20:29 syed: 
diff --git a/archive/_21ksYpYHcVftKsUAsdMa_3Amatrix.org/index.html b/archive/_21ksYpYHcVftKsUAsdMa_3Amatrix.org/index.html
@@ -18,7 +18,7 @@
 em{font-style:italic}
 </style>
 <h1>#jam-conformance:matrix.org</h1>
-<p><small>last updated 2026-01-05 03:49 UTC</small></p>
+<p><small>last updated 2026-01-06 03:46 UTC</small></p>
 <p><a href='room_log.txt'>⇩ plaintext</a> · <a href='../../'>⇦ all rooms</a></p>
 <hr>
 <div class='msg'><a class='ts' href='#$_9hLINsChVG8rufQkmbqp-fIbsNyK1YqpS3C9S7QZHU'>#</a> <a class='ts' name='$_9hLINsChVG8rufQkmbqp-fIbsNyK1YqpS3C9S7QZHU' href='https://matrix.to/#/!ksYpYHcVftKsUAsdMa:matrix.org/$_9hLINsChVG8rufQkmbqp-fIbsNyK1YqpS3C9S7QZHU' target='_blank'>2025-08-20 15:56</a>&ensp;<span class='u' style='color:#787fdf'>erin</span>: tomusdrw: i&#x27;ve set up the archiver to archive this also, so hopefully will be up starting tomorrow</div>
@@ -1685,3 +1685,4 @@ <h1>#jam-conformance:matrix.org</h1>
 I will check this afternoon on jampy 👍</div>
 <div class='msg reply'><a class='ts' href='#$bPKvz2_WC3kWxRGQi-zegeeMUyDBYCYd9nzgP5jovzQ'>#</a> <a class='ts' name='$bPKvz2_WC3kWxRGQi-zegeeMUyDBYCYd9nzgP5jovzQ' href='https://matrix.to/#/!ksYpYHcVftKsUAsdMa:matrix.org/$bPKvz2_WC3kWxRGQi-zegeeMUyDBYCYd9nzgP5jovzQ' target='_blank'>2026-01-04 14:33</a>&ensp;<span class='u' style='color:#d470bf'>jaymansfield</span>: 39/41 pass. I reject 40 for duplicate core indexes in guarantees.</div>
 <div class='msg reply'><a class='ts' href='#$-O3hl3Rjj3Z6HCUVo0n2Tktv5wLJA0x9HjCdHUgMPjQ'>#</a> <a class='ts' name='$-O3hl3Rjj3Z6HCUVo0n2Tktv5wLJA0x9HjCdHUgMPjQ' href='https://matrix.to/#/!ksYpYHcVftKsUAsdMa:matrix.org/$-O3hl3Rjj3Z6HCUVo0n2Tktv5wLJA0x9HjCdHUgMPjQ' target='_blank'>2026-01-04 15:36</a>&ensp;<span class='u' style='color:#bfaf39'>dakkk</span>: I tested again on jampy, block 39 is ok, block 40 is rejected for invalid guarantee order, and block 41 is ok; the trace for block 40 has the same pre and post state root, so rejected the block is correct</div>
+<div class='msg reply'><a class='ts' href='#$dCA9sUTbkaXDCQT5bWCifWBVl0GAG68T2iT-1hbbvqQ'>#</a> <a class='ts' name='$dCA9sUTbkaXDCQT5bWCifWBVl0GAG68T2iT-1hbbvqQ' href='https://matrix.to/#/!ksYpYHcVftKsUAsdMa:matrix.org/$dCA9sUTbkaXDCQT5bWCifWBVl0GAG68T2iT-1hbbvqQ' target='_blank'>2026-01-05 16:06</a>&ensp;<span class='u' style='color:#be2950'>clearloop</span>: Thanks! so likely I got some problems in our implementations, I thought the ex hash check is conflict with other tests</div>
diff --git a/archive/_21ksYpYHcVftKsUAsdMa_3Amatrix.org/room_log.txt b/archive/_21ksYpYHcVftKsUAsdMa_3Amatrix.org/room_log.txt
@@ -1,5 +1,5 @@
 # room: #jam-conformance:matrix.org
-# exported: 2026-01-05 03:49 UTC
+# exported: 2026-01-06 03:46 UTC
 2025-08-20 15:56 erin: tomusdrw: i've set up the archiver to archive this also, so hopefully will be up starting tomorrow
 2025-08-21 06:33 ascriv: https://github.com/davxy/jam-conformance/issues/26 should we not discourage open source implementations (for now)? [edited]
 2025-08-21 10:27 oliver.tale-yazdi: I think open source repos are fine. Other implementors are just not supposed to look at it
@@ -1690,3 +1690,4 @@ Maybe the invalid extrinsic is the expected result?
 I will check this afternoon on jampy 👍
   ↳ 2026-01-04 14:33 jaymansfield: 39/41 pass. I reject 40 for duplicate core indexes in guarantees.
   ↳ 2026-01-04 15:36 dakkk: I tested again on jampy, block 39 is ok, block 40 is rejected for invalid guarantee order, and block 41 is ok; the trace for block 40 has the same pre and post state root, so rejected the block is correct
+  ↳ 2026-01-05 16:06 clearloop: Thanks! so likely I got some problems in our implementations, I thought the ex hash check is conflict with other tests
diff --git a/archive/_21wBOJlzaOULZOALhaRh_3Apolkadot.io/index.html b/archive/_21wBOJlzaOULZOALhaRh_3Apolkadot.io/index.html
@@ -18,7 +18,7 @@
 em{font-style:italic}
 </style>
 <h1>#jam:polkadot.io</h1>
-<p><small>last updated 2026-01-05 03:48 UTC</small></p>
+<p><small>last updated 2026-01-06 03:45 UTC</small></p>
 <p><a href='room_log.txt'>⇩ plaintext</a> · <a href='../../'>⇦ all rooms</a></p>
 <hr>
 <div class='msg'><a class='ts' href='#$we4SYXTHwmKn094X9Zs_7mWUOoUVh4icvVdxD83RZfs'>#</a> <a class='ts' name='$we4SYXTHwmKn094X9Zs_7mWUOoUVh4icvVdxD83RZfs' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$we4SYXTHwmKn094X9Zs_7mWUOoUVh4icvVdxD83RZfs' target='_blank'>2024-04-20 02:08</a>&ensp;<span class='u' style='color:#d0709e'>johnjiao123</span>: </div>
@@ -12215,3 +12215,6 @@ <h1>#jam:polkadot.io</h1>
  - Is the builder responsible for knowing to each validator it should send the work package? In this case, what criteria the builder uses to choose which of the 3 possible validators?</div>
 <div class='msg'><a class='ts' href='#$mcakN6rsuEtKzoP5suLlD7qouc_TH-jy1g7Dx0ctXwI'>#</a> <a class='ts' name='$mcakN6rsuEtKzoP5suLlD7qouc_TH-jy1g7Dx0ctXwI' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$mcakN6rsuEtKzoP5suLlD7qouc_TH-jy1g7Dx0ctXwI' target='_blank'>2026-01-01 11:54</a>&ensp;<span class='u' style='color:#c65779'>dave</span>: You should allow a bit of leeway but if the core is not currently assigned to you then you can just close the stream with an error</div>
 <div class='msg'><a class='ts' href='#$klg_7PGTRbwBIFlGBM7lOy2-ML_NattNVC0uTzl3d5k'>#</a> <a class='ts' name='$klg_7PGTRbwBIFlGBM7lOy2-ML_NattNVC0uTzl3d5k' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$klg_7PGTRbwBIFlGBM7lOy2-ML_NattNVC0uTzl3d5k' target='_blank'>2026-01-01 11:57</a>&ensp;<span class='u' style='color:#c65779'>dave</span>: Yes, the builder needs to decide which validator to send to. Picking randomly amongst the 3 assigned is a good start but obviously you may want to fall back to one of the others if submitting to the first randomly selected one doesn&#x27;t work</div>
+<div class='msg'><a class='ts' href='#$oWHP3O6efgxIA3aGbx8nZ01UbtEWUxBvm6pBQCLjX7U'>#</a> <a class='ts' name='$oWHP3O6efgxIA3aGbx8nZ01UbtEWUxBvm6pBQCLjX7U' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$oWHP3O6efgxIA3aGbx8nZ01UbtEWUxBvm6pBQCLjX7U' target='_blank'>2026-01-05 13:17</a>&ensp;<span class='u' style='color:#35a646'>igankevich</span>: This error means that the program blob lacks metadata.
+
+I&#x27;ve updated <code>polkaports</code> to fix the issue. Simply pull the repo and run setup &amp; quake compilation steps again. You might need to run <code>make clean</code> in <code>quake</code> directory to remove old program blob.</div>
diff --git a/archive/_21wBOJlzaOULZOALhaRh_3Apolkadot.io/room_log.txt b/archive/_21wBOJlzaOULZOALhaRh_3Apolkadot.io/room_log.txt
@@ -1,5 +1,5 @@
 # room: #jam:polkadot.io
-# exported: 2026-01-05 03:48 UTC
+# exported: 2026-01-06 03:45 UTC
 2024-04-20 02:08 johnjiao123: 
 2024-04-20 02:09 johnjiao123: 
 2024-05-30 21:48 nradko: Hey everyone,
@@ -12325,3 +12325,6 @@ For present purposes, PolkaJAM may be used as a reasonable target for that behav
  - Is the builder responsible for knowing to each validator it should send the work package? In this case, what criteria the builder uses to choose which of the 3 possible validators?
 2026-01-01 11:54 dave: You should allow a bit of leeway but if the core is not currently assigned to you then you can just close the stream with an error
 2026-01-01 11:57 dave: Yes, the builder needs to decide which validator to send to. Picking randomly amongst the 3 assigned is a good start but obviously you may want to fall back to one of the others if submitting to the first randomly selected one doesn't work
+2026-01-05 13:17 igankevich: This error means that the program blob lacks metadata.
+
+I've updated `polkaports` to fix the issue. Simply pull the repo and run setup & quake compilation steps again. You might need to run `make clean` in `quake` directory to remove old program blob.
