AppScope trace logging level crashes processes

LD_PRELOAD=lib/linux/x86_64/libscope.so SCOPE_LOG_LEVEL=trace ps -ef
This segfaults on the master branch.  (I happen to be running on an x86_64 on a glibc system)

The issue can be reproduced even with a simple Hello world case:
#include <stdio.h>
int main() {
   printf("Hello, World");

   return 0;
}

SCOPE_LOG_LEVEL=trace ldscope ./main
## we are not able to see "Hello world" message on stdout
echo $?
## exit status should be 0 but it is equal 1

Reported Segfault is caused by stack overflow (see gdb --args ldscope ./main)
Backtrace log:
#19495 0x00007ffff74b4835 in _IO_new_file_xsputn (n=67, data=<optimized out>, f=<optimized out>) at libioP.h:948
#19496 _IO_new_file_xsputn (f=0x5555555594a0, data=<optimized out>, n=67) at fileops.c:1197
#19497 0x00007ffff74a8541 in __GI__IO_fwrite (buf=0x7fffffffa660, size=1, count=67, fp=0x5555555594a0) at libioP.h:948
#19498 0x00007ffff76df7c5 in transportSend (trans=0x55555555c150, msg=0x7fffffffa660 "Scope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\n", len=67) at src/transport.c:1262
#19499 0x00007ffff76dfb13 in logSend (log=0x55555555c0d0, msg=0x7fffffffa660 "Scope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\n", mlevel=CFG_LOG_TRACE) at src/log.c:46
#19500 0x00007ffff76af1e9 in scopeLog (level=CFG_LOG_TRACE, format=0x7ffff7a2739d "fd:%d %s") at src/wrap.c:4866
#19501 0x00007ffff76b4e67 in doWrite (fd=999, initialTime=22989404688954, success=1, buf=0x55555555c530, bytes=132, func=0x7ffff7a261a0 "__write_libc", src=BUF, cnt=0) at src/state.c:2123
#19502 0x00007ffff76a40fc in __write_libc (fd=999, buf=0x55555555c530, size=132) at src/wrap.c:2596
#19503 0x00007ffff74b400d in _IO_new_file_write (f=0x5555555594a0, data=0x55555555c530, n=132) at fileops.c:1176
#19504 0x00007ffff74b5ad1 in new_do_write (to_do=132, data=0x55555555c530 "Scope: main(pid:40): [2021-11-25 14:07:46.096] fd:3 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main6.40\nclf1", fp=0x5555555594a0) at libioP.h:948
#19505 _IO_new_do_write (to_do=132, data=0x55555555c530 "Scope: main(pid:40): [2021-11-25 14:07:46.096] fd:3 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main6.40\nclf1", fp=0x5555555594a0) at fileops.c:426
#19506 _IO_new_do_write (fp=0x5555555594a0, data=0x55555555c530 "Scope: main(pid:40): [2021-11-25 14:07:46.096] fd:3 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main6.40\nclf1", to_do=132) at fileops.c:423
#19507 0x00007ffff74b4835 in _IO_new_file_xsputn (n=67, data=<optimized out>, f=<optimized out>) at libioP.h:948
#19508 _IO_new_file_xsputn (f=0x5555555594a0, data=<optimized out>, n=67) at fileops.c:1197
#19509 0x00007ffff74a8541 in __GI__IO_fwrite (buf=0x7fffffffba80, size=1, count=67, fp=0x5555555594a0) at libioP.h:948
#19510 0x00007ffff76df7c5 in transportSend (trans=0x55555555c150, msg=0x7fffffffba80 "Scope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\n", len=67) at src/transport.c:1262
#19511 0x00007ffff76dfb13 in logSend (log=0x55555555c0d0, msg=0x7fffffffba80 "Scope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\n", mlevel=CFG_LOG_TRACE) at src/log.c:46
#19512 0x00007ffff76af1e9 in scopeLog (level=CFG_LOG_TRACE, format=0x7ffff7a2739d "fd:%d %s") at src/wrap.c:4866
#19513 0x00007ffff76b4e67 in doWrite (fd=999, initialTime=22989404683103, success=1, buf=0x55555555c530, bytes=65, func=0x7ffff7a261a0 "__write_libc", src=BUF, cnt=0) at src/state.c:2123
#19514 0x00007ffff76a40fc in __write_libc (fd=999, buf=0x55555555c530, size=65) at src/wrap.c:2596
#19515 0x00007ffff74b400d in _IO_new_file_write (f=0x5555555594a0, data=0x55555555c530, n=65) at fileops.c:1176
#19516 0x00007ffff74b5ad1 in new_do_write (to_do=65, data=0x55555555c530 "Scope: main(pid:40): [2021-11-25 14:07:46.096] fd:3 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main6.40\nclf1", fp=0x5555555594a0) at libioP.h:948
#19517 _IO_new_do_write (to_do=65, data=0x55555555c530 "Scope: main(pid:40): [2021-11-25 14:07:46.096] fd:3 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main6.40\nclf1", fp=0x5555555594a0) at fileops.c:426
#19518 _IO_new_do_write (fp=0x5555555594a0, data=0x55555555c530 "Scope: main(pid:40): [2021-11-25 14:07:46.096] fd:3 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.096] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main(pid:40): [2021-11-25 14:07:46.097] fd:999 __write_libc\nScope: main6.40\nclf1", to_do=65) at fileops.c:423
#19519 0x00007ffff74b4835 in _IO_new_file_xsputn (n=65, data=<optimized out>, f=<optimized out>) at libioP.h:948
#19520 _IO_new_file_xsputn (f=0x5555555594a0, data=<optimized out>, n=65) at fileops.c:1197
#19521 0x00007ffff74a8541 in __GI__IO_fwrite (buf=0x7fffffffcea0, size=1, count=65, fp=0x5555555594a0) at libioP.h:948
#19522 0x00007ffff76df7c5 in transportSend (trans=0x55555555c150, msg=0x7fffffffcea0 "Scope: main(pid:40): [2021-11-25 14:07:46.096] fd:3 __write_libc\n", len=65) at src/transport.c:1262
#19523 0x00007ffff76dfb13 in logSend (log=0x55555555c0d0, msg=0x7fffffffcea0 "Scope: main(pid:40): [2021-11-25 14:07:46.096] fd:3 __write_libc\n", mlevel=CFG_LOG_TRACE) at src/log.c:46
#19524 0x00007ffff76af1e9 in scopeLog (level=CFG_LOG_TRACE, format=0x7ffff7a2739d "fd:%d %s") at src/wrap.c:4866
#19525 0x00007ffff76b4e67 in doWrite (fd=3, initialTime=22989404679599, success=1, buf=0x555555592880, bytes=60, func=0x7ffff7a261a0 "__write_libc", src=BUF, cnt=0) at src/state.c:2123
#19526 0x00007ffff76a40fc in __write_libc (fd=3, buf=0x555555592880, size=60) at src/wrap.c:2596
#19527 0x00007ffff74b400d in _IO_new_file_write (f=0x555555591170, data=0x555555592880, n=60) at fileops.c:1176
#19528 0x00007ffff74b5ad1 in new_do_write (to_do=60, data=0x555555592880 "  protect memory 0x7ffff7533000 (size=4096, prot=read,exec)\ne,exec) <- 0x7ffff75331d0 (size=5)\nsz=1000\n", fp=0x555555591170) at libioP.h:948
#19529 _IO_new_do_write (to_do=60, data=0x555555592880 "  protect memory 0x7ffff7533000 (size=4096, prot=read,exec)\ne,exec) <- 0x7ffff75331d0 (size=5)\nsz=1000\n", fp=0x555555591170) at fileops.c:426
#19530 _IO_new_do_write (fp=0x555555591170, data=0x555555592880 "  protect memory 0x7ffff7533000 (size=4096, prot=read,exec)\ne,exec) <- 0x7ffff75331d0 (size=5)\nsz=1000\n", to_do=60) at fileops.c:423
#19531 0x00007ffff74b35f8 in _IO_new_file_sync (fp=0x555555591170) at fileops.c:812
#19532 0x00007ffff74a7546 in __GI__IO_fflush (fp=0x555555591170) at libioP.h:948
#19533 0x00007ffff7762fdc in funchook_log () from /tmp/libscope-web/libscope.so
#19534 0x00007ffff77647c3 in funchook_unprotect_end () from /tmp/libscope-web/libscope.so
#19535 0x00007ffff776317a in funchook_install () from /tmp/libscope-web/libscope.so
#19536 0x00007ffff769c949 in initHook (attachedFlag=0) at src/wrap.c:1413
#19537 0x00007ffff769ce94 in init () at src/wrap.c:1557

With the interception of __write_libc we call doWrite and results in calling
https://github.com/criblio/appscope/blob/28c5f7b22b1e77a74011a51c29169f37fa271f50/src/state.c#L2123
Calling scope_log results in calling transportSend
https://github.com/criblio/appscope/blob/28c5f7b22b1e77a74011a51c29169f37fa271f50/src/transport.c#L1262
which results calling in __write_libc and cycle starts again results in a stack overflow.
As a reminder: Default Log destination path is file.
@jrcheli
You will not observe segfault if you change the log destination path:
LD_PRELOAD=lib/linux/x86_64/libscope.so SCOPE_LOG_LEVEL=trace SCOPE_LOG_DEST=tcp://localhost:8125 ps -ef

QA Instructions:
Observe that you will be able to see events and no segfault appeared during the following command:
LD_PRELOAD=libscope.so SCOPE_LOG_LEVEL=trace top

#365 seems similar in nature, maybe a similar approach/solution could be used there too.

I'm just capturing my thoughts while I review this...
At first glance, my worry was that this might not be a "general enough" solution...
My concern was that transportSend() is calling g_fn.fwrite() which by our own policy should be "safe" (should not allow a reentrant path).  So what's going on here that's special?  The answer is that the "special part" is (that inside of initHook()) we're funchooking glibc's (and pthread's) __write function.  So, even though we've been careful to avoid calling anything that we interpose in our library directly, the funchook is allowing us to still intercept our own g_fn.fwrite().
Generally we don't funchook things if we can avoid it.  And I guess this is an example of why.  So do we have any other paths that could be reentrant because we're funchooking them?  I think we can get an answer to this by inspecting initHook(), where funchook is configured via funchook_prepare().  Here's the list of things that need consideration at this time:
SSL_read -> (ok because ssl_read_hook is only use)
SSL_write -> (ok because ssl_write_hook is only use)
sendmmsg -> (ok because internal_sendmsg is only use)
syscall -> (ok because scope_syscall is only use)
sendto -> (ok because internal_sendto is only use)
recvfrom -> (ok because internal_recvfrom is only use)
uv_read -> (ok because uv__read_hook is only use)
__write_libc
__write_pthread
The implication is that if we call any of these specific g_fn functions during our own libscope behavior, it might be possible to cause a stack overflow in a similar manner to what has been described above.  So I've included my analysis in parens of all of the other functions that need consideration right now.  So I'm comfortable saying that at this time, __write_libc and __write_pthread are the only things we need to be worried about.  The trick is that these are relatively hard to confirm that we've got covered...

My conclusion right now is that I don't think this is the ideal general fix because of the way we're funchooking __write().
This is ok though, because I can't imagine any unintended side effects of this change, and in the immediate term, this is a clear incremental improvement in the behavior (before this change, we'd crash when SCOPE_LOG_LEVEL=trace is set, and now we won't).
I think the long term ideal general fix would be to statically link in our own libc implementation and use it for everything our library does internally.  This would allow us to separate the functionality of our library (here __write()) from functions which we are interposing from the host program where we're running.  This is being investigated in #508 as "Approach 3", and is actively being worked on right now.


Add Sn prefix to project names in all places

Follow-up of #958 and a sibling issue to https://github.com/foundry-rs/starknet-foundry/issues/998
Our project binaries use sn prefixes in all places, but usages of names with and without prefixes in other places are inconsistent.
E.g. https://github.com/foundry-rs/starknet-foundry/blob/e0bdc7ce715bb2112380c7be8ddc6503e45ee494/crates/cast/src/main.rs#L21
or in docs headings
We should consider if we want to use consistent names in all places.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a web3 developer
How I plan on tackling this issue
I will add sn prefixes in all places that it need to be added

Is this issue still available?

I’d like to help with this.


Add rowspan and colspan to header

STOP
We do not track feature requests through Github. Please use the Spectrum React Table Forum to talk about new ideas and features.

It seems that Spectrum is also now deprecated?  It would have been nice to see what this feature request at least was, so that I can know it isn't something already built into react-table (I'm still learning its capabilities).


_zsh_highlight_widget_up-line-or-history: job table full or recursion limit exceeded

When I use TAB, the terminal will appear ‘_zsh_highlight_widget_up-line-or-history: job table full or recursion limit exceeded’

And when I use the direction key in order to use the history,the terminal will appear '_zsh_highlight_widget_history-search-forward: job table full or recursion limit exceeded'

And under the terminal using copy and paste will appear this kind of situation

And under the terminal using copy and paste will appear this kind of situation

What version of zsh-syntax-highlighting do you use?
Could you please bisect your configuration?  That is, provide a minimal sequence of commands, starting from zsh -f, that still reproduces the problem?  That sequence would probably be a minimized form of your .zshrc.
What does print -r - $widgets[up-line-or-history] print?

I just now noticed: TAB isn't normally bound to up-line-or-history, nor arrows to history-search-forward. So it seems your terminal sends different escape sequences than zle expects.
Anyway, feel free to reopen if you're still seeing the problem.


Some fixes for focus

Connected to https://github.com/vaadin/vaadin-core/issues/105

This change is

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Daemon not Running

[v ] I have read the FAQ.
[ v] I have searched in existing issues.

Environment

OS: win 10 (installed yesterday
scrcpy version: [2.1.1]
installation method: [e.g. manual build, apt, snap, brew, Windows release...]
device model: huawei p30 lite
Android version: [e.g. 12]

Describe the bug
unable to let it work
i'm using an old version till last week on my old pc
get a new pc yesterday ad I can manage to let it work
thanks in advance
Please paste terminal output in a code block.

daemon not running; starting now at tcp:5037
could not read ok from ADB Server
failed to start daemon

waiting for device -
error: cannot connect to daemon

What is the result of adb devices?


Issues found while working with private datasets

Working in private mode (and then changing to public) went smoothly except for a few issues (that I listed below).
In general, the only differences between working with private and public datasets are:

In the dag, private steps need to start with walden-private:// or data-private:// instead of walden:// or data://.
When running the ETL steps, the flag --private needs to be included.

So, when the dataset becomes public, one simply needs to remove the instances of -private in the dag, and re-run the steps.
However, for the grapher step I encountered some issues (probably interconnected, I haven't had time to look into this in detail):

Instead of simply having data-private://grapher I had to use grapher://grapher/... (and then, when making the dataset public, I changed it to data://grapher). Ideally, I suppose data-private://grapher should work, analogous to other data steps.
When still working in private mode, running etl ... --private --grapher failed on this line, so I simply commented out the assertion assert path == dependencies[0].path and then it worked. This issue happens only in private mode.
When running etl ... --private, ETL writes to grapher database (even if the --grapher flag was not used).
While in private mode, I added some variables in the grapher step, but they were not showing up in the grapher admin (also, in my grapher data channel the dataset did not exist). After I made it public, the grapher data step worked as usual (and the additional variables were properly created).
There were some other problems with the approval tool in local grapher, as discussed on this slack thread.

I've added private datasets support in walkthrough and tested it, but weirdly I couldn't replicate any the issues above. Since they're hard to replicate, I'm not gonna dive into them, but rather wait for our next private dataset and see if they reappear (should be much easier to debug then).

Thanks @Marigold. Good idea, maybe some of those issues were caused by something else, it was a bit hectic this time. Next time we need to work in a private dataset we can hopefully have a bit more time to see if there are issues along the process.

Thanks for reporting your troubles here @pabloarosado. I rewrote this to become a tracking issue now, a place we can link any new things that come up for private datasets.
In general, it's better to file small problems as they come up rather than one mega-issue, since otherwise they can be too hard for us to replicate, which makes it harder to help out.
Let me know how it goes on the next private dataset you try!

Thanks @larsyencken you are right. However when dealing with private datasets we may have to keep the code private, so it may not be possible to report issues one by one, and we'll have to wait until publication.

Ah, you're thinking about situations where we have embargoed data, private data that will one day become public. We also can have situations where there is private data that will never become public, unless the upstream provider changes their policy. I can totally understand that you don't want to accidentally break an embargo by pushing code.
So far, we've taken the design choice that even private datasets have public code. If we want to rethink that, we'd probably want to refactor the ETL and separate the small private data pipeline into its own private repo.


Mosquitto 4.1 broken

Someone please fix the Mosquitto 4.1 . It is broken - no messages are being sent. Others are facing the same issue:(

downgrade Mosquitto  to fix. Use the template instead of just deleting it.

Mosquitto issues should be filed on mosquitto issue tracker, not here.
If this is indeed an issue with home assistant, please create a new issue with the issue template filled in.


Try using {{ compiler('c') }} dependency, try 2

See previous attempt #1 and conda/conda-build#2263 for details.

TODO: install build packages in travis.yml before doing the in-place build.


Registering directly to site w/ username and email creates conflict for site-wide username

Registering for an account on the site and providing a username and email address in the account creation form (not using 3rd party auth to register) creates a situation where the user's username is their email address, however when they create a project, the username associated with the project is the username they gave on the input form, not the email address. This means the user cannot see the project they just created.
Perhaps the form should be changed so that there is no separate username - only an email address?

Let's eliminate usernames and only use email addresses for standalone logins.

I have check production and none of my projects would become un-linked by switching to email address as username.


[Desktop] When navigating thru menu, content seems to not be aligned within pages

Steps to Reproduce

Go to https://napari.staging.imaging.cziscience.com/
Locate left side menu and navigate thru it
Pay attention to content

Expected Results
Content should be located in same place within pages
Actual Results
When navigating thru menu, content seems to not be aligned between all pages
https://user-images.githubusercontent.com/63799148/133844347-693d759b-2b49-4675-9cc9-12becb327eb4.mov

This doesn't happen on stable or dev anymore


Cannot add new relation - own relation disabled

Running task using the file and latest develop (7. 9. morning):
Books-v2.csv.zip
Then go to relations step. Click "Link creation". Create link e.g. between author and series. Now I cannot define the link, because "own relation" is disabled:

Solution: For relations, it must be possible to define custom (own) relations, because otherwise it is not possible to create new edges/demonstrate the features of the graph.

Maybe caused by solving #78 .

@tomas-knap You are right, @KataBoku please fix it as soon as possible.

Fixed as of #88 .

Tested on: 72de95488cf87b91f283b9a9a6f905379a61acb5
But still does not work. When I add new edge, dialog appears, but I cannot add own relation:

It is working


completed frequencyRDD with data frames

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/mango-prb/154/
Test FAILed.

Jenkins, test this please.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/mango-prb/155/
Test FAILed.

Jenkins, test this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/mango-prb/156/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/mango-prb/158/
Test PASSed.

Merged build finished. Test PASSed.

Thanks @akmorrow13


Error 429 "Too many requests" when I make a get API request with JWT

Bug description
when I make a protected request from "postman" or my web application, I send it a token(JWT), it shows me the error 429.
Steps to reproduce
for test purposes leave the route unprotected, and without a token the request works.
without token.

with token.

Expected behavior
return 200 OK.
Laravel version
8.82
stancl/tenancy version
3.5

Probably a misconfigured rate limiter?
Not sure why this would be related to the package

the problem is rare, only that the problem arose when installing and configuring the package, also change the speed limiter, apparently the problem occurs when passing an "Authorization" through the header, choose to create a custom jwt, possibly have a conflict with tymon/jwt-auth package.


Fix changelogs lost in docs PR

Summary and Scope
Description:
Changelog for 1.7.1, 2 3 and 4 were lost when moving from readme.md based changelog to new changelog.

Covering this another way.


Refactor UX

Move data processing, searching and state management into a separate web-worker-ready file

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 27
- Added 75

Complexity increasing per file
==============================
- src/js/array-wrap.js  3
- src/js/ui-utils.js  3
- src/js/omt.js  5

Complexity decreasing per file
==============================
+ src/js/app.js  -3

See the complete overview on Codacy


(iflow-immutable): fix conversion return types

toOrderedMap, toOrderedSet

Thanks for making a PR. But the immutable libdefs are deprecated now.
Since 3.8.0 immutable exports flow libdefs. Please use the one that ship with immutable.js


[Material] Add ContentDialog

What would you like to be added:
Investigation needs to be done to see how customizable is the ContentDialog. We would need the ability to customize the "chrome" surrounding the Content part. So the action button areas as well as CornerRadius, etc.
Material style for ContentDialog
UWP:

Material:

Material Guidance:
https://m3.material.io/components/dialogs/overview
For which Platform:

[x] UWP
[x] iOS
[x] Android
[x] WebAssembly
[x] macOS

Anything else we need to know?

todo: m3 style

@kazo0 I believe we will be adding in the option for users to users to invoque Default Button Property


informational: add a document describing the partition layout

People may want details on how the partition layout works, lets provide those details with the UUIDs, labels, etc.

@philips Why did you suggest we document the UUIDs? I think I covered everything else in #427

Closing due to inactivity.


RabbitMQ Management Plugin is not enabled on vms by default

Describe the bug
Have defined the rabbitmq_management plugin in the data.yaml file but for some reason it is not enabled on the vm.
rabbitmq-plugins list rabbitmq_management

Listing plugins with pattern "rabbitmq_management" ...
Configured: E = explicitly enabled; e = implicitly enabled
[  ] rabbitmq_management       3.7.10
[E ] rabbitmq_management_agent 3.7.10`

Expected behavior
That rabbitmq_management plugin will be installed.
Config files
None
Environment
RHEL 7.6
epicli version: [epicli --version]
TBD
Additional context
None

DoD checklist

Changelog

[ ] updated
[ ] not needed

COMPONENTS.md

[ ] updated
[ ] not needed

Schema

[ ] updated
[ ] not needed

Backport tasks

[ ] created
[ ] not needed

Documentation

[ ] added
[ ] updated
[ ] not needed

[ ] Feature has automated tests
[ ] Automated tests passed (QA pipelines)

[ ] apply
[ ] upgrade
[ ] backup/restore

[ ] Idempotency tested
[ ] All conversations in PR resolved

Needs to be verified if still an issue.


DHO My Profile - My Organizations Widget (#268)

https://github.com/hypha-dao/dho-web-client/issues/268
@leonieherma1 Please note there should be a new ticket for reading the logo of DHO from the backend as that is not ready on the backend part, so there is the placeholder currently. Also what happens when the person is the member of many DHO's ? Do we show all or do we have pagination? The current design is not covering that.

#268
@leonieherma1 Please note there should be a new ticket for reading the logo of DHO from the backend as that is not ready on the backend part, so there is the placeholder currently. Also what happens when the person is the member of many DHO's ? Do we show all or do we have pagination? The current design is not covering that.

Currently the logos will be uploaded manually when creating new dhos. Later there will be a dho creation wizard where users can upload a logo when creating a new dho. So placeholder is fine for now.
The widget should have a "see more" button (like the other widgets on homepage. And then expand if there is more than 3 DHOs.
Thanks


Four-Square animation added

Title and Issue number

I have added the project .Can it be merged now?
Close #4426

Checklist:

[X] I have mentioned the issue number in my Pull Request.
[] I have commented my code, particularly in hard-to-understand areas
[] I have created a helpful and easy to understand README.md

@MohitGupta121 ,@TusharKesarwani Please review my PR.


Modified the code to functional component

@satisshhhhhh you need to sign the Plone Contributor Agreement in order to merge this pull request.
Learn about the Plone Contributor Agreement: http://docs.plone.org/develop/coredev/docs/contributors_agreement_explained.html

@satisshhhhhh please read our contributing guidelines and follow all their directions.

https://6.docs.plone.org/contributing/index.html
https://6.docs.plone.org/volto/developer-guidelines/contributing.html

This PR is not OK.

Not opened in Volto repository
No Contributor Agreement.
Do not delete the docstrings.

Closing.


AKS NetworkPolicy is not supported

Rancher v2.3.6
Unable to create AKS cluster with advanced network config with azure and calico

The full error is as follows:
This cluster is currently Provisioning; areas that interact directly with it will not be available until the API is ready.
Containerservice.ManagedClustersClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="NetworkPolicyNotSupported"
Message="NetworkPolicy is not supported (only azure and calico are supported)" Target="networkProfile.networkPolicy"

For reference this works just fine so I know its not azure
az aks create --resource-group {resGrp} --name {aks} --generate-ssh-keys --aad-server-app-id {server_app_id} --aad-server-app-secret {server_app_secret} --aad-client-app-id ${client_app_id} --aad-tenant-id ${tenantId} --network-plugin azure --dns-name-prefix "${resGrp}-dns"
–vnet-subnet-id ${subnet_id} --docker-bridge-address <IP_ADDRESS>/16 --dns-service-ip $dns_service_ip --service-cidr $service_cidr `
–subscription $azureSubscriptionID --location eastus --kubernetes-version 1.16.7 --node-count 1 --node-vm-size Standard_D2s_v3 --network-policy calico

Useful
Info

Versions
Rancher v2.3.6 UI: v2.3.40

Route
nodes.node-templates

Do you get the same error from the CLI when you use --network-policy Calico at the end? (to root cause this to case sensitivity of the network-policy value)

By CLI assume you mean AzureCli (az aks create)?  It works just fine as posted above (--network-plugin azure and --network-policy calico).  I have not tried it with upper case 'Calico', I just used lower case because that's what was in Azure Docs.

but I can run a test with upper case

It does not like upper case 'Calico'
Operation failed with status: 'Bad Request'. Details: NetworkPolicy is not supported (only azure and calico are supported)

It looks like this is what Rancher is trying to use (View in API) "networkPolicy": "Calico"
That will NOT work if its sending uppercase

I was able to hack at the config in "View in API" and force it to lower case, (and it did not like Null for Tags), then it worked

I have the same, I think the culprit is in this line https://github.com/rancher/ui/blob/da5ef3345dedfba9031d2f8f3fb7511df2fe4840/lib/shared/addon/components/cluster-driver/driver-azureaks/component.js#L21
I would love to submit a PR myself, but can anyone point me to a doc to build rancher for testing? thanks!

@westlywright can we also backport this into 2.4? I left it into the 2.5 milestone due to where we are in the release.

Reproduced the issue with Rancher v2.4.8

Create a AKS cluster with advance settings - Network Plugin : azure, Network Policy: Calico and selecting a Virtual network

Cluster provisioning fails with the error below:
This cluster is currently Provisioning; areas that interact directly with it will not be available until the API is ready.

Containerservice.ManagedClustersClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="NetworkPolicyNotSupported" Message="NetworkPolicy is not supported (only azure and calico are supported)" Target="networkProfile.networkPolicy"


DynamoDB2 update does not work with multiple/complex expression attribute values

DynamoDB updates do not work with all possible expression attribute values.
Code Snippet
This code snippet works exactly as written against the real DynamoDB (as long as you sleep a few seconds between table creation and item insertion). However, it breaks in moto:
import boto3
import moto

@moto.mock_dynamodb2()
def update_does_not_work():
    dynamo_client = boto3.client('dynamodb')

    # Create table - works fine.
    dynamo_client.create_table(
        AttributeDefinitions=[{'AttributeName': 'SHA256', 'AttributeType': 'S'}],
        TableName='TestTable',
        KeySchema=[{'AttributeName': 'SHA256', 'KeyType': 'HASH'}],
        ProvisionedThroughput={'ReadCapacityUnits': 5, 'WriteCapacityUnits': 5}
    )

    # Update item - does not work. "ValueError: too many values to unpack"
    dynamo_client.update_item(
        TableName='TestTable',
        Key={'SHA256': {'S': 'sha-of-file'}},
        UpdateExpression=(
            'SET MD5 = :md5,'
            'MyStringSet = :string_set,'
            'MyMap = :map'  # Maps string to StringSet of strings.
        ),
        ExpressionAttributeValues={
            ':md5': {'S': 'md5-of-file'},
            ':string_set': {'SS': ['string1', 'string2']},
            ':map': {'M': {'EntryKey': {'SS': ['thing1', 'thing2']}}}
        }
    )

I suspect that there is an error in the update parsing logic. Dynamo item updates can be really difficult to wrangle.
Stack Trace
Traceback (most recent call last):
  File "poc.py", line 35, in <module>
    update_does_not_work()
  File "/usr/local/lib/python2.7/site-packages/moto/core/models.py", line 71, in wrapper
    result = func(*args, **kwargs)
  File "poc.py", line 30, in update_does_not_work
    ':map': {'M': {'EntryKey': {'SS': ['thing1', 'thing2']}}}
  File "/usr/local/lib/python2.7/site-packages/botocore/client.py", line 253, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/usr/local/lib/python2.7/site-packages/botocore/client.py", line 530, in _make_api_call
    operation_model, request_dict)
  File "/usr/local/lib/python2.7/site-packages/botocore/endpoint.py", line 141, in make_request
    return self._send_request(request_dict, operation_model)
  File "/usr/local/lib/python2.7/site-packages/botocore/endpoint.py", line 170, in _send_request
    success_response, exception):
  File "/usr/local/lib/python2.7/site-packages/botocore/endpoint.py", line 249, in _needs_retry
    caught_exception=caught_exception, request_dict=request_dict)
  File "/usr/local/lib/python2.7/site-packages/botocore/hooks.py", line 227, in emit
    return self._emit(event_name, kwargs)
  File "/usr/local/lib/python2.7/site-packages/botocore/hooks.py", line 210, in _emit
    response = handler(**kwargs)
  File "/usr/local/lib/python2.7/site-packages/botocore/retryhandler.py", line 183, in __call__
    if self._checker(attempts, response, caught_exception):
  File "/usr/local/lib/python2.7/site-packages/botocore/retryhandler.py", line 251, in __call__
    caught_exception)
  File "/usr/local/lib/python2.7/site-packages/botocore/retryhandler.py", line 269, in _should_retry
    return self._checker(attempt_number, response, caught_exception)
  File "/usr/local/lib/python2.7/site-packages/botocore/retryhandler.py", line 317, in __call__
    caught_exception)
  File "/usr/local/lib/python2.7/site-packages/botocore/retryhandler.py", line 223, in __call__
    attempt_number, caught_exception)
  File "/usr/local/lib/python2.7/site-packages/botocore/retryhandler.py", line 359, in _check_caught_exception
    raise caught_exception
ValueError: too many values to unpack

Environment
I'm running Python 2.7 on Mac OS X. Moto is installed with pip:
$ pip show moto
Version: 0.4.31
Location: /usr/local/lib/python2.7/site-packages

Same issue FWIW. Only expression i'm using is:
UpdateExpression="SET crontab = list_append(crontab, :i)",
        ExpressionAttributeValues={
            ':i': crontab,
        },

I had quite an awkward one:
table.update_item(
          Key={'entity': 'cycle', 'id': 'cycle-id-1'},
          UpdateExpression="SET nominations = :nominationIds",
          ExpressionAttributeValues={':nominationIds': nominationIds},
          ReturnValues="UPDATED_NEW"
        )

... and I see the response from DynamoDB which looks OK:
{
    "Attributes": {
        "nominations": {
            "SS": [
                "nomination-id-1",
                "nomination-id-2"
            ]
        }
    },
    "ResponseMetadata": {
        "RetryAttempts": 0,
        "HTTPStatusCode": 200,
        "RequestId": "3db8cae9-47e8-447b-89e4-7e35426e1a68",
        "HTTPHeaders": {
            "server": "Jetty(8.1.12.v20130726)",
            "content-length": "681",
            "x-amz-crc32": "2586038436",
            "x-amzn-requestid": "3db8cae9-47e8-447b-89e4-7e35426e1a68",
            "content-type": "application/x-amz-json-1.0"
        }
    }
}

but then when I query the table the type is completely different:
"nominations": {
                "M": {
                    "SS": {
                        "L": [
                            {
                                "S": "nomination-id-1"
                            },
                            {
                                "S": "nomination-id-2"
                            }
                        ]
                    }
                }
            }

print(nominations) #nominations ['nomination-id-1', 'nomination-id-2']


'404 Not Found. ' and then some

Cloned a couple repositories. Each one is owned by http:http. Trying to access them yields a 404.
I followed the instructions in Install.md but now when I try to access  the base url I get a file spat out at me unless I add an index.php to the urlbar of my browser.

I guess you need to add some more info if somebody should be able to help you.
Does the gitlist site itself work without a repo included?

I'm having the same issue.  All my repositories are found but clicking on any of them yields a 404 in Apache

Maybe this is related to #799?

Yup, that solved my problem


mrv2 v1.1.3 keeps crashing on Windows 11

Hi,
I've installed mrv2 v1.1.3 on Windows 11, and I can launch it without any issues. However, it consistently crashes/closes after a few seconds of use.
I've attempted to resolve this by trying older versions like mrv2 v1.1.2 and mrv2 v1.1.1, but unfortunately, I encounter the same problem.
System specs:
12th Gen Intel(R) Core(TM) i7-12700K   3.60 GHz
RAM 32.0 GB
NVIDIA GeForce RTX 4070 Ti
Thanks

Can you be more specific?  Is there anything in particular that you do that makes it crash?  Opening a file?  Playing back a movie?  Playing back EXRs?  Saving Sequences or Movies? Using the UI? Changing OCIO configurations?

There doesn't seem to be a specific trigger causing the crashes. I've recently started using mrv2 and have been testing simple tasks.
Typically, I open small video files (mp4, mov, wmv), manipulate the timeline, experiment with annotation tools like arrows, pencils, and text tools and save movies.
Everything appears to be functioning normally, but at random intervals, mrv2 unexpectedly closes without warning.
This occurs even when using different tools, so it's not tied to a specific function.

Okay.  You are the first one to report actual crashes with mrv2, so it is likely something related either to your machine configuration or your workflow.  I assume you don't have another machine on your network to test, so to debug this issue you will have to be patient with me and do some chores.
I'll have you do some things (stick with mrv2-v1.1.3):

Attach your actual preference configuration.  It is in C:/Users/<YourLogin>/.filmaura/mrv2.prefs  or %HOME%/.filmaura/mrv2.prefs if you have that variable defined.

Upgrade your NVidia video drivers to the latest version, just in case.

Are you comfortable with the Terminal / cmd.exe?  If you are, I would like you to open a Terminal and start mrv2.exe from there.  To start mrv2.exe, you would do:
If it is in your PATH already, just:
mrv2-v1.1.3.exe
If it is not in your PATH, type the full path to it:
C:\Program Files\mrv2-v1.1.3\bin\mrv2-v1.1.3.exe
Leave the terminal open and use the program until it crashes.  It should print out a stack trace log of the crash.  It may not tell us much, but it might help.  Copy and Paste the stack trace here without pressing Enter on the terminal.

Record yourself with a screen recording tool using the program until it crashes.  I personally use FreeCam (https://www.freescreenrecording.com/) but if you have other tool you like is fine.  Upload the video without editing it to some web upload service like www.mega.nz, dropbox, etc.  Post the link here.

I've installed and tested mrv2 on a similar machine, and unfortunately, it's experiencing the same random crashes.
Following your instructions, I've:

Located my preference configuration at C:/Users/USER1/.filmaura/mrv2.prefs
Updated my Nvidia drivers
Started mrv2 with the Terminal, crashed as expected and encountered the following output:

C:\Users\USER1>mrv2-v1.1.3.exe

C:\Users\USER1>       [app] mrv2 v1.1.3 - Built Apr 20 2024 21:12:19
       [app] Running on: Windows 8+
       [app] Set Language to en_US.UTF-8, Numbers to C
       [prefs] Reading preferences from "C:\Users\USER1/.filmaura/mrv2.prefs".
       [prefs] Loaded color themes from "C:/Program Files/mrv2-v1.1.3/colors/mrv2.colors".
       [ocio] Setting OCIO config to default:
       [ocio] ocio://default
       [prefs] Path mappings have been loaded from "C:\Users\USER1/.filmaura/mrv2.paths.prefs".
       [prefs] Loading hotkeys from "C:\Users\USER1/.filmaura/mrv2.keys.prefs".
GOT SIGNAL 11
0: RtAudio::getDefaultInputDevice - 0x140699075959504
1: log2f - 0x140711774566800
2: RtApi::verifyStream - 0x140699077557824
3: _C_specific_handler - 0x140711332935328
4: _chkstk - 0x140711815889632
5: RtlFindCharInUnicodeString - 0x140711815338448
6: KiUserExceptionDispatcher - 0x140711815885776
7: Fl_Window::handle - 0x140709297099744
8: Fl_Window::y_root - 0x140709297101632
9: fl_win32_xid - 0x140709297228272
10: Fl_Tiled_Image::draw - 0x140709297052528
11: fl_control_modifier - 0x140709296916000
12: Fl_Window::icons - 0x140709297290000
13: Fl::run - 0x140709296628080
14: RtAudioError::~RtAudioError - 0x140699073157680
15: RtAudioError::~RtAudioError - 0x140699073157680
16: RtApi::verifyStream - 0x140699077557824
17: BaseThreadInitThunk - 0x140711794189664
18: RtlUserThreadStart - 0x140711815588384

At this moment, I'm unable to record my screen.

I hope this information proves helpful.

Okay.  I compiled debug builds of mrv2 (v1.1.4) for you to test.  It won't fix your crashes but it will give me a useful stack trace with line numbers now.
.exe:
https://mega.nz/file/SO4UATCD#pU0jY6E98pJX0lBW5caHCAChD6XQZWTeR2GpqRRCDXw
.zip:
https://mega.nz/file/vGQmAZoA#Wr5MRQP5xtKPZ-yteKBgF9w_pwKbxb_zj6hzlU3O0xI
Install them and run them from the terminal as you did before, like:
C:\Program Files\mrv2-v1.1.4\bin\mrv2-v1.1.4.exe
When it crashes, it may open a popup window.  If it does, click on Retry.  It will print out the stack trace to the terminal but with files and line numbers now.

I updated the mega.nz links.

I've installed mrv2-v1.1.4.exe, but when I try to run it, I encounter the following errors:

I've reinstalled it, but the errors persists.

I apologyze for that.  Windows and cmake prevent distributions of the debug versions of their DLLs for security reasons.  I've compiled overnight a Release version but with line numbers in sourceforge:
https://sourceforge.net/projects/mrv2/files/beta/mrv2-beta-Windows-amd64.exe/download
This should work fine.  If it crashes it will report the crash to the terminal and save a copy to %TEMP%/mrv2_crash.log.

I am also seeing this issue, or at least something similar to it. I will get inconsistent random crashes while I am playing a video file (which is the only thing I use mrv2 for).
Would I be able to install the above version and help you troubleshoot too?
More info / potential hints:

Usually, I see it happen immediately as my mouse exits the window boundaries. (I think. Not 100% sure).

I've seen it crash while not in focus as well, with no input from me. But the above is way more common.

It happens inconsistently, not every time.
I've seen this crash on videos with the container/codec/audio settings of WEBM/VP9/OPUS and MOV/QT/noaudio so far.
I open videos on an rclone network drive (a software-based NAS kinda thing), which tends to have pretty high latency?
I use mrv2 primarily for viewing videos with an alpha channel (the WEBMs and MOVs are partial passes from 3D CGI footage).

Processor	AMD Ryzen 7 5800H with Radeon Graphics            3.20 GHz
Installed RAM	16.0 GB (13.9 GB usable)
System type	64-bit operating system, x64-based processor
Pen and touch	Pen and touch support with 20 touch points

Edition	Windows 11 Home
Version	23H2
Installed on	10/4/2022
OS build	22631.3447
Experience	Windows Feature Experience Pack 1000.22688.1000.0

I am also seeing this issue, or at least something similar to it. I will get inconsistent random crashes while I am playing a video file (which is the only thing I use mrv2 for).

Thanks for reporting this major problem and how you use it.  Please download the beta version from sourceforge that has debugging information on it and try to crash it.
If you are already using it and getting a crash, look in:
%TMP%/mrv2.crash.log
Attach that file here (you might need to rename it as mrv2.crash.txt as GitHub might reject it).

Would I be able to install the above version and help you troubleshoot too?

Yes, please!  Download the beta from sourceforge and try it out.  The sooner we can get a stack trace with files and line numbers, the sooner we can fix the issue.

Just got a crash while viewing a MP4/H264/AAC file on my local drive. It crashed when I left clicked on the timeline to jump ahead. Here's that crash log:
0: RtAudio::getDefaultInputDevice - 0x140696634054128 (line number unavailable)
1: log2f - 0x140712599992720 (line number unavailable)
2: RtApi::verifyStream - 0x140696635975232 (line number unavailable)
3: _C_specific_handler - 0x140712359947296 (line number unavailable)
4: _chkstk - 0x140712637973216 (line number unavailable)
5: RtlFindCharInUnicodeString - 0x140712637422032 (line number unavailable)
6: KiUserExceptionDispatcher - 0x140712637969360 (line number unavailable)
7: Fl_Widget::activate - 0x140711328125695 (line number unavailable)
8: Fl_Widget::activate - 0x140711328125695 (line number unavailable)
9: Fl_Widget::activate - 0x140711328125695 (line number unavailable)
10: Fl_Widget::activate - 0x140711328125695 (line number unavailable)
11: Fl_Widget::activate - 0x140711328125695 (line number unavailable)
12: Fl_Widget::activate - 0x140711328125695 (line number unavailable)
13: Fl_Widget::activate - 0x140711328125695 (line number unavailable)
14: RtAudioError::~RtAudioError - 0x140696631345440 (line number unavailable)
15: RtAudioError::~RtAudioError - 0x140696631345440 (line number unavailable)
16: RtApi::verifyStream - 0x140696635975232 (line number unavailable)
17: BaseThreadInitThunk - 0x140712619091296 (line number unavailable)
18: RtlUserThreadStart - 0x140712637671968 (line number unavailable)

It looks like the audio was a problem, so I'll give you some info about my system regarding that.
File I was playing is:
~500MB MP4 file, h.264 codec, AAC audio
Audio bit rate 316kbps
2 channel stereo
Sample rate 48 kHz
Various screenshots of audio drivers attached, if that could possibly be useful

Sadly, we did not get line numbers, because I found out that on Windows you have to do something else: give you .pdb files.
Downloads
First, download this new .exe installer of mrv2-v1.1.4:
https://mega.nz/file/HW4FXCCR#3jC_WpVkFAg8Br-t170yI6ReMM_bLMwCQ_Pb6qMtxeM
Install the program wherever you want.
Then, download the .pdb files in this zip archive:
https://mega.nz/file/SSRAQZST#q24vnadeLxCzS4AfYySgM7dO0D5yDiV7fR9uScG2xOw
PDB Setup
I hope you have a D: drive with 500Mb or so.  If you don't, I'll have to do a recompile for your C:\ drive assuming you have space there.  The tricky thing is that you need to create a directory that matches my setup:
D:\code\applications\mrv2
Put the .zip archive there and uncompress it with unzip, winzip or winrar, so that you get:
D:\code\applications\mrv2\BUILD-Msys-amd64\
and all .pdb files and subdirectories mimicking my setup.
Testing
Start this new installed version of mrv2 v1.1.4.  I put "a crash" in the button for frame window button (at the top right corner next to the Edit button).  Hit that button to make it crash.  If you installed the .pdb files correctly, you will get a stack trace in %TMP% but with files and line numbers now.  If you don't get files and line numbers, check that you created the directory exactly as shown above.
Now for the real crash
If that worked, then play with the new mrv2 v1.1.4 until you make it crash.  The new stack trace should have files and numbers, which will tell us clearly where it is crashing.

I do not have a D drive, sorry! Laptop here.

Do you have abot 700Mb on your C: drive for the full mrv2?  If not I can send you a trimmed version of mrv2 for testing with just movie playback (no python, no pdf, no network, no tiff, no raw, no tga.  Just movies, codecs and exrs).

I've updated the instructions and links to the files to a trimmed version of mrv2.  Please see above instructions again.

I just followed the instructions again and when I did your test crash, I got this back.
0: mrv::callback - 0x140701647072160 (C:\code\mrv2\mrv2\lib\mrvCore\win32\mrvSignalHandler.cpp:37)
1: raise - 0x140705405068464 (line number unavailable)
2: abort - 0x140705405073008 (line number unavailable)
3: ViewerUI::cb__i - 0x140701646731424 (C:\code\mrv2\BUILD-Msys-amd64-small\Release\mrv2\src\mrv2-build\lib\mrvWidgets\mrViewer.cxx:1127)
4: ViewerUI::cb_ - 0x140701646731312 (C:\code\mrv2\BUILD-Msys-amd64-small\Release\mrv2\src\mrv2-build\lib\mrvWidgets\mrViewer.cxx:1131)
5: Fl_Widget::do_callback - 0x140701644890720 (C:\code\mrv2\BUILD-Msys-amd64-small\Release\FLTK-prefix\src\FLTK\src\Fl_Widget.cxx:382)
6: Fl_Button::handle - 0x140701644892464 (C:\code\mrv2\BUILD-Msys-amd64-small\Release\FLTK-prefix\src\FLTK\src\Fl_Button.cxx:207)
7: mrv::Button::handle - 0x140701646764144 (C:\code\mrv2\mrv2\lib\mrvWidgets\mrvButton.cpp:19)
8: send_event - 0x140701644885120 (C:\code\mrv2\BUILD-Msys-amd64-small\Release\FLTK-prefix\src\FLTK\src\Fl.cxx:1223)
9: Fl::handle_ - 0x140701644880800 (C:\code\mrv2\BUILD-Msys-amd64-small\Release\FLTK-prefix\src\FLTK\src\Fl.cxx:1439)
10: mouse_event - 0x140701645068592 (C:\code\mrv2\BUILD-Msys-amd64-small\Release\FLTK-prefix\src\FLTK\src\Fl_win32.cxx:1091)
11: WndProc - 0x140701645054800 (C:\code\mrv2\BUILD-Msys-amd64-small\Release\FLTK-prefix\src\FLTK\src\Fl_win32.cxx:1724)
12: DispatchMessageW - 0x140705430340128 (line number unavailable)
13: DispatchMessageW - 0x140705430340128 (line number unavailable)
14: Fl_WinAPI_System_Driver::wait - 0x140701645075376 (C:\code\mrv2\BUILD-Msys-amd64-small\Release\FLTK-prefix\src\FLTK\src\Fl_win32.cxx:414)
15: Fl::run - 0x140701644884672 (C:\code\mrv2\BUILD-Msys-amd64-small\Release\FLTK-prefix\src\FLTK\src\Fl.cxx:605)
16: main - 0x140701644700128 (C:\code\mrv2\mrv2\src\main.cpp:70)
17: WinMain - 0x140701644699808 (C:\code\mrv2\mrv2\src\main.cpp:125)
18: __scrt_common_main_seh - 0x140701651483248 (D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288)
19: BaseThreadInitThunk - 0x140705406854496 (line number unavailable)
20: RtlUserThreadStart - 0x140705442605600 (line number unavailable)

I assume this means the steps worked, so I'll keep an eye out for my next crash and send the crashdump once it happens.

Well, that was quick. I started clicking around randomly in the timeline again (outside of the blue buffer bar) and got a crash within 10 clicks.
Real crash dump:
0: mrv::callback - 0x140701647072160 (C:\code\mrv2\mrv2\lib\mrvCore\win32\mrvSignalHandler.cpp:37)
1: log2f - 0x140705404926352 (line number unavailable)
2: `__scrt_common_main_seh'::`1'::filt$0 - 0x140701651910942 (D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:304)
3: _C_specific_handler - 0x140705005169712 (line number unavailable)
4: _chkstk - 0x140705442906848 (line number unavailable)
5: RtlFindCharInUnicodeString - 0x140705442355664 (line number unavailable)
6: KiUserExceptionDispatcher - 0x140705442902992 (line number unavailable)
7: Fl_Window::handle - 0x140701644897184 (C:\code\mrv2\BUILD-Msys-amd64-small\Release\FLTK-prefix\src\FLTK\src\Fl_Window.cxx:595)
8: Fl_Window_Driver::hide_common - 0x140701644960032 (C:\code\mrv2\BUILD-Msys-amd64-small\Release\FLTK-prefix\src\FLTK\src\Fl_Window_Driver.cxx:173)
9: Fl_WinAPI_Window_Driver::hide - 0x140701645080560 (C:\code\mrv2\BUILD-Msys-amd64-small\Release\FLTK-prefix\src\FLTK\src\drivers\WinAPI\Fl_WinAPI_Window_Driver.cxx:470)
10: Fl_Timeout::do_timeouts - 0x140701644961840 (C:\code\mrv2\BUILD-Msys-amd64-small\Release\FLTK-prefix\src\FLTK\src\Fl_Timeout.cxx:490)
11: Fl_System_Driver::wait - 0x140701645030560 (C:\code\mrv2\BUILD-Msys-amd64-small\Release\FLTK-prefix\src\FLTK\src\Fl_System_Driver.cxx:360)
12: Fl_WinAPI_System_Driver::wait - 0x140701645075376 (C:\code\mrv2\BUILD-Msys-amd64-small\Release\FLTK-prefix\src\FLTK\src\Fl_win32.cxx:362)
13: Fl::run - 0x140701644884672 (C:\code\mrv2\BUILD-Msys-amd64-small\Release\FLTK-prefix\src\FLTK\src\Fl.cxx:605)
14: main - 0x140701644700128 (C:\code\mrv2\mrv2\src\main.cpp:70)
15: WinMain - 0x140701644699808 (C:\code\mrv2\mrv2\src\main.cpp:125)
16: __scrt_common_main_seh - 0x140701651483248 (D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288)
17: BaseThreadInitThunk - 0x140705406854496 (line number unavailable)
18: RtlUserThreadStart - 0x140705442605600 (line number unavailable)

Excellent!  We found at least one crashing bug thanks to your help.  Here's a fix to the bug and new .pdb files for you to keep testing:
.exe:
https://mega.nz/file/eTAhiRJL#1cKZ3jHpy0oAtrQtNENpJklGJ_8v8nhrLazJjt3qp8o
.pdb files to install again on the same place (just remove the BUILD-MSys-Windows-small directory):
https://mega.nz/file/zORFmJjI#icfy2YFjt2FxNaTXisWjU4-VsUgqN3x3NB4Fqrk9ghk
If you get further crashes, please report them.

Bug fixed in v1.1.4.

@pxt777 While you wait for v1.1.4 to be released (probably sometime next week), you can work around the crashes if you go to:
Window->Preferences
and then go to:
Timeline
and uncheck:
Preview Thumbnails

@pxt777 While you wait for v1.1.4 to be released (probably sometime next week), you can work around the crashes if you go to:
Window->Preferences
and then go to:
Timeline
and uncheck:
Preview Thumbnails

Yes, that worked! I disabled off the timeline and the crashes stopped.
And thanks to alexvng for all the testing. I didn't have access to the PC during the weekend, so i wasn't able to help you.
Tommorrow, i will try v1.1.4.


How to use Fingerswitcher in js without browser api such as pupeteer, playwright... ?

Hello,
I just only need get fingerprint and use in our side, no need  pupeteer, playwright... or any browser api.
How to get fingerprint in js with api key from FingerSwicher? Thanks!

You can get fingerprints without using browsers, but it doesn't make much sense - you won't be able to apply them correctly without the engine used in plugins.

@CheshireCaat I will use fingerprint to create profile in other Antidect browser, and don't need to use pupeteer, playwright.
Could you tell me how to get fingerprints with API key using Javascript? Do you have any library can run on macos, or HTTP API is also ok.

All plugins work only under Windows, you can also use BAS to work with fingerprints - plugins get fingerprints using it in the same way, I don't have any other options for you. Since the task is not directly related to plugins, I can't help you with anything else.


Use modulepath from environment.conf if available

Overview
This pull request checks environment.conf (if available) and uses the modulepath to inform its lookup locations for the --compare-file-text option.
Fixes https://github.com/github/octocatalog-diff/issues/12
Checklist

[x] Make sure that all of the tests pass, and fix any that don't. Just run rake in your checkout directory, or review the CI job triggered whenever you push to a pull request.
[x] Make sure that there is 100% test coverage by running rake coverage:spec or ignoring untestable sections of code with # :nocov comments. If you need help getting to 100% coverage please ask; however, don't just submit code with no tests.
[x] If you have added a new command line option, we would greatly appreciate a corresponding integration test that exercises it from start to finish. This is optional but recommended.

/cc @eelcomaljaars who originally reported the problem. Can you see if this code fixes the problem without your symlink workaround?

Hi @kpaulisse , switched to the branch and ran the job again without the symlinks, seems mostly ok. I did get a few new warnings that might need attention :
Previous output of this job :
I, [2016-11-09T07:17:33.832042 #91999]  INFO -- : Catalogs compiled for [REDACTED]
I, [2016-11-09T07:17:34.598840 #91999]  INFO -- : Diffs computed for [REDACTED]
diff production/[REDACTED] fea-puppetv4/[REDACTED]

Package[tcpdump] =>
parameters =>
ensure =>
- present
+ absent

New output on the branch :
W, [2016-11-09T07:20:39.047633 #93417]  WARN -- : WARNING: Hiera datadir for yaml doesn't seem to exist at /var/folders/6n/8xsv9cv56h3d6pg5mfx5gx1c0000gr/T/d20161109-93417-cnatq4environments/production/hieradata
W, [2016-11-09T07:20:40.177171 #93418]  WARN -- : WARNING: Hiera datadir for yaml doesn't seem to exist at /var/folders/6n/8xsv9cv56h3d6pg5mfx5gx1c0000gr/T/d20161109-93418-366vwrenvironments/production/hieradata
I, [2016-11-09T07:20:48.810370 #93413]  INFO -- : Catalogs compiled for [REDACTED]
I, [2016-11-09T07:20:49.431704 #93413]  INFO -- : Diffs computed for [REDACTED]
diff production/[REDACTED] fea-puppetv4/[REDACTED]

Package[tcpdump] =>
parameters =>
ensure =>
- present
+ absent

Thanks for your work on this!

W, [2016-11-09T07:20:39.047633 #93417] WARN -- : WARNING: Hiera datadir for yaml doesn't seem to exist at /var/folders/6n/8xsv9cv56h3d6pg5mfx5gx1c0000gr/T/d20161109-93417-cnatq4environments/production/hieradata

There seems to be a missing / somewhere.
Are you using settings[:hiera_path_strip]? If so, does your value have a trailing /?
e.g.
# Bad
settings[:hiera_path_strip] = '/etc/puppetlabs/code/'

# Good
settings[:hiera_path_strip] = '/etc/puppetlabs/code'

Yes that was it. Thanks.


Make reflect_y() a Waypoint method

Codecov Report

Merging #59 into master will increase coverage by 0.14%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #59      +/-   ##
==========================================
+ Coverage   85.31%   85.46%   +0.14%
==========================================
  Files          20       20
  Lines        1369     1369
  Branches      133      133
==========================================
+ Hits         1168     1170       +2
+ Misses        169      168       -1
+ Partials       32       31       -1

Impacted Files
Coverage Δ

utilities/pure_pursuit.py
89.72% <100%> (+1.53%)
:arrow_up:

autonomous/autonomous.py
63.26% <100%> (-0.74%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 67d57a3...a361686. Read the comment docs.


Scalar API Client Proxy Error

I love te new Scalar docs, they are very beautiful and well structured.
However, when I try to make any request to test out the API I get the above error.

My config is as below:
import path from 'node:path'
import url from 'node:url'

export default {
  path: path.dirname(url.fileURLToPath(import.meta.url)) + '/../',
  title: 'SBDC API',
  version: '1.0.0',
  tagIndex: 2,
  snakeCase: false,
  ignore: [
    '/swagger',
    '/docs',
    '/api/internal',
    '/admin',
    // '/partner',
    // '/login',
    // '/register',
    '/jobs',
    '/2fa',
    '/logout',
    '/password',
    '/inertia',
    '/ask',
    '/about',
    '/contact',
    '/auth/*',
    '/portfolio',
    '/our-partners',
    '/p/*',
    '/c/*',
  ],
  preferredPutPatch: 'PUT',
  common: {
    parameters: {
      page: 1,
      per: 10
    },
    headers: {
      'Accept': 'application/json',
      'Content-Type': 'application/json',
    },
  },
  persistAuthorization: true,
  showFullPath: false,
}

and the routes
router.get('swagger', async () => {
  return AutoSwagger.default.docs(router.toJSON(), swagger)
})

router.get('docs', async () => {
  // return AutoSwagger.default.ui('/swagger', swagger)
  return AutoSwagger.default.scalar('/swagger')
})

I'm not 100% sure, but looks like scalar calls api.scalar.com which then tries to connect to localhost:333 (in my case) .. and this obviously wouldn't work, since their server does not know anything about localhost:3333.
I assume, this should work if your app is hosted publicly with an accessible URL like https://myapp.googleapps.com or similar.

Did it work on production?

@ad-on-is Yes it does, thank you.

@maukoese
`
import scalarCustomCss from '#config/scalar'
router.get('/docs', async () => {
return `
<!doctype html>

API

`
})`
this works if still want to use scalar!


fix: fixing gitignore for intellij

Hi there,
Side note: thanks for the cool talk at FOSDEM, really interesting.
This PR is just an additional ignore entry for the .idea folder created by IntelliJ (and other Jetbrain's products I believe).

Closing it for now as it's minor and stalled since about 10 months.


Failed to deploy the rbd by referencing the deployment document

I refer to https://github.com/ceph/ceph-csi/blob/devel/docs/deploy-rbd.md  Unable to start service
The service shows that oidc token is missing
Events:
  Type     Reason       Age                   From               Message
  ----     ------       ----                  ----               -------
  Normal   Scheduled    7m21s                 default-scheduler  Successfully assigned default/csi-rbdplugin-provisioner-7b47fd8df7-kwz87 to single3
  Warning  FailedMount  5m18s                 kubelet, single3   Unable to attach or mount volumes: unmounted volumes=[oidc-token], unattached volumes=[host-dev ceph-csi-config keys-tmp-dir socket-dir ceph-config ceph-csi-encryption-kms-config rbd-csi-provisioner-token-h9cdz host-sys lib-modules oidc-token]: timed out waiting for the condition
  Warning  FailedMount  3m                    kubelet, single3   Unable to attach or mount volumes: unmounted volumes=[oidc-token], unattached volumes=[ceph-csi-encryption-kms-config ceph-config socket-dir host-dev lib-modules ceph-csi-config rbd-csi-provisioner-token-h9cdz keys-tmp-dir oidc-token host-sys]: timed out waiting for the condition
  Warning  FailedMount  68s (x11 over 7m20s)  kubelet, single3   MountVolume.SetUp failed for volume "oidc-token" : failed to fetch token: the API server does not have TokenRequest endpoints enabled
  Warning  FailedMount  46s                   kubelet, single3   Unable to attach or mount volumes: unmounted volumes=[oidc-token], unattached volumes=[socket-dir lib-modules ceph-csi-encryption-kms-config keys-tmp-dir rbd-csi-provisioner-token-h9cdz ceph-csi-config ceph-config oidc-token host-sys host-dev]: timed out waiting for the condition

But I found no relevant resources in the file。

@lixiaopengy
Can you try with release v3.5 ?
https://github.com/ceph/ceph-csi/blob/v3.5.1/deploy/rbd/kubernetes/csi-rbdplugin-provisioner.yaml
Which kubernetes version are you using ?

failed to fetch token: the API server does not have TokenRequest endpoints enabled

please check above error

@lixiaopengy 您可以尝试发布 v3.5 吗？ https://github.com/ceph/ceph-csi/blob/v3.5.1/deploy/rbd/kubernetes/csi-rbdplugin-provisioner.yaml
您使用的是哪个 kubernetes 版本？

I use kubernetes v1.17

We dont support kubernetes 1.17 you need to make some changes in provisioner and daemonset yaml to remove token part

我们不支持 kubernetes 1.17，您需要在配置程序和 daemonset yaml 中进行一些更改以删除令牌部分

OK, thank you for your reply


[dv] Add simulation result summary page

Here is the report that will be generated
https://reports.opentitan.org/hw/top_earlgrey/dv/summarys.html
Also fix xbar coverage error
Signed-off-by: Weicai Yang<EMAIL_ADDRESS>

@sriyerg @weicaiyang can we move forward with this one or is there still something missing? if not I I will move on and rebase my extensions for lint on top of this such that I can reuse the summary report feature....

@sriyerg @weicaiyang can we move forward with this one or is there still something missing? if not I I will move on and rebase my extensions for lint on top of this such that I can reuse the summary report feature....

Will merge it ASAP.
@sriyerg please let me know if you have more comment

I am debugging the CI failure now (testplan tool does not allow testplan name to be empty in tlul_testplan.hjson file. Working on a fix for this).

I am debugging the CI failure now (testplan tool does not allow testplan name to be empty in tlul_testplan.hjson file. Working on a fix for this).

Thank you very much.


Rollback command

$ apex rollback
$ apex rollback --version N

Might be best to use aliases in place of $LATEST
Yeah, makes more sense. I need to read AWS Lambda docs about aliasing and will be back with PR.

Might be best to use aliases in place of $LATEST
Yeah, makes more sense. I need to read AWS Lambda docs about aliasing and will be back with PR.


Add support for multiple bitmaps

Thanks a lot for this software at first. Now I meet with one problem.I want to add different texture mapping bitmap in one cube. I search all codes many times. I choose Object3DBuilder .java.
Now it only support one bitmap. Can you help us realize add different texture mapping bitmap in one cube. (
bitmap[] bm.
bmp[0] = BitmapFactory.decodeResource(context.getResources(), R.drawable.aa);
bmp[1] = BitmapFactory.decodeResource(context.getResources(), R.drawable.bb);
bmp[2] = BitmapFactory.decodeResource(context.getResources(), R.drawable.cc);
bmp[3] = BitmapFactory.decodeResource(context.getResources(), R.drawable.dd);
bmp[4] = BitmapFactory.decodeResource(context.getResources(), R.drawable.ee);
bmp[5] = BitmapFactory.decodeResource(context.getResources(), R.drawable.ff)
not  byte[] textureData and I want to change it to bimtap[]
)
file : Object3DBuilder.java
org.andresoviedo.app.model3D.model;public final class Object3DBuilder
public static Object3DData buildCubeV3(byte[] textureData) {
return new Object3DData(
createNativeByteBuffer(cubePositionData.length * 4).asFloatBuffer().put(cubePositionData),
createNativeByteBuffer(cubeTextureCoordinateData.length * 4).asFloatBuffer()
.put(cubeTextureCoordinateData).asReadOnlyBuffer(),
textureData).setDrawMode(GLES20.GL_TRIANGLES).setId("cubeV3").centerAndScale(1.0f);
}

Another prolem:
I need only mapping one face texture mapping of 8 faces.
I try it and this software api can't support it. Please think it over.
I only handle with one texture mapping of many faces.

Hey body.  Support for multiple textures is not implemented.
I am wondering if it's possible to map all the cube faces with just 1 bitmap.
Gonna change the title to add the feature in the future ;)

Dear @liyihongcug
Latest version of the app should solve most of the texture issues
so I am closing this for now
kind regards


Disable logging integration test

Integration tests were added in ecto_sql to test the logging for casted parameters, but they rely on not using square brackets anywhere else in the log message. It can be disabled this way.

Actually this might not be needed for you. I saw the logging test failure here and think I jumped to this conclusion too quickly: https://github.com/elixir-sqlite/ecto_sqlite3/runs/7150395395?check_suite_focus=true. It doesn't seem to be related to these tests. If you think it's ok for your adapter please I can close this :).


async pipe cases "boolean expression must not be null"

[disabled]="!(onHasUnsavedChangesChanged | async)">

final bool currVal_3 = !_pipe_async_0.transform(_ctx.onHasUnsavedChangesChanged);

Dart VM version: 2.0.0-dev.24.0 (Mon Feb 12 18:55:09 2018 +0100) on "macos_x64"

Angular 5.0.0-alpha+6
I'm sure that onHasUnsavedChangesChanged is never null and never emits null
(store is from built_redux)
Stream<bool> get onHasUnsavedChangesChanged => store
      .substateStream((s) => s.postEditor)
      .where((s) =>
          s.prev.editedPosts.isNotEmpty != s.next.editedPosts.isNotEmpty ||
          s.prev.createdPosts.isNotEmpty != s.next.createdPosts.isNotEmpty)
      .map((s) =>
          s.next.editedPosts.isNotEmpty || s.next.createdPosts.isNotEmpty);

AsyncPipe will return null the first time before any data is made available by the stream, and you're negating that result. In other words, you're seeing an exception for calling !null.
Fix it by providing a default value when null:
<div [disabled]="!((onHasUnsavedChangesChanged | async) ?? false)">

@leonsenft sounds reasonable now after you mention it :D
Thanks a lot.