text:
No ValidSAMrecords when using step4 optionA

Hi,
Thanks for developing this very useful and much needed tool!
I am running step4 option A and it seems like it cannot identify any valid SAMrecords in my file.
The command I am running is
java -jar -Xmx300g Sicelore-2.1.220323.jar IsoformMatrix I=step3output.bam GENETAG=GE UMITAG=U8 CELLTAG=BC REFFLAT=gencode.vM31.refFlat CSV=BarcodesAssigned.tsv DELTA=2 MAXCLIP=150 METHOD=STRICT AMBIGUOUS_ASSIGN=false OUTDIR=/output/ PREFIX=sicelore ISOBAM=TRUE
The output I get is
[Sat Jan 27 17:33:55 CST 2024] Executing as yuanwsy@mgt on Linux 3.10.0-1160.76.1.el7.x86_64 amd64; Java HotSpot(TM) 64-Bit Server VM 17.0.9+11-LTS-201; Deflater: Intel; Inflater: Intel; Provider GCS is not available; Picard version: null
INFO    2024-01-27 17:33:55     IsoformMatrix           Cells detected          [17538]
INFO    2024-01-27 17:33:55     LongreadParser          start...
INFO    2024-01-27 17:34:14     LongreadParser          Processed            1,000,000 Records.  Elapsed time: 00:00:18s.  Time for last 1,000,000:   18s.  Last read position: 1:24,652,271
INFO    2024-01-27 17:34:27     LongreadParser          Processed            2,000,000 Records.  Elapsed time: 00:00:31s.  Time for last 1,000,000:   13s.  Last read position: 1:33,535,346
INFO    2024-01-27 17:34:43     LongreadParser          Processed            3,000,000 Records.  Elapsed time: 00:00:47s.  Time for last 1,000,000:   16s.  Last read position: 1:60,940,022
INFO    2024-01-27 17:35:00     LongreadParser          Processed            4,000,000 Records.  Elapsed time: 00:01:04s.  Time for last 1,000,000:   16s.  Last read position: 1:86,456,892
INFO    2024-01-27 17:35:16     LongreadParser          Processed            5,000,000 Records.  Elapsed time: 00:01:20s.  Time for last 1,000,000:   16s.  Last read position: 1:127,966,314
INFO    2024-01-27 17:35:33     LongreadParser          Processed            6,000,000 Records.  Elapsed time: 00:01:37s.  Time for last 1,000,000:   16s.  Last read position: 1:156,193,610
INFO    2024-01-27 17:35:50     LongreadParser          Processed            7,000,000 Records.  Elapsed time: 00:01:54s.  Time for last 1,000,000:   17s.  Last read position: 1:177,016,694
INFO    2024-01-27 17:36:06     LongreadParser          Processed            8,000,000 Records.  Elapsed time: 00:02:10s.  Time for last 1,000,000:   15s.  Last read position: 2:12,413,864
INFO    2024-01-27 17:36:18     LongreadParser          Processed            9,000,000 Records.  Elapsed time: 00:02:22s.  Time for last 1,000,000:   12s.  Last read position: 2:26,133,461
INFO    2024-01-27 17:36:35     LongreadParser          Processed           10,000,000 Records.  Elapsed time: 00:02:39s.  Time for last 1,000,000:   16s.  Last read position: 2:38,451,760
INFO    2024-01-27 17:36:51     LongreadParser          Processed           11,000,000 Records.  Elapsed time: 00:02:55s.  Time for last 1,000,000:   16s.  Last read position: 2:69,579,379
INFO    2024-01-27 17:37:08     LongreadParser          Processed           12,000,000 Records.  Elapsed time: 00:03:12s.  Time for last 1,000,000:   16s.  Last read position: 2:102,666,440
INFO    2024-01-27 17:37:24     LongreadParser          Processed           13,000,000 Records.  Elapsed time: 00:03:28s.  Time for last 1,000,000:   15s.  Last read position: 2:122,050,391
INFO    2024-01-27 17:37:40     LongreadParser          Processed           14,000,000 Records.  Elapsed time: 00:03:44s.  Time for last 1,000,000:   15s.  Last read position: 2:152,027,164
INFO    2024-01-27 17:37:56     LongreadParser          Processed           15,000,000 Records.  Elapsed time: 00:04:00s.  Time for last 1,000,000:   16s.  Last read position: 2:165,707,190
INFO    2024-01-27 17:38:10     LongreadParser          Processed           16,000,000 Records.  Elapsed time: 00:04:14s.  Time for last 1,000,000:   14s.  Last read position: 2:179,899,211
INFO    2024-01-27 17:38:27     LongreadParser          Processed           17,000,000 Records.  Elapsed time: 00:04:31s.  Time for last 1,000,000:   16s.  Last read position: 3:45,333,034
INFO    2024-01-27 17:38:44     LongreadParser          Processed           18,000,000 Records.  Elapsed time: 00:04:48s.  Time for last 1,000,000:   16s.  Last read position: 3:76,187,099
INFO    2024-01-27 17:39:01     LongreadParser          Processed           19,000,000 Records.  Elapsed time: 00:05:05s.  Time for last 1,000,000:   17s.  Last read position: 3:90,141,919
INFO    2024-01-27 17:39:17     LongreadParser          Processed           20,000,000 Records.  Elapsed time: 00:05:21s.  Time for last 1,000,000:   16s.  Last read position: 3:90,599,939
INFO    2024-01-27 17:39:34     LongreadParser          Processed           21,000,000 Records.  Elapsed time: 00:05:38s.  Time for last 1,000,000:   17s.  Last read position: 3:102,961,027
INFO    2024-01-27 17:39:51     LongreadParser          Processed           22,000,000 Records.  Elapsed time: 00:05:55s.  Time for last 1,000,000:   16s.  Last read position: 3:130,520,484
INFO    2024-01-27 17:40:07     LongreadParser          Processed           23,000,000 Records.  Elapsed time: 00:06:11s.  Time for last 1,000,000:   16s.  Last read position: 4:3,973,093
INFO    2024-01-27 17:40:23     LongreadParser          Processed           24,000,000 Records.  Elapsed time: 00:06:27s.  Time for last 1,000,000:   15s.  Last read position: 4:40,775,089
INFO    2024-01-27 17:40:40     LongreadParser          Processed           25,000,000 Records.  Elapsed time: 00:06:44s.  Time for last 1,000,000:   17s.  Last read position: 4:73,215,481
INFO    2024-01-27 17:40:56     LongreadParser          Processed           26,000,000 Records.  Elapsed time: 00:07:00s.  Time for last 1,000,000:   16s.  Last read position: 4:111,288,219
INFO    2024-01-27 17:41:13     LongreadParser          Processed           27,000,000 Records.  Elapsed time: 00:07:17s.  Time for last 1,000,000:   17s.  Last read position: 4:129,718,904
INFO    2024-01-27 17:41:29     LongreadParser          Processed           28,000,000 Records.  Elapsed time: 00:07:33s.  Time for last 1,000,000:   15s.  Last read position: 4:138,153,051
INFO    2024-01-27 17:41:43     LongreadParser          Processed           29,000,000 Records.  Elapsed time: 00:07:47s.  Time for last 1,000,000:   13s.  Last read position: 4:150,399,531
INFO    2024-01-27 17:41:59     LongreadParser          Processed           30,000,000 Records.  Elapsed time: 00:08:03s.  Time for last 1,000,000:   16s.  Last read position: 5:20,341,036
INFO    2024-01-27 17:42:15     LongreadParser          Processed           31,000,000 Records.  Elapsed time: 00:08:19s.  Time for last 1,000,000:   16s.  Last read position: 5:43,937,095
INFO    2024-01-27 17:42:33     LongreadParser          Processed           32,000,000 Records.  Elapsed time: 00:08:37s.  Time for last 1,000,000:   17s.  Last read position: 5:86,876,908
INFO    2024-01-27 17:42:50     LongreadParser          Processed           33,000,000 Records.  Elapsed time: 00:08:54s.  Time for last 1,000,000:   17s.  Last read position: 5:108,612,445
INFO    2024-01-27 17:43:05     LongreadParser          Processed           34,000,000 Records.  Elapsed time: 00:09:09s.  Time for last 1,000,000:   15s.  Last read position: 5:123,368,694
INFO    2024-01-27 17:43:21     LongreadParser          Processed           35,000,000 Records.  Elapsed time: 00:09:25s.  Time for last 1,000,000:   15s.  Last read position: 5:137,585,391
INFO    2024-01-27 17:43:39     LongreadParser          Processed           36,000,000 Records.  Elapsed time: 00:09:43s.  Time for last 1,000,000:   17s.  Last read position: 6:3,200,912
INFO    2024-01-27 17:43:55     LongreadParser          Processed           37,000,000 Records.  Elapsed time: 00:09:59s.  Time for last 1,000,000:   15s.  Last read position: 6:37,783,257
INFO    2024-01-27 17:44:10     LongreadParser          Processed           38,000,000 Records.  Elapsed time: 00:10:14s.  Time for last 1,000,000:   14s.  Last read position: 6:56,282,657
INFO    2024-01-27 17:44:25     LongreadParser          Processed           39,000,000 Records.  Elapsed time: 00:10:29s.  Time for last 1,000,000:   15s.  Last read position: 6:75,273,056
INFO    2024-01-27 17:44:41     LongreadParser          Processed           40,000,000 Records.  Elapsed time: 00:10:45s.  Time for last 1,000,000:   16s.  Last read position: 6:99,854,572
INFO    2024-01-27 17:44:58     LongreadParser          Processed           41,000,000 Records.  Elapsed time: 00:11:02s.  Time for last 1,000,000:   17s.  Last read position: 6:122,434,065
INFO    2024-01-27 17:45:14     LongreadParser          Processed           42,000,000 Records.  Elapsed time: 00:11:18s.  Time for last 1,000,000:   15s.  Last read position: 6:145,940,712
INFO    2024-01-27 17:45:30     LongreadParser          Processed           43,000,000 Records.  Elapsed time: 00:11:34s.  Time for last 1,000,000:   15s.  Last read position: 7:16,453,039
INFO    2024-01-27 17:45:46     LongreadParser          Processed           44,000,000 Records.  Elapsed time: 00:11:50s.  Time for last 1,000,000:   16s.  Last read position: 7:28,955,766
INFO    2024-01-27 17:46:03     LongreadParser          Processed           45,000,000 Records.  Elapsed time: 00:12:07s.  Time for last 1,000,000:   16s.  Last read position: 7:45,368,676
INFO    2024-01-27 17:46:18     LongreadParser          Processed           46,000,000 Records.  Elapsed time: 00:12:22s.  Time for last 1,000,000:   15s.  Last read position: 7:80,992,479
INFO    2024-01-27 17:46:35     LongreadParser          Processed           47,000,000 Records.  Elapsed time: 00:12:39s.  Time for last 1,000,000:   17s.  Last read position: 7:100,803,813
INFO    2024-01-27 17:46:53     LongreadParser          Processed           48,000,000 Records.  Elapsed time: 00:12:57s.  Time for last 1,000,000:   18s.  Last read position: 7:103,475,739
INFO    2024-01-27 17:47:12     LongreadParser          Processed           49,000,000 Records.  Elapsed time: 00:13:16s.  Time for last 1,000,000:   19s.  Last read position: 7:103,475,742
INFO    2024-01-27 17:47:31     LongreadParser          Processed           50,000,000 Records.  Elapsed time: 00:13:35s.  Time for last 1,000,000:   18s.  Last read position: 7:115,817,593
INFO    2024-01-27 17:47:47     LongreadParser          Processed           51,000,000 Records.  Elapsed time: 00:13:51s.  Time for last 1,000,000:   15s.  Last read position: 7:132,372,597
INFO    2024-01-27 17:48:02     LongreadParser          Processed           52,000,000 Records.  Elapsed time: 00:14:06s.  Time for last 1,000,000:   15s.  Last read position: 8:11,733,394
INFO    2024-01-27 17:48:17     LongreadParser          Processed           53,000,000 Records.  Elapsed time: 00:14:21s.  Time for last 1,000,000:   14s.  Last read position: 8:34,578,113
INFO    2024-01-27 17:48:33     LongreadParser          Processed           54,000,000 Records.  Elapsed time: 00:14:37s.  Time for last 1,000,000:   16s.  Last read position: 8:71,348,023
INFO    2024-01-27 17:48:50     LongreadParser          Processed           55,000,000 Records.  Elapsed time: 00:14:54s.  Time for last 1,000,000:   16s.  Last read position: 8:94,949,578
INFO    2024-01-27 17:49:06     LongreadParser          Processed           56,000,000 Records.  Elapsed time: 00:15:10s.  Time for last 1,000,000:   16s.  Last read position: 8:117,228,920
INFO    2024-01-27 17:49:22     LongreadParser          Processed           57,000,000 Records.  Elapsed time: 00:15:26s.  Time for last 1,000,000:   15s.  Last read position: 9:8,092,011
INFO    2024-01-27 17:49:36     LongreadParser          Processed           58,000,000 Records.  Elapsed time: 00:15:40s.  Time for last 1,000,000:   14s.  Last read position: 9:31,846,577
INFO    2024-01-27 17:49:53     LongreadParser          Processed           59,000,000 Records.  Elapsed time: 00:15:57s.  Time for last 1,000,000:   16s.  Last read position: 9:50,255,506
INFO    2024-01-27 17:50:10     LongreadParser          Processed           60,000,000 Records.  Elapsed time: 00:16:14s.  Time for last 1,000,000:   17s.  Last read position: 9:67,669,149
INFO    2024-01-27 17:50:27     LongreadParser          Processed           61,000,000 Records.  Elapsed time: 00:16:31s.  Time for last 1,000,000:   16s.  Last read position: 9:86,647,982
INFO    2024-01-27 17:50:44     LongreadParser          Processed           62,000,000 Records.  Elapsed time: 00:16:48s.  Time for last 1,000,000:   16s.  Last read position: 9:108,443,064
INFO    2024-01-27 17:51:02     LongreadParser          Processed           63,000,000 Records.  Elapsed time: 00:17:06s.  Time for last 1,000,000:   18s.  Last read position: 9:120,784,602
INFO    2024-01-27 17:51:18     LongreadParser          Processed           64,000,000 Records.  Elapsed time: 00:17:22s.  Time for last 1,000,000:   16s.  Last read position: 10:23,661,104
INFO    2024-01-27 17:51:33     LongreadParser          Processed           65,000,000 Records.  Elapsed time: 00:17:37s.  Time for last 1,000,000:   14s.  Last read position: 10:56,230,727
INFO    2024-01-27 17:51:50     LongreadParser          Processed           66,000,000 Records.  Elapsed time: 00:17:54s.  Time for last 1,000,000:   16s.  Last read position: 10:80,128,301
INFO    2024-01-27 17:52:07     LongreadParser          Processed           67,000,000 Records.  Elapsed time: 00:18:11s.  Time for last 1,000,000:   17s.  Last read position: 10:111,331,205
INFO    2024-01-27 17:52:24     LongreadParser          Processed           68,000,000 Records.  Elapsed time: 00:18:28s.  Time for last 1,000,000:   17s.  Last read position: 10:128,383,986
INFO    2024-01-27 17:52:39     LongreadParser          Processed           69,000,000 Records.  Elapsed time: 00:18:43s.  Time for last 1,000,000:   15s.  Last read position: 11:12,598,058
INFO    2024-01-27 17:52:56     LongreadParser          Processed           70,000,000 Records.  Elapsed time: 00:19:00s.  Time for last 1,000,000:   16s.  Last read position: 11:32,234,099
INFO    2024-01-27 17:53:11     LongreadParser          Processed           71,000,000 Records.  Elapsed time: 00:19:15s.  Time for last 1,000,000:   15s.  Last read position: 11:44,895,851
INFO    2024-01-27 17:53:28     LongreadParser          Processed           72,000,000 Records.  Elapsed time: 00:19:32s.  Time for last 1,000,000:   16s.  Last read position: 11:61,701,401
INFO    2024-01-27 17:53:46     LongreadParser          Processed           73,000,000 Records.  Elapsed time: 00:19:50s.  Time for last 1,000,000:   17s.  Last read position: 11:76,956,479
INFO    2024-01-27 17:54:02     LongreadParser          Processed           74,000,000 Records.  Elapsed time: 00:20:06s.  Time for last 1,000,000:   16s.  Last read position: 11:88,600,029
INFO    2024-01-27 17:54:19     LongreadParser          Processed           75,000,000 Records.  Elapsed time: 00:20:23s.  Time for last 1,000,000:   16s.  Last read position: 11:101,179,091
INFO    2024-01-27 17:54:37     LongreadParser          Processed           76,000,000 Records.  Elapsed time: 00:20:41s.  Time for last 1,000,000:   18s.  Last read position: 11:117,311,468
INFO    2024-01-27 17:54:53     LongreadParser          Processed           77,000,000 Records.  Elapsed time: 00:20:57s.  Time for last 1,000,000:   15s.  Last read position: 12:25,143,934
INFO    2024-01-27 17:55:09     LongreadParser          Processed           78,000,000 Records.  Elapsed time: 00:21:13s.  Time for last 1,000,000:   16s.  Last read position: 12:67,557,494
INFO    2024-01-27 17:55:26     LongreadParser          Processed           79,000,000 Records.  Elapsed time: 00:21:30s.  Time for last 1,000,000:   16s.  Last read position: 12:86,003,345
INFO    2024-01-27 17:55:41     LongreadParser          Processed           80,000,000 Records.  Elapsed time: 00:21:45s.  Time for last 1,000,000:   14s.  Last read position: 12:110,282,577
INFO    2024-01-27 17:55:58     LongreadParser          Processed           81,000,000 Records.  Elapsed time: 00:22:02s.  Time for last 1,000,000:   16s.  Last read position: 13:20,639,115
INFO    2024-01-27 17:56:13     LongreadParser          Processed           82,000,000 Records.  Elapsed time: 00:22:17s.  Time for last 1,000,000:   14s.  Last read position: 13:45,023,266
INFO    2024-01-27 17:56:29     LongreadParser          Processed           83,000,000 Records.  Elapsed time: 00:22:33s.  Time for last 1,000,000:   16s.  Last read position: 13:72,602,772
INFO    2024-01-27 17:56:43     LongreadParser          Processed           84,000,000 Records.  Elapsed time: 00:22:47s.  Time for last 1,000,000:   14s.  Last read position: 13:96,797,616
INFO    2024-01-27 17:56:58     LongreadParser          Processed           85,000,000 Records.  Elapsed time: 00:23:02s.  Time for last 1,000,000:   14s.  Last read position: 13:111,729,792
INFO    2024-01-27 17:57:13     LongreadParser          Processed           86,000,000 Records.  Elapsed time: 00:23:17s.  Time for last 1,000,000:   15s.  Last read position: 14:20,744,282
INFO    2024-01-27 17:57:30     LongreadParser          Processed           87,000,000 Records.  Elapsed time: 00:23:34s.  Time for last 1,000,000:   17s.  Last read position: 14:47,946,264
INFO    2024-01-27 17:57:46     LongreadParser          Processed           88,000,000 Records.  Elapsed time: 00:23:50s.  Time for last 1,000,000:   15s.  Last read position: 14:67,611,263
INFO    2024-01-27 17:58:02     LongreadParser          Processed           89,000,000 Records.  Elapsed time: 00:24:06s.  Time for last 1,000,000:   15s.  Last read position: 14:103,392,703
INFO    2024-01-27 17:58:17     LongreadParser          Processed           90,000,000 Records.  Elapsed time: 00:24:21s.  Time for last 1,000,000:   15s.  Last read position: 15:12,575,570
INFO    2024-01-27 17:58:33     LongreadParser          Processed           91,000,000 Records.  Elapsed time: 00:24:37s.  Time for last 1,000,000:   16s.  Last read position: 15:59,257,164
INFO    2024-01-27 17:58:51     LongreadParser          Processed           92,000,000 Records.  Elapsed time: 00:24:55s.  Time for last 1,000,000:   17s.  Last read position: 15:81,749,522
INFO    2024-01-27 17:59:06     LongreadParser          Processed           93,000,000 Records.  Elapsed time: 00:25:10s.  Time for last 1,000,000:   15s.  Last read position: 15:99,604,370
INFO    2024-01-27 17:59:23     LongreadParser          Processed           94,000,000 Records.  Elapsed time: 00:25:27s.  Time for last 1,000,000:   17s.  Last read position: 16:20,350,329
INFO    2024-01-27 17:59:39     LongreadParser          Processed           95,000,000 Records.  Elapsed time: 00:25:43s.  Time for last 1,000,000:   16s.  Last read position: 16:40,694,040
INFO    2024-01-27 17:59:56     LongreadParser          Processed           96,000,000 Records.  Elapsed time: 00:26:00s.  Time for last 1,000,000:   16s.  Last read position: 16:84,624,762
INFO    2024-01-27 18:00:12     LongreadParser          Processed           97,000,000 Records.  Elapsed time: 00:26:16s.  Time for last 1,000,000:   16s.  Last read position: 17:10,428,380
INFO    2024-01-27 18:00:29     LongreadParser          Processed           98,000,000 Records.  Elapsed time: 00:26:33s.  Time for last 1,000,000:   16s.  Last read position: 17:29,319,160
INFO    2024-01-27 18:00:44     LongreadParser          Processed           99,000,000 Records.  Elapsed time: 00:26:48s.  Time for last 1,000,000:   15s.  Last read position: 17:36,184,656
INFO    2024-01-27 18:01:02     LongreadParser          Processed          100,000,000 Records.  Elapsed time: 00:27:06s.  Time for last 1,000,000:   17s.  Last read position: 17:46,811,539
INFO    2024-01-27 18:01:18     LongreadParser          Processed          101,000,000 Records.  Elapsed time: 00:27:22s.  Time for last 1,000,000:   16s.  Last read position: 17:75,852,344
INFO    2024-01-27 18:01:35     LongreadParser          Processed          102,000,000 Records.  Elapsed time: 00:27:39s.  Time for last 1,000,000:   16s.  Last read position: 18:8,417,302
INFO    2024-01-27 18:01:50     LongreadParser          Processed          103,000,000 Records.  Elapsed time: 00:27:54s.  Time for last 1,000,000:   15s.  Last read position: 18:36,711,738
INFO    2024-01-27 18:02:08     LongreadParser          Processed          104,000,000 Records.  Elapsed time: 00:28:12s.  Time for last 1,000,000:   17s.  Last read position: 18:63,676,490
INFO    2024-01-27 18:02:26     LongreadParser          Processed          105,000,000 Records.  Elapsed time: 00:28:30s.  Time for last 1,000,000:   17s.  Last read position: 19:5,486,519
INFO    2024-01-27 18:02:43     LongreadParser          Processed          106,000,000 Records.  Elapsed time: 00:28:47s.  Time for last 1,000,000:   17s.  Last read position: 19:5,884,666
INFO    2024-01-27 18:03:00     LongreadParser          Processed          107,000,000 Records.  Elapsed time: 00:29:04s.  Time for last 1,000,000:   16s.  Last read position: 19:22,371,224
INFO    2024-01-27 18:03:15     LongreadParser          Processed          108,000,000 Records.  Elapsed time: 00:29:19s.  Time for last 1,000,000:   15s.  Last read position: 19:40,941,576
INFO    2024-01-27 18:03:31     LongreadParser          Processed          109,000,000 Records.  Elapsed time: 00:29:35s.  Time for last 1,000,000:   16s.  Last read position: X:8,008,602
INFO    2024-01-27 18:03:46     LongreadParser          Processed          110,000,000 Records.  Elapsed time: 00:29:50s.  Time for last 1,000,000:   14s.  Last read position: X:51,861,166
INFO    2024-01-27 18:04:00     LongreadParser          Processed          111,000,000 Records.  Elapsed time: 00:30:04s.  Time for last 1,000,000:   13s.  Last read position: X:79,501,653
INFO    2024-01-27 18:04:15     LongreadParser          Processed          112,000,000 Records.  Elapsed time: 00:30:19s.  Time for last 1,000,000:   15s.  Last read position: X:135,172,245
INFO    2024-01-27 18:04:30     LongreadParser          Processed          113,000,000 Records.  Elapsed time: 00:30:34s.  Time for last 1,000,000:   15s.  Last read position: X:165,990,089
INFO    2024-01-27 18:04:48     LongreadParser          Processed          114,000,000 Records.  Elapsed time: 00:30:52s.  Time for last 1,000,000:   17s.  Last read position: MT:2,751
INFO    2024-01-27 18:05:04     LongreadParser          Processed          115,000,000 Records.  Elapsed time: 00:31:08s.  Time for last 1,000,000:   15s.  Last read position: MT:7,765
INFO    2024-01-27 18:05:18     LongreadParser          Processed          116,000,000 Records.  Elapsed time: 00:31:22s.  Time for last 1,000,000:   14s.  Last read position: MT:14,145
INFO    2024-01-27 18:05:25     LongreadParser          end...
INFO    2024-01-27 18:05:25     LongreadParser          Total SAMrecords        116447499
INFO    2024-01-27 18:05:25     LongreadParser          SAMrecords valid        0
INFO    2024-01-27 18:05:25     LongreadParser          SAMrecords unvalid      116447499
INFO    2024-01-27 18:05:25     LongreadParser          SAMrecords mapqv=0      0
INFO    2024-01-27 18:05:25     LongreadParser          SAMrecords no gene      107358445
INFO    2024-01-27 18:05:25     LongreadParser          SAMrecords no UMI       0
INFO    2024-01-27 18:05:25     LongreadParser          SAMrecords chimeria     9089054
INFO    2024-01-27 18:05:25     LongreadParser          Total reads             0
INFO    2024-01-27 18:05:25     LongreadParser          Total reads multiSAM    0
INFO    2024-01-27 18:05:25     MoleculeDataset         MoleculeDataset init start...
INFO    2024-01-27 18:05:25     MoleculeDataset         Total molecules         0
INFO    2024-01-27 18:05:25     MoleculeDataset         Total molecule reads    0
INFO    2024-01-27 18:05:25     MoleculeDataset         Total molecule multiIG  0
INFO    2024-01-27 18:05:25     UCSCRefFlatParser       UCSCRefFlatParser       start...
INFO    2024-01-27 18:05:26     UCSCRefFlatParser       UCSCRefFlatParser       end...
INFO    2024-01-27 18:05:26     UCSCRefFlatParser       Number of Genes Symbols [56775]
INFO    2024-01-27 18:05:26     UCSCRefFlatParser       Number of Transcripts   [149423]
INFO    2024-01-27 18:05:26     MoleculeDataset         SetIsoforms             start...
INFO    2024-01-27 18:05:26     MoleculeDataset         SetIsoforms             end...
INFO    2024-01-27 18:05:26     MoleculeDataset         SetIsoforms             monoexon        [0]
INFO    2024-01-27 18:05:26     MoleculeDataset         SetIsoforms             no match        [0]
INFO    2024-01-27 18:05:26     MoleculeDataset         SetIsoforms             one match       [0]
INFO    2024-01-27 18:05:26     MoleculeDataset         SetIsoforms             ambiguous       [0]
INFO    2024-01-27 18:05:26     MoleculeDataset         DTEMatrix               start...[56775] genes
INFO    2024-01-27 18:05:26     MoleculeDataset         DTEMatrix               [10000/56775] genes processed
INFO    2024-01-27 18:05:26     MoleculeDataset         DTEMatrix               [20000/56775] genes processed
INFO    2024-01-27 18:05:26     MoleculeDataset         DTEMatrix               [30000/56775] genes processed
INFO    2024-01-27 18:05:26     MoleculeDataset         DTEMatrix               [40000/56775] genes processed
INFO    2024-01-27 18:05:26     MoleculeDataset         DTEMatrix               [50000/56775] genes processed
INFO    2024-01-27 18:05:26     MoleculeDataset         DTEMatrix               [56775/56775] genes processed
INFO    2024-01-27 18:05:26     IsoformMatrix           writeIsoformMatrix      [start]
INFO    2024-01-27 18:05:26     IsoformMatrix           writeGeneMatrix         [start]
INFO    2024-01-27 18:05:26     IsoformMatrix           writeCellMetrics        [start]
INFO    2024-01-27 18:05:26     IsoformMatrix           writeJunctionMatrix     [start]
INFO    2024-01-27 18:05:26     IsoformMatrix           Matrix cells size       [17538]
INFO    2024-01-27 18:05:26     IsoformMatrix           Matrix genes size       [0]
INFO    2024-01-27 18:05:26     IsoformMatrix           Matrix junctions size   [0]
INFO    2024-01-27 18:05:26     IsoformMatrix           Matrix isoforms size    [0]
INFO    2024-01-27 18:05:26     IsoformMatrix           Matrix isoforms counts  [0]
INFO    2024-01-27 18:05:26     IsoformMatrix           Matrix isoforms define  [0]
INFO    2024-01-27 18:05:26     IsoformMatrix           Matrix isoforms undefine[0]
INFO    2024-01-27 18:05:27     IsoformMatrix           Producing ISOBAM        [true]
......
Can you please let me know what might be causing this issue and how tofix this ?Thanks!

Hi,
it seems the pipeline does not found any SAM records having a GENETAG:
INFO 2024-01-27 18:05:25 LongreadParser SAMrecords unvalid 116447499
INFO 2024-01-27 18:05:25 LongreadParser SAMrecords no gene 107358445
Are you sure that you add a GENETAG SAM record tag (GE) into your bam file before counting ?
best,
kevin

yeah,in the step3 the command I used is
java -jar -Xmx300g "NanoporeBC_UMI_finder-2.1.jar" assignumis --inFileNanopore "passed.bam" --outfile "step3out.bam" -a "/reference/gencode.vM31.annotation.gtf"
also I have ever tried used refflat instead of gtf,I think I tried to add a GENETAG SAM record tag (GE) into my bam file,
but one line of my bam looks like this ,
32d85a79-2d0c-499c-9173-d0d330386df4_REV_PS=258_PE=289_AE=313_T=39_bc=AGTGTTGAGAGCACTG_ed=0_ed_sec=2147483647_bcStart=312_bcEnd=297_rk=0_X=AAAAAAAAAAAAAAGCAGAGGCTCCAGTGCTCTCAACACTAGA_Q=20.4_kjqey     16      1       3278713 60      100S220M40S *0       0^C     TGTTATGCGTTCAGTTACGTATTGCTCTACACGACGCTCTTCCGATCTAGTGTTGAGAGCACTGGAGCCTCTGCTTTTTTTTTTTTTTTTTTTTTTTTTTTTTGTACTGATATACATTTACATAGTTTCCTCATACCTGTAGCTGTGTGCCAAGTACTTAGTGGCAGGGTTACAGGTAAGTTCTATAAAAGTTTATATTTCTTTACCATTTTAATGTAGAATTAAGTATATATTGAAGTAAGAAAAATGTCAGTCTTCGTGAGTCGAAATGATTTAGAAATAAAGCCTAGGAACCAGTTAAGCAGCTTAGAACCCACTGTCCCATGTACTCTGCGTTGATACCACTGCAGCAATACGTAG     $$%&&&&$##$+05442/---.222576564311///01377300//03355100/.010444634333456666447137:<=>ABHGGFFF{{{{{{IGG@70///01221134466676211114574421111466654566888887665444445566677665556445411112////054443344433345784--...137:9876532222444443333344555222248::;987777787741111142----/5444456777676656766654434554322346799765434457:::6665566545558:70000/01112788877777644..+&  B1:i:0  s1:i:198        B2:Z:2147483647 s2:i:0  U7:Z:GAGCCTCTGCTT       U8:Z:GAGCCTCTGCTT       BB:Z:312        BC:Z:AGTGTTGAGAGCACTG   AE:i:313        BE:Z:297        PE:i:289        RE:Z:   TE:i:39 BF:Z:297        XF:Z:INTERGENIC BH:Z:0       NM:i:2  AS:i:214        PS:i:258        BU:Z:AGTGTTGAGAGCACTG   BV:Z:312        BW:i:0  BX:Z:N.A.       SX:Z:34513018   BZ:Z:AGTGTTGAGAGCACTG   UZ:Z:   de:f:0.0091     rl:i:34 cm:i:30 nn:i:0  tp:A:P  ms:i:214        ts:A:+
it seems no GE ,right?

Hi, it seems the pipeline does not found any SAM records having a GENETAG: INFO 2024-01-27 18:05:25 LongreadParser SAMrecords unvalid 116447499 INFO 2024-01-27 18:05:25 LongreadParser SAMrecords no gene 107358445
Are you sure that you add a GENETAG SAM record tag (GE) into your bam file before counting ?
best, kevin

NanoporeBC_UMI_finder.jar should add the GE tags using standard config file. Did you take a look to your bam file in IGV, is there a lot of reads aligning to genes ?? You can check in IGV if there is the gene tag which is mandatory for counting.

NanoporeBC_UMI_finder.jar should add the GE tags using standard config file. Did you take a look to your bam file in IGV, is there a lot of reads aligning to genes ?? You can check in IGV if there is the gene tag which is mandatory for counting.

I check in IGV,there actually is a lot of reads aligning to genes,so it is confused why NanoporeBC_UMI_finder.jar have not add the GE tags

When using NanoporeBC_UMI_finder.jar, do the reads in the bam file have a GE tag ??
If not you should check the chromosome names 'chr' in the refflat file
as describe in the README : "refFlat file for gene assignment. If supplied will generate a cell/gene umi count table and add the GE tag to SAM record. Uses the “TagReadWithGeneExonFunction” from the DropSeq package. Not required if the GE tag was added to BAM records with the Sicelore package."
You can also add the GE tag using the sicelore package AddGeneNameTag pipeline.
Is there a problem in the strandind of the reads (i.e. opposite strand issue?)
All the different steps should very straightforward in fact.
best,

yeah,there is no GE tag in the bam file I used.
and I followed the tutorial like this to generate the refflat file :
gtfToGenePred -genePredExt -geneNameAsName2 gencode.v38.primary_assembly.annotation.gtf gencode.v38.primary_assembly.annotation.refflat.txt
paste <(cut -f 12 gencode.v38.primary_assembly.annotation.refflat.txt) <(cut -f 1-10 gencode.v38.primary_assembly.annotation.refflat.txt) > gencode.v38.refFlat
and the GTF file I use is gencode.vM34.primary_assembly.annotation.gtf
the first line of the refflat I generated  look like this:
4933401J01Rik	ENSMUST00000193812.2	chr1	+	3143475	3144545	3144545	3144545	1	3143475,	3144545,
and I also try to add the GE tag using the sicelore package AddGeneNameTag pipeline:
INFO    2024-02-15 16:41:39     AddGeneNameTag
********** NOTE: Picard's command line syntax is changing.

********** For more information, please see:
********** https://github.com/broadinstitute/picard/wiki/Command-Line-Syntax-Transition-For-Users-(Pre-Transition)

********** The command line looks like this in the new syntax:

**********    AddGeneNameTag -I /data/R02/yuanwsy/sicelore-2.1/OEpassed2.bam -O OEpassed.GE.bam -REFFLAT /data/R02/yuanwsy/reference/gencode.vM34.refFlat -GENETAG GE

[Thu Feb 15 16:41:41 CST 2024] AddGeneNameTag INPUT=/data/R02/yuanwsy/sicelore-2.1/OEpassed2.bam OUTPUT=OEpassed.GE.bam REFFLAT=/data/R02/yuanwsy/reference/gencode.vM34.refFlat GENETAG=GE    STRANDTAG=GS FUNCTIONTAG=XF USE_STRAND_INFO=true ALLOW_MULTI_GENE_READS=true VERBOSITY=INFO QUIET=false VALIDATION_STRINGENCY=STRICT COMPRESSION_LEVEL=5 MAX_RECORDS_IN_RAM=500000 CREATE_INDEX=false CREATE_MD5_FILE=false GA4GH_CLIENT_SECRETS=client_secrets.json USE_JDK_DEFLATER=false USE_JDK_INFLATER=false
[Thu Feb 15 16:41:41 CST 2024] Executing as yuanwsy@mgt on Linux 3.10.0-1160.76.1.el7.x86_64 amd64; Java HotSpot(TM) 64-Bit Server VM 17.0.9+11-LTS-201; Deflater: Intel; Inflater: Intel; Provider GCS is not available; Picard version: null
{BUFFER_SIZE=131072, COMPRESSION_LEVEL=5, CREATE_INDEX=false, CREATE_MD5=false, CUSTOM_READER_FACTORY=https://www.googleapis.com/genomics,com.google.cloud.genomics.gatk.htsjdk.GA4GHReaderFactory, DISABLE_SNAPPY_COMPRESSOR=false, EBI_REFERENCE_SERVICE_URL_MASK=https://www.ebi.ac.uk/ena/cram/md5/%s, NON_ZERO_BUFFER_SIZE=131072, REFERENCE_FASTA=null, SAM_FLAG_FIELD_FORMAT=DECIMAL, USE_ASYNC_IO_READ_FOR_SAMTOOLS=false, USE_ASYNC_IO_WRITE_FOR_SAMTOOLS=false, USE_ASYNC_IO_WRITE_FOR_TRIBBLE=false, USE_CRAM_REF_DOWNLOAD=false}
INFO    2024-02-15 16:41:42     AddGeneNameTag  Loaded 54 transcripts.
INFO    2024-02-15 16:42:49     AddGeneNameTag          Processed            1,000,000 Records.  Elapsed time: 00:01:09s.  Time for last 1,000,000:   66s.  Last read position: 1:24,652,268
INFO    2024-02-15 16:43:41     AddGeneNameTag          Processed            2,000,000 Records.  Elapsed time: 00:02:02s.  Time for last 1,000,000:   52s.  Last read position: 1:24,653,961
INFO    2024-02-15 16:44:38     AddGeneNameTag          Processed            3,000,000 Records.  Elapsed time: 00:02:58s.  Time for last 1,000,000:   56s.  Last read position: 1:52,497,007
INFO    2024-02-15 16:45:40     AddGeneNameTag          Processed            4,000,000 Records.  Elapsed time: 00:04:00s.  Time for last 1,000,000:   61s.  Last read position: 1:66,987,669
INFO    2024-02-15 16:46:34     AddGeneNameTag          Processed            5,000,000 Records.  Elapsed time: 00:04:55s.  Time for last 1,000,000:   54s.  Last read position: 1:87,008,004
INFO    2024-02-15 16:47:43     AddGeneNameTag          Processed            6,000,000 Records.  Elapsed time: 00:06:03s.  Time for last 1,000,000:   68s.  Last read position: 1:128,198,125
INFO    2024-02-15 16:48:49     AddGeneNameTag          Processed            7,000,000 Records.  Elapsed time: 00:07:10s.  Time for last 1,000,000:   66s.  Last read position: 1:153,784,205
......
INFO    2024-02-15 19:04:41     AddGeneNameTag  TOTAL READS [136661160] CORRECT_STRAND [136658628]  WRONG_STRAND [2532] AMBIGUOUS_STRAND_FIXED [115] AMBIGUOUS REJECTED READS [0]
[Thu Feb 15 19:04:41 CST 2024] org.ipmc.sicelore.programs.AddGeneNameTag done. Elapsed time: 143.01 minutes.
after that ,I checked the taged bam file ,and still not found GE tag:
d5a1855c-9535-4963-acbc-119dbdb4ee01_REV_PS=326_PE=359_AE=381_T=41_bc=TGAGTCAGTCGAACAG_ed=0_ed_sec=2147483647_bcStart=380_bcEnd=365_rk=0_X=AAAAAAAAAAAAGAATAAAGCTCACTGTTCGACTGACTCAAGA_Q=18.2_6ck1d     0       1       3050531 2       42S176M1D65M3D15M137S       *       0       0       CTATGTATTGCTAAGCAGTGGTATCAACGCAGAGTACATGGGCAACATTATGAACTAGCCAGTACCCTGGAGCTCTTGACTCTAGCTGCATATGTATCAAAAGATGGCCTAGCTGGCCATCACTGGAAAGAGAGGCCCATTGGACATGCAAACTTTATATGCCCCAGTACAGGGGAATGCCAGGGCCAAAAAGTGGGAGTGGGTGGGTAGGGGAGTGTGGGGAGGGTATGGGGGACTTTTGGGATAGCACTGGAAATGTAAATGAGGGAAATACCTAATAAAATATAAAAAATAAAAATAAATAAAATGAATCACAACATATGCCAAAAAAAAAAAAAAAAAAAAAAAAAAAGAATAAAGCTCACTGTTCGACTGACTCAAGATCGGAAGAGCGTCGTGTAGAGCAATACGTAACTGAACGAAGTACATACATAA %'++334444456776640////.-...264211012347433321001122011224411111456655443322233444455420000/....0464455443222357455223225667654444443321123244445666553431///0134454////06884221135696753344434475523233555+.--.9<84423368;8884/---.6995444567522000113344573333343544343665432111124579422249=>;999<@><<;8999;;665211012332112012249;@BEFHHGDCCCCABA@=;976465521211211122221-,,--2332223444/-,,+-.6.,,++-..0330001031000012345.---,,*))%$$$$%%$$$#     s1:i:49 s2:i:0  XF:Z:INTERGENIC NM:i:24 AS:i:188        de:f:0.0853     rl:i:255        cm:i:5  nn:i:0      tp:A:P  ms:i:189        ts:A:+
what's wrong with this?
thanks a lot！

i can see "XF:Z:INTERGENIC" in your samrecords so it seems to work (this is a flag integrated by  AddGeneNameTag).
There is no GE tag because the samrecord isn't in a gene region, please look into a gene region, you should have a GE tag.
you can do 'samtools view OEpassed.GE.bam | grep GE"

I have tried grep GE and grep GE:
but still no GE tag
the first command I grep lots of intergenic region ,the second I grep alot like this:
a4ae63f4-263b-46da-9ffd-23b796eb748f_FWD_PS=512_PE=531_AE=557_X=AAAAAAAAAAAAACACCTACTCGCCTGGGCAACCATAGTCAGA_Q=22.7_svi5 16      137448683 60      62S183M2I294M50S        *       0       0       CTACGTATTGCTCTACACTGACGCTCTTCCGATCTGACTATGGTTGCCCAGGCGAGTAGGTGTTTTTTTTTTTTTTTTTTGGCTCCTTTTAGAAACAGGTAACAGCTTGGATCTGGGACATTTGAGGCTTAAGCAGGACCAGTCTTGGCAAGAGTCAGGGAGGGTGCAGGCATCCCTCTCCATAAGTGCAGACAGCCTCCTGTCTCCCCTGCCTGCTGGGAGGAAGATGTGCTCTGCTAAGGGGTGGGGTGTGGCTCACTGCCCCACCCTCTAGGCAGGGCTGTGGAAGGTGAGAGCCAGGAAGCTCTCTTCCCCTAACCCTCCTCCCAGGCCTGCTCTGCTGGTATCAGATTGGCCCGAAGCCCCAGGCCTGATCAAAGATGGCTGAGTCTCAGTGTGGCTGGTTGAGCCTTTTAACTCTTGGTTGGTTCATTTACTCTTAGTCTTTTGTTTTTTGTTTGTTTGGTTTTGCTCATTTTGACATCACTGCCTTTTAGAAATATTTCTTCAGGTTTTAGAATTAAATGTTTCCCATGTACTCTGCGTTGATACCACTGCTTAGCAATACGTAACTGAACGAGTAAACAGTAA   '())//(('''&)((()))+,0-++'&&&&++()''&&&&&001000018?BCCHHH{{{{GE:;565432223334532222321112343330/...1..110111123420/./025843222444333222225444334/6651100---.---.122221..--.0266333335533332223344333447777843432330000025344422)))/6*)))*)5334433100114575434333111139787544444343243324355666343321011124020////.24447888966665755566763----.12111460....232445766440////)),113345443..-----12244553111114322210//0123333344433344211111---,-01364458:9989:322224224;;654335589433223233223234433434221212222323333444332234454221110/01001114-,+++/100011244322123443.,+++,0224/..((('&$$%$%%$### s1:i:439        s2:i:0  XF:Z:INTERGENIC NM:i:5  AS:i:464  de:f:0.0084     rl:i:30 cm:i:77 nn:i:0  tp:A:P  ms:i:464        ts:A:+
the GE above is GE:;565432223334532222321112343330/...1..11011112342
found no GE tag

might be the difference in chromosome name format between refflat and you ref. used for alignment, i can see there is the 'chr' in chromosome name in the refflat but not in the bam file. It need to be coherent between both.

but I used the GRCm39.genome.fa.gz as the genome reference for alignment and gencode.vM34.primary_assembly.annotation.gtf as the annotation reference , it is coherent

authors: cobioda yuanwsy


text:
Data preprocessing

Hi,
Could you please provide the command you used to generate the parses to use as input, as well as any other preprocessing steps required? I have some data that I would like to test your system on, how should I generate an input file in the correct format?
Thanks!

Thanks!

source: gharchive/issue

repo: uclanlp/synpg

license: MIT

license_type: permissive

license_source: github-api


text:
register package

hi

@JuliaRegistrator register

Error while trying to register: Changing UUIDs is not allowed

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/15111
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.5 -m "<description of version>" 24a895d78889e71bd566f93d1835e34bb4e2c9c8
git push origin v0.1.5

Also, note the warning: This looks like a new registration that registers version 0.1.5.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/15113
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.0 -m "<description of version>" 6c29161a2dba186a97bbdb0e8ad45484362a2e27
git push origin v0.2.0

Also, note the warning: This looks like a new registration that registers version 0.2.0.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

linking @gaelforget

authors: JuliaRegistrator gaelforget udistr


text:
Trouble with JWT Config (No secret key configured for JWT)

I'm trying to setup Guardian to work with Phoenix and Ldap. I seem to be stuck with some configuration. My Guardian config looks roughly like this:
config :guardian, Guardian,
  allowed_algos: ["HS512"],
  verify_module: Guardian.JWT,
  issuer: "Issuer",
  ttl: { 30, :days},
  verify_issuer: true,
  secret_key: <MY KEY>,
  serializer: MyApp.Auth.GuardianSerializer

I have a SessionController where I'm hitting Ldap and then doing something like this:
    case Ldap.authenticate(username, password) do
      :ok -> handle_sign_in(conn, username)
      _   -> handle_error(conn)
    end

    {:ok, user} = lookup_user(username)
    conn
    |> put_flash(:info, "Logged in.")
    |> MyApp.Auth.Guardian.Plug.sign_in(user)
    |> redirect(to: "/")

The Ldap portion is working fine, but I keep getting this error from Guardian:
Request: POST /sign_in
** (exit) an exception was raised:
    ** (RuntimeError) No secret key configured for JWT
        (guardian) lib/guardian/token/jwt.ex:319: Guardian.Token.Jwt.fetch_secret/2
        (guardian) lib/guardian/token/jwt.ex:163: Guardian.Token.Jwt.create_token/3
        (guardian) lib/guardian.ex:754: Guardian.returning_tuple/1
        (guardian) lib/guardian.ex:581: Guardian.encode_and_sign/4
        (guardian) lib/guardian/plug.ex:172: Guardian.Plug.sign_in/5
        (infrared) lib/myapp_web/controllers/session_controller.ex:23: MyAppWeb.SessionController.handle_sign_in/2
        (infrared) lib/myapp_web/controllers/session_controller.ex:1: MyAppWeb.SessionController.action/2
        (infrared) lib/myapp_web/controllers/session_controller.ex:1: MyAppWeb.SessionController.phoenix_controller_pipeline/2
        (infrared) lib/myapp_web/endpoint.ex:1: MyAppWeb.Endpoint.instrument/4
        (phoenix) lib/phoenix/router.ex:278: Phoenix.Router.__call__/1
        (infrared) lib/myapp_web/endpoint.ex:1: MyAppWeb.Endpoint.plug_builder_call/2
        (infrared) lib/plug/debugger.ex:99: MyAppWeb.Endpoint."call (overridable 3)"/2
        (infrared) lib/myapp_web/endpoint.ex:1: MyAppWeb.Endpoint.call/2
        (plug) lib/plug/adapters/cowboy/handler.ex:15: Plug.Adapters.Cowboy.Handler.upgrade/4

I can't tell if this is a config issue on my side or a bug. Any help would be much appreciated.

Sorry for the report. This was a config issue on my end. I had my otp_app set to something different that what was in my config file.

repo: ueberauth/guardian

license: mit

license_source: bigquery


text:
Add Dogma and TravisCI

RFC @hassox / @scrogson — Like the other PRs this adds Dogma and TravisCI to the example project.

Do we want to add a TravisCI badge to the README?

source: gharchive/pull-request


text:
構造体の型を使い回すようにする

たとえばSnapshotService.goで定義されているCreateSnapshotResponseなんですが
type CreateSnapshotResponse struct {
	JobID        string `json:"jobid,omitempty"`
	Account      string `json:"account,omitempty"`
	Created      string `json:"created,omitempty"`
	Domain       string `json:"domain,omitempty"`
	Domainid     string `json:"domainid,omitempty"`
	Id           string `json:"id,omitempty"`
	Intervaltype string `json:"intervaltype,omitempty"`
	Name         string `json:"name,omitempty"`
	Physicalsize int64  `json:"physicalsize,omitempty"`
	Project      string `json:"project,omitempty"`
	Projectid    string `json:"projectid,omitempty"`
	Revertable   bool   `json:"revertable,omitempty"`
	Snapshottype string `json:"snapshottype,omitempty"`
	State        string `json:"state,omitempty"`
	Tags         []struct {
		Account      string `json:"account,omitempty"`
		Customer     string `json:"customer,omitempty"`
		Domain       string `json:"domain,omitempty"`
		Domainid     string `json:"domainid,omitempty"`
		Key          string `json:"key,omitempty"`
		Project      string `json:"project,omitempty"`
		Projectid    string `json:"projectid,omitempty"`
		Resourceid   string `json:"resourceid,omitempty"`
		Resourcetype string `json:"resourcetype,omitempty"`
		Value        string `json:"value,omitempty"`
	} `json:"tags,omitempty"`
	Volumeid   string `json:"volumeid,omitempty"`
	Volumename string `json:"volumename,omitempty"`
	Volumetype string `json:"volumetype,omitempty"`
	Zoneid     string `json:"zoneid,omitempty"`
}

これはTagsService.goで定義されたTag型を用いて
type CreateSnapshotResponse struct {
	JobID        string `json:"jobid,omitempty"`
	Account      string `json:"account,omitempty"`
	Created      string `json:"created,omitempty"`
	Domain       string `json:"domain,omitempty"`
	Domainid     string `json:"domainid,omitempty"`
	Id           string `json:"id,omitempty"`
	Intervaltype string `json:"intervaltype,omitempty"`
	Name         string `json:"name,omitempty"`
	Physicalsize int64  `json:"physicalsize,omitempty"`
	Project      string `json:"project,omitempty"`
	Projectid    string `json:"projectid,omitempty"`
	Revertable   bool   `json:"revertable,omitempty"`
	Snapshottype string `json:"snapshottype,omitempty"`
	State        string `json:"state,omitempty"`
	Tags         []Tag `json:"tags,omitempty"`
	Volumeid   string `json:"volumeid,omitempty"`
	Volumename string `json:"volumename,omitempty"`
	Volumetype string `json:"volumetype,omitempty"`
	Zoneid     string `json:"zoneid,omitempty"`
}

このように書き換えることが可能かと思います。
現在あらゆる構造体中のTagsフィールドはTag型ではない（型が定義されていない）ので、たとえばCreateSnapshotResponseやDeployValueVirtualMachineResponseのTagsを引数にとるような関数が作れません。
Tags以外にもEgressrule、Securitygroup、Nic（Networknameのフィールドを持つものとそうでないものがある）なども型で定義して、それを使い回すとよいと思います

@sugiura120 下記のstructを使いまわすようにします

[ ] Tag
[ ] Egressrule
[ ] Securitygroup
[ ] Nic

https://github.com/uesyn/gokcps/pull/11

https://github.com/uesyn/gokcps/issues/3

repo: uesyn/gokcps


text:
Configuration: cycle detection

Implement a 1.5 phase in configuration handling: sort objects between parsing and building, detect cycles in this phase.

jak to vypadá? chystáš se k tomu?

chystám

Pořád se chystáš?

authors: jindrahelcl jlibovicky tomasmcz

repo: ufal/neuralmonkey


text:
Fixed pyunitwizard init file

Fixed init.py in _pyunitwizard
Status

[ ] Ready to go

Codecov Report

Merging #42 (80aae7b) into main (f72f266) will not change coverage.
The diff coverage is 0.00%.

authors: Daniel-Ibarrola codecov-commenter

repo: uibcdf/openpharmacophore


text:
Included License Metadata for setuptools

This allows larger software projects to recognize (with automated software) that they are allowed to use this package.
It would be very nice, if you could tag again, so that we can retrieve the updated pip package soon.
Would help us a lot for our project! Thank you for Open Sourcing :)

Thank you for the improvements!
I'll update the version on pypi right away.

authors: FloWag uijl

repo: uijl/pandablob


text:
🛑 DigitalPartners is down

In fb3c77d, DigitalPartners (https://digitalpartners.ai) was down:

HTTP code: 502
Response time: 293 ms

Resolved: DigitalPartners is back up in 35a25b7.

repo: ulisesthecras/upptime


text:
Tweak conversion mechanics to be more explicit and safe.

Make the decimals field on Currency required and change its description to include more details about its use.
Change the multiplier field from i64 to f64 to allow for very small unit currencies. See https://github.com/uma-universal-money-address/protocol/blob/main/umad-04-lnurlp-response.md for details on why this is needed.

NOTE: This is technically a breaking change. Given that we're not yet at UMA 1.0, I'm bumping the protocol version here to 0.2 to indicate the bump and to be able to tell what version the counterparty is using for debugging.

Shoot, I may need help with the test failure here tomorrow @zhenlu. It looks like f64 doesn't implement core::cmp::Eq (because of NaN?), so I'm not really sure how to propagate equality up the struct hierarchy.


text:
Argument websiteId is missing.

Describe the Bug
Found in the console
Database
PostgreSQL
Relevant log output
umami-1  | PrismaClientValidationError:
umami-1  | Invalid `prisma.websiteEvent.create()` invocation:
umami-1  |
umami-1  | {
umami-1  |   data: {
umami-1  |     id: "9051123e-d9bc-40f3-aaf5-c15a2199b833",
umami-1  |     sessionId: undefined,
umami-1  |     urlPath: "/home",
umami-1  |     urlQuery: undefined,
umami-1  |     referrerPath: "/",
umami-1  |     referrerQuery: undefined,
umami-1  |     referrerDomain: undefined,
umami-1  |     pageTitle: "------------",
umami-1  |     eventType: 1,
umami-1  |     eventName: null,
umami-1  | +   websiteId: String
umami-1  |   }
umami-1  | }
umami-1  |
umami-1  | Argument `websiteId` is missing.
umami-1  |     at ri (/app/node_modules/@prisma/client/runtime/library.js:119:5888)
umami-1  |     at ai.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:126:6431)
umami-1  |     at ai.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/library.js:126:6109)
umami-1  |     at ai.request (/app/node_modules/@prisma/client/runtime/library.js:126:5817)
umami-1  |     at async l (/app/node_modules/@prisma/client/runtime/library.js:131:9709)
umami-1  |     at async h (/app/.next/server/pages/api/send.js:1:2849)
umami-1  |     at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16545)
umami-1  |     at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16981)
umami-1  |     at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:556:9)
umami-1  |     at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:268:37) {
umami-1  |   clientVersion: '5.9.1'
umami-1  | }

Which Umami version are you using? (if relevant)
2.10.2
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
Docker

Both sessionId and websiteId are non-nullable columns, so it should fail. Just wondering how it got to this state. This was produced from the tracker and not a custom payload?

Found the Same Error in the Logs of a self-hosted umami:
PrismaClientValidationError:
Invalid prisma.websiteEvent.create() invocation:
{
data: {
id: "XXXXXXXXXXXXXXXXXXXXXXX",
sessionId: undefined,
visitId: "XXXXXXXXXXXXXXXXXXXXXXXX",
urlPath: "#/XXXXXXXXXXXX",
urlQuery: undefined,
referrerPath: "#/",
referrerQuery: undefined,
referrerDomain: "",
pageTitle: "XXXXXXXXXXXXXXX",
eventType: 1,
eventName: null,

websiteId: String
}
}
Argument websiteId is missing.
at Tn (/app/node_modules/@prisma/client/runtime/library.js:115:5888)
at In.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:122:6510)

Client Version:5.11.0

Fwiw, I had the same issue but the cause was outside Umami. Maybe the info can be of help to others too.
I had a custom script that called umami.track but I forgot to wait for the umami-script to be loaded.
  <script data-id="umami-script" defer src="..." data-website-id="..."></script>

<script type="text/javascript">
    function myTracker(eventName, eventData) {
    ...
    umami.track(eventName, eventData);
    }
</script>

This randomly failed with the above mentioned error, due to the umami script not being loaded yet when myTracker was called. The solution was to add a listener for the umami-script to be loaded, like so:
<script data-id="umami-script" defer src="..." data-website-id="..."></script>

<script type="text/javascript">
    function myTracker(eventName, eventData) {
       document.querySelector('script[data-id="umami-script"]').addEventListener('load', function () {
          ...
          umami.track(eventName, eventData);
       });
    }
</script>

It must be something in Umami or reverse-proxy that serves the slef-hosted Umami. What i did:

The logs show the error.
Surf to a random static page that has the umami script.
Result = the error in the logs.
Stop and start the Umami docker container (Umami + Postgresql database)
Surf to another random static page.
No error in logs + website visit / events are tracked again.

I also have the same issue today.
 Invalid `prisma.websiteEvent.create()` invocation:
   |
   | {
   |   data: {
   |     id: "********",
   |     sessionId: undefined,
   |     visitId: "*******",
   |     urlPath: "/",
   |     urlQuery: undefined,
   |     referrerPath: undefined,
   |     referrerQuery: undefined,
   |     referrerDomain: "",
   |     pageTitle: "******",
   |     eventType: 1,
   |     eventName: null,
   | +   websiteId: String
   |   }
   | }
   |
   | Argument `websiteId` is missing.
   |     at Tn (/app/node_modules/@prisma/client/runtime

I am using v2.11.2 at my own host.

I got the same error. Umami v2.11.3, Postgres 16.2, docker container

Fixed in v2.12.0.

I also still get this issue in our server logs on version v2.12.1.
Database: MySQL
Log output (I redacted information with asterisks *):
Argument `websiteId` is missing.
at Tn (/app/node_modules/@prisma/client/runtime/library.js:115:6855)
at In.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:122:6533)
at In.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/library.js:122:6211)
at In.request (/app/node_modules/@prisma/client/runtime/library.js:122:5919)
at async l (/app/node_modules/@prisma/client/runtime/library.js:127:11167)
at async h (/app/.next/server/pages/api/send.js:1:3068)
at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853)
at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492)
at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9)
at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37) {
  clientVersion: '5.14.0'
}

PrismaClientValidationError:
Invalid `prisma.websiteEvent.create()` invocation:
{
data: {
  id: "81720f84-71f1-4863-b927-07b3e1fbf0e9",
  sessionId: undefined,
  visitId: "0519dbca-d94f-5a53-bfa4-66a53fdfe916",
  urlPath: "/****/*****/**********************/**********",
  urlQuery: "*****=****&****=*",
  referrerPath: "/****/*****/**********************/**********",
  referrerQuery: undefined,
  referrerDomain: "",
  pageTitle: "***** ****** ***** **** **** ***** | ******* ********",
  eventType: 1,
  eventName: null,
  + websiteId: String
  }
}

Umami version: v2.12.1
Deployment: docker from umami packages
Tracker script:
<script defer="" src="https://***************.com/script.js" data-website-id="e9c5a45a-ab11-4bd9-bab1-ceaadf94ca70"></script>

Can someone take another look please?

i'm seeing this problem in 2.13.2 also
2024-08-31T18:34:20.826110+00:00 analytics npx[814]: Argument `websiteId` is missing.
2024-08-31T18:34:20.826122+00:00 analytics npx[814]:     at An (/opt/umami/node_modules/@prisma/client/runtime/library.js:114:7526)
2024-08-31T18:34:20.826135+00:00 analytics npx[814]:     at _n.handleRequestError (/opt/umami/node_modules/@prisma/client/runtime/library.js:121:7392)
2024-08-31T18:34:20.826147+00:00 analytics npx[814]:     at _n.handleAndLogRequestError (/opt/umami/node_modules/@prisma/client/runtime/library.js:121:7057)
2024-08-31T18:34:20.826160+00:00 analytics npx[814]:     at _n.request (/opt/umami/node_modules/@prisma/client/runtime/library.js:121:6741)
2024-08-31T18:34:20.826173+00:00 analytics npx[814]:     at async l (/opt/umami/node_modules/@prisma/client/runtime/library.js:130:9355)
2024-08-31T18:34:20.826185+00:00 analytics npx[814]:     at async x (/opt/umami/.next/server/pages/api/send.js:1:2791)
2024-08-31T18:34:20.826197+00:00 analytics npx[814]:     at async K (/opt/umami/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853)
2024-08-31T18:34:20.826210+00:00 analytics npx[814]:     at async U.render (/opt/umami/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492)
2024-08-31T18:34:20.826223+00:00 analytics npx[814]:     at async NextNodeServer.runApi (/opt/umami/node_modules/next/dist/server/next-server.js:600:9)
2024-08-31T18:34:20.826236+00:00 analytics npx[814]:     at async NextNodeServer.handleCatchallRenderRequest (/opt/umami/node_modules/next/dist/server/next-server.js:269:37) {
2024-08-31T18:34:20.826248+00:00 analytics npx[814]:   clientVersion: '5.17.0'
2024-08-31T18:34:20.826260+00:00 analytics npx[814]: }

@mikecao could this please be re-opened?

+1 in v2.13.2, self hosted, postgres, with docker. Is there a workaround?

found a fix. not sure if it's robust. Here's a PR: https://github.com/umami-software/umami/pull/2946

For more context, the issue arises on new deployments of umami when there is no entries in the website_event table. Therefore performing an inner join on this table returns no entries, even when there is a matching session in the session table. Performing an outer join will at least allow the current session to be returned from this query when the website_event table is empty

We have a deployment with data in the table, and some users are unfortunately triggering this error still. Still diving into it...

Hey everyone!
I'm encountering the same issue with my self hosted instance of Umami (v2.14.0) and Postgres.
If I try to send an identify request and no events has been recorded yet, I get the error that website ID is missing.
The thing is, further requests (regular events) fails too. The app seems to stay in a broken state. I had to clean up the website data and then send regular events to get it to work.
I've got the same exact logs that everyone else but if you need more info, let me know.

Me too. Still encountering the sam issue. Sometimes it works well, sometimes it fails.

self hosted docker
Umami (v2.14.0)
Postgres
image: docker pull docker.umami.is/umami-software/umami:postgresql-latest

Update: I'm now getting the error randomly, even when i'm not using the identify feature. My database has some events already. Had to redeploy the server instance to get it to work again.

Same error
Argument websiteId is missing.
at An (/app/node_modules/@prisma/client/runtime/library.js:114:7526)
at _n.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7392)
at _n.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7057)
at _n.request (/app/node_modules/@prisma/client/runtime/library.js:121:6741)
at async l (/app/node_modules/@prisma/client/runtime/library.js:130:9355)
at async x (/app/.next/server/pages/api/send.js:1:2791)
at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853)
at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492)
at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9)
at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37) {
clientVersion: '5.17.0'
}

Same problem. After I reset the website data the error is gone.
Probably something related with session data since I started using that yesterday (umami.identify) and all the sites that are not using it are working fine.
Self-hosted umami-software/umami:mysql-v2.14.0.

Can confirm (v2.14.0, ghcr.io/umami-software/umami:postgresql-v2.14.0), this issue has not been fixed and should be re-opened.
Argument `websiteId` is missing.
    at An (/app/node_modules/@prisma/client/runtime/library.js:114:7526)
    at _n.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7392)
    at _n.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7057)
    at _n.request (/app/node_modules/@prisma/client/runtime/library.js:121:6741)
    at async l (/app/node_modules/@prisma/client/runtime/library.js:130:9355)
    at async x (/app/.next/server/pages/api/send.js:1:2797)
    at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16881)
    at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17520)
    at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:598:9)
    at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37) {
  clientVersion: '5.17.0'
}

@mikecao Can you re-open this issue? Seems like a lot of people are still encountering this problem.

Re-opening. Found the issue and will push out a fix.

authors: CTHRU Sov3rain d717an diogomartino franciscao633 genki hongkunyoo jjjhill kddial ldpr m1911star manuel-rw mikecao ndaidong obstkompost oliverzgy

repo: umami-software/umami


text:
Improve german (de-DE) translation

Hey, I've improved the German (de-DE) translation.

Previously untranslated values are now translated
Improved spelling of some values

PRs are usually made against the dev branch. You are doing it against the master branch directly, if I am not mistaken, despite it being the default branch you should change your PR against dev.


text:
ListView on Scrollview up The slidepanel hide

Hi good day.
I have my SlidingUpPanelLayout in an Activity and in the SlidePanel i have a FrameLayout that loads a fragment with a ListView. When i made scroll up the panel this hides. I try to use the helper that you mention but i don't see how to use it.

Even i have the same issue...scrollbar is appearing while moving the list item..not like ListView

RecycleView items hidden in SlidePanel :(

repo: umano/AndroidSlidingUpPanel


text:
Update Api endpoints because sagepay.com will retire soon.

The old ‘sagepay.com’ payment gateway URL is being retired at the end of March so all integrations will need to use their new gateway URL.

Just a minor change, otherwise looks good to me.
We'll also need to make sure we release v10, v12 versions as well so you'll need to cherry pick this change back.

authors: mattbrailsford umbracotrd


text:
change textColor when tintColor is changed

Change the text colour instead of only the cursor colour when a tintColor is specified.

Can you resolve the conflicts and provice a screenshot comparison? Thanks


text:
father 4.x 在umd模式下不会自动 将peerDependencies 进行 external

father 4.x 在umd模式下不会自动 将peerDependencies 进行 external

新版没这个约定了，通常 externals 需要配合导出的全局变量，自动推导出来的不一定是对的，还会让构建变得黑盒，所以需要啥单独配 externals 即可

authors: PeachScript blackraindrop

repo: umijs/father


text:
A question about the runtime of the 2d-3d transform

@una-dinosauria  when I use the time.time() to test the running time of the step function which transform the 2d poses to 3d poses. the outcome  time is more than 100 ms ,which is far more  than  3ms mentioned in your article.
        t1 = time.time() * 1000

        _, _, poses3d = model.step(sess, enc_in, np.zeros_like(dec_out), dp, isTraining=False)

        t2 = time.time() * 1000

I just don't know why ? can you give me some  clue ?

Hi @andyqian2015,
Three things:

The code that you are showing is not measuring time. See https://stackoverflow.com/a/14452178/1884420
We reported time on a batch of 64, and using a fairly advanced GPU (Titan Xp). What hardware do you have? How big is the batch in enc_in on that piece of code?
If you run our code that trains for 1 epochs, it will print the elapsed time per training epoch. How much does that print on your machine? (you may also want to look at that code to see how we are measuring time).

Cheers,

@una-dinosauria thx for your reply. I know exactly the reason why the runtime is so long : getting  data form .h5  has taken almost 200ms.
thx


text:
aws lambda layer

Hi,
I tried to create a lambda layer for this library but it's not working, is there a lambda layer zip or docker image to use the library in lambda?

Hi @vikaskookna Already replied your question in this issue https://github.com/unclecode/crawl4ai/issues/155 So I close this issue, thx using Crawl4ai

authors: unclecode vikaskookna


text:
The new changelist horizontal scrollbar position feature not working on google chrome

I don't even know the reason, but the feature works on my firefox and MS edge browser.
While on google chrome the scrollbar still on the bottom.
I 've tried uninstall and install unfold and make sure the version is the newest 0.30.0
My google chrome version is 126.0.6478.127.
It's not that important but hoping I can get some fresh ideas/inspirations why this happens?

I just tested list_horizontal_scrollbar_top flag on ModelAdmin and it works without any issues on Chrome. Please create a minimal repo where it is possible to reproduce the issue.

I cannot reproduce the issue with minimal repo. I guess maybe some mixin class make my project strange. Thank you again for answering.

authors: AckyZhang lukasvinclav

repo: unfoldadmin/django-unfold


text:
🛑 Nitter is down

In 5d6f01f, Nitter (https://nitter.unforest.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nitter is back up in 1a99f54 after 5 minutes.

repo: unforest/uptime


text:
🛑 SearXNG is down

In b38e883, SearXNG (https://searxng.unforest.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SearXNG is back up in 45624d7 after 11 minutes.


text:
🛑 Unforest is down

In 2539f39, Unforest (https://www.unforest.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Unforest is back up in 3f95f51 after 14 minutes.


text:
🛑 Nitter is down

In 604a615, Nitter (https://nitter.unforest.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nitter is back up in d0d0790 after 11 minutes.


text:
🛑 SearXNG is down

In 7b729b4, SearXNG (https://searxng.unforest.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SearXNG is back up in 1b5e5a6 after 10 minutes.


text:
chore(main): release remembit-web 0.1.0

:robot: I have created a release beep boop
0.1.0 (2024-07-08)
Features

web: update landing page (001f64c)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

remembit-web-v0.1.0
:sunflower:

repo: ungnome/remembit


text:
build: Add arch-specific dependencies

Changes:

Use arm64 LLVM when building on Apple Silicon (arm64) (resolve #151)
Bump LLVM to 18 for build

Build failed, related issue, investigating...

Build failed, related issue (and fix?), investigating...

There's still some pretty tricky issues to solve before we can build the thing on LLVM 18...

I've also ran into issues building my fork of Ungoogled Chromium (123) for macOS due to LLVM. Error messages told me to use LLVM 19 IIRC

I've also ran into issues building my fork of Ungoogled Chromium (123) for macOS due to LLVM. Error messages told me to use LLVM 19 IIRC

I haven’t tried build it yet, will try it this weekend and let’s see what happens...

This PR will be closed as it will be included in the PR for the next update.


text:
Interpolation mechanism for discrete fields

This PR depends on #216, which should be merged before this one is considered.
A new interpolation mechanism for discrete fields is introduced. Compared to the original implementation, the new method takes an interpolator object with the interpolation algorithm. We can now write:
val df : DiscreteField[D, Domain, A] = ???
val interpolator = NearestNeighborInterpolator()
val field : Field[D, A] = df.interpolate(interpolator)

This makes it possible to use different interoplation algorithms using the same interface and separates the interpolation algorithm from the field implementation. The same mechanism is also used for the interpolation of a DiscreteLowRankGaussianProcess, i.e. we can write
val discreteGp : DiscreteLowRankGaussianProcess[D, Domain, A]
val interpolator = NearestNeighborInterpolator()
val gp : LowRankGaussianProcess[D, A] = discreteGp.interpolate(interpolator)

:+1:

authors: Ghazi-Bouabene marcelluethi

repo: unibas-gravis/scalismo


text:
Skip parsing cms- attribute.

What is this?
This issue is suggested the following attribute features:

If element has cms-ignore-static attribute, Spear will skip generating CMS Parse.

This attribute will use the case of:

Add Embed JS content into page.
Add announcement block
Add search block
Add Form content into page.

Add

repo: unimal-jp/spear


text:
Proposal: Tag loop in content.

What is this feature?
#123 was focused on tag routing. However we need to provide the tag field in content.
For example, Spear v1.3.1(latest version) will replace the tag field in the content as string which concatenating tag with comma.
If the original content is the following, the spear will generate the second sample code:
Original Content

{%= news_tags %}

Generated Content

Travel,Language

This string doesn't be useful for user. So we need to provide this field as sub-loop.
Proposal Spec
1. Extracting the content tag
If embed tag has cms-tag-sub-loop, Spear extract each tag.
Example:

{%= news_tags %}

Generated File:

Travel

Language

2. Extracting the all of content-type tag
If element has cms-loop-tag-only, Spear extract each all tag which related with content-type.
Example:

{%= news_tag %}

Generated File:

Computer Science

Travel

Art

Language

この機能はなに？
#123 はタグによるルーティングに焦点を当てていました。しかし、コンテンツ内でのタグもサポートする必要があります。
例えば、Spear v1.3.1(最新版)はタグフィールドを各タグをカンマで結合した文字列に置換します。
もし以下のようなコンテンツがあれば、Spear は2つ目のサンプルのようなコードを生成します。:
コンテンツ

{%= news_tags %}

生成されたコンテンツ

Travel,Language

この文字列はなんらユーザーにとって有益なものになりません。そのため、タグフィールドをサブループとして扱う機能を提供する必要があります。
提案する機能
1. コンテンツ内のタグを展開
もし組み込みタグ内に cms-tag-sub-loop があれば、Spearは各タグを展開します。
例：

{%= news_tags %}

生成されたファイル：

Travel

Language

2. content-type に紐づくすべてのタグの展開
もし cms-loop-tag-only を持つ要素があれば、Spear はコンテンツタイプに紐づくすべてのタグを展開する。
例：

{%= news_tag %}

生成されたファイル：

Computer Science

Travel

Art

Language

(160-A)※  [2. content-type に紐づくすべてのタグの展開]について、cms-loopやcms-tag-subloopはoptionの書かれたDOM自体が繰り返されますが、cms-loop-tag-onlyはその一つ階層の下のDOM が繰り返されています。これは意図的ですか？
loopの挙動で混乱を招きそうな問題と、以下のような場合どのように表示するかの問題がありそうです

{%= news_tag %}

{%= news_tag %}の兄弟要素の適当な何か

by @mantaroh
たしかに。正しくはこんな感じでしょうか？

はい！そちらの方が、指定しやすそうと思いました！
ただそれだけだと、コンテンツタイプに複数のタグフィールドタイプが設定されているときの挙動を考える必要がありそうです。
タグフィールドidをそれぞれtag1, tag2とすると仮定して下記(i)(ii)の場合だと、どう表示するのかな私も悩んでいます……
(i)

{%= news-tag1 %}{%= news-tag2 %}

(ii)

{%= news-tag1 %}
    {%= news-tag2 %}

※ 何点下記になるところがあるため、コメントに言及しやすいよう(160-A)のようにナンバリングしていきます

(160-B) [1. コンテンツ内のタグを展開] loopとsubloopの使い分けの意図について教えてください。
参照のループでは*-subloopというoption名ではなく、cms-loop, cms-field="[参照フィールドのID]" の組み合わせで指定しています。
また、タグごとの詳細ページのルーティング( #123 )では、cms-tag-loopというoptionを指定しています。
loopやsubloopという言葉に対して使い分けの意図を揃えておいた方がよさそうと考えたためです。
例を挙げると、「loopやsubloopという言葉に対して、コンテンツ配列を繰り返すときはloop, フィールドの値が配列の場合、繰り返すときはsubloop」などでしょうか。(この例の場合はcms-tag-loopがすこし意図から外れてしまうことを考える必要があります。)

(160-C) [1, 2] 入れ子をした場合など、下記のように書いた場合どうなりますか？
エラーを出すか否かなど、考慮すべきことがありそうです。
タグフィールドidをそれぞれtag1, tag2と仮定します
(i)

    {%= news_tag1 %}
    {%= news_tag2 %}

(ii)

    {%= news_tag1 %}

  {%= news_tag2 %}

(iii)

    {%= news_tag1 %}
    {%= news_tag2 %}

(160-D) [1]タグ以外の複数の値を持つフィールドタイプ(参照など)と命名規則を揃えなくても良いですか？
これは確認です。
(160-A), (160-B)でもすこし触れましたが、参照フィールドとタグフィールドの繰り返しの仕方には違いがあります。
拡張性を考えた時に、なぜ違うかを明確にしておいた方がよさそうと考えたのでコメントしました
cms-ref-subloopではなく、cms-loop, cms-fieldの二つで設定するのは、「タグフィールドはフィールドの値の要素を、参照フィールドは参照しているコンテンツの要素(フィールド)を繰り返しているから」でしょうか？
私的には、タグのような繰り返しのできる新しいフィールドタイプが増えたとしても、cms-NEW_FIELD_TYPE_ID-subloopとすればよさそうであるので、問題はないと考えておりますが、他の皆さんはいかがですか？

起票ありがとうございます！
コンテンツ内のタグループについて
loopという概念になるので、できるだけ既存のコンテンツループと、参照フィールドのループの挙動に寄せるのがいいのかなと思いました。
なのでイメージ的には…

{%= releases_[フィールドID1] %}

{%= releases_[参照フィールドのID]_[参照先コンテンツのフィールドID1] %}

{%= releases_[参照フィールドのID]_[参照先コンテンツのフィールドID2] %}

        <button>{%= releases_[タグフィールドのID]_value %}</button>

みたいなのはどうかなと… 🤔
これからloopできるフィールドが増えた場合は、{%= releases_[タグフィールドのID]_value %}の部分で何を表示するのかコントロールできると、参照コンテンツのループと同じような書き方になるので、直感的でわかりやすいかなと思いました！
2. content-type に紐づくすべてのタグの展開
こちらについては、このコメントの中に書かれている、loopを指定したタグ自体が繰り返される形式がいいと思いました！

@pandaulait
@oxo-yuta
コメントありがとうございます！！
たしかに cms-loop 内の参照ループとタグループ同じ扱いでも良さそうですね！
コメントにもあったように -subloop は誤解を招きそうですね。
現在の cms-tag-loop の命名規則もわかりにくというのもあり。。

現在の cms-tag-loop は cms-tag-routing として、両方サポートする(ただし、cms-tag-loop は非推奨
1コンテンツの保持するタグの展開は cms-loop を用いる
コンテンツタイプに紐づくタグの展開は cms-loop-tag-only を用いる

#変更後のスペック
What is this feature?
#123 was focused on tag routing. However we need to provide the tag field in content.
For example, Spear v1.3.1(latest version) will replace the tag field in the content as string which concatenating tag with comma.
If the original content is the following, the spear will generate the second sample code:
Original Content

{%= news_tags %}

Generated Content

Travel,Language

This string doesn't be useful for user. So we need to provide this field as sub-loop.
Proposal Spec
1. Extracting the content tag
If embed tag has cms-tag and cms-field, Spear extract each tag.
Example:

{%= news_tag1_value %}

Generated File:

Travel

Language

2. Extracting the all of content-type tag
If element has cms-loop-tag-only, Spear extract each all tag which related with content-type.
Example:

{%= news_tag %}

Generated File:

Computer Science

Travel

Art

Language

この機能はなに？
#123 はタグによるルーティングに焦点を当てていました。しかし、コンテンツ内でのタグもサポートする必要があります。
例えば、Spear v1.3.1(最新版)はタグフィールドを各タグをカンマで結合した文字列に置換します。
もし以下のようなコンテンツがあれば、Spear は2つ目のサンプルのようなコードを生成します。:
コンテンツ
{%= news_tags %}

生成されたコンテンツ

Travel,Language

この文字列はなんらユーザーにとって有益なものになりません。そのため、タグフィールドをサブループとして扱う機能を提供する必要があります。
提案する機能
1. コンテンツ内のタグを展開
もし組み込みタグ内に cms-loop と cms-field があり、指定されたフィールドがタグの場合、Spearは各タグを展開します。
例：

{%= news_tags1_value %}

生成されたファイル：

Travel

Language

2. content-type に紐づくすべてのタグの展開
もし cms-loop-tag-only を持つ要素があれば、Spear はコンテンツタイプに紐づくすべてのタグを展開する。
例：

{%= news_tag %}

生成されたファイル：

Computer Science

Travel

Art

Language

content-type に紐づくすべてのタグの展開
2のcms-loop-tag-onlyのタグの取得範囲ですが、これは一つのコンテンツタイプに複数のタグフィールドが設定されていた場合、それらすべてを取得するのですか？
それともどれかタグフィールド一つについてのみ取得するのですか？

もし、一つのタグフィール度についてのみであれば、cms-fieldのように、fieldを指定する必要がありそうです。

コンテンツ内のタグを展開

良さそうです！下記のような入れ子をした場合はどうなりますか？

      {%= news_tags1_value %}

          {%= news_tags2_value %}

@pandaulait

2のcms-loop-tag-onlyのタグの取得範囲ですが、これは一つのコンテンツタイプに複数のタグフィールドが設定されていた場合、それらすべてを取得するのですか？
それともどれか指定したタグフィールド一つについてのみ取得するのですか？
もし、一つのタグフィールドについてのみであれば、cms-fieldのように、fieldを指定する必要がありそうです。
個人的には(i)のどれか指定したタグフィールド一つについてのみ取得するの仕様の方が使用しやすそうと思いました

そうですね。２つタグがあった場合の取り扱いを言及していなかったですね。。。
私も(i)が良いと思います。
ただ、タグフィールドを固定しても良いかなと思いました。
この仕様いかがでしょう？

{%= news_tag1 %}{%= news_tag2 %}

生成後の HTML ({%= news_tag1 %} だけ置換される)

tag1-1 {%= news_tag2 %}

tag1-2 {%= news_tag2 %}

tag1-3 {%= news_tag2 %}

tag1-4 {%= news_tag2 %}

良さそうです！下記のような入れ子をした場合はどうなりますか？

Spear のパーサーを利用すると入れ子の場合、階層深い部分がまず展開され、その後階層が上に行く順番で展開していきます。
以下のサンプルの場合：

      {%= news_tags1_value %}

          {%= news_tags2_value %}

生成される HTML:

 Tag1-val1

Tag2-val1

Tag2-val2

 Tag1-val2

Tag2-val1

Tag2-val2

@mantaroh

ただ、タグフィールドを固定しても良いかなと思いました。
この仕様いかがでしょう？

その仕様でも良いと思います！
ただ一応2点、知りたいです

なぜタグフィールドを固定したいのですか？
タグに関わらず、他にフィールドの埋め込みタグも展開されない仕様でしょうか?

よろしくお願いします 🙇

1.コンテンツ内のタグを展開について
一点別で気づきましたが、{%= news_tags1_value %}のvalueの部分はcmsで指定できない部分なので、{%= news_#published_at %}のように、#をつけた方がわかりやすいのかなと思いましたがいかがですか？
{%= news_tags1_value %} -> {%= news_tags1_#value %}

@pandaulait

ただ一応2点、知りたいです
なぜタグフィールドを固定したいのですか？

タグフィールドが複数あった場合、どちらをどのようにループさせたいかはユーザーの制御に任せたほうが良いと思います。
また、Spear がユーザーが指定した HTML の中身を解析して、ループするべきタグフィールドを知る必要があるので、実装上の成約も多くなる気がしています。

{%= news_tag1 %}{%= news_tag2 %}

このサンプルでは、どのタグをどれだけループするか検討がつきにくいかなと思います。

タグに関わらず、他にフィールドの埋め込みタグも展開されない仕様でしょうか?

明示的に cms-loop-tag-only としているので、単純にタグのループだけをさせる仕様のほうがわかりやすいかなと思います。
ユースケースとしても、これを使う場合はコンテンツタイプで使われているタグをすべて取得して描画するケースが多いかと思います！

一点別で気づきましたが、{%= news_tags1_value %}のvalueの部分はcmsで指定できない部分なので、{%= news_#published_at %}のように、#をつけた方がわかりやすいのかなと思いましたがいかがですか？

そうですね！
確かにこれはサフィックスのような扱いになるので # が必要そうです！つけておきます！

変更後のスペック
What is this feature?
#123 was focused on tag routing. However we need to provide the tag field in content.
For example, Spear v1.3.1(latest version) will replace the tag field in the content as string which concatenating tag with comma.
If the original content is the following, the spear will generate the second sample code:
Original Content

{%= news_tags %}

Generated Content

Travel,Language

This string doesn't be useful for user. So we need to provide this field as sub-loop.
Proposal Spec
1. Extracting the content tag
If embed tag has cms-tag and cms-field, Spear extract each tag.
Example:

{%= news_tag1#value %}

Generated File:

Travel

Language

2. Extracting the all of content-type tag
If element has cms-loop-tag-only, Spear extract each all tag which related with content-type.
Example:

{%= news_tag1 %}

Generated File:

Computer Science

Travel

Art

Language

この機能はなに？
#123 はタグによるルーティングに焦点を当てていました。しかし、コンテンツ内でのタグもサポートする必要があります。
例えば、Spear v1.3.1(最新版)はタグフィールドを各タグをカンマで結合した文字列に置換します。
もし以下のようなコンテンツがあれば、Spear は2つ目のサンプルのようなコードを生成します。:
コンテンツ
{%= news_tags %}

生成されたコンテンツ

Travel,Language

この文字列はなんらユーザーにとって有益なものになりません。そのため、タグフィールドをサブループとして扱う機能を提供する必要があります。
提案する機能
1. コンテンツ内のタグを展開
もし組み込みタグ内に cms-loop と cms-field があり、指定されたフィールドがタグの場合、Spearは各タグを展開します。
例：

{%= news_tags1#value %}

生成されたファイル：

Travel

Language

2. content-type に紐づくすべてのタグの展開
もし cms-loop-tag-only を持つ要素があれば、Spear はコンテンツタイプに紐づくすべてのタグを展開する。
例：

{%= news_tag1 %}

生成されたファイル：

Computer Science

Travel

Art

Language

回答ありがとうございますー！

明示的に cms-loop-tag-only としているので、単純にタグのループだけをさせる仕様のほうがわかりやすいかなと思います。
ユースケースとしても、これを使う場合はコンテンツタイプで使われているタグをすべて取得して描画するケースが多いかと思います！

そうですね、tag onlyですので、他の埋め込みタグの要素が判定できないですね 🙇
LGTMですー！

authors: mantaroh oxo-yuta pandaulait


text:
Segmentation fault (core dumped)

Version: UniMRCP 1.7.0
MRCP V1 crash, Segmentation fault (core dumped),
Would you give me some suggests please? That is backtrace gdb
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/local/unimrcp/bin/unimrcpserver -r /usr/local/unimrcp -o 3 -w'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  apt_header_field_alloc (pool=pool@entry=0x7ff08c04b1d8) at ../../libs/apr-toolkit/include/apt_string.h:46
46		str->buf = NULL;
[Current thread is 1 (Thread 0x7ff099d0e700 (LWP 14))]

Is this problem reproducible? Can you provide the logs?

Closing this issue for now. If you are able to reproduce the problem and provide the logs with a coredump, please feel free to reopen.

authors: achaloyan dragonsongohan

repo: unispeech/unimrcp


text:
Create the UnitsML website

Providing existing information and highlight supporters.
Ping @strogonoff for scaffold.

Done.


text:
Add German ErrorMessages

Given Seshat also has ErrorMessages localized in French, I'm happy to extend that to German.

Thanks!

authors: desruisseaux keilw

repo: unitsofmeasurement/seshat


text:
Add Documentation for the Production Build of the Web UI

Is your feature request related to a problem? Please describe.
There are some differences between the local development environment and the production build. For example, configuring proxy in the package.json does not apply to the production build.
Describe the solution you would like
It would be helpful to include documentation that clarifies these differences and provides guidance on setting up the production build.

Do we need an additional Dockerfile as well?

repo: unitycatalog/unitycatalog


text:
Licence img is broken

See the following screenshot:

I think it's related to the modifications made to resolve #13.

Fixed thanks to @myrdinm, I'll close this one.


text:
Something against Catagories?

Why you build this library as a cascade of inheritited classes is beyond me? Maybe I'm missing something, but why not just build a single class with extensions/catagories for differnet opperations?

The reason for the cascade of inheritance is partially due to the fact that Objective-C does not have multiple inheritance. It makes sense that, for instance, scalable images would be a subclass of basic bitmap images, since scaling uses the functionality provided by the bitmap. I would have preferred to make several subclasses of BitmapImageRep, and then have ANImageBitmapRep subclass from all or most of them, but I simply did not have that option.  It is possible that categories could have provided the structure that I needed to execute this task, but hey, the code is already done, why redo it now?

The reason not to do what you've done is that now your classes have become unnecessaryly dependent on each other. you can't for example simply use the rotation methods without necessarily adding the scaling class. or in my case I just want to use with ANImageBitmapRep methods without including all the Rotation, Scaling & cropping classes.... I'm going to fork, and fix the way I fell it should be done, your welcome to pull if you want....

Categories seem like a feasible solution, with only one problem. With categories, any instance of ANImageBitmapRep will respond to all of the selectors for all categories that were compiled with the app. Despite the fact that you may only import ANImageBitmapRep+Crop.h, all of the scaling and rotating method implementations will still be in the instance's runtime implementation table. This is why using different classes for different functionality is a better method for doing the same thing.
To fix the issue that you bring up (of cascading subclasses), I have instead taken to a composition architecture. There is a base class, namely BitmapContextRep, which serves basic CGContextRef functions, etc. Then, there are a set of "manipulator" classes, which encapsulate BitmapContextReps, but are not subclasses of BitmapContextRep, although they will respond and forward any methods that the underlying BitmapContextRep may implement. Finally, the ANImageBitmapRep class creates an instance of each of these manipulators, and dispatches invocations to those manipulators. This architecture is essentially a roundabout way of doing multiple inheritance in a language that does not support it.
You can look at my latest commits to see what I am talking about. This composition architecture allows you to work with any of the manipulators, without creating an instance that has all of the available implementations in its implementation table.  I prefer this to categories, but of course everyone is entitled to their own opinion.

I guess that makes sense, but out of curisoity why you are concerned about the instances runtime implementation table? Is it for performance reasons or its because you don't want the a class that is only supposed to be able to rotate to be able to scale?

In this case, it's a combination of both reasons. With categories, sure you can not import specific headers, but the ANImageBitmapRep still has the same functionality, you just aren't allowed to use it. My method allows you to create instances of BitmapXXXManipulator, and only use its functionality, without having the rest of the class weighing you down. It seems that this is a slightly better architecture than categories, even though both are better than the old cascading setup.

Makes perfect sense, it looks a little different at first, but I actually quite like it. Do you think you could break the core classes off into a submodule so they can be properly linked to other projects?

authors: bguest unixpickle

repo: unixpickle/ANImageBitmapRep


text:
fix(unhead): falsey class / style breaks merging

🔗 Linked issue
#289
❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Resolves #289
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Fix is available in 1.8.9, thanks again

repo: unjs/unhead


text:
Changes to existing linked text (and for future linked text included)

All linked text must have the following identifiers:

underlined
should be red not blue (please use the UNO red for these links and any other red on the website – RGB 215/25/32 – Hexadecimal #D71920)

These changes are being made as pages are updated.

authors: caadler robynlloos


text:
TS2322: Type 'Preset<{}>' is not assignable to type 'Preset | Preset[]'.

UnoCSS version
0.51.12
Describe the bug
When i use the preset @unocss/preset-rem-to-px ,it report the error TS2322: Type 'Preset<{}>' is not assignable to type 'Preset | Preset[]'.
error log detail
TS2322: Type 'Preset<{}>' is not assignable to type 'Preset<Theme> | Preset<Theme>[]'.   Type 'Preset<{}>' is not assignable to type 'Preset<Theme>'.     Types of property 'rules' are incompatible.       Type 'Rule<{}>[] | undefined' is not assignable to type 'Rule<Theme>[] | undefined'.         Type 'Rule<{}>[]' is not assignable to type 'Rule<Theme>[]'.           Type 'Rule<{}>' is not assignable to type 'Rule<Theme>'.             Type '[RegExp, DynamicMatcher<{}>]' is not assignable to type 'Rule<Theme>'.               Type '[RegExp, DynamicMatcher<{}>]' is not assignable to type '[string, CSSObject | CSSEntries]'.                 Type at position 0 in source is not compatible with type at position 0 in target.                   Type 'RegExp' is not assignable to type 'string'.

Reproduction
// uno.config.ts
import {
    defineConfig,
    presetUno,
} from 'unocss';
import presetRemToPx from '@unocss/preset-rem-to-px';

export default defineConfig({
    presets: [
        presetUno(),
        presetRemToPx({
            baseFontSize: 4,
        }),
    ],
})

System Info
No response
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

It looks like you need to upgrade both unocss and @unocss/preset-rem-to-px to the latest version.

If having similar issue - check if your import is correct.
IntelliJ accidentally imported this
import presetUno from '@unocss/preset-uno'

Instead of
import {defineConfig, presetUno} from 'unocss'

authors: Dunqing changyuqing darylteo

repo: unocss/unocss


text:
[Android/iOS][Controls - Slider] The Slider disable state doesn't match design

Steps to Reproduce:

Launch app
From Burger menu select Controls
Tap Slider > Cupertino
Notice slider disabled state

Current behaviour

Expected behaviour

Repro rate
100%
Affected platform(s):
web
Android
iOS
Version & devices
Chrome
Samsung Galaxy A50 - 9
iPhone 6S - 14.0.1

Verified on build  1.0.0 (675)


text:
[ChipGroup] SelectedItem initial binding is not working

Current behavior

When binding the SelectedItem property from ChipGroup to a property in VM, the initial binding is not taken in consideration and does not propagate.

Clues :

This might be due to a race condition between SelectedItem being set and ItemsSource  being set to late.
Also in OnSelectedItemChanged method of ChipGroup, we noticed that checking if ItemsPanelRoot == null might not be enough and we should also check that there are items in it.

Expected behavior

As long as a value is pushed into SelectedItem, the value should update and propagates

How to reproduce it (as minimally and precisely as possible)
This can be easily reproduced with simple bindings.
In a page define a chip group with  an ItemsSource and bind to a single property for selection :
<controls:ChipGroup x:Name="ChipGroup"
		                    Grid.Row="1"
		                    ItemsSource="{Binding SourceGroup}"
		                    SelectedItem="{Binding SelectedGroup}"
		                    SelectionMode="Single" />

In your VM define :

// Use a simple enum
public enum TestEnum
{
	KitKat,
	Oreo,
	Mars,
	Lion,
	Snickers
}

// Use any property to bind to a list of it

public TestEnum[] SourceGroup
{
    get => _sourceGroup;
    set
      {
	  _sourceGroup= value;
	  RaisePropertyChanged();
	}
}

public TestEnum SelectedGroup
{
	get => _selectedGroup;
	set
	{
		_selectedGroup= value;
		RaisePropertyChanged();
	 }
}

Environment

Nuget Package:
Package Version(s):
Affected platform(s):

[x] iOS
[x] Android
[ ] WebAssembly
[x] UWP
[ ] MacOS

Anything else we need to know?

Fix will be available with the next version that includes #628

authors: jeanplevesque vincentcastagna


text:
change in some natation

Here I ve changed some Boolean logic notation.
example : Or --> OR
And --> AND

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I don't think the proposed changes are actionable enough to merge.

authors: CLAassistant ghuntley gods-mack

repo: unoplatform/calculator


text:
Suggestion: Create an "inclusive" filter for AD Groups Allowed to Change Password

Is your feature request related to a problem? Please describe.
No Problem - Just an idea
Describe the solution you'd like
This would be similar to the "CheckRestrictedAdGroups" functionality, but would only allow users who are members of the listed group(s) to change their password (instead of allowing EVERYONE to change passwords except the restricted groups).
Describe alternatives you've considered
This is doable with "CheckRestrictedAdGroups" but would be cumbersome to maintain.
Additional context
I think this would be useful for situations where a smaller group is a tenant in a given domain and the domain admins don't want to open the entire domain up to user password changes via this app.

@iamperson347 tomorrow we are going to publish the new version, you can now add allowed ad groups as a configuration on the appsettings.json file

Awesome! Thanks everyone - I look forward to trying it out.

Remember, please star this project if you find it useful! ⭐

repo: unosquare/passcore


text:
[Bug]: Sidebar Mobile

Reproduction
N/A
Describe the bug
there are two mobile fixes i did in my own src but
https://github.com/unovue/shadcn-vue/blob/52b9b20b3c128287c81e7c83757494a5c6531275/apps/www/src/lib/registry/default/ui/sidebar/SidebarProvider.vue#L21
const isMobile = useMediaQuery("(max-width: 768px)");

and
https://github.com/unovue/shadcn-vue/blob/52b9b20b3c128287c81e7c83757494a5c6531275/apps/www/src/lib/registry/default/ui/sidebar/SidebarProvider.vue#L42
function toggleSidebar() {
  return isMobile.value
    ? setOpenMobile(!openMobile.value)
    : setOpen(!open.value);
}

System Info
N/A

Contributes

[ ] I am willing to submit a PR to fix this issue
[ ] I am willing to submit a PR with failing tests

I wasn't sure how you wanted either of them actually done, so figured id just submit this

This is great. I also noticed the menu slides in from the right, which feels wrong. So I updated side="left" in Sidebar.vue
<SheetContent
      data-sidebar="sidebar"
      data-mobile="true"
      side="left"
      class="w-[--sidebar-width] bg-sidebar p-0 text-sidebar-foreground [&>button]:hidden"
      :style="{
        '--sidebar-width': SIDEBAR_WIDTH_MOBILE,
      }"
    >
    ```

I also had to remove the bg-sidebar class from the  tag, as it was overlaying the menu.
Is it worth wrapping up these mobile fixes into a PR?

@glennjacobs did you add the extends classes to the config ?

@glennjacobs did you add the extends classes to the config ?

Ah good point. I added those in (as below), but I still have the same issue. I also just noticed I don't have the mouseover styles, I must have done something wrong...
        sidebar: {
          'DEFAULT': 'hsl(var(--sidebar-background))',
          'foreground': 'hsl(var(--sidebar-foreground))',
          'primary': 'hsl(var(--sidebar-primary))',
          'primary-foreground': 'hsl(var(--sidebar-primary-foreground))',
          'accent': 'hsl(var(--sidebar-accent))',
          'accent-foreground': 'hsl(var(--sidebar-accent-foreground))',
          'border': 'hsl(var(--sidebar-border))',
          'ring': 'hsl(var(--sidebar-ring))',
        },
        ```

Ah! I was missing the CSS variables from my app.css.
So the class does NOT need to be removed as you expected.

@glennjacobs did you add the extends classes to the config ?

Ah good point. I added those in (as below), but I still have the same issue. I also just noticed I don't have the mouseover styles, I must have done something wrong...
        sidebar: {
          'DEFAULT': 'hsl(var(--sidebar-background))',
          'foreground': 'hsl(var(--sidebar-foreground))',
          'primary': 'hsl(var(--sidebar-primary))',
          'primary-foreground': 'hsl(var(--sidebar-primary-foreground))',
          'accent': 'hsl(var(--sidebar-accent))',
          'accent-foreground': 'hsl(var(--sidebar-accent-foreground))',
          'border': 'hsl(var(--sidebar-border))',
          'ring': 'hsl(var(--sidebar-ring))',
        },
        ```

Hello, I am new to chadcn-ui and vue. Where those properties should be in ?
Thanks for your help

@glennjacobs did you add the extends classes to the config ?您是否将扩展类添加到配置中？

Ah good point. I added those in (as below), but I still have the same issue. I also just noticed I don't have the mouseover styles, I must have done something wrong...啊，好点。我添加了这些（如下），但我仍然有同样的问题。我还刚刚注意到我没有鼠标悬停样式，我一定做错了什么......
        sidebar: {
          'DEFAULT': 'hsl(var(--sidebar-background))',
          'foreground': 'hsl(var(--sidebar-foreground))',
          'primary': 'hsl(var(--sidebar-primary))',
          'primary-foreground': 'hsl(var(--sidebar-primary-foreground))',
          'accent': 'hsl(var(--sidebar-accent))',
          'accent-foreground': 'hsl(var(--sidebar-accent-foreground))',
          'border': 'hsl(var(--sidebar-border))',
          'ring': 'hsl(var(--sidebar-ring))',
        },
        ```

Hello, I am new to chadcn-ui and vue. Where those properties should be in ?你好，我是 chadcn-ui 和 vue 的新手。这些属性应该在哪里？ Thanks for your help 感谢您的帮助

theme.extend.colors in tailwind.config.js

I noticed there's a hydration problem too (check out the pic). Any ideas how to fix it?

I dont want to wrap sidebar in client component

This is great. I also noticed the menu slides in from the right, which feels wrong. So I updated side="left" in Sidebar.vue这太棒了。我还注意到菜单是从右侧滑入的，这感觉不对。所以我在 Sidebar.vue 中更新了side="left"
<SheetContent
      data-sidebar="sidebar"
      data-mobile="true"
      side="left"
      class="w-[--sidebar-width] bg-sidebar p-0 text-sidebar-foreground [&>button]:hidden"
      :style="{
        '--sidebar-width': SIDEBAR_WIDTH_MOBILE,
      }"
    >
    ```

Can use side prop, change it:
<SheetContent
      data-sidebar="sidebar"
      data-mobile="true"
      :side="side"
      class="w-[--sidebar-width] bg-sidebar p-0 text-sidebar-foreground [&>button]:hidden"
      :style="{
        '--sidebar-width': SIDEBAR_WIDTH_MOBILE,
      }"
    >

@lukepolo thank you, you save my time

I'm searching and searching. What are the variables in this case, I cannot find them anywhere. I have default style and natural as a baseColor.

I'm searching and searching. What are the variables in this case, I cannot find them anywhere. I have default style and natural as a baseColor.

What integration are you using?
I think the issue is the installer and the theme picker don't have these CSS variables included currently.

Its Vite in my case. There is a ./assets/index.css file which I customized a bit. Maybe that's why during the installation of the Sidebar (VSC Plugin) it wasn't changed?

@Nagell this is what I have in my Laravel install
@tailwind base;
@tailwind components;
@tailwind utilities;

@layer base {
    :root {
        --background: 0 0% 100%;
        --foreground: 240 10% 3.9%;

        --card: 0 0% 100%;
        --card-foreground: 240 10% 3.9%;

        --popover: 0 0% 100%;
        --popover-foreground: 240 10% 3.9%;

        --primary: 240 5.9% 10%;
        --primary-foreground: 0 0% 98%;

        --secondary: 240 4.8% 95.9%;
        --secondary-foreground: 240 5.9% 10%;

        --muted: 240 4.8% 95.9%;
        --muted-foreground: 240 3.8% 46.1%;

        --accent: 240 4.8% 95.9%;
        --accent-foreground: 240 5.9% 10%;

        --destructive: 0 84.2% 60.2%;
        --destructive-foreground: 0 0% 98%;

        --border:240 5.9% 90%;
        --input:240 5.9% 90%;
        --ring:240 5.9% 10%;
        --radius: 0.5rem;

        --sidebar-background: 0 0% 98%;
        --sidebar-foreground: 240 5.3% 26.1%;
        --sidebar-primary: 240 5.9% 10%;
        --sidebar-primary-foreground: 0 0% 98%;
        --sidebar-accent: 240 4.8% 95.9%;
        --sidebar-accent-foreground: 240 5.9% 10%;
        --sidebar-border: 220 13% 91%;
        --sidebar-ring: 217.2 91.2% 59.8%;
    }

    .dark {
        --background: 222.2 84% 4.9%;
        --foreground: 210 40% 98%;

        --muted: 217.2 32.6% 17.5%;
        --muted-foreground: 215 20.2% 65.1%;

        --popover: 222.2 84% 4.9%;
        --popover-foreground: 210 40% 98%;

        --card: 222.2 84% 4.9%;
        --card-foreground: 210 40% 98%;

        --border: 217.2 32.6% 17.5%;
        --input: 217.2 32.6% 17.5%;

        --primary: 210 40% 98%;
        --primary-foreground: 222.2 47.4% 11.2%;

        --secondary: 217.2 32.6% 17.5%;
        --secondary-foreground: 210 40% 98%;

        --accent: 217.2 32.6% 17.5%;
        --accent-foreground: 210 40% 98%;

        --destructive: 0 62.8% 30.6%;
        --destructive-foreground: 210 40% 98%;

        --ring: 212.7 26.8% 83.9%;

        --sidebar-background: 222.2 84% 4.9%;
        --sidebar-foreground: 210 40% 98%;
        --sidebar-primary: 210 40% 98%;
        --sidebar-primary-foreground: 222.2 47.4% 11.2%;
        --sidebar-accent: 217.2 32.6% 17.5%;
        --sidebar-accent-foreground: 210 40% 98%;
        --sidebar-border: 217.2 32.6% 17.5%;
        --sidebar-ring: 212.7 26.8% 83.9%;
    }
}

@layer base {
    * {
        @apply border-border;
    }

    body {
        @apply bg-background text-foreground;
    }
}

Some of the dark mode colours are custom however.

This explains a lot :D Thank you @glennjacobs!

In version 0.11.3, the ‘useMediaQuery’ import must be added manually：
import { useEventListener, useVModel, useMediaQuery } from "@vueuse/core";
const isMobile = useMediaQuery("(max-width: 768px)");

In version 0.11.3, the ‘useMediaQuery’ import must be added manually.
import { useEventListener, useVModel, useMediaQuery } from "@vueuse/core";
const isMobile = useMediaQuery("(max-width: 768px)");

authors: Curtion Grzechu335 Nagell Whbbit1999 acrossoffwest glennjacobs hujix jo-pouradier lukepolo

repo: unovue/shadcn-vue