[WFCORE-1123]:  Recreate HttpPostMgmtOpsTestCase.testAddRemove

Reenabling the test using the logging subsystem.
Jira: https://issues.jboss.org/browse/WFCORE-1123

Looks good but needs a rebase.

Windows Build 3248 outcome was FAILURE using a merge of c771f6d6e558a4aa9d30746c4911c6d40ee6f6d3
Summary: Execution timeout (new); tests passed: 3063, ignored: 43 Build time: 01:00:14

Full integration - Windows Build 1306 outcome was FAILURE using a merge of c771f6d6e558a4aa9d30746c4911c6d40ee6f6d3
Summary: Tests failed: 6 (6 new), passed: 3312, ignored: 194 Build time: 01:01:49
Failed tests
org.jboss.as.test.clustering.cluster.web.CoarseWebFailoverTestCase(SYNC-tcp).testGracefulSimpleFailover: 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.ClusteredWebFailoverAbstractCase.establishTopology(ClusteredWebFailoverAbstractCase.java:256)
	at org.jboss.as.test.clustering.cluster.web.ClusteredWebFailoverAbstractCase.testFailover(ClusteredWebFailoverAbstractCase.java:171)
	at org.jboss.as.test.clustering.cluster.web.ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover(ClusteredWebFailoverAbstractCase.java:83)
------- Stdout: -------
18:47:27,934 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
18:47:27,934 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
18:47:27,934 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
18:47:27,947 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\9f\ad6d01816dc7a25ff1504e73b3335073b8655f\content
18:47:27,950 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "coarse-distributable.war" (runtime-name: "coarse-distributable.war")
18:47:27,975 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.coarse-distributable.war" is using a private module ("org.jboss.as.clustering.common:main") which may be changed or removed in future versions without notice.
18:47:27,975 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.coarse-distributable.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
18:47:27,975 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.coarse-distributable.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
18:47:27,981 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment coarse-distributable.war
18:47:27,990 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "coarse-distributable.war"' are as follows:

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

18:47:28,017 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 29) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:47:28,017 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 29) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:47:28,018 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:47:28,019 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:47:28,020 INFO  [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0006: Starting Services for CDI deployment: coarse-distributable.war
18:47:28,029 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0009: Starting weld service for deployment coarse-distributable.war
18:47:28,029 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 13) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:47:28,031 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 13) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:47:28,040 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 31) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:47:28,040 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 31) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:47:28,057 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 13) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:47:28,058 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 13) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:47:28,060 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29) WFLYCLINF0002: Started dist cache from ejb container
18:47:28,075 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 5) WFLYCLINF0002: Started client-mappings cache from ejb container
18:47:28,077 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 13) WFLYCLINF0002: Started coarse-distributable.war cache from web container
18:47:28,084 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) WFLYCLINF0002: Started routing cache from web container
18:47:28,247 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 31) WFLYUT0021: Registered web context: /coarse-distributable
18:47:28,268 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "coarse-distributable.war" (runtime-name : "coarse-distributable.war")
18:47:28,276 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
18:47:28,287 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\a7\4f3e3a262048f1eb3147312909ebeaca556e66\content
18:47:28,289 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "coarse-distributable.war" (runtime-name: "coarse-distributable.war")
18:47:28,313 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.coarse-distributable.war" is using a private module ("org.jboss.as.clustering.common:main") which may be changed or removed in future versions without notice.
18:47:28,313 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.coarse-distributable.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
18:47:28,313 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.coarse-distributable.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.

org.jboss.as.test.clustering.cluster.web.context.InvalidateConversationTestCase(SYNC-tcp).testInvalidate: 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.context.InvalidateConversationTestCase.establishTopology(InvalidateConversationTestCase.java:129)
	at org.jboss.as.test.clustering.cluster.web.context.InvalidateConversationTestCase.testInvalidate(InvalidateConversationTestCase.java:93)
------- Stdout: -------
18:47:53,987 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
18:47:53,987 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
18:47:53,988 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
18:47:53,988 INFO  [org.jboss.as.arquillian.protocol.jmx.ArquillianServiceDeployer] (main) Deploy arquillian service: arquillian-service: 981 assets
18:47:54,787 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\9f\cbe693386118b29cc84e8b5a4991d78c1343a0\content
18:47:54,791 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "arquillian-service" (runtime-name: "arquillian-service")
18:47:54,982 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.arquillian-service" is using a private module ("org.jboss.as.jmx:main") which may be changed or removed in future versions without notice.
18:47:54,982 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.arquillian-service" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
18:47:54,983 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.arquillian-service" is using a private module ("org.jboss.jandex:main") which may be changed or removed in future versions without notice.
18:47:54,983 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.arquillian-service" is using a private module ("org.wildfly.security.manager:main") which may be changed or removed in future versions without notice.
18:47:54,990 WARN  [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0013: Deployment deployment "arquillian-service" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations)
18:47:55,012 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "arquillian-service" (runtime-name : "arquillian-service")
18:47:55,094 WARN  [org.jboss.remotingjmx.Util] (main) The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'.
18:47:55,148 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\30\e7f84b076f508c5dd7041e89452ce0532fc30b\content
18:47:55,153 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "conversation.war" (runtime-name: "conversation.war")
18:47:55,182 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.conversation.war" is using a private module ("org.jboss.as.clustering.common:main") which may be changed or removed in future versions without notice.
18:47:55,182 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.conversation.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
18:47:55,182 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.conversation.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
18:47:55,182 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.conversation.war" is using a private module ("org.wildfly.security.manager:main") which may be changed or removed in future versions without notice.
18:47:55,189 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment conversation.war
18:47:55,194 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "conversation.war"' are as follows:

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

18:47:55,220 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 30) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:47:55,221 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 30) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:47:55,222 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0006: Starting Services for CDI deployment: conversation.war
18:47:55,229 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 10) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:47:55,229 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 10) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:47:55,229 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 30) WFLYCLINF0002: Started dist cache from ejb container
18:47:55,230 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0009: Starting weld service for deployment conversation.war
18:47:55,234 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 30) WFLYCLINF0002: Started client-mappings cache from ejb container
18:47:55,228 INFO  [org.jboss.as.arquillian] (MSC service thread 1-5) Arquillian deployment detected: ArquillianConfig[service=jboss.arquillian.config."conversation.war",unit=conversation.war,tests=[org.jboss.as.test.clustering.cluster.web.context.InvalidateConversationTestCase]]
18:47:55,238 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 10) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:47:55,239 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 10) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:47:55,240 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 30) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:47:55,242 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 30) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:47:55,247 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 30) WFLYCLINF0002: Started routing cache from web container

org.jboss.as.test.clustering.cluster.web.expiration.CoarseSessionExpirationTestCase(SYNC-tcp).test: java.lang.AssertionError: null
	at org.jboss.as.test.clustering.cluster.web.expiration.SessionExpirationTestCase.test(SessionExpirationTestCase.java:101)
------- Stdout: -------
18:48:11,274 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
18:48:11,274 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
18:48:11,274 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
18:48:11,293 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\c6\5945170af0725d2e7f1ffc8772212f1240b236\content
18:48:11,296 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
18:48:11,368 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 82) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,369 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 82) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,372 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 9) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,372 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 9) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,373 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 83) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,373 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 83) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,383 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 9) WFLYCLINF0002: Started routing cache from web container
18:48:11,389 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 83) WFLYCLINF0002: Started expiration.war cache from web container
18:48:11,404 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 83) WFLYUT0021: Registered web context: /expiration
18:48:11,417 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
18:48:11,422 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
18:48:11,434 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\c6\5945170af0725d2e7f1ffc8772212f1240b236\content
18:48:11,436 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
18:48:11,482 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 91) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,483 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 91) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,486 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 91) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,486 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 91) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,488 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 87) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,488 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 87) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,492 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 83) WFLYCLINF0002: Started routing cache from web container
18:48:11,495 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 87) WFLYCLINF0002: Started expiration.war cache from web container
18:48:11,507 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 87) WFLYUT0021: Registered web context: /expiration
18:48:11,517 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
18:48:11,552 INFO  [stdout] (default task-2) http://[::1]:8080/expiration/listener?operation=set&name=a;jsessionid=ZnUpJVxBXhG1yfzf1xoUTyHaSwCQTQX-MB_O8Ne7

18:48:11,575 INFO  [stdout] (default task-3) http://[::1]:8080/expiration/listener?operation=set&name=a&value=1;jsessionid=ZnUpJVxBXhG1yfzf1xoUTyHaSwCQTQX-MB_O8Ne7

18:48:11,586 INFO  [stdout] (default task-22) http://[::1]:8180/expiration/listener?operation=get&name=a;jsessionid=a7Ta73r1RWtCYY802uchWFJJn3Ad0nKYsb8rXQoo

18:48:11,591 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
18:48:11,591 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
18:48:11,591 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-0
18:48:11,596 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 9) WFLYUT0022: Unregistered web context: /expiration
18:48:11,606 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 9) ISPN000029: Passivating all entries to disk
18:48:11,626 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 9) ISPN000030: Passivated 3 entries in 21 milliseconds
18:48:11,630 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 9) WFLYCLINF0003: Stopped expiration.war cache from web container
18:48:11,635 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 9) WFLYCLINF0003: Stopped routing cache from web container
18:48:11,642 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment expiration.war (runtime-name: expiration.war) in 47ms
18:48:11,656 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0002: Content removed from location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\c6\5945170af0725d2e7f1ffc8772212f1240b236\content
18:48:11,656 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0009: Undeployed "expiration.war" (runtime-name: "expiration.war")
18:48:11,658 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-1
18:48:11,663 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 83) WFLYUT0022: Unregistered web context: /expiration
18:48:11,669 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 88) ISPN000029: Passivating all entries to disk

org.jboss.as.test.clustering.cluster.web.expiration.FineSessionExpirationTestCase(SYNC-tcp).test: java.lang.AssertionError: null
	at org.jboss.as.test.clustering.cluster.web.expiration.SessionExpirationTestCase.test(SessionExpirationTestCase.java:101)
------- Stdout: -------
18:48:11,711 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
18:48:11,711 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
18:48:11,712 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
18:48:11,722 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\69\d3c8e33a0c5fb32519dc86b40ca2af161f8c47\content
18:48:11,724 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
18:48:11,778 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 9) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,778 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 9) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,781 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 83) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,782 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,782 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,783 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 83) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,804 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 83) WFLYCLINF0002: Started routing cache from web container
18:48:11,808 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 5) WFLYCLINF0002: Started expiration.war cache from web container
18:48:11,833 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 5) WFLYUT0021: Registered web context: /expiration
18:48:11,852 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
18:48:11,859 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
18:48:11,880 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\69\d3c8e33a0c5fb32519dc86b40ca2af161f8c47\content
18:48:11,882 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
18:48:11,930 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 83) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,930 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 83) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,966 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 91) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,966 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 84) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,967 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 91) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,967 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 84) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:11,970 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 84) WFLYCLINF0002: Started routing cache from web container
18:48:11,980 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 91) WFLYCLINF0002: Started expiration.war cache from web container
18:48:11,990 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 91) WFLYUT0021: Registered web context: /expiration
18:48:12,002 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
18:48:12,032 INFO  [stdout] (default task-4) http://[::1]:8080/expiration/listener?operation=set&name=a;jsessionid=qRZ8rpAoYJv6lIT6sXE7vyCaaPSI8fstE_FCKNYs

18:48:12,040 INFO  [stdout] (default task-5) http://[::1]:8080/expiration/listener?operation=set&name=a&value=1;jsessionid=qRZ8rpAoYJv6lIT6sXE7vyCaaPSI8fstE_FCKNYs

18:48:12,048 INFO  [stdout] (default task-23) http://[::1]:8180/expiration/listener?operation=get&name=a;jsessionid=2RlUs-1uRHlOG5l4kF-_N7FIgPPwJofsQV3CCdw4

18:48:12,053 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
18:48:12,053 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
18:48:12,053 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-0
18:48:12,059 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 83) WFLYUT0022: Unregistered web context: /expiration
18:48:12,064 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 5) ISPN000029: Passivating all entries to disk
18:48:12,066 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 5) ISPN000030: Passivated 3 entries in 2 milliseconds
18:48:12,068 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 5) WFLYCLINF0003: Stopped expiration.war cache from web container
18:48:12,076 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 5) WFLYCLINF0003: Stopped routing cache from web container
18:48:12,082 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment expiration.war (runtime-name: expiration.war) in 24ms
18:48:12,094 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0002: Content removed from location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\69\d3c8e33a0c5fb32519dc86b40ca2af161f8c47\content
18:48:12,094 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0009: Undeployed "expiration.war" (runtime-name: "expiration.war")
18:48:12,095 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-1
18:48:12,100 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 84) WFLYUT0022: Unregistered web context: /expiration
18:48:12,109 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 84) ISPN000029: Passivating all entries to disk

org.jboss.as.test.clustering.cluster.web.ExternalizerTestCase(SYNC-tcp).test: java.lang.AssertionError: expected:<3> but was:<1>
	at org.jboss.as.test.clustering.cluster.web.ExternalizerTestCase.assertValue(ExternalizerTestCase.java:109)
	at org.jboss.as.test.clustering.cluster.web.ExternalizerTestCase.test(ExternalizerTestCase.java:97)
------- Stdout: -------
18:48:12,149 INFO  [org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase] (main) externalizer.war:
/WEB-INF/
/WEB-INF/classes/
/WEB-INF/classes/META-INF/
/WEB-INF/classes/META-INF/services/
/WEB-INF/classes/META-INF/services/org.wildfly.clustering.marshalling.Externalizer
/WEB-INF/classes/org/
/WEB-INF/classes/org/jboss/
/WEB-INF/classes/org/jboss/as/
/WEB-INF/classes/org/jboss/as/test/
/WEB-INF/classes/org/jboss/as/test/clustering/
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/web/
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/web/externalizer/
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/web/externalizer/Counter.class
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/web/externalizer/CounterServlet.class
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/web/externalizer/CounterExternalizer.class
/WEB-INF/web.xml
18:48:12,151 INFO  [org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase] (main) externalizer.war:
/WEB-INF/
/WEB-INF/classes/
/WEB-INF/classes/META-INF/
/WEB-INF/classes/META-INF/services/
/WEB-INF/classes/META-INF/services/org.wildfly.clustering.marshalling.Externalizer
/WEB-INF/classes/org/
/WEB-INF/classes/org/jboss/
/WEB-INF/classes/org/jboss/as/
/WEB-INF/classes/org/jboss/as/test/
/WEB-INF/classes/org/jboss/as/test/clustering/
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/web/
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/web/externalizer/
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/web/externalizer/Counter.class
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/web/externalizer/CounterServlet.class
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/web/externalizer/CounterExternalizer.class
/WEB-INF/web.xml
18:48:12,157 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
18:48:12,157 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
18:48:12,157 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
18:48:12,171 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\d6\5fccab3eca87d1f5fb2cfac28248d779fc6f85\content
18:48:12,173 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "externalizer.war" (runtime-name: "externalizer.war")
18:48:12,222 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:12,223 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:12,224 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:12,224 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:12,225 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 21) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:12,225 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 21) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.

org.jboss.as.test.clustering.cluster.web.GranularWebFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover: java.lang.AssertionError: expected:<200> but was:<500>
	at org.jboss.as.test.clustering.cluster.web.ClusteredWebFailoverAbstractCase.testFailover(ClusteredWebFailoverAbstractCase.java:117)
	at org.jboss.as.test.clustering.cluster.web.ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover(ClusteredWebFailoverAbstractCase.java:103)
------- Stdout: -------
18:48:12,576 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
18:48:12,576 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
18:48:12,576 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
18:48:12,588 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\7c\1d0dfbe1da5f7c655501ee068151352c9b741f\content
18:48:12,591 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "granular-distributable.war" (runtime-name: "granular-distributable.war")
18:48:12,612 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.granular-distributable.war" is using a private module ("org.jboss.as.clustering.common:main") which may be changed or removed in future versions without notice.
18:48:12,613 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.granular-distributable.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
18:48:12,613 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.granular-distributable.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
18:48:12,618 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment granular-distributable.war
18:48:12,624 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "granular-distributable.war"' are as follows:

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

18:48:12,652 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:12,652 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:12,653 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Starting Services for CDI deployment: granular-distributable.war
18:48:12,654 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 84) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:12,654 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 84) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:12,657 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 21) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:12,657 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 21) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:12,661 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 21) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:12,662 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 21) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:12,665 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 84) WFLYCLINF0002: Started client-mappings cache from ejb container
18:48:12,681 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 5) WFLYCLINF0002: Started dist cache from ejb container
18:48:12,685 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0009: Starting weld service for deployment granular-distributable.war
18:48:12,700 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 5) WFLYCLINF0002: Started routing cache from web container
18:48:12,716 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 84) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:12,717 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 84) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
18:48:12,734 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 84) WFLYCLINF0002: Started granular-distributable.war cache from web container
18:48:13,161 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 21) WFLYUT0021: Registered web context: /granular-distributable
18:48:13,175 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "granular-distributable.war" (runtime-name : "granular-distributable.war")
18:48:13,184 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
18:48:13,198 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location C:\BuildAgent\work\db872761b443af46\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\7c\1d0dfbe1da5f7c655501ee068151352c9b741f\content
18:48:13,202 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "granular-distributable.war" (runtime-name: "granular-distributable.war")
18:48:13,228 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.granular-distributable.war" is using a private module ("org.jboss.as.clustering.common:main") which may be changed or removed in future versions without notice.
18:48:13,229 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.granular-distributable.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
18:48:13,229 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.granular-distributable.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
18:48:13,233 INFO  [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment granular-distributable.war
18:48:13,238 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "granular-distributable.war"' are as follows:

	java:global/granular-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener

retest this please


test-branch/execute-job/wrong-comment-on-pr/f2f15dc9-6aa7-497e-a791-00cde8adaf37

PR for testing 6e29c1a6d8463df16a315202d5a9dc070ca4fb5d

comment 1


Make sure existing file path is used for metadata updates

This fixes instances identified in #3417 where updates to existing files in the metadata table were using the normalized path by mistake and not the existing path.

@keith-turner - This should fix the issues you identified in the other PR. Besides the fix MetadataTableUtil in finishSplit(), two spots in ManagerMetadataUtil will now use the overloaded putFile() method that takes a StoredTabletFile and uses getMetaUpdateDeleteText().
https://github.com/apache/accumulo/blob/969fc52f1c5e0c195a8cef800a87e0fab13cd89c/server/base/src/main/java/org/apache/accumulo/server/util/ManagerMetadataUtil.java#L97
https://github.com/apache/accumulo/blob/969fc52f1c5e0c195a8cef800a87e0fab13cd89c/server/base/src/main/java/org/apache/accumulo/server/util/ManagerMetadataUtil.java#L205
Do you think we should try and add the IT you were talking about as part of this or create a follow on?

Sunny IT tests passed and I kicked off a full IT build.
Also, I just had a thought that maybe as part of this PR (which only applies in the 2.1 branch where there is still an inheritance relationship) we should actually override https://github.com/apache/accumulo/blob/969fc52f1c5e0c195a8cef800a87e0fab13cd89c/core/src/main/java/org/apache/accumulo/core/metadata/TabletFile.java#L109 and https://github.com/apache/accumulo/blob/969fc52f1c5e0c195a8cef800a87e0fab13cd89c/core/src/main/java/org/apache/accumulo/core/metadata/TabletFile.java#L109
and either throw a new UnsupportedOperationException or return the metadataEntry (instead of the normalized path) so we prevent any errors in the future so the normalized path is never used. In #3417 this of course wouldn't be necessary anymore.

Full IT passed. As commented on #3435, this PR fixes the test there.


ENH: Consolidate and enhance documentation into the top level functions variants

Following the merge of pygeos into shapely there are many "almost duplicated" functions with similar or different documentation (typically one variant from pygeos and the other from shapely 1.8) also there is no unified docstring conventions and type annotations for most functions.
This issue is to discuss how to consolidate and enhance the documentation in that regard.
My ideas are as follows:

Put the full documentation of the functions in the top level functions (these usually work on array like), including parameters, return type and examples, for example shapely.constructive.snap (https://github.com/shapely/shapely/pull/1673). Move all relevant examples from other copies of the function, i.e. shapely.ops.snap (let's call these secondary functions).
On the docstrings  of the secondary functions (i.e. shapely.ops.snap) leave only a short description and pointer to the main function (i.e. shapely.constructive.snap)
Regards documentation, ignore the fact that sometimes the parameter names or order is different between the main and secondary functions (i.e. transform, https://github.com/shapely/shapely/pull/1676) because the user can see how the secondary parameters are mapped to the main function parameter, and also, usually it's just trivial.
Add proper type annotations to all the affected functions https://github.com/shapely/shapely/pull/1687
Decide on a unified docstring convention https://peps.python.org/pep-0257/  i.e. uniformed documentation of parameter names, types and return type in docstrings - I see that some Sphinx style is used but it's not the "regular style" as described here https://sphinx-rtd-tutorial.readthedocs.io/en/latest/docstrings.html, so for example, how do we describe the function return type ?
In case more clarification is needed, copying/adapting extra documentation and examples can be considered from other sources, like libgeos or PostGIS (example: https://github.com/shapely/shapely/pull/1673)
This will also avoid the need to update duplicated documentation, like in https://github.com/shapely/shapely/pull/1231

Related to:
https://github.com/shapely/shapely/pull/1402
https://github.com/shapely/shapely/issues/962
@jorisvandenbossche @mwtoews @sgillies @caspervdw
I have a fixed amount of time that I have to invest on this major documentation improvement project... So I really need your advise so I can get started and wouldn't waste my time on efforts that won't get accepted.
I thought to implement the ideas we discuss for some functions at a time and make a PR with one commit per function.
If anyone with writing permissions interested in helping with reviewing and merging the documentation PRs (as well as the related PRs I mentioned above) that would be super helpful, as I'm pretty stuck if they don't get feedback as I don't want to invest more time with consolidating and enhancing documentation for other functions if I'm not sure about what is likely to get accepted.
Related/Semi-related PRs that I would be happy if could get reviewed and merged before I dive in further into the documentation project:
https://github.com/shapely/shapely/pull/1687
https://github.com/shapely/shapely/pull/1682
https://github.com/shapely/shapely/pull/1681
https://github.com/shapely/shapely/pull/1673
https://github.com/shapely/shapely/pull/1676
https://github.com/shapely/shapely/pull/1231 (not my PR, but very long standing and could be helpful while I work on this issue)
Thanks and happy holidays 😃

The issue of (partially) duplicated docstrings was a significant issue regarding #1231 and #889 in my opinion, as important part of the documentation were not readily visible everywhere.
I'd say that a major issue at the moment is that manual.rst does not use automated generation tools and that it references object.method instead of of shapely.method.
I think that's the main hurdle to remove so we can simply redirect all other docstrings to the main shapely.method doc.

Just to mention what came out from another PR and does not seem to be mentioned here: I think it would be best to use
.. autosummary::

    shapely.predicates.function

to avoid duplicate docstrings thoughout manual.rst but this would also probably require some rewriting as manual currently refers to the BaseGeometry methods for the examples.


Implement Unit Tests

A unit test for each method is absolutely necessary!

Unit test covering all methods have been implemented. Can you make your request more clear?

What's the current code coverage of the unit tests implemented? Does it cover all LINQ methods?

I think they do

I'll close the ticket but it would be good to add how much coverage (%) is currently supported.


feat(admin): check cluster id in mrmanager

What this PR does
This PR adds codes to check cluster id in mrmanager. Because the admin server doesn't have explicit health checking, comparing cluster id is performed in ClusterMetadataViewer.
In the next PR, checking the replication factor will be added.

Current dependencies on/for this PR:

main

PR #553

PR #554

PR #555   👈

This comment was auto-generated by Graphite.

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.01% :tada:

Comparison is base (b3f894d) 61.07% compared to head (d01fafa) 61.09%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@                 Coverage Diff                  @@
##           mr_no_large_lock     #555      +/-   ##
====================================================
+ Coverage             61.07%   61.09%   +0.01%
====================================================
  Files                   143      143
  Lines                 19081    19082       +1
====================================================
+ Hits                  11654    11658       +4
+ Misses                 6847     6842       -5
- Partials                580      582       +2

Files Changed
Coverage Δ

tests/it/testenv.go
34.59% <100.00%> (+0.05%)
:arrow_up:

... and 8 files with indirect coverage changes

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

Merge Activity

Oct 4, 5:10 AM: @ijsong started a stack merge that includes this pull request via Graphite.


Merge v0.10.0-RC to main

Summary

This PR will be merged to main for the v0.10.0 Axom release.
It includes version updates and updated host-configs for new versions of TPLs .

Please approve this PR, but review https://github.com/LLNL/axom/pull/1421 which contains only the changes to develop that have not yet been merged.

Folks, this should be ready to merge for the release after https://github.com/LLNL/axom/pull/1424 is merged and those changes get pull in to this. Please review and check that release notes are correct and complete. Thank you.


Add IPAddress sealed value classes

Closes #231
Updates ProxyAddress to use new IPAddress sealed value class instead of a String. Binary compatibility maintained, but some things were deprecated in the migration.
This PR is a precursor to implementing #14 and #16 , as well as providing a TorDNS extension library in the future for simplifying torrification of HttpClients used by kmp-tor library consumers.

Added the blocked label until after #232 is completed and a minor version release can be put out.

Removing the blocked label, as #232 was modified to deprecate OnionUrl instead of fix + issue bug fix release.


114942119 add rake task that removes projects

Description

I created models for join tables in order to test whether records from those tables were destroyed.
Because I create those models I could replace 'has_and_belongs_to_many' with 'has_many :through'.
I ensured destroying following associations - 'project_owner' (if he doesn't have other projects), 'tokens', 'commit_fixes', 'commits', 'tickets' and join table 'commits_tickets', 'roles' and join table 'users_roles'.
I look for project inconsistencies - some commit fixing a commit from another project or a ticket with commits from different projects. I don't know if such a scenario is possible and if it is how to handle it, so for now I'm throwing an exception when it happens.
I added rake task to destroy projects with a given name (although there is a validation for unique project names in code, there is none in the database and some duplicates exist on production).
I wrote specs for testing that task.

Pivotal ticket:
https://www.pivotaltracker.com/story/show/114942119
Sign-offs:

[ ] @kamil89

I look for project inconsistencies - some commit fixing a commit from another project or a ticket with commits from different projects.

Hard to say if that can happen, what are reasons we need to add it? Did it happen in past or do you see any possibility to occur?
Overall PR looks good, I think we can delete some of tests, and make a few name changes.

@kamil89 I didn't find any validations for project consistency when it comes to tickets and commit fixes, so the scenarios I described could happen. I just think it's better to be safe than sorry. Destroying a project takes a bit longer because of those consistency checks, but I think speed isn't a priority here.

@konto-andrzeja fine, if you see a possibility those scenarios can occur then it's good to have them covered

Hmm, but then it would be better to check that constraints before commits are created (not deleted) right?

@kamil89 Right, but that would require another ticket. I think it's an edge case, so it's not important enough to work on, but if you want I can of course look into it.
Here I'm just covering a scenario in which project inconsistency already exists in database.

We should ensure consistency when records are created, can you add that change? hope it's not to much work, during deletion we can assume data are consistent.

@kamil89 I don't think we can, since even if I'll add checking project consistency when new records are created, the old ones won't be affected by that.
There's similar issue with project names. They must be unique, there's validation in code for that (https://github.com/netguru/review/blob/master/app/models/project.rb#L9), but apparently before it was added some duplicates were created (e.g. https://review.devguru.co/projects?query=benchify).

Imo still it makes more sense to have validations before records are created, so we prevent next issues. I guess we can not fix easily current data inconsistency, but before_destroy callbacks wont help here. Those data inconsistencies are out of the ticket scope however it's worth to mention them somewhere (eg pivotal ticket)

@kamil89 Well, before_destroy callbacks will at least rollback the whole destroying process, so no orphans will be created in database. I think if something like that happens it would have to be fixed manually anyway.
I'll add a new ticket for those validations.

Thanks @konto-andrzeja for story in pivotal. I think we are ready to go.


Custom type subclassed str used as type in a pydantic model's field becomes of type str instead of the custom type after the model is instantiated.

Initial Checks

[X] I have searched GitHub for a duplicate issue and I'm sure this is something new
[X] I have searched Google & StackOverflow for a solution and couldn't find anything
[X] I have read and followed the docs and still think this is a bug
[X] I am confident that the issue is with pydantic (not my code, or another library in the ecosystem like FastAPI or mypy)

Description
Custom type subclassed str used as type in a pydantic model's field becomes of type str instead of the custom type after the model is instantiated.
I have a custom type called EthereumAddress(str) which subclass the in-built str, it has comparison dunder-interface methods __ne__ and __eq__ implemented to compare if two EthereumAddress are the same (e.g. if the comparison is done between a str and an EthereumAddress, it is compared case-insensitively). Suppose a pydantic model uses EthereumAddress as one of its fields' type, once instantiated, an instance of the model will have this field of type str instead of type EthereumAddress.
This affects the usage of the pydantic model because if a field is annotated with a custom type, it is assumed that the value of the field of that instance of the pydantic model will have that custom type instead of some other type. E.g. the comparison between two str types and that of str and EthereumAddress are implemented different and would give different results.
Example Code
import pydantic

# implementation of `EthereumAddress`

class EthereumAddress(str):

    def __new__(cls, value: str) -> 'EthereumAddress':
        instance = super().__new__(cls, cls.validate_ethereum_address(value.lower()))
        return instance

    @classmethod
    def validate_ethereum_address(cls, v: str) -> str:
        if not v.startswith("0x") or len(v) != 42:
            raise ValueError('Invalid Ethereum address')
        return v

    @classmethod
    def __get_validators__(cls) -> 'CallableGenerator':
        yield cls.validate_ethereum_address

    def __eq__(self, other: object) -> bool:
        if isinstance(other, EthereumAddress):
            return str(self) == str(other)
        elif isinstance(other, str):
            return str(self) == other.lower()
        else:
            return False

    def __ne__(self, other: object) -> bool:
        if isinstance(other, EthereumAddress):
            return str(self) != str(other)
        elif isinstance(other, str):
            return str(self) != other.lower()
        else:
            return False

    def __repr__(self) -> str:
        return f'EthereumAddress("{self}")'

    def __str__(self) -> str:
        return super().__str__()

# codes that show comparison between `str` and `EthereumAddress` is done case-insensitively
# no assertion error raised
assert EthereumAddress('0xd6d88aa34dfba00efcfb564b95bbf20a9c8de545') == '0xD6d88aA34DfBA00efCfb564B95bbF20A9C8de545'

# pydantic model

class EthereumAccount(BaseModel):
    ethereum_address: EthereumAddress

# two `EthereumAccount`s are instantiated

acct = EthereumAccount(ethereum_address='0xd6d88aa34dfba00efcfb564b95bbf20a9c8de545')
acct_two = EthereumAccount(ethereum_address=EthereumAddress('0xd6d88aa34dfba00efcfb564b95bbf20a9c8de545'))

# look at their types of the field `ethereum_address`

type(acct.ethereum_address), type(acct_two.ethereum_address)

# ... (str, __main__.EthereumAddress)

# taking the field `ethereum_address` and compared it with a `str`
acct.ethereum_address == '0xD6d88aA34DfBA00efCfb564B95bbF20A9C8de545'
# False
acct_two.ethereum_address == '0xD6d88aA34DfBA00efCfb564B95bbF20A9C8de545'
# True

Python, Pydantic & OS Version
pydantic version: 1.10.4
            pydantic compiled: True
                 install path: C:\User\AppData\Local\Programs\Python\Python310\Lib\site-packages\pydantic
               python version: 3.10.6 (tags/v3.10.6:9c7b4bd, Aug  1 2022, 21:53:49) [MSC v.1932 64 bit (AMD64)]
                     platform: Windows-10-10.0.19044-SP0
     optional deps. installed: ['dotenv', 'email-validator', 'typing-extensions']

Affected Components

[ ] Compatibility between releases
[X] Data validation/parsing
[ ] Data serialization - .dict() and .json()
[ ] JSON Schema
[ ] Dataclasses
[ ] Model Config
[X] Field Types - adding or changing a particular data type
[ ] Function validation decorator
[ ] Generic Models
[ ] Other Model behaviour - construct(), pickling, private attributes, ORM mode
[ ] Plugins and integration with other tools - mypy, FastAPI, python-devtools, Hypothesis, VS Code, PyCharm, etc.

Hi, how is it going?

I don't understand, as shown in your code type(acct_two.ethereum_address) is EthereumAddress.
I've also run your code and found the same thing, so I'm not sure what the question is.
If you're wondering why acct.ethereum_address is a str, not a EthereumAddress, it's because your validate_ethereum_address method returns the raw input value, not necessarily an EthereumAddress

@samuelcolvin Thank you Samuel for replying and answering my question. Indeed, under validate_ethereum_address I should have returned cls(v), i.e. an instance of EthereumAddress instead of merely v.


repositories: exclude downstream from upstream

We don't want to give the impression we support building Fedora on RHEL or
CentOS Stream, or CentOS Stream on RHEL, so drop these repositories from
the package.
This pull request includes:

[x] adequate testing for the new functionality or fixed issue (this is about dropping untested/unsupported functionality)

cc @bcl

We also don't want to build RHEL 9 on RHEL 8 because of possible kernel issues.

I wonder where we should test this. Is pushing a blueprint enough, or do we have to start a compose?
(Also this needs an exception, do not merge until we have it.)

I suggest we add test/cases/cross-distro.sh, which only makes the call to enumerate the distros (using curl), and asserts that if we are on RHEL we only see RHEL, and if we are on RHEL8 we only see RHEL8.


Only apply refreshOrderedVariant() for basket items that are products

1. Why is this change necessary?
Let the situation be as follows: Your shop has enabled proportional tax calculation. You have a voucher that is restricted to a set of products. A customer has a cart with two products and said voucher. One of the products matches the voucher restriction and the other product does not. The products have different tax rates.
The voucher now is split into two different vouchers; one for each tax rate. The voucher with the tax rate of the matching product has a value below zero. The voucher with a tax rate of the non-matching product has a value of exactly zero, as it does not reduce the value of any line items in the cart.
Shopware would normally not notify the event product_stock_was_changed for line items that have a value below zero. So since vouchers typically have a value below zero, this event is not normally notified for vouchers. But in this specific case, we have a voucher in the cart that has a value of exactly zero, so this event does get notified.
Trying to change sales and instock of a voucher does not break anything, but it is wrong. The actual problematic part is the event notification for product_stock_was_changed. Third party plugin developers rely on this event to only be notified when an actual product stock was changed. If no data is found by the provided identifier, this could result in unexpected errors, since the scenario pictured above is kind of an edge case.
2. What does this change do, exactly?
Only execute the method refreshOrderedVariant when the basket item in question is actually a product. (modus = 0)
3. Describe each step to reproduce the issue or behaviour.
See 1.
4. Please link to the relevant issues (if any).
None.
5. Which documentation changes (if any) need to be made because of this PR?
None.
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

What about for example bundles? Those are products, value > 0 and modus 10
or premium products with modus 1?
Could that be a break?

@uehler Yes, that would break. The actual condition should be: is there an item in s_articles_details for the current $basketRow? Only then it would make sense to actually change sales and instock. Any idea on how to implement this? We cannot check, if $basketRow['ordernumber'] matches an item in s_articles_details because e.g. vouchers can have ordernumbers that already exist as variants. So how do we check it correctly?

Maybe you check, if modus is not one of voucher (2), rebate (3) and surcharge/discount (4)

Hey @jkrzefski,
thank you for your PullRequest! 💙
Could you please adds tests to your PR though?
Also, @uehler's suggestion sounds right.

@shopwareBot  Yes, i will change the condition and add a test case. Would it be sufficient to check if the event product_stock_was_changed is triggered or should I rather check if the method refreshOrderedVariant is executed?

@jkrzefski Do you think it would be possible to do both?

To be compatible with plugins, like the bundle plugin (and others), I would suggest to check for s_articles_details with the condition of the articleID and ordernumber column. Then it should be sure that the correct row is updated.

This PR was closed due to inactivity. If this change is still important to you, feel free to create a new pull request.
For more information about our contribution guidelines, see https://developers.shopware.com/contributing/contribution-guideline/.


Butcher.pythonpath

Issue number: #1
update to access base mapper via PYTHONPATH

Issue number: #1


Need a way to pass array of keys instead of one

@kalekseev do you have an example for an action that takes array arguments?

Maybe dump all the keys into one var and since they have delimiters anyway it'd be easy to split those inside of the action.

Have you tried putting multiple keys into the secret at once? Maybe ssh-add can handle that out of the box?

One secret can be 64K max: https://help.github.com/en/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets#limits-for-secrets.
I tried cat key1 key2 key3 | ssh-add - and it only added one key there. So I guess it doesn't support it out of the box.

Believe I'm also facing similar issue. Although, I'm no expert on SSH and how this process is working under the hood.
I have 3 private repos that are needed to build a project with. I had one of them configured and everything was working well. However, I can't reuse the key on the 2 remaining private repos since it's already in use as a Deploy Key.
Maybe I'm going about the SSH key approach wrong though 🤔 . Would being able to pass different secret keys fix this by being able to pull the remaining private repos? I'm looking into the machine user approach also which mentions ONE key being needed, however, I haven't tested that so I cannot confirm if that will work or not.

@mpdude alternative way to implement this would be to publish SSH agent socket and have end-users pass it as an input invoking this action multiple times in a row. The action would need to be changed to skip starting the new agent then.
@bradmartin a workaround for you would be to do something like "ssh-add - <<< ${{ secrets.YOUR_OTHER_KEY }}" manually.

Thank you for that @webknjaz - I will try that soon today 👍

@webknjaz Do you think 64KB is a limit of practical relevance?
Thinking about splitting the key/secret at some marker in JavaScript, then passing each one to the agent.

Please give #14 a try and leave a note over there if it works for you.

Do you think 64KB is a limit of practical relevance?

You can fit 16-18 4096-bit keys so yes, it's totally fine.

Thinking about splitting the key/secret at some marker in JavaScript, then passing each one to the agent.

No need. Each key starts with -----BEGIN OPENSSH PRIVATE KEY----- on a separate line and ends with -----END OPENSSH PRIVATE KEY----- on a separate line. So all you need to do is use these markers. Extra markers would only consume (waste) space in the var.

Please give #14 a try and leave a note over there if it works for you.

We've migrated away from using pre-defined keys recently so you'll have to wait for somebody else to test it. But I'll try to leave a code review there.

Yeah, my intention was to use -----BEGIN as the marker, see over at #14.

see over at #14.

Yep, already noticed

Implemented in #14.


chore(functions/slack): fix flaky API call

Fixes #6467

I don't see anything for the new keyword.
(I was trying to pick something that wouldn't result in ambiguity on the part of the KGSearch API.)


Demand update and cloning.

Demand fasade object has now two extra methods:

clone - for easy demand cloning
update - for off-chain properties update

Refactorings:

on-chain props object not required anymore to create a demand
demand object uses now strongly typed MarketLogic
MarketLogic now requires string based id property

Looks good, let's get this merged - want to reuse some of this code in https://github.com/energywebfoundation/origin/pull/28.


Trying to Restore Session but got Error 401 Unpaired with Cellphone

First, I scan QR Code, and generate keys.json and session.json. I change *.smile back to *.json.
Second, I restart my application, and try to restore session using already generated *.json file, got 401 Error.
When I use old version, I can use generated *.json.
After the code is updated, is there an error in the parameters I requested?

the library serializes its data as a gzip encoded smile file. It's not a JSON, and it's not even a decoded file. I have no idea what you are referring to


Add plugin functionality via django signals

Coverage increased (+0.03%) to 85.382% when pulling 9f74411690d39700df5b0cf0cf10d5aa4c86d749 on plugins into 5240db03a013e9691fa5b4111c1adb223e944dbe on master.

Not relevant anymore.


Add music

There should be a relaxed tune which plays during menus and the overworld.
There should be an upbeat tune which plays during puzzles.

Music should be continuous; no interruptions during scene transitions
Music should be loop seamlessly
Relaxed tune

Relaxed tune should play on the menus
Relaxed tune should play in the overworld
Relaxed tune should play before the start of a puzzle
Relaxed tune should play when the player first starts the game

Upbeat tune

Upbeat tune should play when the player starts a puzzle
Upbeat tune should stop when a puzzle ends; relaxed tune should fade back in

A few other nice-to-haves:

Music should start at a few predefined mid-song checkpoints, like what Super Hexagon does with its music.

On startup, it starts at the beginning of the song.
After that, it prioritizes parts of the song it hasn't played very much.

Puzzle tune startup should mesh well with the countdown beeps.

Maybe the beeps are too strong. We could use 808s, voices, or something more musical.
The BPMs should sync up. The lead-in should always be 2.5s, but it should count down from 8 if the BPM is very high, or 2 if the BPM is very low.

Added music and "checkpoint system". Checkpoints are just every 6 seconds, it feels OK. Maybe in the future we can do something fancier.


update tgi with text-generation-inference:2.1.0

Description
update tgi with text-generation-inference:2.1.0
Issues
https://github.com/opea-project/GenAIComps/issues/230
Type of change
List the type of change like below. Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would break existing design and interface)

Dependencies
List the newly introduced 3rd party dependency if exists.
Tests
Describe the tests that you ran to verify your changes.

@letonghan the test with Phi-3 failed, please check.

@letonghan the test with Phi-3 failed, please check.

It's mainly caused by the error below. The parameter --max-input-tokens should be smaller than the value of sliding_window=2047.


join command from docker swarm init

This is totally minor, but typically in the docs we include $ for commands to be run at the command line. IMO it would make sense to include this in the docker swarm join command output from docker swarm init
docker info
$ docker info
Containers: 8
 Running: 0
 Paused: 0
 Stopped: 8
Images: 7
Server Version: 1.12.0-rc4
Storage Driver: overlay
 Backing Filesystem: xfs
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge null overlay host
Swarm: active
 NodeID: elezuf7p02lkeci7ki23gbtca
 IsManager: Yes
 Managers: 1
 Nodes: 1
 CACertHash: sha256:19e3bd99c503953887d44ef1068c6cdcf7003fb68ddd44f3ea59a36d7a7f73f9
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 3.10.0-327.10.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 991.7 MiB
Name: manager1
ID: VVLS:3SXS:G7IZ:I6MG:DOQ6:VDI5:YWPO:E3XF:ZPMH:RP7C:RBAN:W2SG
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-ip6tables is disabled
Insecure Registries:
 <IP_ADDRESS>/8

current behavior
$ docker swarm init --listen-addr <IP_ADDRESS>:2377
No --secret provided. Generated random secret:
	667hkyum1xk74ynrmcb5nakjj

Swarm initialized: current node (elezuf7p02lkeci7ki23gbtca) is now a manager.

To add a worker to this swarm, run the following command:
	docker swarm join --secret 667hkyum1xk74ynrmcb5nakjj \
	--ca-hash sha256:19e3bd99c503953887d44ef1068c6cdcf7003fb68ddd44f3ea59a36d7a7f73f9 \
	<IP_ADDRESS>:2377

suggested behavior
$ docker swarm init --listen-addr <IP_ADDRESS>:2377
No --secret provided. Generated random secret:
	667hkyum1xk74ynrmcb5nakjj

Swarm initialized: current node (elezuf7p02lkeci7ki23gbtca) is now a manager.

To add a worker to this swarm, run the following command:
	$ docker swarm join --secret 667hkyum1xk74ynrmcb5nakjj \
	--ca-hash sha256:19e3bd99c503953887d44ef1068c6cdcf7003fb68ddd44f3ea59a36d7a7f73f9 \
	<IP_ADDRESS>:2377

I like $  a lot for docs, but to me including this in command output seems likely to result in accidentally copying and pasting that portion accidentally.  Precedent on Machine was that we didn't include it FWIW.
$ docker-machine env manager
export DOCKER_TLS_VERIFY="1"
export DOCKER_HOST="tcp://<IP_ADDRESS>:2376"
export DOCKER_CERT_PATH="/Users/nathanleclaire/.docker/machine/machines/manager"
export DOCKER_MACHINE_NAME="manager"
# Run this command to configure your shell:
# eval $(/usr/local/bin/docker-machine env manager)

The $ is used to indicate the shell prompt, I agree that adding it, likely will lead to copy paste errors

SGTM


pass frame via socket

This  was the beginning of a larger scope project to integrate with cameras run through SBCs. This is not something that it seems people have interest in, so forget about this goal in this project.


ios region is city, should be state

Contacts from IOS return the city in the region property. Should be returning state/region in the region property.
RCTContacts.m line 193 should be
NSString* region = postalAddress.state;
instead of
NSString* region = postalAddress.city;

+1 I'm experiencing the same issue. Thanks for the temp solution John!


CI: Updated module version 0.0.8 -> 0.0.9

ref:
https://github.com/terraform-redhat/terraform-aws-rosa-sts/tree/v0.0.9

/lgtm


standardize value in total paid

At present, our Vault operates on a generic basis, where both deposit and withdrawal functions accept assets as parameters. We need to refine and establish clear rules regarding:

The criteria or conditions for tokens when making a deposit.
The options available to professionals during withdrawal. Specifically, should they be allowed to claim their payment in any token that the vault currently holds? Or should they only be able to withdraw the specific token that was used for the payment by the company in their agreement?

@danicuki

use correctAmount to update totalPaid according to different stablecoin decimals


[SMALLFIX] Cleanup TODOs in worker module on exception handling

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/5998/
Test PASSed.

LGTM +1

LGTM. Thanks for the cleanup.


MissingPluginException

Hi again,
I'm trying to use RTCPeerConnection,
var peerConnection = RTCPeerConnection("{'iceServers': []}");
problem is, just add this line show an error message on flutter :
Another exception was thrown: MissingPluginException(No implementation found for method listen on channel cloudwebrtc.com/WebRTC/peerConnectoinEvent{'iceServers': []})
Anything wrong?

Hi,  you need use createPeerConnection  method  for rtc_peerconnection_factory.dart,  because Peerconnection needs to be created from the native layer, it needs asynchronous mode.
like this:
Map<String, dynamic> configuration = {
      "iceServers": [ {"url": "stun:stun.l.google.com:19302"}, ]
    };
    final Map<String, dynamic> constraints = {
      "mandatory": {},
      "optional": [ {"DtlsSrtpKeyAgreement": false}, ],
    };

var peerConnection =
      await createPeerConnection(configuration, constraints);

Is there any documentation using webrtc on flutter/native?
Because it's different from webrtc on web. I'm trying to check if my peerconncetion is onIceCandidate
stream() async{
    Map<String,dynamic> configuration = {
      "iceServers" : []
    };

    final Map<String, dynamic> constraints = {
      "mandatory": {},
      "optional": [ {"DtlsSrtpKeyAgreement": false}, ],
    };

    peerConnection = await createPeerConnection(configuration, constraints);
    print('ok');
    peerConnection.onIceCandidate = gotIceCandidate;
    peerConnection.onIceConnectionState = onIceState;
  }

  void gotIceCandidate(RTCIceCandidate iceCandidate){
    if (iceCandidate.candidate != null){
      print("onIceCandidate");
    }
 }

  void onIceState(RTCIceConnectionState iceConnectionState){
    if (iceConnectionState.index == 3){//CONNECTED
      print("connected");
    }else if(iceConnectionState.index == 5){//FAILED
      print("failed");
    }
  }

After connecting, I can do peerConnection.onTrack on web, but there is no onTrack on this library?

There are some differences between the API dart and the web. You can refer to https://github.com/cloudwebrtc/flutter-webrtc-demo first, and the API documentation will be added later.
The dart version of onTrack API looks like this:
typedef void AddTrackCallback(MediaStream stream, MediaStreamTrack track);
typedef void RemoveTrackCallback(MediaStream stream, MediaStreamTrack track);
....
class RTCPeerConnection {
...
  AddTrackCallback onAddTrack;
  RemoveTrackCallback onRemoveTrack;

Use in code:
pc.onAddTrack = (track) {
     //
};

pc.onRemoveTrack = (track) {
     //
};

You can refer to the code in flutter-webrtc-demo. The example can be P2P video call.
flutter-webrtc-demo://lib/src/call_sample/signaling.dart

Hi, Thanks for the answer. I have tried the demo.
But still stack on finding a way to get the EventHandler on PeerConnection.
In web, you can use onTrack to handle event like this, when server give a video/audio, the event will awake and activate it.
private remoteAudio: HTMLAudioElement;
private remoteVideo: HTMLVideoElement;

this.peerConnection.ontrack = (event) => { this.gotRemoteTrack(event) };

gotRemoteTrack(event) {
        switch (event.track.kind) {
            case "video":
                this.remoteVideo.srcObject = event.streams[0];
                break;
            case "audio":
                this.remoteAudio.srcObject = event.streams[0];
                break;
        }
    }

Is RTCVideoRenderer srcObject is MediaStream? I actually do not need a MediaStream because I'm not creating a p2p video call, I just want to stream live through server.

Hi, in the flutter version, RTCVideoRenderer is only used to display video stream, AudioTrack is played in the native layer, you can only get a track object in the dart layer to mute / unmute audio stream.

So, in order to video stream, I need to getUserMedia?
Future<MediaStream> createStream() async {
    final Map<String, dynamic> mediaConstraints = {
      'audio': true,
      'video': {
        'mandatory': {
          'minWidth':
              '640', // Provide your own width, height and frame rate here
          'minHeight': '480',
          'minFrameRate': '30',
        },
        'facingMode': 'user',
        'optional': [],
      }
    };

    MediaStream stream = await navigator.getUserMedia(mediaConstraints);
    if(this.onLocalStream != null){
      this.onLocalStream(stream);
    }
    return stream;
  }

What is facingMode and optional?

Could you give a demo/example to streaming video from server with this plugin?

The next time we update demo, we add an example of how flutter-webrtc interacts with SFU servers. But now, you can handle it on pc.onAddTrack.

I/libjingle(32252): (channel.cc:2033): Setting remote video description
I/libjingle(32252): (webrtcvideoengine.cc:721): SetSendParameters: {codecs: [VideoCodec[97:H264]], extensions: [], max_bandwidth_bps: -1, }
I/libjingle(32252): (webrtcvideoengine.cc:556): Internally supported codecs: {VideoCodec[0:VP8], VideoCodec[0:VP9], VideoCodec[0:red], VideoCodec[0:ulpfec]}
I/libjingle(32252): (webrtcvideoengine.cc:568): Codecs supported by the external encoder factory: {}
E/libjingle(32252): (webrtcvideoengine.cc:665): No video codecs supported.
E/libjingle(32252): (webrtcsession.cc:350): Failed to set remote offer sdp: Session error code: ERROR_CONTENT. Session error description: Failed to set remote video description send parameters..

I got no video codecs supported. What video codec is RTCVideoRenderer support? Is same as this?

WebRTC supports VP8/VP9 by default, and if some devices support H264 HW codec, you can check if your device supports H264 HW.

Is it testable in Emulator? or need a real device?

You need a real device.


IAuthenticationSchemeProvider needs a TryAddScheme()

Looking at this example/test to dynamically add authentication schemes at runtime:
https://github.com/aspnet/Security/blob/0959c941b40086b131b1e01d304fc23bb887fdc8/test/Microsoft.AspNetCore.Authentication.Test/DynamicSchemeTests.cs#L137-L143
If the endpoint is invoked twice, it will result in an InvalidOperationException:
https://github.com/aspnet/HttpAbstractions/blob/dev/src/Microsoft.AspNetCore.Authentication.Core/AuthenticationSchemeProvider.cs#L121
Instead perhaps this method should be bool TryAddScheme(AuthenticationScheme scheme) so users don't have to wrap it in a try-catch.
Also it appears that the underlying _map should be a ConcurrentDictionary?

Re-opening based on offline discussion:
Extra small. It would be one new overload of this method that doesn’t throw:
https://github.com/aspnet/HttpAbstractions/blob/bc7092a32b1943c7f17439e419d3f66cd94ce9bd/src/Microsoft.AspNetCore.Authentication.Core/AuthenticationSchemeProvider.cs#L136-L156
We might want to wait for C# 8 default interface implementations though (later in 3.0).

We have default interface members so we believe this is non-breaking now.

Issues with dim still, moving to preview 8

Glad to see this happening :)

Contingency plan if we can't get DIM working (having some issues) is to punt to 3.1.

We're going to punt on DIM changes due to the limitations (VB support, crossgen issues). Let's move TryAddScheme out to 3.1.

crossgen dim works now in master, still doesn't work in release/3.1, so the fix looks good for 5.0 at least

Added in https://github.com/aspnet/AspNetCore/pull/14448


Fix the roadmap link in the Roadmap section

The roadmap link need to be fixed to redirect at correct page.

Thanks for pointing out the issue, I have made a PR. It will solve the wrong link issue.


vcard photo

Is it possible to attach photo to vcard?
I tryed
vcard = VCardigan.create
vcard.photo File.binread("1.jpg")
vcard.photo "TYPE=JPEG;ENCODING=b:" + Base64.encode64(File.binread("1.jpg"))
but unsuccessful

I just hit this today while attempting to programmatically add images to some vcards:
Base64.encode64 won't work as that has line breaks every so often which causes VCardigan to think you're attaching multiple broken images (as it thinks the photo is an array of text). Instead, use Base64.strict_encode64, which works fine.
Example:
photo = Base64.strict_encode64(some_file)
vcard.photo photo, {:type => 'jpeg', :'ENCODING' => 'b'}

For anyone else running into issues this worked for me:
encoded_string = Base64.strict_encode64(File.open("icon.gif", "rb").read)
vcard.photo encoded_string, {:type => 'image/gif', :'ENCODING' => 'b'}


Add entity proxies

Coverage remained the same at 100.0% when pulling 2b6e510cb43eff6b55c561782277795702d14755 on DASPRiD:feature/entity-proxies into aa9875d1988eaaf1415a74db92a0f3595cec5875 on soliantconsulting:develop.

Coverage remained the same at 100.0% when pulling ac2faf88da7b375d389d4d1409c0a0759a740ba3 on DASPRiD:feature/entity-proxies into aa9875d1988eaaf1415a74db92a0f3595cec5875 on soliantconsulting:develop.


Signup, account creation, in-app purchase

Let's create a system where user can create account instantly with in-app purchase. We can have some boost packages that will fund account with delegation or SP when they purchase something via in-app.
@esteemapp/core, we need to review this and make sure we know all details:
https://medium.com/@dooboolab/react-native-in-app-purchase-121622d26b67
Of course we will have free signup process as well and we can have Topup feature where you can top up account with steem and sp via in-app purchase

related #920


refactor: replace asyncDependenciesBlockId with Identifier

Summary
Replace asyncDependenciesBlockId with Identifier, this can be good for incremental build.
When Modifying a module we will check if its dependencies change, this include static imports(module identifiers) and dyn imports(async dependencies Id), using identifier for asyncDependenciesId can make sure it's the same for every build if not changed.

Require Documentation?

No

!canary

!canary


How to bypass the latest cloudflare hunman verify?

Verify latest release

[X] I verified that the issue exists in the latest chatgpt release

Verify webapp is working

[X] I verify that the ChatGPT webapp is working properly for this account.

Environment details
win10
node v18.13
Describe the Bug

I still based on your v3 branch, which is Browser-based solution，i just want to know how to by pass the human verify, nopecha seems not working... In addition，capacity check seems not working too

Nopecha has a corresponding solution but I don't know how to integrate it into the code. It's really embarrassing. https://developers.nopecha.com/token/turnstile/

See also my answer in #341
I do not plan on continuing to support v3, but the new ChatGPTUnofficialProxyAPI should fulfill most needs since it's free and uses the real ChatGPT – and is much lighter-weight than the previous full browser solution.


Release Trustfall v0.4.0-beta.0 to test the new APIs.

The new query optimization APIs are here! I'm still working on documenting them properly but I wanted to release this beta to get some real-world testing and make the migration easier for Trustfall users, since there are some (extremely-minor) breaking changes for libraries that use Adapter directly i.e. not via BasicAdapter.
@ginger51011 I'm not sure if your use case could benefit from additional query optimizations, but if it can, I'd love to get you as an early adopter and do a user test of the APIs and the docs!

@ginger51011 I'm not sure if your use case could benefit from additional query optimizations, but if it can, I'd love to get you as an early adopter and do a user test of the APIs and the docs!

Ooh very nice! I'm in a bit of a crunch, trying to analyze data from my project to decide the next step, but I think I can see a use case (although optimizations for me rely heavily on other things). I'll see if I can find some time over Easter, but no promises!
I was thinking that in my use-case, I have a spine of the graph from the beginning. Would query hints help me with providing this data to Trustfall early, or am I interpreting them the wrong way?
Great work!

Can you tell me more about what you mean by "spine of the graph" here?
Query hints are meant to prevent situations like e.g. listing all neighbors of a vertex and then applying a property filter that discards nearly all of them. They allow the adapter to check for the existence of the filter before resolving the edge, so it doesn't have to bother to load vertices that will be discarded right away anyway.

Aah I see, yes that does make a lot of sense yes. Come to think of it, I don't think I really understand in what order a graph is resolved. I mean yeah it starts at the root, but I suppose trustfall then goes through the graph calling the adapter methods when it wants to know things about a vertex? But what steps are taken for each vertex?
In this case this might be interesting for me; I have some very expensive operations I might want to filter away early.
I think you answered it but my first idea was "OK these vertecies will be evaluated no matter what, so we can just give them to trustfall in the beginning to optimize", but I don't think that applies here (more than as perhaps being able to give good hints).
I'll try to get time to read the docs to figure out more!

I don't think I really understand in what order a graph is resolved.

Currently, everything happens in order as written: top to bottom, left to right, except @output which generally only happen at the end after all other processing is complete. Use cases that need to affect this can include an IR->IR transform to change the execution order.

"OK these vertecies will be evaluated no matter what, so we can just give them to trustfall in the beginning to optimize"

Would love to hear more, either on a call or Zulip or something if that's easier. At the very least this is info that would be useful in the hints, if not outright being able to lead to a "smarter" adapter that does more of the work earlier.

I've started writing some more docs, you can see some of the progress on this pre-release: https://docs.rs/trustfall/0.4.0-beta.2/trustfall/provider/index.html
One thing I'm struggling with: if you were looking for optimization-related docs, where would you look? Where would you expect to find them? All the answers I've come up with so far have been unsatisfying.

Also, I would particularly value feedback about the naming and documentation of the methods on this trait, which is central to the new optimization capabilities I'm adding: https://docs.rs/trustfall/0.4.0-beta.2/trustfall/provider/trait.VertexInfo.html


Introduce ProviderOption and small cleanup

Details
Some small changes

Introduce ProviderOption interface and update both API and sidecar provider initializations to take options

Add URLOption as an option to override API URL for API provider mode

Remove API key requirement from sidecar provider
Mark some variables as private

Neat, is it go-way to do optional arguments :) ? LG, but I have one question (see comment on the diff).

I think so, yeah it's kind of a cool way of (hopefully) doing things in a canonically Go way. Since Go doesn't have optional parameters, default values, or overloading, this kind of option handling is a clean way of allowing users to not have to pass in nil for empty args or something like that.


 Trying to convert a GOG Y7 save to steam. I keep getting unrecognized argument error for:
rgg_save_tool-windows.exe [--to-steam] [-g {y7_gog}] input_file.sav [output_file.sav].
What am I doing wrong?

you dont need to use the --to-steam option actually! I should clarify that in the readme/args. You just need to load your save with the tool into a json, and back into steam


feat(vehicle_adaptor): add pacakge structure without implementation

Description
WIP
Related links
Parent Issue:

Link

How was this PR tested?
Notes for reviewers
None.
Interface changes
None.

Effects on system behavior
None.

move to https://github.com/autowarefoundation/autoware.universe/pull/8782


Make openai.proxy  configurable for individual request.

Describe the feature or improvement you're requesting
Currently openai.proxy is a global  variable for every OpenAI request, but we have multiple  deployments with different settings like api_type, api_base etc.
Everything is configurable now except proxy. 😢
Additional context
No response

This is fixed in our upcoming v1 beta as you can configure the proxy on a per request basis by instantiating a new client with a different proxy or using the .with_options method!
import httpx
from openai import OpenAI

client = OpenAI(
    http_client=httpx.Client(
        proxies="http://my.test.proxy.example.com/",
    ),
)

# or per-request
with httpx.Client(proxies="http://my.other.proxy.example.com/") as http_client:
  client.with_options(http_client=http_client).chat.completions.create(...)


Upgrade to Node 20 & Upgrade npm packages

Update all pre-commit configs to be in sync with package.json updates
stylelint-config-prettier is no longer required as of Stylelint15
Turn off some new rules that are not required in the existing code
Update Eslint ecmaversion to something closer to real world browser support
Add fix:css npm script for easier Stylelint updates
Add nvmrc for easier FNM/NVM usage
Closes #462

Updated with a few recent package updates since this was created.


Communication plan: Generate a spreadsheet/list of Nuxeo collections currently published in Calisphere

To do once https://github.com/ucldc/rikolti/issues/349 is complete