2 rx588, only one gpu work

logs:
`Jan 21 02:11:04.010 DEBG Received response with id: 0
Jan 21 02:11:04.010 INFO Status for worker miner-rig-0 - Height: 7871, Difficulty: 2, (0/0/0)
Jan 21 02:11:06.087 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:11:06.088 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.833116446s; Graphs per second: 1.200 - Total Attempts: 124
Jan 21 02:11:06.089 INFO Mining: Cuck(at)oo at 1.2003123990664806 gps (graphs per second)
Jan 21 02:11:09.092 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:11:09.092 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.673217113s; Graphs per second: 1.485 - Total Attempts: 128
Jan 21 02:11:09.093 INFO Mining: Cuck(at)oo at 1.4854049023557725 gps (graphs per second)
Jan 21 02:11:12.001 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:11:12.002 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.763280254s; Graphs per second: 1.310 - Total Attempts: 132
Jan 21 02:11:12.002 INFO Mining: Cuck(at)oo at 1.310134769974018 gps (graphs per second)
Jan 21 02:11:13.211 DEBG Client received message: FoundSolution(7871, 3, 29,<PHONE_NUMBER>080616974, [3697601, 38773600, 38976064, 58600793, 62959765, 64507171, 74557868, 92543891, 100502750, 111911141, 117617335, 132219016, 147808651, 149557890, 160667149, 167712929, 198725503, 198784240, 199509300, 215531670, 222431904, 241301903, 255450047, 258438025, 269435177, 287514772, 299394309, 326905322, 331063721, 335804333, 355634332, 374020206, 380198943, 386016559, 402485676, 407577924, 427406638, 454422496, 484815382, 499619723, 504564435, 508370325])
Jan 21 02:11:13.214 DEBG sending request: {"id":"0","jsonrpc":"2.0","method":"submit","params":{"edge_bits":29,"height":7871,"job_id":3,"nonce":8280247823080616974,"pow":[3697601,38773600,38976064,58600793,62959765,64507171,74557868,92543891,100502750,111911141,117617335,132219016,147808651,149557890,160667149,167712929,198725503,198784240,199509300,215531670,222431904,241301903,255450047,258438025,269435177,287514772,299394309,326905322,331063721,335804333,355634332,374020206,380198943,386016559,402485676,407577924,427406638,454422496,484815382,499619723,504564435,508370325]}}
Jan 21 02:11:14.000 DEBG Received message: {"id":"0","jsonrpc":"2.0","method":"submit","result":"ok","error":null}
Jan 21 02:11:14.002 DEBG Received response with id: 0
Jan 21 02:11:14.005 INFO Share Accepted!!
Jan 21 02:11:15.012 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:11:15.012 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.849999074s; Graphs per second: 1.176 - Total Attempts: 136
Jan 21 02:11:15.012 INFO Mining: Cuck(at)oo at 1.17647186989759 gps (graphs per second)
Jan 21 02:11:18.031 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:11:18.034 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.659064365s; Graphs per second: 1.517 - Total Attempts: 140
Jan 21 02:11:18.036 INFO Mining: Cuck(at)oo at 1.517302486836775 gps (graphs per second)
Jan 21 02:11:21.042 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:11:21.042 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.666763704s; Graphs per second: 1.500 - Total Attempts: 144
Jan 21 02:11:21.043 INFO Mining: Cuck(at)oo at 1.4997816977751988 gps (graphs per second)
Jan 21 02:11:24.003 DEBG Received message: {"id":"Stratum","jsonrpc":"2.0","method":"job","params":{"difficulty":2,"height":7872,"job_id":4,"pre_pow":"00010000000000001ec0000000005c457ea400019bd479b1ff4c799978020a0fe1924605d77343d5de72ae0b855f4ef24c0bb74059cd6e5e7e2694513b680da298400bc51c0aebf8016cf2993055152573865c4d85b616f7b0ed0900831e88f758d93ec4a6199f79107c30cdb3b9be4fc07852c39cd2e0f876ab1eaae92e2f2d32c378aa065fd1f086550e2a65f24b46568bd615f2b5cb4dc58ec9ab90e808e7e894d3ae83a0c7dc51f94e6ae893ca71889903a6aa8bc70a5f372872c29c13b887ba6709dfd086add167bcf4bc6dcacbfc04000000000000da1e0000000000008181000003994174801e00000163"}}
Jan 21 02:11:24.015 DEBG Received request type: job
Jan 21 02:11:24.016 INFO Got a new job: JobTemplate { height: 7872, job_id: 4, difficulty: 2, pre_pow: "00010000000000001ec0000000005c457ea400019bd479b1ff4c799978020a0fe1924605d77343d5de72ae0b855f4ef24c0bb74059cd6e5e7e2694513b680da298400bc51c0aebf8016cf2993055152573865c4d85b616f7b0ed0900831e88f758d93ec4a6199f79107c30cdb3b9be4fc07852c39cd2e0f876ab1eaae92e2f2d32c378aa065fd1f086550e2a65f24b46568bd615f2b5cb4dc58ec9ab90e808e7e894d3ae83a0c7dc51f94e6ae893ca71889903a6aa8bc70a5f372872c29c13b887ba6709dfd086add167bcf4bc6dcacbfc04000000000000da1e0000000000008181000003994174801e00000163" }
Jan 21 02:11:24.048 DEBG Miner received message: ReceivedJob(7872, 4, 2, "00010000000000001ec0000000005c457ea400019bd479b1ff4c799978020a0fe1924605d77343d5de72ae0b855f4ef24c0bb74059cd6e5e7e2694513b680da298400bc51c0aebf8016cf2993055152573865c4d85b616f7b0ed0900831e88f758d93ec4a6199f79107c30cdb3b9be4fc07852c39cd2e0f876ab1eaae92e2f2d32c378aa065fd1f086550e2a65f24b46568bd615f2b5cb4dc58ec9ab90e808e7e894d3ae83a0c7dc51f94e6ae893ca71889903a6aa8bc70a5f372872c29c13b887ba6709dfd086add167bcf4bc6dcacbfc04000000000000da1e0000000000008181000003994174801e00000163")
Jan 21 02:11:24.048 DEBG Pause message sent
Jan 21 02:11:24.048 DEBG Resume message sent
Jan 21 02:11:24.048 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:11:24.048 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.897104486s; Graphs per second: 1.115 - Total Attempts: 148
Jan 21 02:11:24.049 INFO Mining: Cuck(at)oo at 1.1146973575606443 gps (graphs per second)
Jan 21 02:11:24.239 DEBG solver_thread - solver_loop_rx got msg: Pause
Jan 21 02:11:24.244 DEBG solver_thread - solver_loop_rx got msg: Resume
Jan 21 02:11:27.053 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:11:27.053 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.645081064s; Graphs per second: 1.550 - Total Attempts: 153
Jan 21 02:11:27.053 INFO Mining: Cuck(at)oo at 1.5501927677108192 gps (graphs per second)
Jan 21 02:11:28.004 DEBG Received message: {"id":"Stratum","jsonrpc":"2.0","method":"job","params":{"difficulty":2,"height":7873,"job_id":5,"pre_pow":"00010000000000001ec1000000005c457ea9000010a2a145fd5b4146cb5a6f93769cb33ef89d5f615fa6018c0291e9ef534a422f8627598a2d65505d3d1b793d52ccc0bf8ce22402aa172c741d587cfdbd51bd72c05485fd948a9ff3978d7cee7bb45e8abcc66ae05c7fd8e31e2ad7a21f4d77ecb7201010afb428df4c51aa080c3a7c4764562b6ac357e619d3560d2d7fa1a01e384a1981a4242398d37fb5e125b02a7b609eff48ff08f5e5956692d5fae003a6aa8bc70a5f372872c29c13b887ba6709dfd086add167bcf4bc6dcacbfc04000000000000da210000000000008184000003995472ce6000000163"}}
Jan 21 02:11:28.005 DEBG Received request type: job
Jan 21 02:11:28.005 INFO Got a new job: JobTemplate { height: 7873, job_id: 5, difficulty: 2, pre_pow: "00010000000000001ec1000000005c457ea9000010a2a145fd5b4146cb5a6f93769cb33ef89d5f615fa6018c0291e9ef534a422f8627598a2d65505d3d1b793d52ccc0bf8ce22402aa172c741d587cfdbd51bd72c05485fd948a9ff3978d7cee7bb45e8abcc66ae05c7fd8e31e2ad7a21f4d77ecb7201010afb428df4c51aa080c3a7c4764562b6ac357e619d3560d2d7fa1a01e384a1981a4242398d37fb5e125b02a7b609eff48ff08f5e5956692d5fae003a6aa8bc70a5f372872c29c13b887ba6709dfd086add167bcf4bc6dcacbfc04000000000000da210000000000008184000003995472ce6000000163" }
Jan 21 02:11:28.055 DEBG Miner received message: ReceivedJob(7873, 5, 2, "00010000000000001ec1000000005c457ea9000010a2a145fd5b4146cb5a6f93769cb33ef89d5f615fa6018c0291e9ef534a422f8627598a2d65505d3d1b793d52ccc0bf8ce22402aa172c741d587cfdbd51bd72c05485fd948a9ff3978d7cee7bb45e8abcc66ae05c7fd8e31e2ad7a21f4d77ecb7201010afb428df4c51aa080c3a7c4764562b6ac357e619d3560d2d7fa1a01e384a1981a4242398d37fb5e125b02a7b609eff48ff08f5e5956692d5fae003a6aa8bc70a5f372872c29c13b887ba6709dfd086add167bcf4bc6dcacbfc04000000000000da210000000000008184000003995472ce6000000163")
Jan 21 02:11:28.056 DEBG Pause message sent
Jan 21 02:11:28.056 DEBG Resume message sent
Jan 21 02:11:28.479 DEBG solver_thread - solver_loop_rx got msg: Pause
Jan 21 02:11:28.479 DEBG solver_thread - solver_loop_rx got msg: Resume
Jan 21 02:11:30.063 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:11:30.064 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.803612306s; Graphs per second: 1.244 - Total Attempts: 157
Jan 21 02:11:30.066 INFO Mining: Cuck(at)oo at 1.2443811431628327 gps (graphs per second)
Jan 21 02:11:33.068 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:11:33.070 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.640838291s; Graphs per second: 1.560 - Total Attempts: 161
Jan 21 02:11:33.072 INFO Mining: Cuck(at)oo at 1.5604560683156805 gps (graphs per second)
Jan 21 02:11:34.002 DEBG sending request: {"id":"0","jsonrpc":"2.0","method":"status","params":null}
Jan 21 02:11:36.008 DEBG Received message: {"id":"0","jsonrpc":"2.0","method":"status","result":{"accepted":1,"difficulty":2,"height":7873,"id":"miner-rig-0","rejected":0,"stale":0},"error":null}
Jan 21 02:11:36.010 DEBG Received response with id: 0
Jan 21 02:11:36.014 INFO Status for worker miner-rig-0 - Height: 7873, Difficulty: 2, (1/0/0)
Jan 21 02:11:36.077 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:11:36.079 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.726836271s; Graphs per second: 1.376 - Total Attempts: 165
Jan 21 02:11:36.079 INFO Mining: Cuck(at)oo at 1.3758256706481837 gps (graphs per second)
Jan 21 02:11:39.085 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:11:39.087 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.662223272s; Graphs per second: 1.510 - Total Attempts: 169
Jan 21 02:11:39.090 INFO Mining: Cuck(at)oo at 1.510064720286665 gps (graphs per second)
Jan 21 02:11:42.007 DEBG Received message: {"id":"Stratum","jsonrpc":"2.0","method":"job","params":{"difficulty":2,"height":7874,"job_id":6,"pre_pow":"00010000000000001ec2000000005c457eb7000011f907b79110ca338fb8705f374fbf34c929e457c83f676d357a0a42f4159da1f6835c3c0e3a432b735173d82b7a2701e8ed3ee920234d6db49ceb2b9b71e29dba6767aa525df34bcdd2d11eba0249ae50c3d87fc294801c41fc89f12dc573799521d688861b592999de88fb6148383d0a82d6c184647233f7cc2d5d1308db85dd809c611ed3389d664418e9c537f0966363cadba3e2bde547ccfc2e288b03a6aa8bc70a5f372872c29c13b887ba6709dfd086add167bcf4bc6dcacbfc04000000000000da22000000000000818500000399681ab94700000163"}}
Jan 21 02:11:42.010 DEBG Received request type: job
Jan 21 02:11:42.012 INFO Got a new job: JobTemplate { height: 7874, job_id: 6, difficulty: 2, pre_pow: "00010000000000001ec2000000005c457eb7000011f907b79110ca338fb8705f374fbf34c929e457c83f676d357a0a42f4159da1f6835c3c0e3a432b735173d82b7a2701e8ed3ee920234d6db49ceb2b9b71e29dba6767aa525df34bcdd2d11eba0249ae50c3d87fc294801c41fc89f12dc573799521d688861b592999de88fb6148383d0a82d6c184647233f7cc2d5d1308db85dd809c611ed3389d664418e9c537f0966363cadba3e2bde547ccfc2e288b03a6aa8bc70a5f372872c29c13b887ba6709dfd086add167bcf4bc6dcacbfc04000000000000da22000000000000818500000399681ab94700000163" }
Jan 21 02:11:42.093 DEBG Miner received message: ReceivedJob(7874, 6, 2, "00010000000000001ec2000000005c457eb7000011f907b79110ca338fb8705f374fbf34c929e457c83f676d357a0a42f4159da1f6835c3c0e3a432b735173d82b7a2701e8ed3ee920234d6db49ceb2b9b71e29dba6767aa525df34bcdd2d11eba0249ae50c3d87fc294801c41fc89f12dc573799521d688861b592999de88fb6148383d0a82d6c184647233f7cc2d5d1308db85dd809c611ed3389d664418e9c537f0966363cadba3e2bde547ccfc2e288b03a6aa8bc70a5f372872c29c13b887ba6709dfd086add167bcf4bc6dcacbfc04000000000000da22000000000000818500000399681ab94700000163")
Jan 21 02:11:42.095 DEBG Pause message sent
Jan 21 02:11:42.097 DEBG Resume message sent
Jan 21 02:11:42.107 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:11:42.108 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.775120627s; Graphs per second: 1.290 - Total Attempts: 174
Jan 21 02:11:42.108 INFO Mining: Cuck(at)oo at 1.290121776103889 gps (graphs per second)
Jan 21 02:11:42.677 DEBG solver_thread - solver_loop_rx got msg: Pause
Jan 21 02:11:42.679 DEBG solver_thread - solver_loop_rx got msg: Resume
Jan 21 02:11:45.099 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:11:45.099 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.662749731s; Graphs per second: 1.509 - Total Attempts: 178
Jan 21 02:11:45.101 INFO Mining: Cuck(at)oo at 1.508865191829101 gps (graphs per second)
Jan 21 02:11:48.019 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:11:48.019 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.68733734s; Graphs per second: 1.455 - Total Attempts: 182
Jan 21 02:11:48.019 INFO Mining: Cuck(at)oo at 1.4548896761523242 gps (graphs per second)
Jan 21 02:11:51.021 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:11:51.023 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.678626837s; Graphs per second: 1.474 - Total Attempts: 186
Jan 21 02:11:51.025 INFO Mining: Cuck(at)oo at 1.473563887365097 gps (graphs per second)
Jan 21 02:11:54.031 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:11:54.032 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.666224809s; Graphs per second: 1.501 - Total Attempts: 190
Jan 21 02:11:54.038 INFO Mining: Cuck(at)oo at 1.5009948391159356 gps (graphs per second)
Jan 21 02:11:55.149 DEBG Client received message: FoundSolution(7874, 6, 29,<PHONE_NUMBER>248815551, [2746287, 21276935, 23549655, 28546397, 54408376, 54670346, 73238298, 89867115, 116365507, 158327105, 166798716, 175519024, 182247953, 183610911, 184457653, 191016526, 194325135, 195465257, 205860665, 209458767, 210916943, 228935541, 233047487, 240457153, 243851433, 268930160, 276146046, 281929941, 318233613, 327572609, 357755141, 376221698, 386280569, 399867695, 404376463, 451163006, 459950233, 472595167, 488112472, 491300482, 519349175, 520658821])
Jan 21 02:11:55.150 DEBG sending request: {"id":"0","jsonrpc":"2.0","method":"submit","params":{"edge_bits":29,"height":7874,"job_id":6,"nonce":7103594248248815551,"pow":[2746287,21276935,23549655,28546397,54408376,54670346,73238298,89867115,116365507,158327105,166798716,175519024,182247953,183610911,184457653,191016526,194325135,195465257,205860665,209458767,210916943,228935541,233047487,240457153,243851433,268930160,276146046,281929941,318233613,327572609,357755141,376221698,386280569,399867695,404376463,451163006,459950233,472595167,488112472,491300482,519349175,520658821]}}
Jan 21 02:11:56.000 DEBG Received message: {"id":"0","jsonrpc":"2.0","method":"submit","result":"ok","error":null}
Jan 21 02:11:56.000 DEBG Received response with id: 0
Jan 21 02:11:56.000 INFO Share Accepted!!
Jan 21 02:11:57.043 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:11:57.044 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.713265623s; Graphs per second: 1.402 - Total Attempts: 194
Jan 21 02:11:57.046 INFO Mining: Cuck(at)oo at 1.4020022383722817 gps (graphs per second)
Jan 21 02:12:00.045 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:12:00.047 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.65649182s; Graphs per second: 1.523 - Total Attempts: 198
Jan 21 02:12:00.049 INFO Mining: Cuck(at)oo at 1.523248225697618 gps (graphs per second)
Jan 21 02:12:03.050 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:12:03.051 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.660896537s; Graphs per second: 1.513 - Total Attempts: 203
Jan 21 02:12:03.053 INFO Mining: Cuck(at)oo at 1.5130961414010256 gps (graphs per second)
Jan 21 02:12:05.000 DEBG sending request: {"id":"0","jsonrpc":"2.0","method":"status","params":null}
Jan 21 02:12:06.009 DEBG Received message: {"id":"0","jsonrpc":"2.0","method":"status","result":{"accepted":2,"difficulty":2,"height":7874,"id":"miner-rig-0","rejected":0,"stale":0},"error":null}
Jan 21 02:12:06.009 DEBG Received response with id: 0
Jan 21 02:12:06.009 INFO Status for worker miner-rig-0 - Height: 7874, Difficulty: 2, (2/0/0)
Jan 21 02:12:06.062 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:12:06.062 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.816969099s; Graphs per second: 1.224 - Total Attempts: 207
Jan 21 02:12:06.062 INFO Mining: Cuck(at)oo at 1.224036504225235 gps (graphs per second)
Jan 21 02:12:09.068 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:12:09.069 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.750150483s; Graphs per second: 1.333 - Total Attempts: 211
Jan 21 02:12:09.071 INFO Mining: Cuck(at)oo at 1.3330658616665851 gps (graphs per second)
Jan 21 02:12:12.079 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:12:12.083 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.671440451s; Graphs per second: 1.489 - Total Attempts: 215
Jan 21 02:12:12.086 INFO Mining: Cuck(at)oo at 1.489335351348976 gps (graphs per second)
Jan 21 02:12:15.082 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:12:15.082 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.654291147s; Graphs per second: 1.528 - Total Attempts: 220
Jan 21 02:12:15.082 INFO Mining: Cuck(at)oo at 1.5283715889862102 gps (graphs per second)
Jan 21 02:12:18.014 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:12:18.015 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 1.097617575s; Graphs per second: 0.911 - Total Attempts: 224
Jan 21 02:12:18.015 INFO Mining: Cuck(at)oo at 0.9110641290524162 gps (graphs per second)
Jan 21 02:12:21.038 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:12:21.038 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.719970761s; Graphs per second: 1.389 - Total Attempts: 228
Jan 21 02:12:21.038 INFO Mining: Cuck(at)oo at 1.3889452935714426 gps (graphs per second)
Jan 21 02:12:24.044 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:12:24.045 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.751707038s; Graphs per second: 1.330 - Total Attempts: 232
Jan 21 02:12:24.045 INFO Mining: Cuck(at)oo at 1.3303054906345042 gps (graphs per second)
Jan 21 02:12:27.068 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:12:27.652 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.694890041s; Graphs per second: 1.439 - Total Attempts: 236
Jan 21 02:12:27.653 INFO Mining: Cuck(at)oo at 1.4390766034881195 gps (graphs per second)
Jan 21 02:12:30.091 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:12:30.092 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.670132444s; Graphs per second: 1.492 - Total Attempts: 240
Jan 21 02:12:30.092 INFO Mining: Cuck(at)oo at 1.4922423305324999 gps (graphs per second)
Jan 21 02:12:33.009 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:12:33.010 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.707533691s; Graphs per second: 1.413 - Total Attempts: 244
Jan 21 02:12:33.010 INFO Mining: Cuck(at)oo at 1.413360257921626 gps (graphs per second)
Jan 21 02:12:36.000 DEBG sending request: {"id":"0","jsonrpc":"2.0","method":"status","params":null}
Jan 21 02:12:36.015 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:12:36.017 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.746232008s; Graphs per second: 1.340 - Total Attempts: 248
Jan 21 02:12:36.020 INFO Mining: Cuck(at)oo at 1.3400658096670655 gps (graphs per second)
Jan 21 02:12:38.008 DEBG Received message: {"id":"0","jsonrpc":"2.0","method":"status","result":{"accepted":2,"difficulty":2,"height":7874,"id":"miner-rig-0","rejected":0,"stale":0},"error":null}
Jan 21 02:12:38.012 DEBG Received response with id: 0
Jan 21 02:12:38.012 INFO Status for worker miner-rig-0 - Height: 7874, Difficulty: 2, (2/0/0)
Jan 21 02:12:39.020 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:12:39.020 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.66127206s; Graphs per second: 1.512 - Total Attempts: 252
Jan 21 02:12:39.020 INFO Mining: Cuck(at)oo at 1.512236884770241 gps (graphs per second)
Jan 21 02:12:42.051 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:12:42.052 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.650463909s; Graphs per second: 1.537 - Total Attempts: 256
Jan 21 02:12:42.052 INFO Mining: Cuck(at)oo at 1.5373643120912956 gps (graphs per second)
Jan 21 02:12:45.058 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:12:45.060 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.659690631s; Graphs per second: 1.516 - Total Attempts: 261
Jan 21 02:12:45.062 INFO Mining: Cuck(at)oo at 1.5158620617123786 gps (graphs per second)
Jan 21 02:12:48.069 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:12:48.069 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.908728856s; Graphs per second: 1.100 - Total Attempts: 265
Jan 21 02:12:48.069 INFO Mining: Cuck(at)oo at 1.1004382587802406 gps (graphs per second)
Jan 21 02:12:51.075 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:12:51.077 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.668046081s; Graphs per second: 1.497 - Total Attempts: 269
Jan 21 02:12:51.079 INFO Mining: Cuck(at)oo at 1.4969027263854273 gps (graphs per second)
Jan 21 02:12:54.084 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:12:54.084 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.826889148s; Graphs per second: 1.209 - Total Attempts: 273
Jan 21 02:12:54.084 INFO Mining: Cuck(at)oo at 1.2093519456854693 gps (graphs per second)
Jan 21 02:12:57.089 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:12:57.093 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.70449818s; Graphs per second: 1.419 - Total Attempts: 277
Jan 21 02:12:57.094 INFO Mining: Cuck(at)oo at 1.4194500828944654 gps (graphs per second)
Jan 21 02:13:00.096 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:13:00.097 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.670138158s; Graphs per second: 1.492 - Total Attempts: 281
Jan 21 02:13:00.098 INFO Mining: Cuck(at)oo at 1.4922296067790846 gps (graphs per second)
Jan 21 02:13:03.039 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:13:03.041 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.857931355s; Graphs per second: 1.166 - Total Attempts: 285
Jan 21 02:13:03.043 INFO Mining: Cuck(at)oo at 1.1655944198472616 gps (graphs per second)
Jan 21 02:13:06.059 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:13:06.059 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.689353367s; Graphs per second: 1.451 - Total Attempts: 289
Jan 21 02:13:06.059 INFO Mining: Cuck(at)oo at 1.4506348236926794 gps (graphs per second)
Jan 21 02:13:07.000 DEBG sending request: {"id":"0","jsonrpc":"2.0","method":"status","params":null}
Jan 21 02:13:08.005 DEBG Received message: {"id":"0","jsonrpc":"2.0","method":"status","result":{"accepted":2,"difficulty":2,"height":7874,"id":"miner-rig-0","rejected":0,"stale":0},"error":null}
Jan 21 02:13:08.005 DEBG Received response with id: 0
Jan 21 02:13:08.005 INFO Status for worker miner-rig-0 - Height: 7874, Difficulty: 2, (2/0/0)
Jan 21 02:13:09.063 DEBG Mining: Plugin 0 - Device 0 () at Cuck(at)oo0 - Status: OK : Last Graph time: 0s; Graphs per second: inf - Total Attempts: 0
Jan 21 02:13:09.063 DEBG Mining: Plugin 1 - Device 1 (Ellesmere) at Cuck(at)oo29 - Status: OK : Last Graph time: 0.662872252s; Graphs per second: 1.509 - Total Attempts: 293
Jan 21 02:13:09.063 INFO Mining: Cuck(at)oo at 1.5085863029910023 gps (graphs per second)
Jan 21 02:13:10.006 DEBG Received message: {"id":"Stratum","jsonrpc":"2.0","method":"job","params":{"difficulty":2,"height":7875,"job_id":7,"pre_pow":"00010000000000001ec3000000005c457f0f0000061a75f3f794e9269231c0461747252270110242c707614bee9ca015eb1dc58bcc997fc9ec70829fb08d0c9acee87dc2c147b7f8bfbdb1453b9bb2d049a751ec2e9515f2f6ba91708ab27d9372fe43ae863e0e24842fffedfef142026d17542e8fa518786479ec00023779bcda90319fa3572d59006a3fa89707db7475bb6700723d75615d0b46336feaf49a0933a1d95f8c4a854589f9f3c0b56efd6b54af4217ad8373d6f6c1a01c360cec1ca7922222562ecfcfbf6b23b8fa1a3fbc68000000000000da2c000000000000818c000003997bc7799c00000163"}}
Jan 21 02:13:10.006 DEBG Received request type: job
Jan 21 02:13:10.006 INFO Got a new job: JobTemplate { height: 7875, job_id: 7, difficulty: 2, pre_pow: "00010000000000001ec3000000005c457f0f0000061a75f3f794e9269231c0461747252270110242c707614bee9ca015eb1dc58bcc997fc9ec70829fb08d0c9acee87dc2c147b7f8bfbdb1453b9bb2d049a751ec2e9515f2f6ba91708ab27d9372fe43ae863e0e24842fffedfef142026d17542e8fa518786479ec00023779bcda90319fa3572d59006a3fa89707db7475bb6700723d75615d0b46336feaf49a0933a1d95f8c4a854589f9f3c0b56efd6b54af4217ad8373d6f6c1a01c360cec1ca7922222562ecfcfbf6b23b8fa1a3fbc68000000000000da2c000000000000818c000003997bc7799c00000163" }
Jan 21 02:13:10.064 DEBG Miner received message: ReceivedJob(7875, 7, 2, "00010000000000001ec3000000005c457f0f0000061a75f3f794e9269231c0461747252270110242c707614bee9ca015eb1dc58bcc997fc9ec70829fb08d0c9acee87dc2c147b7f8bfbdb1453b9bb2d049a751ec2e9515f2f6ba91708ab27d9372fe43ae863e0e24842fffedfef142026d17542e8fa518786479ec00023779bcda90319fa3572d59006a3fa89707db7475bb6700723d75615d0b46336feaf49a0933a1d95f8c4a854589f9f3c0b56efd6b54af4217ad8373d6f6c1a01c360cec1ca7922222562ecfcfbf6b23b8fa1a3fbc68000000000000da2c000000000000818c000003997bc7799c00000163")
Jan 21 02:13:10.064 DEBG Pause message sent
Jan 21 02:13:10.065 DEBG Resume message sent
Jan 21 02:13:10.613 DEBG solver_thread - solver_loop_rx got msg: Pause
Jan 21 02:13:10.615 DEBG solver_thread - solver_loop_rx got msg: Resume`

Closing. Feel free to reopen if this is still relevant.


Nuget cleanup

No need to store Nuget packages to repository, Visual Studio will download them at compilation if needed.

Thanks for the tip! I appreciate your help.


Make keep alive ping response an event

Dispatch ping response times via the Tortoise.Events pubsub registry.
When applied this will change the way we register processes in the registry. Previously a :connection would be stored under {client_id, type} where type was the message type like :connection. Now we store type and the value will be the client_id. This will allow us to register and unregister multiple client_ids.
Lastly it has been made possible to match every client id on a node by specifying :_ as the client id when registering for an event type.
Missing before this can be merged: documentation and an update of the changelog file.

Pull Request Test Coverage Report for Build 401

8 of 9 (88.89%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 86.424%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/tortoise/connection.ex
4
5
80.0%

Totals

Change from base Build 397:
0.02%

Covered Lines:
522

Relevant Lines:
604

💛  - Coveralls


"Achievements database has been reset."

If I try to download any of the achievements, it just has a progress bar that works for a while. Then it goes "Achievements database has been reset" and the numbers are still 0/something.
I gave it my Steam API key. And the log doesn't say anything either, so I'm unsure how to even give more info on this :x
Tried Get missing, as well as Refresh data. Even tried deleting what I think is the folder of it in ExtensionsData to see if there was some corrupted storage somehow.

Are this manipulations did in settings menu?
Are not there any achievements on game selected and/or the main plugin screen?
Can you show the Playnite.log after try this manipulations?

Nevermind I'm dumb... working on a custom theme and didn't style the checkbox background yet, so they have the same colour as the background, and thus didn't realize there was a checkbox to turn on ¬_¬
Sorry :x


java.lang.NoClassDefFoundError: okhttp3/internal/platform/Platform

The version of OkHttp I am using is 3.14.4. Some exceptions occur on some Android 4.4 models.
java.lang.NoClassDefFoundError: okhttp3/internal/platform/Platform
    at okhttp3.internal.tls.CertificateChainCleaner.get(CertificateChainCleaner.java:41)
    at okhttp3.OkHttpClient$Builder.sslSocketFactory(OkHttpClient.java:782)

You will need to use 3.12 branch for these devices.

I want to know what is the root cause of this problem. Thank you！

https://cashapp.github.io/2019-02-05/okhttp-3-13-requires-android-5


https://replicate.com/camenduru/attribute-control is down?

Just saw this at ECCV Workshops - congrats
but - https://replicate.com/camenduru/attribute-control is down? @camenduru

Thanks! The replicate space by camenduru is not officially affiliated with us, I just added it to the readme since I thought it might be useful. /
If I have time after the ICLR submission deadline, I might add a HF space to have an official demo :)

I’m waiting for an answer.

@yosun here: https://github.com/camenduru/attribute-control-replicate
and more: https://github.com/camenduru#-replicate-demos

@replicate omg


create floor map  screen

Idea Description
create floor map  screen without design
issue devided apply design
Reference images and links
coming soon

I think there isn't a design now, so just do this. 🙏
https://github.com/DroidKaigi/conference-app-2022/pull/129

Can i take this issue?

Of course! Thanks as always. Assigned 👍


Error converting shapes due to mismatched size of X and s2

I'm getting this crazy error occasionally while running pybads with specify_target_noise=true. It looks like somehow s2 ends up with more elements than rows of X. Any idea what could be going on here?
Unfortunately, I cant create a reprex—it only happens occasionally with my own model fitting code...
Traceback (most recent call last):
  File "/dfs6/pub/nharhen/foraging/model_fitting/experiment1k_kids/cross_val/bads.py", line 39, in <module>
    result = bads.optimize()
  File "/data/homezvol3/nharhen/.local/lib/python3.9/site-packages/pybads/bads/bads.py", line 1239, in optimize
    ) = self._search_step_(gp)
  File "/data/homezvol3/nharhen/.local/lib/python3.9/site-packages/pybads/bads/bads.py", line 1554, in _search_step_
    gp, gp_exit_flag = local_gp_fitting(
  File "/data/homezvol3/nharhen/.local/lib/python3.9/site-packages/pybads/bads/gaussian_process_train.py", line 402, in local_gp_fitting
    gp, hyp_gp, res, exit_flag = _robust_gp_fit_(
  File "/data/homezvol3/nharhen/.local/lib/python3.9/site-packages/pybads/bads/gaussian_process_train.py", line 542, in _robust_gp_fit_
    new_hyp, _, res = tmp_gp.fit(
  File "/data/homezvol3/nharhen/.local/lib/python3.9/site-packages/gpyreg/gaussian_process.py", line 1008, in fit
    X, y, s2 = self._convert_shapes(X, y, s2)
  File "/data/homezvol3/nharhen/.local/lib/python3.9/site-packages/gpyreg/gaussian_process.py", line 2555, in _convert_shapes
    s2 = s2.reshape(N, 1)
ValueError: cannot reshape array of size 55 into shape (51,1)

Thanks for the report! This seems tough to debug if it happens randomly.
@GurjeetSinghSangra is looking into it but this might take a while.


Fill Lobby doesn't work after update

:)

Thank you for the report. I have been looking into this for a while, but I am still unsure on what they actually changed.
The vanillaCompatible attribute has been added with the last commit, but it does not seem to fix the problem.

Okay, I think I have it working again. Please test 1.2.0 and let me know.

Yup, it is working now. Thanks!

Yup, it's working now. Thanks!


KeyError: 'DELIVERED_READ'

Got this today when visiting an HS with a client:
NOTICE[Mon May 28 13:31:54 2018]: Connected to Tor version <IP_ADDRESS>-alpha-dev (git-c27c86d113108107)
...
DEBUG[Mon May 28 13:32:16 2018]: 650 CIRC_BW ID=27 READ=389 WRITTEN=10 TIME=2018-05-28T10:32:16.010609
Exception in thread Event Notifier:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.7/threading.py", line 754, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/home/f/.local/lib/python2.7/site-packages/stem/control.py", line 953, in _event_loop
    self._handle_event(event_message)
  File "/home/f/.local/lib/python2.7/site-packages/stem/control.py", line 3727, in _handle_event
    listener(event_message)
  File "/home/f/Computers/tor/prop247/vanguards/src/vanguards/bandguards.py", line 122, in circbw_event
    delivered_read = int(event.keyword_args["DELIVERED_READ"])
KeyError: 'DELIVERED_READ'

Looks like you're using a tor master built before #25903 was merged. This used to work for you because the vanguards script used to explicitly check for those fields on every CIRC_BW event. In vanguards commit ec8694ba0f0517a5e3bfd41f89b0d961eac5274e I removed the check on every CIRC_BW event and switched to a version comparison against <IP_ADDRESS>-alpha for efficiency, since #25903 was merged prior to the first alpha release.
If you update your Tor the issue should go away. I don't think this is a bug.

Oh woops. The first tor 0.3.4 release was actually <IP_ADDRESS>. I just pushed a16677fe5192242cb38af070d00eaff90cf66d04 which should also stop this traceback.

LGTM.


Lock key locker

Description of the new feature / enhancement
Set the state of the various lock keys (num lock, caps lock, scroll lock) etc to a user-defined state at startup.
Prevent the lock from changing state, possibly unless a key combination is used (e.g. number lock is always on, unless the user presses Win + NumLock to toggle it).
Optionally, keys could revert to their predefined state at system idle.
Scenario when this would be used?
I find it useful to have the keyboard always be in my preferred state, regardless of meddling by other programs, or my own clumsiness or forgetfulness.
Supporting information
I used to use a program called NumLocker to do this, but it doesn't seem to work great in current builds of Windows 10.

Duplicate of #1196


@ symbol optional when passing EventCallback to child component

I'm seeing that the @ in OnClickCallback="@ShowMessage" below is optional in practice but don't see any mention of that in documentation. Is there a guideline on this?
<ChildComponent Title="Panel Title from Parent"
                OnClickCallback="@ShowMessage">
    Content of the child component is supplied
    by the parent component.
</ChildComponent>

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: aa724f22-3a49-c7f6-1500-ac2d8dde5894
Version Independent ID: 5e8ef502-ccf9-659d-f25a-0f8f3c75f6e0
Content: ASP.NET Core Blazor event handling
Content Source: aspnetcore/blazor/components/event-handling.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @mrlife ... AFAIK, it's by convention. Every product unit sample/example uses this convention. I'll add a remark on this to the topic and then see if on review my hunch is correct or not.


drivers: can: socketCAN: move code from drivers to its own file

Cleanup the drivers from socketCAN and make its own driver that instantiates the net interface.

Doc CI fail is unrelated.

Please rebase to get the documentation build fix from #41865.

Just tested on nucleo_g474 and could not get it working.
Need to investigate what changed during the submission of this patch and now.

Just tested on nucleo_g474 and could not get it working. Need to investigate what changed during the submission of this patch and now.

What is the nature of the errors, you are seeing? I have just tested this PR with samples/net/sockets/can on two twr_ke18f boards without issues.

Tx issues.
API sample works fine.

Tx issues. API sample works fine.

@alexanderwachter Any progress on this? Any more information on the errors, you are seeing? Are they also present on main?

Tx issues. API sample works fine.

@alexanderwachter Any progress on this? Any more information on the errors, you are seeing? Are they also present on main?

@alexanderwachter Please provide further details on the issues you are seeing?

@henrikbrixandersen it was a stack overflow, caused by log immediate and a -115. I used the wrong symbol for the loopback Kconfig (forgot the CONFIG_ prefix).
However, works now!


Error on decodeNotificationPayload

Hi! I am so excited to see this library, thank you for creating it.
I set everything up and attempted to use const payload = await decodeNotificationPayload(signedPayload). However, I got an error:
(node:1) UnhandledPromiseRejectionWarning: TypeError: crypto_1.X509Certificate is not a constructor
[cookup-action-service] [2022-05-20 21:43:16]     at /usr/src/app/node_modules/app-store-server-api/dist/cjs/Decoding.js:133:60
[cookup-action-service] [2022-05-20 21:43:16]     at Array.map (<anonymous>)
[cookup-action-service] [2022-05-20 21:43:16]     at validateCertificates (/usr/src/app/node_modules/app-store-server-api/dist/cjs/Decoding.js:133:34)
[cookup-action-service] [2022-05-20 21:43:16]     at /usr/src/app/node_modules/app-store-server-api/dist/cjs/Decoding.js:111:29
[cookup-action-service] [2022-05-20 21:43:16]     at step (/usr/src/app/node_modules/app-store-server-api/dist/cjs/Decoding.js:52:23)
[cookup-action-service] [2022-05-20 21:43:16]     at Object.next (/usr/src/app/node_modules/app-store-server-api/dist/cjs/Decoding.js:33:53)
[cookup-action-service] [2022-05-20 21:43:16]     at /usr/src/app/node_modules/app-store-server-api/dist/cjs/Decoding.js:27:71
[cookup-action-service] [2022-05-20 21:43:16]     at new Promise (<anonymous>)
[cookup-action-service] [2022-05-20 21:43:16]     at __awaiter (/usr/src/app/node_modules/app-store-server-api/dist/cjs/Decoding.js:23:12)
[cookup-action-service] [2022-05-20 21:43:16]     at getKey (/usr/src/app/node_modules/app-store-server-api/dist/cjs/Decoding.js:106:74)
[cookup-action-service] [2022-05-20 21:43:16] (node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)

Any ideas?

Hi Raquel,
Make sure you are using Node.js 15.6.0 or later. This is where X509Certificate was introduced.


Improve SafeMoney ergonomics

Wishlist:

Discrete lifting (allowing pconstant :: Discrete gt -> Term s (PDiscrete gt))
pdiscrete vs discrete quasiquoter
property tests for extracting to and from PValue

I think these 3 features are small enough and ought to be relatively easy to implement in a fell swoop in order to improve ergonomics. Sadly any other ergonomic improvements are blocked by https://github.com/Plutonomicon/plutarch/issues/308.

I think this is kind of done now, considering we use plutarch-safemoney now. We don't have property tests, but everything else is satisfactory.


[mini-surround] Can the surrounding be highlighted automatically when matching?

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md

Module(s)
mini-surround
Description
Hello.
Can the surrounding be highlighted automatically when matching?
For example, the text is:
"te_st text"

And cursor is on _.
If sr" is pressed, the plugin will highlight the " on both sides.
And if saiw is pressed, the plugin will highlight test.
Well, it's just like nvim-surround.
I know this plugin can highlight surrounding with sh, but it needs to be pressed separately, and it can't highlight text object.

Hi!
Sorry, no, this is by design. Surrounding highlighting is expected to be done on demand while highlighting textobject seems a bit excessive. And it usually adds visual noise in case user already wants what is going to be replaced/surrounded. So this original feature from machakann/vim-sandwich will not be supported.

Is it possible to call the surrounding highlight function when sr<char> is pressed, just like sh<char>.

No, I don't that under current implementation it is possible.


Automatize realeasing by using a script

A script to generate a release PR will be nice to automatize the process. It will require:

[ ] Checkout to master, and assess that there is no change to be included
[ ] Create new release branch.
[ ] It will be optimal if we can parse the CHANGELOG to guess the version number, and modify it accordingly. If so, add a commit with the version number and this change.
[ ] Generate the javadoc with gradle and move to the correct folder (requires #202). Commit with "Release javadoc"
[ ] Generate end-user documentation with Barclay (blocked by #182 and #201) and move to the correct folder. Commit with "Release documentation"
[ ] Push to the repository

Of course, it will require some review of the pull request, but it will simplify it.

I added the first draft of this script in #235, but it still requires some work...

Added the docgen part in 1bf5a5c2f499612b16da43a7cafd19fa18853880


feat: Add Karpenter v1beta1 compatibility

Description
Add IAM support for Karpenter v1beta1 resources.
Motivation and Context
The recent Karpenter v0.32 release added support for v1beta1 resources, as described in https://github.com/aws/karpenter/blob/main/designs/v1beta1-full-changelist.md. As part of this change, new permissions are needed such as the ability to create instance profiles.
The new controller IAM policy is described in https://github.com/aws/karpenter/blob/main/website/content/en/preview/upgrading/v1beta1-controller-policy.json
This PR adds a minimal set of changes for v0.32 compatibility, specifically around instance profiles. This gives the IRSA role the ability to create any instance profile in the account, without attempting to scope it down based on tags as https://github.com/aws/karpenter/pull/3948 would have done.
Breaking Changes
No breaking changes, only adds permissions.
How Has This Been Tested?

[x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[ ] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

I still need to re-test, I was getting some errors
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x1f1f97c]

goroutine 492 [running]:
github.com/aws/karpenter/pkg/cloudprovider.(*CloudProvider).resolveNodeClassFromNodePool(0xc00086a370, {0x308db90, 0xc001042b10}, 0xc0017541c0)
	github.com/aws/karpenter/pkg/cloudprovider/cloudprovider.go:269 +0x19c
github.com/aws/karpenter/pkg/cloudprovider.(*CloudProvider).GetInstanceTypes(0xc00086a370, {0x308db90, 0xc001042b10}, 0xc0017541c0)
	github.com/aws/karpenter/pkg/cloudprovider/cloudprovider.go:175 +0x4b
github.com/aws/karpenter-core/pkg/cloudprovider/metrics.(*decorator).GetInstanceTypes(0xc00047abe0, {0x308db90, 0xc001042b10}, 0xc00065a6c0?)
	github.com/aws/karpenter-core@v0.32.1/pkg/cloudprovider/metrics/cloudprovider.go:139 +0x15c
github.com/aws/karpenter-core/pkg/controllers/disruption.buildNodePoolMap({0x308db90, 0xc001042b10}, {0x309d980, 0xc00065a6c0}, {0x3094388, 0xc00047abe0})
	github.com/aws/karpenter-core@v0.32.1/pkg/controllers/disruption/helpers.go:203 +0x1fa
github.com/aws/karpenter-core/pkg/controllers/disruption.GetCandidates({0x308db90, 0xc001042b10}, 0x0?, {0x309d980, 0xc00065a6c0}, {0x30612a0, 0xc0006254b8}, {0x3091a68, 0x47a3ca0}, {0x3094388, ...}, ...)
	github.com/aws/karpenter-core@v0.32.1/pkg/controllers/disruption/helpers.go:178 +0x7a
github.com/aws/karpenter-core/pkg/controllers/disruption.(*Controller).disrupt(0xc000492f00, {0x308db90, 0xc001042b10}, {0x308e9b8?, 0xc000a3aa40?})
	github.com/aws/karpenter-core@v0.32.1/pkg/controllers/disruption/controller.go:156 +0x3c5
github.com/aws/karpenter-core/pkg/controllers/disruption.(*Controller).Reconcile(0xc000492f00, {0x308db90, 0xc001042b10}, {{{0xc0006a2c00?, 0xc0012aeeec?}, {0x2?, 0xc0006a2c00?}}})
	github.com/aws/karpenter-core@v0.32.1/pkg/controllers/disruption/controller.go:137 +0x36c
github.com/aws/karpenter-core/pkg/operator/controller.(*Singleton).reconcile(0xc000666b00, {0x308db90, 0xc001042b10})
	github.com/aws/karpenter-core@v0.32.1/pkg/operator/controller/singleton.go:98 +0x31c
github.com/aws/karpenter-core/pkg/operator/controller.(*Singleton).Start(0xc000666b00, {0x308dbc8, 0xc0007bf860})
	github.com/aws/karpenter-core@v0.32.1/pkg/operator/controller/singleton.go:86 +0x1f0
sigs.k8s.io/controller-runtime/pkg/manager.(*runnableGroup).reconcile.func1(0xc000666ce0)
	sigs.k8s.io/controller-runtime@v0.16.3/pkg/manager/runnable_group.go:223 +0xc8
created by sigs.k8s.io/controller-runtime/pkg/manager.(*runnableGroup).reconcile in goroutine 488
	sigs.k8s.io/controller-runtime@v0.16.3/pkg/manager/runnable_group.go:207 +0x19d

This PR is included in version 19.18.0 :tada:

is this the module where the karpenter policy will now be managed and if so does that mean the karpenter-controller policy in iam-role-for-service-accounts-eks is being deprecated ?


Recursive minibuffers invoked from find-file broken?

Call find-file
Press M-x -> Candidate list is not updated?

Works with icomplete, this is a selectrum issue and not an issue with my config or something else.

Yes, it is indeed only find-file.

Another regression because of refactorings I guess :( we should add tests to make such things more unlikely.

I was just about to suggest a test suite. Should also add a very basic one to marginalia consult. Is there a recommended lib for tests?

I think for the interactive test we would like to run here with-simulated-input would be a good candidate. awesome-elisp is a nice resource to find libs/packages for Elisp dev.

Cool! I often find this awesome lists cluttered with everything and only few things are really awesome.

Projectile uses buttercup, https://github.com/bbatsov/projectile/blob/master/test/projectile-test.el

Thanks for finding, fixed by #298. We should probably open another issue for adding a test suite.


misc: add a section to store kernel version information

A section in linker is created to store the kernel version information .This feature is enabled based on CONFIG_VERSION_HEADER. This change make a provision to access the version information from the zephyr elf.
Signed-off-by: Savinay Dharmappa<EMAIL_ADDRESS>

No issue with this, but any particular reasons to add this?

@andrewboie @galak  to detect any changes of symbols names in future Zephyr releases in an debug environment.

@nashif  we already have test tests/kernel/common/src/main.c test_version() wouldn't that be suffice.

recheck

@galak @andyross  version header will be part of both binary and ELF. The idea is to have version_header structure object as part of ELF and binary ,even though this object is not referenced by the code(override linker optimization).  This structure object information can be filled externally as this object is part of special section.

Can anyone help me on why I failed to get the required version in the test case please?

I am having problems running tests/kernel/version_header.
Assertion failed at
./tests/kernel/version_header/src/main.c:20: test_version: (version_header.major == KERNEL_VERSION_MAJOR ) major version mismatch

After I add printk() statement in main.c:
printk("EXPECTED=%d.%d.%d\n", KERNEL_VERSION_MAJOR, KERNEL_VERSION_MINOR, KERNEL_PATCHLEVEL);
printk("GOT     =%d.%d.%d\n", version_header.major, version_header.minor, version_header.patch);

I get
EXPECTED=1.13.99
GOT     =0.0.0

I got it on multiple platforms, e.g. 'altera_max10'.
My .config file has CONFIG_VERSION_HEADER. include/generated/version.h contains the KERNEL_VERSION_XXX information which matches the result.

Given that many people have objections to this patch and the original author is no longer working on Zephyr, I think we should just close this.

@marc-hb maybe you could pick this up in a new PR


Installation failed on Dreamhost VPS, Ubuntu 12.04, gcc 4.6

Sharp could not be installed successfully on my dreamhost VPS. Is there anything wrong with my configuration?
npm i sharp --verbose output is included in
npm-debug.txt file.

Hello, are the prerequisites, especially the C++11 compiler requirements, in place?
http://sharp.dimens.io/en/stable/install/#prerequisites
https://www.dreamhost.com/hosting/vps/ suggests Ubuntu 12.04, which provides gcc v4.6 and therefore doesn't meet the v4.8+ requirement.

Ok, that's true,  I have a version of gcc below 4.8. Is there anything besides updating that I can do? Because updating isn't really an option without root access to the VPS which Dreamhost does not provide.

https://www.dreamhost.com/cloud/ ?


Get Node Info via API

Is there a way to get the node info via API? I would like to get the "docker info" output of individual nodes in the cluster (this is required so that I can read the standard filters and user-defined labels to schedule the containers)? If yes, any pointer is appreciated. If this is an open issue, I am happy to send a PR.
Thanks,
Sriram

I guess, by gathering the label values from engine Info and appending this to the cluster info, we can get this information in "docker info" and via the /info api call. I will send a PR for this.


🐞 Bug:  New Mentor Signups Incorrectly Categorized as Members In Group

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
If the primary mentor adds a new mail address for a mentor and there is no user with that mail address then the user is invited. But when the new user signup then it is added as a member not a mentor which is not expected.
Steps To Reproduce

Log in as the primary mentor and navigate to your group.
Add a new email address for a mentor not associated with any existing account.
The invited user signs up, but the system incorrectly adds them as a member, not a mentor.

Expected Behavior
When that new user signup then it should be added as a mentor only not as a member.
Screenshots
https://github.com/CircuitVerse/CircuitVerse/assets/104610119/b496344f-4e40-4d65-86ee-8a8126fd01c1
Device Information [optional]
- OS:
- Browser:
- version:

Additional context
No response
Are you working on this issue?
Yes

@tanmoysrt @Arnabdaz please take a look at this. I have already started working on this. please assign this to me.

Hi @priyam-03 , I can't reproduce the issue. I have tried in production website + locally with latest codebase

Hi @priyam-03 you can work on the issue


Added login and signup pages

The javascript is not working which is supposed to add animation to the text writer please repair it
#8

ok


Move website mirrors to S3

That is, the mirrors of legislators' websites.

[ ] Have cron/mirror.php query S3, rather than the filesystem, to determine the recency of mirrors for each legislator.
[x] Have cron/mirror.php store its files on S3, rather than the filesystem.

aws s3 sync /vol/www/richmondsunlight.com/html/mirror s3://mirror.richmondsunlight.com --grants read=uri=http://acs.amazonaws.com/groups/global/AllUsers

Just add that to the ricsun crontab.

Done. It runs weekly, on Sundays.

Use aws s3 ls --recursive s3://mirror.richmondsunlight.com to generate a file list, and use that in cron/mirror.php to replace the filesystem-based file list process.

Huh. This is trickier than I had considered. Apache does not, of course, have access to the AWS CLI. So this means either installing the whole PHP SDK for AWS or creating a separate cron job that does nothing but generate this file list as a text file, to then be parsed by mirror.php. (I'm leaning toward the latter.)


Remove JDK-17 specific flag.

Due to Apache Hadoop 3.3 and upper supports Java 8 and Java 11 (runtime only), there is no reason to try to start it with JDK 17.
So we need to remove JDK 17 keys in YARN env file.
--add-opens - does not exits in both 8 and 11 and prevent to start Resource Server.
Resource manager log:
Unrecognized option: --add-opens
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
real-time non-blocking time  (microseconds, -R) unlimited
core file size              (blocks, -c) 0
data seg size               (kbytes, -d) unlimited
scheduling priority                 (-e) 0
file size                   (blocks, -f) unlimited
pending signals                     (-i) 63848
max locked memory           (kbytes, -l) 2047542
max memory size             (kbytes, -m) unlimited
open files                          (-n) 32768
pipe size                (512 bytes, -p) 8
POSIX message queues         (bytes, -q) 819200
real-time priority                  (-r) 0
stack size                  (kbytes, -s) 8192
cpu time                   (seconds, -t) unlimited
max user processes                  (-u) 65536
virtual memory              (kbytes, -v) unlimited
file locks                          (-x) unlimited

Closed for the same reason in #86


[bazel] Tag test_suites to fix --build_tag_filters=-verilator

The test suites are useful for individual invocations like
bazel build //sw/device/tests:aes_entropy_test
When using wildcard invocations, disabling the test suite
by tagging it with manual is effective in preventing invocations
like:
bazel build --build_tag_filters=-verilator //sw/device/tests/...
from building the test_suite which depends on the verilator image.
//sw/device/tests/... includes the verilator tests already so we don't
need the test_suite to make this function properly.
Tested:
bazel build //sw/device/tests:aes_entropy_test
works, just as without the tag
bazel build --build_tag_filters=cw310 //sw/device/tests:aes_entropy_test
doesn't build anything with or without the tag. the test suite doesn't have the cw310 tag and won't match
bazel build --build_tag_filters=cw310 //sw/device/tests/...
builds the cw310 tests without invoking Verilator
Signed-off-by: Drew Macrae<EMAIL_ADDRESS>

What will the following invocation do:
bazel  test --test_tag_filters=verilator //sw/device/tests/...

What will the following invocation do:
bazel  test --test_tag_filters=verilator //sw/device/tests/...

This runs all the Verilator tests only as before. The manual tag is applied only to the otherwise mostly untagabble test_suite, and doesn't propagate to the underlying tests.
Depending on the setting of --build_tests_only this will either build everything for every //sw/device/test/... or not. At present this defaults to --nobuild_tests_only so if you want to restrict the build you must also use --build_tag_filters or set --build_tests_only

--test_tag_filters are propagated to the whole set of tests and will remove unwanted tests from the set if the suite is included.
--build_tag_filters are ignored for dependencies which are built regardless of tags.
I haven't seen this documented anywhere but it's the explanation I have for test_tag_filters working to skip appropriate tests without the manual tag.


[FEAT]: Implemented Logout functionality.

📜 Description
Currently, at '/wallet' route Logout button is not working.
👟 Reproduction steps
Go to the Wallet Page.
Click on the Logout button.
Notice that it is not logging the user out.
Users currently have to go to the root route for logging out.
https://github.com/user-attachments/assets/a9c0927e-fbcf-48f3-8bca-f12373abeade
👍 Expected behavior
When the "Logout" button is clicked it needs to log out the user and redirect to the home page or landing page i.e. '/' .
https://github.com/user-attachments/assets/390b253d-e661-4198-8a49-a5f3d8f99558
👀 Have you spent some time to check if this bug has been raised before?
✅ I checked and didn't find similar issue
🏢 Have you read the Contributing Guidelines?
✅ I have read the Contributing Guidelines

is this issue still open? I would like to work on it.

is this issue still open? I would like to work on it.

I had already pulled request for it and it is still about to be reviewed.

@BearerOP logout works already

@BearerOP logout works already

seems it's not working only for me?

its working check pr #132  its merged

and home page logout also works

do later PRs get reviewed before earlier ones?

its working check pr #132 its merged

@BearerOP sir i have done the logout funtionality of the wallet page and you are doing the home page.It was working fine.Maybe you dont have the latest pull.Which you are solving is already solved 2 months ago.Kindly check it thanks

Okay got it, no worries.


ScopeManager for event-loop based frameworks

Current interface for ScopeManager assumes that there is an implicit link to a certain context working as a storage for active scope/span.
For thread-pool oriented applications the default ThreadLocalScopeManager storing the active scope in a thread local variable is a good fit.
How is it supposed to be implemented for models such as Netty/Vert.x where thread-locals are not an option? Usually such details are stored in some kind of request context, but to my knowledge there is no way in Netty to get a current context without an explicit reference and so it is not clear how to implement the ScopeManager#activeSpan() method assuming there's only one tracer and one scope manager.

I don't know of a good way to do this without having a static reference to the context, likely via a threadlocal.  Ratpack exposes something like this, Maybe you could add similar hooks into netty?

There are two approaches that I've seen for passing context around (my use case is Scala, where a lot of code is written async, and callbacks aren't guaranteed to execute on the same thread):

pass a separate "context" object around everywhere: this is the approach taken by e.g. the AWS Java SDK (at least in version 2). See for example their code to intercept and trace calls to AWS services: the ExecutionAttributes object is essentially a strongly-typed map, and can be used to store / retrieve objects across threads:

makes everything explicit, so client code has control
easier to test / mock
requires adding context object to method signatures everywhere you need it

use some kind of AOP to copy trace data between threads. For example, the Scala kamon library uses aspectj to copy trace context data between threads

much less intrusive, doesn't require changing existing code
can be made to work with third-party libraries
trickier to set up / get working correctly
difficult to test / mock reliably

In short, you're always going to require some way of passing around a reference to the "current" trace. With ThreadLocal that knowledge is implicitly defined by the current thread, but this breaks down in async / event-based code.

much less intrusive, doesn't require changing existing code
can be made to work with third-party libraries
trickier to set up / get working correctly
difficult to test / mock reliably

I like the second approach, the problem with it is that there are libraries, like couchbase client that uses the GlobalTracer to access the active span. Also implementations like Jaeger always builds spans as child of the active span if not explicitly specified not to.
I haven't tested it, but on Spring webflux I think that building a bean with a request scope could work.


update

Hello @EdinsonRequena! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file selenium-course/modulo_II/experimentos/repuestos-test.py:

Line 42:80: E501 line too long (83 > 79 characters)
Line 44:80: E501 line too long (85 > 79 characters)


Update community addressing items in the config.js

App is Moving to Mature Support. No Action Required.


Feature: Card Horizontal Component

Added social user profile horizontal card.

@all-contributors please add @Berrones-Edwin for code


Mock out new design with webflow / Figma

Get a decent idea of the design to be implemented before jumping into developing the new remake

Majority of stuff has been mocked out. Projects page will use a lot of the same components as the project showcase so has not been mocked out. About page will be simple since there is no form integration. Just display feather icons with links. Then follow same design theme as other pages

Majority of stuff has been mocked out. Projects page will use a lot of the same components as the project showcase so has not been mocked out. About page will be simple since there is no form integration. Just display feather icons with links. Then follow same design theme as other pages


Missing ESLint ^8.0.0 Peer Dependancy

When running<EMAIL_ADDRESS>along with<EMAIL_ADDRESS>we get the following error when running npm i
npm ERR! peer<EMAIL_ADDRESS>|| ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0" from<EMAIL_ADDRESS>Any chance that this can be patched?

Having the same issue. Is there a workaround?

@notscottthompson just switch to official solution https://tailwindcss.com/blog/automatic-class-sorting-with-prettier

@notscottthompson There's another, better eslint solution https://www.npmjs.com/package/eslint-plugin-tailwindcss which is maintained and have more features. I guess there's no need for this package.

@Idered thank you!


Getting reports of large Fission Reactors causing massive timings

https://github.com/BevoTechPack/BevoTechPack/issues/963
Please note that server runs on cauldron/thermos, we are testing on plain Forge, results to follow.

I think I might be able to find a way to fix this when I change up the fission reactors for the next version - at the moment, the structure is being checked if it is complete, which is probably what is causing the lag for the bigger sizes.

The latest versions of the mod include attempts to fix this - I will not close this until I know for sure that the problem is gone.
There is also a fission config option to further increase the number of ticks per structure check.

Ohh not sure what's going on I'm testing the update to NuclearCraft-1.7c and wanted to test the new explosion blasts on the fission reactors.  So I took a 3x3x3 and a 5x5x5 and put in MOX239 as fuel, the heat went all the way to the top and no explosion, instead TPS hit the floor, was taking ages to do anything at all even break blocks.  This was a test world with nothing else in it except for the above 2 reactors.  Upon breaking the reactor controller block everything returned to normal.

I already know exactly why that happened - fix should be up in a few minutes :)
By the way, do you notice any tickrate improvements?

I'll let you know after the fix lol :D

It's been approved:
http://minecraft.curseforge.com/projects/nuclearcraft-mod/files/2306715

Already way ahead of you :) tested and working, I swore I heard you say you'd toned the explosions down somewhere lol :p could have fooled me :D

Well, they are still pretty big, but they used to be used to be a little ridiculous - just ask Thorgal :P
I think I may tone them down a bit more though.

Just released another version that makes sure that there is only one explosion (in the case that the controller is not destroyed by the explosion).


add keywords to docs for better search results

Describe the problem
To use @tcc-sejohnson's example: if you search for adapter-static in the docs, the page you're probably looking for — this one — is the fifth result:

Describe the proposed solution
I think the easiest and most reliable solution would be to add keywords frontmatter to the relevant markdown files, so that if you match one of them (or a keyword starts with your search term) that document is treated as higher priority than all others.
We could indicate the keyword in the UI somehow but I don't think it's necessary.
Alternatives considered
No response
Importance
nice to have
Additional Information
No response

3 of the 4 documents that rank above it don't contain adapter-static a single time. It must be tokenizing it into "adapter" and "static". Perhaps we can either remove - as a delimiter character or special case the adapter names to be treated as a single word

I think there's another bug as well:
https://github.com/sveltejs/kit/blob/f953c9d810be8b9211ce1fa456d9c96224ec55dc/sites/kit.svelte.dev/src/lib/search/search.js#L64
The problem is that sub-sections rank lower than main pages.
https://kit.svelte.dev/docs/adapter-static#usage - because it has a # is automatically pushed to the bottom
https://kit.svelte.dev/docs/configuration - despite not even having the text adapter-static jumps to the top because there is no#
It should probably be grouping followed by ranking. I.e. we group by the page and then rank based on the highest ranking sub-section or something like that.

Might it be best to implement 3rd party search? Algolia is free for open-source, and does a great job of indexing and ranking...
https://www.algolia.com/for-open-source/
https://www.algolia.com/doc/tools/crawler/getting-started/overview/

The only bullet point I'd comment on before you write this blog post is:

We don't want to cede control over the UI or the search results. While it's arguably true that Algolia will have better out-of-the-box results than our homegrown setup (which uses flexsearch), we have the ability to improve it and tailor it as we see fit, which we'd lose if we had something generic

Flexsearch is incredibly hard to customize relative to Algolia, Elastic, or just about any index I've used in the past. I've spent the morning trying and simply can't understand how Flexsearch's scoring works. I've filed a few issues in the Flexsearch repo asking for more details and hope to come back to this after getting some more details about how to tweak Flexsearch.
In the meantime, I've sent a PR which just does some housekeeping on our side: https://github.com/sveltejs/kit/pull/8727

Right, but we could swap out flexsearch for something else if we needed to. Hell, we could write our own!

A very well reasoned response. Personally I'd put results relevance above all of those points.
I've had some success in the past with Typesense, IIRC it has a rational approach to ranking and relevance. Might be worth a peek:
https://typesense.org/docs/guide/ranking-and-relevance.html
Flexsearch has a list of other libraries, benchmarked:
https://nextapps-de.github.io/flexsearch/bench/

Typesence looks really cool @oodavid.
Could we try implementing it? I'd like to participate.

Right, but we could swap out flexsearch for something else if we needed to. Hell, we could write our own!

LunrJs is also good and is flexible enough with a good documentation. Other alternatives might be stork.js and fuse.js.

LunrJs is also good and is flexible enough with a good documentation. Other alternatives might be stork.js and fuse.js.

There are a lot of options, we should put our focus on the problem we wanna resolve and look at which one is the best for doing it.
The current problem seems to be the priorities.

I'm open to alternatives as I don't particularly like flexsearch, but it'd be nice to find one that allows us to keep the functionality that we have today. In particular today you can see results as you type and many of the tools mentioned above don't appear to support that. The search we use today also does not require any extra infrastructure. I'm not sure if any of the tools mentioned are great fits, but would love if someone can find one that fits the bill.

typesense - can do prefix-based search. appears to require running search server. is it going to require extra infrastructure or can we run as a serverless funtion on vercel?
lunr - uses bm25. unclear if you can search based off prefix
stork search - has markdown and frontmatter support. appears to index substrings. wasm. isn't on npm. appears to want to manage the DOM, so I don't know if it's compatible with Svelte
fuse.js - has weighted search. unclear if you can search based off prefix

@benmccann I didn't get the "search based off prefix" part can you please explain?(If possible with a small example)

What I mean by search off a prefix is this... Imagine that you're typing "adapter". When you start and you type "a" it will show all words beginning with "a", when you get to "ad" it will show all words starting with "ad", and so on. You can see how the search auto-completes in realtime on kit.svelte.dev as you do this.

What I mean by search off a prefix is this... Imagine that you're typing "adapter". When you start and you type "a" it will show all words beginning with "a", when you get to "ad" it will show all words starting with "ad", and so on. You can see how the search auto-completes in realtime on kit.svelte.dev as you do this.

Correct me if I am wrong but are you perhaps talking about auto-complete?
Would this be something we are looking for?
Autocomplete library by Algolia

It's a bit different than autocomplete. It's not completing your queries. Rather it's doing searches based on partial query strings. E.g. to take the "adapter" example from earlier, the way it works is by indexing "a", "ad", "ada", "adap", "adapt", "adapte", "adapter". This takes a lot more memory, but provides the experience you see today on kit.svelte.dev.

It's a bit different than autocomplete. It's not completing your queries. Rather it's doing searches based on partial query strings. E.g. to take the "adapter" example from earlier, the way it works is by indexing "a", "ad", "ada", "adap", "adapt", "adapte", "adapter". This takes a lot more memory, but provides the experience you see today on kit.svelte.dev.

I see then perhaps is this what we are looking for,
Wildcards Lunrjs

Ah, yes! Thanks for the pointer. Lunrjs may indeed work then!
I'd be happy to review any attempt to switch out flexsearch for lunrjs if anyone wants to take a stab at it.

Ah, yes! Thanks for the pointer. Lunrjs may indeed work then!
I'd be happy to review any attempt to switch out flexsearch for lunrjs if anyone wants to take a stab at it.

I can try to make a prototype. Can you guide me through some of the steps to setup the code for docs locally?

Can anyone guide me through some of the steps to setup the code for docs locally?

You'll need to have pnpm installed, then...
git clone git@github.com:sveltejs/kit
cd kit
pnpm install
cd sites/kit.svelte.dev
pnpm dev

...and you should be off to the races!

One thing I'll note is that the web worker that powers our current search — which includes all of flexsearch plus our logic that sits around it — is 18kb of unminified code (though it probably should be minified, not sure why it isn't).
By contrast, lunr by itself weighs 99kb. Probably not a dealbreaker but something to be conscious of.

I suspect you want to keep the search locally on the client, but if you're looking for an alternative to algolia there's meilisearch: https://docs.meilisearch.com - though 11kb minified+zipped

lunr is only 29k minified, so it's not too bad. The thing that I just noticed that gives me more hesitation is that it appears to basically be abandoned. It hasn't been updated since 2020, it still uses Travis CI, there's a number of unreviewed PRs, etc. It'd be nice if we could find something that's a bit better maintained

https://github.com/lucaong/minisearch looks like a promising option. It'd probably be better to try it than lunr

https://github.com/lucaong/minisearch looks like a promising option. It'd probably be better to try it than lunr

Thanks for you suggestion, I will try to use this.

I was trying out minisearch and elasticlunr yesterday, @Hetarth02 you can continue from those branches if it saves you some setup time.
You'll need to be using Chrome for this btw since Firefox doesn't yet support module workers.

@gtm-nayan Thanks for your help, by the way any noticeable results you got from uaing minisearch. Also, if you want we can co-ordinate with each other and work on this topic together.

Minisearch gives out a lot more results than our current setup, and even when searching for exact phrases like "Netlify Forms" but I think that's due to the combineWith setting. Minisearch did improve the query originally mentioned in this issue ie. searching for adapter-static leads to the static site generation page, and I didn't see any glaring problems yet but still have to test for other common queries.

There's an up-and-coming in-memory search engine fully build from the ground up to be performant for full-text search, called Lyra. The project seems quite intuitive and the people behind it are constantly improving it. It might be worth giving it a shot for the docs 🤔

Here's a playground of sorts for lyra, now called orama, https://stackblitz.com/edit/stackblitz-starters-eraanr?file=index.mjs
run node index.mjs "query goes here"
would be great if folks could help with the evaluation, i.e. compare the results it gives against the current setup on kit.svelte.dev and share the findings here

Here's a playground of sorts for lyra, now called orama, https://stackblitz.com/edit/stackblitz-starters-eraanr?file=index.mjs

Amazing! Thank you @gtm-nayan!

I just tried it out:
node index.mjs "ssr"
In the current docs the first result is /docs/page-options#ssr which doesn't seem to be included here in the search results.

Hmm. That's funny. I just tried the command you shared and that page was the second result. Perhaps @gtm-nayan made some improvements
I also tested against the string "adapter-static", which was the original one filed here and it returned the "Static Site Generation" section first as expected.
One that could be better is "assets". I was hoping to see the asset handling page returned higher. Turning on stemming helped quite a bit and boosting the breadcrumbs helped some as well as shown below. I think we may be able to do still better by splitting the breadcrumb into fields like h1, h2, h3, so that we can give a higher boost to larger headings. Right now we can't do that which makes it really hard to get the asset handling page back first since other chunks have the term "assets" in their lower headings.
  const index = await create({
    schema: {
      breadcrumbs: 'string[]',
      content: 'string',
    },
    components: {
      tokenizer: { language: 'english', stemming: true },
    },
  });

  await insertMultiple(index, blocks);

  const results = await search(index, {
    term: query,
    boost: {
      breadcrumbs: 2,
    },
  });

Orama is vastly better than fastsearch from an API perspective. I love how easy it is to boost a field, which I couldn't figure out with flexsearch if I recall.
Another thing I noticed is that we may want to do something to put the migration guide and possibly the types towards the end of the search results. I know we at least discussed that with the current doc search, but can't remember if we implemented it or not.
A small thing I noticed independent of which library we use is that we divide most of the articles into very small chunks, but then leave the config page as a single chunk. That could be worth tweaking.
Finally, something I just noticed in their docs is that they have a grouping functionality. I know we do some grouping on the results after they're returned, so it might be interesting to see if this feature would be useful to us: https://docs.oramasearch.com/usage/search/grouping
Overall, I'd love to switch to Orama. It seems way easier to use, so if we need to make any tweaks I'm a lot more confident we'll be able to do that. Also, my questions in the flexsearch repo have gone unanswered and flexsearch has no commits this year whereas orama seems much more actively developed.

I'm a bit skeptical about Orama based on this https://github.com/oramasearch/orama/issues/76#issuecomment-1352410224
Unless this has been resolved somehow?

That doesn't seems like a deal breaker to me. While it'd nice if it would take into account whether words are found consecutively, I'm not sure how often that would result in different search rankings and there are other ways in which Orama's search is better. I would expect that being able to have the scoring take into account whether a term is found in the first heading, second heading, or content would have a larger effect on search quality and Orama beats flexsearch there.
I actually think the most interesting part of that post is that it lists several other options that I'm not sure we've investigated yet. The ones it lists as potentially performing better than Orama in that one particular benchmark (which is not terribly representative of actual usage) are bulksearch, jsii, wade, and js-search, so it might be worth checking those out as well.

Size would be a factor as well, the current search implementation on the kit site, including flexsearch and the components is about 24kB minified, just the playground I linked above is about 55.7 kB after minification.

jsii says it's not maintained
js-search can't do per-field boosting
wade doesn't appear to do stemming, substring matching, or per-field boosting
bulksearch doesn't appear to do stemming or per-field boosting
I still think Orama is going to give us the best results. Especially since the test in https://github.com/oramasearch/orama/issues/76#issuecomment-1352410224 is so unlike our usecase. It was searching over all of HarryPotter so there's going to be tons more matches for any query and it doesn't have headings that can be used for per-field boosting
Orama is larger. Though it also uses a lot less memory. I don't think we're likely to find a single library that wins across all metrics.

I filed an issue with a suggestion for making Orama a bit smaller: https://github.com/oramasearch/orama/issues/418
I think we could also mitigate it on our end by loading the search functionality in onMount so that we don't block the page load

a bit late to the party, but i'll drop this here:
https://github.com/leeoniya/uFuzzy#a-biased-appraisal-of-similar-work
i'd be interested in benchmarking Orama vs Lyra. lyra didn't come out very fast in my tests, though they're biased towards partial substring matches. Flexsearch is for sure the performance king if you can spare the ram for a giant index.

Sharing an update here from https://github.com/oramasearch/orama/issues/418:

We just published Orama v1.0.7 and went from 20kb to 13kb gziped. If you import the search function only, it will cost around 4.88kb gziped (it was around 11kb yesterday)

@gtm-nayan your stackblitz isn't working for me anymore. Is there a way to go back to a working version of it?

Whoops, forgot to revert the changes after checking the bundle size. Fixed now.

https://github.com/sveltejs/site-kit/pull/162


Review the currently distinct implementations of Loading/Saving a program vs. Reading/Writing a data file

The background to this ticket is #836, in which JS points out that the behaviour of the file-selection dialog for reading/writing data files is different from the behavioir of the same dialog for loading/saving code files.
The implementations are in fact quite different. So the first question is:

Are these so different because there is a fundamental need for them to be different, or are they just different because they were developed many months apart and the second one required investigating more options.

Put another way, is there a case for bringing these implementations together into common code.  If so can we retain the behaviour (of the current program Load/Save) in terms of retaining the directory last used as the default.

Minor changes just discussed:

Get rid of the first dialog - the one that just asks for a file name - because (at least if you are in Chrome) my understanding is that you will now always get the browser-managed file selector dialog anyway.

When the Auto Save button is pressed, set a flag somewhere that is translated into that button being disabled, and the tooltip message changing from the explanation of what button does to 'Auto-save is already activated - will save whenever code parses.' (There is already standard code somewhere managing the changing tooltip on enabled/disabled buttons).

Leave the UNSAVED message as is


feat(dbm-services): add new switch strategy by uptime for all Redis storage

关联研发信息
dev_branch: feat/dbha-for-uptime/#6760
target_branch: v1.5.0


small fixes

Pull Request Test Coverage Report for Build 82

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 58.466%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

astetik/style/template.py
0
1
0.0%

Totals

Change from base Build 81:
0.0%

Covered Lines:
663

Relevant Lines:
1134

💛  - Coveralls

Pull Request Test Coverage Report for Build 82

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 58.466%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

astetik/style/template.py
0
1
0.0%

Totals

Change from base Build 81:
0.0%

Covered Lines:
663

Relevant Lines:
1134

💛  - Coveralls


Fixes #52 The User ID (Subject) is not parsed from the JWT Token

It is trivial to add tests for this in jwt_test.go. However, I was not able to figure out how to modify and sign the JWT tokens that are included in that test. If you let me know how to do that then I can submit some basic tests for this code.

We should probably close this PR in favour of what's been discussed in #52.

Hi @crhym3, I'm trying to understand your comment.
Also could you please sign the CLA? https://cla.developers.google.com/


OCPBUGS-14383: disable autoscaler when no nodepool requires it

Creates a new DisableClusterAutoscalerAnnotation set on the HostedControlPlane by the hypershift-operator when none of the NodePools for a particular HostedCluster have spec.autoScaling set.  When this annotation is set on the HCP, the CPO sets replicas on the cluster-autoscaler Deployment to 0.

/lgtm

Thanks, this is good behavioural fix! fwiw instead of adding a new annotation we could let isAutoscalingNeeded to set hcp.spec.autoscaling or not, and let that be what dictates the deployment.spec.replicas. Might not be trivial since hcp.spec.autoscaling is not a pointer. I'm fine with the annotation too.

/retest

/retest

/test e2e-aws

/test e2e-aws

/test e2e-aws

/test e2e-aws

/test e2e-aws

/test e2e-aws

/override ci/prow/e2e-aws

/cherry-pick release-4.15


chore(deps): upgrade bazel-integration-testing to rules_bazel_integration_test

Deleting is better 🤷 👍
Was this created from a template?


chore(docs): remove references to npm packages

This PR removes references to installing @aztec/aztec-sandbox and @aztec/cli via NPM in favor of installing via Docker. It also updates notes about types imports for the token contract contract tutorial and the token reference in the "writing a dapp" tutorial.
Note: recent additions broke the Quickstart guide. The docs got out of sync with the latest version because docs are always tested against master. This should be fixed with the new release going out tomorrow morning, so I'm not bothering to change it now, but we should test the Quickstart page again once the new release goes out.
closes #3540 #3541
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to relevant issues (if any exist).

Benchmark results
Metrics with a significant change:

note_history_successful_decrypting_time_in_ms (5): 2,500 (+16%)
note_history_successful_decrypting_time_in_ms (10): 5,107 (+23%)
note_history_trial_decrypting_time_in_ms (5): 78.4 (-51%)
note_history_trial_decrypting_time_in_ms (10): 203 (-42%)
note_trial_decrypting_time_in_ms (8): 45.7 (+128%)
note_trial_decrypting_time_in_ms (128): 136 (-31%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 0888c050 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,444
179,588
716,132

l1_rollup_calldata_gas
222,948
867,776
3,449,624

l1_rollup_execution_gas
842,035
3,594,884
22,204,993

l2_block_processing_time_in_ms
2,195
8,412
35,033 (-1%)

note_successful_decrypting_time_in_ms
337 (+9%)
1,028 (+13%)
3,830 (+14%)

note_trial_decrypting_time_in_ms
:warning: 45.7 (+128%)
36.2 (-3%)
:warning: 136 (-31%)

l2_block_building_time_in_ms
20,090
79,935
320,830 (-1%)

l2_block_rollup_simulation_time_in_ms
16,574
66,061
265,201

l2_block_public_tx_process_time_in_ms
3,486
13,804
55,395 (-1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
24,462 (-1%)
47,241

note_history_successful_decrypting_time_in_ms
:warning: 2,500 (+16%)
:warning: 5,107 (+23%)

note_history_trial_decrypting_time_in_ms
:warning: 78.4 (-51%)
:warning: 203 (-42%)

node_database_size_in_bytes
3,630,009
3,925,768

pxe_database_size_in_bytes
29,940 (+1%)
59,499

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
199
43,109
20,441

private-kernel-ordering
114
25,833
9,689

base-rollup
2,957
667,692
873

root-rollup
86.7 (+1%)
4,072
881

private-kernel-inner
260
64,516
20,441

public-kernel-private-input
171
25,203
20,441

public-kernel-non-first-iteration
168
25,245
20,441

merge-rollup
10.8
2,592
873

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
10,323
25,938


Identifiers validation failed for dataset Inventario de Hymenóptera; parasítica en México

Identifier validation failed for the dataset Inventario de Hymenóptera; parasítica en México:

Crawler attempt: 324
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 10879
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 10879 total records; 10879 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3740462/step

New IDs sample:

Old IDs sample:

1c8e43eb13f2423fcaa2678c63f6c971
b913907d6479344d09edfad66244a83f
f5f3822ed3b57fde6885000a3ec1ef4e
423f882301a73ccf7c667e264488a737
5ee48e2445255b71da4afc0ee623afbd
d93bdd77ad75dc36ec9060f41bfc817e
f16c34564f3fad7d8da3ab6324aee0fd
191e8f844855a2a3dd7ca8a2ca36e54e
3a1d87e80bc0f2a2325149cdd16dadac
4948d67a928bd39029fbc12813ac3645

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Inventario de Hymenóptera; parasítica en México : https://doi.org/10.15468/wazk7g.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Inventario de Hymenóptera; parasítica en México:

Crawler attempt: 326
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 10879
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 10879 total records; 10879 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3741866/step

New IDs sample:

Old IDs sample:

1c8e43eb13f2423fcaa2678c63f6c971
b913907d6479344d09edfad66244a83f
f5f3822ed3b57fde6885000a3ec1ef4e
423f882301a73ccf7c667e264488a737
5ee48e2445255b71da4afc0ee623afbd
d93bdd77ad75dc36ec9060f41bfc817e
f16c34564f3fad7d8da3ab6324aee0fd
191e8f844855a2a3dd7ca8a2ca36e54e
3a1d87e80bc0f2a2325149cdd16dadac
4948d67a928bd39029fbc12813ac3645

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Inventario de Hymenóptera; parasítica en México : https://doi.org/10.15468/wazk7g.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.


Unable to create a post model

Hey Ryan,
I tried installing this package into a fresh Laravel 10 install and following your README, however when i try and save a Post model using ::create or ->save();. a file is not created in the content folder and i get a 404.
Ive created an example repo here: https://github.com/jamesdordoy/orbit and tested it on another machine to make sure its still an issue.

Hey, can you try adding $table->id() to the schema and see if that fixes the issue.

Yep perfect mate 👍
Cheers!


Restrict Enabled Checks

Disabled attribute only applies to a handful of elements, we shouldn't be checking for it before clicks for all elements...
https://www.w3.org/TR/2014/REC-html5-20141028/disabled-elements.html

Actually we aren't (any more?) so this issue doesn't apply


Be careful you have to compile sass files again

https://github.com/ankythshukla/underexpress/blob/da45aca09cc595dac4a40ada3fe1cc0de8938a69/assets/css/styles.css#L11
The file 'style.css' is wrong and remove all the overflow, not only horizontal ;-)
You only have to compile sass files again before use assets and all will be good!

https://github.com/ankythshukla/underexpress/blob/da45aca09cc595dac4a40ada3fe1cc0de8938a69/assets/css/styles.css#L11
The file 'style.css' is wrong and remove all the overflow, not only horizontal ;-)
You only have to compile sass files again before use assets and all will be good!

good job dude! youre a life saver!


Add ARIA attributes - Checkbox

Describe the bug
Currently, the Checkbox component doesn't have the ARIA attributes, this will have NextUI more accessible to people with disabilities.
Expected behaviour
Add Aria Attributes to components
Additional info
References:
ARIA-Moz
ARIA-Google
Chrome extension

Yeah for sure! thank you @arthur322


WIP: lilic/add webserver

What: Parsing /mountinfo from different mount namespaces and representing the information as a graph using D3.
Current status: It takes user input and in a new page displays generated tree using d3.
Would love to get suggestions how to handle errors better, as well as overall feedback and any other suggestions always welcome.

Note that FE part is still WIP and some commits are for Heroku deployment.

@krnowak thanks, I addressed your comments, although it seems github does not collapse them anymore even if they are outdated...


When I enter an address for the BBMD, the service fails to start.

Here is a snippet of the logs:  I have tried with a bbmd address like x.x.x.x and x.x.x.x/y
[11:18:01] INFO: Running interface
ERROR:    An error occurred:
Traceback (most recent call last):
File "/usr/bin/main.py", line 261, in
asyncio.run(main())
File "/usr/local/lib/python3.12/asyncio/runners.py", line 194, in run
return runner.run(main)
^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/asyncio/runners.py", line 118, in run
return self._loop.run_until_complete(task)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 664, in run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File "/usr/bin/main.py", line 188, in main
app = BACnetIOHandler(
^^^^^^^^^^^^^^^^
File "/usr/bin/BACnetIOHandler.py", line 41, in init
self.register(addr=Address(foreign_ip), ttl=ttl)
File "/usr/local/lib/python3.12/site-packages/bacpypes3/ipv4/app.py", line 180, in register
self.foreign.register(addr, ttl)
File "/usr/local/lib/python3.12/site-packages/bacpypes3/ipv4/service.py", line 668, in register
if ttl <= 0:
^^^^^^^^
TypeError: '<=' not supported between instances of 'str' and 'int'

Could you try again with the development version?
Please uninstall and check for updates first if you were already using the development version.
I see that ttl wasn't being interpreted as integer so I just pushed a fix for that.

Seems to have corrected the issue.  Thanks, Merry Christmas!

Great, glad to hear! I'll push an update to the regular version sometime next year. Merry (belated) Christmas to you as well.

Pushed to the regular version with 1.3.0.