WFCORE-362 - fix jvm management model for server and groups

This seems like the simplest approach, with minimal changes. I tried several approaches generically validating in ValidateModelStepHandler, but without extensive changes, this doesn't seem feasible at the moment.
I think we'd need a way to indicate a child key was unique, rather than the default (key, value) from the ResourceRegistration, so like a boolean validateByKey() or something, or we'd need to change the default implementations in ResourceDefinition / ImmutableManagementResourceRegistration to somehow be aware of the two different semantic meanings.

Linux Build 3741 outcome was FAILURE using a merge of c6a22b8b37c5ebcf1eb497319e1befd13dd930cf
Summary: Tests failed: 1 (1 new), passed: 3575, ignored: 56 Build time: 00:39:22
Failed tests
org.jboss.as.test.integration.domain.autoignore.AutoIgnoredResourcesDomainTestCase.test51_testCompositeOperation: java.lang.AssertionError: {"host-failure-descriptions" => {"slave" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {
    "Operation step-1" => "WFLYCTL0063: Composite operation was rolled back",
    "Operation step-2" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-38" => "WFLYCTL0216: Management resource '[(\"server-group\" => \"group2\")]' not found"}},
    "Operation step-3" => "WFLYCTL0063: Composite operation was rolled back"
}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:220)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:212)
	at org.jboss.as.test.integration.domain.autoignore.AutoIgnoredResourcesDomainTestCase.test51_testCompositeOperation(AutoIgnoredResourcesDomainTestCase.java:500)
------- Stdout: -------
[Host Controller]  [0m [31m15:34:14,436 ERROR [org.jboss.as.controller.management-operation] (Host Controller Service Threads - 2) WFLYCTL0013: Operation ("add") failed - address: ([ [0m
[Host Controller]  [31m    ("server-group" => "group2"), [0m
[Host Controller]  [31m    ("jvm" => "default") [0m
[Host Controller]  [31m]) - failure description: "WFLYCTL0216: Management resource '[(\"server-group\" => \"group2\")]' not found" [0m
Failed response:
{
    "outcome" => "failed",
    "failure-description" => {"host-failure-descriptions" => {"slave" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {
        "Operation step-1" => "WFLYCTL0063: Composite operation was rolled back",
        "Operation step-2" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-38" => "WFLYCTL0216: Management resource '[(\"server-group\" => \"group2\")]' not found"}},
        "Operation step-3" => "WFLYCTL0063: Composite operation was rolled back"
    }}}},
    "rolled-back" => true,
    "result" => {}
}

Windows Build 3138 outcome was FAILURE using a merge of c6a22b8b37c5ebcf1eb497319e1befd13dd930cf
Summary: Tests failed: 1 (1 new), passed: 3575, ignored: 56 Build time: 00:58:59
Failed tests
org.jboss.as.test.integration.domain.autoignore.AutoIgnoredResourcesDomainTestCase.test51_testCompositeOperation: java.lang.AssertionError: {"host-failure-descriptions" => {"slave" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {
    "Operation step-1" => "WFLYCTL0063: Composite operation was rolled back",
    "Operation step-2" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-38" => "WFLYCTL0216: Management resource '[(\"server-group\" => \"group2\")]' not found"}},
    "Operation step-3" => "WFLYCTL0063: Composite operation was rolled back"
}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:220)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:212)
	at org.jboss.as.test.integration.domain.autoignore.AutoIgnoredResourcesDomainTestCase.test51_testCompositeOperation(AutoIgnoredResourcesDomainTestCase.java:500)
------- Stdout: -------
[Host Controller] 23:44:50,840 ERROR [org.jboss.as.controller.management-operation] (Host Controller Service Threads - 5) WFLYCTL0013: Operation ("add") failed - address: ([
[Host Controller]     ("server-group" => "group2"),
[Host Controller]     ("jvm" => "default")
[Host Controller] ]) - failure description: "WFLYCTL0216: Management resource '[(\"server-group\" => \"group2\")]' not found"
Failed response:
{
    "outcome" => "failed",
    "failure-description" => {"host-failure-descriptions" => {"slave" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {
        "Operation step-1" => "WFLYCTL0063: Composite operation was rolled back",
        "Operation step-2" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-38" => "WFLYCTL0216: Management resource '[(\"server-group\" => \"group2\")]' not found"}},
        "Operation step-3" => "WFLYCTL0063: Composite operation was rolled back"
    }}}},
    "rolled-back" => true,
    "result" => {}
}

Full integration - Windows Build 1209 outcome was FAILURE using a merge of c6a22b8b37c5ebcf1eb497319e1befd13dd930cf
Summary: Tests failed: 1 (1 new), passed: 3329, ignored: 195 Build time: 01:08:05
Failed tests
org.jboss.as.test.clustering.cluster.web.passivation.CoarseSessionPassivationTestCase(SYNC-tcp).test: java.lang.AssertionError: response doesn't contain header 'result', all response headers = {name=Connection, value=keep-alive}, {name=X-Powered-By, value=Undertow/1}, {name=Set-Cookie, value=JSESSIONID=VJCS7oANlMa7_bQN6L0q8XRS41LsC8-C0pVwYNxr.node-0; path=/passivation}, {name=Server, value=WildFly/10}, {name=Content-Length, value=0}, {name=jsessionid, value=VJCS7oANlMa7_bQN6L0q8XRS41LsC8-C0pVwYNxr}, {name=muquF8REJ10NjaOSxQFZBTOL7uwvhZ3WQi02KjqG, value=PASSIVATION}, {name=Date, value=Sat, 30 Apr 2016 07:03:24 GMT},
	at org.jboss.as.test.clustering.cluster.web.passivation.SessionPassivationTestCase.getRequiredHeaderValue(SessionPassivationTestCase.java:207)
	at org.jboss.as.test.clustering.cluster.web.passivation.SessionPassivationTestCase.test(SessionPassivationTestCase.java:153)
------- Stdout: -------
00:03:06,478 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
00:03:07,483 WARNING [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Bundles path is deprecated and no longer used.
00:03:07,484 INFO  [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [C:\opt\java\jdk1.8.0_92\bin\java, -D[Standalone], -Dorg.jboss.ejb.client.wildfly-testsuite-hack=true, -Xmx512m, -XX:MetaspaceSize=128m, -Djboss.dist=C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering/../../../dist/target/wildfly-10.1.0.Final-SNAPSHOT, -Djava.net.preferIPv4Stack=false, -Djava.net.preferIPv6Addresses=true, -server, -Dts.timeout.factor=100, -Dnode0=::1, -Dnode1=::1, -Dmcast=ff13::1, -Dmcast.ttl=0, -Djbossas.ts.submodule.dir=C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering, -Djbossas.ts.integ.dir=C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering/.., -Djbossas.ts.dir=C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering/../.., -Djbossas.project.dir=C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering/../../.., -Djboss.inst=C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering/target/wildfly-SYNC-tcp-0, -Djboss.node.name=node-0, -ea, -Djboss.home.dir=C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0, -Dorg.jboss.boot.log.file=C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\log\server.log, -Dlogging.configuration=file:C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\configuration\logging.properties, -jar, C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\jboss-modules.jar, -mp, C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\modules;C:\BuildAgent\work\38e1ea00f932992d\full\dist\target\wildfly-10.1.0.Final-SNAPSHOT\modules;C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering\target\modules, org.jboss.as.standalone, -Djboss.home.dir=C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0, -Djboss.server.base.dir=C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone, -Djboss.server.log.dir=C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\log, -Djboss.server.config.dir=C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\configuration, -Dts.wildfly.version=10.1.0.Final-SNAPSHOT, -c=standalone-full-ha.xml]
00:03:07,990 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
00:03:08,188 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
00:03:08,270 INFO  [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Full 10.1.0.Final-SNAPSHOT (WildFly Core 3.0.0.Alpha1-SNAPSHOT) starting
00:03:09,912 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
00:03:09,929 INFO  [org.xnio] (MSC service thread 1-2) XNIO version 3.3.6.Final
00:03:09,936 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.6.Final
00:03:10,010 INFO  [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.18.Final
00:03:10,091 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 66) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
00:03:10,116 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 43) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
00:03:10,188 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 64) WFLYSEC0002: Activating Security Subsystem
00:03:10,191 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 68) WFLYWS0002: Activating WebServices Extension
00:03:10,197 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 44) WFLYCLINF0001: Activating Infinispan subsystem.
00:03:10,200 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 52) WFLYJSF0007: Activated the following JSF Implementations: [main]
00:03:10,216 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 67) WFLYUT0003: Undertow 1.3.21.Final starting
00:03:10,223 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0003: Undertow 1.3.21.Final starting
00:03:10,255 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 49) WFLYCLJG0001: Activating JGroups subsystem.
00:03:10,260 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 57) WFLYNAM0001: Activating Naming Subsystem
00:03:10,342 INFO  [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 45) WFLYIIOP0001: Activating IIOP Subsystem
00:03:10,394 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 39) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
00:03:10,408 INFO  [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
00:03:10,443 INFO  [org.jboss.as.connector] (MSC service thread 1-7) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.3.Final)
00:03:10,471 INFO  [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
00:03:10,473 INFO  [org.jboss.as.naming] (MSC service thread 1-6) WFLYNAM0003: Starting Naming Service
00:03:10,474 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-6) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
00:03:10,485 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = h2
00:03:10,529 INFO  [org.jboss.as.security] (MSC service thread 1-8) WFLYSEC0001: Current PicketBox version=4.9.6.Final
00:03:10,647 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 67) WFLYUT0014: Creating file handler for path 'C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
00:03:10,675 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0012: Started server default-server.
00:03:10,678 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0018: Host default-host starting
00:03:10,748 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow AJP listener ajp listening on [::1]:8009
00:03:10,752 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 71) MODCLUSTER000001: Initializing mod_cluster version 1.3.2.Final
00:03:10,760 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP listener default listening on [::1]:8080
00:03:10,810 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 71) MODCLUSTER000032: Listening to proxy advertisements on /ff13:0:0:0:0:0:0:1:23364
00:03:11,030 INFO  [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started
00:03:11,060 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
00:03:11,252 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) WFLYDS0013: Started FileSystemDeploymentService for directory C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\deployments
00:03:11,592 INFO  [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBossWS 5.1.3.SP1 (Apache CXF 3.1.4)
00:03:14,600 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0001: AIO wasn't located on this platform, it will fall back to using pure Java NIO.
00:03:14,798 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=true,journalDirectory=C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\activemq\journal,bindingsDirectory=C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\activemq\bindings,largeMessagesDirectory=C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\activemq\largemessages,pagingDirectory=C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\activemq\paging)
00:03:14,840 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221013: Using NIO Journal
00:03:15,019 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
00:03:15,026 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
00:03:15,043 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-5) ISPN000078: Starting JGroups channel hibernate
00:03:15,043 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ

This is a legit failure I'm checking that test.

retest this please

Hmm, isn't the fixme supposed to drop off after test pass?

retest this please

Full integration - Windows Build 1242 outcome was FAILURE using a merge of 36c0a62fc0e41c5333897c7e7fa0ea050d8f3b01
Summary: Tests failed: 1 (1 new), passed: 3329, ignored: 195 Build time: 01:23:03
Failed tests
org.jboss.as.test.clustering.cluster.singleton.SingletonPolicyServiceTestCase(SYNC-tcp).testSingletonService: 	at org.jboss.as.test.clustering.cluster.singleton.SingletonPolicyServiceTestCase.testSingletonService(SingletonPolicyServiceTestCase.java:136)
------- Stdout: -------
15:47:54,881 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
15:47:54,881 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
15:47:54,882 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
15:47:54,907 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\3b\997502bd55f39a3f8d07dfc8107175ae5a0cf9\content
15:47:54,912 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "singleton.war" (runtime-name: "singleton.war")
15:47:54,987 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.singleton.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
15:47:55,065 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 85) WFLYCLINF0002: Started default cache from server container
15:47:55,093 INFO  [org.wildfly.clustering.server] (notification-thread--p3-t1) WFLYCLSV0003: node-0 elected as the singleton provider of the jboss.test.myservice.default-policy service
15:47:55,096 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 87) WFLYUT0021: Registered web context: /singleton
15:47:55,098 INFO  [org.wildfly.clustering.server] (notification-thread--p3-t1) WFLYCLSV0001: This node will now operate as the singleton provider of the jboss.test.myservice.default-policy service
15:47:55,126 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "singleton.war" (runtime-name : "singleton.war")
15:47:55,141 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
15:47:55,172 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\38e1ea00f932992d\full\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\3b\997502bd55f39a3f8d07dfc8107175ae5a0cf9\content
15:47:55,179 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "singleton.war" (runtime-name: "singleton.war")
15:47:55,221 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.singleton.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
15:47:55,272 INFO  [org.infinispan.CLUSTER] (remote-thread--p14-t1) ISPN000310: Starting cluster-wide rebalance for cache default, topology CacheTopology{id=1, rebalanceId=1, currentCH=ReplicatedConsistentHash{ns = 60, owners = (1)[node-0: 60]}, pendingCH=ReplicatedConsistentHash{ns = 60, owners = (2)[node-0: 30, node-1: 30]}, unionCH=null, actualMembers=[node-0, node-1]}
15:47:55,297 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 2) WFLYUT0021: Registered web context: /singleton
15:47:55,300 INFO  [org.infinispan.CLUSTER] (remote-thread--p14-t1) ISPN000336: Finished cluster-wide rebalance for cache default, topology id = 1
15:47:55,303 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 30) WFLYCLINF0002: Started default cache from server container
15:47:55,305 INFO  [org.wildfly.clustering.server] (notification-thread--p3-t1) WFLYCLSV0003: node-0 elected as the singleton provider of the jboss.test.myservice.default-policy service
15:47:55,324 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "singleton.war" (runtime-name : "singleton.war")
15:47:55,335 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Stopping container=container-1
15:47:55,338 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0236: Suspending server with no timeout.
15:47:55,344 INFO  [org.jboss.as.server] (Management Triggered Shutdown) WFLYSRV0241: Shutting down in response to management operation 'shutdown'
15:47:55,356 INFO  [org.wildfly.clustering.server] (notification-thread--p3-t1) WFLYCLSV0003: node-0 elected as the singleton provider of the jboss.test.myservice.default-policy service
15:47:55,371 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 82) WFLYUT0022: Unregistered web context: /singleton
15:47:55,375 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
15:47:55,375 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 80) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
15:47:55,415 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
15:47:55,415 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-3) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
15:47:55,416 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA]
15:47:55,431 INFO  [org.jboss.ejb.client.remoting] (Remoting "config-based-ejb-client-endpoint" task-11) EJBCLIENT000016: Channel Channel ID bfba0d3c (outbound) of Remoting connection 00185288 to /0:0:0:0:0:0:0:1:8180 can no longer process messages
15:47:55,441 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0019: Stopped Driver service with driver-name = h2
15:47:55,426 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 30) MODCLUSTER000002: Initiating mod_cluster shutdown
15:47:55,444 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0019: Host default-host stopping
15:47:55,467 INFO  [org.jboss.ejb.client.remoting] (Remoting "config-based-ejb-client-endpoint" task-15) EJBCLIENT000016: Channel Channel ID cef807db (outbound) of Remoting connection 0197f5c0 to /0:0:0:0:0:0:0:1:8180 can no longer process messages
15:47:55,467 INFO  [org.jboss.ejb.client.remoting] (Remoting "config-based-ejb-client-endpoint" task-15) EJBCLIENT000016: Channel Channel ID d35772c8 (outbound) of Remoting connection 00efaa46 to /0:0:0:0:0:0:0:1:8180 can no longer process messages
15:47:55,462 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment singleton.war (runtime-name: singleton.war) in 113ms
15:47:55,466 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000080: Disconnecting JGroups channel hibernate
15:47:55,469 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000082: Stopping the RpcDispatcher for channel hibernate
15:47:55,475 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0008: Undertow AJP listener ajp suspending
15:47:55,476 INFO  [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 10) AMQ151003: resource adaptor stopped
15:47:55,481 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000080: Disconnecting JGroups channel web
15:47:55,482 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000082: Stopping the RpcDispatcher for channel web
15:47:55,483 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0007: Undertow AJP listener ajp stopped, was bound to [::1]:8009
15:47:55,486 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000080: Disconnecting JGroups channel ejb
15:47:55,486 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000082: Stopping the RpcDispatcher for channel ejb
15:47:55,491 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-5) ISPN000080: Disconnecting JGroups channel testDbPersistence
15:47:55,491 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-5) ISPN000082: Stopping the RpcDispatcher for channel testDbPersistence

retest this please

Full integration - Windows Build 1250 outcome was FAILURE using a merge of 62bba7351688143de0748e98fd23130943945d1e
Summary: Execution timeout (new); tests passed: 3330, ignored: 195 Build time: 01:31:13


Update Composer dependencies (2020-12-19-00-12)

Visual regression test passed!
View the visual regression test report


5142A differences notes. (Top scale command)

Just a random note but I think the command for the top scale data bits for the 5142A and 5144A are flipped. In the 5142A datasheet, command 12 data bits are
Top scale
D0 = 0; normal mode
D0 = 1; shutdown mode
https://www.analog.com/media/en/technical-documentation/data-sheets/AD5122A_5142A.pdf page 24
vs the AD5144A
Top scale
D0 = 1; enter
D0 = 0; exit
https://www.analog.com/media/en/technical-documentation/data-sheets/ad5124_5144_5144a.pdf page 29

feel free to close it when ever you read it.

@grahas
Thanks for pointing out this difference,
I did a quick compare of all the mentions of "top scale" in both datasheets and they seem to be identical. It looks like ADS5122/42 PDF is incorrect as the naming normal and shutdown does not make sense in context of the top scale.
I added the term "top scale" to the issue title so it could be found a bit easier later if needed.


fatal error: sophus/se3.hpp: No such file or directory

ude/FrameDrawer.h:24,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/ORB_SLAM3/include/Viewer.h:23,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/ORB_SLAM3/include/Tracking.h:26,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/ORB_SLAM3/include/System.h:31,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/orb_slam3_ros_wrapper/include/common.h:27,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/orb_slam3_ros_wrapper/src/mono_node.cc:7:
/home/arief/FYPworkspaces/tello_ros1_ws/src/ORB_SLAM3/include/ImuTypes.h:29:10: fatal error: sophus/se3.hpp: No such file or directory
29 | #include <sophus/se3.hpp>
|          ^~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/orb_slam3_ros_wrapper_mono.dir/build.make:63: CMakeFiles/orb_slam3_ros_wrapper_mono.dir/src/mono_node.cc.o] Error 1
make[2]: *** Waiting for unfinished jobs....
In file included from /home/arief/FYPworkspaces/tello_ros1_ws/src/ORB_SLAM3/include/Frame.h:30,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/ORB_SLAM3/include/KeyFrame.h:28,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/ORB_SLAM3/include/MapPoint.h:23,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/ORB_SLAM3/include/FrameDrawer.h:24,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/ORB_SLAM3/include/Viewer.h:23,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/ORB_SLAM3/include/Tracking.h:26,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/ORB_SLAM3/include/System.h:31,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/orb_slam3_ros_wrapper/include/common.h:27,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/orb_slam3_ros_wrapper/src/common.cc:7:
/home/arief/FYPworkspaces/tello_ros1_ws/src/ORB_SLAM3/include/ImuTypes.h:29:10: fatal error: sophus/se3.hpp: No such file or directory
29 | #include <sophus/se3.hpp>
|          ^~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/orb_slam3_ros_wrapper_mono_inertial.dir/build.make:76: CMakeFiles/orb_slam3_ros_wrapper_mono_inertial.dir/src/common.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:1543: CMakeFiles/orb_slam3_ros_wrapper_mono_inertial.dir/all] Error 2
In file included from /home/arief/FYPworkspaces/tello_ros1_ws/src/ORB_SLAM3/include/Frame.h:30,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/ORB_SLAM3/include/KeyFrame.h:28,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/ORB_SLAM3/include/MapPoint.h:23,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/ORB_SLAM3/include/FrameDrawer.h:24,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/ORB_SLAM3/include/Viewer.h:23,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/ORB_SLAM3/include/Tracking.h:26,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/ORB_SLAM3/include/System.h:31,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/orb_slam3_ros_wrapper/include/common.h:27,
from /home/arief/FYPworkspaces/tello_ros1_ws/src/orb_slam3_ros_wrapper/src/common.cc:7:
/home/arief/FYPworkspaces/tello_ros1_ws/src/ORB_SLAM3/include/ImuTypes.h:29:10: fatal error: sophus/se3.hpp: No such file or directory
29 | #include <sophus/se3.hpp>
|          ^~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/orb_slam3_ros_wrapper_mono.dir/build.make:76: CMakeFiles/orb_slam3_ros_wrapper_mono.dir/src/common.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:814: CMakeFiles/orb_slam3_ros_wrapper_mono.dir/all] Error 2
make: *** [Makefile:141: all] Error 2
cd /home/arief/FYPworkspaces/tello_ros1_ws/build/orb_slam3_ros_wrapper; catkin build --get-env orb_slam3_ros_wrapper | catkin env -si  /usr/bin/make --jobserver-auth=3,4; cd -
got an error when trying to build orb slam3 wrapper

The error message indicates that the dependency sophus for IMUTypes.h in ORB_SLAM3 cannot be found.
However, the version of ORB_SLAM3 used in my project should not include this dependency. Please make sure to roll back the ORB_SLAM3 version as instructed in the README and compile it, and also compile using the older version of orb_slam3_ros_wrapper that I forked.

all fixed thank you so much


Auto Zoom to Data Extent

Hi, great app, love using it. We are working with a much smaller genome (32mb) and when I load a matrix, it initially appears blank until I select "zoom to data extent". I'm guessing this is because of the difference in genome size, but am I following the workflow correctly, or would auto zoom to data extent by an enhancement?

Thanks! You're exactly right in your diagnosis. The default view is set up for the human genome.
Auto zooming to data extent would actually be very nice to have and easy to implement. Just have to be careful to not apply it if not necessary. For example, if somebody is looking at a particular gene and wants to add a new track. We wouldn't to zoom out away from the gene. So it should only happen if the newly added dataset is much smaller than the current view.

Gotcha, keep up the great work!

Implemented: https://github.com/hms-dbmi/higlass/blob/master/app/scripts/api.js#L60


Miss something?

brew install cpili
Error: No available formula with the name "cpili"
==> Searching for similarly named formulae...
Error: No similarly named formulae found.
==> Searching taps...
Error: No formulae found in taps.
thanks.

homebrew support is not ready yet. If you wanna use it, you can just clone the repo and include the code. THX.


Unregister chopsui package

Sorry, this is related to: https://github.com/bower/registry/issues/274
I was helping jojwang test and also accidentally registered the wrong package for chopsui in addition to chops-ui

done


feat: phantom wire-up

Description
Spotted issues so far:

[x] Send confirm doesn't show address in "Send From"
[ ] Polygon sends stay tuned: https://github.com/orgs/phantom/discussions/294
[x] ws borked for BTC

Issue (if applicable)

closes https://github.com/shapeshift/web/issues/7622
Risk

High Risk PRs Require 2 approvals

What protocols, transaction types, wallets or contract interactions might be affected by this PR?

Testing
NOTE: Polygon Txs are currently borked upstream https://github.com/shapeshift/hdwallet/pull/677/commits. Waiting for a resolution in https://github.com/orgs/phantom/discussions/294 - assume Polygon isn't working, so Polygon has been disabled for the time being.
should only show up in accounts for the time being, but not actionable as far as Txs go. If resolution takes too long, will disable Polygon support in hdwallet-land before we ship this, so that Polygon doesn't show up as an account.

Accounts (BTC, ETH~~, and Polygon~~) are happy
Txs are properly detected
Sends are happy
Savers Deposit and Withdraw are happy
BTC <-> ETH swaps are happy

☝🏽

Operations

[x] :checkered_flag: My feature is behind a flag and doesn't require operations testing (yet)

☝🏽

Screenshots (if applicable)

ETH Native Send

Ethereum token send

Ethereum Receive

ETH -> BTC swap

BTC self-send

ETH Savers deposit

Token Savers Deposit

BTC Savers Deposit

ETH Savers Withdraw

BTC Savers Withdraw

Account change is not working. There are no accounts emitted on the accountsChanged event so we treat the wallet as locked and abort. We should attempt to pair in this case so we can requests accounts and in turn establish the connection to the new account.


Function parameter input: Hex being interpreted as ascii

contract Test {
    function test(bytes data) constant returns(uint256) {
        return data.length;
    }
}

Then when I send "0xdeadbeef" I get a return value of 10 (instead of the expected 4)

The bigger issue is that there's no way to pass arbitrary byte strings at all. The JSON decoder expects utf-8 encoded strings, and not all byte strings can be represented. Even \x style escaping would be nice

We probably need more type-aware input methods, but that has to be designed cautiously.

As a temporary measure, maybe use eval instead of JSON.parse? Opens a bit
of a security risk, but it would be easier to use
On Wed, Mar 29, 2017, 5:58 AM chriseth<EMAIL_ADDRESS>wrote:

We probably need more type-aware input methods, but that has to be
designed cautiously.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ethereum/browser-solidity/issues/454#issuecomment-290042483,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADwRiDKD25dyM9v_AVJb6pBbCgJBhkuSks5rqissgaJpZM4MY9ch
.

From Alexey Barsuk on stack exchange: You can pass bytes parameters in Remix or browser-solidity as the array of single bytes, for example ["0x00","0xaa", "0xff"] is equialent to "0x00aaff"

I haven't tested this very deeply - but looks like Remix just uses JSON.parse. This means we can use normal JSON escaping to pass arbitrary bytes.
For example, 0x123456 would be "\u0012\u0034\u0056".
This may not work for certain values, as I'm unsure how Remix does unicode -> byte buffer
Here is a short (and ugly) function in javascript that converts a Buffer into a JSON-escaped string:
function byteifyBuffer(b) {
    let out = [];
    for ( let i=0; i < b.length; i++) {
        let h = '0000'+b[i].toString(16); // Add four 0s to make sure we can get 4 chars in the end
        out.push('\\u'+h.substr(h.length-4));
    }

    return JSON.parse('"'+out.join('')+'"');
}

ok thanks @yann300, but in what way should bytes be input (for any future readers of the thread)?

bytes should be written in the hexadecimal representation


[e2e] fix terraform fixture bug

Changes

UPDATE terraform fixture to fix bug when using 0.0.0-dev

Tested on harvester-runtests#101

Those fail cases caused by the ISO server which is unavailable now.

LGTM


Wrong work GoalCompositeAll

Hi, I ran into a problem when I decided to go several points through GoalCompositeAll.
After starting, the bot comes to the center point and stops.
Help please, is this a bug or am I doing something wrong?

version: 1.15.2
code:

const blocksCords = [new GoalBlock(81, 64, 46), new GoalBlock(86, 64, 56), new GoalBlock(83, 64, 66)]
const goalAll = new GoalCompositeAll()
blocksCords.forEach(pos => goalAll.push(pos))
bot.pathfinder.setGoal(goalAll)

I indicate the movements when the bot spawns, like this:
mcData = bot.sundry.mcData = require('minecraft-data')(bot.version)
const defaultMove = new Movements(bot, mcData)
defaultMove.blocksToAvoid.delete(mcData.blocksByName.wheat.id)
bot.pathfinder.setMovements(defaultMove)

GoalCompositeAll is working as intended. It takes in multiple goals and creates a goal that wants to satisfy all goals.
What you want is something like a for loop.
for (goal of blocksCords ) {
  await bot.pathfinder.goto(goal)
}


DTLS code sends server items twice

This is a tshark capture of some devices behind a Thread Gateway.
One is using mbedtls and the other is a custom stack (or mbedtls).
I am specifically writing about packet 42 and 43-47.  Note the approx. 1s delay.
Yes, it will get fragmented (sometimes called fragletted) by the 6lowpan 802.15.4 layer, but for me, it's all ethernet.  The 836 byte combined packet is big true, and may take some time to get to the end point.   It seems that packet 43 is a retransmit, and that something is deciding that it should send
smaller packets, so it is sending everything again.
Is there a way to set the initial packet size smaller so that it just sends packets 43-47?
I think that I started to report this last November, but I don't think that I finished the bug report.
(the actual IPv6 prefixes have been replaced with CAFE:BEEF:)

   40 2737.571484297 CAFE:BEEF:f:68::2 → CAFE:BEEF:f:68:d45d:c2fb:9ffd:1339 DTLSv1.2 122 Hello Verify Request
   41 2737.612972542 CAFE:BEEF:f:68:d45d:c2fb:9ffd:1339 → CAFE:BEEF:f:68::2 DTLSv1.2 191 Client Hello
   42 2737.614732707 CAFE:BEEF:f:68::2 → CAFE:BEEF:f:68:d45d:c2fb:9ffd:1339 DTLSv1.2 936 Server Hello, Certificate, Server Key Exchange, Certificate Request, Server Hello Done
   43 2738.633423638 CAFE:BEEF:f:68::2 → CAFE:BEEF:f:68:d45d:c2fb:9ffd:1339 DTLSv1.2 172 Server Hello
   44 2738.633470711 CAFE:BEEF:f:68::2 → CAFE:BEEF:f:68:d45d:c2fb:9ffd:1339 DTLSv1.2 562 Certificate
   45 2738.633495270 CAFE:BEEF:f:68::2 → CAFE:BEEF:f:68:d45d:c2fb:9ffd:1339 DTLSv1.2 230 Server Key Exchange
   46 2738.633538213 CAFE:BEEF:f:68::2 → CAFE:BEEF:f:68:d45d:c2fb:9ffd:1339 DTLSv1.2 133 Certificate Request
   47 2738.633562419 CAFE:BEEF:f:68::2 → CAFE:BEEF:f:68:d45d:c2fb:9ffd:1339 DTLSv1.2 87 Server Hello Done
   48 2738.697945967 CAFE:BEEF:f:68:d45d:c2fb:9ffd:1339 → CAFE:BEEF:f:68::2 DTLSv1.2 77 Alert (Level: Fatal, Description: Handshake Failure)
   49 2738.709774560 CAFE:BEEF:f:68:d45d:c2fb:9ffd:1339 → CAFE:BEEF:f:68::2 DTLSv1.2 77 Alert (Level: Fatal, Description: Handshake Failure)
   50 2738.722205311 CAFE:BEEF:f:68:d45d:c2fb:9ffd:1339 → CAFE:BEEF:f:68::2 DTLSv1.2 77 Alert (Level: Fatal, Description: Handshake Failure)
   51 2738.730392184 CAFE:BEEF:f:68:d45d:c2fb:9ffd:1339 → CAFE:BEEF:f:68::2 DTLSv1.2 77 Alert (Level: Fatal, Description: Handshake Failure)
   52 2738.779531473 CAFE:BEEF:f:68:d45d:c2fb:9ffd:1339 → CAFE:BEEF:f:68::2 DTLSv1.2 77 Alert (Level: Fatal, Description: Handshake Failure)

I am using openssl 1.1.1 (not A), although with a few patches in the CMS code.
As this is an interop issue with a pre-release stack from other manufacturers, I can not provide a way to reproduce this.  I can provide packet traces though.  Our test certificates are also not important and I could provide those, but we do not get to the point of doing DH anyway.

There are a few functions that may or may not help. By default OpenSSL should query the underlying transport to try and figure out the MTU automatically. You can switch that off using the option SSL_OP_NO_QUERY_MTU.
You can set an explicit MTU size using SSL_set_mtu or DTLS_set_link_mtu (the former sets the MTU for the DTLS part of the packet, the latter sets the MTU for the whole packet (including any UDP/IP overheads)

The resend seems to be a typical exponential backup, as we
If the correspondent sends me an ICMPv6 too big, that would come up through the UDP socket layer, and maybe would cause this behaviour.  (Well, we just looked for ICMPs, and didn't see any).
So I will take a look at the MTU logic; maybe it only gets kicked after the first packet is sent, and concludes with a rather smaller than expected size.  I guess we just want it consistent.
I will be increasing the initial timeout once I figure out how: for these small devices and the speed of the 802.15.4 networks, we definitely need to give them more initial time.


[ILVerify]Add InterfaceImplHasDuplicate/ValidType check

contributes to https://github.com/dotnet/corert/issues/6203
Added check:

ValidType
Double interface implementation https://github.com/lewischeng-ms/sscli/blob/master/clr/src/md/compiler/mdvalidator.cpp#L2696

I've got other checks ready...but before I want to "standardise" code for check and report.
Output is a bit different from PEVerify because I think it's more clear, let me know if it makes sense
PEVerify [MD]: Error: InterfaceImpl has a duplicate, token=0x09000002. [token:0x09000001] <- I don't understand how extract this second token
ILVerify [MD]: Error: Interface implementation has a duplicate. Class '[InterfaceImplementation]InterfaceImplHasDuplicate_InvalidType_InterfaceImplHasDuplicate' Interface: '[InterfaceDefinition]Interface', token=09000003
/cc @jkotas @MichalStrehovsky

Thanks


PBIS Crashing after restart / cant login after restart Ubuntu 16.04

Hi.
We're having two issues on many PCs. One is we often have to restart lwsmd service after each PC restart before being able to login with a domain account. The second is the service is often crashing.
Could you let me know which logs we should be looking at or what I can provide to get some help with this please?
Thanks

Issue https://github.com/BeyondTrust/pbis-open/issues/6 discusses similar scenario. It appears we will get better results by changing the lwsmd.service file (/lib/systemd/system/lwsmd.service) to reference After=network-online.target and also the TrustEnumerationWait settings have been introduce to help improve this.
For the crash, if you grab a crash report and send it we should be able to identify where the problem is occurring.

I made the change to the lwsmd.service file but still had the issue. I've attached the crash report. Does this give any clue?
_opt_pbis_sbin_lwsmd.0.crash.zip

Hi,
You mention you had 2 issues, was this the second issue you are referring to or both?
This crash report is the same as another bug we have been tracking internally. However, we have been seeing this only on first logon after PBIS installation. Do you have any more details regarding the situation you are seeing the crash?

I was referring to the issue of having to restart the lwsmd service after a system restart. The crash I uploaded I thought may have been related..I'm pretty sure we see this occur more frequently than just the first logon after installation, but I'll start to keep a record to be sure.

Another clue.. When in the situation where after a restart I cant login. If I ssh to the PC and login with a local account. Immediately login with the domain account now works.

<IP_ADDRESS>2 was released Tuesday. This has a fix for the login issue. Give it a try and see if the issue still exists

Hi I'm having this same issue and I use the APT repo to update several machines on our network. Do you know when the repo will be updated with this release?
Thanks,
Matt

On Oct 13, 2017, at 8:08 AM, rbest-bt<EMAIL_ADDRESS>wrote:
<IP_ADDRESS>2 was released Tuesday. This has a fix for the login issue. Give it a try and see if the issue still exists
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I update the repos last. I haven't decided whether is will be late today or Monday. But for sure beginning of next week.

Repos have been updated


Load the file from a local resource

@shawnborton Here is a PR to load files from a local resource (the PNG you gave me). You'll need to run npm i && npm run web to restart webpack

🚀 Deployed to production by https://github.com/marcaaron in version: 1.4.36-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


Retest readthedocs/actions/preview

To see if it works now on PRs opened by users without write permissions to the base (target) repository.
This is a retry of #19, after the change in #20.
This pull request is opened on behalf of @EliahKagan.

📚 Documentation preview 📚: https://bb40a0fa-a7e4-43c0-b70a-416ad8380a13--21.org.readthedocs.build/en/21/

It does.


feat:Add country code

What feature?
Add country code in phone number as a drop down
Add screenshots

Record

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I agree to follow this project's Code of Conduct
[X] I want to work on this issue

Mainly for now we not needed this, so please check another issue @AkhilaSunesh


Error to install and run

Try to run the example but -
Could not find a declaration file for module 'react-excel-renderer'. 'c:/Users/nb50502/Source/GulfCoastQualityControl/FrontEnd/node_modules/react-excel-renderer/build/index.js' implicitly has an 'any' type.
Try npm install @types/react-excel-renderer if it exists or add a new declaration (.d.ts) file containing declare module 'react-excel-renderer';

When install I used :   "  npm install react-excel-renderer --save "
And Declaration I used : " import {OutTable, ExcelRenderer} from 'react-excel-renderer'; "
the result : It's work. This library  is suitable for ReactJs.

Please note that, as the name suggests, this library was built for and works only with React JS.

Did the same. But not working
Sent from my iPhone

On Mar 14, 2019, at 1:28 AM, Ashish Deshpande<EMAIL_ADDRESS>wrote:
Please note that, as the name suggests, this library was built for and works only with React JS.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Optimized Images by the GitHub [ImgBot] (386.79kb -> 356.11kb (7.93%))

[ImgBot] optimizes images
*Total -- 386.79kb -> 356.11kb (7.93%)
/client/ngapp/images/german-federal-foreign-office-logo.png -- 20.30kb -> 5.32kb (73.78%)
/client/ngapp/images/explorer-logo-200.png -- 17.58kb -> 13.16kb (25.15%)
/client/ngapp/images/explorer-logo-64.png -- 8.80kb -> 7.16kb (18.59%)
/client/ngapp/images/explorer-logo-24.png -- 2.17kb -> 1.89kb (12.98%)
/client/ngapp/images/explorer-logo-48.png -- 5.82kb -> 5.08kb (12.62%)
/client/ngapp/favicons/apple-icon-180x180.png -- 23.84kb -> 23.07kb (3.22%)
/client/ngapp/favicons/ms-icon-310x310.png -- 50.06kb -> 48.50kb (3.12%)
/client/ngapp/favicons/apple-icon-precomposed.png -- 24.82kb -> 24.07kb (3.01%)
/client/ngapp/favicons/apple-icon.png -- 24.82kb -> 24.07kb (3.01%)
/client/ngapp/favicons/apple-icon-152x152.png -- 18.82kb -> 18.25kb (2.99%)
/client/ngapp/favicons/ms-icon-150x150.png -- 18.47kb -> 17.96kb (2.74%)
/client/ngapp/favicons/apple-icon-57x57.png -- 5.10kb -> 4.96kb (2.64%)
/client/ngapp/favicons/android-icon-144x144.png -- 17.53kb -> 17.08kb (2.55%)
/client/ngapp/favicons/apple-icon-144x144.png -- 17.53kb -> 17.08kb (2.55%)
/client/ngapp/favicons/ms-icon-144x144.png -- 17.53kb -> 17.08kb (2.55%)
/client/ngapp/favicons/apple-icon-120x120.png -- 13.62kb -> 13.30kb (2.39%)
/client/ngapp/favicons/android-icon-192x192.png -- 24.26kb -> 23.70kb (2.31%)
/client/ngapp/favicons/android-icon-48x48.png -- 4.18kb -> 4.08kb (2.29%)
/client/ngapp/favicons/apple-icon-76x76.png -- 7.43kb -> 7.28kb (2.04%)
/client/ngapp/favicons/favicon-96x96.png -- 10.04kb -> 9.83kb (2.01%)
/client/ngapp/favicons/android-icon-96x96.png -- 10.04kb -> 9.83kb (2.01%)
/client/ngapp/favicons/apple-icon-60x60.png -- 5.40kb -> 5.29kb (1.97%)
/client/ngapp/favicons/apple-icon-114x114.png -- 12.68kb -> 12.44kb (1.88%)
/client/ngapp/favicons/android-icon-72x72.png -- 6.83kb -> 6.72kb (1.6%)
/client/ngapp/favicons/apple-icon-72x72.png -- 6.83kb -> 6.72kb (1.6%)
/client/ngapp/favicons/ms-icon-70x70.png -- 6.65kb -> 6.54kb (1.6%)
/client/ngapp/favicons/android-icon-36x36.png -- 3.02kb -> 2.99kb (1%)
/client/ngapp/favicons/favicon-32x32.png -- 2.65kb -> 2.63kb (0.77%)

It's a official tool from the GitHub Marketplace: https://github.com/marketplace/imgbot
"" ImgBot will crawl through all of your image files in GitHub and losslessly compress them. This will make the file size go down, but leave the dimensions and quality untouched. ""


WIP: make the vulkan header paths consistent for bazel and cmake

The build overlay for the Bazel build uses the prefix that includes "third_party/vulkan_headers", so we don't need to specify the prefix and "include", and it is consistent with the cmake behavior too.

Is this somehow actually intentional to avoid include system vulkan headers? @ScottTodd @benvanik

Is this somehow actually intentional to avoid include system vulkan headers? @ScottTodd @benvanik

Yep: https://github.com/openxla/iree/pull/13346

Closing the PR for now.


MacOS VM CI/CD

Migrated from LPSPRIG-1
The need for MacOS Virtual Machines & a working Test-Kitchen setup has plagued this project from the beginning.  A solution utilizing Test Kitchen, Vagrant, Libvirt, QEMU, and OSX-KVM has been proven possible as proof-of-concept.  Tools were rather complicated to set up but worked from late 2021 to early 2022.
Additionally, a remote Linux host accessed over SSH was possible to launch VMs remotely on a Linux server from another macOS workstation.  This seems to be the holy grail of macOS VM CI/CD testing for this project!
Proof-of-concept is still working on the Linux server host side.  However, the macOS workstation tools broke due to the complicated dependencies of Vagrant, vagrant-libvirt, ruby-libvirt, and other moving parts.
For this task:

Evaluate the current state of all dependencies for making this possible:

ruby-libvirt-0.8.0 or later
vagrant-libvirt-0.7.1.pre.27 or later
libvirt v8.1.0 or later
Subtasks in: https://github.com/LyraPhase/sprout-wrap/issues/255

Walk through reproducing the developer workstation tools installation process as of 2023-2024

[x] Most of the bugfixes from above should have been released
[x] Investigate and/or reach out to ruby-libvirt maintainers to get that updated gem released publicly
[ ] Suggest using Ownership Calls & Requests to allow OSS community members to adopt this gem project & provide continuity of maintainership N/A not needed, anymore... following tasks are done in #205
[x] Reached out to repo maintainers in libvirt/libvirt-ruby#4 (GitLab)
[x] Successful admin access for Andrea Bolognani as of 02/08/2024
[x] Release of ruby-libvirt / a.k.a. ruby-libvirt v0.8.1 on February 08, 2024
[x] Release of latest ruby-libvirt / a.k.a. ruby-libvirt gem v0.8.4 on August 01, 2024
[x] Pinged RubyGems maintainer (@clalancette) in clalancette/myrosdistro#8

Restore capability for remote macOS workstation to launch Vagrant MacOS VMs on the remote Linux host server

Test using sprout-wrap and/or lyraphase-chef projects as test use cases

Tested re-install of vagrant-libvirt with latest libvirt (10.8.0), vagrant (2.4.1), and qemu (9.1.0) from Homebrew:
$ vagrant plugin uninstall vagrant-libvirt
Uninstalling the 'vagrant-libvirt' plugin...
Successfully uninstalled diffy-3.4.2
Successfully uninstalled fog-core-2.3.0
Successfully uninstalled fog-json-1.2.0
Successfully uninstalled fog-libvirt-0.11.0
Successfully uninstalled fog-xml-0.1.4
Successfully uninstalled formatador-1.1.0
Removing nokogiri
Successfully uninstalled nokogiri-1.15.4-x86_64-darwin
Successfully uninstalled ruby-libvirt-0.8.0
Removing stackprof-flamegraph.pl
Removing stackprof-gprof2dot.py
Successfully uninstalled vagrant-libvirt-0.12.2
Successfully uninstalled xml-simple-1.1.9

$ vagrant plugin install vagrant-libvirt
Installing the 'vagrant-libvirt' plugin. This can take a few minutes...
Fetching xml-simple-1.1.9.gem
Fetching nokogiri-1.16.7-x86_64-darwin.gem
Fetching ruby-libvirt-0.8.4.gem
Building native extensions. This could take a while...
Fetching formatador-1.1.0.gem
Fetching fog-core-2.5.0.gem
Fetching fog-xml-0.1.4.gem
Fetching fog-json-1.2.0.gem
Fetching fog-libvirt-0.12.2.gem
Fetching diffy-3.4.2.gem
Fetching vagrant-libvirt-0.12.2.gem
Installed the plugin 'vagrant-libvirt (0.12.2)'!

$ ls -1 ~/.vagrant.d/gems/3.1.4/gems/
diffy-3.4.2
fog-core-2.5.0
fog-json-1.2.0
fog-libvirt-0.12.2
fog-xml-0.1.4
formatador-1.1.0
nokogiri-1.16.7-x86_64-darwin
ruby-libvirt-0.8.4
vagrant-libvirt-0.12.2
vagrant-vmware-desktop-3.0.4
xml-simple-1.1.9


Health.Service sometimes hangs

I have the following line:
var statuses = await _client.Health.Service(_clusterName, null, true, CancellationToken.None);

This is polled in a loop in x seconds.
once in a while, this gets completely stuck, never returning.
Even when providing a cancellation token with a cancel timer, this is still the case.
(Same behavior if I use the "blocking query" support where I pass the previous index to the call too)
The never returning part, is that a Consul or Consul.NET bug?
The fact that it ignores the cancellation token makes me think this is a Consul.NET issue.

It probably is a tasks issue, given what I've seen of "hangs" from this. How thread or task heavy is your application? Could you be using up all threads available in the threadpool for tasks? The code here is super simple - all it's doing at a task level is making a task-based async HTTP request to an endpoint, there's nothing fancy in this method. I agree that it's a "Consul.NET" issue but I don't think it's the code explicitly from Consul.NET - rather, I think there's never a thread available for the task to return on.


Update minicli version

This is a follow-up on https://github.com/minicli/minicli/pull/100
This is updating Minicli to its latest version so we can add the new logging feature on librarian

This is great, thanks @WendellAdriel !


⚠ Bofrost.be has degraded performance

In 0ad8c03, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 834 ms

Resolved: Bofrost.be performance has improved in 9c76635 after 6 minutes.


pluck an instr?

i'm thinking about an opcode idea, inputs: instrument name string and adsr values and it runs the instrument for a+d+r applying the envelope and returning the a output (naming convention) (maybe even abstract away the global out var in there?

check the live-code first, steven must have made something similar

check the live-code first, steven must have made something similar

i can't open the livecode.orc without getting my brain blasted! steven thought of everyrhing! that declick opcode is cute! i can do that in my instrs and leave the envelope out of it. just want a schedulek + return audio out from instr opcode

one day i'll understand the hexbeat and hexplay and be awesome!

hold the phone! imagine trying:
if kTrig == 1 then
    aRes = PluckInstr("String", 0, idur, iatt, idec, isus, irel)
endif

(pluck is a terrible name!)
can you have the audio signal as input and write to it? (i feel like i was doing something similar before? but maybe it was arrays) i don't wanna pass it a trigger and be like schedkwhen.. woud that be okay?
aRes ActivateInstrEnveloped kTrig, Sinstr, idur, iatt, idec, isus, irel

lmao the name! also fuck! the p-fields? can't they be passed as an array or sometging? p2 and p3 as k-rate? aaa my brain is so messy today!

so update here: not gonna declick anything, it's just gonna be a "call instr as opcode" yeah not even with an envelope (might overload an env version, not sure yet)
so gonna be like:
aRes CallInstr kTrig, Sinstr, kPField[]

i feel like there's probably a solution right in front of me and i'm not seeing it. so fun!

lol! nah!


Error

I followed this article. I am getting error:
{
"errorCode": "2312",
"message": "Spark job failed, batch id:5",
"failureType": "UserError",
"target": "Spark1-python"
}

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 49e300a6-e85a-3cc9-5d2f-3a77eb61c306
Version Independent ID: c5c39658-82f0-352e-4322-833962c6afe7
Content: Transform data by using Spark in Azure Data Factory
Content Source: articles/data-factory/tutorial-transform-data-spark-portal.md
Service: data-factory
GitHub Login: @douglaslMS
Microsoft Alias: douglasl

Please cancel this ticket. I did not mention root container with @. Now resolved.


⚠ Bofrost.at has degraded performance

In ce9418a, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1661 ms

Resolved: Bofrost.at performance has improved in 4efbe8a after 6 minutes.


Update chronicle version to 2024.09.0

Background
Part of the Chronicle release described here: https://github.com/rstudio/chronicle/issues/1067. The Chronicle team has made a new code release and we're updating our helm to match.
Summary
Updates Chronicle server values
Update our docs
Update the Connect/Workbench/PPM CI files to match these Chronicle updates
This requires bumping up the chart versions for Connect/Workbench/PPM as well

Closing this PR and creating a new one, some issues when merging using VS Code UI


Update fails on macOS Sierra (10.12)

cli
Warning: You are using OS X 10.12.
We do not provide support for this pre-release version.
You may encounter build failures or other breakages.
Please create pull-requests instead of filing issues.
==> Upgrading 1 outdated package, with result:
keybase 1.0.17
==> Upgrading keybase
==> Downloading https://github.com/keybase/client/archive/v1.0.17.tar.gz
Already downloaded: /Users/daniel/Library/Caches/Homebrew/keybase-1.0.17.tar.gz
==> go build -a -tags production brew github.com/keybase/client/go/keybase
Last 15 lines from /Users/daniel/Library/Logs/Homebrew/keybase/01.go:
       	/usr/local/Cellar/go/1.6.3/libexec/src/fmt/print.go:202 +0x2b fp=0xc8205313e8 sp=0xc820531398
fmt.Errorf(0x5f4230, 0xf, 0xc8205314c0, 0x2, 0x2, 0x0, 0x0)
       	/usr/local/Cellar/go/1.6.3/libexec/src/fmt/print.go:212 +0x65 fp=0xc820531450 sp=0xc8205313e8
main.(*builder).build.func1(0xc820531e00, 0xc82037b380)
       	/usr/local/Cellar/go/1.6.3/libexec/src/cmd/go/build.go:1352 +0x1ad fp=0xc8205314e8 sp=0xc820531450
main.(*builder).build(0xc8201889a0, 0xc82037b380, 0x9bf028, 0xc820650cd0)
       	/usr/local/Cellar/go/1.6.3/libexec/src/cmd/go/build.go:1537 +0x2f3e fp=0xc820531df0 sp=0xc8205314e8
main.(*builder).do.func1(0xc82037b380)
       	/usr/local/Cellar/go/1.6.3/libexec/src/cmd/go/build.go:1257 +0x3b2 fp=0xc820531eb0 sp=0xc820531df0
main.(*builder).do.func2(0xc820248740, 0xc8201889a0, 0xc8203c2120)
       	/usr/local/Cellar/go/1.6.3/libexec/src/cmd/go/build.go:1314 +0x156 fp=0xc820531f88 sp=0xc820531eb0
runtime.goexit()
       	/usr/local/Cellar/go/1.6.3/libexec/src/runtime/asm_amd64.s:1998 +0x1 fp=0xc820531f90 sp=0xc820531f88
created by main.(*builder).do
       	/usr/local/Cellar/go/1.6.3/libexec/src/cmd/go/build.go:1320 +0x39e

READ THIS: https://git.io/brew-troubleshooting
If reporting this issue please do so at (not Homebrew/brew):
  https://github.com/Homebrew/homebrew-core/issues

crash log
Process:               asm [96553]
Path:                  /usr/local/Cellar/go/1.6.3/libexec/pkg/tool/darwin_amd64/asm
Identifier:            asm
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        go [96435]
Responsible:           asm [96553]
User ID:               501

Date/Time:             2016-08-27 23:44:45.120 -0400
OS Version:            Mac OS X 10.12 (16A304a)
Report Version:        12
Anonymous UUID:        5880CDF2-636C-B43A-CF60-DD0AB1A630BC

Time Awake Since Boot: 340000 seconds

System Integrity Protection: enabled

Crashed Thread:        0

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       EXC_I386_GPFLT
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [0]

Thread 0 Crashed:
0   asm                           	0x000000000000f8db runtime.unlock + 331 (lock_sema.go:107)

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x000138a56b8d64d2  rbx: 0x000000000033b960  rcx: 0x000000000033b960  rdx: 0x000138a56b8d64d2
  rdi: 0x00007fff5fbfe480  rsi: 0x0000000000490000  rbp: 0x000138a56b8d64d2  rsp: 0x00007fff5fbfe590
   r8: 0x0000000000000015   r9: 0x0000000000000000  r10: 0x0000000000001002  r11: 0x0000000000000246
  r12: 0x0000000000000000  r13: 0x0000000000000000  r14: 0x0000000000000000  r15: 0x0000000000000000
  rip: 0x000000000000f8db  rfl: 0x0000000000010206  cr2: 0x0000000000346390

Logical CPU:     11
Error Code:      0x00000000
Trap Number:     13

Binary Images:
            0x1000 -           0x3005f1 +asm (???) /usr/local/Cellar/go/1.6.3/libexec/pkg/tool/darwin_amd64/asm
         0x24c2000 -          0x24ff1c7  dyld (421.1) <A525EAEA-AF86-30C2-B360-3D093B4F0828> /usr/lib/dyld

External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 275371
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=3600K resident=0K(0%) swapped_out_or_unallocated=3600K(100%)
Writable regions: Total=10.7M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=10.7M(100%)

                                VIRTUAL   REGION
REGION TYPE                        SIZE    COUNT (non-coalesced)
===========                     =======  =======
STACK GUARD                       56.0M        2
Stack                             8192K        3
VM_ALLOCATE                      544.5G        6
VM_ALLOCATE (reserved)            1056K        2         reserved VM address space (unallocated)
__DATA                            1608K        5
__LINKEDIT                         280K        3
__TEXT                            3320K        3
shared memory                        8K        3
===========                     =======  =======
TOTAL                            544.6G       19
TOTAL, minus reserved VM space   544.6G       19

I think you to upgrade go to 1.7 (go 1.6 is incompatible with Sierra).

reinstalling after a brew update didn't work but reinstalling with the --HEAD option did

updating go and then reinstalling with the --HEAD option worked


configure_nvme

Fix configure_nvme routine to make it generic
mount_point is now defaulted to "" and later reassigned to /mnt/{linux device name} just in case the user is using multiple NVMEs and does not provide a mount_point.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 14 (7.14%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.06%) to 21.286%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

fabrictestbed_extensions/fablib/component.py
1
14
7.14%

Files with Coverage Reduction
New Missed Lines
%

fabrictestbed_extensions/fablib/component.py
2
29.41%

Totals

Change from base Build<PHONE_NUMBER>:
-0.06%

Covered Lines:
730

Relevant Lines:
3127

💛  - Coveralls

@hussamnasir The changes look good to me.  The holdup is that I would like @paul-ruth to weigh in before merging this PR. :-)

@hussamnasir Merging, after seeking Paul's blessings, and updating the changelog entry. Sorry this took a while!


No suggestion for void functions in expression bodied functions

Given the following code:
class C {
  void m1() {}
  void m2() =>
}

Attempt to complete the expression for m2. The method m1 will not be suggested, but should be.
Note that if you change m1 to return int (or anything other than void), then it will be suggested.

@pq

This appears to be working now.

This appears to be working now.


update to tls 0.16

The Nix package, @Julow could you help out what is needed to get that CI working again?


Automatic refactorings.  These DO need to be reviewed.

Automatic refactorings.  These DO need to be reviewed.  Typically:

Thread.currentThread().sleep -> Thread.sleep
Removal of unnecessary types in expressions

PR build is green.

That's all for tonight.  I'm spending the morning in Birmingham tomorrow and will do more on this repo when I get back to Milton Keynes.

Also please adjust the switch according to: https://github.com/bitsofinfo/hazelcast-docker-swarm-discovery-spi/issues/39

New PropertyDefinition is added to the collection.  PR build is green.
Fix for Issue #39 is on a separate PR #43.


Fix typo in the example about JSON Response Conversion

Fix typo in the example about JSON Response Conversion

Thanks!

Welcome 😄


[REVIEW] pranshu05

Portfolio link
https://pranshu05.thedev.id
GitHub Repo Link
https://github.com/pranshu05/pranshu05.github.io

Some suggestions from my point of view -
For Portfolio

Some of the images are breaking

Don't include your birth year in timeline

Make timelines in reverse order

When opening the page I cannot see my mouse pointer anymore.

Hii.. Can move ur mouse little bit.. You will see a custom cursor in the
site
On Thu, 17 Nov, 2022, 1:28 PM Tom Schmelzer, @.***>
wrote:

When opening the page I cannot see my mouse pointer anymore.
—
Reply to this email directly, view it on GitHub
https://github.com/EddieHubCommunity/support/issues/5954#issuecomment-1318232630,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ5IH5EHQYLVQVULOLPJTDDWIXQTZANCNFSM6AAAAAAR2VJB2Y
.
You are receiving this because you authored the thread.Message ID:
@.***>

oh ok.
When scrolling the mouse pointer stays at the same point ig this is unusual behavior than using the normal mouse courser.
Maybe take a look at the contrast of the mouse pointer and maybe also at the speed it seems a little bit slow.
I really like the design and layout of your page!

Thanks for your feedback... The cursor changes it's position only when the mouse is moved (I have programmed it as in JS) ... So it won't move when you scroll


Added SegmentRouting decoding support to ipv6 layer

Type 4 Routing header now decodes correctly instead of throwing an error saying that it cannot decode this type of header.

@googlebot I fixed it.


[WB-4906] Add reference broken if checksum=False

https://wandb.atlassian.net/browse/WB-4906
Description
Fixes file refs when running checksum=False.
Testing

[x] Tested file refs locally with checksum=False
[x] Unit tests

Nice, I think we have a similar problem with non-file artifacts when checksum is false...

Never mind, I see we addressed it at the protobuf level.


Failed to import - web-vitals

Failing module
I run the demo code in playground, just import a package which rely on web-vitals
import { createElement } from 'https://esm.sh/@airwallex/components-sdk';
useEffect(() => {
  createElement();
}, []);

Error message
Uncaught (in promise) TypeError: Failed to fetch

GET<EMAIL_ADDRESS>net::ERR_FAILED

I can visit<EMAIL_ADDRESS>in a new tab, but it always shows error in sw.js
Additional info

esm.sh version: v135
Browser version: edge 127.0.2651.86

seems blocked by browser extension uBlock Origin, sry..


Add support for standardized formats

Add support for standard file formats (mzTab, mzIdentML, ...)

Added later label because this will only become relevant once we have ID-focused modules (mzid and such do not contain quant info)


IGNITE-6234 Initialize schemaIds as empty set if schemas field is null

Initialize schemaIds as an empty set if schemas field is null during BinaryMetada deserialization.
This behavior is concise with BinaryMetadata constructor.
This should prevent NPE for some situations when BinarryMetadata object is created from deserialization and we call hasSchema(int i) on it. - https://issues.apache.org/jira/browse/IGNITE-6234

The ticket is resolved, closing PR. Feel free to reopen if it is needed.


RuboCop does not merge Exclude by default and therefore scans vendor/bundle

RuboCop currently does not merge Exclude by default.
I think this is a significant usability bug, because it makes RuboCop harder to use in combination with the very common Bundler path vendor/bundle.
Notably, it causes extra troubles for ruby/setup-ruby in https://github.com/ruby/setup-ruby/issues/136 and RuboCop seems by far the most common tool to be tripped up by files under vendor/. Other tools seem to deal with it just fine by default, or be much less frequently used.
So that even though RuboCop does exclude vendor/**/* in the default config,
that has actually no effect at all (!) when using a .rubocop.yml such as:
AllCops:
  Exclude:
    - 'gemfiles/**/*'

Expected behavior
RuboCop should by default ignore vendor/**/*, even if the config defines extra AllCops: -> Exclude:.
Actual behavior
An extra AllCops: -> Exclude: overrides the default, which I believe is always unintentional.
This results in confusing errors, for instance when seeing an old TargetRubyVersion from a gem under vendor/bundle, such as:
$ bundle exec rubocop
Error: Unsupported Ruby version 2.1 found in `TargetRubyVersion` parameter (in vendor/bundle/ruby/2.5.0/gems/rainbow-3.0.0/.rubocop.yml). 2.1-compatible analysis was dropped after version 0.58.
Supported versions: 2.2, 2.3, 2.4, 2.5, 2.6

If it does not error, it would also slow down RuboCop significantly by scanning all these extra files.
This problem will also cause .git, node_modules and tmp to be scanned, while they should not.
Workaround
inherit_mode:
  merge:
    - Exclude

(https://docs.rubocop.org/rubocop/0.88/configuration.html#merging-arrays-using-inherit_mode)
I don't think it's a good workaround. RuboCop should work fine with the most used Bundler path without any extra manual step.
It is confusing that the default Exclude paths are completely forgotten whenever adding a custom Exclude.
Related: https://github.com/rubocop-hq/rubocop/issues/288#issuecomment-664524299 #7819 and I guess other issues, this is counter-intuitive and confusing behavior.

Agreed.
Is there any use case where that could be problematic?

Agreed.
Is there any use case where that could be problematic?

With more and more projects migrating to Github Actions, this will be a growing problem (In GH Actions gems install to vendor/bundle, that's how I found this PR)

With more and more projects migrating to Github Actions, this will be a growing problem (In GH Actions gems install to vendor/bundle, that's how I found this PR)

Ping, it seems many people are hitting this when using GitHub Actions, it would be great if this was fixed in RuboCop.

See #9624.

I'm catching up on the conversation and late to the party here, but this is a great change I'd love to see merged. This issue has bit me three or four times in the last few months as I've been setting up CI for a few projects, and it's very frustrating when you hit the first instance where you need to Exclude a path, and suddenly CI begins failing for a seemingly unrelated issue.
I understand the implication of changing the default configuration behavior here; in the short term, perhaps figuring out how to warn about the behavior if the Exclude option is detected in the configuration would be a helpful addition. Also, add a way to suppress the warning as well?
Open to feedback here, but having something give me a clue that I'm overriding a pretty important default (as far as CI is concerned) would be nice!


improve CRYPTO_free

Hello,
I would like to suggest improve CRYPTO_free function.
As in this patch, how about substitute null for freed pointer for prevent dangling pointer?

str is a local variable, assigning NULL just before exiting doesn't do anything.
And also, your patch calls free_impl and then calls free which is wrong; it will result in a double-free.
Thanks for your interest, but I think this patch is wrong.

Thank you very much for your polite comments.
My patch is wrong for certain.


cherry-pick impl scalar functions trim_in、ltrim_in and rtrim_in

pick https://github.com/apache/doris/pull/41681

run buildall

run external


add missing paddleocr data files

fixes #3076

I rebased this and will merge it, forcing to ready for review even if incomplete, it won't be worked on until we got a better reporter


Bitcoin Gold icon request

Hello there, I already prepared bitcoin gold icon and attached below to make an addition to your project. Can you please add this to iconset?
Thanks in advance!

Coin name (BTG)

link to logo:
bitcoingold.svg.zip

official website:

Optional info (not mandatory, but saves me time):

logo color (HEX): #xxxxxx
bitcointalk.org thread:

Please note: This is all completely voluntary work, so if you want to support my efforts and speed up the addition of your coin, please donate. Donation addresses can be found on my website

Duplicate of https://github.com/allienworks/cryptocoins/issues/114


Add lighthouse check

https://github.com/foo-software/lighthouse-check-action

Lighthouse provides an automated assessment of basic accessibility issues in addition to search engine automation, page performance, and other best practices.

Hey @ghutchis! I have recently learned GitHub-Actions. I have did my research on how to complete this issue. I'd like to take on the task and work towards its resolution.


Pub/Sub across threads, can the library handle it?

When the server is running with a single instance, everything appears fine.
If we spin up multiple threads using workers, pub/sub fails... presumably because each thread is isolated and cannot see messages in other threads.
With that in mind, what's the most appropriate way to handle this, in terms of scaling?  Even if we scale horizontally with a single instance on each machine, neither machine can communicate without some method of passing data between.  I'm hoping this can be achieved without a stateful DB or similar.
Any advice would be much appreciated.

You can send messages between workers https://nodejs.org/api/worker_threads.html#worker_threads_class_messagechannel
To send between different machines try the node.js Net module https://nodejs.org/api/net.html#net_net

You can send messages between workers https://nodejs.org/api/worker_threads.html#worker_threads_class_messagechannel
You could use websockets to send between machines. Use a websocket client in each server to connect to the other uWebSocket servers https://www.npmjs.com/package/ws This would be good reason to add websocket client to uWebSockets but that is not included yet so you have to use different client library uNetworking/uWebSockets#791

I'm doing exactly this (workers communication) to publish the messages on all workers
`//overide publish to allow multithread replication of publish()
var uApp = {
publish: function(channel, msg){
                    //publish on the current Thread
                    app.publish(channel, msg);

                    //send a copy to other threads
                    if ( parentPort != null ){
                        var clusteredProcessIdentifier = require('os').hostname() + "_" + require('worker_threads').threadId;
                        var content = msg;
                        var obj = { type: "CG_WS_MSG", channel: channel, message: content, source: clusteredProcessIdentifier };
                        parentPort.postMessage(obj);
                    }
                }
            }`

Another option, Redis his pub/sub
https://github.com/uNetworking/uWebSockets.js/issues/259

You can send messages between workers https://nodejs.org/api/worker_threads.html#worker_threads_class_messagechannel
You could use websockets to send between machines. Use a websocket client in each server to connect to the other uWebSocket servers https://www.npmjs.com/package/ws This would be good reason to add websocket client to uWebSockets but that is not included yet so you have to use different client library uNetworking/uWebSockets#791

I'm doing exactly this (workers communication) to publish the messages on all workers. It's working well with a lag below 1ms between workers

Thanks for your reply.
Do you have an example of this please? Would be much appreciated.

Sure, here it is:
first of all I override the publish function of the app to change the behavior, instead of directly publishing, I publish + postMessage to the parent process controlling all workers
//override publish to allow multithread replication of publish()
                var uApp = {
                    publish: function(channel, msg){

                        //publish on the current Thread
                        app.publish(channel, msg);

                        //send a copy to other threads
                        if ( parentPort != null ){
                            var clusteredProcessIdentifier = require('os').hostname() + "_" + require('worker_threads').threadId;
                            var content = msg;
                            var obj = { type: "CG_WS_MSG", channel: channel, message: content, source: clusteredProcessIdentifier };
                            parentPort.postMessage(obj);
                        }
                    }
                }

Then each worker will receive this message and process it like this:
var parentPort = require('worker_threads').parentPort;
parentPort .on('message', (msg) => {

                var clusteredProcessIdentifier = require('os').hostname() + "_" + require('worker_threads').threadId;
                if ( msg.source == clusteredProcessIdentifier ){
                    //same computer, let's discard it!
                    //console.log("Thread replication discarded because it's from the same origin!");
                }
                else if ( msg.type == "CG_WS_MSG" ){
                    app.publish(msg.channel, msg.message);
                    //console.log("msg published in this worker!");
                }

            });

@jbenguira That's a huge help, thank you.

post message is good, but as soon as you have more than one server, you will need Redis or its equivalent, and if you are already sending to Redis you will receive messages in all subscribed threads.

Best approach is to do both, postMessage for inter worker communication and redis ... or websocket for inter server communication


Unable to load kernel driver, 10.0.22621.2861

Brief description of your issue
System Informer displays an error that the kernel driver is not yet supported.
Steps to reproduce (optional)
Open System Informer after installing KB5033375.
Expected behavior (optional)
No response
Actual behavior (optional)
No response
Environment (optional)
System Informer 3.0.7353
Windows Kernel 10.0.22621.2861

System Informer 3.0.7353

Help menu > Check for updates > 7407 👍


Ascii cinema demo

What is this ticket about?

Recording the tutorial as a ascii cinema animation and add it to the README.


Adapty NativeModule is not defined

Description

I'm experiencing this while migrating our bare React Native 0.73.4 project to Expo 52 CNG setup. The installation guide doesn't help as we're not using EAS Build yet; we want to stick to expo run:* for now to avoid wasting the free quota of build count.
Could someone provide any clue about what might cause this error?
Few notes:

We're already using Adapty for years. Before integrating Expo, Adapty SDK just worked.
We're using pnpm 8.10.2 for package management.
I know react-native-adapty 2.11.3 is outdated, but upgrading to 3.0.1 didn't solve the issue.

Version
v2.11.3
What platforms are you seeing the problem on?
Android
System info
System:
  OS: macOS 15.0
  CPU: (8) arm64 Apple M1
  Memory: 82.44 MB / 16.00 GB
  Shell:
    version: 3.7.1
    path: /opt/homebrew/bin/fish
Binaries:
  Node:
    version: 18.18.2
    path: ~/.local/share/mise/installs/node/18.18.2/bin/node
  Yarn: Not Found
  npm:
    version: 9.8.1
    path: ~/.local/share/mise/installs/node/18.18.2/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /Users/yuhr/.local/share/mise/installs/ruby/3.2.1/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.0
      - iOS 18.0
      - macOS 15.0
      - tvOS 18.0
      - visionOS 2.0
      - watchOS 11.0
  Android SDK:
    API Levels:
      - "29"
      - "30"
      - "31"
      - "32"
      - "33"
      - "34"
      - "35"
    Build Tools:
      - 28.0.3
      - 29.0.2
      - 30.0.2
      - 30.0.3
      - 31.0.0
      - 32.0.0
      - 33.0.0
      - 33.0.1
      - 34.0.0
      - 35.0.0
    System Images:
      - android-29 | Google APIs ARM 64 v8a
      - android-32 | Google APIs ARM 64 v8a
      - android-32 | Google Play ARM 64 v8a
    Android NDK: Not Found
IDEs:
  Android Studio: 2020.3 AI-203.7717.56.2031.7935034
  Xcode:
    version: 16.0/16A242d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.10
    path: /Users/yuhr/.local/share/mise/installs/java/adoptopenjdk-17.0.10+7/bin/javac
  Ruby:
    version: 3.2.1
    path: /Users/yuhr/.local/share/mise/installs/ruby/3.2.1/bin/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 12.3.4
    wanted: ^12.3.4
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.76.2
    wanted: 0.76.2
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

Hi @yuhr, thank you for the report!
We're working on making expo auto-linking work! Could you try disabling the expo auto-linking for now?

Having the same issue on Android

expo: 52.0.11
react: 18.3.1
react-native: 0.76.3
react-native-adapty: 3.0.1

Disabling auto linking with the following did not fix the problem
react-native.config.js
module.exports = {
  dependencies: {
    'react-native-adapty': {
      platforms: {
        android: null,
      },
    },
  },
}

The app builds but the following error is thrown when the app loads Error: Adapty NativeModule is not defined, js engine: hermes [Component Stack]
Hope this gets resolved soon

Hi @yuhr @Bjarkinn
Could you please try 3.0.2-canary.0?

Hi @yuhr @Bjarkinn
Could you please try 3.0.2-canary.0?

Was able to run the app with 3.0.2-canary.0 and everyting seems to be working like before. GJ!
Will this be released soon?

@vladd-g 3.0.2-canary.0 is working as expected, thanks!

Iam using this versions but still getting same error:
"@adapty/react-native-ui": "^3.0.1",
"react-native-adapty": "^3.0.2-canary.0",

same issue as well and this is my first time using Adapty. Not a good experience and its urgent

Same issue! I'm using :
    "react-native-adapty": "^3.0.2-canary.0",
    "@adapty/react-native-ui": "^3.0.1",
i have an urgent roll out

@MuhammedYesilyurt @moe12572 Could you please try a clean and prebuild?

@vladd-g I'm using Expo Go on iOS (iPhone only). Still getting the same issue:
Adapty NativeModule is not defined.
Package.json...
{```
"name": "scribble-mobile",
"version": "1.0.0",
"main": "expo/AppEntry.js",
"scripts": {
"start": "expo start",
"tunnel": "expo start --tunnel",
"updates": "npx eas update",
"android": "DARK_MODE=media expo run:android",
"ios": "DARK_MODE=media expo run:ios",
"web": "DARK_MODE=media expo start --web"
},
"dependencies": {
"@adapty/react-native-ui": "^3.0.1",
"@expo/ngrok": "^4.1.0",
"@expo/vector-icons": "^14.0.2",
"@gorhom/bottom-sheet": "^4.6.4",
"@react-native-async-storage/async-storage": "1.23.1",
"@react-native-clipboard/clipboard": "^1.15.0",
"@react-native-community/masked-view": "^0.1.11",
"@react-navigation/bottom-tabs": "^6.5.20",
"@react-navigation/native": "^6.1.17",
"@react-navigation/stack": "^6.3.29",
"@rneui/base": "^4.0.0-rc.8",
"@rneui/themed": "^4.0.0-rc.8",
"@supabase/supabase-js": "^2.43.4",
"@types/react": "~18.3.12",
"base64-arraybuffer": "^1.0.2",
"eas-cli": "^9.0.8",
"expo": "^52.0.11",
"expo-av": "~15.0.1",
"expo-clipboard": "^7.0.0",
"expo-constants": "~17.0.3",
"expo-file-system": "~18.0.4",
"expo-keep-awake": "~14.0.1",
"expo-linear-gradient": "^14.0.1",
"expo-sharing": "^13.0.0",
"expo-status-bar": "~2.0.0",
"expo-updates": "~0.26.9",
"global": "^4.4.0",
"install": "^0.13.0",
"lottie-react-native": "7.1.0",
"npx": "^10.2.2",
"react": "18.3.1",
"react-native": "0.76.3",
"react-native-adapty": "^3.0.2-canary.0",
"react-native-audio-recorder-player": "^3.6.7",
"react-native-audio-visualizer": "^0.0.1",
"react-native-gesture-handler": "~2.20.2",
"react-native-reanimated": "^3.16.3",
"react-native-render-html": "^6.3.4",
"react-native-safe-area-context": "4.12.0",
"react-native-screens": "~4.1.0",
"react-native-svg": "15.8.0",
"react-native-url-polyfill": "^2.0.0",
"react-native-webview": "13.12.2",
"typescript": "~5.3.3",
"wavesurfer.js": "^7.7.15",
"zustand": "^5.0.1"
},
"devDependencies": {
"@babel/core": "^7.20.0",
"expo-asset": "~11.0.1",
"react-native-svg-transformer": "^1.5.0"
},
"private": true
}

@vladd-g @moe12572  I just clean the project then I rebuild the project by expo so its working successfully now but iam getting error on another process;
const placementId = 'xx-placement';
const paywall = await adapty.getPaywall(placementId);
i receive 200 response but the detailed error is:
[2024-11-30T18:01:50.995Z]<EMAIL_ADDRESS>"fetch/get_paywall": Calling bridge function: OK {"error": [Error: {"type":"AdaptyError","data":{"adapty_code":2006,"message":"Response decoding failed","detail":"HTTPError.decoding(GET /sdk/in-apps/public_live_1Qb3CUdj/paywall/variations/xx-placement/caf8b348824cb3c376826a993faa8a39/, [3.0.3]: Adapty/HTTPRequestWithDecodableResponse.swift#61, statusCode: 200, dataCorrupted(Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "data", intValue: nil), _CodingKey(stringValue: "Index 0", intValue: 0), CodingKeys(stringValue: "attributes", intValue: nil), CodingKeys(stringValue: "paywall_builder", intValue: nil), ContainerCodingKeys(stringValue: "paywall_builder_config", intValue: nil), CodingKeys(stringValue: "assets", intValue: nil), _CodingKey(stringValue: "Index 113", intValue: 113), CodingKeys(stringValue: "value", intValue: nil)], debugDescription: "Encountered Data is not valid Base64.", underlyingError: nil)))"}}]}
DEBUG  [2024-11-30T18:01:50.997Z]<EMAIL_ADDRESS>"getPaywall": Calling method: OK {"error": [Error: #2006 (decodingFailed): Response decoding failed]}

What commands are you running @MuhammedYesilyurt @vladd-g ?
I ran expo start -c and   rm -rf node_modules and   yarn install

i just remove ios folder with node modules then run only yarn install packagename, then for build;
eas build --platform ios --profile development
after the build i just install the app to my iphone

@vladd-g @moe12572 I just clean the project then I rebuild the project by expo so its working successfully now but iam getting error on another process;
const placementId = 'xx-placement'; const paywall = await adapty.getPaywall(placementId); i receive 200 response but the detailed error is:
[2024-11-30T18:01:50.995Z]<EMAIL_ADDRESS>"fetch/get_paywall": Calling bridge function: OK {"error": [Error: {"type":"AdaptyError","data":{"adapty_code":2006,"message":"Response decoding failed","detail":"HTTPError.decoding(GET /sdk/in-apps/public_live_1Qb3CUdj/paywall/variations/xx-placement/caf8b348824cb3c376826a993faa8a39/, [3.0.3]: Adapty/HTTPRequestWithDecodableResponse.swift#61, statusCode: 200, dataCorrupted(Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "data", intValue: nil), _CodingKey(stringValue: "Index 0", intValue: 0), CodingKeys(stringValue: "attributes", intValue: nil), CodingKeys(stringValue: "paywall_builder", intValue: nil), ContainerCodingKeys(stringValue: "paywall_builder_config", intValue: nil), CodingKeys(stringValue: "assets", intValue: nil), _CodingKey(stringValue: "Index 113", intValue: 113), CodingKeys(stringValue: "value", intValue: nil)], debugDescription: "Encountered Data is not valid Base64.", underlyingError: nil)))"}}]} DEBUG [2024-11-30T18:01:50.997Z]<EMAIL_ADDRESS>"getPaywall": Calling method: OK {"error": [Error: #2006 (decodingFailed): Response decoding failed]}

@vladd-g  do you have any suggestion for this issue?

Hello, the app is working fine for me when i run expo run:ios, but as soon as I want to build it with eas it fails with the same error. I installed all the latest versions as you said:
yarn run v1.22.21
$ /Users/expo/workingdir/build/node_modules/.bin/expo export:embed --eager --platform ios --dev false
Starting Metro Bundler

iOS Bundled 7723ms node_modules/expo-router/entry.js (1185 modules)
Exporting server

λ Bundled 3688ms node_modules/expo-router/build/static/getServerManifest.js (905 modules)

Metro error: Adapty NativeModule is not defined

Error: Adapty NativeModule is not defined
    at new NativeRequestHandler (/Users/expo/workingdir/build/node_modules/react-native-adapty/dist/native-request-handler/native-request-handler.js:14:19)
    at factory (/Users/expo/workingdir/build/node_modules/react-native-adapty/dist/bridge.js:21:19)
    at loadModuleImplementation (/Users/expo/workingdir/build/node_modules/metro-runtime/src/polyfills/require.js:277:5)
    at guardedLoadModule (/Users/expo/workingdir/build/node_modules/metro-runtime/src/polyfills/require.js:184:12)
    at require (/Users/expo/workingdir/build/node_modules/metro-runtime/src/polyfills/require.js:92:7)
    at factory (/Users/expo/workingdir/build/node_modules/react-native-adapty/dist/adapty-handler.js:6:18)
    at loadModuleImplementation (/Users/expo/workingdir/build/node_modules/metro-runtime/src/polyfills/require.js:277:5)
    at guardedLoadModule (/Users/expo/workingdir/build/node_modules/metro-runtime/src/polyfills/require.js:184:12)
    at require (/Users/expo/workingdir/build/node_modules/metro-runtime/src/polyfills/require.js:92:7)
    at /Users/expo/workingdir/build/node_modules/react-native-adapty/dist/index.js:5:26
Adapty NativeModule is not defined
Error: Adapty NativeModule is not defined
Error: Adapty NativeModule is not defined
    at new NativeRequestHandler (/Users/expo/workingdir/build/node_modules/react-native-adapty/dist/native-request-handler/native-request-handler.js:14:19)
    at factory (/Users/expo/workingdir/build/node_modules/react-native-adapty/dist/bridge.js:21:19)
    at loadModuleImplementation (/Users/expo/workingdir/build/node_modules/metro-runtime/src/polyfills/require.js:277:5)
    at guardedLoadModule (/Users/expo/workingdir/build/node_modules/metro-runtime/src/polyfills/require.js:184:12)
    at require (/Users/expo/workingdir/build/node_modules/metro-runtime/src/polyfills/require.js:92:7)
    at factory (/Users/expo/workingdir/build/node_modules/react-native-adapty/dist/adapty-handler.js:6:18)
    at loadModuleImplementation (/Users/expo/workingdir/build/node_modules/metro-runtime/src/polyfills/require.js:277:5)
    at guardedLoadModule (/Users/expo/workingdir/build/node_modules/metro-runtime/src/polyfills/require.js:184:12)
    at require (/Users/expo/workingdir/build/node_modules/metro-runtime/src/polyfills/require.js:92:7)
    at /Users/expo/workingdir/build/node_modules/react-native-adapty/dist/index.js:5:26
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Hello @johannbuscail
Does this algorithm not work for you?

@vladd-g No, only when doing expo run:ios. Otherwise it doesn't work with eas

Yes,
eas-cli/13.4.2
darwin-arm64
node-v22.9.0
expo-v0.21.8

And eas.json:
{
	"cli": {
		"version": ">= 12.5.2",
		"appVersionSource": "remote"
	},
	"build": {
		"development": {
			"developmentClient": true,
			"distribution": "internal",
			"ios": {
				"enterpriseProvisioning": "universal"
			}
		},
		"preview": {
			"distribution": "internal",
			"ios": {
				"enterpriseProvisioning": "universal"
			}
		},
		"production": {
			"autoIncrement": true
		}
	},
	"submit": {
		"production": {}
	}
}

@johannbuscail thank you!
You can remove the "extraMavenRepos" block as it's not needed since v3
Could you please share your metro.config.js as well?

Yes, metro.config.js:
// Learn more https://docs.expo.io/guides/customizing-metro
const { getDefaultConfig } = require('expo/metro-config');
const { withNativeWind } = require('nativewind/metro');

/** @type {import('expo/metro-config').MetroConfig} */
// eslint-disable-next-line no-undef
const config = getDefaultConfig(__dirname);
config.resolver.unstable_enablePackageExports = true;
config.resolver.unstable_conditionNames = ['browser', 'require', 'react-native'];
module.exports = withNativeWind(config, { input: './global.css' });

@johannbuscail thank you! Does it happen with dev EAS builds too?

Yes, absolutely

@johannbuscail could you please let me know if eas build --platform ios --local produces the same error?


Request: remove a call to package registry

Summary of error
2.4.2 features a (undocumented, as far as I can tell) call to the npm registry to check the version of the audit-ci package. This causes opaque errors when using a private npm registry.
Details
I recently ran into a surprising error in two different repos, both of which used audit-ci on version 2.4. These repositories are configured to use my company's private package registry, which requires authentication.
Running audit-ci in one case failed with this error
circleci@85c52d082288:~/project$ yarn test-audit
yarn run v1.21.1
$ node ./node_modules/.bin/audit-ci --config .audit-ci.json --pass-enoaudit
running general audit
{"type":"error","data":"Received invalid response from npm."}
Unexpected end of JSON input
Exiting...
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

And another proceeded just fine.
Adding --verbose to the yarn info command in this library's 2.4.2 version showed me that the last line was a 401 from our private package registry. 2.4.0 and 2.4.1 don't have that call to check the self-version of the library - it was added in this commit
Suggested fix
There's a couple of options

(my preference) Remove the yarn info call and establish this package's version via lookup of its package.json's version. This would mean users don't need to have authentication configured and would avoid a network call that (I think) can be avoided with a local filesystem lookup.
Mark 2.4.2 as deprecated and version bump this library to 2.5, with a note in the changelog that 2.5 requires user authentication. And maybe handle authentication errors?

Thank you for the detailed report! This is a priority fix.
My current thought would be to use:
const { version } = require('../package.json');

Makes sense to me 👍


Seurat import

Is your feature request related to a problem? Please describe.
For the moment, the user has to manually install Seurat in its environments. Or use only conda for checkatlas install.
Describe the solution you'd like
It would be nice to add Seurat with pip (but seems impossible)

For the moment rpy2is used in checkatlas.  Seurat has to be installed by the user.


Add KiCAD files/libraries for boards

@ericjunkins is this closed?

yes, closed with Issue d951e720b7725d463b0c95942ee37105f6517a9e


Upgrades dependencies in the project and replaces @react-native-community/async-storage

@react-native-community/async-storage is no more and the repository has changed names and moved to @react-native-async-storage/async-storage
Tests all pass and yarn e2e succeeds.
fixes #19

Closing in favor of #23, but I'll give credit to you too!


Regexp compilation taking a long time

It was noted that in some workloads regexp compliation is taking up to 60% of osv-scanner's runtime.
Especially this line: https://github.com/google/osv-scanner/blob/26c9df8ad0e891dda69f9a620b638710bcd49da2/pkg/lockfile/parse-yarn-lock.go#L114
A solution would be to store the result of the compilation, rather than compiling every time.
FYI @spencerschrock

Interesting - do you have any more details you can share? I went back and forward over this for a while, including doing benchmarking especially because of this this huge regexp because that is large enough that it adds a few seconds to the test suite.
However at runtime I found there wasn't a significant difference which I assumed was due to Go internally caching some things that it didn't do when the tests were being run in parallel, and moving all those regexp compiles out into variables would mean their compilation cost has to be paid regardless of if the related function is actually used.
I had also trailed a JIT-based approach but again found no significant difference in my benchmarks.

So this came from profiling Scorecard's cron, which repeatedly calls osvscanner.DoScan. Selfishly, a one-time cost is better for my use, which is not a typical use case of osv-scanner.
lockfile.Parse 6.54s ->
(lockfile.parseYarnPackageGroup 1.64s +  lockfile.ParseNpmLock 4.75s)  ->
lockfile.tryExtractCommit 4.86s ->
regexp.MustCompile 4.39s

whereas moving all those regexp compiles out into variables would mean their compilation cost has to be paid regardless of if the related function is actually used

Which is a valid concern for the common case.
Would a package variable but lazy init be better? Perhaps behind a sync.Once.Do ?

I'm assuming that is the total time across all calls rather than the time of a single call.

Would a package variable but lazy init be better? Perhaps behind a sync.Once.Do ?

That would be the preferable option - as I said, when I tried this I didn't see any significant difference in my benchmarking to consider it worth the readability cost, but I didn't know sync.Once.Do was a thing and that might make it a bit nicer.
(it also is entirely possible I mucked up my benchmarking 🤷)


Refactor TransportManager to better indicate direction & have more comments / code reuse

Motivation
While I was looking through code to integrate NetworkInterface into PeerManager, I was getting a little confused on direction (Notification vs Request), so I've added direction to names of functions, and did a little cleanup in the TransportManager to hopefully make it mostly straightforward.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
No functional change, unit tests should cover it.

/land


Revert "Temporary disable failing armv7 tests"

radar rdar://problem/33761334
This reverts commit 78e5e25215ef3a3d8abdac7f0450b6aa51858244

@swift-ci Please smoke test and merge

@aschwaighofer The armv7 tests we just talked about.


The font style of sample code in pinia docs

What problem is this solving
Dear developer of pinia:
Hello.The font of sample code in pinia docs is so curious that I could not focus on code itself.so, would you like to replace it.
Proposed solution
replace the font-style with normal style
Describe alternatives you've considered
No response

Already opened multiple times. Please, search existing issues and pull requests before opening issues, it saves maintainers a lot of time 🙏