ietf-netconf-server running library can not be open

hi.
I had upgraded netopeer2 version 0.7-r2, libyang (v1.0-r3), libnetconf2 (v0.12-r2) and sysrepo (v0.7.8).   ietf-netconf-server running library   can not be open,  but others can(such as ietf-interfaces):
[root@localhost ~]# sysrepocfg -d running -e vi -f xml ietf-netconf-server
Cannot operate on the running datastore for 'ietf-netconf-server' as there are no active subscriptions for it.
Canceling the operation.
[root@localhost ~]#

sysrepo debug info as follow:
[DBG] File /etc/sysrepo/data/ietf-netconf-server.persist (fd = 26) has been unlocked
[DBG] Returning info from 'ietf-netconf-server' persist file: module disabled, 0 subtrees enabled in running, 6 features enabled.
[DBG] Enabling feature 'listen' in module 'ietf-netconf-server'
[DBG] Enabling feature 'ssh-listen' in module 'ietf-netconf-server'
[DBG] Enabling feature 'tls-listen' in module 'ietf-netconf-server'
[DBG] Enabling feature 'call-home' in module 'ietf-netconf-server'
[DBG] Enabling feature 'ssh-call-home' in module 'ietf-netconf-server'
[DBG] Enabling feature 'tls-call-home' in module 'ietf-netconf-server'
[DBG] File /etc/sysrepo/data/ietf-netconf-server.persist has been locked

sysrepoctl -l
[root@localhost ~]# sysrepoctl -l
Sysrepo schema directory: /etc/sysrepo/yang/
Sysrepo data directory:   /etc/sysrepo/data/
(Do not alter contents of these directories manually)

Module Name                      | Revision   | Conformance | Data Owner          | Permissions | Submodules                    | Enabled Features
-----------------------------------------------------------------------------------------------------------------------------------------------
ietf-netconf-notifications       | 2012-02-06 | Installed   | root:root           | 600         |                               |
ietf-netconf                     | 2011-06-01 | Installed   | root:root           | 600         |                               | writable-running candidate rollback-on-error validate startup xpath
ietf-netconf-acm                 | 2018-02-14 | Installed   | root:root           | 600         |                               |
nc-notifications                 | 2008-07-14 | Installed   | root:root           | 600         |                               |
notifications                    | 2008-07-14 | Installed   | root:root           | 600         |                               |
iana-if-type                     | 2014-05-08 | Installed   |                     |             |                               |
ietf-interfaces                  | 2014-05-08 | Installed   | root:root           | 600         |                               | if-mib
ietf-ip                          | 2014-06-16 | Installed   |                     |             |                               |
ietf-x509-cert-to-name           | 2014-12-10 | Installed   |                     |             |                               |
ietf-keystore                    | 2016-10-31 | Installed   | root:root           | 600         |                               |
ietf-yang-types                  | 2013-07-15 | Installed   |                     |             |                               |
ietf-access-control-list         | 2018-10-01 | Implemented | root:root           | 600         |                               | match-on-eth match-on-ipv4 match-on-tcp match-on-udp match-on-icmp eth ipv4 mixed-eth-ipv4 interface-attachment interface-stats acl-aggregate-stats
ietf-packet-fields               | 2018-10-01 | Imported    |                     |             |                               |
ietf-ethertypes                  | 2018-10-01 | Imported    |                     |             |                               |
ietf-netconf-with-defaults       | 2011-06-01 | Installed   |                     |             |                               |
ietf-netconf-monitoring          | 2010-10-04 | Installed   | root:root           | 600         |                               |
ietf-yang-library                | 2018-01-17 | Installed   | root:root           | 600         |                               |
ietf-datastores                  | 2017-08-17 | Imported    |                     |             |                               |
ietf-netconf-server              | 2016-11-02 | Installed   | root:root           | 600         |                               | listen ssh-listen tls-listen call-home ssh-call-home tls-call-home
ietf-ssh-server                  | 2016-11-02 | Imported    |                     |             |                               |
ietf-tls-server                  | 2016-11-02 | Imported    |                     |             |                               |

[root@localhost ~]#

Sincerely,
nick

Hi Nick,
that is because you do not have netopeer2-server running, which subscribes to these data. The same command for ietf-interfaces will not work either unless you have a subscription for that module data.
Regards,
Michal

Hi，Michal：
I print out the netopeer startup debug information:
[root@localhost ~]# /usr/bin/netopeer2-server -d -v 2
[INF]: Connected to daemon Sysrepo Engine at socket=/var/run/sysrepod.sock
[INF]: Netopeer2 connected to sysrepod.
[INF]: Plugin "/usr/lib64/libyang/extensions/metadata.so" successfully loaded.
[INF]: Plugin "/usr/lib64/libyang/extensions/nacm.so" successfully loaded.
[INF]: Plugin "/usr/lib64/libyang/extensions/yangdata.so" successfully loaded.
[INF]: Plugin "/usr/lib64/libyang/user_types/user_inet_types.so" successfully loaded.
[INF]: Plugin "/usr/lib64/libyang/user_types/user_yang_types.so" successfully loaded.
[INF]: Reading module "ietf-yang-metadata".
[INF]: Module "ietf-yang-metadata@2016-08-05" successfully parsed as implemented.
[INF]: Reading module "yang".
[INF]: Resolving "yang" unresolved schema nodes and their constraints...
[INF]: All "yang" schema nodes and constraints resolved.
[INF]: Module "yang@2017-02-20" successfully parsed as implemented.
[INF]: Reading module "ietf-inet-types".
[INF]: Resolving derived type "union" failed, it will be attempted later.
[INF]: Resolving derived type "union" failed, it will be attempted later.
[INF]: Resolving derived type "union" failed, it will be attempted later.
[INF]: Resolving derived type "union" failed, it will be attempted later.
[INF]: Resolving "ietf-inet-types" unresolved schema nodes and their constraints...
[INF]: All "ietf-inet-types" schema nodes and constraints resolved.
[INF]: Module "ietf-inet-types@2013-07-15" successfully parsed as implemented.
[INF]: Reading module "ietf-yang-types".
[INF]: Module "ietf-yang-types@2013-07-15" successfully parsed as implemented.
[INF]: Reading module "ietf-datastores".
[INF]: Module "ietf-datastores@2017-08-17" successfully parsed as implemented.
[INF]: Reading module "ietf-yang-library".
[INF]: Module "ietf-yang-library@2018-01-17" successfully parsed as implemented.
[INF]: Loading schema "ietf-netconf-notifications@2012-02-06" from sysrepo.
[INF]: Reading module "ietf-netconf-notifications".
[INF]: Reading module "ietf-netconf".
[INF]: Reading module "ietf-netconf-acm".
[INF]: Module "ietf-netconf-acm@2018-02-14" successfully parsed as imported.
[INF]: Module "ietf-netconf@2011-06-01" successfully parsed as imported.
[INF]: Resolving "ietf-netconf-notifications" unresolved schema nodes and their constraints...
[INF]: All "ietf-netconf-notifications" schema nodes and constraints resolved.
[INF]: Module "ietf-netconf-notifications@2012-02-06" successfully parsed as implemented.
[INF]: Loading schema "ietf-netconf@2011-06-01" from sysrepo.
[INF]: Module ietf-netconf@2011-06-01 already present in context.
[INF]: Module "ietf-netconf@2011-06-01" now implemented.
[INF]: Loading schema "ietf-netconf-acm@2018-02-14" from sysrepo.
[INF]: Module ietf-netconf-acm@2018-02-14 already present in context.
[INF]: Module "ietf-netconf-acm@2018-02-14" now implemented.
[INF]: Loading schema "nc-notifications@2008-07-14" from sysrepo.
[INF]: Reading module "nc-notifications".
[INF]: Reading module "notifications".
[INF]: Module "notifications@2008-07-14" successfully parsed as imported.
[INF]: Module "nc-notifications@2008-07-14" successfully parsed as implemented.
[INF]: Loading schema "notifications@2008-07-14" from sysrepo.
[INF]: Module notifications@2008-07-14 already present in context.
[INF]: Module "notifications@2008-07-14" now implemented.
[INF]: Loading schema "iana-if-type@2014-05-08" from sysrepo.
[INF]: Reading module "iana-if-type".
[INF]: Reading module "ietf-interfaces".
[INF]: Module "ietf-interfaces@2014-05-08" successfully parsed as imported.
[INF]: Module "iana-if-type@2014-05-08" successfully parsed as implemented.
[INF]: Loading schema "ietf-interfaces@2014-05-08" from sysrepo.
[INF]: Module ietf-interfaces@2014-05-08 already present in context.
[INF]: Module "ietf-interfaces@2014-05-08" now implemented.
[INF]: Loading schema "ietf-ip@2014-06-16" from sysrepo.
[INF]: Reading module "ietf-ip".
[INF]: Module "ietf-ip@2014-06-16" successfully parsed as implemented.
[INF]: Loading schema "ietf-x509-cert-to-name@2014-12-10" from sysrepo.
[INF]: Reading module "ietf-x509-cert-to-name".
[INF]: Module "ietf-x509-cert-to-name@2014-12-10" successfully parsed as implemented.
[INF]: Loading schema "ietf-keystore@2016-10-31" from sysrepo.
[INF]: Reading module "ietf-keystore".
[INF]: Module "ietf-keystore@2016-10-31" successfully parsed as implemented.
[INF]: Loading schema "ietf-yang-types@2013-07-15" from sysrepo.
[INF]: Module ietf-yang-types@2013-07-15 already present in context.
[INF]: Module "ietf-yang-types@2013-07-15" now implemented.
[INF]: Loading schema "v3po@2018-12-27" from sysrepo.
[INF]: Reading module "v3po".
[INF]: Reading module "iana-if-type".
[INF]: Module "iana-if-type@2014-05-08" already in context.
[INF]: Module "iana-if-type@2014-05-08" successfully parsed as implemented.
[INF]: Reading module "yang-ext".
[INF]: Module "yang-ext@2013-07-09" successfully parsed as imported.
[INF]: Reading module "vpp-fib-table-management".
[INF]: Module "vpp-fib-table-management@2018-05-21" successfully parsed as imported.
[INF]: Resolving uses "bridge-based-attributes" failed, it will be attempted later.
[INF]: Resolving uses "bridge-based-attributes" failed, it will be attempted later.
[INF]: Resolving uses "l2-config-attributes" failed, it will be attempted later.
[INF]: Resolving augment target "/ietf-interfaces:interfaces/ietf-interfaces:interface" failed, it will be attempted later.
[INF]: Resolving uses "l2-state-attributes" failed, it will be attempted later.
[INF]: Resolving augment target "/ietf-interfaces:interfaces-state/ietf-interfaces:interface" failed, it will be attempted later.
[INF]: Resolving "v3po" unresolved schema nodes and their constraints...
[WRN]: Identityref "action" comparison with identity "l2-fib-filter" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
[WRN]: Previous warning generated by XPath subexpression[3] "action != 'l2-fib-filter'".
[WRN]: Identityref "action" comparison with identity "l2-fib-forward" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
[WRN]: Previous warning generated by XPath subexpression[3] "action = 'l2-fib-forward'".
[WRN]: Identityref "action" comparison with identity "l2-fib-filter" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
[WRN]: Previous warning generated by XPath subexpression[3] "action != 'l2-fib-filter'".
[WRN]: Identityref "action" comparison with identity "l2-fib-forward" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
[WRN]: Previous warning generated by XPath subexpression[3] "action = 'l2-fib-forward'".
[WRN]: Schema node "ietf-interfaces:ipv4" not found (bridged-virtual-interface = 'true' or (not (../ietf-interfaces:ipv4) with context node "/ietf-interfaces:interfaces/interface/v3po:l2".
[WRN]: Schema node "ietf-interfaces:address" not found (bridged-virtual-interface = 'true' or (not (../ietf-interfaces:ipv4[ietf-interfaces:enabled = 'true']/ietf-interfaces:address) with context node "/ietf-interfaces:interfaces/interface/v3po:l2".
[WRN]: Schema node "ietf-interfaces:ip" not found (bridged-virtual-interface = 'true' or (not (../ietf-interfaces:ipv4[ietf-interfaces:enabled = 'true']/ietf-interfaces:address/ietf-interfaces:ip) with context node "/ietf-interfaces:interfaces/interface/v3po:l2".
[WRN]: Schema node "ietf-interfaces:ipv6" not found (bridged-virtual-interface = 'true' or (not (../ietf-interfaces:ipv4[ietf-interfaces:enabled = 'true']/ietf-interfaces:address/ietf-interfaces:ip) and not (../ietf-interfaces:ipv6) with context node "/ietf-interfaces:interfaces/interface/v3po:l2".
[WRN]: Schema node "ietf-interfaces:address" not found (bridged-virtual-interface = 'true' or (not (../ietf-interfaces:ipv4[ietf-interfaces:enabled = 'true']/ietf-interfaces:address/ietf-interfaces:ip) and not (../ietf-interfaces:ipv6[ietf-interfaces:enabled = 'true']/ietf-interfaces:address) with context node "/ietf-interfaces:interfaces/interface/v3po:l2".
[WRN]: Schema node "ietf-interfaces:ip" not found (bridged-virtual-interface = 'true' or (not (../ietf-interfaces:ipv4[ietf-interfaces:enabled = 'true']/ietf-interfaces:address/ietf-interfaces:ip) and not (../ietf-interfaces:ipv6[ietf-interfaces:enabled = 'true']/ietf-interfaces:address/ietf-interfaces:ip) with context node "/ietf-interfaces:interfaces/interface/v3po:l2".
[WRN]: Identityref "type" comparison with identity "gre-tunnel" without prefix, consider adding a prefix or best using "derived-from(-or-self)()" functions.
[WRN]: Previous warning generated by XPath subexpression[3] "ietf-interfaces:type = 'gre-tunnel'".
[WRN]: Failed to resolve identityref "gre-tunnel". (/ietf-interfaces:type)
[WRN]: Previous warning generated by XPath subexpression[3] "ietf-interfaces:type = 'gre-tunnel'".
[WRN]: Schema node "ietf-interfaces:ipv4" not found (bridged-virtual-interface = 'true' or (not (../ietf-interfaces:ipv4) with context node "/ietf-interfaces:interfaces-state/interface/v3po:l2".
[WRN]: Schema node "ietf-interfaces:address" not found (bridged-virtual-interface = 'true' or (not (../ietf-interfaces:ipv4[ietf-interfaces:enabled = 'true']/ietf-interfaces:address) with context node "/ietf-interfaces:interfaces-state/interface/v3po:l2".
[WRN]: Schema node "ietf-interfaces:ip" not found (bridged-virtual-interface = 'true' or (not (../ietf-interfaces:ipv4[ietf-interfaces:enabled = 'true']/ietf-interfaces:address/ietf-interfaces:ip) with context node "/ietf-interfaces:interfaces-state/interface/v3po:l2".
[WRN]: Schema node "ietf-interfaces:ipv6" not found (bridged-virtual-interface = 'true' or (not (../ietf-interfaces:ipv4[ietf-interfaces:enabled = 'true']/ietf-interfaces:address/ietf-interfaces:ip) and not (../ietf-interfaces:ipv6) with context node "/ietf-interfaces:interfaces-state/interface/v3po:l2".
[WRN]: Schema node "ietf-interfaces:address" not found (bridged-virtual-interface = 'true' or (not (../ietf-interfaces:ipv4[ietf-interfaces:enabled = 'true']/ietf-interfaces:address/ietf-interfaces:ip) and not (../ietf-interfaces:ipv6[ietf-interfaces:enabled = 'true']/ietf-interfaces:address) with context node "/ietf-interfaces:interfaces-state/interface/v3po:l2".
[WRN]: Schema node "ietf-interfaces:ip" not found (bridged-virtual-interface = 'true' or (not (../ietf-interfaces:ipv4[ietf-interfaces:enabled = 'true']/ietf-interfaces:address/ietf-interfaces:ip) and not (../ietf-interfaces:ipv6[ietf-interfaces:enabled = 'true']/ietf-interfaces:address/ietf-interfaces:ip) with context node "/ietf-interfaces:interfaces-state/interface/v3po:l2".
[INF]: All "v3po" schema nodes and constraints resolved.
[INF]: Module "v3po@2018-12-27" successfully parsed as implemented.
[INF]: Loading schema "yang-ext@2013-07-09" from sysrepo.
[INF]: Module yang-ext@2013-07-09 already present in context.
[INF]: Loading schema "vpp-fib-table-management@2018-05-21" from sysrepo.
[INF]: Module vpp-fib-table-management@2018-05-21 already present in context.
[INF]: Loading schema "vpp-nat@2018-05-10" from sysrepo.
[INF]: Reading module "vpp-nat".
[INF]: Reading module "ietf-nat".
[INF]: Resolving "ietf-nat" unresolved schema nodes and their constraints...
[INF]: All "ietf-nat" schema nodes and constraints resolved.
[INF]: Module "ietf-nat@2018-06-28" successfully parsed as imported.
[INF]: Resolving "vpp-nat" unresolved schema nodes and their constraints...
[INF]: All "vpp-nat" schema nodes and constraints resolved.
[INF]: Module "vpp-nat@2018-05-10" successfully parsed as implemented.
[INF]: Loading schema "ietf-nat@2018-06-28" from sysrepo.
[INF]: Module ietf-nat@2018-06-28 already present in context.
[INF]: Loading schema "interface-nat@2017-08-16" from sysrepo.
[INF]: Reading module "interface-nat".
[INF]: Module "interface-nat@2017-08-16" successfully parsed as implemented.
[INF]: Loading schema "ietf-inet-types@2013-07-15" from sysrepo.
[INF]: Module ietf-inet-types@2013-07-15 already present in context.
[INF]: Module "ietf-inet-types@2013-07-15" now implemented.
[INF]: Loading schema "policer@2017-03-15" from sysrepo.
[INF]: Reading module "policer".
[INF]: Resolving "policer" unresolved schema nodes and their constraints...
[WRN]: Schema node "meter-action-mark-dscp" not found (../meter-action-type = meter-action-mark-dscp) with context node "/policer:policers/policer/conform-action/dscp".
[WRN]: Schema node "meter-action-mark-dscp" not found (../meter-action-type = meter-action-mark-dscp) with context node "/policer:policers/policer/exceed-action/dscp".
[WRN]: Schema node "meter-action-mark-dscp" not found (../meter-action-type = meter-action-mark-dscp) with context node "/policer:policers/policer/violate-action/dscp".
[WRN]: Schema node "meter-action-mark-dscp" not found (../meter-action-type = meter-action-mark-dscp) with context node "/policer:policers-state/policer/conform-action/dscp".
[WRN]: Schema node "meter-action-mark-dscp" not found (../meter-action-type = meter-action-mark-dscp) with context node "/policer:policers-state/policer/exceed-action/dscp".
[WRN]: Schema node "meter-action-mark-dscp" not found (../meter-action-type = meter-action-mark-dscp) with context node "/policer:policers-state/policer/violate-action/dscp".
[INF]: All "policer" schema nodes and constraints resolved.
[INF]: Module "policer@2017-03-15" successfully parsed as implemented.
[INF]: Loading schema "vpp-classifier@2017-03-27" from sysrepo.
[INF]: Reading module "vpp-classifier".
[INF]: Reading module "policer".
[INF]: Module "policer@2017-03-15" already in context.
[INF]: Module "policer@2017-03-15" successfully parsed as implemented.
[INF]: Module "vpp-classifier@2017-03-27" successfully parsed as implemented.
[INF]: Loading schema "vpp-routing-types@2018-04-06" from sysrepo.
[INF]: Reading module "vpp-routing-types".
[INF]: Module "vpp-routing-types@2018-04-06" successfully parsed as implemented.
[INF]: Loading schema "hc2vpp-ietf-routing@2018-03-13" from sysrepo.
[INF]: Reading module "hc2vpp-ietf-routing".
[INF]: Reading module "vpp-routing-types".
[INF]: Module "vpp-routing-types@2018-04-06" already in context.
[INF]: Module "vpp-routing-types@2018-04-06" successfully parsed as implemented.
[INF]: Resolving "hc2vpp-ietf-routing" unresolved schema nodes and their constraints...
[INF]: All "hc2vpp-ietf-routing" schema nodes and constraints resolved.
[INF]: Module "hc2vpp-ietf-routing@2018-03-13" successfully parsed as implemented.
[INF]: Loading schema "hc2vpp-ietf-ipv4-unicast-routing@2018-03-13" from sysrepo.
[INF]: Reading module "hc2vpp-ietf-ipv4-unicast-routing".
[INF]: Reading module "hc2vpp-ietf-routing".
[INF]: Module "hc2vpp-ietf-routing@2018-03-13" already in context.
[INF]: Module "hc2vpp-ietf-routing@2018-03-13" successfully parsed as implemented.
[INF]: Resolving "hc2vpp-ietf-ipv4-unicast-routing" unresolved schema nodes and their constraints...
[INF]: All "hc2vpp-ietf-ipv4-unicast-routing" schema nodes and constraints resolved.
[INF]: Module "hc2vpp-ietf-ipv4-unicast-routing@2018-03-13" successfully parsed as implemented.
[INF]: Loading schema "vpp-routing@2018-03-19" from sysrepo.
[INF]: Reading module "vpp-routing".
[INF]: Reading module "vpp-classifier".
[INF]: Module "vpp-classifier@2017-03-27" already in context.
[INF]: Module "vpp-classifier@2017-03-27" successfully parsed as implemented.
[INF]: Resolving "vpp-routing" unresolved schema nodes and their constraints...
[INF]: All "vpp-routing" schema nodes and constraints resolved.
[INF]: Module "vpp-routing@2018-03-19" successfully parsed as implemented.
[INF]: Loading schema "interface-l2-classify@2019-01-23" from sysrepo.
[INF]: Reading module "interface-l2-classify".
[INF]: Resolving "interface-l2-classify" unresolved schema nodes and their constraints...
[INF]: All "interface-l2-classify" schema nodes and constraints resolved.
[INF]: Module "interface-l2-classify@2019-01-23" successfully parsed as implemented.
[INF]: Loading schema "interface-policer@2017-03-15" from sysrepo.
[INF]: Reading module "interface-policer".
[INF]: Resolving "interface-policer" unresolved schema nodes and their constraints...
[INF]: All "interface-policer" schema nodes and constraints resolved.
[INF]: Module "interface-policer@2017-03-15" successfully parsed as implemented.
[INF]: Loading schema "ietf-dhcp@2018-10-11" from sysrepo.
[INF]: Reading module "ietf-dhcp".
[INF]: Module "ietf-dhcp@2018-10-11" successfully parsed as implemented.
[INF]: Loading schema "vpp-statistics@2019-02-18" from sysrepo.
[INF]: Reading module "vpp-statistics".
[INF]: Module "vpp-statistics@2019-02-18" successfully parsed as implemented.
[INF]: Loading schema "vpp-ipsec@2018-12-13" from sysrepo.
[INF]: Reading module "vpp-ipsec".
[INF]: Reading module "hc2vpp-ietf-ipsec".
[INF]: Resolving "hc2vpp-ietf-ipsec" unresolved schema nodes and their constraints...
[INF]: All "hc2vpp-ietf-ipsec" schema nodes and constraints resolved.
[INF]: Module "hc2vpp-ietf-ipsec@2018-12-14" successfully parsed as imported.
[INF]: Resolving "vpp-ipsec" unresolved schema nodes and their constraints...
[INF]: All "vpp-ipsec" schema nodes and constraints resolved.
[INF]: Module "vpp-ipsec@2018-12-13" successfully parsed as implemented.
[INF]: Loading schema "hc2vpp-ietf-ipsec@2018-12-14" from sysrepo.
[INF]: Module hc2vpp-ietf-ipsec@2018-12-14 already present in context.
[INF]: Loading schema "dot1q-types@2015-06-26" from sysrepo.
[INF]: Reading module "dot1q-types".
[INF]: Module "dot1q-types@2015-06-26" successfully parsed as implemented.
[INF]: Loading schema "vpp-vlan@2018-03-19" from sysrepo.
[INF]: Reading module "vpp-vlan".
[INF]: Reading module "dot1q-types".
[INF]: Module "dot1q-types@2015-06-26" already in context.
[INF]: Module "dot1q-types@2015-06-26" successfully parsed as implemented.
[INF]: Reading module "v3po".
[INF]: Module "v3po@2018-12-27" already in context.
[INF]: Module "v3po@2018-12-27" successfully parsed as implemented.
[INF]: Resolving uses "tag-rewrite" failed, it will be attempted later.
[INF]: Resolving uses "rewrite-attributes" failed, it will be attempted later.
[INF]: Resolving uses "rewrite-attributes" failed, it will be attempted later.
[INF]: Resolving uses "sub-interface-l2-config-attributes" failed, it will be attempted later.
[INF]: Resolving uses "sub-interface-l2-state-attributes" failed, it will be attempted later.
[INF]: Resolving "vpp-vlan" unresolved schema nodes and their constraints...
[WRN]: Schema node "ietf-interfaces:name" not found (../../ietf-interfaces:name) with context node "/ietf-interfaces:interfaces/interface/vpp-vlan:sub-interfaces/vpp-vlan:sub-interface/vpp-vlan:l2/vpp-vlan:interconnection/vpp-vlan:xconnect-based/vpp-vlan:xconnect-outgoing-interface".
[WRN]: Schema node "ietf-interfaces:name" not found (../../ietf-interfaces:name) with context node "/ietf-interfaces:interfaces-state/interface/vpp-vlan:sub-interfaces/vpp-vlan:sub-interface/vpp-vlan:l2/vpp-vlan:interconnection/vpp-vlan:xconnect-based/vpp-vlan:xconnect-outgoing-interface".
[INF]: All "vpp-vlan" schema nodes and constraints resolved.
[INF]: Module "vpp-vlan@2018-03-19" successfully parsed as implemented.
[INF]: Loading schema "terastream-wireless@2017-08-08" from sysrepo.
[INF]: Reading module "terastream-wireless".
[INF]: Resolving "terastream-wireless" unresolved schema nodes and their constraints...
[INF]: All "terastream-wireless" schema nodes and constraints resolved.
[INF]: Module "terastream-wireless@2017-08-08" successfully parsed as implemented.
[INF]: Loading schema "device-info@2019-03-06" from sysrepo.
[INF]: Reading module "device-info".
[INF]: Module "device-info@2019-03-06" successfully parsed as implemented.
[INF]: Loading schema "voip@2019-03-11" from sysrepo.
[INF]: Reading module "voip".
[INF]: Module "voip@2019-03-11" successfully parsed as implemented.
[INF]: Loading schema "iana-crypt-hash@2014-08-06" from sysrepo.
[INF]: Reading module "iana-crypt-hash".
[INF]: Module "iana-crypt-hash@2014-08-06" successfully parsed as implemented.
[INF]: Loading schema "ietf-system@2014-08-06" from sysrepo.
[INF]: Reading module "ietf-system".
[INF]: Reading module "iana-crypt-hash".
[INF]: Module "iana-crypt-hash@2014-08-06" already in context.
[INF]: Module "iana-crypt-hash@2014-08-06" successfully parsed as implemented.
[INF]: Resolving "ietf-system" unresolved schema nodes and their constraints...
[INF]: All "ietf-system" schema nodes and constraints resolved.
[INF]: Module "ietf-system@2014-08-06" successfully parsed as implemented.
[INF]: Loading schema "vpp-acl@2018-10-22" from sysrepo.
[INF]: Reading module "vpp-acl".
[INF]: Reading module "ietf-access-control-list".
[INF]: Reading module "ietf-packet-fields".
[INF]: Reading module "ietf-ethertypes".
[INF]: Module "ietf-ethertypes@2018-10-01" successfully parsed as imported.
[INF]: Module "ietf-packet-fields@2018-10-01" successfully parsed as imported.
[INF]: Resolving "ietf-access-control-list" unresolved schema nodes and their constraints...
[INF]: All "ietf-access-control-list" schema nodes and constraints resolved.
[INF]: Module "ietf-access-control-list@2018-10-01" successfully parsed as imported.
[INF]: Resolving "vpp-acl" unresolved schema nodes and their constraints...
[INF]: All "vpp-acl" schema nodes and constraints resolved.
[INF]: Module "vpp-acl@2018-10-22" successfully parsed as implemented.
[INF]: Loading schema "ietf-access-control-list@2018-10-01" from sysrepo.
[INF]: Module ietf-access-control-list@2018-10-01 already present in context.
[INF]: Loading schema "ietf-packet-fields@2018-10-01" from sysrepo.
[INF]: Module ietf-packet-fields@2018-10-01 already present in context.
[INF]: Loading schema "ietf-ethertypes@2018-10-01" from sysrepo.
[INF]: Module ietf-ethertypes@2018-10-01 already present in context.
[INF]: Loading schema "ietf-netconf-with-defaults@2011-06-01" from sysrepo.
[INF]: Reading module "ietf-netconf-with-defaults".
[INF]: Module "ietf-netconf-with-defaults@2011-06-01" successfully parsed as implemented.
[INF]: Loading schema "ietf-netconf-monitoring@2010-10-04" from sysrepo.
[INF]: Reading module "ietf-netconf-monitoring".
[INF]: Module "ietf-netconf-monitoring@2010-10-04" successfully parsed as implemented.
[INF]: Loading schema "ietf-yang-library@2018-01-17" from sysrepo.
[INF]: Module ietf-yang-library@2018-01-17 already present in context.
[INF]: Loading schema "ietf-datastores@2017-08-17" from sysrepo.
[INF]: Module ietf-datastores@2017-08-17 already present in context.
[INF]: Loading schema "ietf-netconf-server@2016-11-02" from sysrepo.
[INF]: Reading module "ietf-netconf-server".
[INF]: Reading module "ietf-x509-cert-to-name".
[INF]: Module "ietf-x509-cert-to-name@2014-12-10" already in context.
[INF]: Module "ietf-x509-cert-to-name@2014-12-10" successfully parsed as implemented.
[INF]: Reading module "ietf-ssh-server".
[INF]: Reading module "ietf-keystore".
[INF]: Module "ietf-keystore@2016-10-31" already in context.
[INF]: Module "ietf-keystore@2016-10-31" successfully parsed as implemented.
[INF]: Module "ietf-ssh-server@2016-11-02" successfully parsed as imported.
[INF]: Reading module "ietf-tls-server".
[INF]: Module "ietf-tls-server@2016-11-02" successfully parsed as imported.
[INF]: Resolving "ietf-netconf-server" unresolved schema nodes and their constraints...
[INF]: All "ietf-netconf-server" schema nodes and constraints resolved.
[INF]: Module "ietf-netconf-server@2016-11-02" successfully parsed as implemented.
[INF]: Loading schema "ietf-ssh-server@2016-11-02" from sysrepo.
[INF]: Module ietf-ssh-server@2016-11-02 already present in context.
[INF]: Loading schema "ietf-tls-server@2016-11-02" from sysrepo.
[INF]: Module ietf-tls-server@2016-11-02 already present in context.
[WRN]: Sysrepo does not have the "ietf-netconf-server" module or keystored keys dir unknown, using default NETCONF server options.
[INF]: Listening on <IP_ADDRESS>:830 for SSH connections.

and I use command ‘sysrepocfg -d startup -e vi -f xml ietf-netconf-server’，show result as follow:
<netconf-server xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-server">
  <listen>
    <endpoint>
      <name>test_ssh_listen_endpt</name>
      <ssh>
        <address>::</address>
        <port>830</port>
        <host-keys>
          <host-key>
            <name>test_ssh_listen_key</name>
            <public-key>ssh_host_rsa_key</public-key>
          </host-key>
        </host-keys>
      </ssh>
    </endpoint>
  </listen>
  <call-home>
    <netconf-client>
      <name>netopeer2-cli</name>
      <ssh>
        <endpoints>
          <endpoint>
            <name>netopeer2-cli-ep</name>
            <address><IP_ADDRESS></address>
            <port>6666</port>
          </endpoint>
        </endpoints>
        <host-keys>
          <host-key>
            <name>ssh_host_rsa_key</name>
            <public-key>ssh_host_rsa_key</public-key>
          </host-key>
        </host-keys>
      </ssh>
      <connection-type>
        <persistent/>
      </connection-type>
    </netconf-client>
  </call-home>
</netconf-server>

and show the '/etc/sysrepo/data/ ' file as follow:
[root@localhost ~]# ll /etc/sysrepo/data/  |   grep ietf-netconf-server
-rw-------. 1 root root  184 Jul 19 17:26 ietf-netconf-server.persist
-rw-------. 1 root root    0 Jul 19 17:26 ietf-netconf-server.running
-rw-------. 1 root root    0 Jul 19 17:26 ietf-netconf-server.running.lock
-rw-------. 1 root root  373 Jul 19 19:26 ietf-netconf-server.startup
-rw-------. 1 root root    0 Jul 19 17:26 ietf-netconf-server.startup.lock

Sincerely,
Nick


Remove /page/ prefix from pages adamgreenough#14

Hi @Zarosch, sorry I missed this! Happy to merge these changes if you'd still like? Really appreciate the contribution. Keep meaning to come back to this. :)

@adamgreenough Sorry for closing the pull request. I thought the project was no longer active. Obviously this is not the case, I have opened the pull request again.  ;)


pkg/git: fix ssh credentials detection 🦀

Changes
To detect ssh cerdentials (and validate the git clone url with
cerdentials), we do check if there is a $HOME/.ssh folder. With
disable-home-env-overwrite we do not overwrite $HOME env anymore,
and thus we have no control where $HOME is and wether the image
ships it with a .ssh or not.
This fixes it by looking at a path we control no matter how the
controller is configured : pipeline.CredsDir (/tekton/creds).
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>(cherry picked from commit b35bec85551597c18544a2cf1e8999fbf55b8af3)
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>/cc @sbwsg @bobcatfish @afrittoli
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[x] Commit messages follow commit message best practices
[x] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
fix ssh credential wrong detection in git-init

/approve
/lgtm

/kind bug


Add Nigeria validation

Update validator to validate Nigerian phone numbers.

@verygreenboi see the new version.Now use libphonenumber to check phone.


Completely fails to decompile functions using RAII

I have now tested both the 32bit and the 64bit precompiled versions on Windows 10 and it doesnt seem to work at all for functions using RAII. I have tested simple programs compiled with Visual Studio 12 and 14 in debug and release ,with and without pdbs and with and without the -k switch. It seems to be able to decompile most of the library functions which have been linked into the program. It also decompiles some of the user supplied functions.
But every function using RAII for C++ objects decompiles to basically this:
abort();
// UNREACHABLE
Atleast it seems like RAII is the cause. Since getters and simple calculations not involving any objects are decompiled just fine. Here are some examples from 2 programs i decompiled with pdb information.
Edit:
Might also be related to the security cookie check combined with constant propagation.
Edit 2:
The cookie seems the more likely culprit as all the function that check their stack cookie only call abort in the decompiled output and there is not a single call to the check function even though it has been decompiled.

Hi. Could you please provide the input binaries (+ PDBs when applicable) and decompile.sh parameters that you used for decompilation so we can verify this?

Sure here are both programs with their pdbs. for the Gw2MC.exe the code is also completely in the pastebin if you want to compile it differently. Commandlines used:
decompile.sh Gw2MC.exe
decompile.sh -p Gw2MC.pdb Gw2MC.exe
decompile.sh -p Gw2MC.pdb -k Gw2MC.exe

Same for the update-server. The result was always basically identically aside from the function names ofcourse.

For reference, I do have security cookie checks in the decompiler output, so it's not only that. So far all functions declared "unreachable" have been using security cookies however.
I tried running the decompiler without optimizations, while keeping unreachable functions and disabling removal of statically linked functions. None of these options solved the issue unfortunately.

Further investigation: the issue happens during bin2llvmir stage already. Tweaking the parameters revealed that the secure cookie isn't the culprit, it's rather this instruction which appears to cause trouble:
mov eax, dword ptr fs:[0]

This is related to exception handling, so it would appear that any function using try..catch would be affected.

Further playing with parameters revealed that the issue is triggered by multiple optimizations: -jump-threading, -instcombine, -simplifycfg. Editing retdec-config.py and removing these parameters from BIN2LLVMIR_LLVM_PASSES_ONLY and BIN2LLVMIR_PARAMS (note: some are listed there multiple times) makes sure the produced .ll file still has all the function bodies.

I could trace the issue back to this check. So LLVM considers fs:[0] to be a null pointer, so reading from it would raise an exception. That's why it marks this code as unreachable. Commenting out this check again results in the correct .ll file being generated, even with unchanged retdec-config.py.

On a deeper level, the issue appears to be this comment. While Capstone marks this particular instruction with "segment override," RetDec will ignore the flag and translate the operand into a plain pointer. So LLVM treating it like a null pointer is correct - trash in, trash out.

Comment related to this: https://github.com/avast-tl/retdec/pull/391#issuecomment-423171852.

Code from #391 was merged to master. This should hopefully fix the issue here. Unfortunately the link to sample you gave us is no longer working, and I probably deleted the file from my hard drive - I can't find it anywhere. If you are willing to send it to me again (sorry :-D) I can add it to our regression tests to make sure this is (and stays) fixed.


Add resultmanager class

The resultmanager class has been added so far.

Enhancement of the class will be donw through new issues


Select start location/orientation

It would be nice to be able to select the start location and orientation.

Added as a teleport command, will be in next release


Shrinking a tab enough to hide some content renders it inaccessible until it's extended again

When a tab is shrunk enough to obscure any of the internal content, the tab content should become a scrollable area.
I'm thinking about ditching the custom tab widget approach and replace it with our own egui_dock::Tab with an API similar to one of egui::Window.

Closed by #6


Break up customization points to follow modern standard practice

I'm referring to P1841.

That paper's blocked now.


How to create a plain javascript object

Summary
I'd like to create rust binding for something like this:
export namespace Math {
    type Vector3 = { "x": number, "y": number, "z": number };
}

So I've add binding like this:
use wasm_bindgen::prelude::*;

#[wasm_bindgen]
extern "C" {
    #[wasm_bindgen(extends = js_sys::Object, js_namespace = Math, js_name = Vector3, typescript_type = "Math.Vector3")]
    #[derive(Debug, Clone, PartialEq, Eq)]
    pub type JsVector3;

    #[wasm_bindgen(constructor, js_class = Vector3)]
    pub fn new() -> JsVector3;

    #[wasm_bindgen(method, getter, js_class = Vector3, js_name = x)]
    pub fn x(this: &JsVector3) -> f64;
    #[wasm_bindgen(method, setter, js_class = Vector3, js_name = x)]
    pub fn set_x(this: &JsVector3, value: f64);

    // ...
}

The problem is I don't know how to create a new JsVector3 object like {x: 1.0, y: 2.0, z: 3.0} in javascript.
I've tried let vec = JsVector3::new() in rust but it won't run as Vector3 is not an actual class in javascript.
Additional Details
I've found this post but I don't know how to cast JsObject to JsVector either.

The snippet above is for js-import (extern "C"), hence using a javascript class from Rust. In this case Vector3 should be declared in javascript. Maybe export from Rust to javascript rust-export is appropriate instead.


HOP-13

This PR stays work-in-progress for a while.
For the time being, this PR is to show the difference between the master branch and the web branch.

Recreated as #199 .

I pushed the "web" branch to https://github.com/project-hop/hop again. Now that issues specific to Hop Web are tracked on Jira, it'd be better to track the patch to these issues as GitHub PRs.

Close for now. Will work on my fork.


Azcopy sync between two storage accounts in different tenants fails with CannotVerifyCopySource

Which version of the AzCopy was used?
10.22.2
Note: The version is visible when running AzCopy without any argument
Which platform are you using? (ex: Windows, Mac, Linux)
Linux (WSL)
What command did you run?
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
azcopy sync "https://sourceaccount.file.core.windows.net/sourcefileshare/sourcefolder/" 'https://destinationaccount.blob.core.windows.net/destinationcontainer/destinationpath/?sas-token' --recursive --cap-mbps 100 --from-to FileBlob
What problem was encountered?
output:
Job 080829fd-19ac-5548-7897-54f0650a0667 Summary
Files Scanned at Source: 97
Files Scanned at Destination: 0
Elapsed Time (Minutes): 0.8003
Number of Copy Transfers for Files: 97
Number of Copy Transfers for Folder Properties: 0
Total Number Of Copy Transfers: 97
Number of Copy Transfers Completed: 0
Number of Copy Transfers Failed: 97
Number of Deletions at Destination: 0
Total Number of Bytes Transferred: 0
Total Number of Bytes Enumerated: 11398388
Final Job Status: Failed
Checking the StorageBlobLogs on the destination storage account every copy failed with status code 400 and statusTest "CannotVerifyCopySource"
Both source and destination storage accounts are on DIFFERENT azure tenants, however they both have public access enabled.
I have not tried using SAS authentication for the source account yet as I don't have permission to generate SAS tokens for that account.
How can we reproduce the problem in the simplest way?
Two storage accounts in different tenants. Setup azure files folder in source and a blob storage container in destination with hierarchical namespaces. Use az cli to log into source tenant and then run azcopy sync from source to destination using a sas token for destination
Have you found a mitigation/solution?
Not yet - I'm looking into getting permission to create sas tokens on source account as I believe that might help, but I'd prefer not to require this.

If they are in two different tenants, can you verify vnet peering is done properly if they both fall in two different vnets.
Copy source verification generally fails when destination account is not able to authenticate properly to source account.

If they are in two different tenants, can you verify vnet peering is done properly if they both fall in two different vnets. Copy source verification generally fails when destination account is not able to authenticate properly to source account.

I don't think either storage account is in a vnet

Can not verify copy source generally points that your source account is not accessible from your destination account. This is more of a storage account setup issue and not really an azcopy issue. Kindly check with respective teams on what you might be missing. Mostly we have seen its either a vnet or a firewall related issue where accounts are not accessible in such cases.

Closing this as there is no update. Feel free to reopen once the required information is available.


Profiler usage has problem

🐛 Bug
When I run the PyTorch lightning example code profiler_example.py, the ProfilerStep# and Optimizer.step overlaps, which is not expected behavior.

The current unexpected behavior:

Expected behavior

Additional context
The cause is calling Optimizer.step passing closure and call profiler.step() inside the closure.
Calling optimizer passing closure: https://github.com/PyTorchLightning/pytorch-lightning/blob/4af8eff0a13309b2e030c423db91156b1e869fac/pytorch_lightning/loops/batch/training_batch_loop.py#L397
Calling profiler.step() inside the closure: https://github.com/PyTorchLightning/pytorch-lightning/blob/4af8eff0a13309b2e030c423db91156b1e869fac/pytorch_lightning/profiler/pytorch.py#L447
The calling stack of profiler.step() is below. From this, we can see the "training_step_and_forward" closure is called inside Optimizer.step(), and profiler.step() is called inside the "training_step_and_forward" closure, which leads to intersection.

Fixed here: https://github.com/PyTorchLightning/pytorch-lightning/pull/8224


first commit of the astra vector store code

Summary

Fixes
Depends on
Test plan

Screenshots

Checklist

[ ] My code follows the code style of this project and passes make format.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] My change has adequate unit test coverage.

The code seems to be adding a new file called astra.py in the vectorstores directory.
The file contains a class called AstraVectorStore which initializes some variables and sets up the Astra database connection.
There is a method called embed_documents which takes a list of Document objects and embeds them using the OpenAIEmbeddings model.
The embedded documents are then upserted into the Astra database.
There are some commented out code snippets that seem to be placeholders for future implementation.

Overall, the code looks good and seems to be implementing the embedding and upsert functionality for the Astra database. However, there are some commented out code snippets that need to be removed or implemented.

@Briah need help with this?


Add audit logging for tracing user activities

Issue submitter TODO list

[X] I've searched for an already existing issues here
[X] I'm running a supported version of the application which is listed here and the feature is not present there

Is your proposal related to a problem?
Managing  Kafka Cluster using Kafka UI
Describe the feature you're interested in
We are using Kafka UI for some months. We would like to trace the activity of Kafka UI users in a separate log file ( example: audit.log), or even save it in a specific Kafka topic ( internal topic with long default retention (3 months? )
In this file, we could like to see all the actions made by a user with some details ( date, user, actions ...): create a topic, edit topic configuration, view data in a topic, delete messages from a topic, update schemas, and so on.
Describe alternatives you've considered
No response
Version you're running
0.7.0
Additional context
No response

duplicate of #2998


[Feature-3223]Click DAG connection to add label function

Hi,
Please change the pr title to [Feature-3223][ui] Click DAG connection to add label function, Thx a lot~
If you have any question or suggestion, please put foward.


Results/Output

Hi,
I am running a psexec command to install software on servers without Powershell. If I do a crtl-U after the job has finished, I can see the results have been captured... for instance:

PsExec v1.98 - Execute processes remotely
Copyright (C) 2001-2010 Mark Russinovich
Sysinternals - www.sysinternals.com
How can I get this posted in the Results section of the WebCommander page? Psexec is tricky to get output from, but I see it is here and would like to use it in the Results section.
Thanks for any assistance!
Jen

Please try the command below
$output = cmd /s /c "psexec.exe \$ComputerName command to run 2>&1"

ok, I have found an issue.
When I run the psexec command from WebCommander(in domain1) with my domain1 account to a domain1 server, the Event log says I am loggging in as domain1\id. This is correct.
When I run the psexec command from WebCommander(in domain1) with my domain1 account on a domain2 server, the Event log says I am loggging in as anonymous.
When I run either of the above from Powershell ISE they work perfectly, regardless of the domain.
Are there some other settings in IIS, or PHP that would fix this issue?
Thanks for your help!
Jen

Could you run the psexec command from CMD (not Powershell ISE) with your domain1 account on a domain2 server?

yes, I ran the same command an it worked perfectly. In both cases I am running the command prompt and ISE at an elevated prompt.

Ok, please add the following line in your powershell script and run it from webcommander again
writeCustomizedMsg [Environment]::UserName
It shows the account whose credential is being used by webcommander. If it's different from the one you use to run the command from CMD and Powershell ISE, you need to configure IIS to run webcommander as that user.
You could refer to the installation guide about how to configure IIS.
https://github.com/vmware/webcommander/raw/master/www/images/wiki/IIS_Add_Website.png

ok, that was my problem the entire time, even trying to create a scheduled task. When using psexec, the software is actually on a network share, so administrator won't have access. I will go back to the scheduled task where I can control the user to run it.
Thanks


[FR] : Open terminal at right side instead of bottom

When a new terminal is opened currently it is opening at the bottom of the editor. Suppose

)
but it will be helpful if it is opened at the right side instead of bottom. I'm sorry I can't provide any additional image because I don't have a right-side panel based photo.

You can try x-terminal, which allows you to move the terminal to any panel or dock.

@UziTech thanks ... actually I was looking for it ... for both cased I have seen that both was developed by bus-stop and so I am closing this [FR]. again  thank you.


half and double with tests

Tests depend on https://github.com/torch/cutorch/pull/431
We need to figure out the mechanism of detecting TRUE_HALF mode, currently it will always fall back to pseudo.

@szagoruyko : does it look solid on your end? When do you expect this all to get merged?

@borisfom I think as soon as https://github.com/torch/cutorch/pull/431 gets merged this can go too, there are not many changes to cudnn itself, mostly tests

I tested this PR in https://github.com/szagoruyko/wide-residual-networks/tree/fp16 on CIFAR-10. It works well and fp16 networks are very close in accuracy to fp32. There is one problem with batch normalization which requires fp32 parameters even in fp16 mode, which makes it a little bit difficult to use getParameters on a networks with mixed fp16 and fp32 parameters.
There are three workarounds:

have separate containers for fp32 and fp16 and call getParameters with optim on each one. This could be hidden in torchnet eg. tnt.MultitypeOptimEngine. Downside is it won't work with nn.DataParallelTable.
have all parameters in fp32 and copy some of them to fp16 on forward and backward.
Optim.lua from facebook

Went in! Fingers crossed.

Running on Tesla, I am getting same exact errors as I had in my clone.
Plus (may be new, maybe just random), I am getting those errors every 3-5th time I run the test:
37/38 VolumetricConvolution_backward_single ............................. [ERROR]
THCudaCheck FAIL file=/tmp/buildd/torch7-0.9.99/extra/cutorch/lib/THC/generic/THCStorage.c line=147 error=4 : unspecified launch failure
Segmentation fault (core dumped)
That may ring some bells.

I don't seem to be able to repro the crash anymore - could be fixed.


unable to retrieve child resources EAI_AGAIN

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.24.1
Regression From
No response
Architecture
i86
Storage Explorer Build Number
20220510.2
Platform
Windows
OS Version
Windows 11
Bug Description
Unable to list the blob containers in storage explorer while connecting with account access key 1.
Steps to Reproduce

Launch storage explorer
Attached container by name and using access key2 from azure management portal
Expanded attached storage blob containers to get list of containers

Actual Experience
Unable to retrieve child resources.
Details:
{
"name": "FetchError",
"message": "request to https://saphostingerlabwestus2di.blob.core.cloudapi.de/?comp=list&include=metadata failed, reason: getaddrinfo EAI_AGAIN saphostingerlabwestus2di.blob.core.cloudapi.de",
"stack": "FetchError: request to https://saphostingerlabwestus2di.blob.core.cloudapi.de/?comp=list&include=metadata failed, reason: getaddrinfo EAI_AGAIN saphostingerlabwestus2di.blob.core.cloudapi.de\n    at ClientRequest. (C:\Program Files (x86)\Microsoft Azure Storage Explorer\resources\app\node_modules\node-fetch\lib\index.js:1491:11)\n    at ClientRequest.emit (node:events:390:28)\n    at TLSSocket.socketErrorListener (node:_http_client:447:9)\n    at TLSSocket.emit (node:events:390:28)\n    at emitErrorNT (node:internal/streams/destroy:157:8)\n    at emitErrorCloseNT (node:internal/streams/destroy:122:3)\n    at processTicksAndRejections (node:internal/process/task_queues:83:21)",
"type": "system",
"errno": "EAI_AGAIN",
"code": "EAI_AGAIN"
}
Expected Experience
List the containers
Additional Context
While the expand error is common, I did not see information related to getaddrinfo EAI_AGAIN. Troubleshooting guide about AD issue does not appear to apply.

@daviburg  can you give using system proxy setting a try? You can read more about it here: https://docs.microsoft.com/en-us/azure/storage/common/storage-explorer-network#use-system-proxy-preview

Also, @daviburg, what Azure cloud is your data in. Is it in the old Azure Germany/Blackforest cloud? Asking because I see the .de on your endpoints. As an FYI, that Azure cloud has been shutdown....

Updated storage explorer to the new current latest. Getting a better error message now:
Unable to retrieve child resources.
Details:
{
  "name": "Error",
  "message": "net::ERR_NAME_NOT_RESOLVED",
  "stack": "Error: net::ERR_NAME_NOT_RESOLVED\n    at SimpleURLLoaderWrapper.<anonymous> (node:electron/js2c/browser_init:105:7047)\n    at SimpleURLLoaderWrapper.emit (node:events:390:28)"
}

Which is consistent with the unexpected endpoint suffix from a defunct cloud.
I removed the old connection and re-added it. This time it picks the right cloud. I wonder if the portal was temporarily pointing to Blackforest a month ago? Maybe internal outage tracking system for storage service will have some record of such incident.
(Ok to close).


Check import signature in module resolution

A discrepancy between the import and export declarations would go undetected. Make sure this is caught.

Codecov Report

Merging #94 into master will decrease coverage by 0.1%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master      #94      +/-   ##
==========================================
- Coverage   67.91%   67.81%   -0.11%
==========================================
  Files          33       33
  Lines        3338     3343       +5
==========================================
  Hits         2267     2267
- Misses        820      825       +5
  Partials      251      251

Impacted Files
Coverage Δ

wasm/imports.go
19.1% <0%> (-1.14%)
:arrow_down:

Continue to review full report at Codecov.

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

LGTM.
could you add a test though?

Ok, I think that I will also improve the type checking and write some unit tests anyway; will get to it in the afternoon.

LGTM.
could you add a test though?

we needed a semaphore ;) Yes, I'm planning to do that.

@sbinet I have added unit tests and have improved the checks. It seems to me that codecov doesn't track the file with the tests, although I could very well be wrong.

(modulo the last go-fmt error, "of course" :P)


Karma tests

I have decided to add karma because it allows us to split the compiler tests from the riot tests giving us a better code coverage 34% -> 76.92%

:ship: it!

Great job again!
I merged this from the command line so closing this PR manually.
Getting some errors with make test – need to check them out.

Right now 3 tests fail on server and all passes on browser.

I've fixed the issue. Now we have two kind of tests:
1 node compiler tests running simply with mocha https://github.com/muut/riotjs/blob/dev/test/runner.js#L9 (no need for the DOM)
2 browser tests: running on phantomjs ( or just opening with any browser runner.html ) https://github.com/muut/riotjs/blob/dev/test/karma.conf.js#L15-L18

Awesome. Thank you!


graphql errors

Noticing some errors.
[16:13:06.790Z] ERROR @sample-stack-server: 2 errors were thrown when executing your GraphQL queries.
    Error: 2 errors were thrown when executing your GraphQL queries.
        at /Users/veeramarni/Documents/fullstack-pro/node_modules/react-apollo/server.js:86:19
        at <anonymous>
        at process._tickCallback (internal/process/next_tick.js:188:7)
[HPM] Error occurred while trying to proxy request / from localhost:3000 to http://localhost:3010 (ECONNRESET) (https://nodejs.org/api/errors.html#errors_common_system_errors)

Those errors occur when the server not reachable to graphql server when doing SSR. So make sure the GRAPHQL_SERVER is up and accessible from the CLIENT_SERVER.


Remove always enabled events, allowing toggling.

It makes more sense to allow toggling the eventsEnabled property to enable/disable interaction; for example having game UI visible underneath a pause screen UI and being able to tell the game screen text to ignore interaction temporarily. Currently the only way to do so was to remove the click listener you were using and re-add it after.
Changelog;

Removed always enabled events
Added eventsEnabled toggle attribute

Closing since this repo is now retired.


Add 3rd party provider fees information to the BTC wallet

Add information about fees that will be applied on incoming (and outgoing?) BTC transfer.

Please let me review the text before this feature is added, thanks!

Disabled permanently


Update notifu to 1.6.1

Using the WindowsBalloon on Windows 10 with all the updates, display a extra message in the ballon from Notifu.
1.6.1 of Notifu fixes it.
(https://www.paralint.com/projects/notifu/changelog.html)
Current, 1.6

With Latest 1.6.1

Confirming this

It works :)

When will the NPM package be updated?
https://www.npmjs.com/package/node-notifier

Sorry.
It has been done now
+<EMAIL_ADDRESS>

Thank you!


Binding can cause Catastrophic Failures

Describe the bug
When binding in ListView to a List it works most of the time, however, if the ItemSource is repeatedly changed, it causes catastrophic failures at the app level.
Errors can include kernalBase.dll, comBase, memory allocation errors, and failure to set AnimatedIconSource (which is never set)
This happens in SDK v1.0.0 but does not happen in Reunion 0.8 or WPF
Steps to reproduce the bug
In my code this happens without the reproduction steps below,  due to the complexity of my app and to show the error in as simple way as possible, I wrote a really simple click here and watch the error happen.
Create a new Desktop WinUI app
In XAML - Add the XAML and Code below (very simple) - then run and click the "Click Me" quickly, after about 5 seconds it will error.
<Grid>
		<Grid.RowDefinitions>
			<RowDefinition/>
			<RowDefinition Height="Auto"/>
		</Grid.RowDefinitions>

		<ListView	x:Name="UxListView" SelectionMode="None" IsTabStop="False"  >
			<ListView.Resources>
				<ResourceDictionary Source="ms-appx:///Microsoft.UI.Xaml/DensityStyles/Compact.xaml" />
			</ListView.Resources>

			<ListView.ItemTemplate>
				<DataTemplate>
					<CheckBox	IsChecked="{Binding IsChecked, Mode=TwoWay}" Content="{Binding Text, Mode=OneWay}"		VerticalAlignment="Center" Checked="CheckBox_Checked" Unchecked="CheckBox_Checked" />
				</DataTemplate>
			</ListView.ItemTemplate>

		</ListView>

		<Button Grid.Row="1" x:Name="myButton" Click="myButton_Click" HorizontalAlignment="Center" Margin="16" >Click Me</Button>

	</Grid>

In Code behind, Add this
public sealed partial class MainWindow : Window {
		public MainWindow() {
			this.InitializeComponent();
		}

		public MyModel stringModel = new();

		private void myButton_Click(object sender, RoutedEventArgs e) {
			UxListView.ItemsSource = null;
			UxListView.ItemsSource = stringModel.StringList;
		}

		private void CheckBox_Checked(object sender, RoutedEventArgs e) {	}
	}

	public class MyModel {

		public MyModel() {

			for (var i = 1; i < 100000; i++) {
				var newStringItem = new StringItem();

				newStringItem.IsChecked = true;
				newStringItem.Text = "This is some text to bind to the checkbox " + i.ToString() + " " + GuidHelper.CreateNewGuid();

				StringList.Add(newStringItem);
			}

		}

		public List<StringItem> StringList { get; set; } = new();

	}

	public class StringItem {
		public bool IsChecked { get; set; }
		public string Text { get; set; }
	}

Expected behavior
Setting the ItemSource property should reset the view.
Screenshots

NuGet package version
WinUI 3 - Windows App SDK 1.0 (If you're seeing your issue in older previews of WinUI 3, please try this release)
Windows app type

[ ] UWP
[X] Win32

Device form factor
Desktop
Windows version
No response
Additional context
Windows 11 Pro retail

@RBrid @codendone and @MikeHillberg FYI about this 1.0 regression.

Any update on this? This looks so similar to this issue: #8604
I have also experienced this.
Currently Checkboxes in ListViews should definitely be avoided.

Tried the repro with WinAppSDK 1.4 and it works as expected. We did fix an issue with Checkbox where creating too many of them  would lead to a crash (checkbox uses lottie animations under the covers).


Query caching issues (?)

Following scenario:
var User = use('App/Model/User')

 User.where('email','=',request.param('email')).first().then(function(user){
      response.json(user);
       console.log("GETTING ONE USER VIA It's email");
       console.log(JSON.stringify(user));
});

User.all().then(function(result) {
      console.log("GETTING ALL USERS ? -> NOPE returns same result as in first query");
      console.log(JSON.stringify(result));
})

User.all().then(function(result) {
  console.log("GETTING ALL USERS AGAIN -> returns a list but only item is the user we got initially");
  console.log(JSON.stringify(result));
  User.all().then(function(result) {
    console.log("GETTING ALL USERS YET AGAIN -> this really gives me all users");
    console.log(JSON.stringify(result));

  })

})

This is all happening in a controller action, however as my console.logs describe there is an issue of getting a fresh query started. What am I doing wrong ?

What version are you on?

"adonis-lucid": "^2.0.5",

Yes there is a issue with this. I would recommend upgrading to 3.0 it will be released this weekend.

Ta

Will this be fixed in that version though ?

Yes it has been fixed. Some other issues also reported same.

Closing


what is difference between RRDB_ESRGAN_x4 and RRDB_PSNR_x4

As far as I understood, RRDB_ESRGAN_x4 is the current ESRGAN model, and RRDB_PSNR_x4 is a standart SRGAN one that gives smoother results (can be found here https://github.com/xinntao/BasicSR/blob/master/metrics/calculate_PSNR_SSIM.py).

No, PSNR is the model trained only using content loss to initialize the filters. You use the PSNR model as a pre-trained model to train the ESRGAN model with feature loss and adversarial loss, so it converges faster to the global minima. Read the paper, it's explained there.


fix(updates): update editor commons to fix passing of error metadata

Fixes #741

Messages

:book:

:white_check_mark: All tests are passing
Nice one! All 101 tests are passing.

:book:

:floppy_disk: Here's the built vsix for this change.

  Generated by :no_entry_sign: dangerJS against 78e77c02f98a670ee06bb84a8910a73aa93e324e


Upgrade to sqlite 3.39.2 to resolve CVE-2022-35737

The current vendored version of sqlite, 3.39.1, has a vulnerability CVE-2022-35737 in its custom printf functions, described in detail in https://blog.trailofbits.com/2022/10/25/sqlite-vulnerability-july-2022-library-api/ .
better-sqlite3 currently uses the vulnerable sqlite3_mprintf function in some of its error handling code.
Version 3.39.2 resolves this vulnerability.

Thanks for the heads-up. See https://github.com/WiseLibs/better-sqlite3/pull/896


chore: bdd-nh-1587385097 to 0.0.1

chore: Promote bdd-nh-1587385097 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


suggestion to use v prefix for tags

Hi! Based on this approach https://github.com/golang/go/wiki/Modules#how-can-i-track-tool-dependencies-for-a-module to track tool dependencies for a module, as an example, I found a slight inconvenience when working with fzf, because fzf uses a different style to name tags. For go mod, it's recommended by this https://go.dev/ref/mod#versions

Each version starts with the letter v, followed by a semantic version

As a result, I have a pseudo-version like this instead of v0.32.0. It's challenging to understand which version is under the hood, actually. Is it possible to change the naming convention for tags?

Interesting. Any reason you don't use brew to get the latest stable version of fzf?


Sample code for player

Hello. Could you please provide a sample code for initializing the player and playing the actual movie.
Thank you.

Did you happen to check the demo repo https://github.com/emadalam/appletv-demo which has the player example?
You can create a generic Play page that plays any url passed to it. Something like here, https://github.com/emadalam/appletv-demo/blob/master/web/app/pages/play/index.js could be created. Note, though the urls are hardcoded in the above example, you can receive those as options passed to the page https://github.com/emadalam/appletv-demo/blob/master/web/app/pages/movie-details/template.hbs#L17.
Does this work for you? Or you need more examples?

@emadalam sorry for not following up. Yes, I found what I was looking for. Thank you very much


Added a localized strings class for the app

Description
I've added the localized strings class for all the major strings of the app. Through this class, we can replace the hardcoded strings and it would be easier to support other localizations in different languages through this file in the future.
Fixes #376
Replace issue_no with the issue number which is fixed in this PR
Have you read the Contributing Guidelines on Pull Requests?

[x] Yes
[ ] No

Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works.

@avinashkranjan please review this PR


Stack Overflow reputation badge shows "invalid parameters"

Experiencing an issue with...

[X] shields.io
[ ] My own instance
[ ] badge-maker NPM package

:beetle: Description
It was working fine yesterday, but the Stack Overflow badge now just shows "invalid parameters." On the shields.io generator, all the presets seem to be invalid too.

:link: Link to the badge
<img src="https://img.shields.io/stackexchange/stackoverflow/r/14351818?color=F47F24&label=Stack%20Overflow">

Live URL result
Screenshot

Thanks for reaching out but going to close as a duplicate of #5414, perhaps stemming from #3591


Real Time Translation

Planning to implement something like this:
Sender: Hi how are you today?
Recipient: (From Sender) 안녕하세요, 오늘 어떻게 지내고 있나요?
¿cómo estás hoy?
Привіт, як справи сьогодні?
Recipient: 잘 지내고 있어요 감사합니다!
Sender: (From Recipient) I'm doing well thank you!
¡Lo estoy haciendo bien, gracias!
у мене все добре дякую!
Where ChatGPT sits between two users. The two users will have a language preference and ChatGPT will also relay the message translated based on their preference.

Might have to be a slightly different implementation however.


Convert float16 data to 2 byte array

PR for #3
With the changes so far, the file is written without errors. However, the file is unreadable by Clickhouse. Other parquet readers indicate that logical_type: FLOAT16 is missing from the metadata.

Code works and the output is readable with Python parquet-tools. Other tools, including Clickhouse 24.11, fail to read the file correctly.


Update Single Returns Entity Even if It Does Not Exist

Describe the bug
Consider a table where you just have a single entity

id
name

1
github

If you run an update query, the return value could be slightly deceiving
val site = Website(id = 2, name = "something")
val result = db.runQuery { QueryDsl.update(Meta.website).single(site) }

Expected behavior
I would expect result to be null because the update did not actually update any records
Actual behavior
result is not null
Steps to reproduce the problem
The only way I have found so far to detect this is to include returning()
db.runQuery {
        QueryDsl.update(table).single(e).returning()
      }

This works, but seems wasteful if you have a large-sized row. If you have calculated values (@KomapperUpdatedAt, @KomapperVersion) you'll want those values back. Is there a better way of detecting if the update didn't really do anything?
Versions

Komapper: 3.1.0
Kotlin: 2.0.21
JVM: 21
JDBC Driver or R2DBC Driver: JDBC
Database: Postgresql
OS: OSX

Thank you for your feedback.
In this case, it seems correct for db.runQuery to return null.
We’ll consider making this change.

Alternatively, I would be ok with an exception like RecordNotFoundException being thrown if the update is essentially a no-op.
In order to maintain backwards compatibility, maybe could add a new option to UpdateOptions to throw on no update performed?

Thank you for your suggestion.
I've addressed it in #1421.
Please feel free to share any feedback.

@nakamura-to i tested locally and this looks good! working as expected, thank you!

Close by #1421


Breaks when there is }, in scripts

Having }, inside one of the scripts breaks autocompletion.
The way the JSON is parsed out for script names is pretty archaic since the goal is to keep it portable across platforms.
Happy to take a PR on it if you feel like making the parsing with sed work better

I'm pretty sure I won't be able to crack it in any reasonable time because my level in bash script editing in 0.01 out of 1 😅
Speaking of a a simple fix could a regexp that searches for the end of "scripts" be changed like so?

we terminate if there is } and it is at the end of a line
we terminate if there is }, and it is either at the start or at the end of a line

This still won't be as bug-free as parsing json in full, but the likelihood of bugs should get smaller.

@kachkaev This should be fixed now in 0.6.0.

Thanks for trying to fix this @dsifford! It could be that I've done something wrong, but after updating to 0.6.0 script detection broke completely. I still see it working as it was in the pre-update terminal tabs, but in all new tabs I get:
yarn run →tab yarn run env
yarn →tab all standard yarn commands, no helloX commands
npm run still shows hello1 ... hello5 as it should and it's not just one package.json when I see the problem.
What could be causing this in brew's bash 4.4.19(1)-release (x86_64-apple-darwin17.3.0) with yarn-completion 0.6.0 also installed via homebrew?

Not sure. I tried all the examples you provided when I made the change and it worked for me.
And actually, the change I made to the sed command made it even more POSIX compliant than the earlier one (the earlier one used extended regexp).
Did you try logging out completely and logging back in to make sure you weren't using a stale file or something?

I'll try in on my macbook here in the next hour or so and see if it's a mac quirk or something.

Same behaviour even after a full reboot. Curious to know what your mac test tells you! Thanks a lot for looking into this problem 🚀

Thanks for checking.
Do you have a repo that has a non-parsable package.json file that I can clone when I test on my macbook? I want to be certain that I'm reproducing this correctly.

@kachkaev Cant reproduce on my macbook.
Tried it using the package.json in this repo and it worked just fine for me: https://github.com/callthemonline/client-nextjs

Also, I just tried it again using both GNU and BSD sed and it still worked for me.
I assume you have the default BSD sed installed on your system? Can you try installing GNU sed and see if that works?

@kachkaev what's the output when you enter shopt -p | sort?

Downgrading to 0.5.1 by running
curl -L https://raw.githubusercontent.com/dsifford/yarn-completion/c40137136d8b803407f5f2fb99c1ae92af594b07/yarn-completion.bash > `brew --prefix`/etc/bash_completion.d/yarn

returns yarn-completion to its old behaviour described in this issue (after Terminal is relaunched, of course). This means that my setup is not broken as such and it's not the case of me having using two conflicting yarn completions somehow.
Upgrading one commit up to 3b5a4d7336fef8ac9342509d3637eadc8521111f makes things as broken as on current master (0.6.0), i.e. I only see yarn run  → run yarn env. The behaviour is the same both for https://github.com/callthemonline/client-nextjs and a dummy project where package.json just contains hello1...5 scripts.

@kachkaev I have no idea why this isn't working for you. I just matched all my shell options to the ones you have enabled and it still works perfectly fine on my end.
The only thing I can think of it might still be is that you're using BSD sed. If you can confirm that the issue is still persisting even using GNU sed, then I'm out of ideas and will have to unfortunately wait until more people report this issue.

Thanks for for your hint about GNU sed – turns out this is exactly what caused trouble! Originally, even after installing GNU bash, man sed was starting like:

After I did brew install gnu-sed --with-default-names and restarted the Terminal, it changed to:

Consequently, yarn autocompletion 0.6.0 began to work! 🎉
I'm a frequent user of the command line, but am no way an expert in bash versions and flavours of other standard commands. All this is pretty foggy to me, so thanks for your help with sorting things out! To summarise, this is what I had to do in order to get yarn-completion on macOS High Sierra working:
brew install bash
brew install gnu-sed --with-default-names

brew install bash-completion
## + copy a few commands to ~/.bash_profile as instructed by brew after bash-completion setup

curl -L https://raw.githubusercontent.com/dsifford/yarn-completion/master/yarn-completion.bash > `brew --prefix`/etc/bash_completion.d/yarn

## restart Terminal

Hope this helps someone else in a similar situation!

Urrrrgh! BSD utils are going to be the death of me, I swear....
Glad to hear we've found the culprit. I'll try and get this compatible with BSD as soon as feasible. Thanks for your patience.

Feel free to supplement README with my setup commands. I can easily imagine someone else getting into a similar trouble, so it’ll be great if we can save their time!

Open a PR with the edits and I'll be happy to merge

Version 0.6.1 should work in BSD sed now.

Thank you! 0.6.1 worked for me even after uninstalling gnu-sed 🎉


get_ts_daily

see mda.streams issue https://github.com/USGS-R/mda.streams/issues/204; when that is resolved, link to that function in powstreams

done as new args & behavior in get_ts in https://github.com/USGS-R/mda.streams/pull/216


Multiple Object File Extensions

Hello,
I am trying to use Ceedling with Microchip's XC8 and it's proving to be a bit harder than I'd hoped.  One issue is that XC8 generates object files with a '.o' extension if they've been assembled, and a '.p1' extension if they're the compiler's intermediate files.  XC8 unfortunately does not respect file extensions if you try and force them.
There are workarounds such as writing scripts to compile and assemble with a step to rename the output files.  Or to use string interpolation on the arguments passed into the linker in the project.yml file, which is what I'm currently doing.
What's really required is some sort of :assembly_object: key underneath :extension: - or just allowing :object: to be an array.
Thanks.

I'm having the same problem. The test runner file is being compiled to a test_runner.p1 file, but the Ceedling linker command refers to the [non-existent] test_runner.o file. How do I fix this?

I'm also running XC8, Ceedling 0.31.1, Ruby 3.0. Kept getting the following error:
::: error: (141) can't open intput file "./build/test/out/c/runner.o": No such file or directory
The fix was to add the following line to the extension section:
:extension:
:executable: .out
:object: .p1 <<<<<<<<<<<

Closing this issue but only to cull the open issue list a bit. I'm also rolling this issue up into a single issue that deals with multiple file extensions for a single file type.


[Code review: Contract Bugs]: stakingIndex should have decimals

Describe the bug
Staking index is now an integer. And for the value like 1.999, staking index will be recoreded as 1.0 => make incorrect calculation
Current impl for stakingIndex
_stakingIndex = (totalStake * DECIMALS) / totalWstonMinted;

Deposit: attackers want staking index low
uint256 _wstonAmount = (_amount * DECIMALS) / stakingIndex;

Withdrawal: attacker want staking index high
uint256 _amountToWithdraw;
        _amountToWithdraw = (_wstonAmount * stakingIndex) / DECIMALS;

Impact
Users can take more token from staking pool
Exploit Scenario
Deposit: attackers deposit with amount of token so that the updated staking index is 1.99
For ex:

Total Stake: 99
Total mint: 0
Deposit: 100
=> staking index = 199/100 = 1.0 (Expectation: 1.99)

Withdrawal: attackers

Withdraw 10 token first: => Total staked / total minted = (199-10)/(100-10) = 2.0
Withdraw remaining token 90 with stakingIndex = 2.0 (The bigger stakingIndex, the more benefit for attacker)
=> Attackers can take more tokens then we expected

Recommendation
Consider using decimal for staking index like 6.

Thanks @nguyenzung. Since we are multiplying the index by DECIMALS, it is casted into 27 decimals. You can check by running this test. I can't see any scenario where the staking index is rounded.

Thank you @mehdi-defiesta
I see, you already used 27 decimals for stakingIndex.


Improve database constraints

I've added some extra constraints to the database to ensure our data is correct.
Closes #186

@ChewingBever backend testing failed


feat: Sync Modes in Add Node and Node Settings

set default sync modes in configs
added SyncModes components in Add Node and Node Settings (fixes #412)
tested all EL clients

Really great work! 🙏


New classes (TODO)

Create classes for encryption, decryption, and a builder as each of those two classes requires up to five parameters.

The builder class is done.  The skeletons for encryption and decryption are in place and instead of requiring builders they are consuming an Options class each.


Doesn't "work" with C2ME

When saving world with C2ME running it doesn't save portal tickets.
When opening world that has saved portal tickets(saved when C2ME was not installed) it loads the chunk loaders but just for a couple of seconds, then they get unloaded
Currently tested only on server-side

Thanks for reporting this. I'll try to find some time to check out how C2ME might be interfering with this.


added links to docs.opencollective.com

related to https://github.com/opencollective/opencollective/issues/1612

@xdamman the PR title could be more explicit


doc: translate uncontrolled components to zh-hant

doc: translate uncontrolled components to zh-hant

@neighborhood999 Thanks for reviewing. Just updated.


change sitecoreItems to documents

Hi @alindgren, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@HeidiSteen
Please approve/disapprove this PR with a comment here. Thanks.

#sign-off (verified)


Optimizing carbon to run without a  cache queue

Hi,
We're currently running a single carbon instance on an AWS C5.XLarge (4cores, 8GB) with the following config:
[cache]
LINE_RECEIVER_INTERFACE = <IP_ADDRESS>
PICKLE_RECEIVER_INTERFACE = <IP_ADDRESS>
CACHE_QUERY_INTERFACE = <IP_ADDRESS>

LINE_RECEIVER_PORT = 2003
PICKLE_RECEIVER_PORT = 2004
CACHE_QUERY_PORT = 7002

MAX_CACHE_SIZE = inf
MAX_UPDATES_PER_SECOND = 5000
MAX_UPDATES_PER_SECOND_ON_SHUTDOWN = 5000
MAX_CREATES_PER_MINUTE = 500

USE_FLOW_CONTROL = True

LOG_UPDATES = False
LOG_CACHE_HITS = False
LOG_CACHE_QUEUE_SORTS = False
LOG_CREATES = True

ENABLE_LOGROTATION = True

This runs fine. However, our use case is such that we do not want a queue as this results in a new graphs lag time of about 40-45 minutes. And with increasing clients and in turn increasing metrics, this lag will increase.
In the last few days, I've tried a combination of relay's and multiple carbons per core setups all on a single disk. None have worked.
I also thought the problem could be with the disk IO since it's always busy. To test this, I converted the AWS 3000 IOPs volume to an AWS 10000 IOPs volume and increased the MAX_UPDATES_PER_SECOND to 50000. But this had no effect as it did not even dent the queue.
Am I hitting some kind of soft limit with this config? If not, what steps can I take to decrease this queue?
We have a combination of metrics of varying intervals and retention schemes.
Here's our past 25 days of relevant data: https://imgur.com/Csc9dvx (The dip on the 23rd of May, is when the service was stopped and the volume was converted to an AWS 10k IOPs)

Strange, your points per update is just 3, which would imply that your queues are very small, unless you have some really long interval.

I also thought the problem could be with the disk IO since it's always busy.

What does iostat say?

@piotr1212 Hi. Thanks for the quick reply. Our shortest interval is 5 minutes. Max retention goes up to a year. Here's a small iostat -x 1.  Longer dump is here -> https://paste.debian.net/1082875/
The data disk is nvme2n1
Device:         rrqm/s   wrqm/s     r/s     w/s    rkB/s    wkB/s avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
nvme0n1           0.00     0.00    0.00    0.00     0.00     0.00     0.00     0.00    0.00    0.00    0.00   0.00   0.00
nvme1n1           0.00     0.00    0.00    0.00     0.00     0.00     0.00     0.00    0.00    0.00    0.00   0.00   0.00
nvme2n1           0.00     0.00 2155.00    0.00 12684.00     0.00    11.77     1.77    0.81    0.81    0.00   0.45  96.40

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
          38.21    0.00   15.38   20.00    0.00   26.41

Device:         rrqm/s   wrqm/s     r/s     w/s    rkB/s    wkB/s avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
nvme0n1           0.00     0.00    0.00    0.00     0.00     0.00     0.00     0.00    0.00    0.00    0.00   0.00   0.00
nvme1n1           0.00     0.00    0.00    0.00     0.00     0.00     0.00     0.00    0.00    0.00    0.00   0.00   0.00
nvme2n1           0.00     0.00 2052.00    0.00 11744.00     0.00    11.45     1.98    0.98    0.98    0.00   0.47  95.60

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
          47.92    0.00   27.86    8.33    0.00   15.89

Device:         rrqm/s   wrqm/s     r/s     w/s    rkB/s    wkB/s avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
nvme0n1           0.00     0.00    3.00    0.00    80.00     0.00    53.33     0.00    0.00    0.00    0.00   0.00   0.00
nvme1n1           0.00     0.00    0.00    0.00     0.00     0.00     0.00     0.00    0.00    0.00    0.00   0.00   0.00
nvme2n1           0.00     0.00 1935.00 1435.00 11256.00  5740.00    10.09    87.83   26.06    0.91   59.98   0.27  91.60

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
          46.44    0.00   24.80   10.29    0.00   18.47

Device:         rrqm/s   wrqm/s     r/s     w/s    rkB/s    wkB/s avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
nvme0n1           0.00     0.00    0.00    0.00     0.00     0.00     0.00     0.00    0.00    0.00    0.00   0.00   0.00
nvme1n1           0.00     0.00    0.00    0.00     0.00     0.00     0.00     0.00    0.00    0.00    0.00   0.00   0.00
nvme2n1           0.00     0.00 2212.00    0.00 12792.00     0.00    11.57     1.46    0.66    0.66    0.00   0.42  93.20

Your disk seems saturated (%util) but mostly due to reads rather than writes. Reads are needed for aggregation. Can you post your storage-schemas.conf, you might be able to reduce the number of archive so you need less reads.  Which version of carbon and whisper are you using?

@piotr1212 My carbon and whisper are both Version: 0.9.13. Also, here's my storage schema. I have at most 2 archives per metric.
[carbon]
pattern = ^carbon\.
retentions = 60s:90d

[data.def.retention]
pattern = ^data\.(.*)\.def\.
retentions = 900s:1d,3600s:365d

[data.ghi.retention]
pattern = ^data\.(.*)\.ghi\.
retentions = 3600s:1d,86400s:365d

[data.jkl.retention]
pattern = ^data\.(.*)\.jkl\.
retentions = 1800s:1d,86400s:365d

[data.mno.retention]
pattern = ^data\.(.*)\.disk\.mno\.
retentions = 1800s:1d,86400s:365d

[data.disk.usage.retention]
pattern = ^data\.(.*)\.disk\.root\.
retentions = 1800s:1d,86400s:365d

[data.disk.pqr.usage.retention]
pattern = ^data\.(.*)\.disk\.pqr\.
retentions = 86400s:365d

[data.disk.stu.usage.retention]
pattern = ^data\.(.*)\.disk\.stu\.
retentions = 86400s:365d

[data.vwx.retention]
pattern = ^data\.(.*)\.vwx\.
retentions = 900s:1d,3600s:365d

[data.net.retention]
pattern = ^data\.(.*)\.net\.eth0\.
retentions = 600s:1d,3600s:365d

[data.yz.count.retention]
pattern = ^data\.(.*)\.yz\.count\.
retentions = 1800s:1d,86400s:365d

[data.var.retention]
pattern = ^data\.(.*)\.var\.
retentions = 900s:1d,3600s:365d

[data.cba.retention]
pattern = ^data\.(.*)\.cba\.
retentions = 120s:1d

[data.fed.retention]
pattern = ^data\.(.*)\.fed\.
retentions = 300s:1d,900s:365d

[data.memory.retention]
pattern = ^data\.(.*)\.memory\.
retentions = 300s:1d,900s:365d

[data.ihg.retention]
pattern = ^data\.(.*)\.ihg\.
retentions = 600s:1d,3600s:365d

[data.lkj.retention]
pattern = ^data\.(.*)\.lkj\.
retentions = 1d:365d

[abc2]
pattern = ^abc2\.
retentions = 60s:1d,900s:365d

[abc]
pattern = ^abc\.
retentions = 3600s:1825d

[default_1min_for_1day]
pattern = .*
retentions = 60s:1d,900s:365d

0.9.13 is old, there are some perf improvements in later versions wrt page cache trashing. I don't know your budget for disk space, but I'd just get rid of the second archive and make the first larger, especially for the metrics which have less than 1 datapoint per 15 minutes. More ram could also help, then reads will come from page cache instead of disk, but I have no clue how much more ram you'd need.


Use PR labels when generating release notes

PR labels will allow categorizing changes in release notes, especially highlighting breaking changes.

Neat ..


Fix coverage

Next attempt, this time I try what Chat GPT thinks is the right way of doing this

@gerw Not sure if this does the trick. Would you mind doing another merge and rebase?

Nope. From my very little understanding, it seems that the git workflow is running in my repository (for a PR from my fork), and this does not have access to stuff from this repo (e.g., to GITHUB_TOKEN). But I might be wrong.


Warning: tempnam(): open_basedir restriction in effect.

please what I have wrong?
do I need to allow some such directory?
Warning: tempnam(): open_basedir restriction in effect. File(/tmp) is not within the allowed path(s): (/mnt/databox/www/myweb) in /mnt/databox/www/myweb/pdf/vendor/mikehaertl/php-tmpfile/src/File.php on line 38
in virtualhost config I have:
php_admin_value open_basedir /mnt/databox/www/myweb

I have add new row into virtualhost config:
php_admin_value open_basedir /mnt/databox/www/myweb/pdf/vendor/mikehaertl/php-tmpfile/src
and looks that the problem disappears

but now in appache2 log I see:
[Tue Nov 10 12:36:14.547387 2015] [:error] [pid 23308] [client <IP_ADDRESS>:50496] PHP Warning:  Unknown: open_basedir restriction in effect. File(/mnt/databox/www/myweb/pdf/test.php) is not within the allowed path(s): (/mnt/databox/www/myweb/pdf/vendor/mikehaertl/php-tmpfile/src) in Unknown on line 0

This problem has nothing to do with my library. PHP is configured to not let you write to the PDF output directory. Please use Google to solve this kind of problems, for example here:
http://stackoverflow.com/questions/1846882/open-basedir-restriction-in-effect-file-is-not-within-the-allowed-paths


Provide a Way to Use Runtime Environment Variables

Currently angular-cli has the environment option, which works great for setting environment variables at build time, but I have a requirement to use environment variables at run time.  So I am sent a header from an Apache server called 'X-Environment' which contains 'dev', 'qa', 'prod', etc, and then at I use that to determine which environment variables to use.  The reasoning for this is that the build team at my work wants a single deployable file (what's in the dist folder zipped up) that is built once and and deployed to multiple environments.
All the searching I've done provides solutions about setting environment variables at build time, but none at run time. It would be nice something were built in angular-cli to make this happen, rather than having to do it manually.

+1
"ng eject" is available to run the server with webpack config, but the documentation for it is minimal.

TBH I don't think is a CLI issue, because the CLI isn't a runtime tool. I would really look at refactoring your configuration to to move those runtime variables out of the environment file and into something that can be set dynamically. Most likely you will need some server-side assist to do that since I don't think your angular app would have access to the request headers anyway. So for example you can have your web server inspect the header and set some global variables for the appropriate environment, then reference those variables in your angular app rather than using the environment files.

What I mentioned above is doable because there are two other Angular 2 projects at my work doing it (using a header).  They also had to set it up manually, but I can confirm it's working.  Those projects used one of the angular-seed projects rather than angular-cli, so it uses System.js and gulp, but I about to port over what they did.

I'd be surprised if they're doing it entirely from the angular client-side code. Most likely the page that is loading the angular app contains server-side logic to inspect the header and vary some parameter in the rendered output.

The safest runtime solution is to call http.get('/config.json') at startup.

Well yeah, it's doable but you have to do it yourself. There's plenty of ways of getting config files at runtime. We added a build-time feature because that you couldn't code into your application.
@martinmcwhorter's suggestion is pretty simple and to the point.
Also related https://github.com/angular/angular-cli/issues/3855#issuecomment-274803729

This article has a pretty good example of setting up a runtime solution for anyone stuck on this like I was. https://juristr.com/blog/2018/01/ng-app-runtime-config/

For a framework that is very opinionated about pretty much everything, I'm surprised that there is no "Angular way" of doing this. I agree that this is probably not an angular-cli issue, but hitting a web server to load the config files at runtime feels hacky.


Google AI Gemini: implement streaming model

Discussed in https://github.com/langchain4j/langchain4j/discussions/1902

Originally posted by Bjarne-Kinkel October 11, 2024
Is there allready an efford to implement a GoogleAiGeminiStreamingChatModel as mentioned here? Or at least a feature request?

I haven't succeeded yet with Retrofit/OkHttp to implement a streaming variant, but I'd definitely want to have it!
Would you want to try to implement this yourself?

BTW next week we will start migrating to java 17, so no need in retrofit/okhttp any more, let's use jdk 11 http client by default

I'll take a look at it, though I'm not sure if I'll be able to pull it off. Is there already any code for this?

@Bjarne-Kinkel I had started with Retrofit/OkHttp but never got it to work, and anyway, we need to move to JDK 11 HttpClient, so we have to start from scratch (and we'll have to migrate the current non-streaming model to also use HttpClient instead).
There are 2 streaming modes for the Gemini API:

HTTP/2: which sends a big JSON array that contains response fragments
SSE: a server-sent-event mode that is classical SSE, but you have to alter the endpoint URL by appending ?alt=sse.

I'm not sure what's the easiest to implement with HttpClient, to be honest.
It's worth trying with cURL first, to get a good idea of what is exchanged exactly.
Don't hesitate to ping me here or on the Discord channel to further discuss it as you progress along. Happy to help!

@glaforge Okay, I will take a closer look at it next week. So far, I have only found information about streaming with SSE. Where can I find information about the option with HTTP/2?

@Bjarne-Kinkel good question! I didn't really find any page that documents how streaming really works.
The best way for me was to just to try with curl to better understand what was flying through the wire.
For example on this page they show an example of streaming with SSE:
curl "https://generativelanguage.googleapis.com/v1beta/models/gemini-1.5-flash:streamGenerateContent?alt=sse&key=${GOOGLE_API_KEY}" \
        -H 'Content-Type: application/json' \
        --no-buffer \
        -d '{ "contents":[{"parts":[{"text": "Write a story about a magic backpack."}]}]}'

Notice the alt=sse added as query parameter.
It returns something like this:
HTTP/2 200
content-type: text/event-stream
content-disposition: attachment
vary: Origin
vary: X-Origin
vary: Referer
date: Sat, 12 Oct 2024 17:06:05 GMT
server: scaffolding on HTTPServer2
x-xss-protection: 0
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
server-timing: gfet4t7; dur=299
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000

data: {"candidates": [{"content": {"parts": [{"text": "The backpack"}],"role": "model"},"finishReason": "STOP","index": 0}],"usageMetadata": {"promptTokenCount": 8,"candidatesTokenCount": 2,"totalTokenCount": 10}}

data: {"candidates": [{"content": {"parts": [{"text": " was ordinary, except for the tarnished silver buckle that pulsed faintly whenever Maya touched it."}],"role": "model"},"finishReason": "STOP","index": 0,"safetyRatings": [{"category": "HARM_CATEGORY_SEXUALLY_EXPLICIT","probability": "NEGLIGIBLE"},{"category": "HARM_CATEGORY_HATE_SPEECH","probability": "NEGLIGIBLE"},{"category": "HARM_CATEGORY_HARASSMENT","probability": "NEGLIGIBLE"},{"category": "HARM_CATEGORY_DANGEROUS_CONTENT","probability": "NEGLIGIBLE"}]}],"usageMetadata": {"promptTokenCount": 8,"candidatesTokenCount": 20,"totalTokenCount": 28}}
...

It seems to be SSE over HTTP/2.
For non-SSE, you'll see that each candidate object ends up inside an array, and are thus all separated with commas:
curl "https://generativelanguage.googleapis.com/v1beta/models/gemini-1.5-flash:streamGenerateContent?ke=${GOOGLE_API_KEY}" \
        -H 'Content-Type: application/json'  \
        --http2 \
        --no-buffer \
        -d '{ "contents":[{"parts":[{"text": "Write a story about a magic backpack."}]}]}'

And the output gives:
HTTP/2 200
content-type: application/json; charset=UTF-8
vary: X-Origin
vary: Referer
vary: Origin,Accept-Encoding
date: Sat, 12 Oct 2024 17:08:39 GMT
server: scaffolding on HTTPServer2
cache-control: private
x-xss-protection: 0
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
server-timing: gfet4t7; dur=789
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
accept-ranges: none

[{
  "candidates": [
    {
      "content": {
        "parts": [
          {
            "text": "The"
          }
        ],
        "role": "model"
      },
      "finishReason": "STOP",
      "index": 0
    }
  ],
  "usageMetadata": {
    "promptTokenCount": 8,
    "candidatesTokenCount": 1,
    "totalTokenCount": 9
  }
}
,
{
  "candidates": [
    {
      "content": {
        "parts": [
          {
            "text": " old, worn leather backpack had been in the attic for years, collecting dust alongside"
          }
        ],
        "role": "model"
      },
      "finishReason": "STOP",
      "index": 0,
      "safetyRatings": [
        {
          "category": "HARM_CATEGORY_SEXUALLY_EXPLICIT",
          "probability": "NEGLIGIBLE"
        },
        {
          "category": "HARM_CATEGORY_HATE_SPEECH",
          "probability": "NEGLIGIBLE"
        },
        {
          "category": "HARM_CATEGORY_HARASSMENT",
          "probability": "NEGLIGIBLE"
        },
        {
          "category": "HARM_CATEGORY_DANGEROUS_CONTENT",
          "probability": "NEGLIGIBLE"
        }
      ]
    }
  ],
  "usageMetadata": {
    "promptTokenCount": 8,
    "candidatesTokenCount": 17,
    "totalTokenCount": 25
  }
}
,
...
]

I would go with SSE, as it is used by all other LLM providers, so it will be easier to fit into the abstracted HTTP client which I hope to finalize soon

@langchain4j The idea was to migrate the existing functions to the HttpClient (Java 11) before implementing the StreamingChatModel anyway. However, wouldn’t it make more sense to use your new abstracted client instead of creating a custom implementation with the HttpClient? Therefore, the new plan would be to first migrate the existing functions to the new abstracted client and then implement streaming. How usable is the abstracted client at this point?

@Bjarne-Kinkel that PR is a draft of a concept, it is far from being ready. I do not have clear timelines, it can easily be 2-3 months. So I would suggest implementing streaming using JDK 11 http client using SSE. Once this abstracted clients will be ready, it should be pretty easy to migrate.

Quick update:
I have now completed both tasks:
(1) the migration of the GeminiService to the HttpClient
(2) the GeminiAiStreamingChatModel
After initial testing, both seem to be working. I’ll try to create a PR in the coming days. I'll make two separate ones, marking them as drafts, correct? The PR for the streaming will then depend on the HttpClient PR. Is there anything else I should keep in mind @langchain4j?

@Bjarne-Kinkel great! Yes, 2 smaller is better than 1 big one :) Thank you!

@Bjarne-Kinkel Wonderful! I'm looking forward to reviewing the PRs!