text:
[WFCORE-3818] Improved console color capability detection

https://issues.redhat.com/browse/WFCORE-3818

Core - Full Integration Build 9798 outcome was UNKNOWN using a merge of f25859a70bf2f6a67f95f41a9e9774d4c5c0bb6e
Summary: Canceled (Error while applying patch; cannot find commit 11bb340a812b8e1f22c3bfdc29294990c7a42b64 in the https://github.com/wildfly/wildfly-core.git repository, possible reason: refs/pull/4283/merge branch was updated and the commit selected for the ... Build time: 00:00:12

Core - Full Integration Build 9839 outcome was UNKNOWN using a merge of f25859a70bf2f6a67f95f41a9e9774d4c5c0bb6e
Summary: Canceled (Error while applying patch; cannot find commit 11bb340a812b8e1f22c3bfdc29294990c7a42b64 in the https://github.com/wildfly/wildfly-core.git repository, possible reason: refs/pull/4283/merge branch was updated and the commit selected for the ... Build time: 00:00:14

Core - Full Integration Build 9843 outcome was FAILURE using a merge of 940e5818b19d529b70529c565a3712e531c66c1a
Summary: Tests failed: 1 (1 new), passed: 6719, ignored: 104 Build time: 04:09:51
Failed tests
org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.removeJMSQueueRemovesAllMessages: java.lang.AssertionError: expected:<1> but was:<2>
	at org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.removeJMSQueueRemovesAllMessages(JMSQueueManagementTestCase.java:518)

@jfdenise could you please review?

@lvydra, thank-you. I see this change as an optimization of an existing feature that could be at risk. We have the --no-colour-output that a user can explicitly set if what he observes is not correct. We have so much OS on which this CLI script is running, that I would be concerned that this change breaks an exotic execution context.

Hi @jfdenise , thank you for your comment. OK, I understand, so I suppose I should close this PR and subsequently WFCORE-3818 issue, with this justification?

@lvydra , the issue you are mentioning is more general than CLI, not sure you should close it.

authors: jfdenise jmesnil lvydra wildfly-ci


text:
[WFCORE-5805] HostControllerBootOperationsTestCase fails intermittent…

…ly when Security Manager is enabled
Jira issue: https://issues.redhat.com/browse/WFCORE-5805
This PR follow-ups on https://github.com/wildfly/wildfly-core/pull/4961.
It adds 40 seconds more to the overall test to ensure we are not hitting failures when CI is pretty busy :(. Ideally, we should be able to unlock the Byte man rule by issuing signalWake when the test condition is satisfied, but it is really difficult to find a condition that can be used to trigger the awake by using the same identifier ($this). So I'm trying this with the hope that this additional time is acceptable. It is a workaround though, it won't ensure we will never going to pass the limit that ensures the test can be run, but for the last failures, it looks enough.

Thanks, @yersan

source: gharchive/pull-request

authors: bstansberry yersan

repo: wildfly/wildfly-core

license_type: permissive

license_source: github-api


text:
[JDK9] Fix code/build to work on JDK9

as requirement to move to JDK9 as requested by @n1hility
to properly run you need JDK 9 build b60(planned for release in 2 months)

Linux Build 1456 is now running using a merge of 90cff4eb95e697268b92c367fe8d7f6028157d14

Windows Build 1115 is now running using a merge of 90cff4eb95e697268b92c367fe8d7f6028157d14

Core - Full Integration Build 718 is now running using a merge of 90cff4eb95e697268b92c367fe8d7f6028157d14

Core - Full Integration Build 718 outcome was FAILURE using a merge of 90cff4eb95e697268b92c367fe8d7f6028157d14
Summary: Exit code 1 (new) Build time: 0:01:13
Build problems:
Process exited with code 1

Windows Build 1115 outcome was FAILURE using a merge of 90cff4eb95e697268b92c367fe8d7f6028157d14
Summary: Tests passed: 1563, ignored: 45; exit code 1 (new) Build time: 0:03:20
Build problems:
Process exited with code 1

Linux Build 1456 outcome was FAILURE using a merge of 90cff4eb95e697268b92c367fe8d7f6028157d14
Summary: Tests passed: 1563, ignored: 45; exit code 1 (new) Build time: 0:04:20
Build problems:
Process exited with code 1

needs some rework...

authors: ctomc wildfly-ci


text:
WFLY-18225 Upgrade smallrye-open-api to 3.4.0

https://issues.redhat.com/browse/WFLY-18225
Also fixes WFLY-18224 Fix ClassNotFoundException when scanning annotations on enums
https://issues.redhat.com/browse/WFLY-18224

Thanks @pferraro

authors: bstansberry pferraro

repo: wildfly/wildfly


text:
WFLY-4708 Upgrade to Narayana 5.0.6.Final

The narayana fix for the IIOP shutdown issue (see WFLY-4548) that is holding up the release of WF9 CR2.

Windows Build 79 is now running using a merge of a22a6d52711a1b3c2f6626d5f0f1e01897ceecbe

Linux Build 76 is now running using a merge of a22a6d52711a1b3c2f6626d5f0f1e01897ceecbe

Linux with security manager Build 72 is now running using a merge of a22a6d52711a1b3c2f6626d5f0f1e01897ceecbe

Linux with security manager Build 72 outcome was SUCCESS using a merge of a22a6d52711a1b3c2f6626d5f0f1e01897ceecbe
Summary: Tests passed: 827, ignored: 317 Build time: 0:05:58

Windows Build 79 outcome was SUCCESS using a merge of a22a6d52711a1b3c2f6626d5f0f1e01897ceecbe
Summary: Tests passed: 2869, ignored: 372 Build time: 0:48:17

Linux Build 76 outcome was FAILURE using a merge of a22a6d52711a1b3c2f6626d5f0f1e01897ceecbe
Summary: Tests failed: 8 (8 new), passed: 2861, ignored: 372 Build time: 0:49:16
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.jca.moduledeployment.TwoModulesJarTestCase.testConnection2: <no details avaliable>

org.jboss.as.test.integration.jca.moduledeployment.TwoModulesJarTestCase.testAdminObject: <no details avaliable>

org.jboss.as.test.integration.jca.moduledeployment.TwoModulesJarTestCase.testAdminObject1: <no details avaliable>

org.jboss.as.test.integration.jca.moduledeployment.TwoModulesJarTestCase.testConnectionFactory1: <no details avaliable>

org.jboss.as.test.integration.jca.moduledeployment.TwoModulesJarTestCase.testConnectionFactory: <no details avaliable>

org.jboss.as.test.integration.jca.moduledeployment.TwoModulesJarTestCase.testConnectionFactoryProperties: <no details avaliable>

org.jboss.as.test.integration.jca.moduledeployment.TwoModulesJarTestCase.testConnection1: <no details avaliable>

org.jboss.as.test.integration.jca.moduledeployment.TwoModulesJarTestCase.testConnectionFactoryProperties1: <no details avaliable>

retest this please
I am asking for a retest since the tests:

run fine on my linux laptop;
are unrelated to narayana
the failures may be spurious

Linux with security manager Build 73 is now running using a merge of a22a6d52711a1b3c2f6626d5f0f1e01897ceecbe

Linux Build 77 is now running using a merge of a22a6d52711a1b3c2f6626d5f0f1e01897ceecbe

Windows Build 80 is now running using a merge of a22a6d52711a1b3c2f6626d5f0f1e01897ceecbe

Linux with security manager Build 73 outcome was SUCCESS using a merge of a22a6d52711a1b3c2f6626d5f0f1e01897ceecbe
Summary: Tests passed: 827, ignored: 317 Build time: 0:05:42

Windows Build 80 outcome was SUCCESS using a merge of a22a6d52711a1b3c2f6626d5f0f1e01897ceecbe
Summary: Tests passed: 2865, ignored: 372, muted: 4 Build time: 0:46:54

Linux Build 77 outcome was FAILURE using a merge of a22a6d52711a1b3c2f6626d5f0f1e01897ceecbe
Summary: Tests failed: 1 (1 new), passed: 2868, ignored: 372 Build time: 0:47:40
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.clustering.cluster.ejb.remote.RemoteFailoverTestCase(SYNC-tcp).testStatefulFailover: <no details avaliable>

The first linux build had 8 errors in the jca tests (jndi lookup failures) which I think were all caused:
"WFLYCTL0379: System boot is in process; execution of remote management operations is not currently available"

which looks like a race condition in the test framework.
On the retest, the second linux build ony had a single error. It was in the clustering tests (testStatefulFailover) which is testing:
"Bean should retain weak affinity for this node"

These look like intermittent failures caused by the test framework and are unrelated to the narayana upgrade. Would it be possible to get this PR merged regardless of these intermittent failures.

Windows Build 82 is now running using a merge of a22a6d52711a1b3c2f6626d5f0f1e01897ceecbe

Linux with security manager Build 75 is now running using a merge of a22a6d52711a1b3c2f6626d5f0f1e01897ceecbe

Linux Build 79 is now running using a merge of a22a6d52711a1b3c2f6626d5f0f1e01897ceecbe

Linux with security manager Build 75 outcome was SUCCESS using a merge of a22a6d52711a1b3c2f6626d5f0f1e01897ceecbe
Summary: Tests passed: 827, ignored: 317 Build time: 0:06:34

Linux Build 79 outcome was SUCCESS using a merge of a22a6d52711a1b3c2f6626d5f0f1e01897ceecbe
Summary: Tests passed: 2865, ignored: 372, muted: 4 Build time: 0:48:45

Windows Build 82 outcome was SUCCESS using a merge of a22a6d52711a1b3c2f6626d5f0f1e01897ceecbe
Summary: Tests passed: 2869, ignored: 372 Build time: 0:55:01

authors: mmusgrov wildfly-ci


text:
WFLY-8631 Integration test for WFCORE-2647 Add an option to always

send the client SSL certificate to LDAP server
https://issues.jboss.org/browse/WFLY-8631
This PR depends on https://github.com/wildfly/wildfly-core/pull/2331

@kwart could you please review?

Linux Build 9835 outcome was FAILURE using a merge of 7c4bcffeafc08089900e206b8001c89b8c6687b0
Summary: Tests passed: 3729, ignored: 154; compilation error: Compiler (new) Build time: 00:55:45

Windows Build 4858 outcome was FAILURE using a merge of 7c4bcffeafc08089900e206b8001c89b8c6687b0
Summary: Tests failed: 12 (12 new), passed: 3715, ignored: 155; compilation error: Compiler (new) Build time: 01:06:36
Failed tests
org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testJsfWorks: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
    "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
    "Services that may be the cause:" => [
        "jboss.http-upgrade-registry.default",
        "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
    ]
}}}}}}}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:229)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:221)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.executeOnMaster(MixedDomainDeploymentTest.java:400)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testJsfWorks(MixedDomainDeploymentTest.java:348)
------- Stdout: -------
13:00:48,530 INFO  [org.jboss.modules] (main) JBoss Modules version 1.6.0.Beta6
13:00:48,826 INFO  [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
[Host Controller] 13:00:49,307 INFO  [org.jboss.modules] (main) JBoss Modules version 1.6.0.Beta6
[Host Controller] 13:00:49,582 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1
[Host Controller] 13:00:49,631 INFO  [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 11.0.0.Beta1-SNAPSHOT (WildFly Core 3.0.0.Beta16) starting
[Host Controller] 13:00:50,146 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=native-interface' 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] 13:00:50,148 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=http-interface' 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] 13:00:50,214 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] 13:00:50,214 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] 13:00:50,247 INFO  [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1)
[Host Controller] 13:00:50,250 INFO  [org.xnio] (MSC service thread 1-8) XNIO version 3.5.0.Beta5
[Host Controller] 13:00:50,259 INFO  [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.5.0.Beta5
[Host Controller] 13:00:50,294 INFO  [org.jboss.as.patching] (MSC service thread 1-7) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
[Host Controller] 13:00:50,310 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-2) WFLYDM0111: Keystore C:\BuildAgent\work\a31d203e70e89f90\testsuite\mixed-domain\target\domains\MixedDomain700TestSuite\master\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
[Host Controller] 13:00:50,466 INFO  [org.jboss.remoting] (MSC service thread 1-8) JBoss Remoting version 5.0.0.Beta20
[Host Controller] 13:00:50,532 INFO  [org.jboss.as.remoting] (MSC service thread 1-7) WFLYRMT0001: Listening on [::1]:9999
[Host Controller] 13:00:51,706 INFO  [org.wildfly.security] (Controller Boot Thread) ELY00001: WildFly Elytron version 1.1.0.Beta38
[Host Controller] 13:00:51,719 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=default/subsystem=undertow/server=default-server/https-listener=https' 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] 13:00:51,767 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=ha/subsystem=undertow/server=default-server/https-listener=https' 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] 13:00:51,802 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full/subsystem=undertow/server=default-server/https-listener=https' 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] 13:00:51,841 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full-ha/subsystem=undertow/server=default-server/https-listener=https' 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] 13:00:52,279 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://[::1]:9990/management
[Host Controller] 13:00:52,279 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled
[Host Controller] 13:00:52,279 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 11.0.0.Beta1-SNAPSHOT (WildFly Core 3.0.0.Beta16) (Host Controller) started in 3360ms - Started 49 of 53 services (18 services are lazy, passive or on-demand)
INFO  [org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil] HostController started in 4257 ms
[Host Controller] 13:00:53,625 INFO  [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: WildFly Full 11.0.0.Beta1-SNAPSHOT (WildFly Core 3.0.0.Beta16) stopped in 49ms
[Host Controller] 13:00:53,626 INFO  [org.jboss.as] (MSC service thread 1-8) WFLYSRV0049: WildFly Full 11.0.0.Beta1-SNAPSHOT (WildFly Core 3.0.0.Beta16) starting
[Host Controller] 13:00:53,645 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=native-interface' 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] 13:00:53,646 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=http-interface' 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] 13:00:53,651 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] 13:00:53,653 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] 13:00:53,659 INFO  [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1)
[Host Controller] 13:00:53,673 INFO  [org.jboss.as.patching] (MSC service thread 1-4) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
[Host Controller] 13:00:53,682 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-8) WFLYDM0111: Keystore C:\BuildAgent\work\a31d203e70e89f90\testsuite\mixed-domain\target\domains\MixedDomain700TestSuite\master\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
[Host Controller] 13:00:53,717 INFO  [org.jboss.as.remoting] (MSC service thread 1-5) WFLYRMT0001: Listening on [::1]:9999
[Host Controller] 13:00:53,925 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://[::1]:9990/management
[Host Controller] 13:00:53,925 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://[::1]:9990
[Host Controller] 13:00:53,925 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 11.0.0.Beta1-SNAPSHOT (WildFly Core 3.0.0.Beta16) (Host Controller) started in 299ms - Started 49 of 53 services (18 services are lazy, passive or on-demand)
13:00:54,764 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testUnmanagedArchiveDeployment: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
    "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
    "Services that may be the cause:" => [
        "jboss.http-upgrade-registry.default",
        "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
    ]
}}}}}}}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:229)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:221)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.executeOnMaster(MixedDomainDeploymentTest.java:396)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testUnmanagedArchiveDeployment(MixedDomainDeploymentTest.java:201)
------- Stdout: -------
[Server:server-one] 13:01:10,011 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war")
[Server:server-one] 13:01:10,019 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 29) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "test.war")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
[Server:server-one]     "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
[Server:server-one]     "Services that may be the cause:" => [
[Server:server-one]         "jboss.http-upgrade-registry.default",
[Server:server-one]         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
[Server:server-one]     ]
[Server:server-one] }}
[Server:server-one] 13:01:10,020 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 29) WFLYSRV0021: Deploy of deployment "test.war" was rolled back with the following failure message:
[Server:server-one] {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
[Server:server-one]     "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
[Server:server-one]     "Services that may be the cause:" => [
[Server:server-one]         "jboss.http-upgrade-registry.default",
[Server:server-one]         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
[Server:server-one]     ]
[Server:server-one] }}
[Server:server-one] 13:01:10,029 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 2ms
[Server:server-one] 13:01:10,031 INFO  [org.jboss.as.controller] (ServerService Thread Pool -- 29) WFLYCTL0183: Service status report
[Server:server-one] WFLYCTL0186:   Services which failed to start:      service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener
[Server:server-one]
Failed response:
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-2" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-3" => {
            "outcome" => "failed",
            "rolled-back" => true
        }
    },
    "failure-description" => {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testDeploymentViaStream: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
    "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
    "Services that may be the cause:" => [
        "jboss.http-upgrade-registry.default",
        "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
    ]
}}}}}}}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:229)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:221)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.executeOnMaster(MixedDomainDeploymentTest.java:400)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testDeploymentViaStream(MixedDomainDeploymentTest.java:189)
------- Stdout: -------
[Host Controller] 13:01:14,129 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\mixed-domain\target\domains\MixedDomain700TestSuite\master\data\content\2d\cd1ca375a5c8a9281be529ce07aa35c310d580\content
[Server:server-one] 13:01:14,174 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war")
[Server:server-one] 13:01:14,181 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 29) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "test.war")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
[Server:server-one]     "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
[Server:server-one]     "Services that may be the cause:" => [
[Server:server-one]         "jboss.http-upgrade-registry.default",
[Server:server-one]         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
[Server:server-one]     ]
[Server:server-one] }}
[Server:server-one] 13:01:14,182 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 29) WFLYSRV0021: Deploy of deployment "test.war" was rolled back with the following failure message:
[Server:server-one] {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
[Server:server-one]     "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
[Server:server-one]     "Services that may be the cause:" => [
[Server:server-one]         "jboss.http-upgrade-registry.default",
[Server:server-one]         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
[Server:server-one]     ]
[Server:server-one] }}
[Server:server-one] 13:01:14,184 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 1ms
[Server:server-one] 13:01:14,184 INFO  [org.jboss.as.controller] (ServerService Thread Pool -- 29) WFLYCTL0183: Service status report
[Server:server-one] WFLYCTL0186:   Services which failed to start:      service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener
[Server:server-one]
Failed response:
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-2" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-3" => {
            "outcome" => "failed",
            "rolled-back" => true
        }
    },
    "failure-description" => {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testRedeploy: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
    "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
    "Services that may be the cause:" => [
        "jboss.http-upgrade-registry.default",
        "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
    ]
}}}}}}}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:229)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:221)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.executeOnMaster(MixedDomainDeploymentTest.java:400)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testDeploymentViaStream(MixedDomainDeploymentTest.java:189)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testRedeploy(MixedDomainDeploymentTest.java:302)
------- Stdout: -------
[Host Controller] 13:01:18,255 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\mixed-domain\target\domains\MixedDomain700TestSuite\master\data\content\d1\24886c3d6c549a0c9a944057bc4f9b8bbfdc0d\content
[Server:server-one] 13:01:18,293 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war")
[Server:server-one] 13:01:18,300 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 29) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "test.war")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
[Server:server-one]     "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
[Server:server-one]     "Services that may be the cause:" => [
[Server:server-one]         "jboss.http-upgrade-registry.default",
[Server:server-one]         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
[Server:server-one]     ]
[Server:server-one] }}
[Server:server-one] 13:01:18,301 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 29) WFLYSRV0021: Deploy of deployment "test.war" was rolled back with the following failure message:
[Server:server-one] {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
[Server:server-one]     "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
[Server:server-one]     "Services that may be the cause:" => [
[Server:server-one]         "jboss.http-upgrade-registry.default",
[Server:server-one]         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
[Server:server-one]     ]
[Server:server-one] }}
[Server:server-one] 13:01:18,303 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 2ms
[Server:server-one] 13:01:18,304 INFO  [org.jboss.as.controller] (ServerService Thread Pool -- 29) WFLYCTL0183: Service status report
[Server:server-one] WFLYCTL0186:   Services which failed to start:      service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener
[Server:server-one]
Failed response:
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-2" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-3" => {
            "outcome" => "failed",
            "rolled-back" => true
        }
    },

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testUnmanagedExplodedRedeploy: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
    "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
    "Services that may be the cause:" => [
        "jboss.http-upgrade-registry.default",
        "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
    ]
}}}}}}}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:229)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:221)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.executeOnMaster(MixedDomainDeploymentTest.java:396)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testUnmanagedExplodedDeployment(MixedDomainDeploymentTest.java:213)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testUnmanagedExplodedRedeploy(MixedDomainDeploymentTest.java:318)
------- Stdout: -------
[Server:server-one] 13:01:20,365 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war")
[Server:server-one] 13:01:20,368 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 29) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "test.war")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
[Server:server-one]     "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
[Server:server-one]     "Services that may be the cause:" => [
[Server:server-one]         "jboss.http-upgrade-registry.default",
[Server:server-one]         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
[Server:server-one]     ]
[Server:server-one] }}
[Server:server-one] 13:01:20,369 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 29) WFLYSRV0021: Deploy of deployment "test.war" was rolled back with the following failure message:
[Server:server-one] {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
[Server:server-one]     "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
[Server:server-one]     "Services that may be the cause:" => [
[Server:server-one]         "jboss.http-upgrade-registry.default",
[Server:server-one]         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
[Server:server-one]     ]
[Server:server-one] }}
[Server:server-one] 13:01:20,370 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 1ms
[Server:server-one] 13:01:20,370 INFO  [org.jboss.as.controller] (ServerService Thread Pool -- 29) WFLYCTL0183: Service status report
[Server:server-one] WFLYCTL0186:   Services which failed to start:      service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener
[Server:server-one]
Failed response:
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-2" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-3" => {
            "outcome" => "failed",
            "rolled-back" => true
        }
    },
    "failure-description" => {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testUndeploy: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
    "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
    "Services that may be the cause:" => [
        "jboss.http-upgrade-registry.default",
        "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
    ]
}}}}}}}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:229)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:221)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.executeOnMaster(MixedDomainDeploymentTest.java:400)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testDeploymentViaStream(MixedDomainDeploymentTest.java:189)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testUndeploy(MixedDomainDeploymentTest.java:278)
------- Stdout: -------
[Host Controller] 13:01:22,379 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\mixed-domain\target\domains\MixedDomain700TestSuite\master\data\content\be\b8d189107056849a7fa5a2628345df7e3e23ef\content
[Server:server-one] 13:01:22,412 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war")
[Server:server-one] 13:01:22,416 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 29) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "test.war")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
[Server:server-one]     "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
[Server:server-one]     "Services that may be the cause:" => [
[Server:server-one]         "jboss.http-upgrade-registry.default",
[Server:server-one]         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
[Server:server-one]     ]
[Server:server-one] }}
[Server:server-one] 13:01:22,417 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 29) WFLYSRV0021: Deploy of deployment "test.war" was rolled back with the following failure message:
[Server:server-one] {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
[Server:server-one]     "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
[Server:server-one]     "Services that may be the cause:" => [
[Server:server-one]         "jboss.http-upgrade-registry.default",
[Server:server-one]         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
[Server:server-one]     ]
[Server:server-one] }}
[Server:server-one] 13:01:22,419 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 1ms
[Server:server-one] 13:01:22,419 INFO  [org.jboss.as.controller] (ServerService Thread Pool -- 29) WFLYCTL0183: Service status report
[Server:server-one] WFLYCTL0186:   Services which failed to start:      service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener
[Server:server-one]
Failed response:
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-2" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-3" => {
            "outcome" => "failed",
            "rolled-back" => true
        }
    },

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testUnmanagedExplodedUndeploy: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
    "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
    "Services that may be the cause:" => [
        "jboss.http-upgrade-registry.default",
        "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
    ]
}}}}}}}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:229)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:221)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.executeOnMaster(MixedDomainDeploymentTest.java:396)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testUnmanagedExplodedDeployment(MixedDomainDeploymentTest.java:213)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testUnmanagedExplodedUndeploy(MixedDomainDeploymentTest.java:294)
------- Stdout: -------
[Server:server-one] 13:01:24,495 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war")
[Server:server-one] 13:01:24,498 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 29) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "test.war")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
[Server:server-one]     "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
[Server:server-one]     "Services that may be the cause:" => [
[Server:server-one]         "jboss.http-upgrade-registry.default",
[Server:server-one]         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
[Server:server-one]     ]
[Server:server-one] }}
[Server:server-one] 13:01:24,498 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 29) WFLYSRV0021: Deploy of deployment "test.war" was rolled back with the following failure message:
[Server:server-one] {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
[Server:server-one]     "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
[Server:server-one]     "Services that may be the cause:" => [
[Server:server-one]         "jboss.http-upgrade-registry.default",
[Server:server-one]         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
[Server:server-one]     ]
[Server:server-one] }}
[Server:server-one] 13:01:24,500 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 0ms
[Server:server-one] 13:01:24,500 INFO  [org.jboss.as.controller] (ServerService Thread Pool -- 29) WFLYCTL0183: Service status report
[Server:server-one] WFLYCTL0186:   Services which failed to start:      service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener
[Server:server-one]
Failed response:
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-2" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-3" => {
            "outcome" => "failed",
            "rolled-back" => true
        }
    },
    "failure-description" => {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testReplace: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
    "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
    "Services that may be the cause:" => [
        "jboss.http-upgrade-registry.default",
        "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
    ]
}}}}}}}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:229)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:221)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.executeOnMaster(MixedDomainDeploymentTest.java:400)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testDeploymentViaStream(MixedDomainDeploymentTest.java:189)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testReplace(MixedDomainDeploymentTest.java:326)
------- Stdout: -------
[Server:server-one] 13:01:26,376 WARN  [org.jgroups.protocols.UDP] (multicast receiver,ee,slave:server-one) JGRP000010: packet from fe80:0:0:0:300d:c33c:9fbf:1ea5%12:45688 has different version (3.2.12) than ours (3.6.8); packet is discarded
[Host Controller] 13:01:26,523 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\mixed-domain\target\domains\MixedDomain700TestSuite\master\data\content\8e\80fb30f41b56ef9c120fb60f0a669a4fdff343\content
[Server:server-one] 13:01:26,554 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war")
[Server:server-one] 13:01:26,560 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 29) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "test.war")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
[Server:server-one]     "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
[Server:server-one]     "Services that may be the cause:" => [
[Server:server-one]         "jboss.http-upgrade-registry.default",
[Server:server-one]         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
[Server:server-one]     ]
[Server:server-one] }}
[Server:server-one] 13:01:26,561 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 29) WFLYSRV0021: Deploy of deployment "test.war" was rolled back with the following failure message:
[Server:server-one] {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
[Server:server-one]     "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
[Server:server-one]     "Services that may be the cause:" => [
[Server:server-one]         "jboss.http-upgrade-registry.default",
[Server:server-one]         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
[Server:server-one]     ]
[Server:server-one] }}
[Server:server-one] 13:01:26,562 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 1ms
[Server:server-one] 13:01:26,563 INFO  [org.jboss.as.controller] (ServerService Thread Pool -- 29) WFLYCTL0183: Service status report
[Server:server-one] WFLYCTL0186:   Services which failed to start:      service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener
[Server:server-one]
Failed response:
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-2" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-3" => {
            "outcome" => "failed",
            "rolled-back" => true
        }

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testDeploymentViaUrl: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
    "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
    "Services that may be the cause:" => [
        "jboss.http-upgrade-registry.default",
        "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
    ]
}}}}}}}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:229)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:221)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.executeOnMaster(MixedDomainDeploymentTest.java:396)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testDeploymentViaUrl(MixedDomainDeploymentTest.java:176)
------- Stdout: -------
[Server:server-one] 13:01:28,616 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war")
[Server:server-one] 13:01:28,621 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 29) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "test.war")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
[Server:server-one]     "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
[Server:server-one]     "Services that may be the cause:" => [
[Server:server-one]         "jboss.http-upgrade-registry.default",
[Server:server-one]         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
[Server:server-one]     ]
[Server:server-one] }}
[Server:server-one] 13:01:28,621 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 29) WFLYSRV0021: Deploy of deployment "test.war" was rolled back with the following failure message:
[Server:server-one] {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
[Server:server-one]     "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
[Server:server-one]     "Services that may be the cause:" => [
[Server:server-one]         "jboss.http-upgrade-registry.default",
[Server:server-one]         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
[Server:server-one]     ]
[Server:server-one] }}
[Server:server-one] 13:01:28,622 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 1ms
[Server:server-one] 13:01:28,623 INFO  [org.jboss.as.controller] (ServerService Thread Pool -- 29) WFLYCTL0183: Service status report
[Server:server-one] WFLYCTL0186:   Services which failed to start:      service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener
[Server:server-one]
Failed response:
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-2" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-3" => {
            "outcome" => "failed",
            "rolled-back" => true
        }
    },
    "failure-description" => {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testUnmanagedExplodedDeployment: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
    "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
    "Services that may be the cause:" => [
        "jboss.http-upgrade-registry.default",
        "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
    ]
}}}}}}}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:229)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:221)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.executeOnMaster(MixedDomainDeploymentTest.java:396)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testUnmanagedExplodedDeployment(MixedDomainDeploymentTest.java:213)
------- Stdout: -------
[Server:server-one] 13:01:30,685 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war")
[Server:server-one] 13:01:30,688 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 29) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "test.war")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
[Server:server-one]     "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
[Server:server-one]     "Services that may be the cause:" => [
[Server:server-one]         "jboss.http-upgrade-registry.default",
[Server:server-one]         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
[Server:server-one]     ]
[Server:server-one] }}
[Server:server-one] 13:01:30,689 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 29) WFLYSRV0021: Deploy of deployment "test.war" was rolled back with the following failure message:
[Server:server-one] {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
[Server:server-one]     "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
[Server:server-one]     "Services that may be the cause:" => [
[Server:server-one]         "jboss.http-upgrade-registry.default",
[Server:server-one]         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
[Server:server-one]     ]
[Server:server-one] }}
[Server:server-one] 13:01:30,690 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 1ms
[Server:server-one] 13:01:30,691 INFO  [org.jboss.as.controller] (ServerService Thread Pool -- 29) WFLYCTL0183: Service status report
[Server:server-one] WFLYCTL0186:   Services which failed to start:      service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener
[Server:server-one]
Failed response:
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-2" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-3" => {
            "outcome" => "failed",
            "rolled-back" => true
        }
    },
    "failure-description" => {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testUnmanagedArchiveRedeploy: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
    "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
    "Services that may be the cause:" => [
        "jboss.http-upgrade-registry.default",
        "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
    ]
}}}}}}}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:229)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:221)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.executeOnMaster(MixedDomainDeploymentTest.java:396)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testUnmanagedArchiveDeployment(MixedDomainDeploymentTest.java:201)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testUnmanagedArchiveRedeploy(MixedDomainDeploymentTest.java:310)
------- Stdout: -------
[Server:server-one] 13:01:32,745 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war")
[Server:server-one] 13:01:32,752 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 29) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "test.war")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
[Server:server-one]     "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
[Server:server-one]     "Services that may be the cause:" => [
[Server:server-one]         "jboss.http-upgrade-registry.default",
[Server:server-one]         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
[Server:server-one]     ]
[Server:server-one] }}
[Server:server-one] 13:01:32,752 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 29) WFLYSRV0021: Deploy of deployment "test.war" was rolled back with the following failure message:
[Server:server-one] {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
[Server:server-one]     "Services that were unable to start:" => ["jboss.deployment.unit.\"test.war\".PARSE"],
[Server:server-one]     "Services that may be the cause:" => [
[Server:server-one]         "jboss.http-upgrade-registry.default",
[Server:server-one]         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
[Server:server-one]     ]
[Server:server-one] }}
[Server:server-one] 13:01:32,755 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 1ms
[Server:server-one] 13:01:32,755 INFO  [org.jboss.as.controller] (ServerService Thread Pool -- 29) WFLYCTL0183: Service status report
[Server:server-one] WFLYCTL0186:   Services which failed to start:      service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener
[Server:server-one]
Failed response:
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-2" => {
            "outcome" => "failed",
            "rolled-back" => true
        },
        "step-3" => {
            "outcome" => "failed",
            "rolled-back" => true
        }
    },
    "failure-description" => {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {

##### there are 2 more failed tests, see build details

Retest this please

Retest this please

authors: kabir ppalaga wildfly-ci


text:
Does not install Bootstrap4 dependencies

Bug:: does not install bootstrap4 dependencies
...
New Issue Checklist

[x] Checked that the issue has not already been reported.
[x] Checked that the issue has not already been fixed in the latest code (a.k.a. master).
[x] Issue description of problem is clear, concise and precise.
[x] Issue has a a descriptive title and a summary in grammatically correct, complete sentences.
[ ] Includes the version of ember-bootstrap-controls that you are using.
[ ] Includes any relevant code to the issue summary.

Is this a bug or a feature request?
For bugs...
Can the problem be recreated? If so how?
For features...
Why is this feature important?

We have 2 choices:

ember-bootstrap
ember-cli-bootstrap-4
We should come up with the pros/cons of each one and decide as a team which one to use.

source: gharchive/issue

authors: flarinerin jweakley

repo: wildland/ember-bootstrap-controls

license: mit

license_source: bigquery


text:
Entities retrieved by the integration

Hello,
very pleased to find this integration as it is complementary to the one from LucaPatarca.  Especially that the string voltages and currents are exposed for our hybrid inverter.  However I don't see anything with regards to the battery status - eg the %ge charge of the battery.  Perhaps I should be computing that from some of the values we do get.  I do get this from the other integration however that integration seems to require me to re-enter the credentials often and reboot HA. It is scaled 0 - 100% though ATON's own app regards 20% charge as being the zero whereas we see the real percentage.

@malcolmhm There is a state_of_battery sensor that shows the current battery % charge.
Or at least there is showing on the integration with system, I have the RA-Store3, which do you have?

Hi, apologies only just spotted this. I've got the Gstore 4k - hybrid inverter, installed July this year. Thanks for your comment as it made me look further and found the relevant entity when looking at the integration from the settings/integrations etc- it just hadn't appeared automatically in the overview. So yes its there!

authors: malcolmhm nspickles

repo: wilds/hass-atonstorage

license: MIT


text:
minimum number of characters in entries

enter a minimum number of characters in the input for it to be validated

03 for the person's name
10 for the course name
30 for the course description

I thought about creating a new bool function in the 'ValidationHelper' class with input for the number of characters in the inserted string and the number you want to check, returning true if it is above the value or false if it is below.


text:
WKB dumper

Add dumper for WKB (well-known binary).

Thanks!

authors: jsor willdurand

repo: willdurand/Geocoder


text:
Add support for inlinee lines

This is a followup to #46 which adds support for iterating over inlinee lines. Right now this is pretty ugly and should not be used as I'm exporting some information straight from the c13 module.
Since this is me an @jan-auer hackering around on the same branch now and I am tired of force pushes, we are going to rewrite the history in the end before the merge to make it pretty and keep pushing WIPs in the meantime.

This is not yet complete, but will contain a full refactor of Symbols to fix https://github.com/willglynn/pdb/issues/14. Additionally, this helps to expose binary annotations more neatly.

Since I cannot edit the original PR description, I'll start to maintain a changelog in this comment. Given that all changes are quite connected and build on each other, it would have been too hard to maintain them in separate PRs (although probably possible):
Breaking Changes:

Symbol::name has been removed, since not all symbols have a name. Instead, every symbol with a name now exposes a name field. To provide uniform access to the name, SymbolData::name now exposes an Option<RawString> after parsing. (NB: This felt more robust than maintaining a manual list of offsets)
SymbolData::Public and SymbolData::Data have been stripped of their *Symbol prefix, as this is redundant and inconsistent.
Many symbol kinds, most notablySymbolData::CompileFlags, have been fixed with stronger typing.

Public Changes:

Symbol::starts_scope and Symbol::ends_scope now indicate which symbols can contain sub-symbols. This helps to deal with a hierarchy of symbols, such as building a tree.
Every Symbol now exposes an index. Also, some symbols may refer to others via that index (e.g. inline sites point to their parent and their end). SymbolTable, ModuleInfo and SymbolIter now allow jumping to symbols by their index.
Inline Sites are now supported via SymbolData::InlineSite(InlineSiteSymbol). It exposes an iterator over its binary annotations, which can be used to evaluate the line program of the inline site.
(pending): A higher-level abstraction for uniformly exposing inlinee lines.

Internal Changes:

Pread is now implemented for more types, including: Variant, CPUType, SourceLanguage.
ParseBuffer can now parse any type that implements TryFromCtx, not just the ones that use scroll::Endian as context. There's also a new method parse_with to pass a custom parse context.

@willglynn This is ready for review now. See https://github.com/willglynn/pdb/pull/47#issuecomment-517625235 for a summary of all changes.

When working on the next feature (Cross Module Imports/Exports), I realized that inlinees are probably better placed on the module info directly than the line program.

authors: jan-auer mitsuhiko

repo: willglynn/pdb


text:
Val_loss not available

Describe the bug
When I train my network, which has validation steps defined similar to the doc example
def validation_step(self, batch, batch_nb):
        x = torch.squeeze(batch['x'], dim=0).float()
        y = torch.squeeze(batch['y'], dim=0).long()

        output = self.forward(x)
        return {'batch_val_loss': self.loss(output, y),
                'batch_val_acc': accuracy(output, y)}

    def validation_end(self, outputs):
        avg_loss = torch.stack([x['batch_val_loss'] for x in outputs]).mean()
        avg_acc = torch.stack([x['batch_val_acc'] for x in outputs]).mean()

        return {'val_loss': avg_loss, 'val_acc': avg_acc}

with my cusotm EarlyStopCallback
early_stop_callback = EarlyStopping(monitor='val_loss', patience=5)

    tt_logger = TestTubeLogger(
        save_dir=log_dir,
        name="default",
        debug=False,
        create_git_tag=False
    )

    trainer = Trainer(logger=tt_logger,
                      row_log_interval=10,
                      checkpoint_callback=checkpoint_callback,
                      early_stop_callback=early_stop_callback,
                      gradient_clip_val=0.5,
                      gpus=gpus,
                      check_val_every_n_epoch=1,
                      max_nb_epochs=99999,
                      train_percent_check=train_frac,
                      log_save_interval=100,
                     )

the program cannot see my validation metrics:
Early stopping conditioned on metric `val_loss` which is not available. Available metrics are: loss,epoch,batch_nb,v_nb <class 'RuntimeWarning'>

In a previous release running on Windows (now I am on macOS), this behaviour was not happening. But in the previous version, TestTubeLogger was not present
Desktop (please complete the following information):

OS: macOS
Version: latest

the early stop metrics come from “progress_bar” entry:
So, add a key “progress_bar” and val_loss in there

Thank you this fixed my issue

def validation_end(self, outputs):
        avg_loss = torch.stack([x['batch_val_loss'] for x in outputs]).mean()
        avg_acc = torch.stack([x['batch_val_acc'] for x in outputs]).mean()

        return {
          'val_loss': avg_loss,
          'val_acc': avg_acc,
          'progress_bar':{'val_loss': avg_loss, 'val_acc': avg_acc }}

repo: williamFalcon/pytorch-lightning


text:
Provide go to definition

Pressing Ctrl + mouse click in a source file name in a template should redirect to the file.
Files extension could be .tpl, .js, .css or image extensions.

Supported browsers image extensions: .apng, .gif, .ico, .cur, .jpg, .jpeg, .jfif, .pjpeg, .pjp, .png, .svg
Font: https://www.w3schools.com/html/html_images.asp

repo: williamthome/zotonic-ls


text:
Observation about new Kernel Operator

I notice the new kernel operator makes use of nested for loops and update operations. For JAX that is a very bad idea. for loops should be avoided at all costs.

that's a good point, think we can replace these with a scan @AndPotap ?

Thanks for pointing this out. I'll think about how to do this for it to also be compatible with PyTorch.

I think we would just want to add a xnp.scan function to the backends and then use that. Also for cases where we are using a xnp.for_loop right now, we should probably replace with scan where possible

authors: AndPotap adam-hartshorne mfinzi

repo: wilson-labs/cola


text:
File Types Not Showing Up

https://github.com/win32ss/supermium/releases .
"supermium_122_32_setup.exe" "94.4 MB" .
My problem is that when I tr to open a saved page ( Control + O ), or save a page (Control + S ), in the "Files of type" and "Save as type" all it will show is asterisk.asterisk .
This makes it impossible to open, or save, files. Like .htm, .html, .pdf, .json, etc.. Can someone tell me what to do?
How do I get it to show all the files that are on the HD?

https://www.geocities.ws/arielschnee/gallery/FP-Ariel_Schnee/S_Problem01.png
https://www.geocities.ws/arielschnee/gallery/FP-Ariel_Schnee/S_Problem02.png
https://www.geocities.ws/arielschnee/gallery/FP-Ariel_Schnee/S_Problem03.png
https://www.geocities.ws/arielschnee/gallery/FP-Ariel_Schnee/S_Problem04.png
https://www.geocities.ws/arielschnee/gallery/FP-Ariel_Schnee/S_Problem05.png
https://www.geocities.ws/arielschnee/gallery/FP-Ariel_Schnee/S_Problem06.png
https://www.geocities.ws/arielschnee/gallery/FP-Ariel_Schnee/S_Problem07.png
https://www.geocities.ws/arielschnee/gallery/FP-Ariel_Schnee/S_Problem08.png
https://www.geocities.ws/arielschnee/gallery/FP-Ariel_Schnee/S_Problem09.png
https://www.geocities.ws/arielschnee/gallery/FP-Ariel_Schnee/S_Problem10.png
https://www.geocities.ws/arielschnee/gallery/FP-Ariel_Schnee/S_Problem11.png
https://www.geocities.ws/arielschnee/gallery/FP-Ariel_Schnee/S_Problem12.png

Looks as known problem: #438
https://github.com/win32ss/supermium/issues/438#issuecomment-2025740977

The issue is fixed for me in "Supermium 122.0.6261.152 (R4)". Can you confirm @Ariel-Schnee  ? If yes, then please close this ticket.

authors: Ariel-Schnee IDA-RE-things JoachimHenze


text:
git: add goalnd tempfiles to gitignore so maia and matt can develop in peace

we should fix this bug for real but in the meantime this was throwing
too many errors for me to actually write other code -_-

What is the bug in this case, that Tilt doesn't respect the global gitignore?

I think the lack of support for global gitignore is more just preventing us from working around the problem.
These masks aren't things that goland users will typically put in their gitignores, because they don't generally exist on disk for more than milliseconds.
A tilt user could prevent these from showing up in tilt by adding them to their gitignore (global or otherwise).
I think the proper fix we'll want at some point is to change tilt so that if a file returns to its original state before the build starts, we drop it from the changed files list (this would also fix some issues with temp files made by other editors on save).
I'm leaning strongly towards just hardcoding an ignore of the jb temp files in tilt itself, for now.

authors: jazzdan landism maiamcc

repo: windmilleng/servantes


text:
Nvim Treesitter Setup is deprecated

The error is returned despite using the recommended setup method.
Using latest versions of the plugin, treesitter and nVim (v0.10.0).
Configuration
{
    url = 'https://github.com/windwp/nvim-ts-autotag',
    config = function()
        require('nvim-ts-autotag').setup({
            opts = {
                enable_close = true,
                enable_rename = true,
                enable_close_on_slash = true
            }
        })
    end
}

Error
Nvim Treesitter Setup is deprecated, use `require('nvim-ts-autotag').setup()` instead.
Feature will be removed in nvim-ts-autotag 1.0.0
stack traceback:
        .../share/nvim/lazy/nvim-ts-autotag/lua/nvim-ts-autotag.lua:15: in function 'attach'
        ...vim/lazy/nvim-treesitter/lua/nvim-treesitter/configs.lua:509: in function 'attach_module'
        ...vim/lazy/nvim-treesitter/lua/nvim-treesitter/configs.lua:532: in function 'reattach_module'
        ...vim/lazy/nvim-treesitter/lua/nvim-treesitter/configs.lua:133: in function <...vim/lazy/nvim-treesitter/lua/nvim-treesitter/configs.lua:132>
        [C]: in function 'nvim_cmd'
        /usr/share/nvim/runtime/filetype.lua:36: in function </usr/share/nvim/runtime/filetype.lua:35>
        [C]: in function 'nvim_buf_call'
        /usr/share/nvim/runtime/filetype.lua:35: in function </usr/share/nvim/runtime/filetype.lua:10>

That means you still have a treesitter module setup method somewhere in your config.
Look for something like require("nvim-treesitter.configs").setup and remove the related autotag section from it.
Feel free to reopen this if you can confirm you're not setting up via nvim-treesitter at all and still facing this.
Thanks 🙂

@cool-pants Hi. I was facing the same probem and to fix this problem I just set autotag to false on treesitter config:
autotag = {
    enable = false,
},

This is my treesitter file:
return {
    "nvim-treesitter/nvim-treesitter",
    build = ":TSUpdate",
    config = function()
        require("nvim-treesitter.configs").setup {
            ensure_installed = {
                "lua",
                "luadoc",
                "bash",
                "c",
                "cmake",
                "make",
                "html",
                "css",
                "scss",
                "markdown",
                "markdown_inline",
                "vim",
                "vimdoc",
                "query",
                "dockerfile",
                "gitignore",
                "javascript",
                "jsdoc",
                "typescript",
                "tsx",
                "python",
                "diff",
            },
            -- Autoinstall parsers that are not installed
            auto_install = true,
            autopairs = {
                enable = true,
            },
            autotag = {
                enable = false,
            },
            endwise = {
                enable = true,
            },
            highlight = {
                enable = true,
            },
            indent = {
                enable = true,
            },
            incremental_selection = {
                enable = true,
                keymaps = {
                    init_selection = "gnn",
                    node_incremental = "grn",
                    scope_incremental = "grc",
                    node_decremental = "grm",
                },
            },
        }
    end
}

@cool-pants Hi. I was facing the same probem and to fix this problem I just set autotag to false on treesitter config:
autotag = {
    enable = false,
},

This is my treesitter file:
return {
    "nvim-treesitter/nvim-treesitter",
    build = ":TSUpdate",
    config = function()
        require("nvim-treesitter.configs").setup {
            ensure_installed = {
                "lua",
                "luadoc",
                "bash",
                "c",
                "cmake",
                "make",
                "html",
                "css",
                "scss",
                "markdown",
                "markdown_inline",
                "vim",
                "vimdoc",
                "query",
                "dockerfile",
                "gitignore",
                "javascript",
                "jsdoc",
                "typescript",
                "tsx",
                "python",
                "diff",
            },
            -- Autoinstall parsers that are not installed
            auto_install = true,
            autopairs = {
                enable = true,
            },
            autotag = {
                enable = false,
            },
            endwise = {
                enable = true,
            },
            highlight = {
                enable = true,
            },
            indent = {
                enable = true,
            },
            incremental_selection = {
                enable = true,
                keymaps = {
                    init_selection = "gnn",
                    node_incremental = "grn",
                    scope_incremental = "grc",
                    node_decremental = "grm",
                },
            },
        }
    end
}

This seems to solve my issue as well. Thanks 🫡

authors: PriceHiller mainak-affinsys marcusluis-s savchenko

repo: windwp/nvim-ts-autotag


text:
Country codes

Hi there,
How can I change this to display a dropdown with the Country names and on save, saves the country codes (iso)?
Thank you

@FilipeOS By default, country names with dial code will be shown in the dropdown list. There is no country code returned in onChange function at this moment.

authors: FilipeOS wingkwong


text:
请问直播延迟超过10秒以上是正常现象吗？

我使用的WSL，OS的版本是Ubuntu18.04。我的一台PC在局域网内进行推流，局域网内的另一台设备进行拉流，局域网使用的是千兆的无线路由器，但推流端使用的是网线连接方式，推流的视频质量比特率是10000，分辨率是1080P，60FPS。我使用任何工具拉流都会出现延迟，延迟多少不稳定，但至少会有10秒以上的延迟。我使用的是示例中的nginx配置，请问这是否与配置有关？应该怎么配置能减少延迟？另外是不是有可能和我使用的是WSL有关？另外关于视频质量我试过使用更低质量的视频，但是延迟并没有任何减少。

不太好确定。你先看看你发布的流的GOP是多少，如果GOP（我见过8秒的GOP）比较大，并且开启了gop_cache选项，那么延迟就会比较大，另外，有些播放器会缓存一些数据后再播放，而不是拿到I帧后就播放，我测试过从阿里云的服务器上拉香港卫视的流，然后用nginx-http-flv-module自带的JW Player播放，对比用VLC直接播香港卫视的流，前者居然比后者还快一小点！

非常感谢，刚才去看了一下OBS的推流，关键帧间隔居然设置成了5秒…
我的播放器是ijkplayer，播放速度和VLC基本相同，只是播放一段时间(3分钟左右)后会增加一些延迟，与VLC比较大概是增加了3秒以上。

authors: AngryTurf winshining

repo: winshining/nginx-http-flv-module


text:
Click on Twig paths to open editor

Closes #15
Please, Test it

@erikn69 why close it? I tried testing it locally but it didn't seem to work

I noticed from a comment that twig.environment.cms is not a singleton

repo: wintercms/wn-debugbar-plugin


text:
Add max-height and scroll bar to TeamComposeModal

closes #882

Thank you :)

authors: HuskYzPinto psikoi

repo: wise-old-man/wise-old-man


text:
Docs suggestions and typo fixes

Will continue to re-read the docs during the week and maybe add more commits. Thank you all!

Great stuff, thank you!

authors: icidasset toraritte

repo: witchcrafters/witchcraft


text:
Remove unneeded labelling rule

Since this repo is all about the documentation, every PR is about the docs so this rule isn't needed anymore

True, @Princesseuh. True.

authors: Princesseuh jonathantneal

repo: withastro/docs


text:
i18n(ko-KR): update project-structure.mdx

Description (required)

update project-structure.mdx
#8953

Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

ko
basics/project-structure.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

authors: astrobot-houston jsparkdev


text:
i18n(fr): update server-side-rendering.mdx

Description (required)
Update a code snippet in the French translation of server-side-rendering.mdx (see #9527 and #9533)

Related issues & labels (optional)

Suggested label: i18n

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

fr
guides/server-side-rendering.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

authors: ArmandPhilippot astrobot-houston


text:
💡 RFC: Add support for renaming symbols

I believe renaming has worked at some point, or at least in certain contexts at some point. Nowadays it just seems like it doesn't work at all, it'd be great to bring it back, both inside the HTML template and the JavaScript parts

This can be tackled right now, however the new TSX output will make it so this feature will need fairly consequential changes. As such, I suggest we wait for that to happen first before taking a serious look at renaming

repo: withastro/language-tools


text:
default 14px is too small for landing page text

What version of starlight are you using?
0.9.1
What is your idea?
First of all, thank you for the library. I saw it yesterday and used it today with pure joy!
One of my documentation readers commented that now the text on the landing page is hard to read on mobile.
I think it is customizable, but with great defaults and taste in other aspects, I think it would make starlight even more awesome to set default body text 16px.
Related line:
font-size: clamp(var(--sl-text-sm),calc(.5rem + 1vw),var(--sl-text-body));

Custom fix: add below variable to custom.css explained in the documentation
:root {
	--sl-text-sm: 1rem;
}

Why is this feature necessary?
A reader of my documentation website cared enough to tell me the text is less visible than before.
Do you have examples of this feature in other projects?
No response
Participation

[X] I am willing to submit a pull request for this issue.

Thanks for sharing the feedback @fatihpense — really helpful to hear! In general our default body text is 16px, it’s only the card designs that scale slightly differently on small screens given the way they’re designed to highlight the headlines.
I think this is a case where I’ll defer to our designer who set the original defaults and leave this as something for people to override to their personal taste. But still appreciate you raising it!

Thank you for considering. I respect your decision.
By the way, I'm still enjoying the clutter free, professional, minimalist documentation website. I sometimes visit my page just to look at it!
Thank you for your efforts. Looking forward to see new updates.
Best,
Fatih

authors: delucis fatihpense

repo: withastro/starlight


text:
mocha: Detox interfers with .mocharc's "spec" property when Detox "specs" is not defined

Is your feature request related to a problem? Please describe.
It's a bug(gy feature) of Detox.
If I specify the spec or files option in .mocharc.json
{
  "spec": "e2e/2_commandList.js",
  "timeout": 25000
}

and I don't configure specs in the Detox config, relying on defaults:
Actual result:
The spec option clearly doesn't work, because Detox overrides it with the default e2e value.
Describe the solution you'd like
Detox should not override ...specs with the default e2e value.
Describe alternatives you've considered
If I use the detox specs option in .detoxrc.json like this it works
But suppose if you have 10-20 test files, this wont be ideal to specify it in a string
  "specs": "e2e/init.js e2e/2_commandList.js",

File tree:
e2e
├── 1_runCommand.js
├── 2_commandList.js
├── init.js
└── utils.js

@ShivamJoker hello bro, i watched your youtube video and setup detox in react-native android in windows 10, only difference is i used jest instead of mocha, but getting following errors and i found you on here LOL, now you have to help me....
https://stackoverflow.com/questions/69988326/detoxruntimeerror-no-instrumentation-runner-found-on-device-emulator-5554-for-p   here is the issue.

@rutvikER1999 you need to generate a test build for android with all the dependencies and detox is not supported on Windows officially
Also please don't comment randomly on issues.

The integration with Mocha is not actively developed, but you're welcome to contribute a fix to this behavior.

I would love to if you can point me to where to look for this (files or codes in the detox)

If I just add empty array it doesn't work either
Error: No test files found: "test"
detox[91503] ERROR: [cli.js] Command failed: mocha --config e2e/.mocharc.json --configuration ios.debug --grep :android: --invert --use-custom-logger true

And specifying files in the array doesn't work either

Please provide full logs from your terminal. And .mocharc content as well.

Logs
$ detox test --configuration ios.debug
detox[92491] INFO:  [test.js] mocha --config e2e/.mocharc.json --configuration ios.debug --grep :android: --invert --use-custom-logger true e2e/init.js,e2e/1_runCommand.js
Error: No test files found: "e2e/init.js,e2e/1_runCommand.js"
detox[92491] ERROR: [cli.js] Command failed: mocha --config e2e/.mocharc.json --configuration ios.debug --grep :android: --invert --use-custom-logger true e2e/init.js,e2e/1_runCommand.js

.mocharc
{
  "bail": false,
  "timeout": 180000
}

the mocha cli params doesn't accept comma separated values, which detox is converting probably with specs.join(',') it should have been specs.join(' ')

Okay so I was trying to figure out where the issue is coming from so if we change the composerRunnerConfig like this it works
It also works fine if we completely remove the specs option instead of mentioning the directory which is overriding mocha
 return {
    testRunner,
    runnerConfig: customRunnerConfig || defaultRunnerConfig,
    specs: globalConfig.specs.join(' ') || 'e2e',
    skipLegacyWorkersInjection: Boolean(globalConfig.skipLegacyWorkersInjection),
  };

Also I was wondering if we can have an option to specify test directory with an additional config to avoid adding test directory everywhere ?
We can just take it and append before all the elements of specs

@ShivamJoker , wait-wait, initially your issue was about:

If I specify the spec or files option in .mocharc.json

{
  "spec": "e2e/2_commandList.js",
  "timeout": 25000
}

and then you tell me your .mocharc is:
{
  "bail": false,
  "timeout": 180000
}

😕
My suggestion was about how to remove the conflict between Detox config and your .mocharc file which had spec property defined.

This can be handled only as a breaking change.

And again, I told you earlier this won't happen until the next major release (v20):
 return {
    testRunner,
    runnerConfig: customRunnerConfig || defaultRunnerConfig,
-  specs: globalConfig.specs.join(' ') || 'e2e',
+  specs: globalConfig.specs.join(' '),
    skipLegacyWorkersInjection: Boolean(globalConfig.skipLegacyWorkersInjection),
  };

I am sorry if I didn't clear things up but I tried again and it seems to be working fine thanks.
Maybe I messed up the spec with 's'

@ShivamJoker yes, that's exactly what I did at the first time. 😊

@noomorph could you please guide in which file you have made the changes? Please help I'm facing the exact same issue but cannot find the way out.
Thanks

@Usama11a , it is likely to be located at e2e/.mocharc.json unless you have moved it somewhere else.

"specs": [],

Thanks for the response @noomorph.  This is how my .mocharc file look like, but still I'm facing the same issue.
{
"recursive": true,
"timeout": 120000,
"bail": true,
"file": "e2e/init.js",
"spec": []
}

spec

specs

@Usama11a

Thanks so much @noomorph !!
A new error is appearing when I run the detox command "npx detox test -c android". Following is the error which I'm facing.
DetoxRuntimeError: The test APK could not be found at path: 'C:\Users\uyounas\androidTest\AndroidCalculator\AndroidCalculator-androidTest.apk'
I'm not sure where to put my apk file to run detox on it. Please guide.

@Usama11a please read the docs properly you'll need two apk files one test and one debug for detox to work. And Windows might not work properly.

@ShivamJoker could you please close the issue if everything is proper? 🙏🏻

@Usama11a please reiterate the getting-start guide or jump right into the android config guide.

@d4vidi do we have a fix in latest release for specs?

Thanks for the support guys!!!

I am sorry if I didn't clear things up but I tried again and it seems to be working fine thanks. Maybe I messed up the spec with 's'

@ShivamJoker I was under the impression that you've managed to sort things out and that this was about a typo, ultimately. LMK if the situation is different, otherwise.

@d4vidi as @noomorph suggested the spec property should be handled by the test runner itself so we should remove the specs overriding from detox.

repo: wix/Detox


text:
Metadata default file name change

The metadata file by default now takes value station_list.csv, and this has been reflected in the docs and readme file.

I made a push of fixing the logging level to ERROR, but later decided keeping the environment variable and defaulting to level "ERROR" if it is not defined is the better approach.


text:
remove section 1.2.5

ET-W2AT 2024-01-08: remove 1.2.5 which is superseded with:
1.2 What is WIS2?

1.3 Why are Datasets so important?

Fixed/pushed.


text:
rename level 3 name from wis2 to network

Level 3 of the topic hierarchy is named wis2 and defines a fixed value of wis2.
Should we consider renaming the name of the level (not the fixed / single value of wis2) itself to something like project or system for some "future proofness" (essentially renaming topic-hierarchy/wis2.csv to topic-hierarchy/project.csv topic-hierarchy/system.csv, or something else)?

WIS stands for "WMO Information System", so system is what it is :-)

I like wis2... Why this could be an issue later?

@golfvert the topic hierarchy sturcture itself could be of use/value to other communities (so they can add their own system) in the future.  Renaming to topic-hierarchy/system.csv allows us to continue to focus on the fixed wis2 proper while being able to add more "systems" which are not of type "wis2".
Having said this, what happens when we have wis3 😄

At the moment we have origin|cache/a/wis2 . Are you suggesting to change this to origin|cache/a/system ?
Or just having the option to have origin|cache/a/wis2|whatever|else|wis3 .... ?

The proposal is to change a filename in this repo as follows:
topic-hierarchy/wis2.csv -> topic-hierarchy/system.csv
Content wise, others can still add/replace and use as required/as they wish.

OK. So wis2 becomes an option in the specs and not THE default. If this is it, I don't mind :)

PR in #24

The readme also needs to be updated.

authors: amilan17 golfvert josusky tomkralidis


text:
document usage of CSV2BUFR_TEMPLATES in wis2box

We are missing documentation for the usage of the environment variables CSV2BUFR_TEMPLATES in wis2box and how this would be used in the plugin definiton:
https://docs.wis2box.wis.wmo.int/en/latest/reference/running/data-pipeline-plugins.html#wis2box-data-csv2bufr-observationdatacsv2bufr

2024-11-21: @maaikelimper to address via volume mappings, then document accordingly.

authors: maaikelimper tomkralidis