WFLY-6437 Undertow listener max-post-size attribute default value dis…

…crepancy

Linux Build 9678 outcome was FAILURE using a merge of ab83148008fc0282af23536f7a0895a4030f4f04
Summary: Tests failed: 1 (1 new), passed: 3317, ignored: 194 Build time: 00:59:20
Failed tests
org.jboss.as.test.integration.ejb.stateful.passivation.PassivationTestCase.testPassivationMaxSize: javax.ejb.NoSuchEJBException: WFLYEJB0168: Could not find EJB with id UnknownSessionID [5648704955655348505265655266705056656570676548535651495770675170]
	at org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:61)
	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275)
	at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:327)
	at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239)
	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:79)
	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43)
	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:44)
	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66)
	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
	at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636)
	at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61)
	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
	at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)
	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
	at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195)
	at org.jboss.as.ejb3.remote.LocalEjbReceiver.processInvocation(LocalEjbReceiver.java:257)
	at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:184)
	at org.jboss.ejb.client.EJBObjectInterceptor.handleInvocation(EJBObjectInterceptor.java:58)
	at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
	at org.jboss.ejb.client.EJBHomeInterceptor.handleInvocation(EJBHomeInterceptor.java:83)
	at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
	at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42)
	at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
	at org.jboss.as.test.integration.ejb.remote.client.api.interceptor.SimpleEJBClientInterceptor.handleInvocation(SimpleEJBClientInterceptor.java:48)
	at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
	at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:138)
	at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
	at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
	at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
	at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)

Windows Build 4701 outcome was FAILURE using a merge of ab83148008fc0282af23536f7a0895a4030f4f04
Summary: Tests failed: 7 (7 new), passed: 3311, ignored: 194 Build time: 01:01:20
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: -------
00:57:47,509 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
00:57:47,509 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
00:57:47,509 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
00:57:47,504 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0002: Content removed from location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\91\bbd7c669babafb0eea43ab1dee74dc406545c6\content
00:57:47,504 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0009: Undeployed "coarse-distributable.war" (runtime-name: "coarse-distributable.war")
00:57:47,520 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\91\bbd7c669babafb0eea43ab1dee74dc406545c6\content
00:57:47,522 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "coarse-distributable.war" (runtime-name: "coarse-distributable.war")
00:57:47,548 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) 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.
00:57:47,548 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) 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.
00:57:47,548 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) 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.
00:57:47,553 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment coarse-distributable.war
00:57:47,559 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

00:57:47,585 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0006: Starting Services for CDI deployment: coarse-distributable.war
00:57:47,602 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 35) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:57:47,602 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 35) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:57:47,604 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 8) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:57:47,604 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 8) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:57:47,604 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 32) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:57:47,605 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 32) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:57:47,609 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 8) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:57:47,619 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0009: Starting weld service for deployment coarse-distributable.war
00:57:47,623 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 8) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:57:47,626 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 20) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:57:47,627 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 20) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:57:47,626 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) WFLYCLINF0002: Started client-mappings cache from ejb container
00:57:47,648 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 8) WFLYCLINF0002: Started routing cache from web container
00:57:47,649 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) WFLYCLINF0002: Started coarse-distributable.war cache from web container
00:57:47,656 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) WFLYCLINF0002: Started dist cache from ejb container
00:57:47,795 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 35) WFLYUT0021: Registered web context: /coarse-distributable
00:57:47,807 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "coarse-distributable.war" (runtime-name : "coarse-distributable.war")
00:57:47,815 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
00:57:47,825 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\91\bbd7c669babafb0eea43ab1dee74dc406545c6\content
00:57:47,829 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "coarse-distributable.war" (runtime-name: "coarse-distributable.war")
00:57:47,852 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) 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.

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: -------
00:58:13,497 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
00:58:13,498 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
00:58:13,498 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
00:58:13,499 INFO  [org.jboss.as.arquillian.protocol.jmx.ArquillianServiceDeployer] (main) Deploy arquillian service: arquillian-service: 981 assets
00:58:14,228 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\57\960110e5968e2e1ff5ab7486da4cf0c76c2f91\content
00:58:14,230 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "arquillian-service" (runtime-name: "arquillian-service")
00:58:14,378 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.
00:58:14,378 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.
00:58:14,378 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.
00:58:14,378 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.
00:58:14,385 WARN  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0013: Deployment deployment "arquillian-service" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations)
00:58:14,406 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "arquillian-service" (runtime-name : "arquillian-service")
00:58:14,484 WARN  [org.jboss.remotingjmx.Util] (main) The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'.
00:58:14,547 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\ee\50a8835708a5ce0336a99b2339ba39d40b9e00\content
00:58:14,550 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "conversation.war" (runtime-name: "conversation.war")
00:58:14,581 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.
00:58:14,581 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.
00:58:14,581 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.conversation.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
00:58:14,581 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) 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.
00:58:14,588 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment conversation.war
00:58:14,593 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) 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

00:58:14,643 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Starting Services for CDI deployment: conversation.war
00:58:14,648 INFO  [org.jboss.as.arquillian] (MSC service thread 1-3) Arquillian deployment detected: ArquillianConfig[service=jboss.arquillian.config."conversation.war",unit=conversation.war,tests=[org.jboss.as.test.clustering.cluster.web.context.InvalidateConversationTestCase]]
00:58:14,652 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0009: Starting weld service for deployment conversation.war
00:58:14,653 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.
00:58:14,653 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.
00:58:14,654 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:14,655 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:14,658 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 35) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:14,658 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 35) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:14,659 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 10) WFLYCLINF0002: Started dist cache from ejb container
00:58:14,660 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.
00:58:14,661 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.
00:58:14,665 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 10) WFLYCLINF0002: Started routing cache from web container
00:58:14,668 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) WFLYCLINF0002: Started client-mappings cache from ejb 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: -------
00:58:30,426 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
00:58:30,426 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
00:58:30,427 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
00:58:30,437 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\cd\c51f4b5ecbbf3aafd28ba52aadd2f139bcccbe\content
00:58:30,438 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
00:58:30,500 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:30,501 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:30,502 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:30,502 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:30,510 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 3) WFLYCLINF0002: Started routing cache from web container
00:58:30,512 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 86) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:30,513 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 86) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:30,522 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 86) WFLYCLINF0002: Started expiration.war cache from web container
00:58:30,537 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 86) WFLYUT0021: Registered web context: /expiration
00:58:30,551 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
00:58:30,557 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
00:58:30,568 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\cd\c51f4b5ecbbf3aafd28ba52aadd2f139bcccbe\content
00:58:30,569 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
00:58:30,615 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 89) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:30,615 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 89) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:30,617 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.
00:58:30,618 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.
00:58:30,621 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 89) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:30,621 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 89) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:30,624 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 82) WFLYCLINF0002: Started routing cache from web container
00:58:30,629 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 89) WFLYCLINF0002: Started expiration.war cache from web container
00:58:30,642 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 89) WFLYUT0021: Registered web context: /expiration
00:58:30,652 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
00:58:30,679 INFO  [stdout] (default task-2) http://[::1]:8080/expiration/listener?operation=set&name=a;jsessionid=vEyHP3VNuWTZRS9SaRPufqgCmbWlNJZp8guPrr_7

00:58:30,700 INFO  [stdout] (default task-3) http://[::1]:8080/expiration/listener?operation=set&name=a&value=1;jsessionid=vEyHP3VNuWTZRS9SaRPufqgCmbWlNJZp8guPrr_7

00:58:30,709 INFO  [stdout] (default task-22) http://[::1]:8180/expiration/listener?operation=get&name=a;jsessionid=oh4EcdpgChmX7BA2ye_A355jwPIpcAgnim9oWlVu

00:58:30,713 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
00:58:30,713 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
00:58:30,713 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-0
00:58:30,716 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 87) WFLYUT0022: Unregistered web context: /expiration
00:58:30,723 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 87) ISPN000029: Passivating all entries to disk
00:58:30,742 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 87) ISPN000030: Passivated 3 entries in 18 milliseconds
00:58:30,745 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 87) WFLYCLINF0003: Stopped expiration.war cache from web container
00:58:30,754 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 10) WFLYCLINF0003: Stopped routing cache from web container
00:58:30,757 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment expiration.war (runtime-name: expiration.war) in 40ms
00:58:30,770 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0002: Content removed from location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\cd\c51f4b5ecbbf3aafd28ba52aadd2f139bcccbe\content
00:58:30,770 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0009: Undeployed "expiration.war" (runtime-name: "expiration.war")
00:58:30,771 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-1
00:58:30,775 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 89) WFLYUT0022: Unregistered web context: /expiration
00:58:30,779 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 90) 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: -------
00:58:30,820 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
00:58:30,820 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
00:58:30,820 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
00:58:30,830 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\d0\5f3170276a187340b6bfd8789e43994281a091\content
00:58:30,834 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
00:58:30,888 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.
00:58:30,889 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.
00:58:30,889 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.
00:58:30,890 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.
00:58:30,915 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 87) WFLYCLINF0002: Started routing cache from web container
00:58:30,919 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 35) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:30,920 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 35) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:30,934 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) WFLYCLINF0002: Started expiration.war cache from web container
00:58:30,947 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 35) WFLYUT0021: Registered web context: /expiration
00:58:30,966 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
00:58:30,972 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
00:58:30,982 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\d0\5f3170276a187340b6bfd8789e43994281a091\content
00:58:30,985 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
00:58:31,047 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 89) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:31,048 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 89) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:31,048 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.
00:58:31,048 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.
00:58:31,051 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 85) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:31,051 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 85) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:31,058 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 85) WFLYCLINF0002: Started routing cache from web container
00:58:31,058 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 87) WFLYCLINF0002: Started expiration.war cache from web container
00:58:31,069 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 87) WFLYUT0021: Registered web context: /expiration
00:58:31,098 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
00:58:31,125 INFO  [stdout] (default task-4) http://[::1]:8080/expiration/listener?operation=set&name=a;jsessionid=PbEJjvPGWo4LJ6uzWPb6jdXaESoJTqQglz8AXMUt

00:58:31,132 INFO  [stdout] (default task-5) http://[::1]:8080/expiration/listener?operation=set&name=a&value=1;jsessionid=PbEJjvPGWo4LJ6uzWPb6jdXaESoJTqQglz8AXMUt

00:58:31,140 INFO  [stdout] (default task-23) http://[::1]:8180/expiration/listener?operation=get&name=a;jsessionid=2Ef9LZdJPokc8-Ftr1NHzAUrzpzmzFDQLgvBRbJz

00:58:31,145 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
00:58:31,145 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
00:58:31,145 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-0
00:58:31,149 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 10) WFLYUT0022: Unregistered web context: /expiration
00:58:31,153 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 86) ISPN000029: Passivating all entries to disk
00:58:31,156 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 86) ISPN000030: Passivated 3 entries in 2 milliseconds
00:58:31,158 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 86) WFLYCLINF0003: Stopped expiration.war cache from web container
00:58:31,164 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 86) WFLYCLINF0003: Stopped routing cache from web container
00:58:31,167 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment expiration.war (runtime-name: expiration.war) in 19ms
00:58:31,180 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0002: Content removed from location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\d0\5f3170276a187340b6bfd8789e43994281a091\content
00:58:31,180 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0009: Undeployed "expiration.war" (runtime-name: "expiration.war")
00:58:31,181 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-1
00:58:31,185 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 85) WFLYUT0022: Unregistered web context: /expiration
00:58:31,192 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 85) 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: -------
00:58:31,224 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
00:58:31,225 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
00:58:31,228 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
00:58:31,228 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
00:58:31,228 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
00:58:31,236 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\95\2a8dceecd71cc8d8e7f05b59f958bd944be9c8\content
00:58:31,238 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "externalizer.war" (runtime-name: "externalizer.war")
00:58:31,285 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 86) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:31,286 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 86) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:31,287 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.
00:58:31,288 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.
00:58:31,288 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.
00:58:31,289 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.

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.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:112)
	at org.jboss.as.test.clustering.cluster.web.ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover(ClusteredWebFailoverAbstractCase.java:103)
------- Stdout: -------
00:58:31,802 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
00:58:31,802 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
00:58:31,802 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
00:58:31,815 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\c7\20c52736bdb32bc8829c63904895cdfddfe625\content
00:58:31,818 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "granular-distributable.war" (runtime-name: "granular-distributable.war")
00:58:31,844 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) 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.
00:58:31,844 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) 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.
00:58:31,844 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) 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.
00:58:31,849 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment granular-distributable.war
00:58:31,855 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

00:58:31,879 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Starting Services for CDI deployment: granular-distributable.war
00:58:31,882 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 23) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:31,882 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 23) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:31,884 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 35) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:31,884 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 35) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:31,885 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:31,886 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:31,890 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment granular-distributable.war
00:58:31,893 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 35) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:31,894 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 35) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:31,896 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 23) WFLYCLINF0002: Started dist cache from ejb container
00:58:31,899 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.
00:58:31,899 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.
00:58:31,915 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 3) WFLYCLINF0002: Started client-mappings cache from ejb container
00:58:31,915 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 87) WFLYCLINF0002: Started granular-distributable.war cache from web container
00:58:31,918 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) WFLYCLINF0002: Started routing cache from web container
00:58:32,104 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 87) WFLYUT0021: Registered web context: /granular-distributable
00:58:32,115 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "granular-distributable.war" (runtime-name : "granular-distributable.war")
00:58:32,121 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
00:58:32,132 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\6c\00e6e6dc5a810408646389f081dbe9e850b9a2\content
00:58:32,133 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "granular-distributable.war" (runtime-name: "granular-distributable.war")
00:58:32,156 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.
00:58:32,156 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.
00:58:32,157 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.

org.jboss.as.test.clustering.cluster.web.GranularWebFailoverTestCase(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:112)
	at org.jboss.as.test.clustering.cluster.web.ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover(ClusteredWebFailoverAbstractCase.java:83)
------- Stdout: -------
00:58:47,532 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
00:58:47,533 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
00:58:47,533 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
00:58:47,543 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\98\f0d78ea0a5c6458771e05f978fdbf7ab131ea4\content
00:58:47,545 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "granular-distributable.war" (runtime-name: "granular-distributable.war")
00:58:47,567 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.
00:58:47,567 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.
00:58:47,567 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.
00:58:47,572 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment granular-distributable.war
00:58:47,576 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

00:58:47,599 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0006: Starting Services for CDI deployment: granular-distributable.war
00:58:47,601 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 19) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:47,602 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 19) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:47,604 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.
00:58:47,605 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.
00:58:47,605 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0009: Starting weld service for deployment granular-distributable.war
00:58:47,606 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.
00:58:47,606 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.
00:58:47,607 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.
00:58:47,607 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.
00:58:47,613 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 19) WFLYCLINF0002: Started dist cache from ejb container
00:58:47,616 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 82) WFLYCLINF0002: Started routing cache from web container
00:58:47,621 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 10) WFLYCLINF0002: Started client-mappings cache from ejb container
00:58:47,624 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 35) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:47,625 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 35) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:58:47,631 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 82) WFLYCLINF0002: Started granular-distributable.war cache from web container
00:58:47,758 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 86) WFLYUT0021: Registered web context: /granular-distributable
00:58:47,776 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "granular-distributable.war" (runtime-name : "granular-distributable.war")
00:58:47,788 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
00:58:47,799 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\98\f0d78ea0a5c6458771e05f978fdbf7ab131ea4\content
00:58:47,800 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "granular-distributable.war" (runtime-name: "granular-distributable.war")
00:58:47,824 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) 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.
00:58:47,824 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) 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.
00:58:47,825 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) 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.


Long running stored procedure - socket is not connected error

Hi,
I am having some issues with long running stored procedures (10+ minutes) causing read tcp <IP_ADDRESS>:56028-><IP_ADDRESS>:1521: read: socket is not connected error.
To simulatie I am running Oracle in docker and created a very simple procedure:
create or replace PROCEDURE WaitAndFinish AS
BEGIN
  -- Procedure started
  DBMS_OUTPUT.PUT_LINE('Procedure started');
  -- Wait for 5 minutes (300 seconds)
  DBMS_LOCK.SLEEP(300);
  -- Procedure running 5 minutes
  DBMS_OUTPUT.PUT_LINE('Procedure running 5 minutes');
  -- Wait for 5 minutes (300 seconds)
  DBMS_LOCK.SLEEP(300);
  -- Procedure running another 5 minutes
  DBMS_OUTPUT.PUT_LINE('Procedure running another 5 minutes');
  -- Procedure finished after waiting for 10 minutes
  DBMS_OUTPUT.PUT_LINE('Procedure has finished after waiting for 10 minutes.');
END WaitAndFinish;

Then using:
	urlOptions := map[string]string{
		"TIMEOUT": "0",
	}

And simply call the procedure:
	// Call the stored procedure
	fmt.Println("Started stored procedure")
	t := time.Now()
	_, err = conn.Exec(`BEGIN waitandfinish(); END;`)
	if err != nil {
		fmt.Println("Failed running stored procedure:", err)
		fmt.Println("Stored procedure took:", time.Now().Sub(t))
		return
	}
	fmt.Println("Stored procedure took:", time.Now().Sub(t))

Gives the following error:
Started Loader
Connection string:  (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=<IP_ADDRESS>)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=XEPDB1)))
Started stored procedure
Failed running stored procedure: read tcp <IP_ADDRESS>:58048-><IP_ADDRESS>:1521: read: socket is not connected
Stored procedure took: 10m0.187546811s

the error means oracle server is close the socket while your procedure is waiting
would you please refer to this oracle docs

server sqlnet.ora parameters required

SQLNET.RECV_TIMEOUT
SQLNET.INBOUND_CONNECT_TIMEOUT


Fix xcdevice issues from iOS 17

This PR fixes 2 problems:

iOS 17 devices not being identified as wireless

Introduced in iOS 17 / Xcode 15, all paired devices are automatically wirelessly connected and it can't be disabled.

https://techhub.social/@JTostitos/110499792791802006
However, xcdevice list, which we use to get information about physical iOS devices, return that the interface is usb, rather than network (network is the expected interface for wireless devices). To fix this, this PR changes so that all iOS 17 devices are considered wireless.
In the future, we will probably want to switch to use the new devicectl command, which provides accurate information, once it's out of preview.

Duplicate entries from xcdevice list cause devices to not show in flutter devices, flutter run, etc.

When a duplicate entry is found, use the entry without errors as the authority. If both have errors, use the one with the higher SDK as the authority.
Fixes https://github.com/flutter/flutter/issues/128719.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Have you considered treating all iOS 17 devices as usb connected? or is it arbitrary decision?
Yes, so the interface type influences some logic, such as launch arguments, whether to use MDNS, whether to forward port, etc. The wireless implementation of things will still work even if the device is plugged in. However, the usb implementation of things will not work if the device is not plugged in, which is why I decided to default it to wireless.

Why do we have duplicate entries? Is it a new problem?
Yes, I believe it to be a new problem introduced with Xcode 17. It's not clear why it's happening, or if it'll happen for everyone. It could be a bug with Xcode or the beta. I speculate it's because they implemented a new device connectivity stack and it's a bug/discrepancy.

The wireless implementation of things will still work even if the device is plugged in. However, the usb implementation of things will not work if the device is not plugged in, which is why I decided to default it to wireless.

What happens if you turn off the device's wifi or bluetooth (or whatever wireless debugging uses)?

If you turn wifi off and the device is connected via USB, it still works. If you turn wifi off and the device is not connected via USB, it does not work, which is expected.

@hellohuanlin I decided to remove the wireless stuff for this PR. I realized, depending on which solution we do for ios-deploy will probably influence how we do wireless so I'm going to wait and do it in a future PR. This PR now just addresses the duplicates

If you turn wifi off and the device is connected via USB, it still works. If you turn wifi off and the device is not connected via USB, it does not work, which is expected.

Oh i meant if you turn wifi off, and device is connected via USB, will the device be listed as wired or wireless?


[Linux] trackbar does not display the max value

Hi Fernando,
First over all, congratulations for the 2.0 : the cmake is perfect, and the Linux build works without any glitch. Wow !
Second, your image buttons and all the improvement you did (everything in a .h ) desserve another wow too :-)
I only found one strange issue (see the attached screenshot) : the trackbar do not display the max value. I started to search, but I'm unsure, so I'll add more information, and let you know when things will be ok , means when I'll have a fix or at least a workaround (probably soemthing linked to sprintf_s replaced by sprintf not enough, but I'm unsure).
BTW, what about add those lines in the CMakeLists.txt file (located in $ROOT_DIR) ?
diff_CMakelists.diff.txt
Thanks again for sharing your code,
-- ericb

A screenshot of the issue on Linux

A screenshot of the issue on Linux (look at the red ellipse)
cvui_test_slider_no_max_value.pdf

Hello,
I posted a PR that solved it under OS X
https://github.com/Dovyski/cvui/pull/15
Can you test it ?

@pthom
Hello. Thanks a lot for your patch and your support, greatly appreciated. To answer you, I applied all your changes manualy, and I confirm the current issue is fixed. => OK
However, I still have the same problem with the other examples (I'll attach a screenshot of Trackbar example to illustrate). On your side, do you see eveything fixed, or is there yet a bit of little formating to fix for you ?

Looks like I found another little one:
trackbar_changes.diff.txt

Hum, I think I corrected this example also in the PR. If you did it manually, you might have skipped some needed modifications
Let me explain you how to get the changes without having to apply them manually :-)
# Revert all changes
git reset --hard
# Add a new remote that point to the repo where the PR (Pull Request) resides
git remote add pthom https://github.com/pthom/cvui.git
# Apply the changes from the branch that corrects the formatting issue
git pull pthom/long_double_format

For you own use, the important message is : use "%lF" instead of "%lf" for the trackbar formatting options.

@phtom
Yes, you're right, I just applied partialy the changes manualy (I'm used to patch language since a long time ;) ), but the problem is IMHO elsewhere : applying all your changes gives me several "nan" (not a number) with some trackbars (but not all, because there are several templates in the cvui.h).
That's the reason why I stepped backward and restarted from the begining, applying progressively the changes you propose. Currently - for me- the issue is not solved and I didn't figure out where exactly the problem stands. The wrong formatting in the string is certainly a good track, but I wonder whether this is the only reason. FYI, in meantime, I tested other changes in the whole API, modifying the templates, using float only, and I found other problems.  I don't even know whether this is a Linux_only problem, or a design issue or something else (?). I'm not in a hurry and my time is limited, so I'll continue to search, just in case I find a track. HTH you to understand what I'm doing.
However, thanks a lot for the advices and the "git reset --hard " I didn't know. Instead, I'm used to type other commands like " git diff (file or path) | patch-R -pn and other things close. It seems to work too, but maybe what I do is wrong. Last but not least, I'll keep the second one (git pull pthom/long_double_format) preciously in my logs, because it's very usefull with git and can be applied for other projects.
--
ericb

Ok, I was able to reproduce the problem under linux. Working on it ...

Ok, I found the problem and solved it :
Look at https://github.com/pthom/cvui/commit/84f9b11d8ed65f51f6553af8f1112d492c3ac00f
You can get the patch using git pull pthom/long_double_format

@pthom : I got the same fix :-),  and I confirm the issue is fixed.
Thanks a lot !  I got it all working now :  Wow !
For the record, I was not able to ckeckout the change you did (I'm not handy using git, and got some rights issue), but I'll attach the full diff containing all te changes I did to make it work. It should be very similar to your changes (excepted the - currently useless - add_compile_options(-D__Linux) I added in the CMakefile.txt).
If your changes are accepted, please tell me, and I'll checkout a clean repo, to confirm the issue is definitely fixed.
cvui2.0.0_full_diff.diff.txt

Thanks a lot for your hard work on this issue, guys! I will do a final check of the fix on Windows and merge the pull request (within the next three days).

I've just merged the pull request regarding this issue. It breaks on Windows (Visual Studio 2015) because of the static_cast in the trackbar() function definition:
bool trackbar(int theWidth, T *theValue, T theMin, T theMax, int theSegments = 1, const char *theLabelFormat = "%.1Lf", unsigned int theOptions = 0, T theDiscreteStep = static_cast<T>(1.));
If static_cast is not used, e.g.
bool trackbar(int theWidth, T *theValue, T theMin, T theMax, int theSegments = 1, const char *theLabelFormat = "%.1Lf", unsigned int theOptions = 0, T theDiscreteStep = 1);
things compile and work fine on Windows. The use of static_cast looks necessary to me, but is it really required for a compilation on OSX and Linux? It looks like MSVC started the witch hunting season :smile:

Hi Fernando,
My opinion is that the static_cast ought to be necessary. However, if you remove the static_cast in the declarations only it will still compile and run correctly under linux and OSX. I just made the test and it is ok.
It is probably an issue with visual studio 2015 : static_cast(1.) should be a constexpr, be it seems that visual studio does not see it this way.
So, I guess you can remove it.

Looks like this issue is very close to be closed !
strange issue on Windows, but I'm not surprised  ;-) Of course remove -imho correct - static_cast is no problem for me, and I confirm a simple " (long double)theValue " works on Linux too. Not tested on Mac OS X though.
+... I forgot to mention one format issue in row-coluwn/main.cpp
... and last, other possibility to assume portability could be to use a little -D__Linux in the CMakeLists.txt file. (see attached files)
CMakeLists.txt.diff.txt
row_column_cvui#18.diff.txt
@pthom : how does it work on the pixels side with hdpi on Mac OS X ? My current resolution is 1680 X 1050 (Linux on macbook pro 6,2 , 2011 model + " antiglare" screen), and I never tested more using cvui

I think everything is sorted out, guys. Commit 0a3d61bbee01813d8caba6aa6a99808d0bb4fa70 merges all fixes into master. I've created the release v2.0.0-RC1 to check if everything is ok. Could you please check if this version works for you?

Hi Fernando,
I tested everything, and I see no problem => see the full report I added below.
Thanks agains for sharing your code !
cvui_issue#18_report.txt

Hi,
Everything ok on my side after my tests under OSX and linux.
I only saw a minor warning while compiling under OSX :
cvui-2.0.0-RC1/example/src/trackbar-sparkline/main.cpp:46:44: warning: implicit conversion from
      'double' to 'int' changes value from 0.25 to 0 [-Wliteral-conversion]
                        if (cvui::trackbar(150, &value, 0., 5., 0.25)) {
                            ~~~~                                ^~~~

This warning can be silenced by removing the last param (0.25).
For the rest, perfect :-)

Thank you guys for such valuable help (and awesome reports)! :smile:
I will fix the OSX warning and ship version 2.0.

Again thanks for all the help, guys! This issue has been fixed and v2.0.0 is up.


copy edit to wrap around 80 chars

not all lines wrap at 80 characters but now most do.

Hm, cool - thanks!
(My editor always just wrapped the text but I guess this is good too.)

You can really tell the diff in raw mode:
https://raw.githubusercontent.com/mholt/caddy/master/README.md
Before it was going well off to the right.


Bump JSKit, add support for testing in browsers

Resolves https://github.com/swiftwasm/carton/issues/42.
Also updates JavaScriptKit dependency to 0.9.0.

@swiftwasm/carton-team friendly ping 🙂


Added support for Hoeksch Lyceum

Added support for Hoeksch Lyceum

@pbraas First stage of verification passed, official domain is hoekschlyceum.nl as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

I have just uploaded a new picture related to our school administration on Som Today. Another way to confirm my identity is to look for my name on our website on the page: https://hoekschlyceum.nl/personeel-en-mentoren/ My subject is computer science (informatica).

@pbraas Thank you for your patience while waiting for a review and processing your request. Pull request merged.


[5.7] Command to create custom filesystem links

Currently we have the ability to generate a filesystem link from /public/storage to /storage/app/public using the storage:link artisan command.  AFAIK, any other links would need to be created with a manual process, or a custom script.
This PR gives the programmer the ability to define all the links they would like created in their application programmatically. Links and their targets are defined in the config/filesystems.php file.
'links' => [
    public_path('storage') => storage_path('app/public'),
    public_path('images') => storage_path('app/images'),
],

These links will be generated using the new links:generate command, which the programmer can make a part of their deployment process.
This change is better for the user because it gives them full control over the generation of links, rather than being stuck with only the default public_path('storage') => storage_path('app/public').  Also, for better or worse, the user can opt to use relative links over absolute links if they so choose ('public/storage' => 'storage/app/public').
Originally I was going to adapt the StorageLinkCommand for these changes, but I felt the naming would not appropriately reflect what it now does, so I opted for a completely new command.  Also, this allows us to add it to 5.7 instead of 5.8, because we will not affect current users.  My intention is the StorageLinkCommand will be removed in 5.8 in favor of this.
Obviously open to changing any naming.
If this PR is accepted, I would like to go back and add an option to force the deletion and recreation of the link, in case an existing link is updated to point to a new target. Something like:
php artisan links:generate --force

Could you also update the documentation?

once it gets accepted.

Eh, I think this sounds more like a package.

Sorry, but I would have to disagree with this suggestion.  We're taking an existing framework functionality (creating links) and making it user customizable, rather than only working with the one pre-defined link decided on by the framework.
This is very similar to what we've done other places in the FW where we've taken a manual part of deployment and tuned it into code, so we can consistently and automatically deploy it. For example, rather that SSHing into a server and updating CRON entries, we turned it into code. Rather than logging into MySQL and creating tables and fields, we write migrations. This is exactly the same. Rather than SSHing into the server and creating the links, or using something like Envoyer to create the links in a manual and inconsistent manner, we have the links in code and add the command to our deploy process.
This is along the lines of infrastructure as code, which I think is a great thing because it makes things consistent and automated.


Update encoding in movielens_recommendations_transformers.py

At present the example tutorial raising the UnicodeDecodeError at  movies=pd.read_csv()
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 3114: invalid continuation byte
Hence adding the encoding='latin-1' to the movies=pd.read_csv(...,encoding='latin-1') will get rid of this error.
Hence I proposed this code change for review and approval.
Attaching gist for reference to check the error and solution that works fine.

All the checks passed now. May please review.

Hi @haifeng-jin, Can you please review this PR ? Thank you!

Hi @SuryanarayanaY Can you please check @haifeng-jin's comments and keep us posted ? Thank you!

Hi @SuryanarayanaY Any update on this PR? Please. Thank you!

Closing the PR, since the tutorial is already migrated and working fine with the Keras 3 using ISO encoding here https://keras.io/examples/structured_data/movielens_recommendations_transformers/


use the Joi already required instead of getting it again

https://trello.com/c/uRTYARkF/159-3-as-a-360-product-owner-i-would-like-to-have-claim-entry-fields-validation-stored-on-the-server-so-that-we-can-replace-it-with-
The require of a specific Joi file was causing problems in Stu. The same function can be extracted from the Joi library already required without breaking tests

Wrong merge branch


--declaration reports wrong line number when there are /+..+/ comments

/+
+/
void main(){}
dscanner --declaration main
./test.d(2:6)
after some testing it seems it just skips lines containing '/+' or '+/'

It looks like Github doesn't like your code formatting.

/+
+/
void main(){}

Can you reproduce the problem on your side with a file containing those 5 lines?

No. I'm not able to reproduce this. Which OS/CPU is this on? (Also, have you done git submodule update recently?)

ok problem was fixed after that, thanks. Closing.


Update Anaconda's steering council members

Refs #58.

We need approval from @csoja and then we can merge.

@cjmartian is out on PTO till August 1st FWIW.

We need his consent before moving him to emeritus.

Thank you @cjmartian!


Fix lookup symbol for enum members to search a correct code definition

Fix https://github.com/godotengine/godot/issues/94284

I guess this isn't critical for the 4.3 release? We could move this to 4.4 and cherry-pick it for 4.3.x later?

@HolonProduction Fixed

Thanks!


Enable HIGHMEM or roll back VMSPLIT_3G on 32-bit devices

Enabling VMSPLIT_3G only left us with 768MB of addressable memory on 32-bit boards which effectively limits the maximum memory amount on boards with 1GB of memory. We have compensated for this by enabling zram so the amount of memory that the applications are able to use stays the same but this is only a temporary solution. We either need to enable HIGHMEM, which seems to cause random failures on at least Pi3 and the Fin, or roll back the VMSPLIT_3G change.

The VMSPLIT_3G change has been reverted by https://github.com/balena-os/balena-raspberrypi/pull/556


GR backend

I wonder if @jheinen would be interested in helping setup a GR backend. That would really help get Makie.jl going.

I made some announcements during JuliaCon 2017 (interactivity, Qt5 support, ...), and I'd like to keep those promises. I have underestimated the time and effort for the deployment - but we'll do out best. When we are done, I'll inspect Makie.jl.

I still find it desirable to have GR as a backend because its abstraction nicely sits above Cairo and OpenGL, which should be even faster than Cairo in terms of TTFP, right now:

GLMakie ~ 30s
Cairo ~ 16s
GR ~ 5s?

We had quite a bit of progress but GR, being a high level plotting library, is not as easy to work with as e.g. Cairo is.  There are a lot of high level APIs and assumptions baked in (e.g., there is a fixed set of fonts that can be used) and though they are fairly versatile, reconciling the Makie and GR approaches proved to be difficult.
There is some code at www.github.com/JuliaPlots/GRMakie.jl which used to work back in the AbstractPlotting days but has probably fallen out of sync by now.  As I recall, most 2D plots worked fine, but getting 3D scenes to fit and setting the camera correctly was not working (as well as some text issues).


#3 empty project state

What's this PR do?
Adds empty project state for first time users, with mock placeholder cards generated to give the impression of what a full Kanban board would look like. It prompts them to add an item.
Where should the reviewer start?
placeholder-cards.js
How should this be manually tested?
mock the state.items collection on:
views/compnents/item-column/index:109 so that the empty state can be simulated
What are the relevant tickets?
#3
Screenshots (if appropriate)

@wookiehangover :+1: updated


Cleanup NetBeans license header for module spi.viewmodel

Review and cleanup the license header in spi.viewmodel
Oracle donated NetBeans to the Apache Software Foundation.
Your task now is to replace the old license header that has Oracle (and/or Sun Microsystems
and/or NetBeans) in it with the standard Apache Software Foundation license header.
For an empty file that supports headers you must add the Apache license header.
Note that you have to use the proper license header for Java, .properties or HTML files.
Look at the nearby files for templates and copy-paste the license header.
When done commit the changes with a commit message that starts with first line
"[NETBEANS-54] Module Review " and a message body describing your review.
See a longer explanation about what we are doing here: https://cwiki.apache.org/confluence/display/NETBEANS/List+of+Modules+to+Review
Please announce in a comment when you have started work.
Files that need to be looked at in spi.viewmodel:
spi.viewmodel/src/org/netbeans/spi/viewmodel/package.html

I'm going to work on this one.

@ArkantosC did you comment at the same time with @mihaivpopescu?
@mihaivpopescu: please pick another issue, there's plenty more. I see @ArkantosC is already trying to make a PR.

Sure

I'm sorry @mihaivpopescu, looks like I wrote the comment at the same time.


Empty sections shouldn't be visible at all

I'm not sure if this is intentional or not, but if a section is empty it shouldn't be drawn.
For instance, if I define my w:airline_section_z to '', than the last section separator is shown even though there is nothing after it.
If this is intentional, than it could have a configuration option to "not render empty sections".

I've started to having this problem with a vim update, so I'm gonna fill up the standard issue report template, or if you'd like, I can open up a new ticket:
environment

vim: version 7.4.1529
vim-airline: 168dd7970a95c0c5049fec0b101b7f53b6a22469
OS: Arch Linux x86_64 - 4.4.5-1-ARCH - /bin/bash
terminal: urxvt

actual behavior
The powerline icon of the status-line section for "trailing", "mix-ident" shows up, even doe' it has no content.

expected behavior
It shouldn't show up, like it was not showing up before when on:
vim-runtime-7.4.1386 OR smaller.

output of vim --version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Mar  9 2016 16:25:55)
Included patches: 1-1529
Compiled by Arch Linux
Huge version without GUI.  Features included (+) or not (-):
+acl             +farsi           +mouse_netterm   +tag_binary
+arabic          +file_in_path    +mouse_sgr       +tag_old_static
+autocmd         +find_in_path    -mouse_sysmouse  -tag_any_white
-balloon_eval    +float           +mouse_urxvt     +tcl/dyn
-browse          +folding         +mouse_xterm     +terminfo
++builtin_terms  -footer          +multi_byte      +termresponse
+byte_offset     +fork()          +multi_lang      +textobjects
+channel         +gettext         -mzscheme        +title
+cindent         -hangul_input    +netbeans_intg   -toolbar
-clientserver    +iconv           +packages        +user_commands
-clipboard       +insert_expand   +path_extra      +vertsplit
+cmdline_compl   +job             +perl/dyn        +virtualedit
+cmdline_hist    +jumplist        +persistent_undo +visual
+cmdline_info    +keymap          +postscript      +visualextra
+comments        +langmap         +printer         +viminfo
+conceal         +libcall         +profile         +vreplace
+cryptv          +linebreak       +python/dyn      +wildignore
+cscope          +lispindent      +python3/dyn     +wildmenu
+cursorbind      +listcmds        +quickfix        +windows
+cursorshape     +localmap        +reltime         +writebackup
+dialog_con      +lua/dyn         +rightleft       -X11
+diff            +menu            +ruby/dyn        -xfontset
+digraphs        +mksession       +scrollbind      -xim
-dnd             +modify_fname    +signs           -xsmp
-ebcdic          +mouse           +smartindent     -xterm_clipboard
+emacs_tags      -mouseshape      +startuptime     -xterm_save
+eval            +mouse_dec       +statusline      -xpm
+ex_extra        +mouse_gpm       -sun_workshop
+extra_search    -mouse_jsbterm   +syntax
   system vimrc file: "/etc/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -D_FORTIFY_SOURCE=2  -march=x86-64
-mtune=generic -O2 -pipe -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1

Linking: gcc   -L. -Wl,-O1,--sort-common,--as-needed,-z,relro -fstack-protector
-rdynamic -Wl, -export-dynamic -Wl,-E -Wl,-rpath,/usr/lib/perl5/core_perl/CORE
-Wl,-O1,--sort-common, --as-needed,-z,relro -L/usr/local/lib -Wl,--as-needed -o vim
-lm -lncurses -lelf -lnsl -lacl -lattr -lgpm -ldl   -Wl,-E -Wl,-rpath,
/usr/lib/perl5/core_perl/CORE -Wl,-O1, --sort-common,--as-needed,-z,relro
-fstack-protector-strong -L/usr/local/lib
-L/usr/lib/perl5/core_perl/CORE -lperl -lpthread -lnsl -ldl -lm -lcrypt -lutil -lc
-L/usr/lib -ltclstub8.6 -ldl -lz -lpthread -lieee -lm

I have the same problem has above but I'm using neovim.

I also get same issue with @p1100i ,so what is the status of this issue? it has been open for two years

I'd appreciate some feedback on #1130 thanks.

really thanks

Hi does anyone know how to have an empty section on purpose, like the one shown in bling's comment (the darker one that separates "NORMAL" from "[No Name]") or in p1100i's comment. I just want it as an additional border on the left, but not the trailing red one on the right that #1130 greatly fixed by adding the new let g:airline_skip_empty_sections option. It seems this existed before and then vanished? I wish that to take the same color as an the airline background.


Update Fastlane.swift

[swift] fixed changelogFromGitCommits between

Checklist

[ ] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[ ] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[ ] I've read the Contribution Guidelines
[ ] I've updated the documentation if necessary.

Motivation and Context

https://github.com/fastlane/fastlane/issues/15104#issue-473914348
Description

changelog = changelogFromGitCommits(
	between: ["\(commit_id)", "HEAD"]
)

ok

May be?
Between configuration used commit_count: line:83
Commit_count used between line:98

Closing this in favor of #15165 (which fixes is_string: false) for a bunch of actions.
@philCc Allowing support for plugins is 100% in the plans in the near future 😊


⚡ A couple of tiny improvements

This tiny PR polishes some small aspects of the library. Most importantly it avoids a costly copy in one of the Z3 conversion functions.

(no idea what happened with the git diff in the one file. it works if whitespace changes are hidden 🙃 )


Backing up Durable database with Ephemeral snapshotter

Hi!
I'm trying to backup a Durable database to swift. I'm using the following resource-definition:
apiVersion: kubedb.com/v1alpha1
kind: Postgres
metadata:
  name: quick-postgres-very-long-name-to-test-gluster
  namespace: stage
spec:
  version: "10.6"
  storageType: Durable
  storage:
    storageClassName: "glusterfs"
    accessModes:
    - ReadWriteOnce
    resources:
      requests:
        storage: 1Gi
  terminationPolicy: Delete
  backupSchedule:
    cronExpression: "@every 1m"
    storageSecretName: swift-secret
    swift:
      container: utv-backups
      prefix: test

But when the snapshotter is running it cannot create a PVC because of the following error: "failed to create volume: failed to create endpoint/service stage/glusterfs-dynamic-kubedb-quick-postgres-very-long-name-to-test-20190308-153121: error creating service: Service "glusterfs-dynamic-kubedb-quick-postgres-very-long-name-to-test-20190308-153121" is invalid: metadata.name: Invalid value: "glusterfs-dynamic-kubedb-quick-postgres-very-long-name-to-test-20190308-153121": must be no more than 63 characters".
I would like to solve this by using an emptyDir volume when running the snapshotter instead... Is that possible? (Setting StorageType=Ephemeral of snapshot generated by BackupSchedule)

We added Ephemeral snapshot storage type in 0.10.0. But looks like it is missing from backup scheduler. We need to fix it. :(
I am not seeing any other way, except using snapshot each time. :(

That was quick! Thanks @the-redback


[Documentation] Outdated Fedora versions references on package install

Problem encountered on https://dotnet.microsoft.com/download/linux-package-manager/fedora28/sdk-2.2.301
Operating System: Linux Fedora 28 - x64
Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.
In the documentation there are references to Fedora 27 and 28 when both of those versions was discontinued. Besides this i've tried to use the following link https://packages.microsoft.com/config/fedora/30/prod.repo pointing to the Fedora 30 and its working fine.
I've tried to find the documentation file to fix this, but without any success.

@leecow it looks like https://dotnet.microsoft.com/download/linux-package-manager/fedora28/sdk-2.2.301 needs an update. Is that your page?

This is a known problem--there's a larger discussion/decision that needs to happen about keeping the distro list up to date: https://github.com/dotnet/core/issues/2576.
I would expect the "F27" feed to work for F30. We don't actually produce packages that are specific to F30--they're the same RPMs. @Rubemlrm, did you hit any installation problems, or is this only for the doc problem?

@dagood it's working without any problem, this is a doc problem only.
Thanks

Thanks for confirming! I've updated the title of https://github.com/dotnet/core/issues/2576  and moved the comment about Fedora to the top to make it a little more visible, and I'm going to close this issue as a duplicate.

Duplicate of #2576


error 400 in local

sorry i want to ask, i want to use tus on my local development
first I add gem "tus-server", "~> 2.0" to my gemfile
and i add this to my routes.rb
Rails.application.routes.draw do
mount Tus::Server => "/files"
end
when my IOS hit my localhost:3000/files they get error code 400
can you help me?

What is the body from that response? 400 Bad Request means that the client sent invalid parameters to the server, in which case the response body would contain the error message.

What is the body from that response? 400 Bad Request means that the client sent invalid parameters to the server, in which case the response body would contain the error message.

okay thanks, already solve by
add metadata:  filename: file.name,filetype: file.type
it is possible to add filename and filetype in request header not in metadata????

No, as that’s not part of the tus.io protocol.


added my name to contributor

please merge my PR

resolve conflict or add your name without a serial number


Update tests_requirements.txt

Adding scikit-learn for new RF module

Codecov Report

Merging #6 into master will increase coverage by 1.18%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master       #6      +/-   ##
==========================================
+ Coverage   77.71%   78.90%   +1.18%
==========================================
  Files           7        8       +1
  Lines         368      384      +16
==========================================
+ Hits          286      303      +17
+ Misses         82       81       -1

Impacted Files
Coverage Δ

GCEm/rf_model.py
100.00% <100.00%> (ø)

GCEm/model.py
92.40% <0.00%> (+1.26%)
:arrow_up:

Continue to review full report at Codecov.

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


(Bug) Freeze Time

Holding the freeze time button will cause it to alternate between freeze time and normal time. This becomes an issue if you don't release the key fast enough which results in the time resuming

This was actually intended to be a feature, since once you press the key you cannot re-press it for another 250ms by default. Idea being you can toggle it quickly to get the perfect frame, but I understand how it can be annoying. Will fix.

Perhaps an option to enable/disable that could be helpful

here is the line that controls it, I'll probably remove the 100 so it defaults back to 250, then those who wanna change it can just modify that value.

Reset back to 250


FabricObserverWebApi: Check if deployed, else don't run code related to it in FO...

Enable user setting (bool) ObserverWebApiEnabled and also have ObserverManager check if ObsWeb is deployed in cluster (can only check for the default app name, thus provide a user setting in Settings.xml as well...). For the code that runs to support ObsWeb from FO, don't run it if ObsWeb is not deployed...

Done... In testing...