Crash report, work phantomjs 1.9.0 with webserver

Phantomjs often falls off, is that without crash report. Simply ceases to be executed. Use the original assembly.
Operating system: Linux
0.0.0 Linux 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64
CPU: amd64
family 6 model 26 stepping 5
4 CPUs
Crash reason:  SIGABRT
Crash address: 0xace
Thread 0 (crashed)
0  libc-2.15.so + 0x36425
rbx = 0x0000000004f32000   r12 = 0x0000000005111eb0
r13 = 0x0000000004f31fd0   r14 = 0x0000000004b3fdf0
r15 = 0x0000000004ed9390   rip = 0x00007f247d937425
rsp = 0x00007fffaa03e8b8   rbp = 0x0000000004f32018
Found by: given as instruction pointer in context
1  libc-2.15.so + 0x39b8a
rip = 0x00007f247d93ab8b   rsp = 0x00007fffaa03e8c0
Found by: stack scanning
2  libc-2.15.so + 0x6c47
rip = 0x00007f247d907c48   rsp = 0x00007fffaa03e8d8
Found by: stack scanning
3  phantomjs + 0x1e2a8cb
rip = 0x000000000222a8cc   rsp = 0x00007fffaa03e8e8
Found by: stack scanning
4  libm-2.15.so + 0x2fbfff
rip = 0x00007f247e1d2000   rsp = 0x00007fffaa03e948
Found by: stack scanning
5  ld-2.15.so + 0xe783
rip = 0x00007f247efe2784   rsp = 0x00007fffaa03e950
Found by: stack scanning
6  libstdc++.so.6.0.17 + 0x60e2c
rip = 0x00007f247e232e2d   rsp = 0x00007fffaa03e9f0
Found by: stack scanning
7  libpthread-2.15.so + 0xeccc
rip = 0x00007f247e4e3ccd   rsp = 0x00007fffaa03ea00
Found by: stack scanning
8  libstdc++.so.6.0.17 + 0x5ef25
rip = 0x00007f247e230f26   rsp = 0x00007fffaa03ea20
Found by: stack scanning
9  libstdc++.so.6.0.17 + 0x5ef52
rip = 0x00007f247e230f53   rsp = 0x00007fffaa03ea30
Found by: stack scanning
10  libstdc++.so.6.0.17 + 0x5fa6e
rip = 0x00007f247e231a6f   rsp = 0x00007fffaa03ea40
Found by: stack scanning
11  phantomjs + 0x18d57eb
rip = 0x0000000001cd57ec   rsp = 0x00007fffaa03ea50
Found by: stack scanning
12  libc-2.15.so + 0x82fb4
rip = 0x00007f247d983fb5   rsp = 0x00007fffaa03eab0
Found by: stack scanning
13  phantomjs + 0x18e62fc
rip = 0x0000000001ce62fd   rsp = 0x00007fffaa03eac0
Found by: stack scanning
14  phantomjs + 0x18ed998
rip = 0x0000000001ced999   rsp = 0x00007fffaa03eb00
Found by: stack scanning
Thread 1
0  libc-2.15.so + 0xbf83d
rbx = 0x00007f247cc16cf0   r12 = 0x0000000002acafe0
r13 = 0x00007f247f1db530   r14 = 0x0000000002ad3680
r15 = 0x0000000002ad3650   rip = 0x00007f247d9c083d
rsp = 0x00007f247cc16c40   rbp = 0x00000000ffffffff
Found by: given as instruction pointer in context
1  libc-2.15.so + 0xbf6db
rip = 0x00007f247d9c06dc   rsp = 0x00007f247cc16c50
Found by: stack scanning
2  phantomjs + 0x18ac86f
rip = 0x0000000001cac870   rsp = 0x00007f247cc16c58
Found by: stack scanning
3  phantomjs + 0x2e2c
rip = 0x0000000000402e2d   rsp = 0x00007f247cc16c68
Found by: stack scanning
4  libc-2.15.so + 0x109f7
rip = 0x00007f247d9119f8   rsp = 0x00007f247cc16c70
Found by: stack scanning
5  phantomjs + 0x24c7
rip = 0x00000000004024c8   rsp = 0x00007f247cc16c78
Found by: stack scanning
6  ld-2.15.so + 0xa532
rip = 0x00007f247efde533   rsp = 0x00007f247cc16cc8
Found by: stack scanning
7  libc-2.15.so + 0xbf848
rip = 0x00007f247d9c0849   rsp = 0x00007f247cc16cd8
Found by: stack scanning
8  libpthread-2.15.so + 0xfcaf
rip = 0x00007f247e4e4cb0   rsp = 0x00007f247cc16ce8
Found by: stack scanning
9  libpthread-2.15.so + 0xb103
rip = 0x00007f247e4e0104   rsp = 0x00007f247cc16d90
Found by: stack scanning
10  libc-2.15.so + 0xe54f
rip = 0x00007f247d90f550   rsp = 0x00007f247cc16d98
Found by: stack scanning
11  ld-2.15.so + 0x15244
rip = 0x00007f247efe9245   rsp = 0x00007f247cc16dd0
Found by: stack scanning
12  libpthread-2.15.so + 0xe9f9
rip = 0x00007f247e4e39fa   rsp = 0x00007f247cc16de0
Found by: stack scanning
13  libpthread-2.15.so + 0xbe17
rip = 0x00007f247e4e0e18   rsp = 0x00007f247cc16df0
Found by: stack scanning
14  phantomjs + 0xd4ded
rip = 0x00000000004d4dee   rsp = 0x00007f247cc16e20
Found by: stack scanning
15  libc-2.15.so + 0x977f
rip = 0x00007f247d90a780   rsp = 0x00007f247cc16e28
Found by: stack scanning
16  libpthread-2.15.so + 0x1187f
rip = 0x00007f247e4e6880   rsp = 0x00007f247cc16e50
Found by: stack scanning
17  libpthread-2.15.so + 0x1187f
rip = 0x00007f247e4e6880   rsp = 0x00007f247cc16e80
Found by: stack scanning
18  phantomjs + 0xd5058
rip = 0x00000000004d5059   rsp = 0x00007f247cc16ea0
Found by: stack scanning
19  libpthread-2.15.so + 0x7e99
rip = 0x00007f247e4dce9a   rsp = 0x00007f247cc16eb0
Found by: stack scanning
20  libpthread-2.15.so + 0x1187f
rip = 0x00007f247e4e6880   rsp = 0x00007f247cc16f58
Found by: stack scanning
21  libc-2.15.so + 0xf3cbc
rip = 0x00007f247d9f4cbd   rsp = 0x00007f247cc16fc0
Found by: stack scanning
Thread 2
0  libc-2.15.so + 0xed023
rbx = 0x0000000000000000   r12 = 0x00007f247c415d80
r13 = 0x0000000000000008   r14 = 0x00007f2474000a98
r15 = 0x00007f2474000d30   rip = 0x00007f247d9ee023
rsp = 0x00007f247c415b50   rbp = 0x00007f24740008e0
Found by: given as instruction pointer in context
1  phantomjs + 0x18fcf26
rip = 0x0000000001cfcf27   rsp = 0x00007f247c415b60
Found by: stack scanning
2  ld-2.15.so + 0xa2ad
rip = 0x00007f247efde2ae   rsp = 0x00007f247c415ba0
Found by: stack scanning
3  phantomjs + 0x18fe1e6
rip = 0x0000000001cfe1e7   rsp = 0x00007f247c415bf0
Found by: stack scanning
4  phantomjs + 0x18ed6b6
rip = 0x0000000001ced6b7   rsp = 0x00007f247c415c10
Found by: stack scanning
5  phantomjs + 0x17f85c2
rip = 0x0000000001bf85c3   rsp = 0x00007f247c415c20
Found by: stack scanning
6  linux-gate.so + 0x89b
rip = 0x00007fffaa0dc89c   rsp = 0x00007f247c415c30
Found by: stack scanning
7  librt-2.15.so + 0x415c
rip = 0x00007f247e6f615d   rsp = 0x00007f247c415c60
Found by: stack scanning
8  phantomjs + 0x1837773
rip = 0x0000000001c37774   rsp = 0x00007f247c415c70
Found by: stack scanning
9  phantomjs + 0x1837678
rip = 0x0000000001c37679   rsp = 0x00007f247c415cb0
Found by: stack scanning
10  phantomjs + 0x18fdba5
rip = 0x0000000001cfdba6   rsp = 0x00007f247c415cc0
Found by: stack scanning
11  phantomjs + 0x18fec91
rip = 0x0000000001cfec92   rsp = 0x00007f247c415d30
Found by: stack scanning
12  phantomjs + 0x18d40b4
rip = 0x0000000001cd40b5   rsp = 0x00007f247c415d80
Found by: stack scanning
13  phantomjs + 0x18d48a8
rip = 0x0000000001cd48a9   rsp = 0x00007f247c415d90
Found by: stack scanning
14  phantomjs + 0x18d4517
rip = 0x0000000001cd4518   rsp = 0x00007f247c415db0
Found by: stack scanning
15  phantomjs + 0x17d69f5
rip = 0x0000000001bd69f6   rsp = 0x00007f247c415e10
Found by: stack scanning
16  phantomjs + 0x17d98c1
rip = 0x0000000001bd98c2   rsp = 0x00007f247c415e60
Found by: stack scanning
17  libpthread-2.15.so + 0x7e99
rip = 0x00007f247e4dce9a   rsp = 0x00007f247c415eb0
Found by: stack scanning
Thread 3
0  libc-2.15.so + 0xed023
rbx = 0x0000000000000200   r12 = 0x000000000336ab80
r13 = 0x000000000336ac60   r14 = 0x000000000336b1f0
r15 = 0x00007f247abaeda0   rip = 0x00007f247d9ee023
rsp = 0x00007f247abaed80   rbp = 0x0000000000000000
Found by: given as instruction pointer in context
1  phantomjs + 0x51995
rip = 0x0000000000451996   rsp = 0x00007f247abaed90
Found by: stack scanning
2  phantomjs + 0xc0007e
rip = 0x000000000100007f   rsp = 0x00007f247abaee50
Found by: stack scanning
3  libpthread-2.15.so + 0x7e99
rip = 0x00007f247e4dce9a   rsp = 0x00007f247abaeeb0
Found by: stack scanning
Thread 4
0  libpthread-2.15.so + 0xbd84
rbx = 0x000000000336b1c0   r12 = 0x00007f242c0008c8
r13 = 0x000000000336ab80   r14 = 0x0000000000000000
r15 = 0x000000000336ac60   rip = 0x00007f247e4e0d84
rsp = 0x00007f247a3ab9f0   rbp = 0x00007f242c0008c0
Found by: given as instruction pointer in context
1  phantomjs + 0x51f37
rip = 0x0000000000451f38   rsp = 0x00007f247a3aba20
Found by: stack scanning
Thread 5
0  libpthread-2.15.so + 0xbd84
rbx = 0x00007f23f4005d30   r12 = 0x004189374bc6a7ef
r13 = 0xffffffffffffffff   r14 = 0x00007f23f4005d58
r15 = 0x00007f23f4005380   rip = 0x00007f247e4e0d84
rsp = 0x00007f2479ba6fe0   rbp = 0x00007f23f4005380
Found by: given as instruction pointer in context
1  phantomjs + 0x17da5f4
rip = 0x0000000001bda5f5   rsp = 0x00007f2479ba7010
Found by: stack scanning
2  phantomjs + 0x17d572c
rip = 0x0000000001bd572d   rsp = 0x00007f2479ba7090
Found by: stack scanning
3  phantomjs + 0x251fb
rip = 0x00000000004251fc   rsp = 0x00007f2479ba70c0
Found by: stack scanning
4  phantomjs + 0x1958203
rip = 0x0000000001d58204   rsp = 0x00007f2479ba70c8
Found by: stack scanning
5  phantomjs + 0x195da2f
rip = 0x0000000001d5da30   rsp = 0x00007f2479ba7158
Found by: stack scanning
Thread 6
0  libpthread-2.15.so + 0xbd84
rbx = 0x000000000336b1c0   r12 = 0x00007f24140008c8
r13 = 0x000000000336ab80   r14 = 0x0000000000000000
r15 = 0x000000000336ac60   rip = 0x00007f247e4e0d84
rsp = 0x00007f24793a99f0   rbp = 0x00007f24140008c0
Found by: given as instruction pointer in context
1  phantomjs + 0x51f37
rip = 0x0000000000451f38   rsp = 0x00007f24793a9a20
Found by: stack scanning
Thread 7
0  libpthread-2.15.so + 0xbd84
rbx = 0x00007f2404006360   r12 = 0x004189374bc6a7ef
r13 = 0xffffffffffffffff   r14 = 0x00007f2404006388
r15 = 0x00007f2404005330   rip = 0x00007f247e4e0d84
rsp = 0x00007f2478ba4fe0   rbp = 0x00007f2404005330
Found by: given as instruction pointer in context
1  phantomjs + 0x17da5f4
rip = 0x0000000001bda5f5   rsp = 0x00007f2478ba5010
Found by: stack scanning
2  phantomjs + 0x17d572c
rip = 0x0000000001bd572d   rsp = 0x00007f2478ba5090
Found by: stack scanning
3  phantomjs + 0x251fb
rip = 0x00000000004251fc   rsp = 0x00007f2478ba50c0
Found by: stack scanning
4  phantomjs + 0x19582f6
rip = 0x0000000001d582f7   rsp = 0x00007f2478ba50c8
Found by: stack scanning
5  phantomjs + 0x195da2f
rip = 0x0000000001d5da30   rsp = 0x00007f2478ba5158
Found by: stack scanning
Thread 8
0  libpthread-2.15.so + 0xbd84
rbx = 0x00007f241c006380   r12 = 0x004189374bc6a7ef
r13 = 0xffffffffffffffff   r14 = 0x00007f241c0063a8
r15 = 0x00007f241c006190   rip = 0x00007f247e4e0d84
rsp = 0x00007f2433ff8fe0   rbp = 0x00007f241c006190
Found by: given as instruction pointer in context
1  phantomjs + 0x17da5f4
rip = 0x0000000001bda5f5   rsp = 0x00007f2433ff9010
Found by: stack scanning
2  phantomjs + 0x17d572c
rip = 0x0000000001bd572d   rsp = 0x00007f2433ff9090
Found by: stack scanning
3  phantomjs + 0x251fb
rip = 0x00000000004251fc   rsp = 0x00007f2433ff90c0
Found by: stack scanning
4  phantomjs + 0x1958203
rip = 0x0000000001d58204   rsp = 0x00007f2433ff90c8
Found by: stack scanning
5  phantomjs + 0x195da2f
rip = 0x0000000001d5da30   rsp = 0x00007f2433ff9158
Found by: stack scanning
Thread 9
0  libpthread-2.15.so + 0xbd84
rbx = 0x000000000336b1c0   r12 = 0x00007f23fc0008c8
r13 = 0x000000000336ab80   r14 = 0x0000000000000000
r15 = 0x000000000336ac60   rip = 0x00007f247e4e0d84
rsp = 0x00007f24337fb9f0   rbp = 0x00007f23fc0008c0
Found by: given as instruction pointer in context
1  phantomjs + 0x51f37
rip = 0x0000000000451f38   rsp = 0x00007f24337fba20
Found by: stack scanning
Thread 10
0  libpthread-2.15.so + 0xbd84
rbx = 0x000000000336b1c0   r12 = 0x00007f240c0008c8
r13 = 0x000000000336ab80   r14 = 0x0000000000000000
r15 = 0x000000000336ac60   rip = 0x00007f247e4e0d84
rsp = 0x00007f2432ffa9f0   rbp = 0x00007f240c0008c0
Found by: given as instruction pointer in context
1  phantomjs + 0x51f37
rip = 0x0000000000451f38   rsp = 0x00007f2432ffaa20
Found by: stack scanning
Thread 11
0  libpthread-2.15.so + 0xbd84
rbx = 0x000000000336b1c0   r12 = 0x00007f24240008c8
r13 = 0x000000000336ab80   r14 = 0x0000000000000000
r15 = 0x000000000336ac60   rip = 0x00007f247e4e0d84
rsp = 0x00007f24327f99f0   rbp = 0x00007f24240008c0
Found by: given as instruction pointer in context
1  phantomjs + 0x51f37
rip = 0x0000000000451f38   rsp = 0x00007f24327f9a20
Found by: stack scanning
Thread 12
0  libpthread-2.15.so + 0xbd84
rbx = 0x00007f23ec005950   r12 = 0x004189374bc6a7ef
r13 = 0xffffffffffffffff   r14 = 0x00007f23ec005978
r15 = 0x00007f23ec005be0   rip = 0x00007f247e4e0d84
rsp = 0x00007f2431ff4fe0   rbp = 0x00007f23ec005be0
Found by: given as instruction pointer in context
1  phantomjs + 0x17da5f4
rip = 0x0000000001bda5f5   rsp = 0x00007f2431ff5010
Found by: stack scanning
2  phantomjs + 0x17d572c
rip = 0x0000000001bd572d   rsp = 0x00007f2431ff5090
Found by: stack scanning
3  phantomjs + 0x251fb
rip = 0x00000000004251fc   rsp = 0x00007f2431ff50c0
Found by: stack scanning
4  phantomjs + 0x1958203
rip = 0x0000000001d58204   rsp = 0x00007f2431ff50c8
Found by: stack scanning
5  phantomjs + 0x195da2f
rip = 0x0000000001d5da30   rsp = 0x00007f2431ff5158
Found by: stack scanning
Thread 13
0  libpthread-2.15.so + 0xbd84
rbx = 0x000000000336b1c0   r12 = 0x00007f23f00008c8
r13 = 0x000000000336ab80   r14 = 0x0000000000000000
r15 = 0x000000000336ac60   rip = 0x00007f247e4e0d84
rsp = 0x00007f24317f79f0   rbp = 0x00007f23f00008c0
Found by: given as instruction pointer in context
1  phantomjs + 0x51f37
rip = 0x0000000000451f38   rsp = 0x00007f24317f7a20
Found by: stack scanning
Thread 14
0  libpthread-2.15.so + 0xbd84
rbx = 0x0000000003800480   r12 = 0x004189374bc6a7ef
r13 = 0xffffffffffffffff   r14 = 0x00000000038004a8
r15 = 0x0000000003aa1360   rip = 0x00007f247e4e0d84
rsp = 0x00007f242b455d10   rbp = 0x00007f2428ab1d50
Found by: given as instruction pointer in context
1  phantomjs + 0x17da5f4
rip = 0x0000000001bda5f5   rsp = 0x00007f242b455d40
Found by: stack scanning
2  linux-gate.so + 0x9f4
rip = 0x00007fffaa0dc9f5   rsp = 0x00007f242b455d70
Found by: stack scanning
3  phantomjs + 0xde4a9
rip = 0x00000000004de4aa   rsp = 0x00007f242b455dc0
Found by: stack scanning
4  phantomjs + 0xd7bbe8
rip = 0x000000000117bbe9   rsp = 0x00007f242b455de0
Found by: stack scanning
5  phantomjs + 0xd7be12
rip = 0x000000000117be13   rsp = 0x00007f242b455e20
Found by: stack scanning
6  phantomjs + 0xddcba
rip = 0x00000000004ddcbb   rsp = 0x00007f242b455e50
Found by: stack scanning
7  phantomjs + 0x17d98c1
rip = 0x0000000001bd98c2   rsp = 0x00007f242b455e60
Found by: stack scanning
8  libpthread-2.15.so + 0x7c82
rip = 0x00007f247e4dcc83   rsp = 0x00007f242b455e70
Found by: stack scanning
9  libc-2.15.so + 0x3b4817
rip = 0x00007f247dcb5818   rsp = 0x00007f242b455e78
Found by: stack scanning
10  libc-2.15.so + 0x3b4827
rip = 0x00007f247dcb5828   rsp = 0x00007f242b455e80
Found by: stack scanning
11  libc-2.15.so + 0x3b482f
rip = 0x00007f247dcb5830   rsp = 0x00007f242b455e88
Found by: stack scanning
12  libpthread-2.15.so + 0x7e99
rip = 0x00007f247e4dce9a   rsp = 0x00007f242b455eb0
Found by: stack scanning
Thread 15
0  libpthread-2.15.so + 0xc0fe
rbx = 0x00007f23e4005420   r12 = 0x000000000000001f
r13 = 0x00007f2429f9cdc0   r14 = 0xffffffffffffff92
r15 = 0x0000000000000000   rip = 0x00007f247e4e10fe
rsp = 0x00007f2429f9cd40   rbp = 0x00007f23e40056f0
Found by: given as instruction pointer in context
1  linux-gate.so + 0x9f4
rip = 0x00007fffaa0dc9f5   rsp = 0x00007f2429f9cd70
Found by: stack scanning
2  phantomjs + 0x17da5d6
rip = 0x0000000001bda5d7   rsp = 0x00007f2429f9cda0
Found by: stack scanning
3  phantomjs + 0x17ce43c
rip = 0x0000000001bce43d   rsp = 0x00007f2429f9ce20
Found by: stack scanning
4  phantomjs + 0x17d98c1
rip = 0x0000000001bd98c2   rsp = 0x00007f2429f9ce60
Found by: stack scanning
5  libpthread-2.15.so + 0x7c82
rip = 0x00007f247e4dcc83   rsp = 0x00007f2429f9ce70
Found by: stack scanning
6  libc-2.15.so + 0x3b4827
rip = 0x00007f247dcb5828   rsp = 0x00007f2429f9ce80
Found by: stack scanning
7  libc-2.15.so + 0x3b482f
rip = 0x00007f247dcb5830   rsp = 0x00007f2429f9ce88
Found by: stack scanning
8  libpthread-2.15.so + 0x7e99
rip = 0x00007f247e4dce9a   rsp = 0x00007f2429f9ceb0
Found by: stack scanning
Thread 16
0  libc-2.15.so + 0xed023
rbx = 0x0000000000000000   r12 = 0x00007f242bffed80
r13 = 0x000000000000001b   r14 = 0x00007f23e800a858
r15 = 0x00007f23e800aaf0   rip = 0x00007f247d9ee023
rsp = 0x00007f242bffeb50   rbp = 0x00007f23e800a6a0
Found by: given as instruction pointer in context
1  phantomjs + 0x18fcf26
rip = 0x0000000001cfcf27   rsp = 0x00007f242bffeb60
Found by: stack scanning
2  phantomjs + 0x55fefa
rip = 0x000000000095fefb   rsp = 0x00007f242bffeb90
Found by: stack scanning
3  libpthread-2.15.so + 0xed38
rip = 0x00007f247e4e3d39   rsp = 0x00007f242bffebb0
Found by: stack scanning
4  phantomjs + 0x18fe1e6
rip = 0x0000000001cfe1e7   rsp = 0x00007f242bffebf0
Found by: stack scanning
5  phantomjs + 0x18ed6b6
rip = 0x0000000001ced6b7   rsp = 0x00007f242bffec10
Found by: stack scanning
6  phantomjs + 0x17f85c2
rip = 0x0000000001bf85c3   rsp = 0x00007f242bffec20
Found by: stack scanning
7  linux-gate.so + 0x89b
rip = 0x00007fffaa0dc89c   rsp = 0x00007f242bffec30
Found by: stack scanning
8  librt-2.15.so + 0x415c
rip = 0x00007f247e6f615d   rsp = 0x00007f242bffec60
Found by: stack scanning
9  phantomjs + 0x1837773
rip = 0x0000000001c37774   rsp = 0x00007f242bffec70
Found by: stack scanning
10  phantomjs + 0x55fdf2
rip = 0x000000000095fdf3   rsp = 0x00007f242bffec90
Found by: stack scanning
11  phantomjs + 0x18fe8ed
rip = 0x0000000001cfe8ee   rsp = 0x00007f242bffeca0
Found by: stack scanning
12  phantomjs + 0x1837678
rip = 0x0000000001c37679   rsp = 0x00007f242bffecb0
Found by: stack scanning
13  phantomjs + 0x18fdba5
rip = 0x0000000001cfdba6   rsp = 0x00007f242bffecc0
Found by: stack scanning
14  phantomjs + 0x18fec91
rip = 0x0000000001cfec92   rsp = 0x00007f242bffed30
Found by: stack scanning
15  phantomjs + 0x18d40b4
rip = 0x0000000001cd40b5   rsp = 0x00007f242bffed80
Found by: stack scanning
16  phantomjs + 0x18d48a8
rip = 0x0000000001cd48a9   rsp = 0x00007f242bffed90
Found by: stack scanning
17  phantomjs + 0x18d4517
rip = 0x0000000001cd4518   rsp = 0x00007f242bffedb0
Found by: stack scanning
18  phantomjs + 0x17d69f5
rip = 0x0000000001bd69f6   rsp = 0x00007f242bffee10
Found by: stack scanning
19  phantomjs + 0x17d98c1
rip = 0x0000000001bd98c2   rsp = 0x00007f242bffee60
Found by: stack scanning
20  libpthread-2.15.so + 0x7c82
rip = 0x00007f247e4dcc83   rsp = 0x00007f242bffee70
Found by: stack scanning
21  libc-2.15.so + 0x3b4817
rip = 0x00007f247dcb5818   rsp = 0x00007f242bffee78
Found by: stack scanning
22  libc-2.15.so + 0x3b4827
rip = 0x00007f247dcb5828   rsp = 0x00007f242bffee80
Found by: stack scanning
23  libc-2.15.so + 0x3b482f
rip = 0x00007f247dcb5830   rsp = 0x00007f242bffee88
Found by: stack scanning
24  libpthread-2.15.so + 0x7e99
rip = 0x00007f247e4dce9a   rsp = 0x00007f242bffeeb0
Found by: stack scanning
Thread 17
0  libc-2.15.so + 0xed023
rbx = 0x00007f2423c49d30   r12 = 0x00000000001dcd8e
r13 = 0x0000000000000015   r14 = 0x00007f23e40263f8
r15 = 0x00007f23e4026690   rip = 0x00007f247d9ee023
rsp = 0x00007f2423c49b50   rbp = 0x0000000000005280
Found by: given as instruction pointer in context
1  phantomjs + 0x18fce27
rip = 0x0000000001cfce28   rsp = 0x00007f2423c49b60
Found by: stack scanning
2  phantomjs + 0x1024440
rip = 0x0000000001424441   rsp = 0x00007f2423c49b90
Found by: stack scanning
3  phantomjs + 0x18fe1e6
rip = 0x0000000001cfe1e7   rsp = 0x00007f2423c49bf0
Found by: stack scanning
4  phantomjs + 0x18ed6b6
rip = 0x0000000001ced6b7   rsp = 0x00007f2423c49c10
Found by: stack scanning
5  phantomjs + 0x17f85f3
rip = 0x0000000001bf85f4   rsp = 0x00007f2423c49c20
Found by: stack scanning
6  linux-gate.so + 0x89b
rip = 0x00007fffaa0dc89c   rsp = 0x00007f2423c49c30
Found by: stack scanning
7  librt-2.15.so + 0x415c
rip = 0x00007f247e6f615d   rsp = 0x00007f2423c49c60
Found by: stack scanning
8  phantomjs + 0x1837773
rip = 0x0000000001c37774   rsp = 0x00007f2423c49c70
Found by: stack scanning
9  phantomjs + 0x102437b
rip = 0x000000000142437c   rsp = 0x00007f2423c49c90
Found by: stack scanning
10  phantomjs + 0x18fe8ed
rip = 0x0000000001cfe8ee   rsp = 0x00007f2423c49ca0
Found by: stack scanning
11  phantomjs + 0x1837678
rip = 0x0000000001c37679   rsp = 0x00007f2423c49cb0
Found by: stack scanning
12  phantomjs + 0x18fdba5
rip = 0x0000000001cfdba6   rsp = 0x00007f2423c49cc0
Found by: stack scanning
13  phantomjs + 0x18fec91
rip = 0x0000000001cfec92   rsp = 0x00007f2423c49d30
Found by: stack scanning
14  phantomjs + 0x18d40b4
rip = 0x0000000001cd40b5   rsp = 0x00007f2423c49d80
Found by: stack scanning
15  phantomjs + 0x18d48a8
rip = 0x0000000001cd48a9   rsp = 0x00007f2423c49d90
Found by: stack scanning
16  phantomjs + 0x18d4517
rip = 0x0000000001cd4518   rsp = 0x00007f2423c49db0
Found by: stack scanning
17  phantomjs + 0x17d69f5
rip = 0x0000000001bd69f6   rsp = 0x00007f2423c49e10
Found by: stack scanning
18  phantomjs + 0x17d98c1
rip = 0x0000000001bd98c2   rsp = 0x00007f2423c49e60
Found by: stack scanning
19  libpthread-2.15.so + 0x7c82
rip = 0x00007f247e4dcc83   rsp = 0x00007f2423c49e70
Found by: stack scanning
20  libc-2.15.so + 0x3b4817
rip = 0x00007f247dcb5818   rsp = 0x00007f2423c49e78
Found by: stack scanning
21  libc-2.15.so + 0x3b4827
rip = 0x00007f247dcb5828   rsp = 0x00007f2423c49e80
Found by: stack scanning
22  libc-2.15.so + 0x3b482f
rip = 0x00007f247dcb5830   rsp = 0x00007f2423c49e88
Found by: stack scanning
23  libpthread-2.15.so + 0x7e99
rip = 0x00007f247e4dce9a   rsp = 0x00007f2423c49eb0
Found by: stack scanning
Thread 18
0  libc-2.15.so + 0xed023
rbx = 0x00007f2429403d30   r12 = 0x00000000001dcd8e
r13 = 0x0000000000000018   r14 = 0x00007f23d4007b78
r15 = 0x00007f23d4007e10   rip = 0x00007f247d9ee023
rsp = 0x00007f2429403b50   rbp = 0x00000000000278ca
Found by: given as instruction pointer in context
1  phantomjs + 0x18fce27
rip = 0x0000000001cfce28   rsp = 0x00007f2429403b60
Found by: stack scanning
2  phantomjs + 0x18fe1e6
rip = 0x0000000001cfe1e7   rsp = 0x00007f2429403bf0
Found by: stack scanning
3  phantomjs + 0x18ed6b6
rip = 0x0000000001ced6b7   rsp = 0x00007f2429403c10
Found by: stack scanning
4  phantomjs + 0x17f85f3
rip = 0x0000000001bf85f4   rsp = 0x00007f2429403c20
Found by: stack scanning
5  linux-gate.so + 0x89b
rip = 0x00007fffaa0dc89c   rsp = 0x00007f2429403c30
Found by: stack scanning
6  librt-2.15.so + 0x415c
rip = 0x00007f247e6f615d   rsp = 0x00007f2429403c60
Found by: stack scanning
7  phantomjs + 0x1837773
rip = 0x0000000001c37774   rsp = 0x00007f2429403c70
Found by: stack scanning
8  phantomjs + 0x18fe8ed
rip = 0x0000000001cfe8ee   rsp = 0x00007f2429403ca0
Found by: stack scanning
9  phantomjs + 0x1837678
rip = 0x0000000001c37679   rsp = 0x00007f2429403cb0
Found by: stack scanning
10  phantomjs + 0x18fdba5
rip = 0x0000000001cfdba6   rsp = 0x00007f2429403cc0
Found by: stack scanning
11  phantomjs + 0x18fec91
rip = 0x0000000001cfec92   rsp = 0x00007f2429403d30
Found by: stack scanning
12  phantomjs + 0x18d40b4
rip = 0x0000000001cd40b5   rsp = 0x00007f2429403d80
Found by: stack scanning
13  phantomjs + 0x18d48a8
rip = 0x0000000001cd48a9   rsp = 0x00007f2429403d90
Found by: stack scanning
14  phantomjs + 0x18d4517
rip = 0x0000000001cd4518   rsp = 0x00007f2429403db0
Found by: stack scanning
15  phantomjs + 0x17d69f5
rip = 0x0000000001bd69f6   rsp = 0x00007f2429403e10
Found by: stack scanning
16  phantomjs + 0x17d98c1
rip = 0x0000000001bd98c2   rsp = 0x00007f2429403e60
Found by: stack scanning
17  libpthread-2.15.so + 0x7c82
rip = 0x00007f247e4dcc83   rsp = 0x00007f2429403e70
Found by: stack scanning
18  libc-2.15.so + 0x3b4817
rip = 0x00007f247dcb5818   rsp = 0x00007f2429403e78
Found by: stack scanning
19  libc-2.15.so + 0x3b4827
rip = 0x00007f247dcb5828   rsp = 0x00007f2429403e80
Found by: stack scanning
20  libc-2.15.so + 0x3b482f
rip = 0x00007f247dcb5830   rsp = 0x00007f2429403e88
Found by: stack scanning
21  libpthread-2.15.so + 0x7e99
rip = 0x00007f247e4dce9a   rsp = 0x00007f2429403eb0
Found by: stack scanning
Thread 19
0  libc-2.15.so + 0xefed9
rbx = 0x00007f23e4009630   r12 = 0xfffffffffff0bdc0
r13 = 0x00007f23d8006f30   r14 = 0x0000000000000002
r15 = 0x00007f23d8002e80   rip = 0x00007f247d9f0ed9
rsp = 0x00007f2422f8d5b8   rbp = 0x0000000000000000
Found by: given as instruction pointer in context
1  phantomjs + 0x17d8a02
rip = 0x0000000001bd8a03   rsp = 0x00007f2422f8d5c0
Found by: stack scanning
2  librt-2.15.so + 0x415c
rip = 0x00007f247e6f615d   rsp = 0x00007f2422f8d5d0
Found by: stack scanning
3  phantomjs + 0x18377f5
rip = 0x0000000001c377f6   rsp = 0x00007f2422f8d5e0
Found by: stack scanning
4  phantomjs + 0x17d487c
rip = 0x0000000001bd487d   rsp = 0x00007f2422f8d610
Found by: stack scanning
5  phantomjs + 0x18eb9be
rip = 0x0000000001ceb9bf   rsp = 0x00007f2422f8d690
Found by: stack scanning
6  phantomjs + 0x1774d8f
rip = 0x0000000001b74d90   rsp = 0x00007f2422f8d6a8
Found by: stack scanning
7  phantomjs + 0x1d9e26b
rip = 0x000000000219e26c   rsp = 0x00007f2422f8d6d0
Found by: stack scanning
8  phantomjs + 0x18ec983
rip = 0x0000000001cec984   rsp = 0x00007f2422f8d6e0
Found by: stack scanning
9  phantomjs + 0x1956014
rip = 0x0000000001d56015   rsp = 0x00007f2422f8d710
Found by: stack scanning
10  phantomjs + 0x18d4fd3
rip = 0x0000000001cd4fd4   rsp = 0x00007f2422f8d720
Found by: stack scanning
11  phantomjs + 0x1956013
rip = 0x0000000001d56014   rsp = 0x00007f2422f8d740
Found by: stack scanning
12  phantomjs + 0x1d9e26b
rip = 0x000000000219e26c   rsp = 0x00007f2422f8d750
Found by: stack scanning
13  phantomjs + 0x18e74c4
rip = 0x0000000001ce74c5   rsp = 0x00007f2422f8d770
Found by: stack scanning
14  phantomjs + 0x17725c9
rip = 0x0000000001b725ca   rsp = 0x00007f2422f8d810
Found by: stack scanning
15  phantomjs + 0x17729a0
rip = 0x0000000001b729a1   rsp = 0x00007f2422f8d880
Found by: stack scanning
16  phantomjs + 0x1774741
rip = 0x0000000001b74742   rsp = 0x00007f2422f8d8d0
Found by: stack scanning
17  phantomjs + 0x17f85f3
rip = 0x0000000001bf85f4   rsp = 0x00007f2422f8d8e0
Found by: stack scanning
18  phantomjs + 0x170352a
rip = 0x0000000001b0352b   rsp = 0x00007f2422f8d900
Found by: stack scanning
19  phantomjs + 0x1774b76
rip = 0x0000000001b74b77   rsp = 0x00007f2422f8d930
Found by: stack scanning
20  phantomjs + 0x1774e46
rip = 0x0000000001b74e47   rsp = 0x00007f2422f8d9f0
Found by: stack scanning
21  phantomjs + 0x17d59a8
rip = 0x0000000001bd59a9   rsp = 0x00007f2422f8da10
Found by: stack scanning
22  phantomjs + 0x18df5a2
rip = 0x0000000001cdf5a3   rsp = 0x00007f2422f8da20
Found by: stack scanning
23  phantomjs + 0x1774d8f
rip = 0x0000000001b74d90   rsp = 0x00007f2422f8da38
Found by: stack scanning
24  libc-2.15.so + 0x54308
rip = 0x00007f247d955309   rsp = 0x00007f2422f8da40
Found by: stack scanning
25  phantomjs + 0x1774d8f
rip = 0x0000000001b74d90   rsp = 0x00007f2422f8da78
Found by: stack scanning
26  phantomjs + 0x1d9ae90
rip = 0x000000000219ae91   rsp = 0x00007f2422f8daa0
Found by: stack scanning
27  phantomjs + 0x1d9e226
rip = 0x000000000219e227   rsp = 0x00007f2422f8dab0
Found by: stack scanning
28  phantomjs + 0x1d9e22e
rip = 0x000000000219e22f   rsp = 0x00007f2422f8dac0
Found by: stack scanning
29  phantomjs + 0x1d9ae90
rip = 0x000000000219ae91   rsp = 0x00007f2422f8dbb0
Found by: stack scanning
30  phantomjs + 0x1d9e226
rip = 0x000000000219e227   rsp = 0x00007f2422f8dbb8
Found by: stack scanning
31  phantomjs + 0x1d9e22e
rip = 0x000000000219e22f   rsp = 0x00007f2422f8dbc0
Found by: stack scanning
32  phantomjs + 0x18db8bf
rip = 0x0000000001cdb8c0   rsp = 0x00007f2422f8dc30
Found by: stack scanning
33  phantomjs + 0x18e05fd
rip = 0x0000000001ce05fe   rsp = 0x00007f2422f8dc70
Found by: stack scanning
34  phantomjs + 0x1d9ae90
rip = 0x000000000219ae91   rsp = 0x00007f2422f8dc80
Found by: stack scanning
35  phantomjs + 0x1d9e226
rip = 0x000000000219e227   rsp = 0x00007f2422f8dc90
Found by: stack scanning
36  phantomjs + 0x1d9e22e
rip = 0x000000000219e22f   rsp = 0x00007f2422f8dca0
Found by: stack scanning
37  phantomjs + 0x1d9ae90
rip = 0x000000000219ae91   rsp = 0x00007f2422f8dd28
Found by: stack scanning
38  phantomjs + 0x1d9e226
rip = 0x000000000219e227   rsp = 0x00007f2422f8dd30
Found by: stack scanning
39  phantomjs + 0x1d9e22e
rip = 0x000000000219e22f   rsp = 0x00007f2422f8dd38
Found by: stack scanning
Loaded modules:
0x00400000 - 0x026e3fff  phantomjs  ???  (main)
0x7f2422f90000 - 0x7f2422fa1fff  n019004l.pfb  ???
0x7f24289ac000 - 0x7f24289fdfff  DejaVuSansMono.ttf  ???
0x7f242b65a000 - 0x7f242b6fefff  DejaVuSans-Bold.ttf  ???
0x7f243008c000 - 0x7f243009ffff  n019003l.pfb  ???
0x7f24300a8000 - 0x7f2430157fff  DejaVuSans.ttf  ???
0x7f24303e4000 - 0x7f24305ebfff  libnss_dns-2.15.so  ???
0x7f24305ec000 - 0x7f24307f8fff  libnss_files-2.15.so  ???
0x7f2430b8d000 - 0x7f2430bd9fff  DejaVuSansMono-Bold.ttf  ???
0x7f247818f000 - 0x7f24783a8fff  libresolv-2.15.so  ???
0x7f247b4aa000 - 0x7f247b4b0fff  gconv-modules.cache  ???
0x7f247cc18000 - 0x7f247ce6afff  libssl.so.0.9.8  ???
0x7f247ce6b000 - 0x7f247d1f4fff  libcrypto.so.0.9.8  ???
0x7f247d1f8000 - 0x7f247d4c0fff  locale-archive  ???
0x7f247d4c1000 - 0x7f247d6e9fff  libexpat.so.1.6.0  ???
0x7f247d6ea000 - 0x7f247d900fff  libz.so.1.2.7  ???
0x7f247d901000 - 0x7f247dcbafff  libc-2.15.so  ???
0x7f247dcc0000 - 0x7f247ded5fff  libgcc_s.so.1  ???
0x7f247ded6000 - 0x7f247e1d1fff  libm-2.15.so  ???
0x7f247e1d2000 - 0x7f247e4bffff  libstdc++.so.6.0.17  ???
0x7f247e4d5000 - 0x7f247e6edfff  libpthread-2.15.so  ???
0x7f247e6f2000 - 0x7f247e8f9fff  librt-2.15.so  ???
0x7f247e8fa000 - 0x7f247eafdfff  libdl-2.15.so  ???
0x7f247eafe000 - 0x7f247ed36fff  libfontconfig.so.1.6.2  ???
0x7f247ed38000 - 0x7f247efd3fff  libfreetype.so.6.9.0  ???
0x7f247efd4000 - 0x7f247eff5fff  ld-2.15.so  ???
0x7f247f1dc000 - 0x7f247f1e4fff  945677eb7aeaf62f1d50efc3fb3ec7d8-le64.cache-3  ???
0x7f247f1f0000 - 0x7f247f1f3fff  6d41288fd70b0be22e8c3a91e032eec0-le64.cache-3  ???
0x7fffaa0dc000 - 0x7fffaa0dcfff  linux-gate.so  ???

Please upgrade to PhantomJS 2.0. 1.9.x is no longer supported, and known to have many crasher bugs that are fixed in 2.0.


chore: remove distribution files from github release

PR Details

Removed distribution files from github release
Removed changelog file from github release

Description

Having distribution files in the github release is an overkill since it can be accessed from npm.
Having the changelog there also doesn't make sense since the release's body contains the release notes.
Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Disclaimer
By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement

:tada: This PR is included in version 1.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


all the tools - which execution order?

Sorry for sort of "hijacking" here but I found no common place (meta project?) which discusses all your solution file and project file related tools at once:

From a 2020/NET6 perspective: Which ones of the MsBuildXyz and VisualStudioSolutionXyz tools would make sense in which order?
Since today not a single project in my ecosystem has a ProjectGuid at all - will the tools still work?

My personal use case explained (not using any of your tools yet):
I have some dozen projects (each in its own git repo) which all use and depend on the same CompanySDK included as a sub-repository in git.
With 64bit having arrived to VS I created an optional/additional AllInOne.sln which (using symlinks) joins all the projects and ensures (symlink again) that there is only 1 copy of the CompanySDK repository which is then used by all of the projects - in order for refactorings of code in CompanySDK to affect all of the projects in one step.
Now after adding/removing/refactoring projects before doing final commits I have to ensure that the some dozen Project.sln files of the indiviual git repositories get updated/correct as within VS I only updated the AllInOne.sln.
I'm pretty sure I wanna use VisualStudioSolutionSorter to get rid of the git-conflict stress and VisualStudioSolutionUpdater to at least fill in new projects - but also VisualStudioSolutionFixer since for coming refactorings at lot of projects will have to be renamed and their directories as well (and again: none of the projects has a ProjectGuid yet, and I did not spot a MsBuildFillMissingProjectGuids tool either).
So my plan would be to create batch file which will be executed right after all code commits have been persisted (but not pushed to origin yet) which would then ensure that all the projects are consistent inself - executing the same batch file again should not introduce additional changes (if the execution order of your tools would be correct).
(if there is a better place for this issue just push me to destination)

@aolszowka the solution filters work great in later versions of VS2019 and in VS2022. Definitely a good feature for managing the load of subsets of a larger solution. It even filters the unloaded projects out of sight unless you toggle them. Would not have made such fast progress without your leg work.

@madkat Out of morbid curiosity how does the BIG BOY load up in VS2022 x64? Is SynergyDBL supported in 64bit land these days? I'd have to imagine its better. Hope you are well!

The big one loads quite well in testing. I haven't heard about results in the field so far. We sim-shipped 64-bit support with VS2022's launch, of course. There have been some nasty bugs, but it's generally way better. Things are going well, hope it's the same for you!

Is any of the tools capable of changing the project type guid FAE04EC0-301F-11D3-BF4B-00C04F79EFBC to 9A19103F-16F7-4668-BE54-9A1E7A4F7556?
This is also a big merge conflict PITA, see https://github.com/dotnet/project-system/issues/1821#issuecomment-544373435

@springy76 I do not believe so, but the tools were SDK/.NET Core aware in the sense that they'd crack open the referenced Project File and then assuming it had the sdk attribute on the project tag would adjust appropriately, here's the appropriate code:
https://github.com/aolszowka/VisualStudioSolutionGenerator/blob/f8ce0822f8894dbd211b80afcaf59e606608128b/VisualStudioSolutionGenerator/SolutionUtilities.cs#L127
and
https://github.com/aolszowka/VisualStudioSolutionGenerator/blob/f8ce0822f8894dbd211b80afcaf59e606608128b/VisualStudioSolutionGenerator/MSBuildUtilities.cs#L154
I would be totally up front and say I was just getting into .NET Core at that time and probably didn't have a whole lot of them being encountered, FWIW you also need to look out for the F# (fsproj) also doing the same thing on you: F2A71F9B-5D33-465A-A702-920D77279786 (Classic) -> 6EC3EE1D-3C4E-46DD-8F32-0CC8E7565705 (.NET Core), honestly probably all of them (we only had csproj/fsproj/synproj/sqlproj in this place).
I'll dig a little more but nothing comes to mind.


Update 8.0/beta to v8.0.28

UniFi Network Application 8.0.28 has been released.
Changes proposed in this pull request:

Update 8.0/beta to v8.0.28

@goofball222

Thank you for your contribution!


Add react-native setup-ios-permissions command

Hi folks 👋
Let's face it: the current iOS permission handlers setup is not that great. Having to deal with the Podfile file is a chore and not well understood by "non-native" developers.
This pull request adds a new system based on a new react-native CLI command: setup-ios-permissions. To use it, it's fairly easy!
1⃣ First declare the used iOS permissions in your iosPermissions config (the command uses cosmiconfig, so we can put that in our project package.json if we want):
{
  "iosPermissions": [
    "Camera",
    "LocationWhenInUse",
    "Notifications",
    "SpeechRecognition"
  ]
}

2⃣ Then run the CLI command:
$ npx react-native setup-ios-permissions

3⃣ Don't forget to reinstall Pods:
$ npx pod-install

4⃣ And…it's done ✨
P.-S. Note that you can use a postinstall script to simplify this:
{
  "scripts": {
    "postinstall": "react-native setup-ios-permissions && pod-install"
  },
  "devDependencies": {
    "pod-install": "0.1.38"
  },
  "iosPermissions": [
    "Camera",
    "LocationWhenInUse",
    "Notifications",
    "SpeechRecognition"
  ]
}

P.-S. (2) Did I mention that this approach fixes the issue with use_frameworks! that need this ugly workaround? 👀 (As permissions handlers will now be parts of the RNPermissions pod directly):

Fascinating!! Very nice (as probably the creator of all the motivation for use_frameworks adoption in react-native 😅 )

I wonder about the name in package.json. "iosPermissions" is pretty generic and doesn't immediately point to this library. Since this is probably gonna be copy-pasted initially, how about something more explicit like "reactNativePermissionsIOS"? On the other hand, what's the chance other nodejs tool would use this namespace? Probably really low

@thymikee Good though! I updated the config key.

I appreciate the library and all the work you put in 🙏  just struggling a little to see how this makes it easier or more performant. Sometimes you just want to run yarn install  to update the js node modules without running pod install everytime.
For some projects im working on, they use expo, so this is a very common scenario where pods aren't needed when running yarn install .
Any way to have a solution where the pods are nicely structured but without the need for an setup script?

@helenaford You actually don't have to run pod install each time you run a yarn install. I added that in README so people don't forget it.
You can remove the pod install from postinstall if you want, just don't forget to run it every time you change the reactNativePermissionsIOS config.

@zoontek yeah sorry, that's what i meant, every time the node modules are removed, you have to run the setup script right?
So for CI, we need the postinstall step?

also, for local development, i'd say it's not great to have that manual step. I can see how that can easily get missed out each time the node modules are cleared

@helenaford Yes. The CLI modify the podspec source paths, then you run the pod install.
Not ideal, but unfortunately the best compromise we found yet 😕

@zoontek  like i said above, i really appreciate how hard this is to do and what the intention is to try and make it as easy as possible, but in my opinion, the other way was better because you just configured it once per permission module.  Rather than everytime the node modules are cleared.

@zoontek thank you that would be perfect if we could put something in the Podfile. thanks for looking into this! 😎

@helenaford Could you try it? I released a new version, 3.9.0-beta.0 with it.
yarn add react-native-permissions@next

Then update your Podfile like this:
require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
+ require_relative '../node_modules/react-native-permissions/scripts/permissions_setup'

platform :ios, min_ios_version_supported
prepare_react_native_project!
+ prepare_react_native_permissions!

And run pod install (pod install must be re-executed each time you update reactNativePermissionsIOS config, but that's all)
PS: Don't forget to remove the pod-install call on postinstall if you want, as it's not needed anymore.

I'm not sure about the wording (the script file + function name) tho, it is subject to change before a release. Does it sounds good for you? @mikehardy @thymikee, do you have an opinion / some ideas for that?


excel export or print

I wish there was a function button on the top right of the table that can excel export or print the contents of 1 page where the current filter, ordering, and pagination are applied. This is a useful function in actual cms work.

Hey @gtolarc—this is actually a planned feature and will be deployed within the next two months or so!
We will be making our roadmap public shortly, and you’ll see this feature set reflected within it!


swap to using high-level gifsicle api

fixes https://github.com/choderalab/asapdiscovery/issues/478
ez pz, this doesn't break anything.

Codecov Report

Merging #484 (0d14a73) into main (3e455eb) will decrease coverage by 27.14%.
The diff coverage is n/a.

Additional details and impacted files


CB-16451: Fix issue when getting SDX events for environment with deleted datalakes.

Jira: https://jira.cloudera.com/browse/CB-16451
Please look at the Jira description for the reason behind this bug and how I resolved it. Essentially, SDX events will run into an error if any of the environment's DLs are deleted, this being a result of additional error handling we added into 2.54.0.
This simply does nothing for the cloudbreak events if the DL is deleted, allowing for its SDX events to still be present, but not breaking the overall event retrieval.
I have tested this both via local UI and through both endpoint methods via Postman.

I want this to go into 2.54.0 since the bug was introduced in that branch. I don't expect many people to run into issues, I believe it mainly only happens with processes such as resize, but I want to make sure the branch is perfectly safe.

pls rebase your PR onto top of CB-2.54.0

so we will get events from datalake service but not from cloudbreak in case of deleted/detached datalake?

Yes exactly, which is desirable, for example in the resize case, where the events from the original deleted datalake contain useful info about the resize process overall.

I will dismiss my review and let you (as feature creator/owner) decide what is the best solution here


List of errorcodes in wlfreerdp

Hello,
we moved from xfreerdp to wlfreerdp due to Debian 12 Bookworm.
Version:
wlfreerdp --version
Output: This is FreeRDP version 2.11.2 (2.11.2)
I have a script running and doing stuff based on the error code xfreerdp returned.
This is the list i used for that, which to be fair, has some mistakes...
https://github.com/FreeRDP/FreeRDP/blob/2.11.2/client/X11/xfreerdp.h (Line 282-348 - enum XF_EXIT_CODE)
=> for example, xfreerdp actually returnd exit code 12 for EXIT_LOGOFF, not 2
But with wlfreerdp it seems that this list is unusable, because for the most of the time i receive error code 255 for whatever reason...
=> for example, xfreerdp returned 134 if my password is wrong, now it is 255
Where can i find an updated list of the exit codes?
Thank you in advance
Cheers

better stay with xfreerdp, wlfreerdp does lack a lot of features (like this one).
we´re deprecating it with FreeRDP 3.0 in favour of sdl-client, which already can do more

Hello @akallabeth
thanks for your reply.
We used wlfreerdp because it has way better performance than xfreerdp.
I am trying to use the new sdl-client, but i have a few questions..
I followed theese instructions: https://github.com/FreeRDP/FreeRDP/wiki/Compilation
and build and installed SDL2, SDL_ttf and FreeRDP.
Versions are:
FreeRDP: 3.0.0-beta4
SDL2: 2.28.4
SDL2_ttf: 2.20.2
Little sidenode..
There is a list of "suggested base dependencies" for debian based.
There are 2 packages/libraries that are incorrect.
libkrb5-multidev should be libkrb5-dev
and
libsdl2-tty-dev should be libsdl2-ttf-dev
Am i correct here? Because i can´t find libkrb5-multidev nor libsdl-tty-def when i try sudo apt install..
Now i am a bit confused, because i can choose between xfreerdp, wlfreerdp and sdl-freerdp.
I guess sdl-freerdp is the one i should use?
Cheers

@akallabeth
Thank you, i gave it a try but i came to a point where i don´t know what to do..
I will open a new issue to split it.
Cheers


confusion around x86 "and" instructions

These two seem to conflict:
["and"              , "X:r32/m32, id/ud"                                , "MI"      , "81 /4 id"                     , "ANY _XLock       OF=0 SF=W ZF=W AF=U PF=W CF=0"],
["and"              , "X:r64, ud"                                       , "MI"      , "81 /4 id"                     , "X64 _XLock       OF=0 SF=W ZF=W AF=U PF=W CF=0"],

This is on purpose - you can encode 64-bit AND with unsigned immediate by not promoting the instruction to 64-bit. Then it's basically the same as the former - it's only possible when the operand is a register though.

Suppose I am looking at this from the perspective of a decode and I encounter a byte sequence that matches
"81 /4 id"
how do I know whether this which "rule" applies. In other words: is this a 32bit or a 64bit instructions.
Maybe this is dependent on the processor mode?
I would also expect that the "or" instruction has similar/symmetric rules but I did not see any.

In case of decode, you should always decode to an original instruction and consider all other aliases as just aliases. The encoder would support the alias (or not, depending on how you see it), but the decoder would always decode to a canonical representation.
OR doesn't have that capability, because it would zero extend the high part of 32-bit reg, which is what AND r64, ud does, but OR r64, ud encoded as 32-bit would essentially do (r64 | ud) & 0xFFFFFFFF

Ah I see. Is there a  programmatic way to determine which instructions are "original" .
I noticed some instructions have an AltFrom tag but that seems to be something slightly different.

I found another conflict:
  ["and"              , "X:eax, id/ud" , "I"       , "25 id"                        , "ANY AltForm      OF=0 SF=W ZF=W AF=U PF=W CF=0"],
  ["and"              , "X:rax, ud"  , "I"       , "25 id"                        , "X64 AltForm      OF=0 SF=W ZF=W AF=U PF=W CF=0"],

These are the only two such cases I found in the fairly large part of the tables that I process.
This is seems like an odd exception given that this pattern is not repeated with another ALU type instruction.

I spoke to soon. Here is another ambiguity of a slightly different flavor:
    ["movss"            , "w:xmm[31:0], xmm[31:0]"                          , "RM"      , "F3 0F 10 /r"                  , "SSE"],
    ["movss"            , "W:xmm[31:0], m32"                                , "RM"      , "F3 0F 10 /r"                  , "SSE"],

    ["movsd"            , "w:xmm[63:0], xmm[63:0]"                          , "RM"      , "F2 0F 10 /r"                  , "SSE2"],
    ["movsd"            , "W:xmm[63:0], m64"                                , "RM"      , "F2 0F 10 /r"                  , "SSE2"],

Can you describe what is ambiguous in movss / movsd case?
The instructions really do what is described. movss|movsd from memory clears the rest of the register, movss|movsd between registers won't (that's the W vs w).

I see. I think the  problems is that I am  currently mostly focused on the decoding part while asmdb is more focused on encoding.
If I encounter F3 0F 10 xx xx ... I do not know what rule to chose based on only the bytes and the format ("RM").
This is similar to the ambiguity I reported with the "and" instructions further up.
What I have done on my side to deal with this is

ignore the rules for

and              , "X:rax, ud"
and"              "X:r64, ud" ,

change the movss/movsd rules slightly:

movss      "w:xmm[31:0], xmm[31:0]"       "RM"   =>   ......  "Rr"
movss      "w:xmm[31:0], m32"                 "RM" =>     ......  "Rm"

where r = M format restricted to reg    m = M format restricted to m
This gets rid of the ambiguity for me. Not sure if this makes sense for asmdb, though


forge script --verify fails with "Etherscan could not detect the deployment"

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (4e141e7 2022-07-21T00:08:59.558233829Z)
What command(s) is the bug in?
forge script
Operating System
Linux
Describe the bug
I have a fairly simple contract which I'm trying to deploy though a script:
Contract:
pragma solidity ^0.8.14;

contract Example {
  uint256 public immutable a;

  constructor(uint256 a_) {
    a = a_;
  }
}

Script:
pragma solidity ^0.8.14;

import "forge-std/Script.sol";
import {Example} from "./Example.sol";

contract ExampleDeploy is Script {
  function run() external returns (Example) {
    vm.startBroadcast();

    Example tpl = new Example(1);

    vm.stopBroadcast();

    return tpl;
  }
}

Then I try to execute the script like:
export ETHERSCAN_API_KEY=MY_API_KEY
forge script ExampleDeploy --fork-url=http://localhost:8545 -vvv --verify --broadcast

The contract is deployed, however the source code verification fails as I the following error:
> Error:
> Etherscan could not detect the deployment.

I have tried executing this script several times and the failure rate is 100%, always on the verification step.

Which network? Do you actually see it deployed on the etherscan in question ?

Oops, I forgot to specify: I'm using Goerli.
Yes, the contract was deployed to Goerli, however the verification failed.

If you call again without the --broadcast flag, and only with the --verify, does it still happen ? I noticed that Goerli etherscan can be quite slow updating sometimes...

I've been running into the same issue.
I'm still trying to verify on rinkeby. Pretty much happened exactly with the new recent update for me.
Before it would at least wait a bit (or have some retries), now it just instantly spits out the error.
Been swapping out --broadcast with --resume after running the script to get it to verify.

If you call again (once you see it on etherscan) without the --broadcast flag, and only with the --verify, does it still happen ? I noticed that Goerli etherscan can be quite slow updating sometimes...
I tried it now, and that's what happened.
1. Gave me that error

2. Had to wait around 2 minutes for the contract to show up on etherscan

3. Called just with the --verify flag and it worked.

Yeah, omitting the --broadcast flag and calling it again makes the verification go through.
Would it be possible to embed this mechanism within the command?
As it is the command will exit with non-zero code, which can lead to all sorts of issues with shells running them.

I have something similar happening for a contract as simple as the op has. Not much error details except "Etherscan could not detect the deployment". using --resume instead --broadcast make it go thru the second run on my Mac.
Unfortunately on Windows, it always says and using --resume instead --broadcast  doesn't change anything.
Start Contract Verification
Transactions saved to: broadcast\Contract.s.sol\1\run-latest.json

The contracts are deployed correctly, it's just the verification process that seems to fails without giving any clues.

Has this been fixed recently? @joshieDo

Linked the above PR that taclkes this issue. However, not if the indexer takes 2 mins. But I think waiting 25 seconds for a contract should be enough. wdyt


Doesn't work anymore with Rails 4.x

This is what happens:
$ rails g models_from_tables
"******************************************************************"
"The 'matthuhiggins-foreigner' gem has changed names to 'foreigner'"
"Install the renamed gem using 'gem install foreigner'"
"******************************************************************"
/home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/activerecord-4.2.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:570:in `retrieve_connection': No connection pool for ActiveRecord::Base (ActiveRecord::ConnectionNotEstablished)
        from /home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/activerecord-4.2.3/lib/active_record/connection_handling.rb:113:in `retrieve_connection'
        from /home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/activerecord-4.2.3/lib/active_record/connection_handling.rb:87:in `connection'
        from /home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/legacy_data-0.1.11/lib/legacy_data.rb:9:in `block in <module:ActiveRecord>'
        from /home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/legacy_data-0.1.11/lib/legacy_data.rb:8:in `class_eval'
        from /home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/legacy_data-0.1.11/lib/legacy_data.rb:8:in `<module:ActiveRecord>'
        from /home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/legacy_data-0.1.11/lib/legacy_data.rb:7:in `<top (required)>'
        from /home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/bundler-1.10.6/lib/bundler/runtime.rb:76:in `require'
        from /home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/bundler-1.10.6/lib/bundler/runtime.rb:76:in `block (2 levels) in require'
        from /home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/bundler-1.10.6/lib/bundler/runtime.rb:72:in `each'
        from /home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/bundler-1.10.6/lib/bundler/runtime.rb:72:in `block in require'
        from /home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/bundler-1.10.6/lib/bundler/runtime.rb:61:in `each'
        from /home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/bundler-1.10.6/lib/bundler/runtime.rb:61:in `require'
        from /home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/bundler-1.10.6/lib/bundler.rb:134:in `require'
        from /home/sixtyfive/tmp/msa-legacy-db-access/config/application.rb:7:in `<top (required)>'
        from /home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/spring-1.3.6/lib/spring/application.rb:82:in `require'
        from /home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/spring-1.3.6/lib/spring/application.rb:82:in `preload'
        from /home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/spring-1.3.6/lib/spring/application.rb:143:in `serve'
        from /home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/spring-1.3.6/lib/spring/application.rb:131:in `block in run'
        from /home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/spring-1.3.6/lib/spring/application.rb:125:in `loop'
        from /home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/spring-1.3.6/lib/spring/application.rb:125:in `run'
        from /home/sixtyfive/.rvm/gems/ruby-2.2.0/gems/spring-1.3.6/lib/spring/application/boot.rb:18:in `<top (required)>'
        from /home/sixtyfive/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from /home/sixtyfive/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from -e:1:in `<main>'

@sixtyfive I'm glad that you're finding this gem useful. I have to be honest that I haven't looked at it in several years. I'm sorry but I don't have the time to figure out what's going on and bring this up to date. I'd be more than happy if you want to fork & update this yourself and would be happy to make you the owner on rubygems so you could then push your changes.
I expect this is not the answer you are hoping for and I'm sorry I don't have the time to be of more help.

Alex, thank you for responding! Unfortunately I'm in a similar position time-wise (as probably a lot of people interested in a gem like this one might be). At least now this issue exists, so perhaps someone decides to step up...

For anyone finding this, I have successfully used this gem to build models in a dummy Rails3 app, which I then modified and dropped into a new Rails4 app.  Some awk/sed steps help with this.  See my comment in other thread in this issue for some steps that worked for me:
https://github.com/alexrothenberg/legacy_data/issues/4


Remove AntiGhost

Mod name
AntiGhost
Curseforge link
No response
Other links
No response
What it does
Asks the server to resend the packets when glitching inside blocks
Why should it be in the modpack

Very useful in Hypixel and other 1.8 servers
Avoids having to relog

Why shouldn't it be in the modpack
People may:

not know it's there
not know what it does
not know when to use it
be afraid to use it #95
not want to bother with it as it takes long to type (compared to keybind)
may have actually been kicked from the server for wrong usage
misuse can be negative to servers (see Julien's comment below)

Also

This should be fixed for the most part by Mojang already
This seems to go against the principle of not having to learn what mods FO has

Categories
New feature
Additional details
See https://github.com/Fabulously-Optimized/fabulously-optimized/issues/316#issuecomment-1125160521 for a potential alternative to advertise by

Ghost blocks appear more often on low ping and not only in older MC version servers. Also ghost blocks appear in singleplayer mode too

If I keep the mod, how could I advertise it for the right players at the right time?
It is already mentioned in Mod Menu and the description. Making the text more noticable probably wouldn't help as there is lots of text anyway and people could forget it by the time they need it.

If I keep the mod, how could I advertise it for the right players at the right time? It is already mentioned in Mod Menu and the description. Making the text more noticable probably wouldn't help as there is lots of text anyway and people could forget it by the time they need it.

With the needed information, I am willing to write a full description in the wiki

Is it only activated by command, rather than keybind? If so we could just add a keybind to the mod. That'll also make its presence more known to users changing their keybinds when they find it in the list.

There is a keybind - it defaults to G. FO disabled it since 2.x.x because users should not hold it down or hit it repeatedly, plus it was hit by an accident.

There is a keybind - it defaults to G. FO disabled it since 2.x.x because users should not hold it down or hit it repeatedly, plus it was hit by an accident.

Maybe we should bind it to some key that is far on the right of the keyboard or to a function key because these can't be hit by accident.

 Besides, no matter what key it is, they still need to learn it and use it, how would I tackle that issue?

Well antighost should either be more "advertised" (it's not what i exactly mean but I'm not sure how to say it) or removed because having it in if majority of people don't use it is against FO basic rules.
And the fact people would have to learn something makes it even against the rules.
But it's really useful in some case and if more people knew about it, it would be more used when needed.
Personnally i have removed it from my own modpack because one of my friend used it to make my own server lag by spamming it (and yes he's now banned).

I'm in favor of pruning the modpack a bit (I think it's getting a bit too large for its own good) and AntiGhost is a good place to start pruning. In a modpack about performance and beauty, AntiGhost doesn't really have a legitimate claim to exist. I'll post a larger pruning-focused issue later this week.

Anti Gosto fixes one of the most annoying bugs in Minecraft, happens a lot to players that plays in servers and a considerable number of times
I don't see a reason to remove It besides "the modpack is way too big", It does not add lag nor delays the updates

how to make users use this mod for the right purpose at the right time?
Maybe in the modpack descrition?

I personally never used this mod, but it can cause pain b/c of some anticheats, so I'm favour of removing it

Maybe in the modpack descrition?

The modpack description is already long (and mentions it!) and while I have plans to shorten it, I don't think mentioning this there should be a goal in itself, just keep it as a disclaimer.
I am thinking more contextual stuff like the TAB menu, the pause menu, the chat? And specific mod suggestions that would actually be able to achieve that.

I think this mod shows a lack of consistency in FO currently. Mods such as Beenfo, Chunky, and Suggestion Tweaker are rejected because they will only help a niche of players, but mods such as this are allowed. I think FO needs a clearer stance on mods that help the life of a certain niche of players. If AntiGhost is allowed to stay, I think that the pack should allow itself to open up to other QoL mods. However, if we remove AntiGhost, I think that should be the stance going forward on similar mods that only impact vanilla experience to make something easier.

Let's clear some things up first:

AntiGhost was added at the beginning of FO, in 2020. There were not a lot of mods that optimize the game at the time (except CaffeineMC's) so this was added as it seemed to be a good idea.
AntiGhost does help a lot in 1.8 servers, which the majority of the players (still) play in, even if only time to time. So, not exactly niche, just need to know when and how to use it.
Beenfo is currently not rejected. I think I will add it, just want to do some testing for it and resolve some other FO things first.
Chunky is server-side, which is not really the goal of FO, and it must be learned how to usexecuted manually
Suggestion Tweaker helps a limited amount of people using creative commands, so it does seem niche to me
The pack already is open (and has!) to QoL mods, you might be interested in this discussion: https://discord.com/channels/859124104644788234/859124543712133130/973219951114592337 It's rather about the scope of the QoL mods I add, it must not derive too much from vanilla.
I appreciate the criticism, but it is not that easy to make decisions when they are controversial :grin:

Here's one approach I could think of.
The real thing would require the files of all ~120 languages in-game, but since it is just one row of text, it will probably take less than a megabyte. The proof of concept is currently EN-US only.
And no, vanilla doesn't like newlines, otherwise I would've used that.
[(https://github.com/Fabulously-Optimized/fabulously-optimized/files/8680693/AntiGhost.reminder.zip)
AntiGhost reminder.zip

Maybe the issue you have to learn the mod is actually the mods fault. Instead, an improved mod that automatically updates ghost blocks if you lag back.

The issue is not exclusive to ViaVersion servers. I have gotten the issue on 1.18.2 servers using a 1.18.2 client.

Here's one approach I could think of. The real thing would require the files of all ~120 languages in-game, but since it is just one row of text, the resourcepack would probably take way less than a megabyte in total.
The proof of concept is currently EN-US only, feel free to try different text variations to improve it. And no, vanilla doesn't like newlines, otherwise I would've used that.

I personally disagree with the RP addition because:

It would take a long time to translate this in all the MC supported languages, like you said
It would be annoying to see this message every time you pause the game

I personally disagree with the RP addition because:

It would take a long time to translate this in all the MC supported languages, like you said
It would be annoying to see this message every time you pause the game

Thanks for the feedback.

If I kept "Game Menu" translated, indeed it would require constant maintenance unfortunately. But if I didn't, the zip would probably optimize it as ~100 files with identical contents 😄
Good point, as it should be still rarely needed.

Maybe I will overhaul the main description after all and mention it there, it is long overdue... 🤔

Maybe something like main menu credits for the pause screen? Put it in grey text bottom right?

That could work, but is it worth adding an another mod for it...

Main Menu Credits

Main Menu Credits

Okay, that's cool. I hope it didn't affect the mod too much (e.g. don't mixin that view unless there is text to insert).

Remember, text objects can also be translation keys for different languages.

I'm aware that I can use existing ones but you're saying that I can also create new ones?

Not sure. You would probably have to do this under assets/isxander-main-menu-credits

Main Menu Credits
Remember, text objects can also be translation keys for different languages.

Is it toggleable?

I would make it gray like in that picture so it would be minimally obtrusive but no, I don't think a toggle would be needed for this.
Easiest way to get rid of it would indeed be disabling the whole mod, blanking or deleting its config.
But otherwise I still think it would add more value than annoyance in my opinion because it doesn't have the limits of the resource pack approach.

I do not think this should be removed. This has come in handy so many times that it's not even funny lol.
I assume you can manually bind the keybind? If you wanted it for some reason

I do not think this should be removed. This has come in handy so many times that it's not even funny lol.
I assume you can manually bind the keybind? If you wanted it for some reason

Thanks for the input. As said before, there already was a keybind, but it was too easy to hit by accident and I did not see that switching to a different key would really fix the core problem.
Right now I think that Xander's solution is the best, just waiting for the mod to update now, so I can test it.

Pause Menu Credits added:
https://github.com/isXander/main-menu-credits/releases/tag/1.1.0

Broken atm. Need to release hotfix.


mental health notebook

Closes #380
Mental health notebook, adapted from the notebook by @MayanaPereira:
https://github.com/opendp/smartnoise-samples/blob/master/analysis/tutorial_mental_health_in_tech_survey.ipynb
Thanks Mayana!

Dependency: #494

TODO: rebuild on new Polars APIs

Closing for https://github.com/opendp/opendp/pull/1666


Constrain dcat:mediaType in SHACL file

dcat:mediaTypes should be constrained to agreed upon text labels and/or URLs
copied from https://github.com/fair-ease/IDDAS/issues/4

for now in PR, dcat:mediaType values can be:

https://www.iana.org/assignments/media-types/application/netcdf
http://www.iana.org/assignments/media-types/text/csv
https://www.iana.org/assignments/media-types/application/ld+json
https://www.iana.org/assignments/media-types/text/turtle
https://www.iana.org/assignments/media-types/application/rdf+xml

But this is only a preliminary list..
Does anyone know of other types that can/need to be added?

Hi @laurianvm good suggestion. The IANA list is great but it could be enhanced by the SDN data transport formats https://vocab.nerc.ac.uk/collection/L24/current/

SDN data transport formats have been included
note: updates to this list are not (yet) automatically included in the shacl file...

SDN data transport formats have been included
newly described formats in the https://vocab.nerc.ac.uk/collection/L24/current/ namespace should be automatically included
@alko-k  chould you check and close the issue if OK? :)


Update DOI when the final version is published

The links referring to the article are at least the following:

DOI badge in README
DOI in CITATION.cff

https://www.cell.com/cell-reports/fulltext/S2211-1247(22)00330-8

Ah thanks :)


Where we are with Informational meeting -> Goal when can users start using it

We met today and conclusion is we need to do:

UI improvements
Update email template
Update wiki page and aka.ms link

Once that is done, our users can use the tool.
There is also an exatra ask of surface the Service Product when scheduling an Informational meeting. This will come from the Release Planner App and if not provided, user can select it.


Is there any plans for react native support?

Is there any plans in the coming days to support react native or releasing react native compatible library?

Without react-primitives (which eliminates non flexbox browsers), it’d have to be a separate library.

@raharida we do not, at this time, have any plans to move in that direction unfortunately. As @ljharb mentioned, it would require porting over to react-primitives or something similar which we're not quite ready to do.

Hi, thank you for this great library! No plans yet for React Native?


HTYI: Game is never-ending, ignores config in Keystone

Right now in keystone HTYI is set to have 3 rounds, but my current game hasn't ended yet after at least six.

I'm still playing as well, probably upwards of 20 rounds! I assumed there was supposed to be an option to end the game manually somewhere on the main page, I didn't know it was set to end after a certain number of rounds.

update: I just continued to play but game got disconnected without an ending score screen, it's stuck on the 0 countdown.


Fix: typo in create-image-and-azure-resources.md

Description
New tool, Bug fixing, or Improvement?
Please include a summary of the change and which issue is fixed. Also include relevant motivation and context.
For new tools, please provide total size and installation time.

Related issue:
Check list

[ ] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

@rasa thank you for your contribution!


Merge release preparation back to master

Coverage remained the same at 47.232% when pulling eac09de622a2dc50452ebd85a22dba95c712f9fb on release into 729fb23ed6f04a6c8d6ed9945ed5fd77905abd34 on master.


Deduplicate productions

@virgil-serbanuta do you have a minimal example where multiple productions are produced? I guess that causes a crash, because in several places we assert that a single production is produced, so w eshould add a test of that to our integration tests, to make sure the filtering is working correctly.
I haven't seen a case where this happens yet, but maybe I haven't used fancy enough import structure yet. Maybe we also just need to change the way we recursively collect sentences from imported modules instead of deduplicating the productions after the fact. Right now KDefinition.sentences, for example, just grabs all the sentences in all the modules. It could instead, for example, walk the import DAG, build a traversal that makes sense given the import structure that only visits each module once, then collect the sentences from the modules in that order.

@virgil-serbanuta do you have a minimal example where multiple productions are produced?
a.k:

module A
  imports B
  imports C
endmodule

module B
  syntax Int
endmodule

module C
  syntax Int
endmodule

kompile a.k --backend haskell --emit-json

Search for
{"node":"KProduction","klabel":{"node":"KLabel","name":"isInt","params":[]}

in a-kompiled/compiled.json

I also added a test which fails on master.

I still don't understand how we are getting duplicate productions in the first place, which is what I think needs to be addressed rather than just filtering them out.
Here is where we gather the productions: https://github.com/runtimeverification/pyk/blob/8b8f791d136b5307ed093850c3318401186b4a91/src/pyk/kast/outer.py#L985.
Which uses the gathering of the modules: https://github.com/runtimeverification/pyk/blob/8b8f791d136b5307ed093850c3318401186b4a91/src/pyk/kast/outer.py#L981.
Which uses the gathering of the module names: https://github.com/runtimeverification/pyk/blob/8b8f791d136b5307ed093850c3318401186b4a91/src/pyk/kast/outer.py#L966
Which as far as I can tell, should only gather each module a single time (as long as it gets the same name). So in the example of your test,  the module INT should only be collected a single time, not twice as it traverses both sides of the import path.

@virgil-serbanuta please get in the habit of adding a description to the main PR comment body (which gets included in the git changelog). It helps the reviewer, and it helps people who need to look through the history to find out why a change was introduced.


Exportimporter leaves importfiles OPEN or PENDING

TL;DR
If an importfile is unable to be ingested by exportimporter (due to incorrect formatting of export url, etc), it sometimes remains in "PENDING" status instead of failing.
Expected behavior
Import should fail after X number of tries.
Observed behavior
Importfile left in PENDING status.
@mikehelmick

/assign
my plan is to retry a file as long as it appears in the index.txt file - when it drops out of there, we'll move it to failed.
will also add a retry count, so an operator could see this

yoink


ToolTipster functionBefore might be causing tooltipster not a function error

Hi I get the following error: TypeError: jQuery(...).tooltipster is not a function
The strange thing is this only happens on one page and from what I can see JQuery is loaded before the plugin is loaded and the html element exists in the DOM before the call is made, what is also strange is the first time I see   jQuery('#customerNameHeader').tooltipster called there is no error, it only seems to error on the second call from functionBefore. I am out of ideas on what to look for as to what might be the cause of this error since the plugin works fine on other views in my application.
I have looked at the how the code runs on a page where it works and then again on this single view where it doesn't and I see no difference at all, I am stumped here.
I have no idead what is causing the error and no idead what else to try and solve it.

Hi, maybe you loaded jQuery twice, and the Tooltipster plugin is only added to the first one.

I don't see JQuery loaded more then once, I  was debugging what is defined with Firebug before I posted here, I tried a different tooltip plugin and got the same error on the same page so it has to be something with this page not being able to locate the plug-in library which makes no sense to me as I can see it is loaded.

I'm not sure how can I help further on this. Good luck debugging :/


if delete the process but the process's io still used by other process.tell ctr io still in use by other process.

find this error in  ctr v1.7   "TestContainerDrainExecIOAfterExit" ,if ctr send 'delete' info to shim ,the shim return ok ,the ctr will think that IO is being closed. but this IO may still used by other process , may shim can't close it .

When failed to delete, shim will return the underlaying error. If IO was used by another process, I think it is the underlaying runtime that should report this error instead of shim.

Do you mean to implement it in runc.rs？

Do you mean to implement it in runc.rs？

Not yet,  runC command should do this. You can try go-shim and check its behaviour. If go-shim doesn't report, neither of rs-shim.

Do you mean to implement it in runc.rs？

Not yet, runC command should do this. You can try go-shim and check its behaviour. If go-shim doesn't report, neither of rs-shim.

I feel confused, Can you provide a solution？the go shim use pipe+fifo , so they can close pipe and fifo will not be used by Daemon , rust-shim use fifo directly,  you can't close the io , it will still used by Daemon.this the between goshim and rustshim , there's any nice solution to resolve this problem ?

I guess you have a main container that has opened other containers' IO in your case, right? And you expect the other containers shouldn't get removed when their IO is still in use.

sorry,I don't think I described it clearly. I find this problem in "TestContainerDrainExecIOAfterExit" from containerd V1.7.6 , it use ExecSync function , but rustshim can not pass this test.

sorry,I don't think I described it clearly. I find this problem in "TestContainerDrainExecIOAfterExit" from containerd V1.7.6 , it use ExecSync function , but rustshim can not pass this test.

OK. Let me check it.

Hi @jokemanfire，I mentioned the same problem in #9568.I thought of a solution, query the process that took the pipe when deleting, and kill then all. But I haven't tested this yet. Can your modification pass “TestContainerDrainExecIOAfterExit”?

Hi @jokemanfire，I mentioned the same problem in #9568.I thought of a solution, query the process that took the pipe when deleting, and kill then all. But I haven't tested this yet. Can your modification pass “TestContainerDrainExecIOAfterExit”?

yes, I found your issus and I have mentioned it in rust-shim discussion , this code can pass that test, I think you need't kill them ,because containerd will take these io .Another solution  (like go shim use pipe + fifo) .

Hello , @Burning1020  @Wabct Is there an elegant solution to this problem found？ or this issus has been found?Thank you for your reply....  0.0

您好，我是姚鑫，您的邮件已收到，我查阅后会尽快回复您。谢谢！


info!(

On STM32WL example
lora_lorawan.rs
wich UART PORT is redirect the data of info!(
thanks

probe-run uses rtt to log output, not uart.

See:
https://github.com/embassy-rs/embassy/issues/1894
for some follow-on discussion.  Are there any known tricks to using the STLINK on an stm32wl when running WSL2 on Windows as a substitute for a Linux kernel?

Not sure if WSL supports USB. You can always build inside WSL and run probe-rs outside, though.


Training and Inference with Custom Dataset

Hi, I want to use custom dataset (in COCO format) but I have some questions.

What do I do after I open a folder named "datasets" and put my dataset in it? When I start the training it doesn't see my dataset and gives an error. It automatically sees coco2017 and some other famous datasets, but how can I train on my own dataset? Can you tell me the scripts I need to add?
What should the hierarchy of the dataset be like? Should the annotation files be in a separate folder or inside the image folders?
I also have test set (unseen data, in addition to training and validation sets). How do I edit the config file to inference on this test dataset?
How can I use COCO Evaluator with my custom dataset?

I know the following commands but I don't understand the usage with custom dataset.
(1) python ./tools/train_net.py --num-gpus 8 --config-file ./configs/yolof_R_50_C5_1x.yaml
(2) python ./tools/train_net.py --num-gpus 8 --config-file ./configs/yolof_R_50_C5_1x.yaml --eval-only MODEL.WEIGHTS /path/to/checkpoint_file

@chensnathan


Feature request: Generate multiple bolt12 offers

Hi
It could make sense to generate multiple bolt12 offers to preserve some privacy
Thanks

Ok, created discussion #81

Moved to discussions


[Bug]: HVAC state not visible in text & icon

Current Behavior
Hi,
First of all thanks for your nice work.
Matches perfect with the mushroom cards :-)
The icon action/state is correct for me when hvac_action is cooling (blue snowflake icon) & hvac_action is heating (orange fire icon). Thats's working perfect! However when the hvac_action is idle, then it gives a grey thermostat icon.
For my understanding: the state (mode) of the climate entity is cool/heat/off, so that should define the icons (snowflake, fire, thermostat).
Then the hvac_action defines cooling, heating, idle. This should match the color: cooling: blue, heating: orange, idle: grey.
Does that sound logical to you?
So for example, you could have a mode: cool & hvac_action: idle --> icon: grey snowflake. When you have mode: cool & hvac_action: cooling --> icon: blue snowflake.
Now I see it like this (in my understanding it should have had a grey fire icon because the mode is "heat" and the hvac_action is "idle"):

And would it also be possible to add the climate state text next to the hvac_action?
Would be great to see in the text: Inactive - Heat - auto
First: hvac_action (heating, cooling, idle)
Second: state of climate (cool, heat, off)
Third: preset (auto for me)
Like that it's also mentioned in the standard climate entity:

Many thanks!
Expected Behavior
No response
Steps To Reproduce
No response
Environment
- OS:HA OS 8.1
- Node:
- Version: Core 2022.5.5
- Hassio:

Anything else?
No response

For my understanding: the state (mode) of the climate entity is cool/heat/off, so that should define the icons (snowflake, fire, thermostat). Then the hvac_action defines cooling, heating, idle. This should match the color: cooling: blue, heating: orange, idle: grey. Does that sound logical to you? So for example, you could have a mode: cool & hvac_action: idle --> icon: grey snowflake. When you have mode: cool & hvac_action: cooling --> icon: blue snowflake.
Now I see it like this (in my understanding it should have had a grey fire icon because the mode is "heat" and the hvac_action is "idle")

I understand what you are saying.  Let me provide some further clarity as to how it's actually design.  Currently it's designed to show the action icon if your device supports the hvac_action attribute (not all do) else it shows the state icon.  The part in your suggestion that doesn't work (or at least that I'm not fond of) is when you have a device that supports auto or heat/cool mode.  In that mode currently it displays the thermostat icon and changes to the hvac_action icon if available.  With what describe the auto or heat/cool icon would be displayed always and just the color would change.
I'm not sure one way is better than the other, but I'm also not sure what might be better than either of them.
P.S.  The action, stat/mode, preset string was implemented in #18, but has not yet been released as I ponder your other suggestion.

Let me provide some further clarity as to how it's actually design.
Many thanks for clarification 👍

Currently it's designed to show the action icon if your device supports the hvac_action attribute (not all do) else it shows the state icon.
Absolutely great you thought about that. It's a really nice feature. Indeed, I have 1 climate entity which doesn't have the hvac_action and it nicely showed the icon and colors. I would absolutely keep that.

The part in your suggestion that doesn't work (or at least that I'm not fond of) is when you have a device that supports auto or heat/cool mode.
You're totally right on that :-). I didn't take that into account.
Would it be an idea (don't know if it's technically difficult or not) that in case there is an "auto" or "heat/cool" mode active that you set the icon and color depending on the hvac_action? And in case there is another mode active than "auto" or "heat/cool" (for example heat, cool or off) it takes the icon from the mode and the color from hvac_action?

Hey there,
Thank you for your great Work. I'm not quite sure if this is related or if I should open a new Issue.
When I set my Thermostats on Auto there is no visualization for the set Temperature.
In heating mode it looks as it should like this:

This is how it looks in Auto:

@LucaOverflow Yes, please open a new issue if you don't mind.  Also include a screen shot of your device from the developer tools, so I can see the state and attributes when it's not functioning correctly.

These issues have been resolved in v1.8.8-thermostat.0


Switch all component build to rollup

With #147 in place, and incoming new way to register global resources via https://github.com/aurelia/framework/pull/858 , it's now possible to distribute every ux package in a single file., and it's more desirable to to do, for build pref, runtime startup perf, size reasons.
Rollup is a good bundler for this, and it will also make the build setup very simple.
Thoughts ? @ZHollingshead @EisenbergEffect

I like the idea of this. Is this one file overall per component or one file per format? (i.e. one for AMD, one for CommonJS, one for system)

it will be one file overall per module type (amd, commonjs ...) , like what we did with core.

Alright, I think this will be fine then. We should have the packages and core synced up anyways as far as the build method.

@bigopon This can be closed right?

Yes, Rollup, while gives a lot of benefits related to distribution, limits the consumption of a component library that distributes custom element (ex: CSS autoprefixing).
Closing this as we went for the middle way.


Mem leak fixed for garbage collector

NOTE: If you see this PR and if you review it then do not directly merge it, instead do a "Squash and merge". You can write commit message as, "Memory leak fixed for garbage collector".


Need to escape ampersand signs in PLSQL

I fixed this in your script.  You need double && instead of single &.


bwDraco: Blacklist pure\W?force\W?x

bwDraco requests the blacklist of the keyword pure\W?force\W?x. See the Metasmoke search here

Note that "pure force x" is on the watch list and needs to be removed from watch.

!!/approve


A11y_SQLAzureDataStudio_Extension_Install-UninstallExtension_ScreenReader: Heading content not reading as heading by screen reader.

“Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
#A11yMAS; #A11yTCS; #SQL Azure Data Studio; #DesktopApp; #MacOs; #Benchmark; #A11y_SQLAzureDataStudioBenchmark; #A11ySev2; #MAS2.4.6; #MAS1.3.1; #VoiceOver;
Environment Details:
Version: 1.16.0-insider
Commit: 506c6a5
Date: 2020-02-17T05:43:18.399Z
VS Code: 1.42.0
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363
Additional Details:
Screen reader: Voice Over
MAS reference: MAS2.4.6, MAS1.3.1
Repro Steps:
Launch Azure Data Studio.
From the left menu, click the 'Extensions' icon to open the Extension Manager.
Choose any extension from the library.
Click the green 'Install' button to install.
Launch Voice Over screen reader and navigate to the heading 'Admin pack for SQL Server'.
Check if all headings are announced by screen reader.
Actual:
Heading content is not announced by Voice Over as heading to screen reader users present at the top of the screen. "Admin pack for SQL Server".
Expected:
Heading content should be announced as heading by Voice Over.
User Impact:
Screen reader users might miss the heading content present on the screen.
Attachment link reference:
9411_A11y_SQLAzureDataStudio_Extension_Install-UninstallExtension_ScreenReader.zip

@v-atkulk this is an upstream issue, you can also reproduce it with VSCode, please file the issue in vscode github repo.

@v-atkulk We're marking this bug for Exclusion. Please work with @Alexandria-R or another SME to review.
This is an upstream bug with VS Code and we filed a bug in their repo here: https://github.com/microsoft/vscode/issues/94955
Importance of Experience: somewhat important
Extensions are a crucial part of using Azure Data Studio, but visiting the extension manager is likely not an everyday (or even every-week) action. The extension manager is where users can browse, install, uninstall, and disable extensions — which may be necessary every once in a while, but infrequently.
Quality of Experience: Not impacted
Since users must select "Admin Pack for SQL Server" from a list to open this page, even if the title of the newly opened page is identified as text content, the user would likely be able to deduce that the text "Admin Pack for SQL Server" is the heading, since it matches the name of the extension they just selected. The same logic applies for all extensions.
AAT Conformance Doc: https://cela-ra-aat-prod.azurewebsites.net/#/workflow/ee5c9007-47f4-4fcb-a4d7-a998a617edde?tab=default

@hannahqin I am closing this one since this is showing up on our s360 dashboard.

https://user-images.githubusercontent.com/91586743/218713793-ff3d4166-de15-4192-bd1a-235325bc3eb4.mov
Verified the issue Now it is not reproducing.
Git Hub Tags: #Closed;

GitHubTags:#BM-TCS-SQLADS-MAC-Feb2020;


[o2k] add defaults for services & upstreams

This adds support for 2 keys; x-kong-service-defaults, and x-kong-upstream-defaults.
This allows to configure specific techincal properties for the generated Kong configuration that cannot be derived from the OAS spec itself.
for example:
openapi: "3.0.0"
info:
  title: Simple API overview
  version: v2
servers:
  - url: http://backend.com/path
x-kong-service-defaults:
  retries: 10
  connect_timeout: 30000
  write_timeout: 30000
  read_timeout: 30000
x-kong-upstream-defaults:
  hash_on: ip
  healthchecks:
    passive:
      unhealthy:
        http_failures: 3
        tcp_failures: 3
        timeouts: 3
paths:
  /:
    x-kong-name: x-kong-name-override-at-path-item
    get:
      x-kong-name: x-kong-name-override-at-method
      operationId: listVersionsv2
      summary: List API versions

closes INS-653
EDIT: also added a replacement commit for PR #3273, which fixes INS-122

these commits were added through #3273 , closing this.


Include config option to list stopped containers.

Hi!
I noticed that the initial code was not listing my stopped containers, so I thought I could push a quick fix to correct that. Now you can set the setting "listStoppedContainers":false on config file to list stopped containers.
Default is false.

I just read https://github.com/dunklesToast/DockerKit/issues/2 and it looks like I have to change some things in the publishService function. I'll merge this PR now, will fix the issues I brought up and then also fix #2.

I just thought about this and imo it should publish all containers by default, not just running ones. We could add a blacklist to the config with containers that should never be listed in HomeKit.


Hidden select option

Is your feature request related to a problem? Please describe.
In my application I have a scenario where a select form control has a null default value that should not be selectable by the user and also not visible among the options, but it should act as a placeholder until the user picks a value
Describe the solution you'd like
My proposed solution would be to add a "hidden" prop in the select option interface to enable the "hidden" attribute of the option element. I think this should apply to the placeholder too so a "hidePlaceholder" prop should set the hidden attribute to the placeholder option (having the disable attribute on the placeholder would be nice too) so that it won't be visible among the available options
// select field props

placeholder: 'I am the placeholder',
hidePlaceholder: true // this won't show the placeholder among the options,
disablePlaceholder: true // with the previous prop set to false, this would prevent the placeholder to be selected although visible as an option
placeholderValue : null // this overrides the placeholder ngValue to null instead of undefined,
options: [{
     label: 'alternative placeholder',
     value: null,
     hidden: true, // still needed as an enchancement
     disabled: true
}]

Describe alternatives you've considered
As seen in the snippet an alternate way to have a hidden placeholder that works on the "null' value instead of 'undefined' would be to just have the hidden prop for each option along side the disabled one

I think that a specific use-case which is not something that we're willing to support instead I would suggest to use a custom type.


Add RNN for batch normalization

What changes were proposed in this pull request?
Add RNN batch norm support
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
Quick checklist
The following checklist helps ensure your PR is complete:

[ X] Eclipse Contributor Agreement signed, and signed commits - see IP Requirements page for details
[X ] Reviewed the Contributing Guidelines and followed the steps within.
[ X] Created tests for any significant new code additions.
[X ] Relevant tests for your changes are passing.

Thank you for taking care of this. When will this changes be reflected in the Maven snapshot?

thanks for the update

@joel-a  snapshots should be in there now. I've also ensure we have automation built in  for publishing snapshots every other day to get around ossrh auto purging snapshots every 3 days. We  will also be doing a service release here within the next few weeks to address some of the other changes the community found from doing the post github actions migration. Let us know if you have any other issues.

@agibsonccc  I'm seeing a new error that I believe is related to this issue. It seems like the batch normalization layer is not outputting the correct type. Here's the error message:
Exception in thread "main" java.lang.IllegalStateException: Invalid input for 1D CNN layer (layer name = "conv1d_16"): expect RNN input type with size > 0. Got: InputTypeFeedForward(10,NWC)
	at org.deeplearning4j.nn.conf.layers.Convolution1DLayer.setNIn(Convolution1DLayer.java:104)
	at org.deeplearning4j.nn.conf.ComputationGraphConfiguration.getLayerActivationTypes(ComputationGraphConfiguration.java:554)
	at org.deeplearning4j.nn.conf.ComputationGraphConfiguration.addPreProcessors(ComputationGraphConfiguration.java:458)
	at org.deeplearning4j.nn.modelimport.keras.KerasModel.getComputationGraphConfiguration(KerasModel.java:613)
	at org.deeplearning4j.nn.modelimport.keras.KerasModel.getComputationGraph(KerasModel.java:635)
	at org.deeplearning4j.nn.modelimport.keras.KerasModel.getComputationGraph(KerasModel.java:624)
	at org.deeplearning4j.nn.modelimport.keras.KerasModelImport.importKerasModelAndWeights(KerasModelImport.java:168)

Adding an activation layer to the model after the batch normalization layer triggers this error:
[batchNormError2.zip](https://github.com/eclipse/deeplearning4j/files/6638978/batchNormError2.zip)

in_layer = Input((25, 25,))
x = Conv1D(filters=10, kernel_size=2)(in_layer)
x = BatchNormalization()(x)
x = Activation('relu')(x)
out_layer = Conv1D(512, 3, strides=1,
                          dilation_rate=3,
                          padding='same',
                          activation='linear')(x)
model = Model(in_layer, out_layer)
model.save("batchNormError2.h5")

DL4j code to import model:
String modelPath = "batchNormError2.h5";
ComputationGraph model = KerasModelImport.importKerasModelAndWeights(modelPath);

I'm including this simple test model here for convenience:
batchNormError2.zip
Thank you very much for the great work and attention to this issue.

@joel-a https://github.com/eclipse/deeplearning4j/pull/9365


chore: update manifest to include missing packages

Fixes https://github.com/open-telemetry/opentelemetry-js-contrib/pull/920#pullrequestreview-894051020

Thanks! so when adding new packages, the manifest should be updated as well as the release-please-config.json file, right? If so I'll update the amqplib PR

if you leave it off it uses 1.0.0 as the default first version for release. this might be configurable.


HIP6: Reward onramp for packets

For discussion of https://github.com/helium/HIP/pull/20
Latest rendered view: https://github.com/helium/HIP/blob/60ba6cb841d3ef66020a8504070f7016d20ef5ab/0006-reward-ramp-for-packets.md

Closing since this is technically still just a draft HIP


Give peterhornyack Compute Engine admin access

https://cloud.google.com/iam/docs/understanding-roles#compute-engine-roles

Role should be a string instead of a list.


Install the Ubuntu font family

We should automagically snag and put https://design.ubuntu.com/font/ in the right place.

Check how we copy the wallpaper for the syntax, but tldr copy the right files into the right place, it will be in /var/home/$USER/ so remember to not assume ~/.
Also to fit in with the other styles make it so the default only does the ubuntu font but leave a place where people can add their own goodies (and recommend your favorite ones).


Comment on the last line is moved on the line above

Considering this yml input
environment:
  ### SESSION START ###
  A: "true"
  B: "true"
  ### SESSION END ###

if the document is parsed and then printed out the result is not the same, but the comment goes on the same line as 'B'.
const file = fs.readFileSync('./test/input/config.yml', 'utf8')
const doc = YAML.parseDocument(file)
doc.toString()

output
environment:
  ### SESSION START ###
  A: "true"
  B: "true" ### SESSION END ###

Expected behaviour
I would like to preserve the positioning of the comment. There is a way to achieve it?
Versions:

Environment:
Node.js: v12.14.0
yaml: 2.0.0-5

Are you sure that this is happening with the example that you posted above? I'm not able to replicate this behaviour:
const doc = YAML.parseDocument(`environment:
  ### SESSION START ###
  A: "true"
  B: "true"
  ### SESSION END ###
`)

doc.toString()
> 'environment:\n' +
  '  ### SESSION START ###\n' +
  '  A: "true"\n' +
  '  B: "true"\n' +
  '  ### SESSION END ###\n'

I don't doubt that end-comment placement is problematic, so this may well be a dupe of #244.

Oh yeah, my bad I haven't reported an important detail apparently: The empty line at the end of the input.
const doc = YAML.parseDocument(`environment:
  ### SESSION START ###
  A: "true"
  B: "true"
  ### SESSION END ###

`);

doc.toString()
> 'environment:\n' +
  '  ### SESSION START ###\n' +
  '  A: "true"\n' +
  '  B: "true" ### SESSION END ###\n'

Here the project to reproduce it: https://stackblitz.com/edit/test-yml
This use case is useful for me when there are ymls more complex and space and line comment can be used to gain more clarity.
environment:
  ### SESSION START ###
  A: "true"
  B: "true"
  ### SESSION END ###

  ### ANOTHER SESSION START ###
  C: "true"
  D: "true"
  ### ANOTHER SESSION END ###

like this example above.


Investigate sysroot configuration with Xcode's clang

See https://github.com/Microsoft/azure-pipelines-image-generation/issues/898

https://github.com/gradle/gradle/issues/9359
I had reported this to Gradle here as well, with full logs.

See https://github.com/gradle/gradle/issues/9359 for the complete logs to help the investigation.

I asked on slack, but never got an answer. Why does gradle even handle the sysroot configuration. No other build system I have ever used has done this, and instead just calls the compiler directly. That seems to work fine for all the other build systems.

Also for a workaround, here is a simple model rule that removes all the sysroot things from mac.
        @Mutate
        @CompileStatic
        void removeMacSystemIncludes(ModelMap<Task> tasks, BinaryContainer binaries) {
            binaries.each {
                if (!(it instanceof NativeBinarySpec)) {
                    return
                }
                NativeBinarySpec nativeBin = (NativeBinarySpec)it
                if (nativeBin.targetPlatform.operatingSystem.isMacOsX()) {
                    nativeBin.tasks.withType(AbstractNativeSourceCompileTask) { AbstractNativeSourceCompileTask compileTask->
                        compileTask.getSystemIncludes().setFrom()
                    }
                }
            }
        }

Modelling the sysroot allow for a better understanding of what the user's intention is and provide good defaults. We want to prefer stronger modelling and understanding than leaving everything to the user which requires more configuration to get something working.

Ok. We will likely keep the rule posted above then, as we would prefer the compiler provide the defaults, rather then gradle choosing the wrong defaults.


[Bugs?] Duplicate code above class name

Hi giginet! I found small issue. I would be very grateful if you could resolve this 🙏
Issue detail
When the script is run with a comment a few lines above the class in the test case, there seems to be a problem with duplication.
Method
mint
Sample code
original source code
@testable import FooService
import XCTest

// swiftlint:disable type_body_length

final class FooServiceTestCases: XCTestCase {

after run swiftTestingRevolutionary
// swiftlint:disable type_body_length

@Suite

// swiftlint:disable type_body_length // here is duplicated 😭

struct FooServiceTestCases {

Treating leading trivia is too complex. I'll add the test case!


Props, config and different image types

Internally, the detection algorithm does not care much about the pixel values. Instead, it produces its detections based on pixel intensities, i.e. how "shiny" a pixel appears to be. Therefore, in case of an RGB or BGR image, we can simply take one its channels.

Due to "correctness" I think we'll have to convert to Grayscale. Picking just any R/G/B channel on its own, won't produce good results when tags are colored, tinted, not uniformly lit, etc...

Due to "correctness" I think we'll have to convert to Grayscale. Picking just any R/G/B channel on its own, won't produce good results when tags are colored, tinted, not uniformly lit, etc...

There is also image_u8x3_t in the AprilTag library which we can use for planar RGB types @lnotspotl