Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Socket error: 111
Connection to remote host failed!
Read blend: "/workspace/revon/blender_ci_test/models/rock_2.blend"
Warning: region type 14 missing in space type "Image" (id: 6) - removing region
regiondata free error
Warning: region type 15 missing in space type "Image" (id: 6) - removing region
Warning: region type 14 missing in space type "Image" (id: 6) - removing region
regiondata free error
Warning: region type 15 missing in space type "Image" (id: 6) - removing region
Warning: region type 14 missing in space type "Image" (id: 6) - removing region
regiondata free error
Warning: region type 15 missing in space type "Image" (id: 6) - removing region
Warning: region type 14 missing in space type "Image" (id: 6) - removing region
regiondata free error
Warning: region type 15 missing in space type "Image" (id: 6) - removing region
Error: Engine 'BLENDER_EEVEE_NEXT' not available for scene 'Scene' (an add-on may need to be installed or enabled)
Warning: File written by newer Blender binary (402.66), expect loss of data!
13:56:52 | INFO: Draco mesh compression is available, use library at /usr/local/bin/blender/4.1/python/lib/python3.11/site-packages/libextern_draco.so
13:56:53 | INFO: Starting glTF 2.0 export
13:56:53 | INFO: Extracting primitive: Cube.008
Error: Tangent space can only be computed for tris/quads, aborting
13:56:53 | WARNING: Could not calculate tangents. Please try to triangulate the mesh first.
13:56:53 | INFO: Primitives created: 1
13:56:53 | INFO: Finished glTF 2.0 export in 0.03023386001586914 s
<IP_ADDRESS> - - [15/Aug/2024 13:56:53] "POST / HTTP/1.1" 200 -
glTF: Total buffers: 1
glTF: Total buffer views: 4
glTF: Total accessors: 4
glTF: Total images: 1
Total materials: 1
glTF: Parsing mesh: 0
glTF: type vec3 component type: Float stride: 12 amount 146
glTF: accessor offset 0 view offset: 0 total buffer len: 5188 view len 1752
glTF: type vec3 component type: Float stride: 12 amount 146
glTF: accessor offset 0 view offset: 1752 total buffer len: 5188 view len 1752
glTF: type vec2 component type: Float stride: 8 amount 146
glTF: accessor offset 0 view offset: 3504 total buffer len: 5188 view len 1168
glTF: type float component type: UShort stride: 2 amount 258
glTF: accessor offset 0 view offset: 4672 total buffer len: 5188 view len 516
glTF: Total meshes: 1
glTF: Creating mesh for: rock_2-col
Fix: Renamed rock_2-col to rock_2
	import: step 2: Running Custom Script...
	import: step 104: Saving...

XR: Clearing primary interface
XR: Removed interface "Native mobile"
XR: Removed interface "OpenXR"
Orphan StringName: Node (static: 5, total: 6)
StringName: 1 unclaimed string names at exit.

Turns out, I just need to install all the dependencies of Blender... which I solved by installing Blender from apt-get. There's probably a better way, but this is the fastest way to debug out the issue.

I had the same issue as @arnaudvergnet and identified this underlying issue: In the editor settings file, there's a line with the blender path existing per default. The added line with the filled blender path is then ignored.
If I change the blender path, instead of simply adding a line, I get one step further.
After that, blender fails as numpy is missing (at least for me, as I start my docker from ubuntu:oracular. But adding python3-numpy to the apt-get install command helps with that.
I still get a lot of socket errors, but they apparently can be ignored.
So, my proposal would be to not just get stuck, but complain if no blender is installed, but needed.

@LasseSchnepel Your issue seems to be different from mine as the file ~/.config/godot/editor_settings-4.tres does not already have a line for the blender path on my end.
@revonzev Your solution of installing blender from apt did not work for me. It should not be necessary as the blender downloaded from the website should contain all the dependencies. The blender version in the repos is also the version 3, so I guess the dependencies for blender 4 would be different somewhat.

Hi @arnaudvergnet , at least for me, the -4.tres is not looked at, it is the -4.3.tres, so take care what file you look at / add to.

Ah yes indeed there are both 4.tres and 4.3.tres files, the first one without the blender path line and the other with it set to an empty path. I tried setting the path in the 4.3.tres by replacing the line but the CI still gets stuck at the same place.


Frontend refactoring

Change page title via ngrx-store

Use new Ionic Menu layout and reorganise Menu links to retrieve their data via routes info

Put a settings page and add version info etc. Also ENV, DB url etc. (can be visible only in Dev mode, like the Devtools)

Done


Add aqt.metadata.Versions.flattened()

This adds a function to Versions that returns a flattened list of Version objects. This is a spinoff from #318 that I needed for that feature, but I think it's outside the scope of that PR.
This also adds test coverage for the whole Versions class.

LGTM


Indrev and Cabricality support

It's wired that my md editor change ''' to ''' but it effect nothing.

thx


ct_icp no timestamps

Hi! I am trying to run your algorithm on some data I generate from a gazebo simulation. Such data do not come with timestamps associated with the points and I would like to know if the algorithm can still run on them.
At the moment when I try and launch the file I get the error:
The point cloud does not have timestamps, this is incompatible with the `CONTINUOUS_TIME` representation of pose in CT-ICP
[ INFO] [1680086675.307007042]: The schema of the point cloud is:
Item Size: 32
Elements Layout:
	properties: [offset in item:0]
		x: [type:f / offset in elem:0 / dim:1]
		y: [type:f / offset in elem:4 / dim:1]
		z: [type:f / offset in elem:8 / dim:1]
		padding_0: [type:b / offset in elem:12 / dim:4]
		intensity: [type:f / offset in elem:16 / dim:1]
		tag: [type:B / offset in elem:20 / dim:1]
		line: [type:B / offset in elem:21 / dim:1]
		padding_1: [type:b / offset in elem:22 / dim:10]
	vertex: [offset in item:0]
		x: [type:f / offset in elem:0 / dim:1]
		y: [type:f / offset in elem:4 / dim:1]
		z: [type:f / offset in elem:8 / dim:1]

What parameter should I change from CONTINUOUS_TIME to something else?

You should change it to "CONSTANT_VELOCITY" / "ITERATIVE",
Depending on your use case, you should try either

the driving config:
config/driving_config.yaml
Or the mobile robotics config:
config/driving_config.yaml
https://github.com/jedeschaud/ct_icp/blob/master/config/odometry/nclt_config.yaml

Hi, thank you for pointing me in the right direction. I am using CT-ICP on ROS and if I try and set the parametrization value to CONSTANT_VELOCITY" / "ITERATIVE I get the error:
Loading Config from yaml file: /home/MyUserName/ct_icp_ros/src/ct_icp_odometry/params/ct_icp/ct_icp_driving_fast.yaml
[ERROR] [1680179983.763600138]: Error while loading the config from path: `/home/MyUserName/ct_icp_ros/src/ct_icp_odometry/params/ct_icp/ct_icp_driving_fast.yaml`
inotify_add_watch(/home/MyUserName/.config/ibus/bus/5f473cec13374b419a0b78498fa8d504-unix-1) failed: (No space left on device)
terminate called after throwing an instance of 'std::runtime_error'
  what():  Parametrization is not supported !
Caught SIGABRT: usually caused by an abort() or assert()
  message for depth: [2]: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb) [0x7fa81862d00b]
  message for depth: [3]: /lib/x86_64-linux-gnu/libc.so.6(abort+0x12b) [0x7fa81860c859]
  message for depth: [4]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa1a31) [0x7fa8189e9a31]
  message for depth: [5]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xad5dc) [0x7fa8189f55dc]
  message for depth: [6]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xad647) [0x7fa8189f5647]
  message for depth: [7]: /lib/x86_64-linux-gnu/libstdc++.so.6(__cxa_rethrow+0x4d) [0x7fa8189f593d]
  message for depth: [8]: /home/MyUserName/ct_icp_ros/devel/lib/ct_icp_odometry/ct_icp_odometry_node(+0x153b6) [0x55e6477073b6]
  message for depth: [9]: /home/MyUserName/ct_icp_ros/devel/lib/ct_icp_odometry/ct_icp_odometry_node(+0x16aa3) [0x55e647708aa3]
  message for depth: [10]: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7fa81860e083]
[ct_icp_odometry_node-3] process has died [pid 184369, exit code 1, cmd /home/MyUserName/ct_icp_ros/devel/lib/ct_icp_odometry/ct_icp_odometry_node /ct_icp/pointcloud:=/livox/lidar __name:=ct_icp_odometry_node __log:=/home/MyUserName/.ros/log/f200a7be-cef7-11ed-aef6-bb7807375447/ct_icp_odometry_node-3.log].
log file: /home/MyUserName/.ros/log/f200a7be-cef7-11ed-aef6-bb7807375447/ct_icp_odometry_node-3*.log

However I can set parametrization: SIMPLE and it works very well, you can see below the results using my data where the pointclouds have no timestamp data:

Nice ! Thanks for sharing :)


Expose a way to add functions to the FluentBundle

Currently the FluentBundle instances created inside the FluentTranslator class cannot be configured after construction, so it's impossible to call addFunction.
Perhaps a method could be added to FluentTranslator to allow adding functions when new bundles are constructed? Something like:
$translator = app('translator'); // instanceof FluentTranslator

$translator->addFunction('MY_FUNCTION', Closure::fromCallable('my_function'));

Then the FluentTranslator would pass these on whenever a bundle is created.
The user would call this in their own service provider. I don't think config files are useful here as they cannot contain closures.

Thank you for the suggestion, that would be a useful addition. I will add it tomorrow.


disable ckeditor maximizing for iOS, use different maximize

on iOS we should never have ckeditor maximized because the panels will
not open anymore

LGTM


Refactored database secret block.

There was no option to use existing config for Database credentials. This is usual case for EKS with ExternalSecrets operator that takes secret values from AWS SM. Now, there is an option to omit creation of the secret for the database and use existing one.

@hunters-vlasov-y sounds reasonable. Thank you.
Could you please keep 0.2.4-SNAPSHOT version of chart (we will update it after release only) and default -db suffix of the secret?

@alexandrvb Changed version back to 0.2.4-SNAPSHOT

@alexandrvb When this chart will be released to the helm registry?

@hunters-vlasov-y after the next Datalore release. I hope it will be the beginning of September


[Swift] Defer initialization of variables checks to the compiler.

rdar://problem/45588366

@swift-ci test and merge

There was a little code between type-checking and this second hand-verification pass, so theoretically this extra check could serve the purpose of verifying that the intervening AST manipulations didn't introduce an error.  But those manipulations don't do very much, so it's hard to see this as being necessary.  Anyway, if we end up needing to do another verifier pass at this point, that's something we should depute to the compiler rather than trying to roll it by hand.
So this seems good to me.


feat(signers): exports arbundles ArconnectSigner and ArweaveSigner

This prevents clients from having to install arbundles separately from our SDK and gives us the ability to pin to specific implementations if necessary

:tada: This PR is included in version 1.5.0-alpha.3 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Query Builder withCount not available when using select

Laravel Version: 5.3.1
PHP Version: 7.0.10
Database Driver & Version: mysql 5.6.28

Description:
I have the following code to get some specific events (Events of Clubs that a user has liked)
$events = Event::query();

$events->with('club');
$events->with('hasUserTicket');
$events->with('hasUserGuestlist');

$events->withCount('tickets');
$events->withCount('guestlist');

$events->join('clubs', 'clubs.id', '=', 'events.club_id');
$events->join('likeables', 'likeables.likeable_id', '=', 'clubs.id');
$events->join('users', 'users.id', '=', 'likeables.user_id');

$events->select('clubs.*', 'clubs.name as clubs.name', 'events.*');

$events->where('likeables.likeable_type', 'App\\Club');
$events->where('users.id', $user->id);
$events->orderBy('events.date', 'ASC');

return $events->get();

My problem is, that because of the line $events->select... the two columns tickets_count & guestlist_count (from ->withCount('guestlist'); & ->withCount('tickets');) are missing in the result.
Is that expected behaviour? Because the values of hasUserTicket and hasUserGuestlist are available in the result. Or do I need to explicitly call the two properties in the select method and if so, how?

Okay, so I figured out that it works when I put withCount after the select method
            ->select('clubs.*', 'clubs.name as clubs.name', 'events.*')
            ->withCount('tickets')
            ->withCount('guestlist')

Strange (to me) but good that it works!

When encapsulating the withCount in a function within a EloquentModel we need to use the select after the encapsulated function as the select return QueryBuilder so not sure if its something woth addressing

Hello, I'm working on something which needs similar implemetation and using the withCount below the select works fine. However, I also need to use having() like so:
...
->having('tickets_count', '<', 'clubs.capacity')
when I replace clubs.capacity with a number, it works fine but it doesn't with the code above.
Any help??


Task/service

Codecov Report
Patch coverage: 66.98% and project coverage change: -9.40% :warning:

Comparison is base (30a244c) 59.00% compared to head (9fab83a) 49.60%.

Additional details and impacted files
@@             Coverage Diff              @@
##               main      #14      +/-   ##
============================================
- Coverage     59.00%   49.60%   -9.40%
+ Complexity       36       33       -3
============================================
  Files            11       12       +1
  Lines           261      254       -7
  Branches          9       10       +1
============================================
- Hits            154      126      -28
- Misses          101      123      +22
+ Partials          6        5       -1

Files Changed
Coverage Δ

...ntervaltimer/core/service/CountDownTimerService.kt
0.00% <0.00%> (ø)

...antos/intervaltimer/core/service/CountDownTimer.kt
85.54% <85.54%> (ø)

... and 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[3.x] - Add white paper link to README.MD

^^^

Move it to the Documentation section and emphasize it with camel case (White Paper).


Restrict a Stack's access to core types when the stack claims they "depend on" them

What problem are you facing?
As per the stacks security and isolation design, it is intended to restrict access to the resources that a Stack can perform operations on.  Specifically, a stack only gets access to the CRDs that it owns or declares that it depends on.
However, we don't discriminate at all about what resources a Stack claims it depends on.  I believe that if a stack declares it "depends on" volumes or pods, then we'd be OK with that and create the necessary RBAC to allow that access.
Important: Must support a run mode compatible with running Crossplane directly in the target cluster such that Crossplane stacks can manage Kubernetes core types including Deployment, Ingress, Services.
How could Crossplane help solve your problem?
We should consider black or white listing the API groups or resources that stacks can get access to, even if they claim they depend on them.  If a stack says it depends on volumes or pods, we should not grant them RBAC access to them.
The code that would need to be updated lives here:
https://github.com/crossplaneio/crossplane/blob/master/pkg/stacks/unpack.go#L359-L376

Alternatively, if a Stack requires access to core or extension types, or any unknown outside type, UI tools (the CLI or Web UIs) should prompt for user confirmation or require arguments to override the default restrictive behavior.
I believe Stacks will benefit from being able to create any type of Kubernetes resource.  We can use https://github.com/crossplaneio/crossplane/issues/758 to restrict this.
Perhaps the restrictive behavior could be toggled through a feature flag of the Stack Manager.

If the base set of permitted CRDs are 'those owned by any Stack', then we may have a need to expand the dependsOn pool using a Stack Manager argument.

The existing RoleBinding vs ClusterRoleBinding dicotomy that differentiates StackInstall and ClusterStackInstall service accouts creates a boundary preventing namespaced Stacks from depending on cluster-scoped Stack owned types.
We may want to put more definition around these boundaries, through this dependsOn restriction work:

a namespace stack can not dependOn a cluster-scoped CRD (this is only a pre-validation step, since the rolebinding would prevent such access)


Optimise TextEdit get line height and width

Getting TextEdit line height and width looped over every line, line height in particular was called multiple times every time we drew. This was quite expensive. TextEdit::Text now caches the line height and width.
There were also some cases where we were invalidating the cache, or updating data that was not required. These calls have been removed. As an addition, get_text now uses StringBuilder.
One stand out performance hit is drawing line numbers, most of it was previously spent in calculating the line height, and shaping text. However, there was also a significant amount of time spent in format_number due to string manipulation. Most of this data is static. This has now been changed to insert at launch rather then on every call.
This has increased performance at launch for a test script by ~6ms, switching tabs by ~100ms and avg draw time by ~2ms.

Rebased following #51908, which decreased performance for draw time by around ~5ms. Most of this time was spent doing string comparisons on static data. I've converted this to a Map rather then an array. This bought us roughly back to where this PR was originally, maybe around 0.5ms slower.

Thanks!


Actions dont work on dropped items

What happened?
Actions dont work on dropped items.
What did you expect to happen?
Actions should still work on dropped items.
How can we reproduce it (as minimally and precisely as possible)?
Drop any EveronLife item (apple, tomato, etc..) that doesn't have a collider on the ground and try to pick it up via action.
This only happens if there is no other collider near the item. E.g it works fine when the item is on a table.
*None of the items currently has a collider.
Anything else we need to know?
Fix: A proper collider should be added to every item.
EveronLife Version

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Items usually do not have colliders yes, that is intended. Them not having a pickup interaction is odd.

Items usually do not have colliders yes, that is intended.

Is it? Every item in the game has at least one collider.

Okay found an ez fix

it is preferred to not have colliders on smaller items like an apple for example, you wouldn't want an apple left in the middle of the road to send your car flying

I am working on it.
@TL6868 Colliders have different types of layers as far as im aware. Not every layer sends the car flying

it is preferred to not have colliders on smaller items like an apple for example, you wouldn't want an apple left in the middle of the road to send your car flying

I wonder if there's an easy way we can have the colliders that aren't static and the apple would easily be smashed out of the way by a car tire?
It does seem that they are 100% required for items to be picked up though unfortunatley.


Webhook post url from within a plugin

I am not able to find the correct URL to post a webhook from within a plugin container. I tried all possible combinations (by reading the plugin documentation) and received either 400 / 401 or 404.
I also posted some days ago the same question in the community but no one was able to answer the question.
https://community.home-assistant.io/t/webhook-endpoint-address-within-a-plugin-container/108032
Is it possible at all and what is the URL? My assumption is the webhook URL should be reachable without authentication.

It's on my task list to write a document.
http://hassio/homeassistant/api/webhook/xy look in developer page for token handling

Why is a token needed? If I call the webhook from outside, no token is needed.

Are you sure about the token? With a valid token and the url you mentioned I receive 401.
string token = environment.get("HASSIO_TOKEN");
auto client = new HttpClient();
auto request = client.request(arsd.http2.Uri(targetUrl), HttpVerb.POST);
request.requestParameters.headers ~= "X-HASSIO-KEY: " ~ token;
auto response = request.perform();

because it works over an internal API gateway. But you can also call it over your external URL without an internal API Gateway.

While trying to call the external URL (post) from within the plugin container I get an connection refused exception.
POST http://hassio:8123/api/webhook/xy
Are you sure calling the internal/external webhook API is working from within plugin container?

@andre2007 If you want to post directly to HA you have to post to:
http://homeassistant:8123/api/webhook/xy
If you want to use the bridge provided by Hass.io you'd use:
http://hassio/homeassistant/api/webhook/xy, which requires authentication using the HASSIO_TOKEN that is available from the add-on environment.

Thanks.


scons build error

scons: Reading SConscript files ...
Detected compiler gcc 5.4.0
scons: done reading SConscript files.
scons: Building targets ...
protoc -I. --cpp_out=. --python_out=. build/Protocol/ServerControl.proto
sh: 1: protoc: not found
protoc -I. --cpp_out=. --python_out=. build/Protocol/Client.proto
sh: 1: protoc: not found
Compiling build/Client/Backoff.cc
Compiling build/Client/Util.cc
protoc -I. --cpp_out=. --python_out=. build/Protocol/ServerStats.proto
sh: 1: protoc: not found
protoc -I. --cpp_out=. --python_out=. build/Tree/Snapshot.proto
sh: 1: protoc: not found
protoc -I. --cpp_out=. --python_out=. build/Protocol/Raft.proto
sh: 1: protoc: not found
protoc -I. --cpp_out=. --python_out=. build/Protocol/RaftLogMetadata.proto
sh: 1: protoc: not found
Compiling build/RPC/Address.cc
Compiling build/RPC/ClientRPC.cc
Compiling build/RPC/ClientSession.cc
Compiling build/RPC/MessageSocket.cc
Compiling build/RPC/OpaqueClientRPC.cc
Compiling build/RPC/OpaqueServer.cc
Compiling build/RPC/OpaqueServerRPC.cc
scons: *** [build/Protocol/ServerControl.pb.cc] Error 127
Compiling build/RPC/Protocol.cc
scons: *** [build/Protocol/Client.pb.cc] Error 127
scons: *** [build/Protocol/ServerStats.pb.cc] Error 127
scons: *** [build/Tree/Snapshot.pb.cc] Error 127
scons: *** [build/Protocol/Raft.pb.cc] Error 127
scons: *** [build/Protocol/RaftLogMetadata.pb.cc] Error 127
scons: building terminated because of errors.

when i build with scons command, as a result it throw some error. didn't pass. Please help me. thanks so much

Hi there,
I encountered a similar error when build with scons.
$: scons
scons: Reading SConscript files ...
Detected compiler gcc 7.4.0
scons: done reading SConscript files.
scons: Building targets ...
scons: `build/liblogcabin.a' is up to date.
scons: `build/Client/ServerControl' is up to date.
scons: `build/Examples/Benchmark' is up to date.
scons: `build/Examples/FailoverTest' is up to date.
scons: `build/Examples/HelloWorld' is up to date.
scons: `build/Examples/Reconfigure' is up to date.
scons: `build/Examples/ReconfigureTest' is up to date.
scons: `build/Examples/SmokeTest' is up to date.
scons: `build/Examples/TreeOps' is up to date.
scons: *** [build/test/gtest-all.o] Source `gtest/src/gtest-all.cc' not found, needed by target `build/test/gtest-all.o'.
scons: building terminated because of errors.

How can I fix it?
Thank you so much.


Could not find a declaration file or module

Could not find a declaration file for module 'c:xxxxx/node_modules/vue-burger-menu'. 'c:xxxxx/node_modules/vue-burger-menu/dist/vue-burger-menu.common.js' implicitly has an 'any' type.Vetur(7016)

I'm also facing the same issue here.
module "/Users/vparannattilcherul/code/sunrise-spa/node_modules/vue-burger-menu/dist/vue-burger-menu.common" Could not find a declaration file for module 'vue-burger-menu'. '/Users/vparannattilcherul/code/sunrise-spa/node_modules/vue-burger-menu/dist/vue-burger-menu.common.js' implicitly has an 'any' type.   Try npm i --save-dev @types/vue-burger-menuif it exists or add a new declaration (.d.ts) file containingdeclare module 'vue-burger-menu';ts(7016) No quick fixes available
This is what my VS Code editor shows.


Makefile: debug target should mkdir bin

The debug target should create the bin directory, just like the "all" target.
Also, "debug" and "man" should be added to .PHONY.

This should be done in the latest commit (see the changelog).


Use document instead of $document

Reverts commit 3963afb8. Fixes #133. Supersedes #136, which doesn’t take into consideration that neither $document.body nor $document.documentElement exist.

Sorry, if I had looked first, I would have seen that there are the working pull requests #134 and #135 already open.


Add Benchmark Comparison

Description
As title, I added a benchmark comparison between QuantumToolbox.jl, QuTiP, dynamiqs, and QuantumOptics.jl. I made a script file which makes everything reproducible. I added the plot on both the Documentation and the README.

The figure should not be tracked by git, cause it keeps updating everytime the script is executed.
So, I suggest we don't put the figure in README.md


Image Scaling Feture

Hi, thank you so much for this library. I want to scale the imageview.
How can I do? Can you add a feture?

i have the same problem here where is this guy

Hi, you can with new version.
implementation 'com.github.denzcoskun:ImageSlideshow:0.0.7'
Please read the readme before use. Scale types changed.


Upload and read from knowledge base

Feature Request: AI-Powered Code Pattern Replication
Overview
Could you implement a feature that allows CodeBuddy, our generative AI system, to learn and replicate coding patterns from user-provided text files? This functionality will enable the automated creation of customized modules and components based on user-defined patterns.
Objectives
Enable users to upload text files containing their preferred coding patterns for component creation.
Codebuddy analyzes and learns from these patterns and generates code components that adhere to the learned patterns.
User Story
As a developer, I want to upload my coding patterns for component creation so that CodeBuddy can automatically generate similar components following my preferred style and structure. This will streamline my workflow for recurrent tasks and ensure consistency across my project.
Proposed Functionality
File Upload: Provide an interface for users to upload text files containing their coding patterns.
Knowledge Base: Create a system to store and manage the extracted patterns.
Technical Considerations
Acceptance Criteria
Users can successfully upload text files containing coding patterns.
CodeBuddy can accurately analyze and learn from the uploaded patterns.
Generated components closely match the style and structure of the original patterns.
The system performs efficiently, generating new components within a reasonable timeframe.
The user interface is intuitive and provides clear feedback throughout the process.
Future Enhancements
Support for multiple pattern libraries per user
Pattern sharing and collaboration features

PR: https://github.com/olasunkanmi-SE/codebuddy/pull/62

sample knowledge base
ola.txt


The CommandAPI should safeguard against duplicate command path types

Description
If a user registers multiple commands that have the same argument type paths, the CommandAPI should tell the user that there are commands with identical types which can lead to unexpected outcomes.
For example, if someone registers the following:
new CommandAPICommand("test")
	.withArguments(new StringArgument("str_1"))
	.executesPlayer((player, args) -> {
		// str1.set((String) args[0]);
	})
	.register();

new CommandAPICommand("test")
	.withArguments(new StringArgument("str_2"))
	.executesPlayer((player, args) -> {
		// str2.set((String) args[0]);
	})
	.register();

The following JSON is generated (as expected):
{
  "type": "root",
  "children": {
    "test": {
      "type": "literal",
      "children": {
        "str_1": {
          "type": "argument",
          "parser": "brigadier:string",
          "properties": {
            "type": "word"
          },
          "executable": true
        },
        "str_2": {
          "type": "argument",
          "parser": "brigadier:string",
          "properties": {
            "type": "word"
          },
          "executable": true
        }
      }
    }
  }
}

Running /test hello will always run using str_1, and the str_2 case will never be called. During command registration, an error warning message should be displayed on the second argument's registration - this will produce the same result (i.e. the second command can't be run) at all times.
Expected code
Fail to register the command message is displayed:
Failed to register command:

    /test str_2<StringArgument>

Because it conflicts with this previously registered command:

    /test str_1<StringArgument>

This should only be called when the whole path is identical in argument type. This doesn't apply to literal arguments.
Extra details
No response

This also doesn't apply to arguments that are distinguishable. For example, an integer argument with bounds (1, 10) and another with bounds (50, 100) are distinguishable if the values provided are 5 and 60.
However, if the first argument has bounds (1, 100) and the values are 5 and 60, they're indistinguishable (and all pass to the first case)

Alternatively (and ideally), the CommandAPI should use dispatcher.findAmbiguities to find the ambiguities in the command tree and generate some meaningful output based on that (which saves trying to implement an ambiguity checker)

Alternatively (and ideally), the CommandAPI should use dispatcher.findAmbiguities to find the ambiguities in the command tree and generate some meaningful output based on that (which saves trying to implement an ambiguity checker)

In fact, in 9.5.1, distinguishable BooleanArguments and IntegrArguments were also blocked.

distinguishable BooleanArguments and IntegrArguments were also blocked

I think you've a case of a duplicate command path. When Brigadier registers commands, it merges command paths based on the node names of the arguments. When this happens, the ArgumentTypes being used default to the first command, while the command executor defaults to the second.
In this case, you tried to register the two commands:
lumina config modify <node: String> <value: Integer> {
    get(node) as String
    get(value) as Integer
}

lumina config modify <node: String> <value: Boolean> {
    get(node) as String
    get(value) as Boolean
}

If the CommandAPI gave these two commands to Brigadier, they would get merged into this command:
lumina config modify <node: String> <value: Integer> {
    get(node) as String
    get(value) as Boolean
}

Here, the command path defines value as an Integer, but the executor tries to cast it to a Boolean. This would sneakily cause a ClassCastException, so the CommandAPI checks for this situation and avoids it by reporting that error.
Perhaps the exception message could be changed to more clearly define what conflicts means and what to do about it. In your case, you can either give the IntegerArgument and BooleanArgument different node names, or you can put them on different command paths (e.g. /lumina config modify <node: String> int <value: Integer> and /lumina config modify <node: String> boolean <value: Boolean>.

To clarify, this issue considers the case where two nodes have different node names, but ArgumentTypes that are ambiguous. Brigadier will default to the first successful command path, which can leave other paths inaccessible.
test {
    <string1: String> {
        // This StringArgument always successfully parses the input and is always used
    }
    <string2: String> {
        // This StringArgument and any of its children are inaccessible
    }
    <int: Integer> {
        // This IntegerArgument is inaccessible
    }
}

The CommandAPI does not yet do anything to avoid making these inaccessible commands.

I'm sorry, this is really my question, do you mean if you need to use different ArgumentTypes in the same place, you should use different names?
It's been tested and it works, and my question. sorry


Proposal: version changelogs

It would be awesome if Laravel had a changelog for every version. This is quite simple to do with using PR history.
See https://github.com/twbs/bootstrap/releases

Unlikely to ever happen. The history is VERY large, and it would take hours to generate a meaningful, correct, complete history. Just dumping a few major things, or dumping the commit log isn't really good enough.


Option to change completion color

Optimized config module with Config class.
Config option to change OpenAI completion color in terminal.

Is this expected?
> echo 'DEFAULT_COLOR=bright_green' > ~/.config/shell_gpt/.sgptrc
> cat ~/.config/shell_gpt/.sgptrc
DEFAULT_COLOR=bright_green
> sgpt "what day is today"
Traceback (most recent call last):
  File "/home/linuxbrew/.linuxbrew/bin/sgpt", line 5, in <module>
    from sgpt import cli
  File<EMAIL_ADDRESS>line 3, in <module>
    from .client import OpenAIClient as OpenAIClient
  File<EMAIL_ADDRESS>line 11, in <module>
    CACHE_LENGTH = int(config.get("CACHE_LENGTH"))
  File<EMAIL_ADDRESS>line 64, in get
    assert value, UsageError(f"Config missing: {key}.")
AssertionError: Config missing: CACHE_LENGTH.

Adding CACHE_LENGTH doesn't fix it, it just requires to add all of config vars to config, instead of just picking default values.
Also sgpt ignores env vars set on the command line (see screenshot):
> DEFAULT_COLOR=bright_green sgpt "what day is today"
Today is [insert current day of the week].

And same for var exported into env:

Verify you have latest version:

should output Version: 0.8.7
Update your version of ShellGPT:
pip install shell-gpt --upgrade --no-cache


Missing xml declaration

Hi there - I'm not sure what this PR is trying to achieve.  Can you elaborate on this change?

hi ,Sorry for that , i was want to send last commit on new PR and close this one but i made mistake and commit that in here ;
in application in fragment_view_pager title of the toolbar when toolbar is under status bar is semi visible (status bar is transparent)
and statusBarScrim will fix that (when toolbar is under status bar status bar color will change to not transparent color in this case colorPrimaryDark)

@googlebot I consent.


Fix failing tests + make Git tests more robust

the tests were failing just when executed directly
using Maven (running from IDE was OK). However,
the clean-up should be done anyway.
the Git tests are using random new port every
time. This makes them more robust in case there
is rogue process listeting on the default port

I think it makes sense to cherry-pick the fixes also into master and 0.6.x.

@porcelli - would you mind taking a look please (since it relates to nio2 related things)
@psiroky - do you mean to target 0.5.x? This would affect only KIE 6.2.x code. We'd need the same on master to apply to KIE 6.3.0-SNAPSHOT.

@manstis agreed, we should fix this on master too (and probably also 0.6.x?). See the last line in the description.


tridentControllerPluginNodeSelector/tridentNodePluginNodeSelector  won't work with "true" value

Describe the bug
Trying to use tridentControllerPluginNodeSelector and tridentNodePluginNodeSelector with helm chart setup providing the following values per yaml file would fail:
tridentControllerPluginNodeSelector:
  node-role.kubernetes.io/worker: "true"

tridentNodePluginNodeSelector:
  node-role.kubernetes.io/worker: "true"

This bug is exactly the same one which is reported in new nodeSelectors are not working when label value contains "true".
According to this update https://github.com/NetApp/trident/issues/700#issuecomment-1195891827, it's fixed in Trident 22.07 release, but some users reported it still exists in 23.04.0, 23.07.0, 23.10, and I hit this bug with 24.02 release.
I confirmed that Parajwal V brought in this problem again on 03/06/23 98c0d9ae, which Arnav Srivastava had solved on 06/01/22 a53cf69e.
Environment
Provide accurate information about the environment to help us reproduce the issue.

Trident version: 24.02
Trident installation flags used: helm setup with above custom yaml
Container runtime: [e.g. Docker 19.03.1-CE]
Kubernetes version: 1.28.3
Kubernetes enabled feature gates: -
OS: Ubuntu 24.04LTS
NetApp backend types: ONTAP NAS
Other:

Kustomize version: 5.3.0

To Reproduce
see above.
Expected behavior
node selector handles the value "true" correctly.

Hi @kmizumar , we are using the nodeAffinity and podAffinity with IN operator, which works on the set of strings.
You're trying to use node-role.kubernetes.io/worker: "true" which treats it as string and fails.

Hi @prajwalv-netapp, I also got the same behavior while trying to use a label with value set to "true" in the Helm values.
I tried as you mentioned by putting "'true'" in the value for the key used in tridentNodePluginNodeSelector in Helm.
This translates to '''true''' in the TridentOrchestrator and the operator correctly patches the deamonSet.
Nevertheless, I don't understand what you mean that the IN operator is working on a set of strings being the problem?
I got the following error in the operator when trying to use "true" :
json: cannot unmarshal bool into Go struct field NodeSelectorRequirement.spec.template.spec.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms.matchExpressions.values of type string, requeuing"
This seems like it is the wrong type (as described in the bug mentioned by @kmizumar) and not due to the fact that it is not a list.
In the end, I think the value "true" should be usable as is.

Hi @prajwalv-netapp, I also got the same behavior while trying to use a label with value set to "true" in the Helm values. I tried as you mentioned by putting "'true'" in the value for the key used in tridentNodePluginNodeSelector in Helm. This translates to '''true''' in the TridentOrchestrator and the operator correctly patches the deamonSet.
Nevertheless, I don't understand what you mean that the IN operator is working on a set of strings being the problem? I got the following error in the operator when trying to use "true" : json: cannot unmarshal bool into Go struct field NodeSelectorRequirement.spec.template.spec.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms.matchExpressions.values of type string, requeuing"
This seems like it is the wrong type (as described in the bug mentioned by @kmizumar) and not due to the fact that it is not a list. In the end, I think the value "true" should be usable as is.

Hi @E-Zurg ,
I provided a workaround until the Trident fixes this. If you refer to the below document, it states that IN would treat each value as string but the value true is interpreted as a boolean and hence you see the error.
https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#operators


List up necessary tests

List the necessary e2e tests to make sure the application is working as expected.

Show device selector on join page
Show volume movement when device is selected
Have user A join
Show announcement after joining
Be able to drag avatar
Have another user B join
show announcement
See the user B's avatar
See the moved user A avatar on user B's screen
See user B's avatar move on user A's screen and vice versa
Hear user A's audio on user B's side
Make sure volume varies depending on distance between user avatars

Can be implemented as we go.


Bug: The Bitmap in MainActivity / ManageFragement may cause OUT OF MEMORY error.

Reason: Memory leak caused when loading images.
Solution: Use Glide library to load images.