[WFCORE-3883] / [WFCORE-3890] WildFly Elytron Component Upgrades

https://issues.jboss.org/browse/WFCORE-3883
https://issues.jboss.org/browse/WFCORE-3890
Release Notes - WildFly Elytron - Version 1.3.3.Final
** Bug
* [ELY-1568] - elytron-client-1.1.xsd xsd:all minOccurs="0"
* [ELY-1589] - elytron-client-1_1.xsd is invalid
* [ELY-1592] - CLI + Kerberos authentication fails in CD13
** Release
* [ELY-1594] - Release WildFly Elytron 1.3.3.Final

Core - Full Integration Build 7453 outcome was FAILURE using a merge of febb274866ca183699168b6ff9fc99016942e2c6
Summary: Tests failed: 3 (2 new), passed: 4338, ignored: 142 Build time: 02:49:05
Failed tests
org.jboss.as.test.clustering.cluster.singleton.SingletonServiceTestCase.testSingletonService: 	at org.jboss.as.test.clustering.cluster.singleton.SingletonServiceTestCase.testSingletonService(SingletonServiceTestCase.java:175)
------- Stdout: -------
 [0m05:35:51,613 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/a9/ba4cce35aa9e7ff0f41a1ee34ec58defaac132/content
 [0m [0m05:35:51,630 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "SingletonServiceTestCase.war" (runtime-name: "SingletonServiceTestCase.war")
 [0m [33m05:35:51,766 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.SingletonServiceTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [0m05:35:51,845 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 11) WFLYCLINF0002: Started default cache from server container
 [0m [0m05:35:51,866 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 11) WFLYUT0021: Registered web context: '/SingletonServiceTestCase' for server 'default-server'
 [0m [0m05:35:51,882 INFO  [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0003: node-1 elected as the singleton provider of the jboss.test.service.default service
 [0m [33m05:35:51,882 WARN  [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0006: Failed to reach quorum of 2 for jboss.test.service.quorum service. No singleton master will be elected.
 [0m [0m05:35:51,891 INFO  [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0001: This node will now operate as the singleton provider of the jboss.test.service.default service
 [0m [0m05:35:51,920 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "SingletonServiceTestCase.war" (runtime-name : "SingletonServiceTestCase.war")
 [0m [0m05:35:51,963 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/a9/ba4cce35aa9e7ff0f41a1ee34ec58defaac132/content
 [0m [0m05:35:51,968 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "SingletonServiceTestCase.war" (runtime-name: "SingletonServiceTestCase.war")
 [0m [33m05:35:52,125 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.SingletonServiceTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [0m05:35:52,284 INFO  [org.infinispan.CLUSTER] (remote-thread--p6-t1) ISPN000310: Starting cluster-wide rebalance for cache default, topology CacheTopology{id=2, phase=READ_OLD_WRITE_ALL, rebalanceId=2, currentCH=ReplicatedConsistentHash{ns = 256, owners = (1)[node-1: 256]}, pendingCH=ReplicatedConsistentHash{ns = 256, owners = (2)[node-1: 122, node-2: 134]}, unionCH=null, actualMembers=[node-1, node-2], persistentUUIDs=[023714fa-de84-4cab-beac-3d42ce221360, 290217b0-5233-435a-aef5-5db6b98b01cf]}
 [0m [0m05:35:52,285 INFO  [org.infinispan.CLUSTER] (remote-thread--p6-t1) [Context=default][Scope=node-1]ISPN100002: Started rebalance with topology id 2
 [0m [0m05:35:52,299 INFO  [org.infinispan.CLUSTER] (transport-thread--p13-t1) [Context=default][Scope=node-1]ISPN100003: Node node-1 finished rebalance phase with topology id 2
 [0m [0m05:35:52,301 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 7) WFLYUT0021: Registered web context: '/SingletonServiceTestCase' for server 'default-server'
 [0m [0m05:35:52,384 INFO  [org.infinispan.CLUSTER] (remote-thread--p6-t1) [Context=default][Scope=node-2]ISPN100003: Node node-2 finished rebalance phase with topology id 2
 [0m [0m05:35:52,391 INFO  [org.infinispan.CLUSTER] (remote-thread--p6-t1) ISPN000336: Finished cluster-wide rebalance for cache default, topology id = 2
 [0m [0m05:35:52,397 INFO  [org.infinispan.CLUSTER] (transport-thread--p13-t4) [Context=default][Scope=node-1]ISPN100003: Node node-1 finished rebalance phase with topology id 3
 [0m [0m05:35:52,409 INFO  [org.infinispan.CLUSTER] (remote-thread--p6-t1) [Context=default][Scope=node-2]ISPN100003: Node node-2 finished rebalance phase with topology id 3
 [0m [0m05:35:52,414 INFO  [org.infinispan.CLUSTER] (transport-thread--p13-t6) [Context=default][Scope=node-1]ISPN100003: Node node-1 finished rebalance phase with topology id 4
 [0m [0m05:35:52,425 INFO  [org.infinispan.CLUSTER] (remote-thread--p6-t1) [Context=default][Scope=node-2]ISPN100003: Node node-2 finished rebalance phase with topology id 4
 [0m [0m05:35:52,437 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 10) WFLYCLINF0002: Started default cache from server container
 [0m [0m05:35:52,459 INFO  [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0003: node-2 elected as the singleton provider of the jboss.test.service.default service
 [0m [0m05:35:52,461 INFO  [org.wildfly.clustering.server] (ChannelCommandDispatcherFactory - 1) WFLYCLSV0002: This node will no longer operate as the singleton provider of the jboss.test.service.default service
 [0m [0m05:35:52,494 INFO  [org.wildfly.clustering.server] (ChannelCommandDispatcherFactory - 1) WFLYCLSV0001: This node will now operate as the singleton provider of the jboss.test.service.default service
 [0m [0m05:35:52,499 INFO  [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0007: Just reached required quorum of 2 for jboss.test.service.quorum service. If this cluster loses another member, no node will be chosen to provide this service.
 [0m [0m05:35:52,501 INFO  [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0003: node-2 elected as the singleton provider of the jboss.test.service.quorum service
 [0m [0m05:35:52,594 INFO  [org.wildfly.clustering.server] (ChannelCommandDispatcherFactory - 1) WFLYCLSV0001: This node will now operate as the singleton provider of the jboss.test.service.quorum service
 [0m [0m05:35:52,616 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "SingletonServiceTestCase.war" (runtime-name : "SingletonServiceTestCase.war")
 [0m [0m05:35:52,673 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0236: Suspending server with no timeout.
 [0m [0m05:35:52,678 INFO  [org.jboss.as.ejb3] (management-handler-thread - 2) WFLYEJB0493: EJB subsystem suspension complete
 [0m [0m05:35:52,683 INFO  [org.jboss.as.server] (Management Triggered Shutdown) WFLYSRV0241: Shutting down in response to management operation 'shutdown'
 [0m [0m05:35:52,778 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 33) WFLYUT0022: Unregistered web context: '/SingletonServiceTestCase' from server 'default-server'
 [0m [0m05:35:52,791 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-3) ISPN000080: Disconnecting JGroups channel ejb
 [0m [0m05:35:52,792 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000080: Disconnecting JGroups channel ejb
 [0m [0m05:35:52,809 INFO  [org.wildfly.clustering.server] (ChannelCommandDispatcherFactory - 1) WFLYCLSV0002: This node will no longer operate as the singleton provider of the jboss.test.service.default service
 [0m [0m05:35:52,803 INFO  [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0003: node-1 elected as the singleton provider of the jboss.test.service.default service
 [0m [0m05:35:52,811 INFO  [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0001: This node will now operate as the singleton provider of the jboss.test.service.default service
 [0m [33m05:35:52,865 WARN  [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0006: Failed to reach quorum of 2 for jboss.test.service.quorum service. No singleton master will be elected.
 [0m [0m05:35:52,872 INFO  [org.wildfly.clustering.server] (ChannelCommandDispatcherFactory - 1) WFLYCLSV0002: This node will no longer operate as the singleton provider of the jboss.test.service.quorum service
 [0m [0m05:35:52,931 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
 [0m [0m05:35:52,976 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0019: Host default-host stopping
 [0m [0m05:35:52,973 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 33) MODCLUSTER000002: Initiating mod_cluster shutdown
 [0m [0m05:35:52,998 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 10) WFLYCLINF0003: Stopped default cache from server container
 [0m [0m05:35:53,002 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000080: Disconnecting JGroups channel ejb
 [0m [0m05:35:53,006 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0019: Stopped Driver service with driver-name = h2
 [0m [33m05:35:53,013 WARN  [org.jboss.modcluster] (ServerService Thread Pool -- 33) MODCLUSTER000033: Failed to interrupt socket reception.: java.io.IOException: Invalid argument (sendto failed)
	at java.net.PlainDatagramSocketImpl.send(Native Method)

org.jboss.as.test.clustering.cluster.web.DistributableTestCase.testSessionReplication: java.lang.AssertionError: expected:<3> but was:<1>
	at org.jboss.as.test.clustering.cluster.web.DistributableTestCase.testSessionReplication(DistributableTestCase.java:153)
------- Stdout: -------
 [0m05:36:51,805 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/21/0eaa0ecc0a56a898351ea2d98f9bbc02e3d155/content
 [0m [0m05:36:51,810 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "DistributableTestCase.war" (runtime-name: "DistributableTestCase.war")
 [0m [0m05:36:52,142 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 79) WFLYCLINF0002: Started default-server cache from web container
 [0m [0m05:36:52,152 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 80) WFLYCLINF0002: Started DistributableTestCase.war cache from web container
 [0m [0m05:36:52,175 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 80) WFLYUT0021: Registered web context: '/DistributableTestCase' for server 'default-server'
 [0m [0m05:36:52,210 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "DistributableTestCase.war" (runtime-name : "DistributableTestCase.war")
 [0m [0m05:36:52,247 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/2c/10cb3b55cbc9b56c529c06fb3aa8ae7f32641f/content
 [0m [0m05:36:52,253 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "DistributableTestCase.war" (runtime-name: "DistributableTestCase.war")
 [0m [0m05:36:52,486 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 79) WFLYCLINF0002: Started default-server cache from web container
 [0m [0m05:36:52,501 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 80) WFLYCLINF0002: Started DistributableTestCase.war cache from web container
 [0m [0m05:36:52,523 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 79) WFLYUT0021: Registered web context: '/DistributableTestCase' for server 'default-server'
 [0m [0m05:36:52,547 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "DistributableTestCase.war" (runtime-name : "DistributableTestCase.war")
 [0m [0m05:36:52,589 INFO  [io.undertow.servlet] (default task-2) /DistributableTestCase/simple, value = 1
 [0m [0m05:36:52,604 INFO  [io.undertow.servlet] (default task-1) /DistributableTestCase/simple, value = 2
 [0m [0m05:36:55,646 INFO  [io.undertow.servlet] (default task-1) /DistributableTestCase/simple, value = 1
 [0m [0m05:36:55,659 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 80) WFLYUT0022: Unregistered web context: '/DistributableTestCase' from server 'default-server'
 [0m [0m05:36:55,667 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 79) ISPN000029: Passivating all entries to disk
 [0m [0m05:36:55,670 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 79) ISPN000030: Passivated 3 entries in 2 milliseconds
 [0m [0m05:36:55,681 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 79) WFLYCLINF0003: Stopped DistributableTestCase.war cache from web container
 [0m [0m05:36:55,709 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 80) WFLYCLINF0003: Stopped default-server cache from web container
 [0m [0m05:36:55,724 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment DistributableTestCase.war (runtime-name: DistributableTestCase.war) in 69ms
 [0m [0m05:36:55,740 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/21/0eaa0ecc0a56a898351ea2d98f9bbc02e3d155/content
 [0m [0m05:36:55,740 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0009: Undeployed "DistributableTestCase.war" (runtime-name: "DistributableTestCase.war")
 [0m [0m05:36:55,762 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 79) WFLYUT0022: Unregistered web context: '/DistributableTestCase' from server 'default-server'
 [0m [0m05:36:55,789 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 79) ISPN000029: Passivating all entries to disk
 [0m [0m05:36:55,794 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 79) ISPN000030: Passivated 3 entries in 5 milliseconds
 [0m [0m05:36:55,807 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 79) WFLYCLINF0003: Stopped DistributableTestCase.war cache from web container
 [0m [0m05:36:55,826 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment DistributableTestCase.war (runtime-name: DistributableTestCase.war) in 69ms
 [0m [0m05:36:55,827 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 79) WFLYCLINF0003: Stopped default-server cache from web container
 [0m [0m05:36:55,851 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/2c/10cb3b55cbc9b56c529c06fb3aa8ae7f32641f/content
 [0m [0m05:36:55,851 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0009: Undeployed "DistributableTestCase.war" (runtime-name: "DistributableTestCase.war")
 [0m

org.jboss.as.test.clustering.cluster.web.ConcurrentFineWebFailoverTestCase.test: java.lang.AssertionError: expected:<200> but was:<500>
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:69)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:58)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:52)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.establishTopology(AbstractWebFailoverTestCase.java:360)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:120)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:112)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.test(AbstractWebFailoverTestCase.java:103)
------- Stdout: -------
 [0m05:36:26,940 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/26/3f8cac76030f20e164f54143eb945721df8382/content
 [0m [0m05:36:26,945 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "ConcurrentFineWebFailoverTestCase.war" (runtime-name: "ConcurrentFineWebFailoverTestCase.war")
 [0m [33m05:36:27,202 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m05:36:27,203 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m05:36:27,203 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m05:36:27,203 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m05:36:27,203 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m05:36:27,283 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment ConcurrentFineWebFailoverTestCase.war
 [0m [0m05:36:27,421 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-1) HV000001: Hibernate Validator 5.3.6.Final
 [0m [0m05:36:27,569 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ConcurrentFineWebFailoverTestCase.war"' are as follows:

	java:global/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:jboss/exported/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	ejb:ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:global/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean
	java:app/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean
	java:module/TopologyChangeListenerBean

 [0m [0m05:36:27,889 INFO  [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900: 3.0.4 (Final)
 [0m [0m05:36:28,191 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 76) WFLYCLINF0002: Started default-server cache from web container
 [0m [0m05:36:28,206 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 75) WFLYCLINF0002: Started ConcurrentFineWebFailoverTestCase.war cache from web container
 [0m [33m05:36:28,674 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-5) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor is deprecated from CDI 1.1!
 [0m [33m05:36:28,708 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-5) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.jberet.creation.BatchBeanProducer is deprecated from CDI 1.1!
 [0m [0m05:36:29,865 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 75) WFLYUT0021: Registered web context: '/ConcurrentFineWebFailoverTestCase' for server 'default-server'
 [0m [0m05:36:29,915 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "ConcurrentFineWebFailoverTestCase.war" (runtime-name : "ConcurrentFineWebFailoverTestCase.war")
 [0m [0m05:36:30,052 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/cf/3e8df7bf034c1f600b4182f7d51c9c7bc8b576/content
 [0m [0m05:36:30,057 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "ConcurrentFineWebFailoverTestCase.war" (runtime-name: "ConcurrentFineWebFailoverTestCase.war")
 [0m [33m05:36:30,253 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m05:36:30,254 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m05:36:30,254 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m05:36:30,254 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m05:36:30,254 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m05:36:30,327 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment ConcurrentFineWebFailoverTestCase.war
 [0m [0m05:36:30,464 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-5) HV000001: Hibernate Validator 5.3.6.Final
 [0m [0m05:36:30,618 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ConcurrentFineWebFailoverTestCase.war"' are as follows:

	java:global/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:jboss/exported/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener

Core - Full Integration Build 7460 outcome was FAILURE using a merge of febb274866ca183699168b6ff9fc99016942e2c6
Summary: Tests failed: 1, passed: 4340, ignored: 142 Build time: 01:40:35
Failed tests
org.jboss.as.test.clustering.cluster.web.ConcurrentFineWebFailoverTestCase.test: java.lang.AssertionError: expected:<200> but was:<500>
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:69)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:58)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:52)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.establishTopology(AbstractWebFailoverTestCase.java:360)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:120)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:112)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.test(AbstractWebFailoverTestCase.java:103)
------- Stdout: -------
 [33m07:57:59,618 WARN  [org.jgroups.protocols.pbcast.GMS] (VERIFY_SUSPECT.TimerThread-81,ejb,node-3) node-3: failed to collect all ACKs (expected=1) for view [node-3|33] after 2000ms, missing 1 ACKs from (1) node-1
 [0m [0m07:57:59,623 INFO  [org.infinispan.CLUSTER] (VERIFY_SUSPECT.TimerThread-81,ejb,node-3) ISPN000094: Received new cluster view for channel ejb: [node-3|34] (1) [node-3]
 [0m [0m07:57:59,623 INFO  [org.infinispan.CLUSTER] (VERIFY_SUSPECT.TimerThread-81,ejb,node-3) ISPN100001: Node node-1 left the cluster
 [0m [0m07:57:59,624 INFO  [org.infinispan.CLUSTER] (VERIFY_SUSPECT.TimerThread-81,ejb,node-3) ISPN000094: Received new cluster view for channel ejb: [node-3|34] (1) [node-3]
 [0m [0m07:57:59,624 INFO  [org.infinispan.CLUSTER] (VERIFY_SUSPECT.TimerThread-81,ejb,node-3) ISPN100001: Node node-1 left the cluster
 [0m [0m07:57:59,624 INFO  [org.infinispan.CLUSTER] (VERIFY_SUSPECT.TimerThread-81,ejb,node-3) ISPN000094: Received new cluster view for channel ejb: [node-3|34] (1) [node-3]
 [0m [0m07:57:59,624 INFO  [org.infinispan.CLUSTER] (VERIFY_SUSPECT.TimerThread-81,ejb,node-3) ISPN100001: Node node-1 left the cluster
 [0m [0m07:57:59,624 INFO  [org.infinispan.CLUSTER] (VERIFY_SUSPECT.TimerThread-81,ejb,node-3) ISPN000094: Received new cluster view for channel ejb: [node-3|34] (1) [node-3]
 [0m [0m07:57:59,628 INFO  [org.infinispan.CLUSTER] (VERIFY_SUSPECT.TimerThread-81,ejb,node-3) ISPN100001: Node node-1 left the cluster
 [0m [0m07:57:59,674 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/5e/62ff62ede8ab2cc2f66ad5227c506f06ae40c4/content
 [0m [0m07:57:59,677 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "ConcurrentFineWebFailoverTestCase.war" (runtime-name: "ConcurrentFineWebFailoverTestCase.war")
 [0m [33m07:57:59,816 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m07:57:59,817 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m07:57:59,817 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m07:57:59,817 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m07:57:59,817 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m07:57:59,861 INFO  [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment ConcurrentFineWebFailoverTestCase.war
 [0m [0m07:57:59,975 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-8) HV000001: Hibernate Validator 5.3.6.Final
 [0m [0m07:58:00,077 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ConcurrentFineWebFailoverTestCase.war"' are as follows:

	java:global/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:jboss/exported/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	ejb:ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:global/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean
	java:app/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean
	java:module/TopologyChangeListenerBean

 [0m [0m07:58:00,230 INFO  [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 3.0.4 (Final)
 [0m [0m07:58:00,363 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 2) WFLYCLINF0002: Started default-server cache from web container
 [0m [0m07:58:00,392 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 28) WFLYCLINF0002: Started ConcurrentFineWebFailoverTestCase.war cache from web container
 [0m [33m07:58:00,659 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-3) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor is deprecated from CDI 1.1!
 [0m [33m07:58:00,676 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-3) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.jberet.creation.BatchBeanProducer is deprecated from CDI 1.1!
 [0m [0m07:58:01,151 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 2) WFLYUT0021: Registered web context: '/ConcurrentFineWebFailoverTestCase' for server 'default-server'
 [0m [0m07:58:01,169 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "ConcurrentFineWebFailoverTestCase.war" (runtime-name : "ConcurrentFineWebFailoverTestCase.war")
 [0m [0m07:58:01,221 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/cb/27c73df95e126611d495840decb1fb89c25833/content
 [0m [0m07:58:01,225 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "ConcurrentFineWebFailoverTestCase.war" (runtime-name: "ConcurrentFineWebFailoverTestCase.war")
 [0m [33m07:58:01,306 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m07:58:01,306 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m07:58:01,306 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m07:58:01,306 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.

Getting closer, 4 out of 5 now passed !


Deprecate TaskInputs query methods

These methods expose internal state that is expensive to calculate. Instead of using them, user code can rely on declared task properties.

Feedback build: https://builds.gradle.org/viewQueued.html?itemId=9895234

Feedback build: https://builds.gradle.org/viewQueued.html?itemId=9895444

Feedback build: https://builds.gradle.org/viewQueued.html?itemId=9899595

Build: https://builds.gradle.org/viewQueued.html?itemId=9900584


how to change the cancelButton title?

I want to change the cancelButton title from "Cancel" to another one!
is there some ways to change it?
thank you!

Yes.
The system should localize it to whatever cancel is in your language, as it is UIBarButtonSystemItemCancel.
If you aren't happy with that you can do some voodoo on it to change the title. I do it with the done button to add the count.
Check out a function named something like updateDoneButton in PhotosViewController for an example.
I don't have my computer with me today, so this is the best answer I can give at the moment, I hope it helps! :)


chore(deps): use working version of strapi + plugins

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

:crossed_fingers: this version should pass all the tests.

Closing in favour of https://github.com/freeCodeCamp/publish/pull/319


Small examples

We need small examples of two tasks we want to achive:

Gazebo plugin in Python
Flask like interface for publishing and subscribing

Hello @awesomebytes,
I agree with your list.  In my opinion Python should play a much larger role in robotics, similar to how it is in data science.
The last days I have played with pybind11. I have started writing a wrapper for Gazebo sensor plugins (similar to your image_transport wrapper), but it is much harder than I have hoped. I will keep trying and publish my results here.

Hey @arturmiller, when I wrote my previous comment I gave a quick thought at "what is the minimum needed to actually make a gazebo plugin in Python?".
And by checking the API, the classes involved, and my experience patching plugins and developing others... It's a lot of work. I think it's not really human-friendly work.
I've been toying with tools that automate the work of generating wrappers with pybind11, but I haven't found any magical tool that just worked.
If you'd be ok with it, I'd like to see the progress you do on your approach. If you check my repos about the pybind11 wrapping of image transport I do a lot of commits that just explain what I'm doing while fixing mistakes or learning how things work. Granted I don't write enough to understand my full thought process but it's enough to get the hang of it I think. I'd love to be able to follow what you do also to learn on the way.
Otherwise, we could have a chat at some point in a more interactive manner. I strongly think Python should be playing an even major role too.


Only set the atexit hook when simulation is running

I often will use CTRL-C in an ipython / python shell to escape out of the current statement. It's all good until I import armi and these hooks will throw a sys.exit
https://github.com/terrapower/armi/blob/5b3555cbc6f07470f03d395b00920b2dc4f05290/armi/__init__.py#L334-L342
I get why these are here: to gracefully cleanup when a simulation is running and an interrupt is thrown. But when I'm just poking around in an ARMI model, or debugging, and I've filled my python shell with setup stuff, a (potentially bad) habit of CTRL-C throws it all away.
Would it be possible to have these atexit calls when something expensive is being performed? Like by the operator?
Other atexit related things

https://github.com/terrapower/armi/issues/257
https://github.com/terrapower/armi/issues/308

Maaaaaybe.
But ARMI is using the pluggy system, and pluggys whole deal is it loads up all the hooks at import time.
In the past, I've had a really hard time doing anything extra with hooks after the initial pluggy setup.
Off the top of my head, this might be impossible without making a big PR into the pluggy system to allow for post-fact hooks to be registered.  BUT, also, maybe I'm wrong.  It's worth exploring.

@john-science the usage of "hooks" was not meant to be a red herring about pluggy. Rather than these lines being added and called anytime you import armi, could they be guarded in a function that is called when something big is about to happen? Like Operator.operate?


added pen pal analogy

Perhaps it isn't the most zoomer explanation, but I think it is pretty good.

Here I'll edit it a bit and see what I can do @detjensrobert.

I might take another look at it later with a fresh set of eyes, but hopefully that is more friendly sounding.

I like the changes you made--- looks good to me!


Styling configuration

fixes #5

I think this is good to go -- though haven't done extensive testing
I added some actions which don't appear to be executing, not sure if that's something you need to trigger/enable? Looks like it should be free though https://github.blog/2019-08-08-github-actions-now-supports-ci-cd/

LGTM, will look at adding the actions.
I still don't really like using " when ' are enough, that should be the real debate, not space or tabs, but will listen to ruff wisdom from now on.


Map component

As a developer, I want the capabilities of #19 to be refactored as a reusable component so that it can be used for the main map view and also used in other places, such as the two column layout (with an image of the station) that is used in the metadata view.

Can we close this?


The new chisel (updated in Rocket on 02/03/2017) does not work with riscv-boom.

Old version (works): e27657118ff5915b96f8e3a467d464245fe09769
New version (does not work): 97871178cb511063965f971b768f91c289c4776f
When compiling the riscv-boom code, an exception occurs in this line:
https://github.com/freechipsproject/chisel3/blob/97871178cb511063965f971b768f91c289c4776f/chiselFrontend/src/main/scala/chisel3/core/Aggregate.scala#L617
error text:
...
[error] Caused by: chisel3.core.AutoClonetypeException: Unable to automatically infer cloneType on class boom.IssueSlotIO$$anon$1: Unable to determine instance of outer class class boom.IssueSlotIO, multiple possible candidates List(boom.IssueSlotIO@69a5c, boom.IssueSlotIO@69da4) assignable to outer class type
[error] 	at chisel3.core.Bundle.chisel3$core$Bundle$$autoClonetypeError$1(Aggregate.scala:576)
[error] 	at chisel3.core.Bundle$$anonfun$11.apply(Aggregate.scala:617)
[error] 	at chisel3.core.Bundle$$anonfun$11.apply(Aggregate.scala:593)
[error] 	at scala.Option.map(Option.scala:146)
[error] 	at chisel3.core.Bundle.cloneType(Aggregate.scala:593)
[error] 	at chisel3.core.Bundle.cloneType(Aggregate.scala:511)
[error] 	at chisel3.core.Output$.apply(Data.scala:180)
[error] 	at Chisel.package$AddDirectionToData$.asOutput$extension(compatibility.scala:28)
[error] 	at boom.IssueSlotIO.<init>(issue_slot.scala:42)
[error] 	at boom.IssueSlotIO.cloneType(issue_slot.scala:45)
[error] 	at boom.IssueSlotIO.cloneType(issue_slot.scala:19)
...

the riscv-boom code in which the error occurs:
...
19: class IssueSlotIO(num_wakeup_ports: Int)(implicit p: Parameters) extends BoomBundle()(p)
20: {
...
36:   val debug = {
37:     val result = new Bundle {
38:       val p1 = Bool()
39:       val p2 = Bool()
40:       val p3 = Bool()
41:    }
42:    result.asOutput
43:  }
44:
45:   override def cloneType = new IssueSlotIO(num_wakeup_ports)(p).asInstanceOf[this.type]
...

What do you think about it?

In case anyone else is looking at this, I was able to reproduce it with the code below. Note that the Wire construction is necessary (in that it doesn't trip on the first clone in IO), which leads me to believe this can be cloned once but not again. It also does not work with any iteration of autoclonetype. As in the error message above, it appears to have two candidates of MyCoolBundle for the outer object which is strange.
import chisel3._

class MyCoolBundle(w: Int) extends Bundle {
  val foo = {
    val bar = new Bundle {
      val a = UInt(w.W)
    }
    Output(bar)
  }
  override def cloneType = new MyCoolBundle(w).asInstanceOf[this.type]
}

class AutoCloneTypeTop extends Module {
  val io = IO(new MyCoolBundle(8))
  val wire = WireInit(io)
}

Thanks for the minimal test case. It's potentially the outer class detection by stack frame examination, it's seeing both the cloneType call on the earlier Bundle, and the call to init inside cloneType for the new Bundle. Potentially solvable by having the stack frame examination filter only init calls, or just being more stricter about matching name/line/frame position/etc. Will give that a try and see if it solves the minimal test case.


[PE-D][Tester D] Different color for success message

difference in font color of success message between the screenshot provided on the UG vs the actual product

Labels: severity.VeryLow type.DocumentationBug
original: tanyunchao/ped#4

fixed


Refactor nodesyncer

Refactor and testing commits from https://github.com/rancher/rancher/pull/20375

lgtm

@daxmc99 please reference the issue that caused you to make this change (for fixing the syncing), i know it wont go to test yet bc you have the "real" fix to make, but i want both prs to have a link to the issue

lgtm

Part of addressing https://github.com/rancher/rancher/issues/14184


[Feature Request]: Allow config option to allow database to generate uuid

Description
Im new to lucia auth, but loving how easy it is to get auth going.
Maybe its already possible, but wondering if there is a way to not generate the uuid via lucia, I would like to leave it up to the db via something like @default(uuid()).
Also its possible that this is only an issue with the prisma connector, I'm not sure.
I tried the following with a ts-ignore:
export const auth = lucia({
	adapter: prisma(client),
	// @ts-ignore
	generateCustomUserId: () => undefined,
})

I then get the following error showing that user does not get created:
PrismaClientValidationError:
Invalid `prisma.authKey.create()` invocation:

{
  data: {
    id<EMAIL_ADDRESS>    user_id: undefined,
    hashed_password: 's2:6SHyaUmqIW1qfeB1:c22581dc9f2f9713b83a6028f0540e7bd6b8f982a91d02f04ada5dec6db5eb5174d4d1244b57855af59e74f32c71aa57f719803517017a15d2aa93ec752f18d9',
    primary_key: true,
?   expires?: BigInt | null,
+   auth_user: {
+     create?: AuthUserCreateWithoutAuth_keyInput | AuthUserUncheckedCreateWithoutAuth_keyInput,
+     connectOrCreate?: AuthUserCreateOrConnectWithoutAuth_keyInput,
+     connect?: AuthUserWhereUniqueInput
+   }
  }
}

Unfortunately no, especially with v2. See https://github.com/pilcrowOnPaper/lucia/discussions/678, specifically "Remove support for default values in the user table"


Update requirements.txt and use optional dependencies

It would be good to have an updated requirements.txt since there are several dependencies that are not listed (e.g. onnxoptimizer, nvidia-tensorrt, onnxruntime, transformer-deploy) and also requires TVM to be installed.
If any of these are not core to VoltaML it might be worth adopting an installation method that allows the user to select what is needed, e.g:
pip install voltaml[minimal]
pip install volatml[tvm]
etc...

If TVM is a core requirement, it would probably be worth documenting that since building TVM from source may not be trivial in some environments (e.g. Kaggle GPU notebooks, Colab etc)

Hi @Anjum48. Thanks for your suggestion. We will update our requirements soon and also have installation methods for different compilers.


change compiler source version to 1.6

since SQLFeatureNotSupportedException is documented to only be available since 1.6
https://docs.oracle.com/javase/7/docs/api/java/sql/SQLFeatureNotSupportedException.html

OK. LGTM


CMake improvements, make package relocatable

The current build does not allow one to move the library to another directory. By writing a config with absolute paths, the dependencies will incorrectly check the build directory instead of the current location. This patch uses relative paths from the CMake config to keep the config valid even if the entire package is moved.

Coverage decreased (-0.1%) to 93.825% when pulling 2c98c30a02e0d8ba004f9db7005dc7fbd9a90f1b on isaachier:cmake into d098c0ff86a1a704ab4b42eef8efbee8dec5cf9d on akheron:master.

Hi and thanks for the PR.
I've felt that the CMake configuration needs cleanup for a long time now. The problem is that my knowledge about CMake is close to zero, and I don't really mind learning it to be honest.
Do you think this PR cleans as much of the CMake config as possible? I think at least most of the comment near the top of CMakeLists.txt should also be removed. Is there anything else after that?

@JoakimSoderberg do you happen to have time to comment on this PR?

I deleted the original configs. I added a new one in cmake/Config.cmake.in. I've love to help enhance the CMake build in general. These changes were minimal to ensure compliance with the Hunter package manager (https://github.com/ruslo/hunter). My project relies on Hunter to download and build a relocatable Jansson.

Definitely not the same as C++ namespace. In general, cmake doesn't do symbol renaming or anything libtool might do. This pull request is a bit outdated so let me update it before merging.

Merged, thanks!


User should be able to choose to display more items in the deposit list

As an example see https://sdr.stanford.edu/collections/285/works, shown below.
This defaults to displaying 10. The user can select the other options from the dropdown list, but the page does not update to display the selected number. It just keeps displaying 10.

This now seems to be working fine.

(was also working fine for me when i tested in FF, chrome, and safari)


HA does not restart due to alexa media player error

Describe the bug
Upgraded HA from 2021.11.5 to 2021.12.10 worked
Update AMP via HACS to x.x.15
Tried to restart HA but the restart was refused due to the error
Deleted Alexa component folder and reloaded via HACS
Restart still refused due to the same error
rolled back to 2021.11.5 - everythings fine.
To Reproduce
Steps to reproduce the behavior:
See  description above
System details

Home-assistant (version): 2021.11.5
Hassio (Yes/No): Yes
alexa_media  (version from const.py or HA startup):
alexapy (version from pip show alexapy or HA startup): 3.10.12
Amazon 2FA is enabled (y/n). We will not debug login issues if unanswered: yes

Logs
Logger: homeassistant.components.websocket_api.http.connection
Source: custom_components/alexa_media/__init__.py:16
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 09:49:49 (3 occurrences)
Last logged: 09:55:58

[281472370983696] function() argument 'code' must be code, not str
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 185, in handle_call_service
    await hass.services.async_call(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1495, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1530, in _execute_service
    await handler.job.target(service_call)
  File "/usr/src/homeassistant/homeassistant/components/hassio/__init__.py", line 586, in async_handle_core_service
    errors = await conf_util.async_check_ha_config_file(hass)
  File "/usr/src/homeassistant/homeassistant/config.py", line 938, in async_check_ha_config_file
    res = await check_config.async_check_ha_config_file(hass)
  File "/usr/src/homeassistant/homeassistant/helpers/check_config.py", line 218, in async_check_ha_config_file
    platform = p_integration.get_platform(domain)
  File "/usr/src/homeassistant/homeassistant/loader.py", line 530, in get_platform
    cache[full_name] = self._import_platform(platform_name)
  File "/usr/src/homeassistant/homeassistant/loader.py", line 535, in _import_platform
    return importlib.import_module(f"{self.pkg_path}.{platform_name}")
  File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 972, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 850, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/config/custom_components/alexa_media/__init__.py", line 16, in <module>
    from alexapy import (
  File "/usr/local/lib/python3.9/site-packages/alexapy/__init__.py", line 16, in <module>
    from .alexaapi import AlexaAPI
  File "/usr/local/lib/python3.9/site-packages/alexapy/alexaapi.py", line 21, in <module>
    from alexapy.aiohttp import ClientConnectionError, ClientResponse
  File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/__init__.py", line 6, in <module>
    from .client import (
  File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/client.py", line 35, in <module>
    from . import hdrs, http, payload
  File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/http.py", line 7, in <module>
    from .http_parser import (
  File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/http_parser.py", line 15, in <module>
    from .helpers import NO_EXTENSIONS, BaseTimerContext
  File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/helpers.py", line 667, in <module>
    class CeilTimeout(async_timeout.timeout):
TypeError: function() argument 'code' must be code, not str

Additional context
Add any other context about the problem here.

You need to use 3.10.15. The error is caused by trying to use 3.10.12 code with HA 2021.12. Please update. Make sure you've cleaned out the old files.

sorry, but I did update to 3.10.15.
and I deleted the old files (folder)
HA refused to restart

@alandtse Sorry Alan, but I have to be a little annoying because I would like to update before the 2022.02.x comes out.
What did I wrong when i approach as follows?

update HA
directly go to Hacs and update AMP to 3.10.15
Then try to restart - doesn't work
Delete amp component folder and reload amp via HACS
Try to restart

Shall I delete the folder before updating the amp the first time?

Your method isn't working. Remove the integration first. Then upgrade. Then reinstall.
In truth a failing component should not stop a HA start so you have something else wrong you may need to resolve.

But doesn't removing the complete integration lead to other problems when upgrading HA without amp?
I have tons of yaml code related to amp entities (reading out reminders and timers, music, tts notifications etc)

So you'll have some broken automations until you install it again. Again, the problem is your system doesn't start when a custom component breaks, which isn't how HA should be. That's fundamentally going to cause you many issues moving forward because HA likes to break custom components.
There's nothing else I can do for you here. 3.10.15 doesn't work for 2021.11. Even force upgrading AMP first won't help if it means your HA won't start. Your only hope based on what you've described is to start without AMP and then install it after.

That sounds like some work for me.😕
Thank you alandtse.

FYI - did it like recommended. Worked without issue. Thanks again.

Great to hear. Hopefully you also figured out or figure out soon why a broken component stops your HA from starting.

Yes, interesting thing I have to dig in. I have no single issue so far except an uncought error appearing in the browser console which tells me that a component could not be initialized because it's already there.
But I definitely haven't declared any front end component twice. But OK,I will look into that tomorrow.


Publish CF template for AMI mapping

It would be convenient for the README for RancherOS to link to a prebuilt CloudFormation 'mapping' of regions to AMI id.

@jhmartin This is a great idea.  We will look into doing this.


v3:  scope not properly reflected in (type|java)scriptreact

In v2 the scope updates when moving around between JSX elements.  In v3 with the configuration in the GIF, the scope does not update.  You can see that it does update correctly within the class/methods, so not sure if something is up with that case in particular.
The example below is for a super minimal config I tested with, but I have also confirmed in my full configuration.  I swear at one point I saw it actually work correctly with the same v3 setup, but I can't replicate that now.

Let me know if you need any more info!
Thank you :)

I think this is a bug in nvim-treesitter :thinking:
It starts working when you make a change to the buffer.
ident-blankline just uses what is returned from nvim-treesitter containing_scope.
I will look into the nvim-treesitter code and see if I can figure it out.
https://github.com/lukas-reineke/indent-blankline.nvim/assets/12900252/c9a41c7e-6676-479f-9b10-21b88634eca4

Hmm, interesting.  I'm not sure if v2 is handling this differently somehow, but it seems to work without modification.  Also what you did above doesn't seem to fix it for me in my regular config, though it does in my stripped out config.  The setup is the same though.  I guess maybe something else I have is conflicting with that somehow.

I'm not sure if v2 is handling this differently somehow

v2 by default was doing something different, but I don't want to support that anymore. nvim-treesitters scope is objectively a lot better, as long as it works :sweat_smile:.
I'll find some time next week to try to debug it.

Totally understand.  Thank you so much for digging into this!

I looked more into this and discovered that there was a bunch of stuff broken.
Most importantly for this issue, nvim-treesitters caching was too aggressive. That's why it sometimes worked and sometimes didn't. Sometimes the cache matched the buffer, but sometimes it didn't.
I tried to fix the caching, but that caused way too many updates, which was too slow. I ended up changing how this works completely.
I pushed a new version that should work. And it should also be a lot faster.

Wow this works great!  Thank you


Don't ignore Debug profile on MSVC

Fixes #19
@alexcrichton Do you remember why you added this check?
I tested building cargo with this change and it seems to work fine.

Trying to remember what's going on here, my guess is that the debug profile linked with /MDd or /MTd, the debug versions of the MSVC runtimes. Rust, however, currently links with either /MD or /MT which can cause incompatibilities.
I'm pretty sure this'll break some projects, but if it works for Cargo that at least means a good number should continue to work. In that sense I'm curious to see what the breakage is here, and we can always back it out if there's too much breakage!

 Anyway, since cargo is statically linked that explains why cargo just works with this change. IIUC there would only ever be a problem when dynamically linking multiple build artifacts. In those cases however you'd want finer-grained control over what CRT is used anyway.


Update use as node module example

In my testing, I found the example given for using slack-irc as a node module is incorrect.
index.js exports one property (default) that points to _helpers.createBots

Awkward, thanks for noticing. This must have broken when I upgraded to babel 6, ages ago. I added babel-plugin-add-module-exports though, which should make it possible to do require('slack-irc')(config).
Please test with version 3.8.6 when you get time :)


Getting error No named parameter with the name 'dragDevices' with latest version 0.1.2

I am getting below error while running flutter application.
lib/flutter_image_slideshow.dart:123:15: Error: No named parameter with the name 'dragDevices'.
As I checked latest library code, dragDevices parameter is not defined in PageView.builder, but it is mentioned in flutter_image_slideshow.dart.
Kindly resolve the issue.

This is for Android

@ritsat
Your SDK version is outdated.
You need to run flutter upgrade or use version 0.1.2 of this package.


Added Falco to microk8s community addons

Thank you for making MicroK8s better
Please reference the issue this PR is fixing, or provide a description of the problem addressed.
Also verify you have:

[X] Read the contributions page.
[X] Submitted the CLA form, if you are a first time contributor.

I am adding Falco (https://falco.org/) which is a CNCF Incubating Project for runtime threat detection/security of Kubernetes to the community addons for microk8s. I mirrored the Trivy add-on for inspiration (also Helm-based) so this should work the same as that existing one.

Thank you for this PR @jasonumiker. We will review it soon, in the next few weeks.

@jasonumiker, the CLA check is failing with:
Checking the following users on Launchpad:
-<EMAIL_ADDRESS>✕ (has no Launchpad account)

The email on the commit should match the one used in the CLA and the LP account. When did you sign the CLA? Maybe it needs some time for everything to sync.
One more question, are you submitting this on behalf of sysdig or as an individual? If sysdig is supporting this work we should include you in our partnership program.

I was doing it personally (the<EMAIL_ADDRESS>but my git must have been misconfigured with my other GitHub login and put that on the commit? I am open to doing it as Sysdig instead - not sure how much more is involved with the partner program if we do it that way...

I'll re-do it on a machine that only has my personal GitHub on it to be sure for now...
I'll open a new one from that shortly...


fix(install): mopidy for spotify install

Follow up of https://github.com/MiczFlor/RPi-Jukebox-RFID/pull/1789/files fixing the issue also for the spotify install

Thanks for the additional PR.
This change would also be necessary in: scripts/installscripts/buster-install-default-with-autohotspot.sh

Thanks for the additional PR.
This change would also be necessary in: scripts/installscripts/buster-install-default-with-autohotspot.sh

@s-martin added it to the other script as well


destroy method

Is it possible to destroy the instance - or a way to reinit it?

@b0gd4n Reinitialise by calling the function returned by autosizeInput:
const foo = autosizeInput(document.querySelector('#foo'))

// ...

foo()

what I am trying to achieve with this is make it responde to screen resizing - I have a breakpoint which makes the font-size for the input smaller for mobile. That means that the initial width calculated by the placeholder will be smaller - so I need to reinit it at that point
const foo = autosizeInput(document.querySelector('#search'));
calling foo() inside a resize function doesn't fix this.

This would also be useful for removing the ghost element and removing event binding that may turn into memory leaks. What would be a good api for this?
I could implement when I have time, but what would be the preferred API? We could have autosizeInput return an object with multiple functions e.g.:
return { set, destroy };

The module returns a destroy method as of 1.0.0


[interactive] Fix #17740: az interactive fails with progress_patch() got an unexpected keyword argument 'det'

This checklist is used to make sure that common guidelines for a pull request are followed.
Fix https://github.com/Azure/azure-cli/issues/17740
As progress_patch() will raise exception when specifying det=xx, we change progress_patch() to accept key-value pairs.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

aks

Good work. 🚢

Why are chances reverted?

Why are chances reverted?

rebase main branch to make sure correct incremental test detection. Otherwise, there will be some test failures.

You didn't pull before rebasing, causing changes from code review to be lost.

code review (d67a86d)

Thanks for the check. Add back now.


Release alpha version for 3.0 alphas

With proper feature plugin support

I want use in feature plugin but show an error:
Attribute value must be constant
and i can't use it

I faced the error mentioned in this issue 963.
I am now using a forked version of the repo.
The main changes are:

the modification of the gradle distribution url
the update of the androidPlugin
the addition of one line to generate R2 in feature module

I don't see the error mentioned in the issue #963 anymore but it still doesn't assemble.
The error I see is
error: cannot find symbol
import com.elodieferrais.myapp.R2;
symbol: class R2
location: package com.elodieferrais.myapp

What I don't understand is that I see the R2 file being generated but for some reason the java class doesn't pick it up...
Like it has been generated but too late maybe... ¯_(ツ)_/¯
I created a sample app where I reproduced the error: https://github.com/elodieferrais/ButterknifeSample
The title and comment of this ticket seemed to be similar to the problem I am facing, did you create it to fix an issue like this one?

I added all the dependencies but there were errors
Error:(2,0) Cannot add extension with name "buildOutputs" ,as there is an extension already registered with that name
I use AS3.0 canary 4

AS 3.0 Canary 5
Butterknife 8.7.0
Caused by: java.lang.NoSuchMethodError: com.android.build.gradle.api.BaseVariant.getOutputs()Ljava/util/List;
        at butterknife.plugin.ButterKnifePlugin$applyPlugin$1.execute(ButterKnifePlugin.kt:27)
        at butterknife.plugin.ButterKnifePlugin$applyPlugin$1.execute(ButterKnifePlugin.kt:15)
        at org.gradle.internal.ImmutableActionSet$CompositeSet.execute(ImmutableActionSet.java:196)
        at org.gradle.internal.MutableActionSet.execute(MutableActionSet.java:35)
        at org.gradle.api.internal.DefaultDomainObjectCollection.doAdd(DefaultDomainObjectCollection.java:204)
        at org.gradle.api.internal.DefaultDomainObjectCollection.add(DefaultDomainObjectCollection.java:198)
        at com.android.build.gradle.LibraryExtension.addVariant(LibraryExtension.java:70)
        at com.android.build.gradle.FeatureExtension.addVariant(FeatureExtension.java:80)
        at com.android.build.gradle.internal.ApiObjectFactory.create(ApiObjectFactory.java:137)
        at com.android.build.gradle.BasePlugin.lambda$createAndroidTasks$8(BasePlugin.java:625)
        at com.android.builder.profile.ThreadRecorder.record(ThreadRecorder.java:81)
        at com.android.build.gradle.BasePlugin.createAndroidTasks(BasePlugin.java:610)
        at com.android.build.gradle.BasePlugin.lambda$null$6(BasePlugin.java:537)
        at com.android.builder.profile.ThreadRecorder.record(ThreadRecorder.java:81)
        at com.android.build.gradle.BasePlugin.lambda$createTasks$7(BasePlugin.java:533)
        at org.gradle.internal.event.BroadcastDispatch$ActionInvocationHandler.dispatch(BroadcastDispatch.java:91)
        at org.gradle.internal.event.BroadcastDispatch$ActionInvocationHandler.dispatch(BroadcastDispatch.java:80)
        at org.gradle.internal.event.AbstractBroadcastDispatch.dispatch(AbstractBroadcastDispatch.java:42)
        at org.gradle.internal.event.BroadcastDispatch$SingletonDispatch.dispatch(BroadcastDispatch.java:230)
        at org.gradle.internal.event.BroadcastDispatch$SingletonDispatch.dispatch(BroadcastDispatch.java:149)
        at org.gradle.internal.event.AbstractBroadcastDispatch.dispatch(AbstractBroadcastDispatch.java:58)
        ... 90 more

@Yuliya-Kaleda The stacktrace you posted is related to the issue 963 I believe.

@elodieferrais it is. You added a link from 963  to this issue. So I am posting here to inform that feature plugin is not fully supported.

use 8.5.1 can work it.

@JakeWharton You can close this now as you have 9.0.0-SNAPSHOT released.

Is support for "api" and "implementation" separation to replace "compile" within scope of this request?
https://docs.gradle.org/current/userguide/java_library_plugin.html#sec:java_library_separation

Since AS 3.0 becomes stable, when migrating our project to AS 3.0, can we use 9.0.0-SNAPSHOT in production, is it stable enough? If not, can we have a stable mid version before 9.0.0 release. Thanks

This issue is resolved with the release of 9.0.0-rc1.


v3.4.0 Eevee crash

Issue reported by @waltage80 on the release discussion.
blender_debug_output.txt
blender_system_info.txt
bug.crash.txt

@waltage80, based on your last comment from the discussion page i suspect that the cause of this crash is the "Limit Size" option "Preferences -> Viewport -> Textures" as mentioned it this bug: https://developer.blender.org/T103075 from Blender's bug tracker.
Since you have reset your preferences, can you try turning that option on and see if it causes the crash ?

YES!!! this option is causes the crash of Eevee!

OK. In this case the Blender developers are aware of it, and it will probably be fixed for v3.4.1.

Are you sure that BF know about this?

Yes, the link to the bug report is in the second message of this issue.

3.4.1 do not solve this problem
why they release this?

I am not part of the Blender dev team. Please ask your question on their bug tracker (the report for this issue is at the link in the second comment).

thank you


More info in logs

Please provide a bit of context about how users would benefit from this change and why this is logged as info rather than debug log entry.

They will benefit by seeing changes in the logs. It is as info to be visible even if user not enable debug mode - In debug there are rather errors and these are informations.


Fix errors in mutex debugging (#1235)

Store the lock owner thread rather than m_locked, so that multiple threads
accessing the same mutex do not give false positives, but recursive locks on
the same thread are still caught.

Match the std::mutex API: return bool from try_lock() and remove locked().
No code is using this, but any new code that did would only build in either
release or debug configuration.

@brechtvl let us know if you need help resolving the CLA issue.

The CLA issue should be resolved now.

Apologies for the late reply, I lost of track of this pull request.


List v2020-06-05 release in readme

Overview

[x] Added v2020-06-05 release to readme (forgot previously)

Comments

bors r+


892 implement simple lct model

Changes and Information
Please briefly list the changes (main added features, changed items, or corrected bugs) made:

Added simple version of the lct secir model with related example and test.

If need be, add additional information and what the reviewer should look out for in particular:

Most important file is model.cpp
simulation.h is comparable to memilio/compartments/simulation.h, see also #914.

Merge Request - Guideline Checklist
Please check our git workflow. Use the draft feature if the Pull Request is not yet ready to review.
Checks by code author

[x] Every addressed issue is linked (use the "Closes #ISSUE" keyword below)
[x] New code adheres to coding guidelines
[ ] No large data files have been added (files should in sum not exceed 100 KB, avoid PDFs, Word docs, etc.)
[x] Tests are added for new functionality and a local test run was successful
[x] Appropriate documentation for new functionality has been added (Doxygen in the code and Markdown files if necessary)
[x] Proper attention to licenses, especially no new third-party software with conflicting license has been added
[ ] (For ABM development) Checked benchmark results and ran and posted a local test above from before and after development to ensure performance is monitored.

Checks by code reviewer(s)

[ ] Corresponding issue(s) is/are linked and addressed
[ ] Code is clean of development artifacts (no deactivated or commented code lines, no debugging printouts, etc.)
[ ] Appropriate unit tests have been added, CI passes, code coverage and performance is acceptable (did not decrease)
[ ] No large data files added in the whole history of commits(files should in sum not exceed 100 KB, avoid PDFs, Word docs, etc.)
[ ] On merge, add 2-5 lines with the changes (main added features, changed items, or corrected bugs) to the merge-commit-message. This can be taken from the briefly-list-the-changes above (best case) or the separate commit messages (worst case).

Closes #892.

@mknaranja I think this PR can lead to issues with PR #894. Do we wait until this is merged?

@HenrZu @lenaploetzke We should advance both pull requests with review (and adaptations) at the same time and for the one to be merged later we should combine forces to not put to much on the shoulder of the persons who comes second ;)


Add support for org.apache.calcite:calcite-core:1.35.0

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

No.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Add support for org.apache.calcite:calcite-core:1.35.0.
The relevant JSON entry is available at https://github.com/apache/shardingsphere/tree/0397f829d60b47cd57b255a4f48132d627e7b10c/infra/reachability-metadata/src/main/resources/META-INF/native-image/org.apache.calcite/calcite-core/1.35.0 .

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Null.

Additional context
Add any other context or screenshots about the feature request here.

Refer to https://github.com/apache/shardingsphere/issues/29052 .

I'm working on this issue.


Skip attribute should apply to attributes

e.g, https://github.com/rust-lang-nursery/rustfmt/issues/1987#issuecomment-330995380

Hi.  I started to look at this as an issue to dip into.  As far as I can tell #[rustfmt_skip] does apply to attributes (at the same time as the item the attributes apply to).  For example, running rustfmt over:
#[cfg(
"foo")]
fn
main() {}

turns into:
#[cfg("foo")]
fn main() {}

But adding the skip attribute:
#[rustfmt_skip]
#[cfg(
"foo")]
fn
main() {}

causes rustfmt not to change anything.  (Apparently the #[rustfmt_skip] can come after the other attribute).
Should it be doing something different?

Ah, right, no skipping does not (yet) skip the width check.
We just need a test to close this issue.


Setup request timeouts + check connect timeouts

Closes #4220

Frontend tests were OK :+1: (details)

@rafatower CR please

:+1:


Send message in channel when locking via API

When I lock via the API, I would like to see a message posted in the channel to indicate I've locked a resource. At the moment this just happens with no visibility to other users.

Not ideal but in the meantime users can use /locks to see what is currently locked, including when locked via the API

If a team has fully integrated their CI pipeline with Lockbot they might not actually want to be notified so this behaviour should be configurable.


Does ATQ work with tensor parallelism?

I've been using atq.INT4_AWQ_CFG and observing a performance drop when quantizing a Llama 70B model with tensor parallelism withatq.quantize(model, quant_cfg, forward_loop=calibrate_loop).
Quantization works well through HuggingFace using pipeline parallelism though.
Is this a feature or a bug? Do we expect performance drops when using tensor parallelism with ATQ?

Can you share command lines to reproduce the issue, please? And tell us your hardware configuration. Thanks!

do u still have further issue or question now? If not, we'll close it soon.


Clarify PlaceholderField usage

We should document that a PlaceholderField only creates the placeholder when the object it's
attached to is saved.
This means if the placeholder field is added to a model that had existing objects, all those objects
need to be resaved for the CMS to create the necessary placeholders.
Source https://github.com/divio/django-cms/issues/4265

As placeholder field is deprecated in V4 closing this for now.

As placeholder field is deprecated in V4 closing this for now.

Where I can read about new in v4 and deprecations?

@useHTML5 v4 is still heavily in the development phase with no fully agreed approach to a community release just yet. We are however currently trying to clean the codebase and Github for the 3.x release stream. To keep up to date you may find the following information useful. :-)
If you want to learn more about the work of the technical committee, our product vision and how you can become a member of the dCA, you can find all information here:

The Technical Committee of the django CMS Association
Technical Roadmap and Product Vision for django CMS
How to become a member of the django CMS Association

We are looking forward to every companion who would like to shape the future of django CMS together with us!
If you have any questions, feel free to reach out to Nicolai, our Community Manager<EMAIL_ADDRESS>Sign up for the Association now!


Normalize Events in State

Atm events and counterparts are nested. This could be the source of bugs. It would be better to store them normalized, i.e. as flat map with hasCorrespondingRemoteMessage as URI that can be used up to query the map again.

events are not saved in the state anymore -> close


Support "Comment with Line Comment" code action

Please support using the "Comment with Line Comment" code action (i.e. ⌘/ on a Mac), and the similar Block action.  This is helpful when editing to quickly enable/disable blocks of DSL.  Currently one needs to place comments manually on each line.
The Structurizr DSL Comments support both C-style and shell-style comments, so perhaps a setting and/or auto-detection of currently used style (first seen?).

Hi, thanks again for your feedback 😃. The linked PR adds basic support for the "Comment with line/block comment" actions. Currently, it will always use // as the line comment prefix.


Backwards Compatibility for Autocomplete Component

Due to changes in accessibility functionality many custom autocomplete components will lose hover effect.

In v0.43.0 release.


Mastodon feed articles have no titles at all

Newsboat version:
Newsboat 2.33.0
System: Linux 6.5.5-hardened1-1-hardened (x86_64)
Compiler: g++ 13.2.1 20230801
ncurses: ncurses 6.4.20230520 (compiled with 6.4)
libcurl: libcurl/8.3.0 OpenSSL/3.1.3 zlib/1.3 brotli/1.1.0 zstd/1.5.5 libidn2/2.3.4 libpsl/0.21.2 (+libidn2/2.3.4) libssh2/1.11.0 nghttp2/1.56.0 (compiled with 8.3.0)
SQLite: 3.43.1 (compiled with 3.43.1)
libxml2: compiled with 2.11.5

Config file:
Doesn't matter, but here is one it happens with anyway:
urls-source "ocnews"
ocnews-url ***
ocnews-login ***
ocnews-password ***

Steps to reproduce the issue:

Subscribe to a mastodon feed (e. g<EMAIL_ADDRESS>via nextcloud news.
Retrieve nextcloud news via newsboat

Other info you think is relevant:
Probably related: #2530 #2531
No Errors in log, just:
[2023-10-07 11:34:24] INFO: Reloader::reload: parsing feed
[2023-10-07 11:34:24] INFO: RssParser::parse: added article title = `' link = `https://social.tchncs.de/@kuketzblog/111192088490735640' ign = 0x74b83a27cda0

I can reproduce this, and git bisect indeed points to https://github.com/newsboat/newsboat/commit/9b386432d903c92d9b100879154ca96867a48ff1.
It looks like the item descriptions from nextcloud (and the other external APIs) are placed in the RssItem::content_encoded field instead of the RssItem::description.
That field is currently ignored when trying to create a fallback title.


add_picture fails to dead with pictures in header

When using a template that has an image in the header. You add a picture it produces a document with an error that word will offer to fix. The fix involves renumbering the picture boxes document wide. It appears add_picture does not check the header before choosing the picture box number.

Please send an example document, before and after. Also, what version are you using?

I am using 0.8.6 with a recent install of Anaconda Python 2.7 and Word 2013. In the attached zip is:

The script used to create the problem (word_equations.py)
The files used as the template (test_input.docx)
The file output from the script (test_output.docx)
The file words generates when it fixes the file (test_output_fixed.docx)

header_pic_issue.zip

Hmm, the file test_output.docx is loading just fine on my side. I'm running Mac Word 2011.
What do you mean when you say 'fix involves renumbering the pictures boxes'? I'm not aware of any picture boxes per se and what numbering they might have.
Is there a specific message or diagnostic information given when it doesn't load for you?
I see that the document is more complicated than most I've run across in that it includes a glossary (like a second embedded document) and some embedded XML for a bibliography or something. If you don't need that, you might try creating a new template document from scratch with your header and stuff in there, avoiding copying and pasting in Word itself (so just building it up item by item, inserting the picture in the header, trying it every so often to see what makes it fail or if it doesn't). If that works, that might be the quickest path to a fix for you :)

I think the best quick fix falls in the category of "Why didn't I try that sooner?" I took the output that caused the error, allowed word to fix it, deleted the new content added by python and used that as the template and the result is in a clean file. So that is the fix I'll be using.
Thanks for the help! This is a great library I'm looking forward to using it more. In the interest of documenting the problem in case it helps with a more robust engine my debugging results are below:
I redid the document from a scratch using the built in word 2013 template and style. I added the letter head furniture clean without any copy and paste to make as clean a file as possible, it should not be a complicated document from a user standpoint. It appears that the addition of the word art vertical lines is the addition that breaks things. Using empty1.docx has the problem as before, empty1_nolines.docx does not. I also added the error box to the archive but it is not very useful.
What I meant by 'fix involves renumbering picture boxes' is that when I compared the header2.xml files between the broken and fixed word files in the original upload (using https://www.corefiling.com/opensource/xmldiff.html) the differences all looked like:
> -               <wp:docPr id='1' name='Text Box 1' />
> +               <wp:docPr id='3' name='Text Box 3' />

However in the later versions of the error this was not repeated so I withdraw that assertion.
empty1_output.zip

Glad you got it working @iohazard :)


Improve the successor market docs

Feature overview
One of the market makers returned the issue with successor market documentation. I think it would be good to write it ASAP:
> Hello, I am a bit confused by the successor market docs. I don't see the necessary fields in the examples
> Am I blind or are they missing?
> Also is it the same process for Perps? The decimals on the LINK market are a bit silly so I'm going to propose we close it and re-open it using the successor feature
> https://docs.vega.xyz/mainnet/tutorials/proposals/new-successor-market-proposal
> Also when we make a proposal for a successor market while the parent is active does this mean that the protocol duplicates our LP commitments or will thye automatically be withdrawn from the parent market at enactment time of the successor market?

Tasks
A checklist of the tasks that are needed to document the requested topic fully.

[ ] Test current documentation
[x] Update docs
[x] Make sure we create successor market on one of our internal docs

@daniel1302 thanks for reporting this, it's now fixed. The fields were there in the past, but I removed them in another change by mistake. My fault, sorry for the confusion.


update changelog

What current issue(s) does this address, or what feature is it adding?
How did you solve this problem?
How did you make sure your solution works?
Are there any special changes in the code that we should be aware of?
Please check the following, if applicable:

[ ] Did you add any tests?
[ ] Did you run make lint?
[ ] Did you run make test?
[ ] Are you making a PR to a feature branch or development rather than master?
[ ] Did you add an entry to CHANGELOG.rst? (if not, please do)

Coverage remained the same at 79.447% when pulling c60c9cc8170d63bea99c69c1e835036e0999bfa5 on HandsomeJeff:patch-2 into 311df80dc1d6cc3f2d61b0aab43591b479886a6e on CityOfZion:master.

Could you push this change to the branch of your existing PR? Thanks!


The method 'listenable' is not defined for the class 'Box'

Whenever I try to access listenable method, I get the error The method 'listenable' is not defined for the class 'Box'.
Hive.box('diary').listenable()
My Hive Versions
hive: 1.4.1
hive_flutter: 0.3.0+2
hive_generator: 0.7.0+2

You need to import 'package:hive_flutter/hive_flutter.dart'.

Thank you. It worked.


denali publish command fails

denali publish
cli v0.0.17 [local]  | denali v0.0.37 [local]

✔ Addon built
✔ Tests passed
✖ Publish failed
NestedError: "publish" command failed
    at Function.<anonymous> (./seawatts/denali-jwt/node_modules/denali-cli/lib/command.ts:89:13)
    at Generator.throw (<anonymous>)
    at rejected (./seawatts/denali-jwt/node_modules/tslib/tslib.js:94:69)
    at <anonymous>
Caused By: Error: Command failed: npm publish
npm WARN prepublish-on-install As of npm@5, `prepublish` scripts are deprecated.
npm WARN prepublish-on-install Use `prepare` for build steps and `prepublishOnly` for upload-only.
npm WARN prepublish-on-install See the deprecation note in `npm help scripts` for more information.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>prepublish: `in-publish && echo "Use 'denali publish' instead." && exit 1 || not-in-publish`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepublish script.

This looks like an issue in your repo:
npm ERR<EMAIL_ADDRESS>prepublish: `in-publish && echo "Use 'denali publish' instead." && exit 1 || not-in-publish`

Looks like you are using a recent denali, but still have the old prepublish hook in your package.json.
tl;dr:

Replace the "prepublish" hook with a "prepublishOnly": "npm run build" and make sure your build script is denali build
Remove in-publish from your project

Longer explanation:
The old prepublish script was placed in the addon blueprint to ensure that publishing would always fail. Then the old build script, when it copied the package.json into dist, actually removed that hook. So basically, it was setup to block publishing from the root dir by accident, and instead force you to rely on denali publish, which would build and then publish from dist, as was needed under the old build system, pre main-dir
Now, with main-dir, we don't need to publish from a different folder, so the publish command changed - it no longer does the whole "remove the hook from package.json and publish from dist". It just builds and publishes - that's it.

Closing since I'm pretty sure this is an issue in the consuming project. But feel free to leave a comment if you find otherwise and I'll happily reopen

Sounds great! I'll check when I get home
On Wed, Oct 4, 2017 at 9:03 AM Dave Wasmer<EMAIL_ADDRESS>wrote:

Closing since I'm pretty sure this is an issue in the consuming project.
But feel free to leave a comment if you find otherwise and I'll happily
reopen
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/denali-js/denali/issues/400#issuecomment-334205536,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACDIwnS__R2oR-a7-X2Q1ogeMsDnrdCgks5so6xagaJpZM4PtDzf
.


Windows Setup: Add additional metadata to inno_updater.exe

Type: Bug
The file is missing ProductName and Version in the signature.
This blocks usage of the updater by Applocker rules, when only signed executables with ProductName are allowed to run.
For Inno_Updater this is what I have now:
Publisher          : O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US\\,<IP_ADDRESS>
Hash               : SHA256 0x7CBB990B9373F31A9135B72DAD8C6176E245299C7902A78F9FD71C7329CCDFDE

While for code.exe ProductName and Version are present:
Publisher  : O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US\VISUAL STUDIO CODE\ELECTRON.EXE,<IP_ADDRESS>
Hash       : SHA256 0x889F539FBDA59F7569A8E0A483EC2EC51056B266415352C082A60BB7B74D87D4

VS Code version: Code 1.73.1<PHONE_NUMBER>f055b99068d3688932416f2346dd3b, 2022-11-09T04:27:29.066Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz (8 x 1498)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
31.60GB (12.59GB free)

Process Argv
--crash-reporter-id 96107d8f-e7b4-45bd-8a2d-dd44bcb5f0d4

Screen Reader
no

VM
0%

This was once open as https://github.com/microsoft/vscode/issues/106721

This also effects other binaries, like CODE-TUNNEL.EXE
Path       : %PROGRAMFILES%\MICROSOFT VS CODE\BIN\CODE-TUNNEL.EXE
Publisher  : O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US\\,<IP_ADDRESS>

I think Windows Defender Application Control (WDAC) and AppLocker are becoming more and more relevant in the enterprise space. Support for signature-based application whitelisting should become a priority in this project.


Index [0] of grad tensor

Hi,
I am a little confused about taking only the zero index of gradient tensor in the penalty function:
gradients = autograd.grad(outputs=disc_interpolates, inputs=interpolates, grad_outputs=torch.ones(disc_interpolates.size()), create_graph=True, retain_graph=True, only_inputs=True)[0]
Why is it not possible to take the whole grad tensor ?
Best

because autograd.grad takes in a sequence(tuple) of tensors (w.r.t which the gradient of ouput have to be computed as inputs) the return is also a sequence(tuple) of gradient tensors w.r.t each input tensor in the sequence. Here, since you are differentiating only w.r.t one input tensor, you use the [0] th grad tensor from the sequence.

In fact, there is only one element in the tuple returned by the autograd.grad function, [0] just removes the tuple container and takes out the internal tensor information.
This is a reply from the author of the paper on the same question, and I want to help you.
https://github.com/igul222/improved_wgan_training/issues/34


endpoint: extract endpoint configuration update from regeneratePolicy

Decoupling policy updates from configuration updates allows for policy computation to be entirely separate from endpoint configuration. As a result, policy generation for an endpoint is now based only upon the endpoint's identity / set of labels in relation to the policy repository. This will make testing endpoint policy generation much easier in the future.
Signed-off by: Ian Vernon<EMAIL_ADDRESS>

This change is

test-me-please

test-me-please

test-me-please

test-me-please

Tests failed due to unused import that I didn't clean up in unit tests... trying again.

test-me-please

test-me-please

test-me-please

Re-testing. The build got scheduled on a bad node on Jenkins.

test-me-please

test-me-please

Prior build passed. Fixed comments and rebased against master; if passes, will merge.

test-me-please

Build failed due to infrastructural issues:
21:30:32 make[1]: go-bindata: Command not found
21:30:32 Makefile:54: recipe for target 'go-bindata' failed

Trying again.

test-me-please


In WebGL render image to canvas as part of fromPixels to match CPU.

This fixes https://github.com/tensorflow/tfjs/issues/1719.
This fixes https://github.com/tensorflow/tfjs/issues/1488.
MobileNet v2 shows no difference in inference time given this change compared to master.
To see the logs from the Cloud Build CI, please join either
our discussion
or announcement mailing list.

This change is

@dsmilkov sounds good - I've added a test.

@dsmilkov yep!


Events and Errors vs. goroutines

Hi,
The FAQ claims that Events and Errors must not be read from in the same goroutine.  Then the NewWatcher example goes ahead and does exactly that.
If the FAQ is correct, the example should be changed.  If the FAQ incorrect, it should be amended to reflect the current state of affairs.

The FAQ should be clarified.
It means that the main goroutine can't be used because it will block.

Ah, apparently I misread the FAQ.  I looked into the linked issue reports and the source of the problem isn't exactly clear.  Is the point that watcher.Add() might block indefinitely if nobody's reading from the Event/Error channels concurrently?

Not Add specifically, but the run loop that NewWatcher kicks off. I think it depends on the OS, whether or not the Kernel is blocking. It would be nice to handle all this better internally, but I haven't looked into it that deeply yet. :disappointed:


Add docs website

This adds a Nextra + Typescript + Next.js react web app to display documentation and moves our docs pages from /doc/ to /docs/pages (mostly in order to appease Nextra).

You can develop & test this website like so:
$ cd docs
$ npm i
$ npm run dev

and opening localhost:3000

Once this PR is merged, I'll deploy the site to Vercel and fix all the links + add a "Docs" link to exo.deref.io before making it available at another subdomain. I'm thinking exo-docs.deref.io @brandonbloom

Looking pretty good! A few quick comments:

kinda a bummer that the /docs directory had to have everything pushed down in to /docs/pages, but probably OK for now.
Instead of exo-docs.deref.io, is docs.exo.deref.io possible?
We should probably do a content pass before we deploy this. I'll block off some time early next week to make some tweaks to this branch for meta & the .md files.

Thanks!

@brandonbloom

docs.exo.deref.io

I'm not sure, I'd prefer that as well but I guess we'll see what Vercel can do. I'll try this first.

Yeah :/

3

Yep. There's still some remaining work to be done:

[ ] Favicon needs to be added
[ ] Links in the .md files need to be fixed such that they navigate between pages in this website. We might want a ...[page].md to ...[page] redirect, or just rewrite all the links with the assumption people view them on the docs site and not in the GitHub previews.
[ ] It seems like Nextra is automatically creating tables of content for subsection headings but the links for these appear broken. I mean, you'll get linked to .../page#subsection but the <h2>Subsection doesn't get an id attribute so it doesn't scroll for you.
[ ] Probably makes sense to import prismjs or something for syntax highlighting (I think Nextra has an easy example of this)

OK, keep at it. We'll sync Monday morning.

Also, after this is deployed, we should update the main exo.deref.io site to:

Add a "Docs" link (to the top right, across from the main logo?)
Update the e.g. install.md links in the landing page from pointing to the GitHub repo markdown preview to the docs website pages instead

I have no idea why page section headings aren't getting id attributes, as mentioned above.
I've looked into Nextra and SWR-site's own documentation websites and I see no relevant config difference which should cause their section headings to have proper id links but ours not to.

closing, since we decided on gitbook


Unable to use Hand Tracking Graph in different Scenes

Description
Hello Sir,
I wanted to use Hand Tracking Graph in two different Scenes in unity.
Can you please give me some Solution of how I can use Hand Tracking Graph in two different scenes !!

Try to explore the wiki
You can checkout #446 issue as well.