netopeer2-server Segmentation fault & netopeer2-cli SSH channel poll error (Socket error: disconnected)

Hi,
I tried to build the Netopeer2 environment on openwrt. I connected to netopeer2-server using netopeer2-cli, and then sent the ‘get-data’ command using netopeer2-cli, but the netopeer2-server Segmentation fault, please refer to log information.
Thanks,
Best regards.
log information:
netopeer2-server log.
root@OpenWrt:~#
root@OpenWrt:~#
root@OpenWrt:~#
root@OpenWrt:~# netopeer2-server -d -v 3
[INF]: LY: Plugin "/usr/lib/libyang/extensions/yangdata.so" successfully loaded.
[INF]: LY: Plugin "/usr/lib/libyang/extensions/nacm.so" successfully loaded.
[INF]: LY: Plugin "/usr/lib/libyang/extensions/metadata.so" successfully loaded.
[INF]: LY: Plugin "/usr/lib/libyang/user_types/user_yang_types.so" successfully loaded.
[INF]: LY: Plugin "/usr/lib/libyang/user_types/user_inet_types.so" successfully loaded.
[INF]: LY: Reading module "ietf-yang-metadata".
[INF]: LY: Module "ietf-yang-metadata@2016-08-05" successfully parsed as implemented.
[INF]: LY: Reading module "yang".
[INF]: LY: Resolving "yang" unresolved schema nodes and their constraints...
[INF]: LY: All "yang" schema nodes and constraints resolved.
[INF]: LY: Module "yang@2017-02-20" successfully parsed as implemented.
[INF]: LY: Reading module "ietf-inet-types".
[INF]: LY: Resolving derived type "union" failed, it will be attempted later.
[INF]: LY: Resolving derived type "union" failed, it will be attempted later.
[INF]: LY: Resolving derived type "union" failed, it will be attempted later.
[INF]: LY: Resolving derived type "union" failed, it will be attempted later.
[INF]: LY: Resolving "ietf-inet-types" unresolved schema nodes and their constraints...
[INF]: LY: All "ietf-inet-types" schema nodes and constraints resolved.
[INF]: LY: Module "ietf-inet-types@2013-07-15" successfully parsed as implemented.
[INF]: LY: Reading module "ietf-yang-types".
[INF]: LY: Module "ietf-yang-types@2013-07-15" successfully parsed as implemented.
[INF]: LY: Searching for "ietf-yang-types" in /etc/sysrepo/yang.
[INF]: LY: Resolving "sysrepo" unresolved schema nodes and their constraints...
[INF]: LY: All "sysrepo" schema nodes and constraints resolved.
[INF]: LY: Module "sysrepo@2020-01-15" successfully parsed as implemented.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: SR: Scheduled changes not applied because of other existing connections.
[INF]: LY: Searching for "ietf-datastores" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Module "ietf-datastores@2018-02-14" successfully parsed as implemented.
[INF]: LY: Searching for "ietf-yang-library" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Searching for "ietf-inet-types" in /etc/sysrepo/yang.
[INF]: LY: Searching for "ietf-datastores" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Module "ietf-yang-library@2019-01-04" successfully parsed as implemented.
[INF]: LY: Searching for "sysrepo-monitoring" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Resolving "sysrepo-monitoring" unresolved schema nodes and their constraints...
[INF]: LY: All "sysrepo-monitoring" schema nodes and constraints resolved.
[INF]: LY: Module "sysrepo-monitoring@2020-04-17" successfully parsed as implemented.
[INF]: LY: Searching for "ietf-netconf-with-defaults" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Searching for "ietf-netconf" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Searching for "ietf-netconf-acm" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Module "ietf-netconf-acm@2018-02-14" successfully parsed as imported.
[INF]: LY: Module "ietf-netconf@2013-09-29" successfully parsed as imported.
[INF]: LY: Resolving "ietf-netconf-with-defaults" unresolved schema nodes and their constraints...
[INF]: LY: All "ietf-netconf-with-defaults" schema nodes and constraints resolved.
[INF]: LY: Module "ietf-netconf-with-defaults@2011-06-01" successfully parsed as implemented.
[INF]: LY: Searching for "ietf-netconf-notifications" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Resolving "ietf-netconf-notifications" unresolved schema nodes and their constraints...
[INF]: LY: All "ietf-netconf-notifications" schema nodes and constraints resolved.
[INF]: LY: Module "ietf-netconf-notifications@2012-02-06" successfully parsed as implemented.
[INF]: LY: Searching for "ietf-origin" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Searching for "ietf-yang-metadata" in /etc/sysrepo/yang.
[INF]: LY: Resolving "ietf-origin" unresolved schema nodes and their constraints...
[INF]: LY: All "ietf-origin" schema nodes and constraints resolved.
[INF]: LY: Module "ietf-origin@2018-02-14" successfully parsed as implemented.
[INF]: LY: Module "ietf-netconf-acm@2018-02-14" now implemented.
[INF]: LY: Searching for "ietf-netconf-monitoring" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Module "ietf-netconf-monitoring@2010-10-04" successfully parsed as implemented.
[INF]: LY: Searching for "ietf-netconf-nmda" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Searching for "ietf-origin" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Searching for "ietf-netconf-with-defaults" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Resolving "ietf-netconf-nmda" unresolved schema nodes and their constraints...
[INF]: LY: All "ietf-netconf-nmda" schema nodes and constraints resolved.
[INF]: LY: Module "ietf-netconf-nmda@2019-01-07" successfully parsed as implemented.
[INF]: LY: Searching for "nc-notifications" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Searching for "notifications" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Module "notifications@2008-07-14" successfully parsed as imported.
[INF]: LY: Module "nc-notifications@2008-07-14" successfully parsed as implemented.
[INF]: LY: Module "notifications@2008-07-14" now implemented.
[INF]: LY: Searching for "ietf-x509-cert-to-name" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Module "ietf-x509-cert-to-name@2014-12-10" successfully parsed as implemented.
[INF]: LY: Searching for "ietf-crypto-types" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Module "ietf-crypto-types@2019-07-02" successfully parsed as implemented.
[INF]: LY: Searching for "ietf-keystore" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Searching for "ietf-crypto-types" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Resolving "ietf-keystore" unresolved schema nodes and their constraints...
[INF]: LY: All "ietf-keystore" schema nodes and constraints resolved.
[INF]: LY: Module "ietf-keystore@2019-07-02" successfully parsed as implemented.
[INF]: LY: Searching for "ietf-truststore" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Module "ietf-truststore@2019-07-02" successfully parsed as implemented.
[INF]: LY: Searching for "ietf-tcp-common" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Module "ietf-tcp-common@2019-07-02" successfully parsed as implemented.
[INF]: LY: Searching for "ietf-ssh-server" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Searching for "ietf-ssh-common" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Module "ietf-ssh-common@2019-07-02" successfully parsed as imported.
[INF]: LY: Searching for "ietf-keystore" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Searching for "iana-crypt-hash" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Module "iana-crypt-hash@2014-08-06" successfully parsed as imported.
[INF]: LY: Module "ietf-ssh-server@2019-07-02" successfully parsed as implemented.
[INF]: LY: Searching for "ietf-tls-server" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Searching for "ietf-tls-common" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Module "ietf-tls-common@2019-07-02" successfully parsed as imported.
[INF]: LY: Searching for "ietf-truststore" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Module "ietf-tls-server@2019-07-02" successfully parsed as implemented.
[INF]: LY: Searching for "ietf-netconf-server" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Searching for "ietf-x509-cert-to-name" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Searching for "ietf-tcp-client" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Searching for "ietf-tcp-common" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Module "ietf-tcp-client@2019-07-02" successfully parsed as imported.
[INF]: LY: Searching for "ietf-tcp-server" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Module "ietf-tcp-server@2019-07-02" successfully parsed as imported.
[INF]: LY: Resolving "ietf-netconf-server" unresolved schema nodes and their constraints...
[INF]: LY: All "ietf-netconf-server" schema nodes and constraints resolved.
[INF]: LY: Module "ietf-netconf-server@2019-07-02" successfully parsed as implemented.
[INF]: LY: Module "ietf-inet-types@2013-07-15" now implemented.
[INF]: LY: Searching for "ietf-hardware" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Searching for "iana-hardware" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Module "iana-hardware@2018-03-13" successfully parsed as imported.
[INF]: LY: Resolving "ietf-hardware" unresolved schema nodes and their constraints...
[INF]: LY: All "ietf-hardware" schema nodes and constraints resolved.
[INF]: LY: Module "ietf-hardware@2018-03-13" successfully parsed as implemented.
[INF]: LY: Searching for "o-ran-hardware" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Searching for "ietf-hardware" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Resolving "o-ran-hardware" unresolved schema nodes and their constraints...
[INF]: LY: All "o-ran-hardware" schema nodes and constraints resolved.
[INF]: LY: Module "o-ran-hardware@2020-02-19" successfully parsed as implemented.
[INF]: LY: Searching for "o-ran-file-management" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Resolving "o-ran-file-management" unresolved schema nodes and their constraints...
[INF]: LY: All "o-ran-file-management" schema nodes and constraints resolved.
[INF]: LY: Module "o-ran-file-management@2019-07-03" successfully parsed as implemented.
[INF]: LY: Searching for "o-ran-software-management" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Searching for "o-ran-hardware" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Searching for "o-ran-file-management" in /etc/sysrepo/yang.
[INF]: LY: Loading schema from<EMAIL_ADDRESS>file.
[INF]: LY: Resolving "o-ran-software-management" unresolved schema nodes and their constraints...
[INF]: LY: All "o-ran-software-management" schema nodes and constraints resolved.
[INF]: LY: Module "o-ran-software-management@2019-07-03" successfully parsed as implemented.
[WRN]: SR: Cleaning up after a non-existent sysrepo client with PID 3492.
[INF]: SR: Ext SHM was defragmented and 7784 B were saved.
[INF]: SR: Session 8 (user "root") created.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: There is no leafref "/ietf-keystore:keystore/ietf-keystore:asymmetric-keys/ietf-keystore:asymmetric-key/ietf-keystore:name" with the value "genkey", but it is not required.
[INF]: LY: All data nodes and constraints resolved.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: LN: Listening on <IP_ADDRESS>:830 for SSH connections.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Ext SHM was defragmented and 4272 B were saved.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: SR: Ext SHM was defragmented and 4464 B were saved.
[INF]: SR: Triggering "ietf-keystore" "done" event on enabled data.
[INF]: SR: Triggering "ietf-truststore" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-acm" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-acm" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-acm" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-acm" "done" event on enabled data.
[INF]: LN: Accepted a connection on <IP_ADDRESS>:830.
[INF]: SR: Session 9 (user "root") created.
[2015/08/02 11:13:29.641635, 2] ssh_pki_import_privkey_base64:  Trying to decode privkey passphrase=false
[2015/08/02 11:13:29.646818, 2] ssh_server_connection_callback:  SSH client banner: SSH-2.0-libssh_0.9.3
[2015/08/02 11:13:29.646856, 2] ssh_analyze_banner:  Analyzing banner: SSH-2.0-libssh_0.9.3
[2015/08/02 11:13:29.649102, 2] ssh_kex_select_methods:  Negotiated curve25519-sha256,rsa-sha2-512,aes256-gcm@openssh.com,aes256-gcm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-256-etm@openssh.com,none,none,,
[2015/08/02 11:13:29.663692, 2] ssh_packet_server_curve25519_init:  SSH_MSG_KEX_ECDH_REPLY sent
[2015/08/02 11:13:29.663745, 2] ssh_init_rekey_state:  Set rekey after<PHONE_NUMBER> blocks
[2015/08/02 11:13:29.663771, 2] ssh_init_rekey_state:  Set rekey after<PHONE_NUMBER> blocks
[2015/08/02 11:13:29.663827, 2] ssh_packet_server_curve25519_init:  SSH_MSG_NEWKEYS sent
[2015/08/02 11:13:29.665946, 2] ssh_packet_newkeys:  Received SSH_MSG_NEWKEYS
[INF]: LN: Received an SSH message "request-service" of subtype "ssh-userauth".
[INF]: LN: Received an SSH message "request-auth" of subtype "none".
[INF]: LN: Received an SSH message "request-auth" of subtype "interactive".
[2015/08/02 11:13:32.555050, 2] ssh_message_auth_interactive_request:  Warning: Got a keyboard-interactive response but it seems we didn't send the request.
[INF]: LN: Received an SSH message "request-auth" of subtype "interactive".
[INF]: LN: User "root" authenticated.
[INF]: LN: Received an SSH message "request-channel-open" of subtype "session".
[INF]: LN: Received an SSH message "request-channel" of subtype "subsystem".
[2015/08/02 11:13:39.886512, 2] grow_window:  growing window (channel 43:43) to 1280000 bytes
[2015/08/02 11:13:39.886768, 2] channel_rcv_change_window:  Adding 1217013 bytes to channel (43:43) (from 61173 bytes)
[INF]: SR: Session 10 (user "root") created.
[INF]: SR: There are no subscribers for "ietf-netconf-notifications" notifications.
[INF]: NP: Generated new event (netconf-session-start).
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-datastores" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 1: thread 3 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: SR: Published event "rpc" "/ietf-netconf:get" with ID 1 priority 0 for 1 subscribers.
[INF]: SR: Processing "/ietf-netconf:get" "rpc" event with ID 1 priority 0 (remaining 1 subscribers).
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: SR: Successful processing of "rpc" event with ID 1 priority 0 (remaining 0 subscribers).
[INF]: SR: Event "rpc" with ID 1 priority 0 succeeded.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 1: thread 3 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "sysrepo" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 1: thread 3 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "sysrepo-monitoring" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 1: thread 3 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-datastores" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 1: thread 3 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-netconf-with-defaults" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 1: thread 3 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-netconf-notifications" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 1: thread 3 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-origin" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 1: thread 3 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-yang-metadata" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 1: thread 3 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-origin" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 1: thread 3 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-netconf-with-defaults" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 1: thread 3 event new RPC.
[ERR]: LN: Session 1: inactive read timeout elapsed.
[INF]: NP: Session 1: thread 3 event session terminated.
[INF]: SR: There are no subscribers for "ietf-netconf-notifications" notifications.
[INF]: NP: Generated new event (netconf-session-end).
[INF]: LN: Accepted a connection on <IP_ADDRESS>:830.
[INF]: SR: Session 11 (user "root") created.
[2015/08/02 11:14:26.128702, 2] ssh_pki_import_privkey_base64:  Trying to decode privkey passphrase=false
[2015/08/02 11:14:26.131179, 2] ssh_server_connection_callback:  SSH client banner: SSH-2.0-libssh_0.9.3
[2015/08/02 11:14:26.131211, 2] ssh_analyze_banner:  Analyzing banner: SSH-2.0-libssh_0.9.3
[2015/08/02 11:14:26.133441, 2] ssh_kex_select_methods:  Negotiated curve25519-sha256,rsa-sha2-512,aes256-gcm@openssh.com,aes256-gcm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-256-etm@openssh.com,none,none,,
[2015/08/02 11:14:26.147908, 2] ssh_packet_server_curve25519_init:  SSH_MSG_KEX_ECDH_REPLY sent
[2015/08/02 11:14:26.147962, 2] ssh_init_rekey_state:  Set rekey after<PHONE_NUMBER> blocks
[2015/08/02 11:14:26.147989, 2] ssh_init_rekey_state:  Set rekey after<PHONE_NUMBER> blocks
[2015/08/02 11:14:26.148023, 2] ssh_packet_server_curve25519_init:  SSH_MSG_NEWKEYS sent
[2015/08/02 11:14:26.150147, 2] ssh_packet_newkeys:  Received SSH_MSG_NEWKEYS
[INF]: LN: Received an SSH message "request-service" of subtype "ssh-userauth".
[INF]: LN: Received an SSH message "request-auth" of subtype "none".
[INF]: LN: Received an SSH message "request-auth" of subtype "interactive".
[2015/08/02 11:14:26.150768, 2] ssh_message_auth_interactive_request:  Warning: Got a keyboard-interactive response but it seems we didn't send the request.
[INF]: LN: Received an SSH message "request-auth" of subtype "interactive".
[INF]: LN: User "root" authenticated.
[INF]: LN: Received an SSH message "request-channel-open" of subtype "session".
[INF]: LN: Received an SSH message "request-channel" of subtype "subsystem".
[2015/08/02 11:14:30.332910, 2] grow_window:  growing window (channel 43:43) to 1280000 bytes
[2015/08/02 11:14:30.333162, 2] channel_rcv_change_window:  Adding 1217013 bytes to channel (43:43) (from 61173 bytes)
[INF]: SR: Session 12 (user "root") created.
[INF]: SR: There are no subscribers for "ietf-netconf-notifications" notifications.
[INF]: NP: Generated new event (netconf-session-start).
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-datastores" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 2: thread 0 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: SR: Published event "rpc" "/ietf-netconf:get" with ID 2 priority 0 for 1 subscribers.
[INF]: SR: Processing "/ietf-netconf:get" "rpc" event with ID 2 priority 0 (remaining 1 subscribers).
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: SR: Successful processing of "rpc" event with ID 2 priority 0 (remaining 0 subscribers).
[INF]: SR: Event "rpc" with ID 2 priority 0 succeeded.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 2: thread 2 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "sysrepo" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 2: thread 4 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "sysrepo-monitoring" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 2: thread 3 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-datastores" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 2: thread 2 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-netconf-with-defaults" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 2: thread 4 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-netconf-notifications" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 2: thread 3 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-origin" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 2: thread 2 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-yang-metadata" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 2: thread 4 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-origin" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 2: thread 3 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-netconf-with-defaults" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 2: thread 2 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: SR: Published event "rpc" "/ietf-netconf:get-config" with ID 1 priority 0 for 1 subscribers.
[INF]: SR: Processing "/ietf-netconf:get-config" "rpc" event with ID 1 priority 0 (remaining 1 subscribers).
[INF]: SR: Successful processing of "rpc" event with ID 1 priority 0 (remaining 0 subscribers).
[INF]: SR: Event "rpc" with ID 1 priority 0 succeeded.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 2: thread 4 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: SR: Published event "rpc" "/ietf-netconf:get-config" with ID 2 priority 0 for 1 subscribers.
[INF]: SR: Processing "/ietf-netconf:get-config" "rpc" event with ID 2 priority 0 (remaining 1 subscribers).
[INF]: SR: Successful processing of "rpc" event with ID 2 priority 0 (remaining 0 subscribers).
[INF]: SR: Event "rpc" with ID 2 priority 0 succeeded.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 2: thread 4 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: SR: Published event "rpc" "/ietf-netconf:get-config" with ID 3 priority 0 for 1 subscribers.
[INF]: SR: Processing "/ietf-netconf:get-config" "rpc" event with ID 3 priority 0 (remaining 1 subscribers).
[INF]: SR: Successful processing of "rpc" event with ID 3 priority 0 (remaining 0 subscribers).
[INF]: SR: Event "rpc" with ID 3 priority 0 succeeded.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 2: thread 4 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: SR: Published event "rpc" "/ietf-netconf:get-config" with ID 4 priority 0 for 1 subscribers.
[INF]: SR: Processing "/ietf-netconf:get-config" "rpc" event with ID 4 priority 0 (remaining 1 subscribers).
[INF]: SR: Successful processing of "rpc" event with ID 4 priority 0 (remaining 0 subscribers).
[INF]: SR: Event "rpc" with ID 4 priority 0 succeeded.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 2: thread 4 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: SR: Published event "rpc" "/ietf-netconf:get-config" with ID 5 priority 0 for 1 subscribers.
[INF]: SR: Processing "/ietf-netconf:get-config" "rpc" event with ID 5 priority 0 (remaining 1 subscribers).
[INF]: SR: Successful processing of "rpc" event with ID 5 priority 0 (remaining 0 subscribers).
[INF]: SR: Event "rpc" with ID 5 priority 0 succeeded.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 2: thread 2 event new RPC.
[ERR]: LN: Session 2: inactive read timeout elapsed.
[INF]: NP: Session 2: thread 2 event session terminated.
[INF]: SR: There are no subscribers for "ietf-netconf-notifications" notifications.
[INF]: NP: Generated new event (netconf-session-end).
[INF]: LN: Accepted a connection on <IP_ADDRESS>:830.
[INF]: SR: Session 13 (user "root") created.
[2015/08/02 11:15:26.730370, 2] ssh_pki_import_privkey_base64:  Trying to decode privkey passphrase=false
[2015/08/02 11:15:26.732823, 2] ssh_server_connection_callback:  SSH client banner: SSH-2.0-libssh_0.9.3
[2015/08/02 11:15:26.732855, 2] ssh_analyze_banner:  Analyzing banner: SSH-2.0-libssh_0.9.3
[2015/08/02 11:15:26.735079, 2] ssh_kex_select_methods:  Negotiated curve25519-sha256,rsa-sha2-512,aes256-gcm@openssh.com,aes256-gcm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-256-etm@openssh.com,none,none,,
[2015/08/02 11:15:26.749557, 2] ssh_packet_server_curve25519_init:  SSH_MSG_KEX_ECDH_REPLY sent
[2015/08/02 11:15:26.749609, 2] ssh_init_rekey_state:  Set rekey after<PHONE_NUMBER> blocks
[2015/08/02 11:15:26.749636, 2] ssh_init_rekey_state:  Set rekey after<PHONE_NUMBER> blocks
[2015/08/02 11:15:26.749668, 2] ssh_packet_server_curve25519_init:  SSH_MSG_NEWKEYS sent
[2015/08/02 11:15:26.751792, 2] ssh_packet_newkeys:  Received SSH_MSG_NEWKEYS
[INF]: LN: Received an SSH message "request-service" of subtype "ssh-userauth".
[INF]: LN: Received an SSH message "request-auth" of subtype "none".
[INF]: LN: Received an SSH message "request-auth" of subtype "interactive".
[2015/08/02 11:15:26.752532, 2] ssh_message_auth_interactive_request:  Warning: Got a keyboard-interactive response but it seems we didn't send the request.
[INF]: LN: Received an SSH message "request-auth" of subtype "interactive".
[INF]: LN: User "root" authenticated.
[INF]: LN: Received an SSH message "request-channel-open" of subtype "session".
[INF]: LN: Received an SSH message "request-channel" of subtype "subsystem".
[2015/08/02 11:15:30.349768, 2] grow_window:  growing window (channel 43:43) to 1280000 bytes
[2015/08/02 11:15:30.350019, 2] channel_rcv_change_window:  Adding 1217013 bytes to channel (43:43) (from 61173 bytes)
[INF]: SR: Session 14 (user "root") created.
[INF]: SR: There are no subscribers for "ietf-netconf-notifications" notifications.
[INF]: NP: Generated new event (netconf-session-start).
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-datastores" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 3: thread 0 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: SR: Published event "rpc" "/ietf-netconf:get" with ID 3 priority 0 for 1 subscribers.
[INF]: SR: Processing "/ietf-netconf:get" "rpc" event with ID 3 priority 0 (remaining 1 subscribers).
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: SR: Successful processing of "rpc" event with ID 3 priority 0 (remaining 0 subscribers).
[INF]: SR: Event "rpc" with ID 3 priority 0 succeeded.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 3: thread 0 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "sysrepo" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 3: thread 0 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "sysrepo-monitoring" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 3: thread 0 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-datastores" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 3: thread 3 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-netconf-with-defaults" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 3: thread 0 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-netconf-notifications" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 3: thread 3 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-origin" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 3: thread 0 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-yang-metadata" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 3: thread 4 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-origin" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 3: thread 3 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LN: Schema "ietf-netconf-with-defaults" was requested.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: NP: Session 3: thread 0 event new RPC.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: LY: Resolving unresolved data nodes and their constraints...
[INF]: LY: All data nodes and constraints resolved.
[INF]: SR: Published event "rpc" "/ietf-netconf-nmda:get-data" with ID 1 priority 0 for 1 subscribers.
[INF]: SR: Processing "/ietf-netconf-nmda:get-data" "rpc" event with ID 1 priority 0 (remaining 1 subscribers).
Segmentation fault
root@OpenWrt:~#
root@OpenWrt:~#
netopeer2-cli log.
root@OpenWrt:~# netopeer2-cli
get_netconf_dir: Configuration directory "/root/.netopeer2-cli" did not exist, created.
load_config: No saved history.
load_config: No saved configuration.

connect localhost
The authenticity of the host 'localhost' cannot be established.
ssh-rsa key fingerprint is bd:b3:59:b3:a8:2a:c3:dd:7d:18:5d:d7:da:a3:c5:fa:45:3c:81:b6.
Are you sure you want to continue connecting (yes/no)? yes
Interactive SSH Authentication
Type your password:
Password:
get-config -h
get-config [--help] --source running|startup|candidate [--filter-subtree[=] | --filter-xpath ] [--defaults report-all|report-all-tagged|trim|explicit] [--out ] [--rpc-timeout ]
get-config --source running
nc ERROR: Session 1: communication socket unexpectedly closed.
cli_send_recv: Failed to send the RPC.
status
Client is not connected to any NETCONF server.
connect localhost
Interactive SSH Authentication
Type your password:
Password:
get-data -h
get-data [--help] --datastore running|startup|candidate|operational [--filter-subtree[=] | --filter-xpath ] [--config true|false] [--origin ]* [--negated-origin] [--depth ] [--with-origin] [--defaults report-all|report-all-tagged|trim|explicit] [--out ] [--rpc-timeout ]
get-data --datastore running
nc ERROR: Session 2: communication socket unexpectedly closed.
cli_send_recv: Failed to send the RPC.
connect localhost
Interactive SSH Authentication
Type your password:
Password:
get-data --datastore running
nc ERROR: Session 3: SSH channel poll error (Socket error: disconnected).
cli_send_recv: Failed to receive a reply.
connect localhost
nc ERROR: Unable to connect to localhost:830 (Connection refused).
cmd_connect: Connecting to the localhost:830 as user "root" failed.
connect localhost
nc ERROR: Unable to connect to localhost:830 (Connection refused).
cmd_connect: Connecting to the localhost:830 as user "root" failed.

Hi,
unfortunately I cannot help you based on this output only. But what netopeer2-server version are you using? Also, you have the problem with inactive timeout elapsed because you are using libssh 0.9.3 and libnetconf2 will refuse to compile with it so you must have bypassed it somehow. I am wondering what else you solved like this and whether it is not the cause for your problem.
Regards,
Michal

Thanks, this issue has been resolved [https://github.com/CESNET/netopeer2/issues/584].


improve the documentation

Clearly state that users need to start with the GKE doc.
Update the example applications.
Be more specific on the SA role.
Sync the doc with the GKE doc.
Talk about internal errors in the common issues section.
Be more specific on how to troubleshoot and check the errors.
Be more specific when the WI fails to work on TSG.

Fixed in commit https://github.com/GoogleCloudPlatform/gcs-fuse-csi-driver/commit/35cefc94f04a5859cb0a91154618031ab2099239


Fix comment on weighted sampler

The implementation is correct (as evidenced by the unit tests), but the comment describing the binary search was incorrect.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 83.02%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2606

Relevant Lines:
3139

💛  - Coveralls


Default argument of tf.placeholder

InvalidArgumentError (see above for traceback): You must feed a value for placeholder tensor 'x' with dtype float
[[{{node x}} = Placeholderdtype=DT_FLOAT, shape=, _device="/job:localhost/replica:0/task:0/device:GPU:0"]]
I think  tf.placeholder(tf.float32, shape=None, name='x') is equivalent to  tf.placeholder(tf.float32,  name='x')? But the results are different for these two lines of code.
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution Windows10:
TensorFlow installed from pip:
TensorFlow version (use command below): 1.11.0
Python version: 3.6
CUDA/cuDNN version: 9.0
GPU model and memory: 1080Ti

Code to reproduce the issue
x = tf.placeholder(tf.float32, shape=None, name='x')
y = tf.placeholder(tf.float32, shape=None, name='y')
with tf.Session() as sess:
    total_loss = 0
    sess.run(tf.global_variables_initializer())
    _, loss_ = sess.run([optimizer, loss], feed_dict={x: 1.0, y: 2.0})

The code presented above returned InvalidArgumentError.
x = tf.placeholder(tf.float32, name='x')
y = tf.placeholder(tf.float32, name='y')
with tf.Session() as sess:
    total_loss = 0
    sess.run(tf.global_variables_initializer())
    _, loss_ = sess.run([optimizer, loss], feed_dict={x: 1.0, y: 2.0})

These code works well.

@MasKong  Could you please provide the full code so that we try to reproduce the error at our end.

@harshini-gadige sorry for late reply. I am sorry that I cannot provide the code because it is in my another device. I was trying to do a linear regression. The first snippet of code did not work well but the sceond snippet of code worked well. The only difference is that shape argument.

Hi @MasKong! We are checking to see if you still need help in this issue.
It  also seems you are using older versions(1.x versions) of Tensorflow. We recommend that you upgrade  your code base to 2.x  versions as many features and bug fixes has been done in newer versions and let us know if the issue still persists in newer versions. Thanks!


Param not allowed

Hi
After calling create I have to call an other microservice. I'd like to do with the Operation Processors after_create_resource method.
I want to be able to use the create function with these params
{
  "data": {
    "type": "registrations",
    "attributes": {
      "person_code": 7,
      "presentation_code": 1088,
      "promo_code": "WEB1000",
      "payment_plan_code": 3,
      "billing_address_line_1": "esse ex",
      "billing_city": "Excepteur ipsum cillum ad",
      "billing_region": "sed",
      "billing_postal_zip_code": "voluptate in adipisicing consectet",
      "country_billing_address": "in adipisicing irure do qui",
      "person": {
        "first_name": "in",
        "last_name": "qui tem",
        "email"<EMAIL_ADDRESS>        "telephone": "laboris in",
        "highest_level_of_education": 10,
        "work_experience": 10
      }
    }
  }
}

but I'm getting this error
{
  "errors": [
    {
      "title": "Param not allowed",
      "detail": "person is not allowed.",
      "code": "105",
      "status": "400"
    }
  ]
}

Do you know any workaround for this error?

Can you give more details?
As I see response says that RegistrationResource doesn't have attribute :person at all or in fetchable_fields

Hi
Sorry for not being clear
so basically person params are not used in registration at all. I just want to pass those to an other microservice after a registration is created

Is there anyway to add person to the permitted params?

@RitterNorbert you can add person to fetchable_fields but not tocreatable_fields and pass serialized response to another microservice. But in this case your client will receive person in response too.
Could you give some small example of what you want to do?
You mean something like:
# resource
class RegistrationResource < JSONAPI::Resource
  model 'RegistrationModel'
  attributes :email, :password, :person
  def self.creatable_fields(_options)
    [:login, :password]
end

# route
jsonapi_resources :registrations, only: [:create]

# processor
class RegistrationProcessor < JSONAPI::Processor
  after_create_resource do
    payload = result.to_hash(MyMicroServiceRegistrationSerializer)
    MyMicroService.new(payload).process!
  end
end

# serializer
class MyMicroServiceRegistrationSerializer < JSONAPI::ResourceSerializer
  def object_hash(source, include_directives = {})
    obj_hash = super
    unless source.is_a?(JSONAPI::CachedResourceFragment)
      attributes = attributes_hash(source, fetchable_fields + [:person])
      obj_hash['attributes'] = attributes unless attributes.empty?
    end
    obj_hash
  end
end

just small example. Didn't tested it

@senid231, could you please hint how 0.7.0 version processor should be upgraded to 0.9.11 ?
otherwise how to access to request/operations which were replaced?


GUACAMOLE-996: Add support for configuring group filter.

This provides ldap-group-search-filter functionallity. Tested and working OK!

Closing in favor of #497 , sorry for the mess.


nixos/mosquitto: remove the bind_interface test

Description of changes
bind_interface is the mosquitto way of trying to bind to all addresses on an interface, but it is unreliable (trying to bind to link-local v6 addresses sometimes but not always) and just prone to failure in general for reasons we have yet to discover.
since this kind of automatic behavior isn't particularly necessary in a declarative system we may as well skip it.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@ofborg test mosquitto


Modules, VersionConflict error

I'm pretty much a complete noob. I installed downloading source via git and running the install script. Now when I try to run gcalcli, I get the following output. I'm not even sure what the error is, but I can't use it.
brenda@debian:~$ gcalcli  list
Traceback (most recent call last):
  File "/usr/local/bin/gcalcli", line 4, in <module>
    __import__('pkg_resources').run_script('gcalcli==3.3', 'gcalcli')
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2876, in <module>
    working_set = WorkingSet._build_master()
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 451, in _build_master
    return cls._build_from_requirements(__requires__)
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 464, in _build_from_requirements
    dists = ws.resolve(reqs, Environment())
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 644, in resolve
    raise VersionConflict(dist, req)
pkg_resources.VersionConflict: (pyasn1 0.1.7 (/usr/lib/python2.7/dist-packages), Requirement.parse('pyasn1>=0.1.8'))

For some reason I had tried installing dependences with pip and thought they had installed correctly.
I tried installing packages python-gflags and python-dateutil from debian repos and that solved the issue. It's working correctly now.


Add command "Run QuickAdd"

Many people run their Obisidan templates to create new notes with the QuickAdd addon.
On my local fork of the obsidian-raycast extension I added a command "Run QuickAdd". Which checks the plugins, lets you select vault and runs the command.
@KevinBatdorf is this a wanted feature?
I could open a PR for this.

Hey yeah if you want to submit a PR for that I think it's a good idea.
Could you first detect whether the addon is installed and only show the command if so?
Also, probably easier to PR on the the main Raycast repo (https://github.com/raycast/extensions) but here is ok too if you prefer


Issue Classification/and other scenerio doesn't work after image classification

reproduce:

try one of the first three scenarios
then try image classification ( you don't have to wait it finished, just cancel that) (notice the exception thrown by tensorflow, it should also be a bug)
then try one of first three scenarios again, training never ends, and cancel not work.

@LittleLittleCloud Will this issue be fixed in your PR 429?

Yep

Validated working.


bug(db-postgres): Duplicated ID error when duplicate array/block includes array/block.

Link to reproduction
https://github.com/SimYunSup/example-list/tree/payload/bug-postgres-nested-id
Describe the Bug
Duplicated ID error when duplicate Array/Block that includes Array/Block.

Reported Bug

[16:56:40] ERROR (payload): TypeError: Cannot read properties of undefined (reading 'nested_blocks_just_text_pkey')
    at upsertRow (D:\GithubProject\example-list\node_modules\.pnpm\@payloadcms+db-postgres@0.8.4_@types+react@18.3.3_payload@2.18.3_@swc+helpers@0.5.11_@types+r_utjmzo3j7ceboprn5scvypgwvm\node_modules\@payloadcms\db-postgres\src\upsertRow\index.ts:318:57)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Object.updateOne (D:\GithubProject\example-list\node_modules\.pnpm\@payloadcms+db-postgres@0.8.4_@types+react@18.3.3_payload@2.18.3_@swc+helpers@0.5.11_@types+r_utjmzo3j7ceboprn5scvypgwvm\node_modules\@payloadcms\db-postgres\src\update.ts:44:18)
    at async updateByID (D:\GithubProject\example-list\node_modules\.pnpm\payload@2.18.3_@swc+helpers@0.5.11_@types+react@18.3.3_esbuild@0.19.12_typescript@5.4.5_webpa_w2wwwoljy4lt2mm3kbswof65oi\node_modules\payload\src\collections\operations\updateByID.ts:269:16)
    at async updateByIDHandler (D:\GithubProject\example-list\node_modules\.pnpm\payload@2.18.3_@swc+helpers@0.5.11_@types+react@18.3.3_esbuild@0.19.12_typescript@5.4.5_webpa_w2wwwoljy4lt2mm3kbswof65oi\node_modules\payload\src\collections\requestHandlers\updateByID.ts:43:17)

To Reproduce

Create a Nested collection item.
Fill in the fields in one of the order listed below.
Block in Block
- Create nested-block in blocks
- Create just-text in nested
- Fill title(optional)
Array in Block
- Create nested-array in blocks
- Create item in nested
- Fill title(optional)
Block in Array
- Create item in nestedArrayBlocks
- Create just-text in nested
- Fill title(optional)
Block in Block
- Create item in nestedArrayArray
- Create item in nested
- Fill title(optional)
Duplicates any top-level Block or Array.
When you submit, you should get an error.

I think It must replace nested ID.
And I think Same in 3.0.0-beta.39 because DUPLICATE_ROW has same logic.
Payload Version
2.18.3
Adapters and Plugins
<EMAIL_ADDRESS><EMAIL_ADDRESS>

Seeing the same issue with 3.0.0-beta.36 - but have been seeing this for a while.

Same error on payload 2.23.1, db-postgres 0.8.5. I can trigger it for any document that has a nested array field, regardless of whether it was duplicated or not. In my case it also seems related to draft/publish, I observed this strange behavior:

Save a draft change to any document that has a nested array (succeeds)
Publish that change (fails w/ OP's error)
Delete the nested array items, save draft change (succeeds)
Publish that change (succeeds.... and the deleted array items have been magically restored 🤯 )
Repeat and see the same results, even if you delete the entire parent field in step 3 rather than just the nested array

This is causing issues in prod for me so hoping to follow up with more debugging and a repro later tonight 👍

Hey @SimYunSup @siobahnschuck @wkentdag - we just merged the fix for this on v3 and have a PR for it on v2 here.
Thanks for your patience and we'll get all of this merged and released asap!


C3 pie chart label position

I need to know how to configure position of pie chart labels in customised way that is outside the pie chart

Currently there's no option for that purposes.
You need positioning text label manually like this way.
onrendered: function() {
	d3.selectAll(".c3-chart-arc text").each(function(v) {
		var label = d3.select(this);
		var pos = label.attr("transform").match(/-?\d+(\.\d+)?/g);

		// pos[0] is x, pos[1] is y. Do some position changes and update value
		label.attr("transform", "translate("+ pos[0] +","+ pos[1] +")");
	});
});

And don't forget change label text color updating fill property value as your necessity.
.c3-chart-arc text {
    fill: red;
    font-size: 13px;
}

@Jae Thanks a lot... One more thing on hovering the tooltip is going inside
the div which should be in front of div...other types of charts except pie
in c3 handle properly the position of tooltip
On 3 Mar 2017 7:30 a.m., "Jae Sung Park"<EMAIL_ADDRESS>wrote:

Currently there's no option for that purposes.
You need positioning text label manually like this way.
onrendered: function() {
d3.selectAll(".c3-chart-arc text").each(function(v) {
var label = d3.select(this);
var pos = label.attr("transform").match(/-?\d+(.\d+)?/g);
  // pos[0] is x, pos[1] is y. Do some position changes and update value
  label.attr("transform", "translate("+ pos[0] +","+ pos[1] +")");

});
});
And don't forget change label text color updating fill property value as
your necessity.
.c3-chart-arc text {
fill: red;
font-size: 13px;
}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/c3js/c3/issues/1982#issuecomment-283843058, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AY7PlFeX5Tkfy86SecdxU27mn_ZReMXaks5rh3RRgaJpZM4MQvMj
.

@gballampalli, set tooltip.position callback to handle the position of tooltip.

http://c3js.org/reference.html#tooltip-position

        tooltip: {
            position: function (data, width, height, element) {
                // in this case, tooltip will appear x,30 and y:20
                return {
                    top: 20, left: 30
                };
            }
        }

Can we make this a native option in C3?

Alguna solución para C3?

Any feedback about making this native to C3?

The top and bottom labels are cutoff , do you have any solutions for this?

Do you know if BillboardJs is working with Rotativa? I need to export these charts to a pdf, C3.js is the only library that I found to work (I ve tried chart.js / chartist.js/ and d3.js)

I ve just tried and is not showing up in pdf :(

@StanicaAndi89 -- I do have a similar requirement as yours..I f you are using C3 JS or D3 JS Please Can you share me an example to display the labels outside the doughnut chart..
Thanks in Advance


allow max-content as default scrollWidth

Describe your changes
set default scrollwidth to max-content
Screenshots [Optional]
Issue ticket number and link
Closes #
Checklist before requesting a review

[ ] I have performed a self-review of my code
[ ] I have added tests
[ ] I have added a changeset pnpm changeset add
[ ] I have added example usage in the kitchen sink app

allow max-content as default scrollWidth


Log error class

Hi, very good work! i love this
I'm using the last HA version 2022.02.5 and see this in logs:
Logger: homeassistant.helpers.entity
Source: helpers/entity.py:580
First occurred: 11:21:40 (5 occurrences)
Last logged: 11:21:41
Entity sensor.aquariumled_current_profile (<class 'custom_components.juwel_helialux.sensor.JuwelSensor'>) implements device_state_attributes. Please report it to the custom component author.
Entity sensor.aquariumled_white (<class 'custom_components.juwel_helialux.sensor.JuwelSensor'>) implements device_state_attributes. Please report it to the custom component author.
Entity sensor.aquariumled_blue (<class 'custom_components.juwel_helialux.sensor.JuwelSensor'>) implements device_state_attributes. Please report it to the custom component author.
Entity sensor.aquariumled_red (<class 'custom_components.juwel_helialux.sensor.JuwelSensor'>) implements device_state_attributes. Please report it to the custom component author.
Entity sensor.aquariumled_green (<class 'custom_components.juwel_helialux.sensor.JuwelSensor'>) implements device_state_attributes. Please report it to the custom component author.

The latest version should have fixed that :)


cadl-ranch-spec, add test case for json-merge-patch

Add test cases for json-merge-patch.
I'm not using Azure core template ResourceCreateOrUpdate currently because I would like to make the case reusable for both azure and non-azure. Template underline set the content type to merge-patch+json, and it is transparent to emitters as we only get the content type regardless it's set by template or by user. Let me know if you feel it's necessary to add another test file under Azure folder.
Test serialization for json merge patch on below cases:

request body required and optional.
property is Record(map): this is the same case as loadtesting, loadtesting is using map property to do json merge patch.  https://github.com/Azure/azure-rest-api-specs/blob/main/specification/loadtestservice/LoadTestService/models.tsp#L418-L431
property is string: this is the same case as content safety.  https://github.com/Azure/azure-rest-api-specs/blob/main/specification/cognitiveservices/ContentSafety/models.tsp#L136-L149
property is inner model
property is array
property is int
property is float

Cadl Ranch Contribution Checklist:

[x] I have written a scenario spec
[x] I have meaningful @scenario names. Someone can look at the list of scenarios and understand what I'm covering.
[x] I have written a mock API
[x] I have used @scenarioDocs for extra scenario description and to tell people how to pass my mock api check.

Another existing tsp source (already have SDK generated -- every createOrUpdate there is a PATCH)
op https://github.com/Azure/azure-rest-api-specs/blob/main/specification/communication/Communication.JobRouter/routes.tsp#L104
resource https://github.com/Azure/azure-rest-api-specs/blob/main/specification/communication/Communication.JobRouter/models.tsp#L457


Add raw field to the transaction

Resolves #1481

Codecov Report
Base: 40.18% // Head: 39.99% // Decreases project coverage by -0.18% :warning:

Coverage data is based on head (ae3ad92) compared to base (57c6bbd).
Patch coverage: 18.95% of modified lines in pull request are covered.

 Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Mark c_str() methods of nb::str and nb::bytes as const.

Could you update the documentation as well? (api_core.rst)

Could you update the documentation as well? (api_core.rst)

Done.

Thanks!


Add ability to skip CREATE TABLE statement

Sometimes it makes sense to just import data without creating a new table.

Gregory, sorry it's taken me so long to get back to this pull request. I think this is a solid feature and I went ahead and implemented it, though I changed the switch name to --no-create to be consistent with other options and added some additional option validation. I've added you to AUTHORS file as well.
Best,
Chris

Wow, awesome, thank you.


[FEATURE] Allow passing related objects as id for creating objects

Currently, json has to be written like this to create objects:
{
  "name": "Account",
  "user": {
    "id": "26132E11-6D13-4983-9FAE-71B705439BD8"
  }
}

It would be nice to only have to do this:
{
  "name": "Account",
  "user": "26132E11-6D13-4983-9FAE-71B705439BD8"
}

This should be possible with DTOs.

@PSchmiedmayer is the use case for this only when doing manual JSON requests? As far as I know, when sending requests through a client, everything goes through Codable, so the user is not really exposed to this syntax.

This is currently a limitation of Fluent, because it expects an actual object as part of a Model, not just an id reference.


feat: pass parameter overrides as prefixed environment variables

Issue #, if available: -
Description of changes:
I have added a feature that allows users to use action's prefixed environment variables as parameter overrides. The prefix of environment key is removed before passing it to cloudformation.
This approach is based on Heroku Deploy action and addresses couple of issues including:

a lot of parameters to override
sensitive inputs are not stored on disk/in the file
values of parameters passed to action using this way are automatically escaped - no need for additional escape, especially if using Github vars/secrets - whatever github accepts will be passed as parameters.

I have added feature, tests and documentation snippet. Feature should be backward compatible as it's only activated if user adds an envs-prefix-for-parameter-overrides parameter with a desired prefix.
I hope that you will find this feature useful and include it in the main release.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Actually solves some of the already existing issues too:

#47
#86 (kind of I would say - envs are defined in YAML format, so... would work?)

@kddejong can I have a little bit of your attention here? 😄

Force pushed all the commits to rebase and update to the changes in tests.

@kddejong Hey, any chances for you to look into it?


the difference of map between val and test-dev

in mmdet, MAP is reported on coco_2017_val ,usually in most detection paper, MAP is reported on test-dev,  any relationship between the MAP on val and test-dev? what's more, how can we get the performance on test-dev?

They are different split of COCO. You can test the model on test-dev and submit the results to the official test server to get the performance.

They are different split of COCO. You can test the model on test-dev and submit the results to the official test server to get the performance.

how can i find the official test server to get the performance?


Add shard option as plugin

Takes an object of methods and sets the createRest property of the database.

Resolved with https://github.com/ClickerMonkey/neurosync/commit/d884946494765a21b18aa012d0c667207cf885dd


chore: dynamic plugins update for 1.1...

What does this PR do?
chore: dynamic plugins update for 1.1 (RHIDP-1475)
Signed-off-by: Nick Boldt<EMAIL_ADDRESS>Screenshot/screencast of this PR
N/A
What issues does this PR fix or reference?
N/A (or see commit message above for issue number)
How to test this PR?
N/A
PR Checklist
As the author of this Pull Request I made sure that:

[x] The Eclipse Contributor Agreement is valid
[x] Code produced is complete
[x] Code builds without errors
[ ] Tests are covering the bugfix
[x] The repository devfile is up to date and works, if one exists
[x] Sections What issues does this PR fix or reference and How to test this PR completed
[x] Relevant user documentation updated
[x] Relevant contributing documentation updated
[x] CI/CD changes implemented, documented and communicated

Reviewers
Reviewers, please comment how you tested the PR when approving it.

@nickboldt This looks good to me. Before we merge the PR should we wait for @kadel to reply regarding the missing Required Variables values referred to in https://issues.redhat.com/browse/RHIDP-1475

cc @Gerry-Forde @kadel

@nickboldt It looks like we just need to commit those couple of updates for the required variables and then we're good to merge this. Is there anything else required?

It looks like we just need to commit those couple of updates for the required variables and then we're good to merge this. Is there anything else required?

I was waiting for @davidfestal and @kadel to confirm that there were no other env vars we needed to list, but I'll set this to automerge and we can iterate on Monday if there's more to be done.

@nickboldt

The table of dynamic plugins looks good to me.
WRT the updated Release Notes content, I understand that the tables of plugins have been removed from the RNs for RHDH 1.1 - @shipsing can you confirm, please?

@nickboldt

The table of dynamic plugins looks good to me.
WRT the updated Release Notes content, I understand that the tables of plugins have been removed from the RNs for RHDH 1.1 - @shipsing can you confirm, please?

Hi @Gerry-Forde @nickboldt, Yes, I have removed the table of plugins  from RN to avoid redundnat work. We have all the plugin details in the admin guide and we have provided a reference to that in our 1.1 RN.
See this section: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-79/rel-notes-rhdh/#_plugins-available-in-red-hat-developer-hub


Add resize node function for azure driver

Add resize node function for azure driver
Description
Background
https://github.com/apache/libcloud/issues/1964
To start with we have def ex_change_node_size(self, node, new_size) function in [https://github.com/apache/libcloud/blob/trunk/libcloud/compute/drivers/ec2.py] which supports instance type change for AWS.
We need similar functionality for Azure cloud as well where we could change the vmSize for Azure cloud. This could be done by adding node_resize function at (https://github.com/apache/libcloud/blob/trunk/libcloud/compute/drivers/azure_arm.py )
Implementation

Added ex_resize_node to change the azure vm instance type.
Added equivalent test test_resize_node to test ex_resize_node

Status

done, ready for review

Checklist (tick everything that applies)

[x] Code linting (required, can be done after the PR checks)
[ ] Documentation
[x] Tests
[ ] ICLA (required for bigger changes)

@Kami Can u take a look into this?

We're currently processing your upload.  This comment will be updated when the results are available.

Merged into trunk. Thanks for the contribution.