Reth node always one or two block behind

Describe the bug
I notice the problem since beta6 and then update to beta7 and same problem, sometimes it gets even up to 16 blocks behind in comparation with infura, alchecmy, thirdweb and quicknode. Those are the one im using to compare the current block number of the chain
Steps to reproduce
Im running the full node archive mode
Node logs
Excecution layer
2024-05-18T15:18:16.939895Z  INFO Pruner finished tip_block_number=19897672 elapsed=165.82µs stats={}
2024-05-18T15:18:24.897206Z  INFO Block added to canonical chain number=19897674 hash=0x87f9d1df11ad1b15f85c111012e648af384b1d8ac2081b4d0f07a2824fa382b5 peers=100 txs=206 mgas=17.073 full=56.9% base_fee=3.49gwei blobs=0 excess_blobs=0 elapsed=6.903115257s
2024-05-18T15:18:38.832849Z  INFO Canonical chain committed number=19897673 hash=0xd4be87072a5a8a12250b36fd285bb43d09ceb10717ede4844b48255c8e477626 elapsed=11.631425426s
2024-05-18T15:18:41.630659Z  INFO Block added to canonical chain number=19897675 hash=0xde383ed89032ba72a979c6203f4ec9bc8b67845dfc81b399386bdce316bd1d64 peers=100 txs=165 mgas=18.030 full=60.1% base_fee=3.55gwei blobs=1 excess_blobs=0 elapsed=2.796589659s
2024-05-18T15:18:58.132999Z  INFO Canonical chain committed number=19897674 hash=0x87f9d1df11ad1b15f85c111012e648af384b1d8ac2081b4d0f07a2824fa382b5 elapsed=16.502329284s
2024-05-18T15:18:58.135229Z  INFO Block is already canonical, ignoring. block_hash=0x87f9d1df11ad1b15f85c111012e648af384b1d8ac2081b4d0f07a2824fa382b5
2024-05-18T15:18:58.136362Z  INFO Forkchoice updated head_block_hash=0x87f9d1df11ad1b15f85c111012e648af384b1d8ac2081b4d0f07a2824fa382b5 safe_block_hash=0x292308250e894687675b64c6c24af364a512d516df1f5869df090e831a26eb23 finalized_block_hash=0x96eb7ca6f5f7f3041001556d9ee87b857d868a12f01beb78f3ffa799af0fd9cb
2024-05-18T15:19:00.966816Z  INFO Block added to canonical chain number=19897676 hash=0x87adce5cb58053abeb1d498cf6823fb47cdf6d6dabab5171b6976a992394e451 peers=100 txs=157 mgas=13.830 full=46.1% base_fee=3.64gwei blobs=6 excess_blobs=0 elapsed=2.224231737s
2024-05-18T15:19:04.432175Z  INFO Block added to canonical chain number=19897677 hash=0x2d8a55cc042bd14aa418eb63c0c372ff7d7e935a22e9590ed934f065e77ab9a4 peers=100 txs=159 mgas=18.137 full=60.5% base_fee=3.61gwei blobs=6 excess_blobs=3 elapsed=1.983393156s
2024-05-18T15:19:25.938709Z  INFO Status connected_peers=100 freelist=242610 latest_block=19897674
2024-05-18T15:19:38.385144Z  INFO Canonical chain committed number=19897675 hash=0xde383ed89032ba72a979c6203f4ec9bc8b67845dfc81b399386bdce316bd1d64 elapsed=33.952978068s
2024-05-18T15:19:39.167565Z  INFO Block added to canonical chain number=19897678 hash=0x9e948f38aa6d8026413877d540ef5ecee8ec907df64de18d8590a13a781fd85c peers=100 txs=137 mgas=11.559 full=38.5% base_fee=3.70gwei blobs=2 excess_blobs=6 elapsed=781.585982ms
2024-05-18T15:19:41.597581Z  INFO Canonical chain committed number=19897677 hash=0x2d8a55cc042bd14aa418eb63c0c372ff7d7e935a22e9590ed934f065e77ab9a4 elapsed=2.42992923s
2024-05-18T15:19:46.210707Z  INFO Pruner started tip_block_number=19897677
2024-05-18T15:19:46.210876Z  INFO Pruner finished tip_block_number=19897677 elapsed=134.353µs stats={}
2024-05-18T15:19:47.597653Z  INFO Block added to canonical chain number=19897679 hash=0xc417683b552126b96d8a98ee55e0c846d880f96fa6b323f8b562b2e7ec896c03 peers=100 txs=182 mgas=16.180 full=53.9% base_fee=3.59gwei blobs=0 excess_blobs=5 elapsed=1.093411337s
2024-05-18T15:19:49.848971Z  INFO Block added to canonical chain number=19897680 hash=0x1f239673ecc44f7c235d08fa219d1d85fd485880461749164f3b5513fad2d227 peers=100 txs=159 mgas=14.143 full=47.1% base_fee=3.63gwei blobs=0 excess_blobs=2 elapsed=2.106397002s
2024-05-18T15:19:50.938803Z  INFO Status connected_peers=100 freelist=242090 latest_block=19897677
2024-05-18T15:19:52.959255Z  INFO Canonical chain committed number=19897678 hash=0x9e948f38aa6d8026413877d540ef5ecee8ec907df64de18d8590a13a781fd85c elapsed=3.11020209s
2024-05-18T15:19:55.640453Z  INFO Block added to canonical chain number=19897681 hash=0x461c3e7d7d50fd1b7eece78a0e7dbc0f0b92f528d4ab6f5cd253b0bc10322039 peers=100 txs=146 mgas=22.546 full=75.2% base_fee=3.60gwei blobs=3 excess_blobs=0 elapsed=2.680187775s
2024-05-18T15:19:57.916561Z  INFO Canonical chain committed number=19897679 hash=0xc417683b552126b96d8a98ee55e0c846d880f96fa6b323f8b562b2e7ec896c03 elapsed=2.275972936s
2024-05-18T15:19:59.795369Z  INFO Canonical chain committed number=19897681 hash=0x461c3e7d7d50fd1b7eece78a0e7dbc0f0b92f528d4ab6f5cd253b0bc10322039 elapsed=1.878196898s
2024-05-18T15:20:00.282936Z  INFO Block added to canonical chain number=19897682 hash=0x3140ca80b3d4400a8e648e0ae8f56601ff1efaa01429fb49ff905acf6b8db7a2 peers=100 txs=124 mgas=8.111 full=27.0% base_fee=3.83gwei blobs=0 excess_blobs=0 elapsed=411.625652ms
2024-05-18T15:20:00.766783Z  INFO Block added to canonical chain number=19897683 hash=0x7f2c2c3bebe1dfc2353d49fb891388694c2d48988ec770d088901e5b45aa0f1a peers=100 txs=58 mgas=2.847 full=9.5% base_fee=3.61gwei blobs=0 excess_blobs=0 elapsed=218.54478ms
2024-05-18T15:20:01.455326Z  INFO Canonical chain committed number=19897683 hash=0x7f2c2c3bebe1dfc2353d49fb891388694c2d48988ec770d088901e5b45aa0f1a elapsed=421.640381ms
2024-05-18T15:20:14.825564Z  INFO Block added to canonical chain number=19897684 hash=0x066bdf313e9a6262fc67e0868fec33da8a88bacd5c7cdf69857cb7bf56ce4a5a peers=100 txs=337 mgas=23.601 full=78.7% base_fee=3.24gwei blobs=0 excess_blobs=0 elapsed=2.054135118s
2024-05-18T15:20:14.825615Z  INFO Pruner started tip_block_number=19897683
2024-05-18T15:20:14.825779Z  INFO Pruner finished tip_block_number=19897683 elapsed=145.299µs stats={}
2024-05-18T15:20:16.283497Z  INFO Canonical chain committed number=19897684 hash=0x066bdf313e9a6262fc67e0868fec33da8a88bacd5c7cdf69857cb7bf56ce4a5a elapsed=1.163081574s
2024-05-18T15:20:25.577990Z  INFO Block added to canonical chain number=19897685 hash=0xdcb843d2da57b2872732a029815b030279a410fa6593b9a377ecdf0e9b60fecc peers=100 txs=168 mgas=15.757 full=52.5% base_fee=3.48gwei blobs=0 excess_blobs=0 elapsed=529.70003ms
2024-05-18T15:20:26.557419Z  INFO Canonical chain committed number=19897685 hash=0xdcb843d2da57b2872732a029815b030279a410fa6593b9a377ecdf0e9b60fecc elapsed=693.155572ms
2024-05-18T15:20:36.889033Z  INFO Block added to canonical chain number=19897686 hash=0x5ca490cb61fcb04d0d0c5dc949f9ec0f406166076605ed2c8422825aac638909 peers=100 txs=26 mgas=3.551 full=11.8% base_fee=3.50gwei blobs=0 excess_blobs=0 elapsed=338.436809ms
2024-05-18T15:20:41.029939Z  INFO Canonical chain committed number=19897686 hash=0x5ca490cb61fcb04d0d0c5dc949f9ec0f406166076605ed2c8422825aac638909 elapsed=3.87438031s
2024-05-18T15:20:53.064255Z  INFO Block added to canonical chain number=19897687 hash=0x9d4f3477be755b165b9b7b89ba21cd05a65e9f561e0fee0b865c85076a6491cd peers=100 txs=330 mgas=25.017 full=83.4% base_fee=3.16gwei blobs=0 excess_blobs=0 elapsed=3.717518851s
2024-05-18T15:21:10.617199Z  INFO Canonical chain committed number=19897687 hash=0x9d4f3477be755b165b9b7b89ba21cd05a65e9f561e0fee0b865c85076a6491cd elapsed=17.250088028s
2024-05-18T15:21:11.973433Z  INFO Block added to canonical chain number=19897688 hash=0xd08eb9f1c1c52dc293248583bdbf5cbb48e0286e94b03112675e2f6bb1b63e46 peers=98 txs=197 mgas=16.813 full=56.0% base_fee=3.43gwei blobs=6 excess_blobs=0 elapsed=1.355151976s
2024-05-18T15:21:18.660988Z  INFO Block added to canonical chain number=19897689 hash=0x801654536045270a3529ea1571e73fd914e4217714ba0f05ebdd564b8007dbbb peers=99 txs=142 mgas=12.654 full=42.2% base_fee=3.48gwei blobs=0 excess_blobs=3 elapsed=582.914554ms
2024-05-18T15:21:20.823076Z  INFO Canonical chain committed number=19897689 hash=0x801654536045270a3529ea1571e73fd914e4217714ba0f05ebdd564b8007dbbb elapsed=1.886234272s
2024-05-18T15:21:25.624020Z  INFO Pruner started tip_block_number=19897689
2024-05-18T15:21:25.624049Z  INFO Block added to canonical chain number=19897690 hash=0x6d1340b448fcbee00eb4334da50aefbf05d20c749f33764d6b526d2d840eebac peers=99 txs=136 mgas=12.752 full=42.5% base_fee=3.41gwei blobs=0 excess_blobs=0 elapsed=427.515783ms
2024-05-18T15:21:25.624195Z  INFO Pruner finished tip_block_number=19897689 elapsed=139.281µs stats={}
2024-05-18T15:21:27.500492Z  INFO Canonical chain committed number=19897690 hash=0x6d1340b448fcbee00eb4334da50aefbf05d20c749f33764d6b526d2d840eebac elapsed=1.601541004s
2024-05-18T15:21:40.937628Z  INFO Block added to canonical chain number=19
897691 hash=0xef908b8f6046c97cdc8192c9bdb3461bedc3d1736995a6eabdd8af1afb532108 peers=99 txs=226 mgas=23.828 full=79.4% base_fee=3.35gwei blobs=2 excess_blobs=0 elapsed=2.211969536s
2024-05-18T15:21:43.660532Z  INFO Canonical chain committed number=19897691 hash=0xef908b8f6046c97cdc8192c9bdb3461bedc3d1736995a6eabdd8af1afb532108 elapsed=2.422993318s
2024-05-18T15:21:50.807561Z  INFO Block added to canonical chain number=19897692 hash=0x5ca066cda27ebb6af87f378bd38b63078d2a0cfe005a86882369dc9fcea21db5 peers=98 txs=173 mgas=21.127 full=70.4% base_fee=3.60gwei blobs=6 excess_blobs=0 elapsed=560.102633ms
2024-05-18T15:21:52.591657Z  INFO Canonical chain committed number=19897692 hash=0x5ca066cda27ebb6af87f378bd38b63078d2a0cfe005a86882369dc9fcea21db5 elapsed=1.511761145s
2024-05-18T15:22:01.634056Z  INFO Block added to canonical chain number=19897693 hash=0xb7048cef70e561e39d7563a1b11d79a0bfe1067d0558aa1465b69a9898cd0fc6 peers=101 txs=117 mgas=10.411 full=34.7% base_fee=3.78gwei blobs=0 excess_blobs=3 elapsed=1.167733112s
2024-05-18T15:22:04.274501Z  INFO Canonical chain committed number=19897693 hash=0xb7048cef70e561e39d7563a1b11d79a0bfe1067d0558aa1465b69a9898cd0fc6 elapsed=2.346343134s
2024-05-18T15:22:14.386940Z  INFO Block added to canonical chain number=19897694 hash=0xe8252f20213f4485dbb5d4065f955e6b2503f3e77493192d5dd980d2fb0ca6bc peers=99 txs=175 mgas=14.858 full=49.5% base_fee=3.63gwei blobs=6 excess_blobs=0 elapsed=1.222233938s
2024-05-18T15:22:15.843689Z  INFO Pruner started tip_block_number=19897694
2024-05-18T15:22:15.843711Z  INFO Canonical chain committed number=19897694 hash=0xe8252f20213f4485dbb5d4065f955e6b2503f3e77493192d5dd980d2fb0ca6bc elapsed=1.113409409s
2024-05-18T15:22:15.843868Z  INFO Pruner finished tip_block_number=19897694 elapsed=161.227µs stats={}
2024-05-18T15:22:24.903048Z  INFO Block added to canonical chain number=19897695 hash=0x393fb676e53c4246033a8d832edc68c3c2ca42cc4e458331accba31592db295a peers=99 txs=120 mgas=9.905 full=33.0% base_fee=3.63gwei blobs=0 excess_blobs=3 elapsed=362.89492ms
2024-05-18T15:22:26.781117Z  INFO Canonical chain committed number=19897695 hash=0x393fb676e53c4246033a8d832edc68c3c2ca42cc4e458331accba31592db295a elapsed=1.61750736s
2024-05-18T15:22:36.150592Z  INFO Block added to canonical chain number=19897696 hash=0xcbf57835f184e0c46fb4440f908308e3aefebf50804d8969cbc0efbf563c689c peers=99 txs=31 mgas=2.045 full=6.8% base_fee=3.48gwei blobs=6 excess_blobs=0 elapsed=152.936003ms
2024-05-18T15:22:37.288292Z  INFO Canonical chain committed number=19897696 hash=0xcbf57835f184e0c46fb4440f908308e3aefebf50804d8969cbc0efbf563c689c elapsed=657.888878ms
2024-05-18T15:22:50.524293Z  INFO Block added to canonical chain number=19897697 hash=0x234b9c642a220e26aa80c4ae5d4204c5904c4251076543f76309d221b6bba834 peers=100 txs=217 mgas=20.884 full=69.6% base_fee=3.10gwei blobs=0 excess_blobs=3 elapsed=1.270610063s

Consensus Layer
May 18 15:22:49.093 INFO New block received                      root: 0x9e2ac7bb821602b5031b96f75f8d5b127c70ba240cd15efc23affc90a34bd130, slot: 9101812
May 18 15:22:53.000 INFO Synced                                  slot: 9101812, block: 0x9e2a…d130, epoch: 284431, finalized_epoch: 284429, finalized_root: 0xeea1…a960, exec_hash: 0x234b…a834 (verified), peers: 64, service: slot_notifier
May 18 15:23:00.470 INFO New block received                      root: 0x92313717080443a37ac76edc297596020be6ff380d5428b618e14ae517af1a73, slot: 9101813
May 18 15:23:05.000 INFO Synced                                  slot: 9101813, block:    …  empty, epoch: 284431, finalized_epoch: 284429, finalized_root: 0xeea1…a960, exec_hash: 0x234b…a834 (verified), peers: 61, service: slot_notifier
May 18 15:23:08.001 WARN Did not advance head state              reason: Err(HeadMissingFromSnapshotCache(0x9e2ac7bb821602b5031b96f75f8d5b127c70ba240cd15efc23affc90a34bd130)), service: state_advance
May 18 15:23:08.614 WARN Execution engine call failed            error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out), service: exec
May 18 15:23:08.614 WARN Error whilst processing payload status  error: Api { error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out) }, service: exec
May 18 15:23:17.000 INFO Synced                                  slot: 9101814, block:    …  empty, epoch: 284431, finalized_epoch: 284429, finalized_root: 0xeea1…a960, exec_hash: 0x234b…a834 (verified), peers: 56, service: slot_notifier
May 18 15:23:18.100 INFO New RPC block received                  hash: 0x9231…1a73, slot: 9101813
May 18 15:23:25.023 INFO New block received                      root: 0x382d0b36c6ba027ff647b76646eb8dc99bb14ee9ebf28cdb9e023320007a1c34, slot: 9101815
May 18 15:23:27.937 WARN Execution engine call failed            error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out), service: exec
May 18 15:23:27.937 WARN Error whilst processing payload status  error: Api { error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out) }, service: exec
May 18 15:23:27.937 CRIT Failed to update execution head         error: ExecutionForkChoiceUpdateFailed(EngineError(Api { error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out) })), service: beacon
May 18 15:23:29.001 INFO Downloading historical blocks           est_time: 5 days 0 hrs, speed: 3.33 slots/sec, distance: 1448864 slots (28 weeks 5 days), service: slot_notifier
May 18 15:23:29.001 INFO Synced                                  slot: 9101815, block:    …  empty, epoch: 284431, finalized_epoch: 284429, finalized_root: 0xeea1…a960, exec_hash: 0x6774…ccc9 (verified), peers: 56, service: slot_notifier
May 18 15:23:32.000 WARN Did not advance head state              reason: Err(HeadMissingFromSnapshotCache(0x9115350d24e2a68d39ec912f6221723cac36ef8953c78bd3de50d01be5797cb8)), service: state_advance
May 18 15:23:36.838 INFO New block received                      root: 0xf25108a7fdb0d0872f899443bc8a4b140b995835fab1796cb6a9ab24ee3bff1c, slot: 9101816
May 18 15:23:41.001 INFO Synced                                  slot: 9101816, block: 0xf251…ff1c, epoch: 284431, finalized_epoch: 284429, finalized_root: 0xeea1…a960, exec_hash: 0x6d4e…cf5f (verified), peers: 57, service: slot_notifier
May 18 15:23:48.746 INFO New block received                      root: 0x6125e892a42268bafa7ad54ba826f3f46806abcb992d32967ac753e6e1b2ed55, slot: 9101817
May 18 15:23:53.001 INFO Synced                                  slot: 9101817, block: 0x6125…ed55, epoch: 284431, finalized_epoch: 284429, finalized_root: 0xeea1…a960, exec_hash: 0xd372…ff27 (verified), peers: 58, service: slot_notifier
May 18 15:23:58.856 WARN Execution engine call failed            error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out), service: exec
May 18 15:23:58.856 WARN Error whilst processing payload status  error: Api { error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out) }, service: exec
May 18 15:23:58.856 CRIT Failed to update execution head         error: ExecutionForkChoiceUpdateFailed(EngineError(Api { error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out) })), service: beacon
May 18 15:24:01.588 INFO New block received                      root: 0x3de2338200a7285c169e4c62c11472a2f04e612cf323456a4057c875c5f65ad7, slot: 9101818
May 18 15:24:05.000 INFO Synced                                  slot: 9101818, block: 0x3de2…5ad7, epoch: 284431, finalized_epoch: 284429, finalized_root: 0xeea1…a960, exec_hash: 0xd0a8…76a0 (verified), peers: 57, service: slot_notifier
May 18 15:24:12.791 INFO New block received                      root: 0x9461621b04429f18cca124d3019d5554b1ac283e03d43ded5160db5512655e33, slot: 9101819
May 18 15:24:17.001 INFO Synced                                  slot: 9101819, block: 0x9461…5e33, epoch: 284431, finalized_epoch: 284429, finalized_root: 0xeea1…a960, exec_hash: 0x3cca…065b (verified), peers: 58, service: slot_notifier
May 18 15:24:22.964 WARN Execution engine call failed            error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out), service: exec
May 18 15:24:22.964 WARN Error whilst processing payload status  error: Api { error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out) }, service: exec
May 18 15:24:22.964 CRIT Failed to update execution head         error: ExecutionForkChoiceUpdateFailed(EngineError(Api { error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out) })), service: beacon
May 18 15:24:24.927 INFO New block received                      root: 0x64649dec422eada99acf1a639ad5cb9649cfb74cb5db15002f7aa30b57b8a1e7, slot: 9101820
May 18 15:24:29.001 INFO Downloading historical blocks           est_time: 3 days 3 hrs, speed: 5.33 slots/sec, distance: 1448512 slots (28 weeks 5 days), service: slot_notifier
May 18 15:24:29.001 INFO Synced                                  slot: 9101820, block: 0x6464…a1e7, epoch: 284431, finalized_epoch: 284429, finalized_root: 0xeea1…a960, exec_hash: 0x89e7…2494 (verified), peers: 60, service: slot_notifier
May 18 15:24:36.207 INFO New block received                      root: 0xb5703ab743d1bcd8785a38754c48eb373f8059e0e75748ad8f3bbaa99ae3493a, slot: 9101821
May 18 15:24:41.001 INFO Synced                                  slot: 9101821, block: 0xb570…493a, epoch: 284431, finalized_epoch: 284429, finalized_root: 0xeea1…a960, exec_hash: 0x06d0…81ce (verified), peers: 62, service: slot_notifier
May 18 15:24:49.030 INFO New block received                      root: 0x7a284489c937dc46e2a674814b470fd6545e368fb59bdd06e3726b5d9dabf879, slot: 9101822
May 18 15:24:53.000 INFO Synced                                  slot: 9101822, block: 0x7a28…f879, epoch: 284431, finalized_epoch: 284429, finalized_root: 0xeea1…a960, exec_hash: 0x79e6…640b (verified), peers: 66, service: slot_notifier
May 18 15:25:00.420 INFO New block received                      root: 0x92f7c21c7d8ca1eb8a5c20de1ef4cb316fc59dd221228a611d32e94b4ea5bb56, slot: 9101823
May 18 15:25:05.001 INFO Synced                                  slot: 9101823, block: 0x92f7…bb56, epoch: 284431, finalized_epoch: 284429, finalized_root: 0xeea1…a960, exec_hash: 0xe015…f4ef (verified), peers: 64, service: slot_notifier
May 18 15:25:17.000 INFO Synced                                  slot: 9101824, block:    …  empty, epoch: 284432, finalized_epoch: 284430, finalized_root: 0xc92a…24fc, exec_hash: 0xe015…f4ef (verified), peers: 64, service: slot_notifier
May 18 15:25:25.782 INFO Imported deposit log(s)                 new: 1, total: 1476842, latest_block: 19896170, service: deposit_contract_rpc
May 18 15:25:27.044 INFO New block received                      root: 0xaf2225238597168c3e03d392f2485668ee3b5d20c385fea6f19f74bb2032b1f9, slot: 9101825
May 18 15:25:29.001 INFO Downloading historical blocks           est_time: 3 days 3 hrs, speed: 5.33 slots/sec, distance: 1448160 slots (28 weeks 5 days), service: slot_notifier
May 18 15:25:29.001 INFO Synced                                  slot: 9101825, block:    …  empty, epoch: 284432, finalized_epoch: 284430, finalized_root: 0xc92a…24fc, exec_hash: 0xe015…f4ef (verified), peers: 61, service: slot_notifier
May 18 15:25:37.957 INFO New block received                      root: 0x19c9c182b227dc657dc2fd715d98d384e9711f785ea2b877b21471758394c70e, slot: 9101826
May 18 15:25:41.000 INFO Synced                                  slot: 9101826, block: 0x19c9…c70e, epoch: 284432, finalized_epoch: 284430, finalized_root: 0xc92a…24fc, exec_hash: 0xb615…8058 (verified), peers: 59, service: slot_notifier
May 18 15:25:47.807 WARN Execution engine call failed            error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out), service: exec
May 18 15:25:47.807 WARN Error whilst processing payload status  error: Api { error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out) }, service: exec
May 18 15:25:47.807 CRIT Failed to update execution head         error: ExecutionForkChoiceUpdateFailed(EngineError(Api { error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out) })), service: beacon
May 18 15:25:48.403 INFO New block received                      root: 0x5a17811056cf98018e3b7e3bc5c1fd15022544895ef58dbe5d5515994f56e6f4, slot: 9101827
May 18 15:25:53.001 INFO Synced                                  slot: 9101827, block: 0x5a17…e6f4, epoch: 284432, finalized_epoch: 284430, finalized_root: 0xc92a…24fc, exec_hash: 0xd91e…482f (verified), peers: 59, service: slot_notifier
May 18 15:25:59.909 WARN Execution engine call failed            error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out), service: exec
May 18 15:25:59.909 WARN Error whilst processing payload status  error: Api { error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out) }, service: exec
May 18 15:25:59.909 CRIT Failed to update execution head         error: ExecutionForkChoiceUpdateFailed(EngineError(Api { error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out) })), service: beacon
May 18 15:26:00.896 INFO New block received                      root: 0xf4eedaca5a439747e6502f1e7a591f9095c486ca0bb988401722cbf700263b02, slot: 9101828
May 18 15:26:05.001 INFO Synced                                  slot: 9101828, block:    …  empty, epoch: 284432, finalized_epoch: 284430, finalized_root: 0xc92a…24fc, exec_hash: 0xd91e…482f (verified), peers: 56, service: slot_notifier
May 18 15:26:13.628 INFO New block received                      root: 0x7b9f755906696c8862d91e31048530d32e12d1f6f3336af043db5e2c3dee2056, slot: 9101829
May 18 15:26:17.000 INFO Synced                                  slot: 9101829, block: 0x7b9f…2056, epoch: 284432, finalized_epoch: 284430, finalized_root: 0xc92a…24fc, exec_hash: 0x2187…f5af (verified), peers: 59, service: slot_notifier
May 18 15:26:25.704 INFO New block received                      root: 0xc36c75b37b91dbe1d44d1013d56f00ff171d609b81bb026a6f349f7710c25a55, slot: 9101830
May 18 15:26:29.000 INFO Downloading historical blocks           est_time: 2 days 2 hrs, speed: 8.00 slots/sec, distance: 1447680 slots (28 weeks 5 days), service: slot_notifier
May 18 15:26:29.000 INFO Synced                                  slot: 9101830, block: 0xc36c…5a55, epoch: 284432, finalized_epoch: 284430, finalized_root: 0xc92a…24fc, exec_hash: 0x82f1…8a54 (verified), peers: 63, service: slot_notifier
May 18 15:26:37.688 INFO New block received                      root: 0x60f476bb58311d3e6b466c8c3307ca2b1bbc44af74cedfc8570664ea25a7500b, slot: 9101831
May 18 15:26:41.000 INFO Synced                                  slot: 9101831, block: 0x60f4…500b, epoch: 284432, finalized_epoch: 284430, finalized_root: 0xc92a…24fc, exec_hash: 0x446a…a567 (verified), peers: 68, service: slot_notifier
May 18 15:26:47.029 WARN Batch received out of range blocks      start_slot: 1446784, end_slot: 1446815, downloaded: 1, processed: 0, processed_no_penalty: 0, state: AwaitingDownload, batch_ty: blocks, peer_id: 16Uiu2HAkzyFLyKV7YCKSzt6BesFbPZSWBFWJBveNX1QyMJDdJznd, received_boundary: 1446817, expected_boundary: 1446816, service: sync
May 18 15:26:48.885 INFO New block received                      root: 0x9324febcd120c421f4c3d2995f4b59c2252dad39b336b9fda3e99decdce0888c, slot: 9101832
May 18 15:26:53.000 INFO Synced                                  slot: 9101832, block: 0x9324…888c, epoch: 284432, finalized_epoch: 284430, finalized_root: 0xc92a…24fc, exec_hash: 0x4350…1cba (verified), peers: 65, service: slot_notifier
May 18 15:26:59.574 WARN Execution engine call failed            error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out), service: exec
May 18 15:26:59.574 WARN Error whilst processing payload status  error: Api { error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out) }, service: exec
May 18 15:26:59.574 CRIT Failed to update execution head         error: ExecutionForkChoiceUpdateFailed(EngineError(Api { error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out) })), service: beacon
May 18 15:27:00.423 INFO New block received                      root: 0xbc4573d6ec2a4f24227192038e2201ac264ad4fa76cf9a5c5432bbf71dcfcfad, slot: 9101833
May 18 15:27:05.001 INFO Synced                                  slot: 9101833, block:    …  empty, epoch: 284432, finalized_epoch: 284430, finalized_root: 0xc92a…24fc, exec_hash: 0x4350…1cba (verified), peers: 65, service: slot_notifier
May 18 15:27:08.000 WARN Did not advance head state              reason: Err(HeadMissingFromSnapshotCache(0x9324febcd120c421f4c3d2995f4b59c2252dad39b336b9fda3e99decdce0888c)), service: state_advance
May 18 15:27:13.612 INFO New block received                      root: 0x7f5262faf0199076e529d4799eccf83bf5f973da9af562fd967ff283e617b3fa, slot: 9101834
May 18 15:27:17.000 INFO Synced                                  slot: 9101834, block: 0x7f52…b3fa, epoch: 284432, finalized_epoch: 284430, finalized_root: 0xc92a…24fc, exec_hash: 0xc2b5…ec6e (verified), peers: 65, service: slot_notifier
May 18 15:27:23.833 INFO New block received                      root: 0x2a1967ec73e42666615b860a1c88169902b3c272f8d173e5704568e920d56bb9, slot: 9101835
May 18 15:27:29.000 INFO Downloading historical blocks           est_time: 2 days 2 hrs, speed: 8.00 slots/sec, distance: 1447200 slots (28 weeks 5 days), service: slot_notifier
May 18 15:27:29.000 INFO Synced                                  slot: 9101835, block: 0x2a19…6bb9, epoch: 284432, finalized_epoch: 284430, finalized_root: 0xc92a…24fc, exec_hash: 0x9670…0577 (verified), peers: 63, service: slot_notifier
May 18 15:27:36.769 INFO New block received                      root: 0xae24d3b51e13625ff89f41caebce6866c96bcf34ade26b3ef58b9a7672d0cb72, slot: 9101836
May 18 15:27:41.001 INFO Synced                                  slot: 9101836, block: 0xae24…cb72, epoch: 284432, finalized_epoch: 284430, finalized_root: 0xc92a…24fc, exec_hash: 0x183e…5e2a (verified), peers: 59, service: slot_notifier
May 18 15:27:48.838 INFO New block received                      root: 0x2f3d355b27df11b818a89de9fa23cb3319692cd9d4ab3d1f13ca52d397a5a5c7, slot: 9101837
May 18 15:27:53.000 INFO Synced                                  slot: 9101837, block: 0x2f3d…a5c7, epoch: 284432, finalized_epoch: 284430, finalized_root: 0xc92a…24fc, exec_hash: 0x5e2f…87e2 (verified), peers: 58, service: slot_notifier
May 18 15:27:59.410 INFO New block received                      root: 0x6bc779137ff724bf68f2a5ac78fd4924dae047600c0686e2dc760d85a9115f72, slot: 9101838
May 18 15:28:05.000 INFO Synced                                  slot: 9101838, block: 0x6bc7…5f72, epoch: 284432, finalized_epoch: 284430, finalized_root: 0xc92a…24fc, exec_hash: 0x3a81…7731 (verified), peers: 61, service: slot_notifier
May 18 15:28:12.808 INFO New block received                      root: 0x3ab99ea26b7ad1a14cd98e9614d2a6ac9f682cb3a61ed1a651cc47c4c4e28ee0, slot: 9101839
May 18 15:28:17.001 INFO Synced                                  slot: 9101839, block: 0x3ab9…8ee0, epoch: 284432, finalized_epoch: 284430, finalized_root: 0xc92a…24fc, exec_hash: 0xb46e…19f1 (verified), peers: 63, service: slot_notifier
May 18 15:28:23.559 WARN Execution engine call failed            error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out), service: exec
May 18 15:28:23.559 WARN Error whilst processing payload status  error: Api { error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out) }, service: exec
May 18 15:28:23.559 CRIT Failed to update execution head         error: ExecutionForkChoiceUpdateFailed(EngineError(Api { error: HttpClient(url: http://execution:8551/, kind: timeout, detail: operation timed out) })), service: beacon
May 18 15:28:25.114 INFO New block received                      root: 0x836cc199a7107d83498c57c598026722458d3eef7395d548734521d9963b5ebc, slot: 9101840
May 18 15:28:29.000 INFO Downloading historical blocks           est_time: 2 days 2 hrs, speed: 8.00 slots/sec, distance: 1446720 slots (28 weeks 4 days), service: slot_notifier
May 18 15:28:29.001 INFO Synced                                  slot: 9101840, block: 0x836c…5ebc, epoch: 284432, finalized_epoch: 284430, finalized_root: 0xc92a…24fc, exec_hash: 0x6d9b…eeda (verified), peers: 58, service: slot_notifier
May 18 15:28:36.629 INFO New block received                      root: 0x93616e3b30e3b83c42d9464e8af39e8219abb7594be64f32dcfca9dbba62d1d1, slot: 9101841
May 18 15:28:41.001 INFO Synced                                  slot: 9101841, block: 0x9361…d1d1, epoch: 284432, finalized_epoch: 284430, finalized_root: 0xc92a…24fc, exec_hash: 0xaa48…7f97 (verified), peers: 65, service: slot_notifier

Platform(s)
Linux (x86)
What version/commit are you on?
reth Version: 0.2.0-beta.7
Commit SHA: a44e085
Build Timestamp: 2024-05-09T21:04:29.696046697Z
Build Features: jemalloc
Build Profile: maxperf
What database version are you on?
Current database version: 2
Local database is uninitialized
Which chain / network are you on?
mainnet
What type of node are you running?
Archive (default)
What prune config do you use, if any?
default reth.toml
reth@f7f00e8595be:/$ cat /var/lib/reth/reth.toml
[stages.headers]
downloader_max_concurrent_requests = 100
downloader_min_concurrent_requests = 5
downloader_max_buffered_responses = 100
downloader_request_limit = 1000
commit_threshold = 10000

[stages.bodies]
downloader_request_limit = 200
downloader_stream_batch_size = 1000
downloader_max_buffered_blocks_size_bytes =<PHONE_NUMBER>
downloader_min_concurrent_requests = 5
downloader_max_concurrent_requests = 100

[stages.sender_recovery]
commit_threshold = 5000000

[stages.execution]
max_blocks = 500000
max_changes = 5000000
max_cumulative_gas =<PHONE_NUMBER>000
max_duration = "10m"

[stages.account_hashing]
clean_threshold = 500000
commit_threshold = 100000

[stages.storage_hashing]
clean_threshold = 500000
commit_threshold = 100000

[stages.merkle]
clean_threshold = 5000

[stages.transaction_lookup]
chunk_size = 5000000

[stages.index_account_history]
commit_threshold = 100000

[stages.index_storage_history]
commit_threshold = 100000

[stages.etl]
file_size = 524288000

[peers]
refill_slots_interval = "5s"
trusted_nodes = []
trusted_nodes_only = false
max_backoff_count = 5
ban_duration = "12h"

[peers.connection_info]
max_outbound = 100
max_inbound = 30
max_concurrent_outbound_dials = 15

[peers.reputation_weights]
bad_message = -16384
bad_block = -16384
bad_transactions = -16384
already_seen_transactions = 0
timeout = -4096
bad_protocol = -2147483648
failed_to_connect = -25600
dropped = -4096
bad_announcement = -1024

[peers.backoff_durations]
low = "30s"
medium = "3m"
high = "15m"
max = "1h"

[sessions]
session_command_buffer = 32
session_event_buffer = 260

[sessions.limits]

[sessions.initial_internal_request_timeout]
secs = 20
nanos = 0

[sessions.protocol_breach_request_timeout]
secs = 120
nanos = 0

[sessions.pending_session_timeout]
secs = 20
nanos = 0

If you've built Reth from source, provide the full command you used
im using ./ethd
Code of Conduct

[X] I agree to follow the Code of Conduct

Related #7322

full node archive mode

please clarify
these logs don't cover the same timespan, so I'm afraid they are not helpful


Enable cors

Description
As outlined here: #494 setting up a Zappa application to use CORS along with an api-gateway managed authentication mechanism requires enabling cors at the api-gateway layer to deal with the pre-flight options requests. There is a fairly simple button to manage this in the API-gateway management console, but I'd rather not have to take those steps after doing a deployment.
The "cors" option in the settings can either be "true" (defaulting to the AWS
API Gateway "Enable Cors" values) or a dictionary specifying "allowed_headers"
"allowed_methods" and "allowed_origin". Any keys not specified will default
to the API Gateway defaults.
GitHub Issues
https://github.com/Miserlou/Zappa/issues/494

Coverage increased (+0.3%) to 80.6% when pulling a137d586d2ad8cede57278d25c6b1854e2edcb5e on AusIV:enable_cors into<PHONE_NUMBER>5c073da7750e27e8291d7fbf2341ae on Miserlou:master.

Huge!
Requesting input from @aectann @bjinwright and @collingreen since I think they use these services.

I haven't tested it yet. But I do like how it seemingly makes CORS configuration a breeze. Nice work! I'll try to give it a go later today.

I think we're good!


eBrary URLs should not have proxy prefix

Duplicate of https://github.com/sandbergja/blacklight_ingest_scripts/issues/3

And maybe need to start being eBook central urls

Fixed in traject


minikube-gui should have a setting page to override the minikube binary

currently minikube-gui uses whatever binary is in the path based on an order in this PR:
https://github.com/kubernetes-sigs/minikube-gui/pull/4
but it would be best if we have a settings page that would let you override/select the exact minikube binary to use (maybe show the version in parentheses
(drop down menu)

/usr/loca/bin/minikube (version 1.28.0)
/opt/homebrew/bin/minikube  (version 1.27.1)
...

or and maybe minikube gui should default to the latest version instead.
Originally posted by @medyagh in https://github.com/kubernetes-sigs/minikube-gui/pull/4#pullrequestreview-1254175211

Please close this pr if its completed

Completed in
https://github.com/kubernetes-sigs/minikube-gui/pull/38
https://github.com/kubernetes-sigs/minikube-gui/pull/41
https://github.com/kubernetes-sigs/minikube-gui/pull/43


BUG Ensure sake works when called from any directory

Credit to the kind users of silverstripe-users slack for testing this out.
Checks have been simplified and cleaned up, checking:

relative path from vendor/bin/sake. (simlink dir)
relative path from vendor/silverstripe/framework/sake (real dir)
base relative search for vendor/silvestripe/framework (for global sake install)
base relative search for legacy framework (in case run on an old framework installation, for global sake install)

Thanks, works perfectly in all my scenarios!


Refractor editor plugin API in order to expose more parts of the editor UI

(Proposal in progress)
This PR aims to expose (where possible) every part of the editor UI to plugins.
I want to achieve it by:

Add dedicated singletons for groping opportunely nodes by category (Docks, viewport tabs, ...) and using these singletons to interact with the "category".
For each component of the editor UI (e.g. the scene dock), add some getters for getting the relevant part of it, reducing the amount of time (and errors) that plugin devs uses to navigate the node structure (The granularity is not defined, but I don't want to expose every button).
This doesn't mean the node structure must be kept stable or nodes must be named. Ideally, neither of those getters should be stable, but I don't think it is possible to mark the API as "always unstable".

Note for reviewers: since this is going to be a big PR, I'd be verbose with commits and squash them when this became stable enough.

Note for reviewers: since this is going to be a big PR, I'd be verbose with commits and squash them when this became stable enough.

I think it would be better to do this in steps, in several PRs.
"Expose all the editor UI" sounds impossible or at least controversial to begin with. But say exposing all the docks in a nice way is totally doable and I was eyeing it for some time now. As docks are already somewhat encapsulated in the EditorNode API and only need to be properly sanitized for what they expose of themselves. So if done correctly, I would be completely behind such PR, but other issues may not be that straightforward.

I think it would be better to do this in steps, in several PRs.

Yeah, I wanted to do it too, but since that for only exposing the docks I need to change 33 files, it'll come with lots of PR that depends on each other.

"Expose all the editor UI"

I was worried that it is misleading, so I'll change it to something softer (the idea behind the PR doesn't change for now).

I would generally prefer to keep plugin API smaller and instead provide a more general help to navigating the editor UI, like naming more nodes.

Like godotengine/godot-proposals#1018? The issue with it is that if something change in the structure (like moving nodes) you lose the compatibility. Instead, if the interested component provides getters for relevant subcomponents, the problem came less frequently.

Like godotengine/godot-proposals#1018? The issue with it is that if something change in the structure (like moving nodes) you lose the compatibility. Instead, if the interested component provides getters for relevant subcomponents, the problem came less frequently.

Yes, frequently used parts or parts of higher interest should be exposed via specific, stable APIs. I was refering to your original title more, because to make the entirety of the UI tree more accessible the better option is to name nodes, even if they would break from time to time.
Generally I think that the approach should be:

APIs for higher interest nodes
Names for their children of lower interest
Keep the rest as is, unnamed

Points 1 and 3 are exactly what I thought.
2 requires a naming scheme (as you pointed out in godotengine/godot-proposals#1018) and I don't plan to do it here.

After thinking a bit, I decide to keep this PR only for exposing singleton as described in godotengine/godot-proposals#2537 and open other PRs.

The implementation of this PR was not accepted in a PR meeting, and in the last live Q&A Akien says that a refractor of editor plugin API will be done after 4.0.
Since the release of Godot 4 is not incoming, I'm going to close this PR, as it's quite difficult to rebase.
I'm happy to redo it from scratch, but only when there will be interest on it.

Rejected in a discussion, the Godot contributor chat.
Part of this PR will be extracted to make a cleanup PR.


Crop disappears after a few seconds

Issue
Crop range disappears roughly 2 seconds following a selection.
Expected Result
Crop range stays until new range generated or user clicks on other element.
Code
<ReactCrop
    crop={{aspect:1}}
    src={this.state.imagePreviewUrl}
    onComplete={(c,p)=>this.cropComplete(c,p)}
    keepSelection
/>

If you need more info I'd be happy to provide a GIF demonstrating this issue.

My bad, the crop variable needs to be stored and updated within state in order for changes to persist. This could be more clear in the documentation.


Stale Pull Requests

What is the current policy to deal with stale pull requests?
If we look at the list of open PRs we can see that the majority was opened from May 13 to May 17 ( they were part of a workshop if I'm not mistaken). Most of them have not been updated and I'm afraid this could reduce/be reducing the number of new PRs, first because these exercises are literally blocked and second because some people generally avoid contributing to projects with tons of open PRs.

I don't know of any "Policy" but they should be bumped and then if no response from the owner, and it is a good PR, then ownership can be assumed.

Maybe policy is the wrong word here? :)
But thanks for the info, I'm going to close this.

What is the current policy to deal with stale pull requests?

I've asked this question in the general discussions: https://github.com/exercism/discussions/issues/56


Add finalfusion, rust2vec

Both are word embedding crates

Now that CI is fixed (after many months), I'm catching up on stale PRs. This needed the topic set to nlp instead of natural-language-processing since that's the tag that the generator looks for. I took your commit, rebased it, and fixed the topic tag in #111. I'll merge that PR once the CI checks pass.
Thanks.


Fixed unlinking the shared memory region on non-Android platform

Current implementation does not unlink the shared memory region for non-Android platforms.

@miaowang14 could you review this PR?

@robert-kalmar  Can you please check @miaowang14's comments and keep us posted ? Thanks!


Print inverted pyramid pattern

Description
Input   : 5

Output :
1 2 3 4 5
1 2 3 4
1 2 3
1 2
1

Program added successfully :tada:
Thanks for your contribution :hugs:


VIDCS-869: Update Basic Video2Catpurer

Related to https://github.com/opentok/opentok-android-sdk-samples/issues/461

Has this been updated based on our camera2 capturer?

@juliobecerragomez @goncalocostamendes Those changes have been taken from the updated native SDK. I haven't made any modifications other than renaming variables and fixing the logs.

@juliobecerragomez @goncalocostamendes Those changes have been taken from the native SDK code. I haven't made any modifications other than renaming variables and fixing the logs. I think @jintgeorge would be best to reply to the comment here (cc @v-kpheng )

Yes, just confirmed it is the same as native SDK. Approving

@vona-ben So at least we should fix the commented out code. I do not think it is ok to show it as part of the linux sample apps.

@vona-ben So at least we should fix the commented out code. I do not think it is ok to show it as part of the linux sample apps.

Done


Support custom metadata field for optional packages (and possibly other type of packages)

Proposal: Support custom metadata field for optional packages (and possibly other type of packages)

Summary
Allow main package to selectively load optional packages by querying exposed custom metadata as available in app extensions, without the need to load the code from optional packages. This would immensely help apps with plugin architecture.
Rationale

Application with plugin architecture currently have to expose interfaces to decide if the optional package implements certain services to be used by main application, which is slow and possibly ends up keeping the code in memory for long time.
Custom metadata helps avoid loading the code.
By keeping the mechanism of defining custom metadata same as app extension, developer are less burdened.

Scope

Capability
Priority

Allow optional packages to define custom meta data in a manner similar to app extensions
Must

Important Notes

Example shared in the #81

We are creating an application that is divided into a main app and lots and lots of plugins. We would like to load plugins on demand when we connect a hardware device, detected by the main app. Main application queries the meta data of the hardware and invokes/load the appropriate plugin assembly matching the meta data (things like make of hardware, year manufactured, product code, firmware id, etc).
The plugins are currently optional packages (we can't use app extensions because plugins also have UI component and communication between main app and plugins in non-trivial). We would only like to load the plugin assembly when required, i.e. when the meta data matches. Currently we are using a json file to store the meta data per optional package, this require some boilerplate code and other things to ensure we always package the json file with the plugins.
It seems that the Extension provide the same functionality as we require, however within the manifest as you have described above. If we can get a similar option to define custom properties in the optional package, it would help everyone save writing some code and do testing.

Open Questions

@DrusTheAxe - is this in your area?

Allow optional packages to define custom meta data in a manner similar to app extensions

One solution is to support a package-scope equivalent to <Extension Category="windows.appExtension"> and all that implies

Add support for package-scope manifested data, e.g.

<Package>
    <Extensions>
        <Extension Category="windows.packageExtension"...>

Add APIs equivalent to Windows.ApplicationModel.AppExtensions and AppExtensionCatalog. Functionally the API could be similar (nigh identical?) except...

a. AppExtension.GetExtensionPropertiesAsync returns the package-scope <Extension>'s data rather than a per-app's <Extension> data.
b. Remove .AppInfo
Otherwise you could rename AppExtension[[Catalog]] to PackageExtension[[Catalog]] and get the desired result.
@harvinders would that satisfy the proposal?

@DrusTheAxe. Yes, it would satisfy the need. Just wanted to understand why do you propose to remove AppInfo? seems like useful information to allow the main app to enquire.

@harvinders sorry I overlooked your message. Let's fix that...

why do you propose to remove AppInfo?

Because package != application
A Package contains 0-100 applications so we need to get 'the list of apps', not 'the app'.
The obvious answer is to replace .AppInfo with .Package. But lo' and behold, AppExtension already has a .Package property!
Given a Package object you can get the list of apps it provides so today given AppExtension we can...
appextension.AppInfo
appextension.Package
FOREACH ale IN appextension.Package.GetAppListEntries()
    appinfo = ale.AppInfo

We can have the equivalent model with a PackageExtension object
packageextension.Package
FOREACH ale IN packageextension.Package.GetAppListEntries()
    appinfo = ale.AppInfo


Check 3 string values in one log file

i have a log file, where there are 3 different lines to be checked which are at 3 different lines(not consecutively).
Which command to use to check 3 strings

@manishurs This is an issue tracker, not a help forum. Rather, post your question to robotframework-users mailing list


doc link broken

Do you want to request a feature or report a bug?
What is the current behavior?
Doc link broken and get into empty state page for github
If the current behavior is a bug, please provide the steps to reproduce and either a repl.it demo through https://repl.it/languages/jest or a minimal repository on GitHub that we can yarn install and yarn test.
What is the expected behavior?
go to the correct link
Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.
https://facebook.github.io/jest/docs/snapshot-testing.html#content
This is the page broken. the link broken are:

Consider this example test
Edit This Doc button

Thanks

I think it needs to go to https://github.com/facebook/jest/edit/master/docs/en/SnapshotTesting.md instead of https://github.com/facebook/jest/edit/master/docs/SnapshotTesting.md

It works when you explicitly go to the English version https://facebook.github.io/jest/docs/en/snapshot-testing.html#content

It is weird because this https://github.com/facebook/jest/blob/master/website/core/Doc.js#L16 should fall back to english... @thymikee am I  missing something?

Haven't worked on this, but it should work like you said. There's a PR rewriting our docs where this should be already implemented

Could this be related to #4250?

I'm not sure if this is related, but the content varies and is different depending on if en is in the link.
Ex:
https://facebook.github.io/jest/docs/troubleshooting.html#content
https://facebook.github.io/jest/docs/en/troubleshooting.html#content

I just replaced all the old docs pages with redirects to the en versions (finally).

:clap:


Stupid Question regarding gRPC-Gateway

Hi,
I'm trying to use gRPC-Gateway for my microservice, but when I follow the usage tutorial here
https://docs.konghq.com/hub/kong-inc/grpc-gateway/
The route is working fine, but got an error of
transcoding requests require a .proto file defining the service

Tried including it using githubraw. Doesn't work. I deployed kong in kubernetes as ingress-controller. Can someone help me? Thanks before!

@DarthJonathan, did you try to point it to URI or upload the raw content?

I did, but it's on a private repository, so it has token id in the end, that might be the issue?

Maybe adding option to add binary descriptors of the protobuf is a nice step forward

@DarthJonathan The error seems to be that proto field is missing. Did you configure the plugin's proto field?
It expect the path of .proto file, we doesn't support passing the content of .proto file now.
apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  name: some-name
plugin: grpc-gateway
config:
  proto: /path/to/proto/file

@fffonion yes I understand that, but since I deployed it on kubernetes, can I use ex : raw.githubusercontent.com as a proto source? or does it need to be in disk / container file?

@DarthJonathan Right now the plugin only supports local file. But there could be some tooling elsewhere to
mount a remote file into the container.

@fffonion I see, so CDN doesn't work, sad. A binary descriptor can be a great addition though. Thanks!


The start/end_listening sounds should be called with the pulse media.role=phone to enable ducking

Copied from https://github.com/MycroftAI/mycroft-core/issues/3148
This will likely never get fixed upstream since MycrodtAI has moved on to dinkum. But now that I am building my home setup around ovos, maybe there is a chance?
The linked ticket describes the issue.
Basically, the start listening sound play command  should be passed the same environment as the tts play command.
This let's pulse properly handle ducking of the start listening sound.
Without this, as it currently stands, the start listening sound is played without the phone role, so it is treated as music. This is problematic because I want the start listening sound and the tts to be played at the same volume.

Have to check os.environ. The way this is coded is weird and indicates the common PULSE_PROP environmental variable is media.role=phone
_ENVIRONMENT = deepcopy(os.environ)
_ENVIRONMENT['PULSE_PROP'] = 'media.role=music'

def _get_pulse_environment(config):
    """Return environment for pulse audio depeding on ducking config."""
    tts_config = config.get('tts', {})
    if tts_config and tts_config.get('pulse_duck'):
        return _ENVIRONMENT
    else:
        return os.environ


[bug] Can't work with controlnet at the same time

While working with controlnet, it crash when images generating comes to face editor phase (which is the end of whole job).
If I disable controlnet, face editor works well, and vice versa, If I disable face editor, controlnet works well.
I'll post the error message later.

Error running postprocess: D:\APPs\stable-diffusion\stable-diffusion-webui\extensions\sd-face-editor\scripts\face_editor_extension.py
Traceback (most recent call last):
File "D:\APPs\stable-diffusion\stable-diffusion-webui\modules\scripts.py", line 478, in postprocess
script.postprocess(p, processed, *script_args)
File "D:\APPs\stable-diffusion\stable-diffusion-webui\extensions\sd-face-editor\scripts\face_editor_extension.py", line 98, in postprocess
script.proc_images(mask_model, detection_model, o, res,
File "D:\APPs\stable-diffusion\stable-diffusion-webui\extensions\sd-face-editor\scripts\face_editor.py", line 321, in proc_images
proc = self.__proc_image(p, mask_model, detection_model,
File "D:\APPs\stable-diffusion\stable-diffusion-webui\extensions\sd-face-editor\scripts\face_editor.py", line 417, in __proc_image
proc = process_images(p)
File "D:\APPs\stable-diffusion\stable-diffusion-webui\modules\processing.py", line 611, in process_images
res = process_images_inner(p)
File "D:\APPs\stable-diffusion\stable-diffusion-webui\extensions\sd-webui-controlnet\scripts\batch_hijack.py", line 42, in processing_process_images_hijack
return getattr(processing, '__controlnet_original_process_images_inner')(p, *args, **kwargs)
File "D:\APPs\stable-diffusion\stable-diffusion-webui\modules\processing.py", line 729, in process_images_inner
samples_ddim = p.sample(conditioning=p.c, unconditional_conditioning=p.uc, seeds=p.seeds, subseeds=p.subseeds, subseed_strength=p.subseed_strength, prompts=p.prompts)
File "D:\APPs\stable-diffusion\stable-diffusion-webui\extensions\sd-webui-controlnet\scripts\hook.py", line 290, in process_sample
return process.sample_before_CN_hack(*args, **kwargs)
File "D:\APPs\stable-diffusion\stable-diffusion-webui\modules\processing.py", line 1262, in sample
samples = self.sampler.sample_img2img(self, self.init_latent, x, conditioning, unconditional_conditioning, image_conditioning=self.image_conditioning)
File "D:\APPs\stable-diffusion\stable-diffusion-webui\modules\sd_samplers_kdiffusion.py", line 356, in sample_img2img
samples = self.launch_sampling(t_enc + 1, lambda: self.func(self.model_wrap_cfg, xi, extra_args=extra_args, disable=False, callback=self.callback_state, **extra_params_kwargs))
File "D:\APPs\stable-diffusion\stable-diffusion-webui\modules\sd_samplers_kdiffusion.py", line 257, in launch_sampling
return func()
File "D:\APPs\stable-diffusion\stable-diffusion-webui\modules\sd_samplers_kdiffusion.py", line 356, in
samples = self.launch_sampling(t_enc + 1, lambda: self.func(self.model_wrap_cfg, xi, extra_args=extra_args, disable=False, callback=self.callback_state, **extra_params_kwargs))
File "D:\APPs\stable-diffusion\stable-diffusion-webui\venv\lib\site-packages\torch\utils_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "D:\APPs\stable-diffusion\stable-diffusion-webui\repositories\k-diffusion\k_diffusion\sampling.py", line 594, in sample_dpmpp_2m
denoised = model(x, sigmas[i] * s_in, **extra_args)
File "D:\APPs\stable-diffusion\stable-diffusion-webui\venv\lib\site-packages\torch\nn\modules\module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "D:\APPs\stable-diffusion\stable-diffusion-webui\modules\sd_samplers_kdiffusion.py", line 169, in forward
devices.test_for_nans(x_out, "unet")
File "D:\APPs\stable-diffusion\stable-diffusion-webui\modules\devices.py", line 156, in test_for_nans
raise NansException(message)
modules.devices.NansException: A tensor with all NaNs was produced in Unet. This could be either because there's not enough precision to represent the picture, or because your video card does not support half type. Try setting the "Upcast cross attention layer to float32" option in Settings > Stable Diffusion or using the --no-half commandline argument to fix this. Use --disable-nan-check commandline argument to disable this check.
Total progress: 100%|██████████████████████████████████████████████████████████████████| 23/23 [00:24<00:00,  1.07s/it]
100%|██████████████████████████████████████████████████████████████████████████████████| 23/23 [00:05<00:00,  3.96it/s]

As you can see, the whole generation crash at face editor phase.

@JoeyLearnsToCode
Thanks for the detailed error information.
After updating ControlNet to the latest version I too could see this error. I will investigate the cause and solution.

The problem i met with when enabling CN and SD-Face-editor at the same time is not a crashed phase, but just not working. No optimized faces output.

I understand that it stopped working due to this commit, but I still do not understand why it stopped working properly :thinking:
https://github.com/Mikubill/sd-webui-controlnet/pull/1337

@VenomSnake01
Thanks!
It seems that depending on the startup options of the Web UI, it may not work correctly without error.

@JoeyLearnsToCode @VenomSnake01
The error has been fixed.
Please try it!

不再会崩溃了，但是仍然有问题：
当我同时启用 CN 和 faceeditor ，并且选择只生成一张图，会产生好几张图，并且保存的图不正确（不是我预期的那张）。
It doesn't crash anymore, but there is still a problem:
When I enable both CN and face editor and choose to generate only one image, several images are generated and the saved one is wrong (not the one I expected).

@JoeyLearnsToCode
Thanks for giving it a quick try!
This is the expected result.

The first image is before the Face Editor (not saved by default).
The third image is after the Face Editor has processed it (it is saved).
The other images are images created by ControlNet, but they are only displayed on the screen and are not saved, so you do not need to worry about them.

In some cases, it may be preferable to use the image before the Face Editor modifies it. For such cases, there is a "Save original image" option. If you enable this option, you can save the original image (first one) too, so you can choose the image that is more desirable to you.
(Since Face Editor works on the " zoom in on a face image and redraw it in detail" mechanism, it tends to generate more realistic images. That can be counterproductive if you want an anime-like image. Note that when Face Editor processes the image, it uses the same checkpoint as the original image.)

Oh I see now, that sounds acceptable.
One more question though:

Note that when Face Editor processes the image, it uses the same checkpoint as the original image.

What if original image is not a SD generated image at all (like a real photo)? Which checkout will be using?

@JoeyLearnsToCode
Sorry. The expression is a little confusing.
A more accurate expression would be "use the currently selected checkpoint in the Web UI as it is".

Note that when Face Editor processes the image, it uses the same checkpoint as the original image.

The intent of the above statement is as follows:
When using Face Editor with txt2img tab, the image first created by txt2img + ControlNet and the image modified by Face Editor are created using the same checkpoint.

Now it's clear enough, thx :D


Idea for Green's theorem for arbitrary limb-darkening

@rodluger If we want to derive (1-z)^n = dG_{n,x}/dx-dG_{n,y}/dy for the nth limb-darkening term, then taking the s_2 term as guidance, we can write this as: G_n = f(z) (-y {\bf \hat x} + x {\bf \hat y}), where f(z) is a function that satisfies the differential equation:  2f(z) + df/dz ( z-1/z) = (1-z)^n.
In the s_2 case, the right hand side equals z, and f(z) = (1-z^3)/(1-z^2)/3 from equation (34) in the s^TAR'Ry paper.   In the Green's basis function in equation (34) of the starry paper, the h has an extra 1/3 added to it, i.e. (1-z^3)/3 instead of -z^3/3; but no matter since the derivatives are the same, so the Green's function should be the same.
Back to the arbitrary limb-darkening term:   if I make the substitution f(z) = h(z)/(1-z^2), then this differential equation simplifies to dh/dz = -z(1-z)^n.  This has solution h = (1-z)^{n+1}(1+z+nz)/(n+1)/(n+2).
All to say that for g_n = (1-z)^n, we have the Green's integral solution of G_n = h(z)/(1-z^2) (-y {\bf \hat x}+x{\bf \hat y}).  These can be substituted into equations (31) and (32) to give the primitive integrals in the general limb-darkened case.

@rodluger Actually, I think a better way to go is to pick f(z) = z^{n+2} so that G_n =   Then, g_n = dG_{n,y}/dx-dG_{n,x}/dy = (n+4)z^{n+2}+(n+2)z^n.  Linear combinations of these terms can be used to get arbitrary order limb-darkening, when combined with the s_0ands_2terms.  And, the primitive integrals can be expressed in terms ofH_v, I_v, J_v;  no need to use transformation of Green's basis or Y_{lm}`.

Awesome, I love this. I can work out the math in the next week if you don't beat me to it :)

I'm happy to let you work out the math, but taking one more step, this G_n yields a primitive integral of:

where for even n, the integrand is a polynomial in s_\varphi which can be expressed as sums over I_v, while for odd n, the integrand is a polynomial times (1-b^2-r^2-2br s_\varphi)^{3/2}, which can be expressed in terms of sums over J_v.  I suspect something similar should work for Q(G_n).
\mathcal{P}(\mathbf{G}n) = \int{2\pi-\phi}^{2\pi+\phi} \left(1-r^2-b^2-2br s_\varphi\right)^{\tfrac{n+2}{2}} \left(r+bs_\varphi\right)d\varphi

You beat me to it in the end :) Nice! Any idea if this is numerically stable?

No, but I'm concerned about that:  between the (-1) factors in the binomial expansion,  and cancellations we may get when combining various powers of z, I'm not clear whether this will be stable.  We've already gotten the s_n terms working pretty well, so perhaps we should just stick with that.

OK. I'll code it up when I have a chance and run some tests. We can always
switch between the expressions based on speed/stability.
On Wed, Jun 27, 2018 at 11:20 AM Eric Agol<EMAIL_ADDRESS>wrote:

No, but I'm concerned about that: between the (-1) factors in the
binomial expansion, and cancellations we may get when combining various
powers of z, I'm not clear whether this will be stable. We've already
gotten the s_n terms working pretty well, so perhaps we should just stick
with that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rodluger/limbdark/issues/10#issuecomment-400781555,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AI5FK-HTvv6dq7Qqbw613TPnFiFBOb6Xks5uA8zwgaJpZM4Ubx8v
.

I found a recursion relation for dJ_v/dk, which is:

So, we can compute both dI_v/dk and dJ_v/dk.  The rest should be straightforward algebra.
\frac{\partial J_v}{\partial k} &= -3 k^{-1} J_v +k^2 \frac{\partial J_{v-1}}{\partial k}\\ \frac{\partial J_0}{\partial k} &= \frac{2}{k^4}\left[(2-k^2)E(k^2)+2(k^2-1)K(k^2)\right]

Of course, it remains to be seen whether this recursion is stable...

And here are some other expressions for dJ_v/dk for k^2 < 1:

\frac{\partial J_v}{\partial k} &= 3 k^{2v} \int_0^1 du u^{v+\tfrac{1}{2}} (1-u)^{1/2} (1-k^2u)^{-1/2}\\ &= 3 k^{2v} \frac{\sqrt{\pi}}{2} \Gamma(v+\tfrac{3}{2}) \,_2{\tilde F}_1(\tfrac{1}{2},v+\tfrac{3}{2},3+v,k^2)

Also,

for k^2 < 1, and dI_v/dk=0 for k^2 > 1.   As with s_2, this seems like it is easier to differentiate than I expected.
\frac{\partial I_v}{\partial k} = k^{2v} k_c^{-1}.

And for k^2 > 1,

\frac{\partial J_0}{\partial k} &= k^{-3} \left[2(2-k^2)E(k^{-2}) + 2(k^2-1) K(k^{-2})\right]\\ \frac{\partial J_v}{\partial k} &=  (-1)^{v+1} \frac{3k^{-3}\pi^{3/2}}{\Gamma(-(v+\tfrac{1}{2}))} \,_2\tilde{F}_1(-\tfrac{1}{2},v+\tfrac{3}{2},v+2,k^{-2})
with the same recursion relation.  Again, I think we can differentiate our series expressions. This gives the derivatives for both I_v and J_v for all k^2, so I think we can compute all derivatives analytically.

@rodluger It turns out that Q(G_n)=0 in this case!  I'm working on coding this up today.

@rodluger I got this working with auto-diff (haven't implemented the analytic derivatives yet), and for the two test cases of r=0.01 and r=100 it seems to give ~ machine precision everywhere!  I still may need to implement analytic derivatives (at least for the linear limb-darkening term), but for now this is heartening.
I will try to write this up for limbdark paper, but probably not until next week.

@rodluger The relevant routines are transit_poly.jl (which uses sn_bigr.jl, which uses s2_stable.jl and cel_bulirsch.jl), transit_poly_gradient.jl which  carries out auto diff of transit_poly.jl, and test_transit_poly_gradient.jl which computes light curves and derivatives for a set of u_n limb-darkening coefficients for the two r values, and a grid of b values for each.
Here are the error plots for:
julia> test_transit_poly_gradient([0.1,0.1,0.1,0.1])
Yields these (rather boring) error plots.

Awesome! I'll probably be slow to catch up on these things on the C++ side,
as I'm traveling the next two weeks and focusing on vplanet stuff with
Rory. But keep me posted!
On Sat, Jun 30, 2018, 10:39 AM Eric Agol<EMAIL_ADDRESS>wrote:

@rodluger https://github.com/rodluger The relevant routines are
transit_poly.jl (which uses sn_bigr.jl, which uses s2_stable.jl and
cel_bulirsch.jl), transit_poly_gradient.jl which carries out auto diff of
transit_poly.jl, and test_transit_poly_gradient.jl which computes light
curves and derivatives for a set of u_n limb-darkening coefficients for
the two r values, and a grid of b values for each.
Here are the error plots for:
julia> test_transit_poly_gradient([0.1,0.1,0.1,0.1])
Yields these (rather boring) error plots.
[image: transit_poly_error_r100]
https://user-images.githubusercontent.com/243664/42126723-fbe8d5c6-7c40-11e8-8168-96f97982ab98.png
[image: transit_poly_error_r0 01]
https://user-images.githubusercontent.com/243664/42126724-fc059648-7c40-11e8-9d74-a443e6ce4958.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rodluger/limbdark/issues/10#issuecomment-401548437,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AI5FK3G3USeMlHlOqGUgY5P6rdHpqR1gks5uB5ujgaJpZM4Ubx8v
.

@rodluger I decided to code up the analytic differentiation, and I now have an initial version working.  The derivatives are precise to better than 10^{-9} for the test cases of r=0.01 and r=100 we have been running, and even better elsewhere.  The derivatives during ingress/egress for r=0.01 could still use some improvement in precision, but overall this is pretty impressive.
The code which implements this is transit_poly.jl (I've added a version of the functions which computes derivatives with respect to the input parameters), which calls IJv_derivative.jl which computes the derivatives described above.
The following plots show the derivatives with respect to the r, b, and u_i parameters for the nth-order limb-darkening function.

This is now implemented, and seems to work with good precision everywhere (although not machine precision yet).


Using generics?

I'm trying to use generics to be able to pass around an entity definition, and use kysely to operate on it. Is this possible?
With this code, calling selectAll().execute() is typed as an array - (Person & Pet)[]. Would expect it to be ItemSchema[K][]
type Pet = {
    ownerName: string
}
type Person = {
    name: string
}
type ItemSchema = {
    persons: Person
    pets: Pet
}
type EntityDef<K extends keyof ItemSchema> = {
    table: TableExpression<ItemSchema, K>
}
function doStuff<K extends keyof ItemSchema>(db: Kysely<ItemSchema>, def: EntityDef<K>) {
    const results = db.selectFrom(def.table).selectAll().execute();
}

ItemSchema[keyof ItemSchema] is Person $ Pet. Everything works correctly there. My have misunderstood how typescript works. The type cannot be narrower until you use the doStuff somewhere, but the implementation types cannot change based on the call site.


chore(functions): use proper Java test naming

~Please do not merge until cl/350839917 is approved.~

Test run looks outdated for some reason; rerunning.

Test run looks outdated for some reason; rerunning.


Add bootsnap to optimize boot time

Currentry, fastlane takes a time nearly 1 sec even if it displays help message.
$ time bundle exec fastlane -h > /dev/null
bundle exec fastlane -h > /dev/null  0.73s user 0.22s system 98% cpu 0.966 total

If you create new lane/action by trial and error, I think it is useful if boot time will be reduced.
This patch will reduce the boot time 0.966 sec -> 0.584 sec using bootsnap gem.
https://github.com/Shopify/bootsnap
Seems fastlane requires many Ruby files such as plugins/helpers and it takes a time where parses/generates AST and Ruby instruction sequences.
bootsnap gem generates Ruby instruction sequences cache and it will be able to reduce boot time.
At first boot, bootsnap generates Ruby instruction sequences cache and it take a time.
$ time bundle exec fastlane -h > /dev/null
bundle exec fastlane -h > /dev/null  0.94s user 0.45s system 98% cpu 1.420 total

But, after generated Ruby instruction sequences cache, boot time will be reduced.
$ time bundle exec fastlane -h > /dev/null
bundle exec fastlane -h > /dev/null  0.43s user 0.14s system 97% cpu 0.584 total

My environment is

MacBook 2017
CPU : 1.4 GHz Core i7
Memory : 16 GB
OS : macOS 10.13

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[ ] I've updated the documentation if necessary.

Motivation and Context

Description

I signed it!

This is awesome! 🚀

Hey @Watson1978, thanks for your contribution, this is great. I'm a little worried that adding another dependency for this, might have unexpected side effects. e.g. does it affect the way plugins are loaded, or the homebrew based fastlane installation, or the Fabric mac app based installation?
I want to be sure we're not breaking any existing fastlane setups, that worked fine so far.

Thank you for your reply.
OK I need to investigate about installation process in fastlane with more carefully.
However, you can stop to use this feature ease if it could not be installed with homebrew or another.
You just catch the exception in require with begin/rescue/end, like,
diff --git a/bin/fastlane b/bin/fastlane
index a5c215d75..5ead9716c 100755
--- a/bin/fastlane
+++ b/bin/fastlane
@@ -4,16 +4,19 @@ if RUBY_VERSION < '2.0.0'
   abort "fastlane requires Ruby 2.0.0 or higher"
 end

-require 'bootsnap'
-require 'fastlane/version'
-Bootsnap.setup(
-  cache_dir: "/tmp/fastlane-#{RUBY_VERSION}-#{Fastlane::VERSION}",
-  load_path_cache: true,
-  autoload_paths_cache: false,
-  disable_trace: true,
-  compile_cache_iseq: true,
-  compile_cache_yaml: true
-)
+begin
+  require 'bootsnap'
+  require 'fastlane/version'
+  Bootsnap.setup(
+    cache_dir: "/tmp/fastlane-#{RUBY_VERSION}-#{Fastlane::VERSION}",
+    load_path_cache: true,
+    autoload_paths_cache: false,
+    disable_trace: true,
+    compile_cache_iseq: true,
+    compile_cache_yaml: true
+  )
+rescue LoadError
+end

 $LOAD_PATH.push File.expand_path("../../lib", __FILE__)

hmm, looks like bootsnap gem depends on bundler.
When you run fastlane command without bundle exec, bootsnap raises exception.
$ rake build
fastlane 2.60.1 built to pkg/fastlane-2.60.1.gem.

$ gem install pkg/fastlane-2.60.1.gem

$ fastlane -h
/Users/watson/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/bootsnap-1.1.5/lib/bootsnap/load_path_cache/path_scanner.rb:18:in `<module:PathScanner>': uninitialized constant Bootsnap::LoadPathCache::PathScanner::Bundler (NameError)
...

Hey @Watson1978, apologies for the delayed response here. I am going to close this PR for now as we are hesitant to introduce any more dependencies that are not totally necessary to fastlane's functionality. Thank you for the contribution though! Let us know if there is anything else we can do to help and we hope to see some more PRs from you in the future! 🚀  🐙

@Watson1978 I actually would like to see this looked at again, as fastlane really tends to be a bit on the slower side sometimes.
Can you provide timings on the speedup without bundle exec?

@janpio If bootsnap will be shipped with my patch (https://github.com/Shopify/bootsnap/pull/91) , I will send this pull request again :)


Category names for server don't read well.

IMO add a label on top of the group and drop the ":S" which  is cryptic.

 doesn't work at the top

See line 208 of serverservicesdsl.ts
        return [
            <SeparatorDefinition>{
                kind: "sep",
            },
            <LabelDefinition>{
                kind: "label",
                text: "Servers",
            },
            ...serverServicesCategories,
        ]
    }

Hummm blocky may not support those at top level then.

From: Tom Ball @.>
Sent: Saturday, July 3, 2021 7:02:32 PM
To: microsoft/jacdac @.>
Cc: Peli de Halleux @.>; Author @.>
Subject: Re: [microsoft/jacdac] Category names for server don't read well. (#509)
See line 208 of serverservicesdsl.ts
    return [
        <SeparatorDefinition>{
            kind: "sep",
        },
        <LabelDefinition>{
            kind: "label",
            text: "Servers",
        },
        ...serverServicesCategories,
    ]
}

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fjacdac%2Fissues%2F509%23issuecomment-873437877&data=04|01|jhalleux%40microsoft.com|2dd43d86931444a85c1908d93e44597f|72f988bf86f141af91ab2d7cd011db47|1|0|637609285541536704|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Po7OjjgDgOrvJycoba0qbi%2BcD6lE%2BWjv2uKYWMl8R6I%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAA73QKMFVWD2OHGL76VIXUDTV47CRANCNFSM47X335QA&data=04|01|jhalleux%40microsoft.com|2dd43d86931444a85c1908d93e44597f|72f988bf86f141af91ab2d7cd011db47|1|0|637609285541536704|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Vq3hfxdUH5uD%2F%2FFVuWv5eUSnzG%2BGHOFgcpI1mM1k3Vg%3D&reserved=0.


Research what postgres drivers are available for Swift and what can be done to build off of these

Hey, I am Fahad Zaheer, excited to work on this project

Here's one used inside an ORM:
https://github.com/vapor/fluent-postgres-driver
Here's a standalone one:
https://github.com/codewinsdotcom/PostgresClientKit

Hi this is Steve Shin from Vancouver Team.

https://github.com/codewinsdotcom/PostgresClientKit
This one is convenient and easy to use. I have started working on this.
We can design some wrapper classes and functions, the same as in python and get it done

This task is completed with my draft pull request, will start with AGE part now

Hey, I am Mahmudul Islam, excited to work on this project


Light difference question

Light difference question
Description
The project exported to html is much lighter when viewed in a browser than in the editor. The dark parts on the exported view is visibly lighter.
What causes this? What did I do wrong?
Test screenshot: (https://prnt.sc/tmopi9)
Version

0.97.14

Platform

Web Version []
Windows [X]
Linux []

Hello
Well they should be the same when running on the editor and on export.
There is the possibility that the export was using  a older runtime from cache, that could expain the differente (between some versions there are some tweaks in the lighting model that can cause slight changes).
Another options it that the exported version might not be using the correct tonemapping settings (i have to check it).
This can be a bug i will have to take a closer look into it.
Thanks a lot!

Hello
Thanks for your answer!
The runtime version is 0.97.1, not minimized js and the tonemappings type in my editor is Cineon.
Sadly, the tonemappings are different in the editor and the browser version (I think, the browser use the default tonemappings type (None)  )
If i try console.log the RendererConfiguration.prototype.fromJSON 'a' parameter, i see this:
toneMapping: 3
but if i hardcoded the following, inside the RendererConfiguration.prototype.fromJSON function:
 this.toneMapping = THREE.CineonToneMapping;
the lights/tonemappings looks correct.

Thanks a lot for debugging this issue. It should be then a serialization/parsing problem with the renderer configuration.
I will take a close look into it today.
Thanks a lot!


add work vlan and refactoring state name

Ran Plan for project: local-lhr-unifi dir: infrastructure/local/lhr/unifi workspace: terragrunt
Show Output
03:24:20.982 INFO   Downloading Terraform configurations from ../../.. into ./.terragrunt-cache/NH-kQUcMzmyih1BwT2s78Ce04vA/xle0S0rGn88d7-up2AflODSVl6M
03:24:21.347 STDOUT tofu: Initializing the backend...
03:24:21.653 STDOUT tofu:
03:24:21.653 STDOUT tofu: Successfully configured the backend "s3"! OpenTofu will automatically
03:24:21.653 STDOUT tofu: use this backend unless the backend configuration changes.
03:24:21.739 STDOUT tofu: Initializing provider plugins...
03:24:21.739 STDOUT tofu: - Reusing previous version of vexxhost/uptimerobot from the dependency lock file
03:24:21.853 STDOUT tofu: - Reusing previous version of paultyng/unifi from the dependency lock file
03:24:21.909 STDOUT tofu: - Reusing previous version of hashicorp/aws from the dependency lock file
03:24:21.980 STDOUT tofu: - Reusing previous version of backblaze/b2 from the dependency lock file
03:24:22.019 STDOUT tofu: - Reusing previous version of cloudflare/cloudflare from the dependency lock file
03:24:22.067 STDOUT tofu: - Reusing previous version of integrations/github from the dependency lock file
03:24:23.434 STDOUT tofu: - Installing backblaze/b2 v0.8.12...
03:24:25.709 STDOUT tofu: - Installed backblaze/b2 v0.8.12. Signature validation was skipped due to the registry not containing GPG keys for this provider
03:24:26.987 STDOUT tofu: - Installing cloudflare/cloudflare v4.43.0...
03:24:28.864 STDOUT tofu: - Installed cloudflare/cloudflare v4.43.0 (signed, key ID C76001609EE3B136)
03:24:30.114 STDOUT tofu: - Installing integrations/github v6.2.2...
03:24:31.276 STDOUT tofu: - Installed integrations/github v6.2.2 (signed, key ID 38027F80D7FD5FB2)
03:24:32.519 STDOUT tofu: - Installing vexxhost/uptimerobot v0.8.2...
03:24:33.585 STDOUT tofu: - Installed vexxhost/uptimerobot v0.8.2. Signature validation was skipped due to the registry not containing GPG keys for this provider
03:24:34.796 STDOUT tofu: - Installing paultyng/unifi v0.41.0...
03:24:35.835 STDOUT tofu: - Installed paultyng/unifi v0.41.0. Signature validation was skipped due to the registry not containing GPG keys for this provider
03:24:37.072 STDOUT tofu: - Installing hashicorp/aws v5.70.0...
03:24:53.366 STDOUT tofu: - Installed hashicorp/aws v5.70.0 (signed, key ID 0C0AF313E5FD9F80)
03:24:53.366 STDOUT tofu: Providers are signed by their developers.
03:24:53.367 STDOUT tofu: If you'd like to know more about provider signing, you can read about it here:
03:24:53.367 STDOUT tofu: https://opentofu.org/docs/cli/plugins/signing/
03:24:53.367 STDOUT tofu: OpenTofu has made some changes to the provider dependency selections recorded
03:24:53.367 STDOUT tofu: in the .terraform.lock.hcl file. Review those changes and commit them to your
03:24:53.367 STDOUT tofu: version control system if they represent changes you intended to make.
03:24:53.381 STDOUT tofu: OpenTofu has been successfully initialized!

03:25:06.227 STDOUT tofu: OpenTofu used the selected providers to generate the following execution
03:25:06.227 STDOUT tofu: plan. Resource actions are indicated with the following symbols:
03:25:06.227 STDOUT tofu:   - destroy
03:25:06.227 STDOUT tofu: OpenTofu will perform the following actions:
03:25:06.227 STDOUT tofu:   # unifi_firewall_group.rfc1918 will be destroyed
03:25:06.227 STDOUT tofu:   # (because unifi_firewall_group.rfc1918 is not in configuration)
03:25:06.227 STDOUT tofu:   - resource "unifi_firewall_group" "rfc1918" {
03:25:06.227 STDOUT tofu:       - id      = "67145a5829233015f715173d" -> null
03:25:06.227 STDOUT tofu:       - members = [
03:25:06.228 STDOUT tofu:           - "<IP_ADDRESS>/8",
03:25:06.228 STDOUT tofu:           - "<IP_ADDRESS>/12",
03:25:06.228 STDOUT tofu:           - "<IP_ADDRESS>/16",
03:25:06.228 STDOUT tofu:         ] -> null
03:25:06.228 STDOUT tofu:       - name    = "RFC1918 IP Addresses" -> null
03:25:06.228 STDOUT tofu:       - site    = "default" -> null
03:25:06.228 STDOUT tofu:       - type    = "address-group" -> null
03:25:06.229 STDOUT tofu:     }
03:25:06.229 STDOUT tofu:   # unifi_firewall_group.this["vlan01"] will be destroyed
03:25:06.229 STDOUT tofu:   # (because unifi_firewall_group.this is not in configuration)
03:25:06.229 STDOUT tofu:   - resource "unifi_firewall_group" "this" {
03:25:06.229 STDOUT tofu:       - id      = "67145a5829233015f715173f" -> null
03:25:06.229 STDOUT tofu:       - members = [
03:25:06.229 STDOUT tofu:           - "<IP_ADDRESS>/24",
03:25:06.229 STDOUT tofu:         ] -> null
03:25:06.229 STDOUT tofu:       - name    = "vlan01" -> null
03:25:06.229 STDOUT tofu:       - site    = "default" -> null
03:25:06.229 STDOUT tofu:       - type    = "address-group" -> null
03:25:06.229 STDOUT tofu:     }
03:25:06.229 STDOUT tofu:   # unifi_firewall_group.this["vlan03"] will be destroyed
03:25:06.229 STDOUT tofu:   # (because unifi_firewall_group.this is not in configuration)
03:25:06.229 STDOUT tofu:   - resource "unifi_firewall_group" "this" {
03:25:06.229 STDOUT tofu:       - id      = "67145a5729233015f7151739" -> null
03:25:06.229 STDOUT tofu:       - members = [
03:25:06.229 STDOUT tofu:           - "<IP_ADDRESS>/24",
03:25:06.229 STDOUT tofu:         ] -> null
03:25:06.230 STDOUT tofu:       - name    = "vlan03" -> null
03:25:06.230 STDOUT tofu:       - site    = "default" -> null
03:25:06.230 STDOUT tofu:       - type    = "address-group" -> null
03:25:06.230 STDOUT tofu:     }
03:25:06.230 STDOUT tofu:   # unifi_firewall_group.this["vlan04"] will be destroyed
03:25:06.230 STDOUT tofu:   # (because unifi_firewall_group.this is not in configuration)
03:25:06.230 STDOUT tofu:   - resource "unifi_firewall_group" "this" {
03:25:06.230 STDOUT tofu:       - id      = "67145a5829233015f7151743" -> null
03:25:06.230 STDOUT tofu:       - members = [
03:25:06.230 STDOUT tofu:           - "<IP_ADDRESS>/24",
03:25:06.230 STDOUT tofu:         ] -> null
03:25:06.230 STDOUT tofu:       - name    = "vlan04" -> null
03:25:06.230 STDOUT tofu:       - site    = "default" -> null
03:25:06.230 STDOUT tofu:       - type    = "address-group" -> null
03:25:06.230 STDOUT tofu:     }
03:25:06.230 STDOUT tofu:   # unifi_firewall_group.this["vlan05"] will be destroyed
03:25:06.230 STDOUT tofu:   # (because unifi_firewall_group.this is not in configuration)
03:25:06.231 STDOUT tofu:   - resource "unifi_firewall_group" "this" {
03:25:06.231 STDOUT tofu:       - id      = "67145a5729233015f715173b" -> null
03:25:06.231 STDOUT tofu:       - members = [
03:25:06.231 STDOUT tofu:           - "<IP_ADDRESS>/24",
03:25:06.231 STDOUT tofu:         ] -> null
03:25:06.231 STDOUT tofu:       - name    = "vlan05" -> null
03:25:06.231 STDOUT tofu:       - site    = "default" -> null
03:25:06.231 STDOUT tofu:       - type    = "address-group" -> null
03:25:06.231 STDOUT tofu:     }
03:25:06.231 STDOUT tofu:   # unifi_firewall_group.this["vlan06"] will be destroyed
03:25:06.231 STDOUT tofu:   # (because unifi_firewall_group.this is not in configuration)
03:25:06.231 STDOUT tofu:   - resource "unifi_firewall_group" "this" {
03:25:06.231 STDOUT tofu:       - id      = "67145a5829233015f7151745" -> null
03:25:06.231 STDOUT tofu:       - members = [
03:25:06.231 STDOUT tofu:           - "<IP_ADDRESS>/24",
03:25:06.231 STDOUT tofu:         ] -> null
03:25:06.231 STDOUT tofu:       - name    = "vlan06" -> null
03:25:06.232 STDOUT tofu:       - site    = "default" -> null
03:25:06.232 STDOUT tofu:       - type    = "address-group" -> null
03:25:06.232 STDOUT tofu:     }
03:25:06.232 STDOUT tofu:   # unifi_firewall_group.this["vlan07"] will be destroyed
03:25:06.232 STDOUT tofu:   # (because unifi_firewall_group.this is not in configuration)
03:25:06.232 STDOUT tofu:   - resource "unifi_firewall_group" "this" {
03:25:06.232 STDOUT tofu:       - id      = "67145a5829233015f7151741" -> null
03:25:06.232 STDOUT tofu:       - members = [
03:25:06.232 STDOUT tofu:           - "<IP_ADDRESS>/24",
03:25:06.232 STDOUT tofu:         ] -> null
03:25:06.232 STDOUT tofu:       - name    = "vlan07" -> null
03:25:06.232 STDOUT tofu:       - site    = "default" -> null
03:25:06.232 STDOUT tofu:       - type    = "address-group" -> null
03:25:06.232 STDOUT tofu:     }
03:25:06.232 STDOUT tofu: Plan: 0 to add, 0 to change, 7 to destroy.
03:25:06.232 STDOUT tofu:
03:25:06.232 STDOUT tofu: Changes to Outputs:
03:25:06.232 STDOUT tofu:   - firewall_group_rfc1918 = {
03:25:06.232 STDOUT tofu:       - id = "67145a5829233015f715173d"
03:25:06.233 STDOUT tofu:     } -> null
03:25:06.233 STDOUT tofu:   - firewall_group_vlans   = {
03:25:06.233 STDOUT tofu:       - vlan01 = {
03:25:06.233 STDOUT tofu:           - id = "67145a5829233015f715173f"
03:25:06.233 STDOUT tofu:         }
03:25:06.233 STDOUT tofu:       - vlan03 = {
03:25:06.233 STDOUT tofu:           - id = "67145a5729233015f7151739"
03:25:06.233 STDOUT tofu:         }
03:25:06.233 STDOUT tofu:       - vlan04 = {
03:25:06.233 STDOUT tofu:           - id = "67145a5829233015f7151743"
03:25:06.233 STDOUT tofu:         }
03:25:06.233 STDOUT tofu:       - vlan05 = {
03:25:06.233 STDOUT tofu:           - id = "67145a5729233015f715173b"
03:25:06.233 STDOUT tofu:         }
03:25:06.233 STDOUT tofu:       - vlan06 = {
03:25:06.233 STDOUT tofu:           - id = "67145a5829233015f7151745"
03:25:06.233 STDOUT tofu:         }
03:25:06.233 STDOUT tofu:       - vlan07 = {
03:25:06.233 STDOUT tofu:           - id = "67145a5829233015f7151741"
03:25:06.233 STDOUT tofu:         }
03:25:06.233 STDOUT tofu:     } -> null

:arrow_forward: To apply this plan, comment:atlantis apply -p local-lhr-unifi

:put_litter_in_its_place: To delete this plan and lock, click here
:repeat: To plan this project again, comment:atlantis plan -p local-lhr-unifi

Plan: 0 to add, 0 to change, 7 to destroy.

:fast_forward: To apply all unapplied plans from this Pull Request, comment:atlantis apply

:put_litter_in_its_place: To delete all plans and locks from this Pull Request, comment:atlantis unlock

atlantis apply

Ran Apply for project: local-lhr-unifi dir: infrastructure/local/lhr/unifi workspace: terragrunt
Show Output
03:26:46.304 INFO   Downloading Terraform configurations from ../../.. into ./.terragrunt-cache/NH-kQUcMzmyih1BwT2s78Ce04vA/xle0S0rGn88d7-up2AflODSVl6M
03:26:46.993 STDOUT tofu: Initializing the backend...
03:26:48.899 STDOUT tofu: Initializing provider plugins...
03:26:48.899 STDOUT tofu: - Reusing previous version of paultyng/unifi from the dependency lock file
03:26:49.035 STDOUT tofu: - Reusing previous version of hashicorp/aws from the dependency lock file
03:26:49.088 STDOUT tofu: - Reusing previous version of backblaze/b2 from the dependency lock file
03:26:49.132 STDOUT tofu: - Reusing previous version of cloudflare/cloudflare from the dependency lock file
03:26:49.196 STDOUT tofu: - Reusing previous version of integrations/github from the dependency lock file
03:26:49.248 STDOUT tofu: - Reusing previous version of vexxhost/uptimerobot from the dependency lock file
03:26:49.318 STDOUT tofu: - Using previously-installed paultyng/unifi v0.41.0
03:26:49.894 STDOUT tofu: - Using previously-installed hashicorp/aws v5.70.0
03:26:49.933 STDOUT tofu: - Using previously-installed backblaze/b2 v0.8.12
03:26:49.973 STDOUT tofu: - Using previously-installed cloudflare/cloudflare v4.43.0
03:26:49.992 STDOUT tofu: - Using previously-installed integrations/github v6.2.2
03:26:50.004 STDOUT tofu: - Using previously-installed vexxhost/uptimerobot v0.8.2
03:26:50.005 STDOUT tofu: OpenTofu has been successfully initialized!
03:26:50.005 STDOUT tofu:
03:26:50.005 STDOUT tofu: You may now begin working with OpenTofu. Try running "tofu plan" to see
03:26:50.005 STDOUT tofu: any changes that are required for your infrastructure. All OpenTofu commands
03:26:50.005 STDOUT tofu: should now work.
03:26:50.005 STDOUT tofu: If you ever set or change modules or backend configuration for OpenTofu,
03:26:50.005 STDOUT tofu: rerun this command to reinitialize your working directory.  Resources: 0 added, 0 changed, 7 destroyed.
03:26:55.866 STDOUT tofu:

Automatically merging because all plans have been successfully applied.

Locks and plans deleted for the projects and workspaces modified in this pull request:

dir: infrastructure/local/lhr/unifi workspace: terragrunt


Fix #173: Reportal reportal.proxy.user is set to the report creator inst...

...ead of the report executor

LGTM


How to pass Token to the servlet

Hi I made a test with ng-flow and backend with java and I managed to make it work, mixing the examples from resumable and the others.  As far as I have being reading ng-flow doesnt use $http to make requests, so that seems reasonable why my tokens are not being passed along authInterceptor.
I am using a keycloak server to authenticate, and it generates my tokens.
I added with withCredentials : true, to my config, but I am pretty sure there is something else I should do

I understand headers now but I cant find a way to dynamically add my token to it


Update GCP Icons

Preflight Checklist

[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
The current GCP icon for draw.io is out of date.
Expected behavior
Please include with draw.io the latest set of GCP icons
Additional context
The latest PNG and SVG Icons can be found here
Many services, such as binary authorizations and assets inventory are in the official icon pack but not available in draw.io

+1

Implemented.


Reduce line-height on titles in EDS

Is your feature request related to a problem? Please describe.
In Figma the EDS typographical styles for titles have a to large line height. They are set with 1.5 ratio to the font size. This is too much for titles, which are generally more compact in expression compared to body text where this ratio is normal, and recommended.
Describe the solution you'd like
For titles I would suggest a ratio of 1.1 which would achieve readability and more compactness. In the example below, I also suggest a h1,h2,...{margin-bottom: 1em} and p:last-child { margin-bottom: 2em} to achieve spacing according to difi recommendations.
Additional context
I have made some examples for comparison and to show the context

Figma link: https://www.figma.com/file/cydecneJ8Kc4ErBS3GsoXt/lineheight?node-id=0%3A1

Great, thank you 😊 We do have typography on our list this autumn, we’re well aware that there’s room for improvement in this area, so we’ll definitely take your proposal into consideration.

blocked by #918

The suggested change of line height for Heading1 is 1,1 of font size. I think this is too little. I agree that 1,5 in large headings are too much, though. My preference would be 1,3. In addition to the example made in this issue I have made some examples here. What do you say @lucasveil and @vnys ?

I didn't find any Difi recommendation on the subject (specific to line-height) and according to Design System is the 1.5 ratio the "rule of thumb". @vnys would be nice to have your feedback on this?

Damn, I wrote a lot and it disappeared before I managed to hit comment 🤦🏻♂ I need a draft function. Short version, the success criterion 1.4.12 AA says 1.5em for line-height, but even Deque use 1.35em for headings on their the web site – so I think the most important thing here is to focus on body copy.

Agreed @vnys. I'd say we go ahead with 1,3. That reads well.

Just to throw in there, inspecting https://www.uutilsynet.no/wcag-standarden/sidetittel-navigasjon/221 shows using line-height: 1,3  also (overriding a default 1,2 🤔)

hm, interesting. Maybe 1,2 was too close the..

On a side note, I added some examples of type scales in that same page in Figma – that’s also something we’ve had in the backlog for a while to improve – so I thought I’d set up some examples to understand what other projects do.

After a discussion we decided to change the line height from 1,5 to 1,25 for headings H1 - H3.  We have tested different line heights and looked into how others are doing it. For now we keep the font sizes but want to look into an adjustment of the scale later on. We want to gather some more feedback from our users and are planning a Typograpics theme for one of our meet the designer meeting.  We should also change the naming from H1 etc to instead referanse the size of the font and not the semantic.


The following assertion was thrown during performLayout(): 'package:flutter/src/rendering/object.dart': Failed assertion: line 1840 pos 12: '!_debugDoingThisLayout': is not true.

Steps to Reproduce

Execute flutter run on the code sample
...
...

Expected results:
Actual results:

Code sample

Logs

Hello @goodavid. Looks like your issue report isn't complete. Please edit your original comment to include the following:

Minimal reproducible code sample
Logs showing the error
flutter doctor -v output


[2.12.5] No scrolbar when selecting wallet account

I used to get a scrollbar to select account 6 and beyond, this is on both Chrome and Firefox /Windows 10.

We just pushed a fix for this, which is live in Firefox but not Chrome quite yet. Mind retesting in Firefox after confirming that version v2.13.0 is installed?

We just pushed a fix for this, which is live in Firefox but not Chrome quite yet. Mind retesting in Firefox after confirming that version v2.13.0 is installed?

I just checked, the scrollbar is Firefox is back! thanks for the quick fix!


Linking against a dylib which is not safe for use in application extensions

In later versions of Xcode 14, this warning started appearing.
It's discussed in this thread:
https://forums.swift.org/t/set-application-extension-api-only-on-a-spm-package/39333/42
Let's hope that Xcode 15 makes it easy to adjust the package to remove this warning.

I no longer see this warning.


Julia Notebook support for VS Code

I love how I can write python scripts and run them in the interactive notebook on VS Code.  I would love to have a similar feature available for Julia where cells can be separated using #%% or maybe even something else.

Once we make the Notebook API public, this can be done by an extension, thanks!

We are working on support for Julia Notebooks that use the Notebook API in this branch. Things are pretty functional already!


metadata-sidecar should work for ARC files also

Warcio is able to read ARC files, but not write them. Will have to figure out something that can help with that.

We won't need to write actual ARC files for the sidecars, so we should be able to use warcio still to write the sidecar files theoretically. The issue I am thinking there may be is that ARC files don't have an equivalent of WARC fields, so there is no ID affiliated with what would be a "record" in an ARC file, so how do we want to tie the sidecar metadata records back to the ARC in a way that makes them usable? Do we need to convert the ARC files to WARC files?

With 1 line change the warc-metadata-sidecar works for ARC files too. At least with the 2 files I played with. Like you mentioned above, the ARC records do not contain a record ID. One gets generated for the sidecar, but there would be no way to link the sidecar records to the original ARC records they generated from. So, you asked a good question. Do we need to convert the ARC files into WARC files? @vphill

I think the metadata-sidecar should always generate WARC files as output.
We shouldn't change the original files ie convert from arc-warc in this process (if that's what I am understanding).
We can accept that there will be some functionality lost when using arc vs warc.
Is that what you meant?

I think we were wondering if you need the WARC metadata sidecar file that gets generated to have a way to reference it's original individual records. The file itself will be referenced, but each record in the file would not have a reference to it's original record. WARC files that get processed through the warc-metadata-sidecar have this ID WARC-Record-ID: <urn:uuid:956aff57-0466-4041-8c37-a0fd664871b4> and that gets transferred to the sidecar that gets generated, but ARC files don't have any type of identifier. So you may have a sidecar with metadata, but no way to match each individual record on it.

@gracieflores it sounds like it is acceptable that we won't have an ID to explicitly tie the sidecar record to (such as WARC-Record-ID). So, I think it means we won't have WARC-Concurrent-To nor WARC-Warcinfo-ID in the sidecar records. @vphill do you think we should add a field in the sidecar records for something like ARC-Filename-Concurrent-To, so an individual sidecar record could theoretically be tied loosely/inprecisely back to the name of the ARC file it came from, or does this sound not particularly helpful?

Mark says we would likely use the uri and timestamp from the metadata sidecar, so I don't think we need to add anything extra. But I can remove the WARC-Concurrent-To and WARC-Warcinfo-ID from the metadata sidecar records when the file being processed is an ARC file.

When we process an ARC file, the extension will still change to warc.meta.gz?
ex:
file to process - LOC-ENDOFTERM-01-20090122204532-14087-crawling108.us.archive.org.arc.gz
sidecar generated - LOC-ENDOFTERM-01-20090122204532-14087-crawling108.us.archive.org.warc.meta.gz