WFLY-6695: Replace \n with platform specific line ending

Linux Build 9722 outcome was FAILURE using a merge of b95e8aaf7fbb3d7a57d8b09fcab5280c3c19b8e3
Summary: Tests failed: 1 (1 new), passed: 3397, ignored: 193 Build time: 00:57:31
Failed tests
org.jboss.as.test.clustering.cluster.web.passivation.FineSessionPassivationTestCase(SYNC-tcp).test: java.lang.AssertionError: response doesn't contain header 'result', all response headers = {name=Connection, value=keep-alive}, {name=X-Powered-By, value=Undertow/1}, {name=Set-Cookie, value=JSESSIONID=yz3bNydx06nNU1RZxNMjOzTQgIxujj6KMlY4nNkM.node-0; path=/passivation}, {name=Server, value=WildFly/10}, {name=fIBezWCGUTD7Jf0hW5gvy9buVyaqALIx3tFhRWw7, value=PASSIVATION}, {name=Content-Length, value=0}, {name=jsessionid, value=yz3bNydx06nNU1RZxNMjOzTQgIxujj6KMlY4nNkM}, {name=Date, value=Thu, 09 Jun 2016 15:38:46 GMT},
	at org.jboss.as.test.clustering.cluster.web.passivation.SessionPassivationTestCase.getRequiredHeaderValue(SessionPassivationTestCase.java:207)
	at org.jboss.as.test.clustering.cluster.web.passivation.SessionPassivationTestCase.test(SessionPassivationTestCase.java:121)
------- Stdout: -------
08:38:45,823 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
08:38:45,823 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
08:38:45,823 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
 [0m08:38:45,846 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0/standalone/data/content/84/16bf5daff179cc10fc0f1edd67d71fcf001850/content
 [0m [0m08:38:45,848 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "passivation.war" (runtime-name: "passivation.war")
 [0m [0m08:38:45,882 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.
 [0m [0m08:38:45,882 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.
 [0m [0m08:38:45,884 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.
 [0m [0m08:38:45,884 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.
 [0m [0m08:38:45,894 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 34) WFLYCLINF0002: Started passivation.war cache from web container
 [0m [0m08:38:45,908 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 3) WFLYCLINF0002: Started routing cache from web container
 [0m [0m08:38:45,928 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 3) WFLYUT0021: Registered web context: /passivation
 [0m [0m08:38:45,935 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "passivation.war" (runtime-name : "passivation.war")
 [0m08:38:45,940 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
 [0m08:38:45,951 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-SYNC-tcp-1/standalone/data/content/84/16bf5daff179cc10fc0f1edd67d71fcf001850/content
 [0m [0m08:38:45,953 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "passivation.war" (runtime-name: "passivation.war")
 [0m [0m08:38:45,998 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.
 [0m [0m08:38:45,998 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.
 [0m [0m08:38:46,002 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 81) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m08:38:46,003 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 81) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m08:38:46,003 INFO  [org.infinispan.CLUSTER] (ServerService Thread Pool -- 83) ISPN000310: Starting cluster-wide rebalance for cache routing, topology CacheTopology{id=1, rebalanceId=1, currentCH=DefaultConsistentHash{ns=80, owners = (1)[node-0: 80+0]}, pendingCH=DefaultConsistentHash{ns=80, owners = (2)[node-0: 40+40, node-1: 40+40]}, unionCH=null, actualMembers=[node-0, node-1]}
 [0m [0m08:38:46,003 INFO  [org.infinispan.CLUSTER] (ServerService Thread Pool -- 83) [Context=routing][Scope=node-1]ISPN100002: Started local rebalance
 [0m [0m08:38:46,009 INFO  [org.infinispan.CLUSTER] (ServerService Thread Pool -- 81) ISPN000310: Starting cluster-wide rebalance for cache passivation.war, topology CacheTopology{id=1, rebalanceId=1, currentCH=DefaultConsistentHash{ns=80, owners = (1)[node-0: 80+0]}, pendingCH=DefaultConsistentHash{ns=80, owners = (2)[node-0: 40+40, node-1: 40+40]}, unionCH=null, actualMembers=[node-0, node-1]}
 [0m [0m08:38:46,009 INFO  [org.infinispan.CLUSTER] (ServerService Thread Pool -- 81) [Context=passivation.war][Scope=node-1]ISPN100002: Started local rebalance
 [0m [0m08:38:46,014 INFO  [org.infinispan.CLUSTER] (remote-thread--p8-t3) [Context=routing][Scope=node-0]ISPN100003: Finished local rebalance
 [0m [0m08:38:46,015 INFO  [org.infinispan.CLUSTER] (remote-thread--p8-t3) [Context=passivation.war][Scope=node-0]ISPN100003: Finished local rebalance
 [0m [0m08:38:46,026 INFO  [org.infinispan.CLUSTER] (transport-thread--p16-t17) [Context=passivation.war][Scope=node-1]ISPN100003: Finished local rebalance
 [0m [0m08:38:46,027 INFO  [org.infinispan.CLUSTER] (transport-thread--p16-t17) ISPN000336: Finished cluster-wide rebalance for cache passivation.war, topology id = 1
 [0m [0m08:38:46,030 INFO  [org.infinispan.CLUSTER] (transport-thread--p16-t19) [Context=routing][Scope=node-1]ISPN100003: Finished local rebalance
 [0m [0m08:38:46,033 INFO  [org.infinispan.CLUSTER] (transport-thread--p16-t19) ISPN000336: Finished cluster-wide rebalance for cache routing, topology id = 1
 [0m [0m08:38:46,033 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 81) WFLYCLINF0002: Started passivation.war cache from web container
 [0m [0m08:38:46,036 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 83) WFLYCLINF0002: Started routing cache from web container
 [0m [0m08:38:46,054 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 83) WFLYUT0021: Registered web context: /passivation
 [0m [0m08:38:46,062 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "passivation.war" (runtime-name : "passivation.war")
 [0m [0m08:38:46,078 INFO  [stdout] (default task-64) http://[::1]:8080/passivation/listener?operation=set&name=a&value=1;jsessionid=8RJkF7FvyYvt-LEWoAvelwNaAdStl6ckyRaAgbGK
 [0m [0m08:38:46,087 INFO  [stdout] (default task-52) http://[::1]:8080/passivation/listener?operation=set&name=a&value=2;jsessionid=fIBezWCGUTD7Jf0hW5gvy9buVyaqALIx3tFhRWw7
 [0m [0m08:38:46,095 INFO  [stdout] (default task-35) http://[::1]:8080/passivation/listener?operation=get&name=a;jsessionid=yz3bNydx06nNU1RZxNMjOzTQgIxujj6KMlY4nNkM
 [0m08:38:46,099 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
08:38:46,099 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
08:38:46,100 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-0
 [0m08:38:46,104 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 34) WFLYUT0022: Unregistered web context: /passivation
 [0m [0m08:38:46,135 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 82) ISPN000029: Passivating all entries to disk
 [0m [0m08:38:46,135 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 82) ISPN000030: Passivated 5 entries in 0 milliseconds
 [0m [0m08:38:46,139 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 82) WFLYCLINF0003: Stopped passivation.war cache from web container
 [0m [0m08:38:46,144 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment passivation.war (runtime-name: passivation.war) in 40ms
 [0m [0m08:38:46,173 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 82) WFLYCLINF0003: Stopped routing cache from web container
 [0m [0m08:38:46,188 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location /opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0/standalone/data/content/84/16bf5daff179cc10fc0f1edd67d71fcf001850/content

Windows Build 4761 outcome was FAILURE using a merge of b95e8aaf7fbb3d7a57d8b09fcab5280c3c19b8e3
Summary: Tests failed: 6 (6 new), passed: 3364, ignored: 194 Build time: 01:11:26
Failed tests
org.jboss.as.test.integration.jsp.JspTagTestCase.test:

tag

Static content
]
> but was:<This is a header[

tag

Static content]
>

tag

Static content
]
> but was:<This is a header[

tag

Static content]
>
	at org.jboss.as.test.integration.jsp.JspTagTestCase.test(JspTagTestCase.java:66)
------- Stdout: -------
16:23:54,458 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 4) WFLYUT0022: Unregistered web context: /DefaultConcurrencyServletTestCase
16:23:54,467 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment DefaultConcurrencyServletTestCase.war (runtime-name: DefaultConcurrencyServletTestCase.war) in 10ms
16:23:54,477 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0002: Content removed from location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\web\target\jbossas\standalone\data\content\c4\c4bf6bc903f6068930374e42abcc7bb7225c05\content
16:23:54,477 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0009: Undeployed "DefaultConcurrencyServletTestCase.war" (runtime-name: "DefaultConcurrencyServletTestCase.war")
16:23:54,499 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\web\target\jbossas\standalone\data\content\8c\996ea005cae6127ef29c0598a01e8da0319beb\content
16:23:54,501 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "2efa2522-3395-431a-a8d2-753ce2b43024.war" (runtime-name: "2efa2522-3395-431a-a8d2-753ce2b43024.war")
16:23:54,526 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.2efa2522-3395-431a-a8d2-753ce2b43024.war" is using a private module ("org.wildfly.security.manager:main") which may be changed or removed in future versions without notice.
16:23:54,536 INFO  [org.jboss.as.arquillian] (MSC service thread 1-2) Arquillian deployment detected: ArquillianConfig[service=jboss.arquillian.config."2efa2522-3395-431a-a8d2-753ce2b43024.war",unit=2efa2522-3395-431a-a8d2-753ce2b43024.war,tests=[org.jboss.as.test.integration.jsp.JspTagTestCase]]
16:23:54,543 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 4) WFLYUT0021: Registered web context: /2efa2522-3395-431a-a8d2-753ce2b43024
16:23:54,551 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "2efa2522-3395-431a-a8d2-753ce2b43024.war" (runtime-name : "2efa2522-3395-431a-a8d2-753ce2b43024.war")

org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase(SYNC-tcp).testBasicXPC: java.lang.AssertionError: expected:<200> but was:<500>
	at org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase.executeUrlWithAnswer(StatefulWithXPCFailoverTestCase.java:249)
	at org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase.testBasicXPC(StatefulWithXPCFailoverTestCase.java:224)
------- Stdout: -------
16:44:52,969 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
16:44:52,970 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
16:44:52,970 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
16:44:52,986 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\e3\8c405147b441be6a053d0781aa848839111bd4\content
16:44:52,987 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "stateful.war" (runtime-name: "stateful.war")
16:44:53,012 INFO  [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Read persistence.xml for mypc
16:44:53,027 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 19) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'stateful.war#mypc'
16:44:53,027 INFO  [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 19) HHH000204: Processing PersistenceUnitInfo [
	name: mypc
	...]
16:44:53,030 INFO  [org.hibernate.orm.deprecation] (ServerService Thread Pool -- 19) HHH90000001: Found usage of deprecated setting for specifying Scanner [hibernate.ejb.resource_scanner]; use [hibernate.archive.scanner] instead
16:44:53,034 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment stateful.war
16:44:53,040 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'StatefulBean' in deployment unit 'deployment "stateful.war"' are as follows:

	java:global/stateful/StatefulBean!org.jboss.as.test.clustering.cluster.ejb.xpc.bean.Stateful
	java:app/stateful/StatefulBean!org.jboss.as.test.clustering.cluster.ejb.xpc.bean.Stateful
	java:module/StatefulBean!org.jboss.as.test.clustering.cluster.ejb.xpc.bean.Stateful
	java:global/stateful/StatefulBean
	java:app/stateful/StatefulBean
	java:module/StatefulBean

16:44:53,040 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'SecondBean' in deployment unit 'deployment "stateful.war"' are as follows:

	java:global/stateful/SecondBean!org.jboss.as.test.clustering.cluster.ejb.xpc.bean.SecondBean
	java:app/stateful/SecondBean!org.jboss.as.test.clustering.cluster.ejb.xpc.bean.SecondBean
	java:module/SecondBean!org.jboss.as.test.clustering.cluster.ejb.xpc.bean.SecondBean
	java:global/stateful/SecondBean
	java:app/stateful/SecondBean
	java:module/SecondBean

16:44:53,071 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.
16:44:53,071 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.
16:44:53,076 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 31) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:44:53,077 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 31) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:44:53,077 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.
16:44:53,078 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.
16:44:53,081 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 15) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'stateful.war#mypc'
16:44:53,082 INFO  [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 15) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
16:44:53,082 WARN  [org.hibernate.dialect.H2Dialect] (ServerService Thread Pool -- 15) HHH000431: Unable to determine H2 database version, certain features may not work
16:44:53,085 INFO  [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 15) Envers integration enabled? : true
16:44:53,088 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 19) WFLYCLINF0002: Started client-mappings cache from ejb container
16:44:53,090 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 3) WFLYCLINF0002: Started routing cache from web container
16:44:53,090 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) WFLYCLINF0002: Started stateful.war cache from web container
16:44:53,096 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 31) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:44:53,096 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 31) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:44:53,104 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) WFLYCLINF0002: Started stateful.war cache from ejb container
16:44:53,220 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 15) WFLYCLINF0002: Started stateful.war#mypc.org.jboss.as.test.clustering.cluster.ejb.xpc.bean.Employee cache from hibernate container

org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase(SYNC-tcp).testSecondLevelCache: 	at org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase.testSecondLevelCache(StatefulWithXPCFailoverTestCase.java:178)
------- Stdout: -------
16:45:06,323 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
16:45:06,323 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
16:45:06,324 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
16:45:06,339 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\e8\eff57edc445c3c86793a8292c684e9fe9686ee\content
16:45:06,341 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "stateful.war" (runtime-name: "stateful.war")
16:45:06,364 INFO  [org.jboss.as.jpa] (MSC service thread 1-3) WFLYJPA0002: Read persistence.xml for mypc
16:45:06,385 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 19) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'stateful.war#mypc'
16:45:06,385 INFO  [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 19) HHH000204: Processing PersistenceUnitInfo [
	name: mypc
	...]
16:45:06,388 INFO  [org.hibernate.orm.deprecation] (ServerService Thread Pool -- 19) HHH90000001: Found usage of deprecated setting for specifying Scanner [hibernate.ejb.resource_scanner]; use [hibernate.archive.scanner] instead
16:45:06,391 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment stateful.war
16:45:06,398 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-7) WFLYEJB0473: JNDI bindings for session bean named 'StatefulBean' in deployment unit 'deployment "stateful.war"' are as follows:

	java:global/stateful/StatefulBean!org.jboss.as.test.clustering.cluster.ejb.xpc.bean.Stateful
	java:app/stateful/StatefulBean!org.jboss.as.test.clustering.cluster.ejb.xpc.bean.Stateful
	java:module/StatefulBean!org.jboss.as.test.clustering.cluster.ejb.xpc.bean.Stateful
	java:global/stateful/StatefulBean
	java:app/stateful/StatefulBean
	java:module/StatefulBean

16:45:06,398 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-7) WFLYEJB0473: JNDI bindings for session bean named 'SecondBean' in deployment unit 'deployment "stateful.war"' are as follows:

	java:global/stateful/SecondBean!org.jboss.as.test.clustering.cluster.ejb.xpc.bean.SecondBean
	java:app/stateful/SecondBean!org.jboss.as.test.clustering.cluster.ejb.xpc.bean.SecondBean
	java:module/SecondBean!org.jboss.as.test.clustering.cluster.ejb.xpc.bean.SecondBean
	java:global/stateful/SecondBean
	java:app/stateful/SecondBean
	java:module/SecondBean

16:45:06,431 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.
16:45:06,432 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.
16:45:06,438 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 19) WFLYCLINF0002: Started client-mappings cache from ejb container
16:45:06,445 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 15) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:45:06,445 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 15) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:45:06,446 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 24) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:45:06,446 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 24) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:45:06,448 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 19) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'stateful.war#mypc'
16:45:06,448 INFO  [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 19) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
16:45:06,449 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 24) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:45:06,449 WARN  [org.hibernate.dialect.H2Dialect] (ServerService Thread Pool -- 19) HHH000431: Unable to determine H2 database version, certain features may not work
16:45:06,449 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 24) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:45:06,456 INFO  [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 19) Envers integration enabled? : true
16:45:06,486 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 15) WFLYCLINF0002: Started routing cache from web container
16:45:06,491 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 85) WFLYCLINF0002: Started stateful.war cache from web container
16:45:06,495 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 85) WFLYCLINF0002: Started stateful.war cache from ejb container
16:45:06,498 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 19) WFLYCLINF0002: Started stateful.war#mypc.org.jboss.as.test.clustering.cluster.ejb.xpc.bean.Employee cache from hibernate container
16:45:06,507 INFO  [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 19) HHH000227: Running hbm2ddl schema export
16:45:06,509 INFO  [stdout] (ServerService Thread Pool -- 19) Hibernate: drop table Employee if exists

org.jboss.as.test.clustering.cluster.jsf.JSFFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover: java.lang.AssertionError: expected:<200> but was:<500>
	at org.jboss.as.test.clustering.cluster.jsf.JSFFailoverTestCase.testGracefulUndeployFailover(JSFFailoverTestCase.java:375)
------- Stdout: -------
16:45:08,039 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
16:45:08,039 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
16:45:08,039 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
16:45:08,054 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\dd\8067e18dc8a71a4e169725d6f2f17288ef5fe9\content
16:45:08,056 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "numberguess-jsf.war" (runtime-name: "numberguess-jsf.war")
16:45:08,084 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment numberguess-jsf.war
16:45:08,113 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.
16:45:08,114 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.
16:45:08,114 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.
16:45:08,115 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.
16:45:08,140 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 19) WFLYCLINF0002: Started numberguess-jsf.war cache from web container
16:45:08,181 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) WFLYCLINF0002: Started routing cache from web container
16:45:08,335 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 19) Initializing Mojarra 2.2.13.SP1 20160303-1204 for context '/numberguess-jsf'
16:45:08,399 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 19) WFLYUT0021: Registered web context: /numberguess-jsf
16:45:08,409 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "numberguess-jsf.war" (runtime-name : "numberguess-jsf.war")
16:45:08,414 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
16:45:08,427 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\dd\8067e18dc8a71a4e169725d6f2f17288ef5fe9\content
16:45:08,429 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "numberguess-jsf.war" (runtime-name: "numberguess-jsf.war")
16:45:08,462 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment numberguess-jsf.war
16:45:08,769 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.
16:45:08,771 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.
16:45:08,771 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 28) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:45:08,772 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 28) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:45:08,780 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 28) WFLYCLINF0002: Started numberguess-jsf.war cache from web container
16:45:08,788 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) WFLYCLINF0002: Started routing cache from web container
16:45:08,930 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 35) Initializing Mojarra 2.2.13.SP1 20160303-1204 for context '/numberguess-jsf'
16:45:09,331 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 35) WFLYUT0021: Registered web context: /numberguess-jsf
16:45:09,349 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "numberguess-jsf.war" (runtime-name : "numberguess-jsf.war")
16:45:09,803 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-0
16:45:09,809 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 19) WFLYUT0022: Unregistered web context: /numberguess-jsf
16:45:09,818 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 85) ISPN000029: Passivating all entries to disk
16:45:09,854 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 85) ISPN000030: Passivated 3 entries in 36 milliseconds
16:45:09,857 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 85) WFLYCLINF0003: Stopped numberguess-jsf.war cache from web container
16:45:09,860 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 19) WFLYCLINF0003: Stopped routing cache from web container
16:45:09,863 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment numberguess-jsf.war (runtime-name: numberguess-jsf.war) in 56ms
16:45:09,875 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\dd\8067e18dc8a71a4e169725d6f2f17288ef5fe9\content
16:45:09,875 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0009: Undeployed "numberguess-jsf.war" (runtime-name: "numberguess-jsf.war")
16:45:10,234 ERROR [io.undertow.request] (default task-13) UT005023: Exception handling request to /numberguess-jsf/home.jsf: javax.servlet.ServletException: viewId:/home.jsf - View /home.jsf could not be restored.
	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:671)
	at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85)
	at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
	at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
	at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
	at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
	at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
	at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
	at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
	at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)

org.jboss.as.test.clustering.cluster.jsf.JSFFailoverTestCase(SYNC-tcp).testGracefulSimpleFailover: java.lang.AssertionError: expected:<200> but was:<500>
	at org.jboss.as.test.clustering.cluster.jsf.JSFFailoverTestCase.testGracefulSimpleFailover(JSFFailoverTestCase.java:251)
------- Stdout: -------
16:45:10,304 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
16:45:10,304 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
16:45:10,304 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
16:45:10,316 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\85\58a8f7f877ea526ef787a06d1a6aa476d1777e\content
16:45:10,318 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "numberguess-jsf.war" (runtime-name: "numberguess-jsf.war")
16:45:10,345 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment numberguess-jsf.war
16:45:10,397 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.
16:45:10,398 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.
16:45:10,401 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.
16:45:10,401 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.
16:45:10,402 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 85) WFLYCLINF0002: Started routing cache from web container
16:45:10,410 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 85) WFLYCLINF0002: Started numberguess-jsf.war cache from web container
16:45:10,501 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 85) Initializing Mojarra 2.2.13.SP1 20160303-1204 for context '/numberguess-jsf'
16:45:10,565 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 85) WFLYUT0021: Registered web context: /numberguess-jsf
16:45:10,575 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "numberguess-jsf.war" (runtime-name : "numberguess-jsf.war")
16:45:10,583 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
16:45:10,601 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\85\58a8f7f877ea526ef787a06d1a6aa476d1777e\content
16:45:10,604 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "numberguess-jsf.war" (runtime-name: "numberguess-jsf.war")
16:45:10,761 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment numberguess-jsf.war
16:45:10,793 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 13) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:45:10,793 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 13) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:45:10,799 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 28) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:45:10,800 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 28) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:45:10,846 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 13) WFLYCLINF0002: Started routing cache from web container
16:45:10,854 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 28) WFLYCLINF0002: Started numberguess-jsf.war cache from web container
16:45:11,070 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 13) Initializing Mojarra 2.2.13.SP1 20160303-1204 for context '/numberguess-jsf'
16:45:11,208 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 13) WFLYUT0021: Registered web context: /numberguess-jsf
16:45:11,230 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "numberguess-jsf.war" (runtime-name : "numberguess-jsf.war")
16:45:11,246 INFO  [org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase] (main) URLs are: http://[::1]:8080/numberguess-jsf/home.jsf, http://[::1]:8180/numberguess-jsf/home.jsf
16:45:11,346 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Stopping container=container-0
16:45:11,349 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0236: Suspending server with no timeout.
16:45:11,353 INFO  [org.jboss.as.server] (Management Triggered Shutdown) WFLYSRV0241: Shutting down in response to management operation 'shutdown'
16:45:11,382 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 15) WFLYUT0022: Unregistered web context: /numberguess-jsf
16:45:11,387 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0019: Host default-host stopping
16:45:11,388 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 92) ISPN000029: Passivating all entries to disk
16:45:11,403 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 35) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
16:45:11,407 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 35) MODCLUSTER000002: Initiating mod_cluster shutdown
16:45:11,408 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
16:45:11,408 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-3) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
16:45:11,409 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-7) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA]
16:45:11,443 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 92) ISPN000030: Passivated 3 entries in 55 milliseconds
16:45:11,444 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0019: Stopped Driver service with driver-name = h2
16:45:11,464 INFO  [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 94) AMQ151003: resource adaptor stopped
16:45:11,464 INFO  [org.jboss.ejb.client.remoting] (Remoting "config-based-ejb-client-endpoint" task-8) EJBCLIENT000016: Channel Channel ID ccbf21cc (outbound) of Remoting connection 00f5b018 to /0:0:0:0:0:0:0:1:8080 can no longer process messages
16:45:11,486 INFO  [org.jboss.ejb.client.remoting] (Remoting "config-based-ejb-client-endpoint" task-8) EJBCLIENT000016: Channel Channel ID a42a29a5 (outbound) of Remoting connection 00c26c01 to /0:0:0:0:0:0:0:1:8080 can no longer process messages
16:45:11,486 INFO  [org.jboss.ejb.client.remoting] (Remoting "config-based-ejb-client-endpoint" task-8) EJBCLIENT000016: Channel Channel ID a07c8463 (outbound) of Remoting connection 012aeabd to /0:0:0:0:0:0:0:1:8080 can no longer process messages
16:45:11,502 INFO  [org.jboss.ejb.client.remoting] (Remoting "config-based-ejb-client-endpoint" task-14) EJBCLIENT000016: Channel Channel ID c01a9d0a (outbound) of Remoting connection 01ca4147 to /0:0:0:0:0:0:0:1:8080 can no longer process messages
16:45:11,502 INFO  [org.jboss.ejb.client.remoting] (Remoting "config-based-ejb-client-endpoint" task-2) EJBCLIENT000016: Channel Channel ID c6fc9a58 (outbound) of Remoting connection 00c0f456 to /0:0:0:0:0:0:0:1:8080 can no longer process messages

org.jboss.as.test.integration.domain.mixed.eap640.MixedDomainDeployment640TestCase: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil.awaitServers(DomainLifecycleUtil.java:449)
	at org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil.start(DomainLifecycleUtil.java:251)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSupport.startAndAdjust(MixedDomainTestSupport.java:160)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSupport.start(MixedDomainTestSupport.java:86)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:96)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:59)
	at org.jboss.as.test.integration.domain.mixed.eap640.MixedDomain640TestSuite.initializeDomain(MixedDomain640TestSuite.java:44)
	at org.jboss.as.test.integration.domain.mixed.eap640.MixedDomainDeployment640TestCase.beforeClass(MixedDomainDeployment640TestCase.java:38)
------- Stdout: -------
17:19:27,485 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
17:19:27,750 INFO  [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
[Host Controller] 17:19:28,355 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
[Host Controller] 17:19:28,511 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
[Host Controller] 17:19:28,558 INFO  [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 10.1.0.Final-SNAPSHOT (WildFly Core 2.2.0.CR2) starting
[Host Controller] 17:19:29,118 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'permgen-size' in the resource at address '/host=master/jvm=default' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 17:19:29,118 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'max-permgen-size' in the resource at address '/host=master/jvm=default' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 17:19:29,183 INFO  [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1)
[Host Controller] 17:19:29,185 INFO  [org.xnio] (MSC service thread 1-5) XNIO version 3.3.6.Final
[Host Controller] 17:19:29,193 INFO  [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.3.6.Final
[Host Controller] 17:19:29,288 INFO  [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 4.0.18.Final
[Host Controller] 17:19:29,318 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) WFLYRMT0001: Listening on [::1]:9999
[Host Controller] 17:19:30,747 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://[::1]:9990/management
[Host Controller] 17:19:30,747 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled
[Host Controller] 17:19:30,747 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final-SNAPSHOT (WildFly Core 2.2.0.CR2) (Host Controller) started in 2827ms - Started 46 of 49 services (15 services are lazy, passive or on-demand)
INFO  [org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil] HostController started in 3823 ms
[Host Controller] 17:19:32,495 WARN  [org.jboss.as.messaging] (management-handler-thread - 3) WFLYMSG0071: There is no resource matching the expiry-address jms.queue.ExpiryQueue for the address-settings #, expired messages from destinations matching this address-setting will be lost!
[Host Controller] 17:19:32,495 WARN  [org.jboss.as.messaging] (management-handler-thread - 3) WFLYMSG0072: There is no resource matching the dead-letter-address jms.queue.DLQ for the address-settings #, undelivered messages from destinations matching this address-setting will be lost!
[Host Controller] 17:19:33,542 INFO  [org.jboss.as.controller.management-deprecated] (management-handler-thread - 2) WFLYCTL0028: Attribute 'default-stack' in the resource at address '/' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 17:19:34,211 INFO  [org.jboss.as.controller.management-deprecated] (management-handler-thread - 3) WFLYCTL0028: Attribute 'stack' in the resource at address '/' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 17:19:34,364 INFO  [org.jboss.as] (MSC service thread 1-7) WFLYSRV0050: WildFly Full 10.1.0.Final-SNAPSHOT (WildFly Core 2.2.0.CR2) stopped in 13ms
[Host Controller] 17:19:34,366 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 10.1.0.Final-SNAPSHOT (WildFly Core 2.2.0.CR2) starting
[Host Controller] 17:19:34,382 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'permgen-size' in the resource at address '/host=master/jvm=default' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 17:19:34,382 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'max-permgen-size' in the resource at address '/host=master/jvm=default' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 17:19:34,385 INFO  [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1)
[Host Controller] 17:19:34,417 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) WFLYRMT0001: Listening on [::1]:9999
[Host Controller] 17:19:34,511 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'default-stack' in the resource at address '/profile=full-ha/subsystem=jgroups' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 17:19:34,609 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://[::1]:9990/management
[Host Controller] 17:19:34,610 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://[::1]:9990
[Host Controller] 17:19:34,610 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final-SNAPSHOT (WildFly Core 2.2.0.CR2) (Host Controller) started in 243ms - Started 46 of 49 services (15 services are lazy, passive or on-demand)
17:19:35,510 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.6.Final-redhat-1
17:19:35,661 INFO  [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'
[Host Controller] 17:19:36,107 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.6.Final-redhat-1
[Host Controller] 17:19:36,258 INFO  [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1
[Host Controller] 17:19:36,317 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) starting
[Host Controller] 17:19:36,908 INFO  [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.13.GA-redhat-1
[Host Controller] 17:19:36,911 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.13.GA-redhat-1
[Host Controller] 17:19:36,979 INFO  [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.3.4.Final-redhat-1
[Host Controller] 17:19:37,000 INFO  [org.jboss.as.remoting] (MSC service thread 1-6) JBAS017100: Listening on [::1]:19999
[Host Controller] 17:19:38,154 ERROR [org.jboss.as.controller.management-operation] (Host Controller Service Threads - 41) WFLYCTL0013: Operation ("read-master-domain-model") failed - address: ([]): java.lang.NullPointerException: NPE for [
[Host Controller]     ("profile" => "full-ha"),

Looked again at the failed test case.
Surprisingly, failed test case passed on windows without this fix but after re fetch from base. Looking at details, pull request doesn't seems to be required due to index.jsp have LF characters and test case expected result is properly set with "\n".
I'm unable to undo approval.

Closing, as it appears to be unessesary and causes CI failures


[BUG] Folder creating error

Describe the bug
I'm trying to download photo with any folder in args but it can't download the photo (not only photo)
BTW without "folder" arg it works
To Reproduce
cl = Client()
cl.login(INST_USERNAME, INST_PASSWORD)
pk = cl.media_pk_from_url(URL)
path = cl.photo_download(pk, folder='/source') # i tried 'source', r'/source', r'\source' and other

Traceback
It does't raise any error but it's my log:
2023-07-10 16:33:16,803 INFO [None] [401] GET https://www.instagram.com/graphql/query/?variables=%7B%22shortcode%22%3A%22Cubp6Tot8hX%22%2C%22child_comment_count%22%3A3%2C%22fetch_comment_count%22%3A40%2C%22parent_comment_count%22%3A24%2C%22has_threaded_comments%22%3Afalse%7D&query_hash=477b65a610463740ccdb83135b2014db
2023-07-10 16:33:20,078 INFO [None] [401] GET https://www.instagram.com/graphql/query/?variables=%7B%22shortcode%22%3A%22Cubp6Tot8hX%22%2C%22child_comment_count%22%3A3%2C%22fetch_comment_count%22%3A40%2C%22parent_comment_count%22%3A24%2C%22has_threaded_comments%22%3Afalse%7D&query_hash=477b65a610463740ccdb83135b2014db
2023-07-10 16:33:23,356 INFO [None] [401] GET https://www.instagram.com/graphql/query/?variables=%7B%22shortcode%22%3A%22Cubp6Tot8hX%22%2C%22child_comment_count%22%3A3%2C%22fetch_comment_count%22%3A40%2C%22parent_comment_count%22%3A24%2C%22has_threaded_comments%22%3Afalse%7D&query_hash=477b65a610463740ccdb83135b2014db
2023-07-10 16:33:24,357 INFO https://i.instagram.com/api/v1/media/3142289491741886551/info/
2023-07-10 16:33:24,668 INFO XXXXXX [200] GET https://i.instagram.com/api/v1/media/3142289491741886551/info/ (2<IP_ADDRESS>.75, OnePlus 6T Dev)

Expected behavior
I excpected for a photo in a folder but nothing
Desktop (please complete the following information):

OS: Windows 11
Python version 3.11.0
instagrapi version 1.17.13

Additional context
And i'm afraid of some INFO [None] [401] GET ...
Is it okey?

But I have a directory :D

Do you have a /folder directory on Windows? At the root of what disk? I don’t know Windows, but it seems that you need to specify the full path there, starting from the disk name, figure it out yourself

OMG okey the folder error fixed
But what about "None 401 GET..."?

Any url to instagram like
https://www.instagram.com/p/CtzKdjMvh3e/?igshid=MzRlODBiNWFlZA==

Works fine:
In [14]: URL = "https://www.instagram.com/p/CtzKdjMvh3e/?igshid=MzRlODBiNWFlZA=="

In [15]: pk = cl.media_pk_from_url(URL)

In [16]: pk
Out[16]:<PHONE_NUMBER>077312990

In [17]: cl.media_info_v1(3130892177077312990)
Out[17]: Media(pk='3130892177077312990', id='3130892177077312990_3152631628', code='CtzKdjMvh3e', taken_at=datetime.datetime(2023, 6, 22, 16, 30, 56, tzinfo=datetime.timezone.utc), media_type=1, image_versions2={'candidates': [{'width': 1080, 'height': 608, 'url': 'https://scontent-zrh1-1.cdninstagram.com/v/t51.2885-15/355257897_577961381165767_45367380427411658_n.jpg?stp=dst-jpg_e35_s1080x1080&_nc_ht=scontent-zrh1-1.cdninstagram.com&_nc_cat=107&_nc_ohc=Mt7BYUsk7usAX9IUwA-&edm=ALQROFkBAAAA&ccb=7-5&ig_cache_key=MzEzMDg5MjE3NzA3NzMxMjk5MA%3D%3D.2-ccb7-5&oh=00_AfDOfHhQMgPohNm1A34bJAoeJQguz5z-wRd0XA8uquhPiQ&oe=64B4A57B&_nc_sid=fc8dfb', 'scans_profile': 'e35', 'estimated_scans_sizes': [15212, 30424, 45636, 60848, 76061, 85112, 108308, 123098, 136910]}, {'width': 360, 'height': 202, 'url': 'https://scontent-zrh1-1.cdninstagram.com/v/t51.2885-15/355257897_577961381165767_45367380427411658_n.jpg?stp=dst-jpg_e35_s360x360&_nc_ht=scontent-zrh1-1.cdninstagram.com&_nc_cat=107&_nc_ohc=Mt7BYUsk7usAX9IUwA-&edm=ALQROFkBAAAA&ccb=7-5&ig_cache_key=MzEzMDg5MjE3NzA3NzMxMjk5MA%3D%3D.2-ccb7-5&oh=00_AfBCgi6-g-8UitZ8lUQzgVyOg0eVidrpCebSntLDzlJgDg&oe=64B4A57B&_nc_sid=fc8dfb', 'scans_profile': 'e35', 'estimated_scans_sizes': [2108, 4217, 6326, 8435, 10544, 12695, 366362, 18980, 18980]}]}, product_type='feed', thumbnail_url=HttpUrl('https://scontent-zrh1-1.cdninstagram.com/v/t51.2885-15/355257897_577961381165767_45367380427411658_n.jpg?stp=dst-jpg_e35_s1080x1080&_nc_ht=scontent-zrh1-1.cdninstagram.com&_nc_cat=107&_nc_ohc=Mt7BYUsk7usAX9IUwA-&edm=ALQROFkBAAAA&ccb=7-5&ig_cache_key=MzEzMDg5MjE3NzA3NzMxMjk5MA%3D%3D.2-ccb7-5&oh=00_AfDOfHhQMgPohNm1A34bJAoeJQguz5z-wRd0XA8uquhPiQ&oe=64B4A57B&_nc_sid=fc8dfb', ), location=None, user=UserShort(pk='3152631628', username='boeing', full_name='The Boeing Company', profile_pic_url=HttpUrl('https://scontent-zrh1-1.cdninstagram.com/v/t51.2885-19/43914117_558426674627648_8801360730877067264_n.jpg?stp=dst-jpg_s150x150&_nc_ht=scontent-zrh1-1.cdninstagram.com&_nc_cat=1&_nc_ohc=XCPzh_v_WckAX90gbKO&edm=ALQROFkBAAAA&ccb=7-5&oh=00_AfC43ccMRgn2dY2nOAtlCdWWjcSskuAyCK4j9IxOJgNHSA&oe=64B4B000&_nc_sid=fc8dfb', ), profile_pic_url_hd=None, is_private=False, stories=[]), comment_count=192, comments_disabled=False, commenting_disabled_for_viewer=False, like_count=19075, play_count=0, has_liked=False, caption_text='The first 787 #Dreamliner for #IraqiAirways arrived home in Baghdad today. 🛬😍\n\nOne of the oldest airlines in the world, and the second oldest in the Middle East, Iraqi Airways now boasts a 42-strong 💪 Boeing fleet!', accessibility_caption=None, usertags=[], sponsor_tags=[], video_url=None, view_count=0, video_duration=0.0, title='', resources=[], clips_metadata={})

In [18]: path = cl.photo_download(pk, folder='/tmp')

In [19]: path
Out[19]: PosixPath('/tmp/boeing_3130892177077312990.jpg')

In [20]: !stat /tmp/boeing_3130892177077312990.jpg
  File: /tmp/boeing_3130892177077312990.jpg
  Size: 91955           Blocks: 184        IO Block: 4096   regular file
Device: 902h/2306d      Inode: 40974856    Links: 1
Access: (0664/-rw-rw-r--)  Uid: ( 1001/  adw0rd)   Gid: ( 1001/  adw0rd)
Access: 2023-07-13 10:59:11.721263520 +0000
Modify: 2023-07-13 10:59:11.749263771 +0000
Change: 2023-07-13 10:59:11.749263771 +0000
 Birth: 2023-07-13 10:59:11.721263520 +0000


[editor] Remove mako variables for editor id and notebooks as well as the old notebooks listing page

In this commit I'm removing the editor_id and notebooks that gets set from the backend when opening the editor. The editor ID is now taken from the url parameter and notebooks isn't actually used anymore.
As part of this I'm also removing the notebooks listing page which should be considered dead code as it's no longer reachable from the UI or via URL.
This is part of the effort of removing inline script and our goal of moving towards CSR.
Manually tested and unit tests introduced for the changes

Changes looks good, but I don't understand the notebook changes. Why are we removing the notebooks listing page? If notebooks aren't actually used anymore then why are we keeping the NotebookViewModel?

That's the problem with not removing code once it's "dead", the notebooks listing page was detached from the UI at some point and left behind. It's no longer used as we have the assist documents panel and the dedicated documents page that does the same trick.

Changes looks good, but I don't understand the notebook changes. Why are we removing the notebooks listing page? If notebooks aren't actually used anymore then why are we keeping the NotebookViewModel?

That's the problem with not removing code once it's "dead", the notebooks listing page was detached from the UI at some point and left behind. It's no longer used as we have the assist documents panel and the dedicated documents page that does the same trick.
I tried my best to get it to render but it's broken and likely has been for 5 or so years.

Got it


Rotating not working correctly with Dragging

Hi Guys,
i have some wired Problems with the rotatable Plugin.
This happens also on the normal demo page.
http://godswearhats.com/jquery-ui-rotatable/demo.html
When i start to drag and then rotate all look fine but when i try it a second or third time the rotation is really wired. Look at the Video:
https://youtu.be/AQqBJRco7VE
I hope someone can fix this.
Thank You,
Daniel

Forget it you're noob!!!!!!!!!

I have the same issue. Please fix @godswearhats 👍

https://github.com/godswearhats/jquery-ui-rotatable/issues/68

https://jsfiddle.net/fwv34xux/

Fixed with Commit https://github.com/godswearhats/jquery-ui-rotatable/commit/bcbadef03ebff144ee07727af40afd4aac65d972


PullRefreshto GridView

Dear Mark,
I want to use your algorithm with listview to gridview. Please help me
Thank you so much.

I want to use your solution to gridview,
because gridview don't support add header and footer so that i implemented it.
And continue ?
What is need consider ?
Thanks,


Failed to start Determine the Kubelet Image Version

Issue Report Template
Tectonic Version
1.7.1-tectonic.2.
CoreOS Version
1465.6.0
MatchBox Version
0.6.1
Environment
Bare Metal , 1 master, 1 worker
hardware: Dell Desktop for test
Expected Behavior
Finish the installation process of tectonic installer
Actual Behavior
Install Failed on bootstrapping state (see log file below)
null_resource.bootstrap: Still creating... (20m10s elapsed)
null_resource.bootstrap (remote-exec): A dependency job for tectonic.service failed. See 'journalctl -xe' for details.
Error applying plan: 1 error(s) occurred: * null_resource.bootstrap: 1 error(s) occurred: * Script exited with non-zero exit status: 1
Reproduction Steps

Start tectonic Installer
Configure and submit
Boot master on network (Pxe) OK
Reboot of master OK
5 Master connected
6 Boot Worker on network
7 Reboot of worker OK
8 Worker connected
9 After 20 min Installer failed

Other Information
After Ssh connect to worker and master we saw 'journalctl -xe' (see journalworker.txt and journalmaster.txt)
On worker we saw : "Failed to start Determine the Kubelet Image Version"
Log File from tectonic
tectonic-sodicluster01.txt
Log File from worker
journalworker.txt
Log File from master
journalmaster.txt

What does sudo journalctl -e -u bootkube says on master?

Thanks for answer so quickly... See result and file attached.
ug 22 13:19:47 master01.sodifrance.fr bash[1349]: [ 1500.807584] bootkube[5]: Error: API Server is not ready: timed out waiting for the con
Aug 22 13:19:47 master01.sodifrance.fr bash[1349]: [ 1500.808138] bootkube[5]: API Server is not ready: timed out waiting for the condition
Aug 22 13:19:47 master01.sodifrance.fr systemd[1]: bootkube.service: Main process exited, code=exited, status=1/FAILURE
Aug 22 13:19:47 master01.sodifrance.fr systemd[1]: Failed to start Bootstrap a Kubernetes cluster.
Aug 22 13:19:47 master01.sodifrance.fr systemd[1]: bootkube.service: Unit entered failed state.
Aug 22 13:19:47 master01.sodifrance.fr systemd[1]: bootkube.service: Failed with result 'exit-code'.

journbootkub.txt

From a quick look, it looks like bootstrapping the control plane on master is failing. However I don't  see any specific failure entry in the log, just generic connection failures on both master and worker.
The suspicious part is that the kubelet seems to detect the assets for the bootstrapping control plane and creating the pods, but never progressing from there. I'm not sure what could be causing this behavior. Did the docker/containerd by chance get stuck or killed while trying to execute those pods?

It actually doesn't look like the kubelet starts any pods at all. The service successfully downloads the bootkube container and runs bootkube start, but nothing ever happens after that. It could be that the kubelet is erroring or dead and unable to start any of the bootstrap control plane pods. Could you post the output of sudo journalctl -eu kubelet?

@tlarmier could you post your tfvars file? That would be helpful for debugging.

terraform.tfvars.txt
thanks

We found on the master log multiple acces to this adress:
Get https://masterkbn.sodifrance.fr:443
This machine masterkbn.sodifrance.fr is our matcbox server ...
We havent no 443 port open on this machine, in https we use only the 8081 standart port for matchbox...
The question is what master and worker expect to found on this address ???
please help !!!

@tlarmier it expect the k8s api-server to show up there. Going through your tfvars, it looks like you may have a misconfigured entry pointing tectonic_metal_controller_domain to it.

We made a mistake on DNS Name declaration during configuration for workers and controllers....
It's OK Now.
Thanks for help.


[Feature Request] /customize [CUSTOMIZATION NAME] [TARGET]

Would love to have a command to assign the customization I'd like by using macros to make the process simple just like penumbra does it.
Their command is:
Use with /penumbra collection [Collection Type] | [Collection Name] | <Identifier>
》 Valid Collection Types are Base, Ui, Selected, Individual, and all those selectable in Character Groups.
》 Valid Collection Names are None, all collections you have created by their full names, and Delete to remove assignments (not valid for all types).
》 If the type is Individual you need to specify an individual with an identifier of the form:
》》》 <me> or <t> or <mo> or <f> as placeholders for your character, your target, your mouseover or your focus, if they exist.
》》》 p | [Player Name]@<World Name>, if no @ is provided, Any World is used.
》》》 r | [Retainer Name]
》》》 n | [NPC Type] : [NPC Name], where NPC Type can be [M]ount, [C]ompanion, [A]ccessory, [E]vent NPC, or [B]attle NPC.
》》》 o | [NPC Type] : [NPC Name] | [Player Name]@<World Name>.

It'd be incredible to change what customization to use with a macro and combine it with other macros to easily change characters on the fly by the click of a button

I tried to use this new feature with  instead of Character name but it didn't work. Am I using it wrong? If  or  is not supported, would it be possible to support it? This way the macros would be only one instead of one per character

Can you open /xllog and show us what it says when you try it with those commands? I have no idea how these are translated, I have a suspicion why they dont work, but that would help!

Also would it be possible to instead of having the Scale assigned to a character, just replace the name of the owner of the scale so they are re-usable?

Not entirely sure what you mean by that?

Wait but  is not a valid tag,  is

So right now the macro works as a toggle. If the Scale exist for X character then the macro turns it on. My suggestion would be to instead of being a toggle, use the macro to replace the name of the character assigned to the Scale, so that way Scales are reusable among other characters by using the macro.

So right now the macro works as a toggle. If the Scale exist for X character then the macro turns it on. My suggestion would be to instead of being a toggle, use the macro to replace the name of the character assigned to the Scale, so that way Scales are reusable among other characters by using the macro.

No sorry, while obviously possible changing things via Commands is not something I'd want, at least not in that format. Just duplicate that scale and give it that other characters name. We COULD allow a placeholder as character name entirely, but that would require a check. Cant say at the top of my head how much work it would be.
As for the log, thank you! Its about as I expected, will have to look at how Chat handles the tags then and implement that.

So right now the macro works as a toggle. If the Scale exist for X character then the macro turns it on. My suggestion would be to instead of being a toggle, use the macro to replace the name of the character assigned to the Scale, so that way Scales are reusable among other characters by using the macro.

No sorry, while obviously possible changing things via Commands is not something I'd want, at least not in that format. Just duplicate that scale and give it that other characters name. We COULD allow a placeholder as character name entirely, but that would require a check. Cant say at the top of my head how much work it would be.
As for the log, thank you! Its about as I expected, will have to look at how Chat handles the tags then and implement that.

A placeholder would work too, I really wouldn't mind it. Some clothes need different scales so it's really annoying to change manually and with different characters. I would REALLY appreciate it.
Thank you so much for at least considering it. And Thank you for checking into my < me> issue.

For the clothing its planned to sometime have conditional application instead of just names, like youd see with XLHeels. That is still along way out though.

For the clothing its planned to sometime have conditional application instead of just names, like youd see with XLHeels. That is still along way out though.

This would also work for those who want to show different characters with different scales. Like having "Glamourer Alts" instead of having a brand new character. It's not only clothes but totally different characters as well.


Update Config.java

Change constructor to use new io

Thanks for the pull request! I've merged the new message. I'm not sure I understand the advantage of this way of doing io. Would you mind elaborating?

Apart from the cleaner syntax (from my point of view) using nio is non-blocking, so operations that do not depend on that file being read can be done while waiting for it. Additionally - taken from the nio Wikipedia page - "In most operating systems, provided the particular area of memory has the right properties, transfer can take place without using the CPU at all."


nav  bar has a responsive issue when moving from mobile to desktop

I am having an issue with the nav bar when it goes from the desktop to mobile. I think the issue is coming from the media query. I have made changes to the media query but have not had any luck maybe someone can give me a hand to fix this issue.

I can help with this issue.  creating a more responsive nav bar for mobile

Great, thanks @egpennington ! Assigning it to you now.


Wiki bug: File watching issues for Logging (remote)

https://github.com/microsoft/vscode/wiki/File-Watcher-Issues#logging-local says that viewing remote file watcher issues should be done by checking the Log (Remote Server) output channel. But it does not exist.

Note that I am trying to find file watching issues in regards to using WSL, and that the Source Control view does not refresh after saving files.

Does this help?
Logging (remote)
!!! This is ONLY when you open a remote workspace (WSL, Docker, SSH), for local see above !!!
We provide logging for file events when you enable verbose logging. Steps are:

open VSCode on the remote workspace that shows the issue
select View | Command Palette...
select Developer - Set Log Level...
pick Trace
select View | Output
select Log (Remote Server) from the dropdown
attach the output when doing the operation that exhibits the issue

@bpasero no. That was the part I went through and followed. You can see it says:

select Log (Remote Server) from the drop down.

As you can see in the screenshot, there is no Log (Remote Server) for me to select.

True, its called Server now. Updated the wiki.


Update contract runtime host functions to polkadot v0.9.39

Let's adapt to latest contract env first before upgrading ask all dependencies and some break changes.
This can minimize break change, but cannot completely avoid it.

#268


Dockerfile??

As per the documentation in "https://openvinotoolkit.github.io/anomalib/getting_started/installation/docker/index.html#".....
"Build the Docker Image
To use anomalib with Docker, you can build a Docker image containing anomalib all its dependencies from the provided Dockerfile. To this end, navigate to the anomalib root directory (the one containing the Dockerfile) and build the Docker image with"
I could not find the Dockerfile.

It is here
https://github.com/openvinotoolkit/anomalib/blob/main/.ci/Dockerfile

It is here https://github.com/openvinotoolkit/anomalib/blob/main/.ci/Dockerfile

Thank you. My ubuntu file explorer was not showing it up, as it was inside a ".ci" folder and it was hidden. I got it now......


Switch to use cabal-cache-s3

@newhoggy Lift stuff seems to be fixed in the latest main (I merged a PR recently), it should work if you rebase


api: v2alpha1: Fix issue with filtering by address in transaction service

Transactions that don't have results yet can't be found by address field. This PR adds Group filtering to the builder to allow filtering by both address and principal at the same time.

bors merge


Parquet spams output during testing.

Parquet produces lots of output when running tests such as:
Mar 17, 2015 2:54:14 AM INFO: parquet.hadoop.ColumnChunkPageWriteStore: written 33B for [field922] BINARY: 4 values, 2B raw, 2B comp, 1 pages, encodings: [PLAIN_DICTIONARY, BIT_PACKED], dic { 1 entries, 7B raw, 1B comp}
Mar 17, 2015 2:54:14 AM INFO: parquet.hadoop.ColumnChunkPageWriteStore: written 33B for [field923] BINARY: 4 values, 2B raw, 2B comp, 1 pages, encodings: [PLAIN_DICTIONARY, BIT_PACKED], dic { 1 entries, 7B raw, 1B comp}
Mar 17, 2015 2:54:14 AM INFO: parquet.hadoop.ColumnChunkPageWriteStore: written 33B for [field924] BINARY: 4 values, 2B raw, 2B comp, 1 pages, encodings: [PLAIN_DICTIONARY, BIT_PACKED], dic { 1 entries, 7B raw, 1B comp}

Not sure if your case is exactly the same as mine, but you could suppress parquet logging through slf4j jul bridge. (and then configure slf4j as you like)

import java.util.logging._
import org.slf4j.bridge._

object ParquetLogger {

  def bridgeToSlf4j() = {
    // Getting the parquet log to force initialization of the jul Logger that it uses, so that we can remove the handlers and install the bridge.
    parquet.Log.getLog(classOf[String])
    SLF4JBridgeHandler.removeHandlersForRootLogger();
    SLF4JBridgeHandler.install();
  }
}

Do you know why the log4j config is not working to reduce to the log output?

Parquet uses jul and some compile flag if I remember correctly
On Tue 17 Mar 2015 at 23:51 Stephan Hoermann<EMAIL_ADDRESS>wrote:

Do you know why the log4j config is not working to reduce to the log
output?
—
Reply to this email directly or view it on GitHub
https://github.com/CommBank/ebenezer/issues/89#issuecomment-82631693.

@RayRoestenburg thank you that is very helpful.
Here are some useful links to help me or someone else when they deal with this:

https://groups.google.com/forum/#!topic/parquet-dev/Eb0btS78M5g
http://www.slf4j.org/legacy.html#jul-to-slf4j

No worries
On Wed 18 Mar 2015 at 00:55 Stephan Hoermann<EMAIL_ADDRESS>wrote:

@RayRoestenburg https://github.com/RayRoestenburg thank you that is
very helpful.
Here are some useful links to help me or someone else when they deal with
this:

https://groups.google.com/forum/#!topic/parquet-dev/Eb0btS78M5g
http://www.slf4j.org/legacy.html#jul-to-slf4j

—
Reply to this email directly or view it on GitHub
https://github.com/CommBank/ebenezer/issues/89#issuecomment-82645758.


Copy and Paste Doesn't Preserve Formatting

To reproduce:

Go to https://jsfiddle.net/r2os14qk/
In the single field, type in '1233423432'
Select all the characters in the field and copy (e.g. ctrl + c)
Paste into any text editor

Expected Results:
The value pasted in the text editor is '(123) 342-3432' (with formatting preserved).
Actual Results:
The value pasted in the text editor is '1233423432' (without formatting preserved).

What browser are you using? that is working perfectly fine on Chrome, i copy 'n' pasted your examples, both with and without the actual formatting you expect, and it's pasted as the expected result always

Weird. I'm using Chrome, Version 73.0.3683.86 (Official Build) (64-bit), on Windows 10. I just tried with a guest profile (no extensions activated), and it's reproducible.
I also just tried in Firefox, and it's reproducible.

Sorry about that, i read it the wrong way...
In any case, this line here tells you how to get what you want: https://github.com/nosir/cleave.js/blob/master/src/Cleave.js#L202

Awesome, worked like a charm! Thanks!


Can't find system packages definition.

Environment data
dotnet --info output:
.NET SDK:
Version:   7.0.203
Commit:    5b005c19f5
Runtime Environment:
OS Name:     Mac OS X
OS Version:  13.2
OS Platform: Darwin
RID:         osx.13-arm64
Base Path:   /usr/local/share/dotnet/sdk/7.0.203/
Host:
Version:      7.0.5
Architecture: arm64
Commit:       8042d61b17
VS Code version:
1.79.2
695af097c7bd098fbf017ce3ac85e09bbc5dda06
arm64
C# Extension version:  v2.0.212
Actual behavior
when update c# to pre-release  v2.0.212, can't find any system packages definition:
https://github.com/dotnet/vscode-csharp/assets/26156999/ef05f4dd-ae71-47be-9b26-0ba973df8e4e

No repro on a windows device, may be mac specific.

@zhen8838 Did you also have the Dev Kit extension installed? Either way, did you have any errors in the C# output log?

(it's also possible this is now fixed by the change @tmeschter made around ensuring design time builds actually run CoreCompile)

now I switch to the old version.

now I switch to the old version.

@zhen8838 Do you mean you switched to an older version to work around this, or it's working for you now on new versions?


show y axis of reflectivity plots in scientific notation (10 to a power)

It has been requested by @hoogerheide that the y-axis number formatting for reflectivity plots be changed to a power of 10, e.g. $10^{-6}$
What it looks like now:

What it would look like after this PR:

Oh that's a good question... Not sure if plotly supports unicode annotations

It definitely does...I use one for Angstroms in the molgroups custom plots


Bug fix for hp restriction matrix

This PR fixes the bug described in https://github.com/mfem/mfem/issues/2779.

I can confirm that with this all the unit tests for the variable-order  true-transfer operator in the case of strict conformity are successful!
I do have one question here, maybe for @jakubcerveny. Shouldn't GetConfomingRestriction() always return the hpRestriction for a variable order FiniteElementSpace. In other words, will R (and not Rhp) be useful anywhere in the  code in this case?

Thanks for fixing this!
As for the restriction matrix, my hopes were initially also that R would simply be R_hp in the case of variable orders, but it turns out the classic R matrix is still needed for essential DOF identification/elimination, which gets spoiled by the extra elements when the R_hp matrix is treated as a Boolean matrix :-|

Thanks @dylan-copeland !
Can we mark it as ready-for-review?

As for the restriction matrix, my hopes were initially also that R would simply be R_hp in the case of variable orders, but it turns out the classic R matrix is still needed for essential DOF identification/elimination, which gets spoiled by the extra elements when the R_hp matrix is treated as a Boolean matrix :-|

Thanks @jakubcerveny

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

Merged in next for testing...


Add failing Revwalk test for fileHistoryWalk(*)

It seems that Revwalk's fileHistoryWalk(*) function does not find merge commits.
 However, fileHistoryWalk(*) will not find this commit as shown by the attached failing test.
This bug makes fileHistoryWalk(*) unsuitable for creating a graphical log of a file. Do you have any ideas, @implausible?

Okay. After looking at the code, it seems like the fileHistoryWalk(*) function will just ignore any commit that has more than one parent. I'm not sure what the reasoning behind this is though.
if (parents > 1) {
  git_commit_free(nextCommit);
  continue;

walker.push(commitA);
// only check the A commit
walker.fileHistoryWalk("package.json", 1);

So what should happen when the user runs this code where A is a merge commit? Here are a couple of scenarios I have thought of. The following all assume a common ancestor exists for the merge commit A.
Scenario 1 - YES

A   Merged content from both branches
|\
B | Modified
\ C Modified
 \|
  D Unmodified

Scenario 2 - NO

A   Merged in branch containing commit C
|\
B | Modified
\ C Unmodified
 \|
  D Unmodified

Scenario 3 - YES

A   Merged in branch containing commit C
|\
B | Unmodified
\ C Modified
 \|
  D Unmodified

Scenarios 2 and 3 are very close but it's an issue of which branch is the master and which branch is the feature. Let's assume commit B is in the master branch and commit C is in the feature branch.
So, if you're merging in a feature branch and that branch has modified package.json (scenario 3) then I feel like the merge commit should be flagged as you're bringing in changes to the file into your current branch. On the other hand, if the change is in feature and not in the master then I'm inclined to say the merge commit shouldn't be flagged as the merge commit is not bringing in any new changes to the file.
Of course, the same logic would apply if the merge commit contains three or more parents. If any of the branches that are being merged in have modified the file, then the merge commit should be flagged.
Scenario 4 - YES

A   Merged content from both branches
|\
B | Unmodified
| C Unmodified
D | Modified
| E Modified
 \|
  F Unmodified

Scenario 5 - NO

A   Merged content from both branches
|\
B | Unmodified
| C Modified again, but reverts the changes from E
D | Modified
| E Modified
 \|
  F Unmodified

Scenario 6 - YES

A   Merged and further modified in A, such as by amending the commit with further changes
|\
| B Modified
|/
C   Unmodified

Scenario 7 - NO

A   Fast-forwarded merge commit with no further content change
|\
| B Modified
|/
C   Unmodified

Scenario 8 - NO

A   Fast-forwarded merge commit with no further content changes
|\
| B Modified
|/
C   Modified

The following scenarios have no common ancestors. This unique kind of merge commit does exist in the NodeGit repository.
Scenario 9 - YES

 A   Merged in branch containing commit C, creating the file with the content of C
/ \
B  | File did not exist
|  C Modified
|  |

Scenario 10 - NO

 A   Merged in branch containing commit C, file is of course unchanged
/ \
B  | Modified
|  C File did not exist
|  |

Yes. So when we developed this, we originally did show merge commits, but for some reason or another, that was shot down from one of the main NodeGit crowd so I ripped it out. Definitely is a bug now that we've used it and considered what the implications of that decision were. Thanks for adding the failing test. We'll need to revise the fileHistoryWalk to include merge commits.

Took a little more time to digest what you're saying. I think your approach of diffing parents until we can prove there is no file change in a merge commit (octopus like commits) should suffice. We should move in the direction that tests merge commit parent diffs until all parents have been tested or a the file change was discovered. Thanks so much for breaking out this scenario for me.

Hmm, so I did some playing around with this today. I think maybe we should just try removing the skip merge commits statement all together. We will have the merge commit be treated like any other commit and diff against it's 0th parent. I think that's what git log does anyway.

Talked to @implausible a little about this on Slack. Many moons ago I implemented git log myself and found that it wasn't always enough to just compare the merge commit its first (0-th) parent.
$ git init

$ touch a.txt

$ git add a.txt

$ git commit -m "Add"
[master (root-commit) d38b8cb] Add
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 a.txt

$ git checkout -b branch
Switched to a new branch 'branch'

$ echo "a" > a.txt

$ git commit -a -m "Mod"
[branch fe5b100] branch #time Mod
 1 file changed, 1 insertion(+)

$ git checkout master
Switched to branch 'master'

$ git merge --no-ff branch

$ git log a.txt

If you perform the following, you will actually notice that the merge commit is not included in git log even though from a comparison point of view it has changed.


2945 remove couch http cors

Remove second implementation of CORS (couch_http_cors) in favor of chttpd_cors. This refactoring is done in order to make sure we always call chttpd_cors:headers for backdoor interface as well as chttpd interface.
This PR depends on https://github.com/apache/couchdb-chttpd/pull/101

I'm all +1 for this, except that I'm not sure if this is correct design-wise solution. Because we actually bring bits from cluster httpd interface to the backdoor one. And since chttpd uses couch_httpd internally, this makes circular dependency between them.
What I think would be correct is to move common httpd bits into own package. We already have couch-httpd repository as empty and it name sounds to be good place for such kind of things. And then we can have
     couch-httpd
     ^         ^
     |         |
  chttpd couch_httpd

model instead of
chttpd <--> couch_httpd

In mid/long term couch-httpd app can help to isolate mochiweb from rest CouchDB and simplify migration to some else web framework: webmachine, cowboy, whatever it'll be.
What do you think about this?

@kxepal: https://github.com/apache/couchdb-couch-httpd is not empty. I'm not brave enough to pull off 3-ways refactoring in a reasonable time. Are there any plans to keep the current content of couchdb-couch-httpd?

@iilyak Oh, I forgot about those. That content was a part of contributed RCouch fork, where couch_http* modules were moved into own app.
Currently it doesn't get used anyhow. I don't remember if there are any valuable features to backport (except refactoring), but since it's isolated into own branch, I think we can use use master branch for our needs while rcouch bits remains untouched till we figure out what to do with them.
@rnewson @davisp @chewbranca @eiri - what's your opinion on this?

My understanding is that this refactoring addressing the problem we have with CORS for some of end-points (_sessions ?) that hasn't been fixed by previous CORS' PR?
On a big scale of things I agree that having common couch-httpd lib is a great idea, but if this change is not a cleanup, but a fix, I think we can do that after getting it in, not instead.

If this fixes a specific issue then we should call it out. The commit message is vague enough it sounds like just a style/debt thing. I think we're all in agreement that we want to dedupe everything and this is only a very small part of that. If this is just a small part of the dedupe then I'd delay this until we do the whole dedupe. However if its a fix for a problem them I'm fine pulling it in so long as we make sure and explain the specific problem we're solving so that future us are more prepare when we get to the eventual dedupe work.

@kxepal @iilyak @eiri @davisp in general I think the approach of deleting couch_httpd_cors in favor of chttpd_cors is correct and is fine to do here. The chttpd_cors implementation was based off of couch_httpd_cors with a number of changes cleaning things up and improving the implementation. We talked about whether to remove couch_httpd_cors in the past but the chttpd_cors implementation did not support the same multi-host config format that already existed, a problem @iilyak has rectified in this set of PRs, so in general I'm +1 to this change.
For this PR, does it make sense to delete the CORS implementation but leave in the CORS tests?
As for introducing a third *_httpd library layer, I think we would be better off spending the time consolidating down to a single HTTP stack and removing the current dichotomy as quickly as we can.

@chewbranca: For this PR, does it make sense to delete the CORS implementation but leave in the CORS tests?

Traditionally we put integration tests related to other repositories into couchdb-couch application see chttpd_endpoints_tests.erl. So the old CORS test suite is just lifted to become an integration suite.

I wish to break this tradition, but don't have enough strength and will to rework whole the tests once again. For now it doesn't matter where to place integration tests since for each app we build full CouchDB to run the tests. So integration tests could be places wherever, but I would agree that it's quite strange to see chttpd_* tests in couch app and vice versa.

+1


Image not written to disk

We have been trying docunotion and ran into an issue where an image that was being downloaded was not making it to the disk correctly.
I tracked it down to this line:
https://github.com/sillsdev/docu-notion/blob/f1176c574cce15244b65dd77c43de2e791fe361c/src/images.ts#L204
Changing it to fs.writeFileSync(path, buffer) fixes the issue.
It's unclear why the code does not await for the file to be written, is there any reason for that?

There was an image that would not make it to disk.
It would simply be missing, and then the docusaurus build would fail with a broken link to it. The documentation would properly reference the file, just that it wasn't there.
Regarding the optimization: it seems odd that writing files on modern SSD drives would need this, and it would make any difference.

Regarding the optimization: it seems odd that writing files on modern SSD drives would need this, and it would make any difference.

I haven't profiled this. Bu in theory, it should make a difference: SSDs are faster than mechanical drives, but still very, very slow compared to code. After all, the premise here is that the problem you encountered is that the async call failed to finish in time and so it didn't complete.
To fix the problem you encountered, so we should collect up the promises from the async write and then await Promise.all(promises) at some point.

Even mechanical drives have caches, so this impact is mostly theoretical.
Here's a benchmark script:
const fs = require("fs/promises");
const { writeFileSync } = require("fs");
const path = require("path");

// Benchmark Helper Function
async function benchmark(fn, label) {
  const start = process.hrtime.bigint();
  await fn();
  const end = process.hrtime.bigint();
  console.log(`${label} took ${(end - start) / 1000000n} ms`);
}

// Generate 100KB of data
const dataSize = 100 * 1024; // 100KB
const data = "A".repeat(dataSize); // Repeat character 'A' to make up 100KB
const iterations = 1000; // How many times to write the file for benchmarking
const tempDir = "./temp"; // Directory to store test files

// Ensure temporary directory exists
async function ensureDirExists() {
  try {
    await fs.mkdir(tempDir, { recursive: true });
  } catch (err) {
    console.error("Error creating directory", err);
  }
}

// Async Write Function with Promise.all
async function writeFilesAsync() {
  const promises = [];
  for (let i = 0; i < iterations; i++) {
    const filePath = path.join(tempDir, `test-file-async-${i}.txt`);
    promises.push(fs.writeFile(filePath, data));
  }
  await Promise.all(promises);
}

// Sync Write Function
function writeFilesSync() {
  for (let i = 0; i < iterations; i++) {
    const filePath = path.join(tempDir, `test-file-sync-${i}.txt`);
    writeFileSync(filePath, data);
  }
}

// Warm-Up Function
async function warmUp(fn, label, runs = 2) {
  console.log(`Running ${runs} warm-up runs for ${label}...`);
  for (let i = 0; i < runs; i++) {
    await fn(); // Perform the warm-up run
  }
  console.log(`${label} warm-up completed.`);
}

// Run the benchmarks
(async () => {
  await ensureDirExists();

  // Warm-up and Benchmark for Async (Promise.all) Write
  await warmUp(writeFilesAsync, "Async (Promise.all)");
  await benchmark(writeFilesAsync, "Async (Promise.all) file write");

  // Warm-up and Benchmark for Sync Write
  await warmUp(writeFilesSync, "Sync");
  await benchmark(writeFilesSync, "Sync file write");
})();

Writing 1000 * 100KB files takes less than 100ms on my machine:
Running 2 warm-up runs for Async (Promise.all)...
Async (Promise.all) warm-up completed.
Async (Promise.all) file write took 73 ms
Running 2 warm-up runs for Sync...
Sync warm-up completed.
Sync file write took 102 ms

The async version is slightly faster, but it still takes less than 1 ms per write.
It takes 0.1 seconds to write 1000 images with writeFileSync.


Debounced kube updated alpha rebased on master plus delay

Chris's  debounced-kube-updated-alpha
rebased on master with Jacob fix
cherry picked changes from "line delay" PR  https://github.com/logdna/logdna-agent-v2/pull/537

cc: @c-nixon @jakedipity


feedtools.js link in documentation returns 404 page

The link to feedtools.js in the section https://github.com/scripting/river5#wheres-the-code returns a 404 page not found error now that it is no longer part of this repo.

Thanks for the report! Fixed.


Cleanup GNOME3 default applications

Describe the bug
Currently, the gnome3 module automatically adds the following to environment.systemPackages
optionalPackages = with gnome3; [ baobab eog epiphany evince
  gucharmap nautilus totem vino yelp gnome-bluetooth
  gnome-calculator gnome-contacts gnome-font-viewer gnome-screenshot
  gnome-system-monitor simple-scan
  gnome-terminal gnome-user-docs evolution file-roller gedit
  gnome-clocks gnome-music gnome-tweaks gnome-photos
  nautilus-sendto dconf-editor vinagre gnome-weather gnome-logs
  gnome-maps gnome-characters gnome-calendar accerciser gnome-nettool
  gnome-getting-started-docs gnome-packagekit gnome-software
  gnome-power-manager gnome-todo pkgs.gnome-usage
];

I know that gnome-usage is still experimental, and probably shouldn't be installed by default.
Does GNOME3 document their distribution defaults anywhere?
I think we could clean this up slightly.
Note that if we remove anything from here it would be a good idea to conditionally add them based off the users stateVersion. That way current users won't see these packages magically disappear from their machine.
Or perhaps it's better document that in the release notes.

cc @jtojnar

If I recall correctly, we should be concerned about core and world:
https://gitlab.gnome.org/GNOME/gnome-build-meta/tree/master/elements

Ahh, looks like there's a bit to do here.
For example gnome-user-share should be :wave:

https://gitlab.gnome.org/GNOME/gnome-build-meta/blob/master/elements/core/meta-gnome-core-shell.bst#L23

I think it is just CI breakage after they removed gnome-common, see https://gitlab.gnome.org/GNOME/gnome-build-meta/merge_requests/280#note_487663

So after discussing briefly in irc, I guess we can implement profiles for

gnome-world-packages
gnome-games-packages

And the gnome3 module will continue to bring in core-utilities, core-shell, and core-os-services. In the future we can split that up so we can use flashback without gnome3.
Then we can eliminate the lists in gnome-3/default.nix since that should be in the profiles where it's useful.
One thing I'm unclear on is how to organize the profiles, and do they have options to enable?

Thinking about it more, the main benefit of profiles is that they would not need enable options. But if we want parts of the profiles to be disableable, we would need to have options for them anyway. Also with options, we get generated documentation for free. I am not sure that is a way to go an more.
As for the subdivision, maybe it would make more sense to look on it from users’ perspective:

Hard-core hacker wants a bare-bones GNOME Shell with minimum necessary services, not even file manager or terminal emulator – they already have favourite ones.
Casual user might have some favourite apps but they are generally happy to use whatever comes with the desktop environment. Here we would ship the core apps.
An organization such as a library might want a full desktop environment for their shared workstations, with programs for all possible purposes. But they probably have a sysadmin who wants to have a fine control over what gets installed on the workstations. For that reason, creating a profile that bundles all the world apps probably does not make sense.
Non-GNOME users who want to use GNOME apps probably do not want to use all GNOME apps either, so a core collection might not make sense for them.
A parent wants to install various games on the children’s computer. This is kind of similar to the organization but here the collection is more useful.

…

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/why-i-switched-to-manjaro-linux/5903/8

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/why-i-switched-to-manjaro-linux/5903/24


Delete translations, replace tags when pushing content

Update the "push" command with more management options.
More specifically:
manage.py transifex push --do-not-keep-translations will delete translations when source content on existing keys changes.
manage.py transifex push --override-tags will replace all tags on pushed strings with tags uploaded through the command.
Also CDSHandler is updated to reflect the above when used programmatically.

Codecov Report

Merging #103 (9afdb0d) into devel (056df76) will decrease coverage by 0.22%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##            devel     #103      +/-   ##
==========================================
- Coverage   78.10%   77.89%   -0.22%
==========================================
  Files          47       47
  Lines        3864     3868       +4
==========================================
- Hits         3018     3013       -5
- Misses        846      855       +9

Impacted Files
Coverage Δ

transifex/native/cds.py
89.92% <100.00%> (ø)

transifex/native/core.py
91.04% <100.00%> (ø)

transifex/native/django/management/utils/push.py
86.79% <100.00%> (+0.34%)
:arrow_up:

... and 1 file with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


consider changing validate(IonValue, Violations) to validate(IonValue): Violations

Applicable to both Constraint and Type interfaces.

The Type interface already follows functional style (fun validate(value: IonValue): Violations), so I stand corrected:  this issue applies only to the internal Constraint interface.
Additionally, the Constraint interface (fun validate(value: IonValue, issues: Violations)) uses issues to accumulate Violations, so it must be passed as a parameter.  The remaining question, then, is whether there's value in having this signature return the Violations object as well.

No issue here, and no obvious value in having Constraint.validate() return the Violations object;  closing