[WFCORE-1427] Provide ability to suspend and resume the set of servers managed by a specific host controller

New suspend/resume operations at host level
Enable suspend-timeout attribute for shutdown operation in domain mode
Rename timeout in favor of suspend-timeout for the other lifecycle operations
Basic tests for transformers, timeout rename and new operations using a suspend-timeout value

Jira issue: https://issues.jboss.org/browse/WFCORE-1427
Analysis doc: https://github.com/wildfly/wildfly-proposals/pull/54
Community doc: https://github.com/wildfly/wildfly/pull/11970

Core - Full Integration Build 8319 outcome was UNKNOWN using a merge of 7d85963c008fa2f80347f66c207dc7d7b20f4496
Summary: Canceled (Error while applying patch; cannot find commit d8a2a87dde9a9d7836d46fc26ba5e4d7f378ef02 in the https://github.com/wildfly/wildfly-core.git repository, possible reason: refs/pull/3632/merge branch was updated and the commit selected for the ... Build time: 00:00:19

It seems something was wrong with the PR force update. Let's try to kick off the jobs again doing a force-push again

Core - Full Integration Build 8320 outcome was FAILURE using a merge of 7d85963c008fa2f80347f66c207dc7d7b20f4496
Summary: Tests failed: 1 (1 new), passed: 4784, ignored: 132 Build time: 03:23:27
Failed tests
org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase.testSameTransactionEachCall: javax.ejb.EJBException: EJBCLIENT000082: Cannot outflow the remote transaction "Local transaction (delegate=TransactionImple < ac, BasicAction: 0:ffff7f000101:-62575750:5c5993f2:10 status: ActionStatus.RUNNING >, owner=Local transaction context for provider JBoss JTA transaction provider)" as its timeout elapsed
	at org.jboss.ejb.protocol.remote.EJBClientChannel.processInvocation(EJBClientChannel.java:471)
	at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.lambda$handleDone$0(RemoteEJBReceiver.java:91)
	at org.xnio.FinishedIoFuture.addNotifier(FinishedIoFuture.java:79)
	at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.handleDone(RemoteEJBReceiver.java:76)
	at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.handleDone(RemoteEJBReceiver.java:74)
	at org.xnio.IoFuture$HandlingNotifier.notify(IoFuture.java:208)
	at org.xnio.AbstractIoFuture$NotifierRunnable.run(AbstractIoFuture.java:720)
	at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:949)
	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
	at java.lang.Thread.run(Thread.java:748)
Caused by: javax.transaction.SystemException: EJBCLIENT000082: Cannot outflow the remote transaction "Local transaction (delegate=TransactionImple < ac, BasicAction: 0:ffff7f000101:-62575750:5c5993f2:10 status: ActionStatus.RUNNING >, owner=Local transaction context for provider JBoss JTA transaction provider)" as its timeout elapsed
	at org.jboss.ejb.protocol.remote.EJBClientChannel.writeTransaction(EJBClientChannel.java:581)
	at org.jboss.ejb.protocol.remote.EJBClientChannel.processInvocation(EJBClientChannel.java:367)
	... 12 more
------- Stdout: -------
06:47:20,284 INFO  [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
06:47:20,500 INFO  [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [/usr/java/jdk1.8.0_152/bin/java, -D[Standalone], -Dorg.jboss.ejb.client.wildfly-testsuite-hack=true, -Xmx512m, -XX:MetaspaceSize=128m, -Djboss.dist=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/../../../build/target/wildfly-16.0.0.Beta1-SNAPSHOT, -Dmaven.repo.local=/store/repository, -Djava.net.preferIPv4Stack=false, -Djava.net.preferIPv6Addresses=true, -Djboss.bind.address=::1, -Djboss.bind.address.unsecure=::1, -Djboss.bind.address.private=::1, -Djboss.bind.address.management=::1, -Djboss.default.multicast.address=ff13::1, -server, -Dts.timeout.factor=100, -Dnode0=::1, -Dnode1=::1, -Dmcast=ff13::1, -Dmcast.ttl=0, -Djbossas.ts.submodule.dir=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode, -Djbossas.ts.integ.dir=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/.., -Djbossas.ts.dir=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/../.., -Djbossas.project.dir=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/../../.., -Djava.io.tmpdir=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target, -Djboss.node.name=multinode-client, -ea, -Djboss.home.dir=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target/jbossas-multinode-client, -Dorg.jboss.boot.log.file=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target/jbossas-multinode-client/standalone/log/server.log, -Dlogging.configuration=file:/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target/jbossas-multinode-client/standalone/configuration/logging.properties, -jar, /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target/jbossas-multinode-client/jboss-modules.jar, -mp, /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target/jbossas-multinode-client/modules:/store/work/tc-work/37b47ae8b9c60325/full/build/target/wildfly-16.0.0.Beta1-SNAPSHOT/modules:/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target/modules, org.jboss.as.standalone, -Djboss.home.dir=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target/jbossas-multinode-client, -Djboss.server.base.dir=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target/jbossas-multinode-client/standalone, -Djboss.server.log.dir=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target/jbossas-multinode-client/standalone/log, -Djboss.server.config.dir=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target/jbossas-multinode-client/standalone/configuration, -Dts.wildfly.version=16.0.0.Beta1-SNAPSHOT, -c=standalone.xml]
06:47:20,551 INFO  [org.jboss.remoting] (main) JBoss Remoting version 5.0.8.Final
06:47:20,611 INFO  [org.xnio] (main) XNIO version 3.6.5.Final
06:47:20,626 INFO  [org.xnio.nio] (main) XNIO NIO Implementation Version 3.6.5.Final
06:47:20,769 INFO  [org.wildfly.security] (main) ELY00001: WildFly Elytron version 1.8.0.CR1
 [0m06:47:21,588 INFO  [org.jboss.modules] (main) JBoss Modules version 1.9.0.Final
 [0m [0m06:47:22,605 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.5.Final
 [0m [0m06:47:22,648 INFO  [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
 [0m [0m06:47:23,018 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 16.0.0.Beta1-SNAPSHOT (WildFly Core 8.0.0.Beta4-SNAPSHOT) starting
 [0m [0m06:47:25,694 INFO  [org.wildfly.security] (ServerService Thread Pool -- 24) ELY00001: WildFly Elytron version 1.8.0.CR1
 [0m [0m06:47:27,468 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m06:47:27,607 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 14) WFLYCTL0028: Attribute 'username' in the resource at address '/subsystem=remoting/remote-outbound-connection=remote-ejb-connection' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m06:47:27,607 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 14) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=remoting/remote-outbound-connection=remote-ejb-connection' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m06:47:27,608 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 14) WFLYCTL0028: Attribute 'protocol' in the resource at address '/subsystem=remoting/remote-outbound-connection=remote-ejb-connection' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m06:47:27,635 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 19) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m06:47:27,864 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
 [0m [0m06:47:27,913 INFO  [org.xnio] (MSC service thread 1-5) XNIO version 3.6.5.Final
 [0m [0m06:47:27,949 INFO  [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.6.5.Final
 [0m [0m06:47:28,097 INFO  [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 5.0.8.Final
 [0m [0m06:47:28,237 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 62) WFLYNAM0001: Activating Naming Subsystem
 [0m [0m06:47:28,270 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 49) WFLYCLINF0001: Activating Infinispan subsystem.
 [0m [33m06:47:28,245 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 70) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
 [0m [0m06:47:28,454 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 72) WFLYWS0002: Activating WebServices Extension
 [0m [0m06:47:28,464 INFO  [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 58) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
 [0m [0m06:47:28,534 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 68) WFLYSEC0002: Activating Security Subsystem
 [0m [0m06:47:28,488 INFO  [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 61) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
 [0m [0m06:47:28,458 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 51) WFLYRS0016: RESTEasy version 3.6.2.Final
 [0m [0m06:47:28,644 INFO  [org.jboss.as.naming] (MSC service thread 1-6) WFLYNAM0003: Starting Naming Service
 [0m [0m06:47:28,719 INFO  [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool -- 59) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
 [0m [0m06:47:28,809 INFO  [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=5.0.3.Final
 [0m [0m06:47:28,812 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 56) WFLYJSF0007: Activated the following JSF Implementations: [main]

Core - Full Integration Build 8324 outcome was FAILURE using a merge of 89566371bfbe403d28e8d1a49af2a3787fd68f9f
Summary: Tests failed: 1, passed: 4786, ignored: 132 Build time: 02:49:18
Failed tests
org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase.testSameTransactionEachCall: javax.ejb.EJBException: EJBCLIENT000082: Cannot outflow the remote transaction "Local transaction (delegate=TransactionImple < ac, BasicAction: 0:ffff7f000101:5e0a3714:5c5abc0f:10 status: ActionStatus.RUNNING >, owner=Local transaction context for provider JBoss JTA transaction provider)" as its timeout elapsed
	at org.jboss.ejb.protocol.remote.EJBClientChannel.processInvocation(EJBClientChannel.java:471)
	at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.lambda$handleDone$0(RemoteEJBReceiver.java:91)
	at org.xnio.FinishedIoFuture.addNotifier(FinishedIoFuture.java:79)
	at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.handleDone(RemoteEJBReceiver.java:76)
	at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.handleDone(RemoteEJBReceiver.java:74)
	at org.xnio.IoFuture$HandlingNotifier.notify(IoFuture.java:208)
	at org.xnio.AbstractIoFuture$NotifierRunnable.run(AbstractIoFuture.java:720)
	at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:949)
	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
	at java.lang.Thread.run(Thread.java:748)
Caused by: javax.transaction.SystemException: EJBCLIENT000082: Cannot outflow the remote transaction "Local transaction (delegate=TransactionImple < ac, BasicAction: 0:ffff7f000101:5e0a3714:5c5abc0f:10 status: ActionStatus.RUNNING >, owner=Local transaction context for provider JBoss JTA transaction provider)" as its timeout elapsed
	at org.jboss.ejb.protocol.remote.EJBClientChannel.writeTransaction(EJBClientChannel.java:581)
	at org.jboss.ejb.protocol.remote.EJBClientChannel.processInvocation(EJBClientChannel.java:367)
	... 12 more
------- Stdout: -------
03:50:48,515 INFO  [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
03:50:48,809 INFO  [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [/usr/java/jdk1.8.0_152/bin/java, -D[Standalone], -Dorg.jboss.ejb.client.wildfly-testsuite-hack=true, -Xmx512m, -XX:MetaspaceSize=128m, -Djboss.dist=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/../../../build/target/wildfly-16.0.0.Beta1-SNAPSHOT, -Dmaven.repo.local=/store/repository, -Djava.net.preferIPv4Stack=false, -Djava.net.preferIPv6Addresses=true, -Djboss.bind.address=::1, -Djboss.bind.address.unsecure=::1, -Djboss.bind.address.private=::1, -Djboss.bind.address.management=::1, -Djboss.default.multicast.address=ff13::1, -server, -Dts.timeout.factor=100, -Dnode0=::1, -Dnode1=::1, -Dmcast=ff13::1, -Dmcast.ttl=0, -Djbossas.ts.submodule.dir=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode, -Djbossas.ts.integ.dir=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/.., -Djbossas.ts.dir=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/../.., -Djbossas.project.dir=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/../../.., -Djava.io.tmpdir=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target, -Djboss.node.name=multinode-client, -ea, -Djboss.home.dir=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target/jbossas-multinode-client, -Dorg.jboss.boot.log.file=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target/jbossas-multinode-client/standalone/log/server.log, -Dlogging.configuration=file:/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target/jbossas-multinode-client/standalone/configuration/logging.properties, -jar, /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target/jbossas-multinode-client/jboss-modules.jar, -mp, /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target/jbossas-multinode-client/modules:/store/work/tc-work/37b47ae8b9c60325/full/build/target/wildfly-16.0.0.Beta1-SNAPSHOT/modules:/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target/modules, org.jboss.as.standalone, -Djboss.home.dir=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target/jbossas-multinode-client, -Djboss.server.base.dir=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target/jbossas-multinode-client/standalone, -Djboss.server.log.dir=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target/jbossas-multinode-client/standalone/log, -Djboss.server.config.dir=/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/multinode/target/jbossas-multinode-client/standalone/configuration, -Dts.wildfly.version=16.0.0.Beta1-SNAPSHOT, -c=standalone.xml]
03:50:48,904 INFO  [org.jboss.remoting] (main) JBoss Remoting version 5.0.8.Final
03:50:49,028 INFO  [org.xnio] (main) XNIO version 3.6.5.Final
03:50:49,056 INFO  [org.xnio.nio] (main) XNIO NIO Implementation Version 3.6.5.Final
03:50:49,229 INFO  [org.wildfly.security] (main) ELY00001: WildFly Elytron version 1.8.0.CR1
 [0m03:50:49,948 INFO  [org.jboss.modules] (main) JBoss Modules version 1.9.0.Final
 [0m [0m03:50:50,762 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.5.Final
 [0m [0m03:50:50,787 INFO  [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
 [0m [0m03:50:51,136 INFO  [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 16.0.0.Beta1-SNAPSHOT (WildFly Core 8.0.0.Beta4-SNAPSHOT) starting
 [0m [0m03:50:52,934 INFO  [org.wildfly.security] (ServerService Thread Pool -- 24) ELY00001: WildFly Elytron version 1.8.0.CR1
 [0m [0m03:50:54,049 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m03:50:54,116 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 29) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m03:50:54,150 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 19) WFLYCTL0028: Attribute 'username' in the resource at address '/subsystem=remoting/remote-outbound-connection=remote-ejb-connection' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m03:50:54,151 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 19) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=remoting/remote-outbound-connection=remote-ejb-connection' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m03:50:54,151 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 19) WFLYCTL0028: Attribute 'protocol' in the resource at address '/subsystem=remoting/remote-outbound-connection=remote-ejb-connection' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m03:50:54,238 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
 [0m [0m03:50:54,286 INFO  [org.xnio] (MSC service thread 1-1) XNIO version 3.6.5.Final
 [0m [0m03:50:54,296 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.6.5.Final
 [0m [0m03:50:54,400 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 49) WFLYCLINF0001: Activating Infinispan subsystem.
 [0m [0m03:50:54,436 INFO  [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 58) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
 [0m [0m03:50:54,444 INFO  [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 61) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
 [0m [0m03:50:54,459 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 72) WFLYWS0002: Activating WebServices Extension
 [0m [0m03:50:54,437 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 51) WFLYRS0016: RESTEasy version 3.6.2.Final
 [0m [33m03:50:54,466 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 70) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
 [0m [0m03:50:54,481 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 68) WFLYSEC0002: Activating Security Subsystem
 [0m [0m03:50:54,493 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 62) WFLYNAM0001: Activating Naming Subsystem
 [0m [0m03:50:54,534 INFO  [org.jboss.as.security] (MSC service thread 1-3) WFLYSEC0001: Current PicketBox version=5.0.3.Final
 [0m [0m03:50:54,571 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 50) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
 [0m [0m03:50:54,572 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
 [0m [0m03:50:54,618 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0003: Undertow 2.0.17.Final starting
 [0m [0m03:50:54,693 INFO  [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool -- 59) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem


Make a flowchart

Make a flowchart of the scripts which shows how the interaction is.
@florian-huber nows how the scripts work.

code_flowchart.pdf

thanks!


Add Cyder slide

Please add a slide (or three, but not more) describing :

the current Cyder work you're working on
the conditioning facility
how's it going to work
when will it be ready
what kinds of questions will it answer
where is the repo

closed with #7


Create test.md

@lecoursen
Did this request of yours kicked in automatically?

I created a minimal testing repo on my own:
https://github.com/NikoKrause/notsofunny/pull/2
And I don't see any of those messages like yours in the red boxes.
Do the users mentioned in the CODEWONERS file need to have write access to the repo to make it work? Or are some other requirements needed?
I've read about this cool feature and it does not work, when I try it. And I feel as I don't understand how it works or am doing something wrong. And I don't know why. That's why I created a minimal testing repo and even there it doesn't work.


glide.sh has broken.

Hi, guys~
here is one problem: when I up the mongodb_exporter, it's broken~, it said:
curl: (6) Couldn't resolve host 'glide.sh'
So I tired to curl https://glide.sh/get, ok ~ it still down :(

glide's server being down isn't our problem.. you'll have to try again, sorry about that


feat: Add interactive prompt

This PR adds an interactive prompt that I mentioned wanting in a comment on #4. I also fixed some other issues that I had run into, included extraneous newlines in the ls output, and letting cat accept multiple files.
https://user-images.githubusercontent.com/48231187/159779121-c668e4e2-4e5a-4ee6-be65-a713f1ac1a22.mp4

Is it possible to add tab complete to ls?  I guess you would know about the folders/files in the cwd, but to tab tab you'd need to run a "ls" in the background?

Good idea. I'm trying to think of how to implement this permanently though. Because just saving the current cwd would help when going deeper into the tree.

Where you going to try and implement tab tab in this PR?

I hope to, but I probably won't get to it for a while, sorry.

No worries! 👍

I'm just going to merge this now as it's awesome and I'll try and improve the API to make tab tab easier to do 👍


Error when using --separate-weights

Get the following error when trying to use the separate weights flag on my first build. Running on an M1 MacBook.
Building Docker image from environment in cog.yaml as r8.im/umarramzan/packet-manager...
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x102d6091c]
goroutine 1 [running]:
github.com/replicate/cog/pkg/weights.(*Manifest).Equal(...)
/private/tmp/cog-20230727-4732-1tv3cfa/cog-0.8.3/pkg/weights/manifest.go:66
github.com/replicate/cog/pkg/image.Build(0x1400022e680, {0x1400002c044, 0x35}, {0x16d4c7531, 0x1f}, {0x103281b20, 0x0, 0x0}, 0x0?, 0x1, ...)
/private/tmp/cog-20230727-4732-1tv3cfa/cog-0.8.3/pkg/image/build.go:54 +0x29c
github.com/replicate/cog/pkg/cli.push(0x1400025d200?, {0x140002295a0, 0x1, 0x2?})
/private/tmp/cog-20230727-4732-1tv3cfa/cog-0.8.3/pkg/cli/push.go:49 +0xc0
github.com/spf13/cobra.(*Command).execute(0x1400025d200, {0x14000229580, 0x2, 0x2})
/Users/brew/Library/Caches/Homebrew/go_mod_cache/pkg/mod/github.com/spf13/cobra@v1.7.0/command.go:940 +0x5c8
github.com/spf13/cobra.(*Command).ExecuteC(0x1400025c000)
/Users/brew/Library/Caches/Homebrew/go_mod_cache/pkg/mod/github.com/spf13/cobra@v1.7.0/command.go:1068 +0x35c
github.com/spf13/cobra.(*Command).Execute(0x60?)
/Users/brew/Library/Caches/Homebrew/go_mod_cache/pkg/mod/github.com/spf13/cobra@v1.7.0/command.go:992 +0x1c
main.main()

Hello 👋 - I think this was a hidden bug/issue in v0.8.3 version that it appears you're using, based on the output. I believe this bug was patched in https://github.com/replicate/cog/pull/1239 which was released in version v0.8.5 :

https://github.com/replicate/cog/releases/tag/v0.8.5

Could you try updating your version of cog to at least v0.8.5 and see if the problem remains?
Cheers!

Yes that fixed it. Thank you!

Great to hear! Cheers


Allow repository branch and commit

Small PR (building on i003707) to allow RepositoryBranch and RepositoryCommit to be specified as per https://docs.microsoft.com/en-us/nuget/reference/msbuild-targets
Also, when setting up from a clean Windows box the bin folder was not created in the root of the project. When I manually ran the publish task it was created, so I have included a lone commit add the publish step into the "all" target.

thanks!


Add cluster registration component

Signed-off-by: Chris Ahl<EMAIL_ADDRESS>

Please re-review

/ok-to-test


refactor(NODE-3790): Remove oppressive language from test files

Description
NODE-3790
What is changing?
"ismaster" has been replaced with a constant in all test files.
Exception:

Spec test files will be updated as part of NODE-3791

Is there new documentation needed for these changes?
No
What is the motivation for this change?
Following the guidance documented in tools.ietf.org/id/draft-knodel-terminology-00.html, we will remove all oppressive and unnecessarily gendered language in driver documentation, code, tests, specs, and spec tests.
Double check the following

[x] Ran npm run check:lint script
[x] Self-review completed using the steps outlined here
[x] PR title follows the correct format: <type>(NODE-xxxx)<!>: <description>
[x] Changes are covered by tests
[x] New TODOs have a related JIRA ticket

@durran I made the update you suggested. This PR is ready for another review. The test failure is reported in https://jira.mongodb.org/browse/NODE-3808

Looks like there's a merge conflict that needs resolving. I'm LGTM as well once that's fixed 🙂

Thanks @nbbeeken! I fixed the merge conflicts, and the build is running now.


Since update latest very slow

Today I did an upgrade to the latest version. My previous was from oct/nov last year.
I tried a manual conversion. But it's very slow now.
I am running on windows
Any clue how to debug or find out what is causing this?

Haven't made any changes that should impact performance
Need more information
My guess would be one of the new settings or options you have set in autoProcess.ini is preventing the script for remuxing/copying the video stream and its instead converting it, which slows down the process tremendously, but without some logging and some more details that's just a guess

Thank for the update. Issue closed.


Add proper mlcp SSL support.

mlcp can leverage the Hadoop Connector SSL support through -conf parameter:
https://lists.marklogic.com/search/?q=ssl mlcp#query:ssl mlcp from%3A"Jane Chen"+page:1+mid:ny2iy3t4uz2esxbv+state:results
I recently learned that this was actually used by Aetna, and people at World Bank made a syntax error when trying to copy the model.  So it would be worth testing it.

copy -input_username admin -input_password admin -input_host localhost -input_port 5275  -output_username admin -output_password admin -output_host localhost -output_port 5276 -mode local -input_ssl -output_ssl
export -username admin -password admin -host jchen -port 5275 -output_file_path /tmp/dump -output_type archive -ssl
IMPORT -username admin -password admin -host jchen -port 5275 -input_file_path /space/hadoop-0.20.2/conf -ssl

Nightly regression now run mlcp on SSL days also. will add specific test to regression in 9.0-1 timeframe.


How to integrate with existing expressjs server

Is it possible to integrate with existing nodejs / expressjs server? Do you mind share an example (if there is one). Thanks

You can have your custom routing, optionally rewrite parts of the request (e.g. req.url), and then use emit('request', req, res); on the CORS Anywhere proxy instance (the return value of require('cors-anywhere').createServer) to forward requests.
Search for "createServer" on the issue tracker for previous answers about creating an internal server:
https://github.com/Rob--W/cors-anywhere/issues?utf8=✓&q=is%3Aissue createServer
E.g. https://github.com/Rob--W/cors-anywhere/issues/43#issuecomment-212483004, https://github.com/Rob--W/cors-anywhere/issues/51#issuecomment-255424553,

Thanks Rob, will read through those link :)

Any luck @dcworldwide? I haven't figured out how to make this work with an Express server yet. I've tried doing the below, but get "invalid host: proxy" returned when I do that.
const originBlacklist = parseEnvList(process.env.CORSANYWHERE_BLACKLIST);
const originWhitelist = parseEnvList(process.env.CORSANYWHERE_WHITELIST);
const cors_proxy = require('cors-anywhere').createServer({
  originBlacklist: originBlacklist,
  originWhitelist: originWhitelist,
  requireHeader: ['origin', 'x-requested-with'],
  removeHeaders: [
    'cookie',
    'cookie2',
    'x-heroku-queue-wait-time',
    'x-heroku-queue-depth',
    'x-heroku-dynos-in-use',
    'x-request-start'
  ],
  redirectSameOrigin: true,
  httpProxyOptions: {
    xfwd: false
  }
});

express.get('/proxy', function(req, res) {
  cors_proxy.emit('request', req, res);
});

@DevanB You need to rewrite the URL before passing on the request. Assuming that you want to support http://example.com/proxy/http://cross-domain.example.net/path/to/resource:
express.get('/proxy', function(req, res) {
  req.url = req.url.replace('/proxy/', '/'); // Strip "/proxy" from the front of the URL.
  cors_proxy.emit('request', req, res);
});

This works for me:
        let proxy = corsAnywhere.createServer({
            originWhitelist: [], // Allow all origins
            requireHeaders: [], // Do not require any headers.
            removeHeaders: [] // Do not remove any headers.
        });

        /* Attach our cors proxy to the existing API on the /proxy endpoint. */
        api.get('/proxy/:proxyUrl*', (req, res) => {
            req.url = req.url.replace('/proxy/', '/'); // Strip '/proxy' from the front of the URL, else the proxy won't work.
            proxy.emit('request', req, res);
        });

How to make this work with koa?

@Shion093  I have a similar one

Cannot remove headers after they are sent to the client

Did you figure out that?

Hi, @Jelledb
I'm trying to get this to work on Firebase function as well. Do you mind sharing your settings (firebase.json, functions dir tree and index.js)
Thanks in advance

Could someone share an example with proxying POST requests as well? Many thanks.

Could someone share an example with proxying POST requests as well? Many thanks.


Question about the CT3D-based two-stage DSVT on WOD training yaml file

Thanks for your excellent work, I wanted to reproduce the experimental results of the two-stage DSVT-TS on waymo's 100% training set, but I did not find the relevant two-stage configuration file with CT3D as the model, all of which are the first-stage configuration files with CenterPoint as the model.
Can you upload or tell me where it is?
Thank you very much

Sorry for the late reply. Regarding the training of our two-stage model, we fix the 1st-stage DSVT model and only finetune the 2nd-stage refinement module for 12 epochs with the same training schedule.  The process is a bit complex and detailed, we may not release it.  However, if you require it urgently, please feel free to send me an email.

Thanks for your excellent work, I wanted to reproduce the experimental results of the two-stage DSVT-TS on waymo's 100% training set, but I did not find the relevant two-stage configuration file with CT3D as the model, all of which are the first-stage configuration files with CenterPoint as the model.
Can you upload or tell me where it is?
Thank you very much

Please give me your email. I will give you an unrefined CT3D-based two-stage code in a few days as soon as possible. :)
Haiyang

Hi! Thank you very much for your previous help and patience. I have achieved excellent results in my task with your amazing DSVT model.
I would like to try the two-stage model further. Could you please send me the  CT3D-based code ? Thanks again! Also, I would like to know if the two-stage model would significantly slow down the inference speed.
Here is my email<EMAIL_ADDRESS>

Hi! Thank you very much for your previous help and patience. I have achieved excellent results in my task with your amazing DSVT model. I would like to try the two-stage model further. Could you please send me the CT3D-based code ? Thanks again! Also, I would like to know if the two-stage model would significantly slow down the inference speed. Here is my email<EMAIL_ADDRESS>
Have sent it to email! :)

hello, Could you send me the CT3D-based two-stage code?
my email<EMAIL_ADDRESS>


add .well-known/security.txt

https://securitytxt.org/

We can adapt some things from https://github.com/firoorg/firo/wiki/Firo-Vulnerability-Bounty-Program for this.


AzCopy doesn't work with user delegation key

Which version of the AzCopy was used?
7.3.0
Which platform are you using? (ex: Windows, Mac, Linux)
Windows
What command did you run?
Azcopy /Source:https://source.blob.core.windows.net/caps/ /Dest:https://dest.blob.core.windows.net/zvali5weicr2ks35v7uvnddspykx2wrkwc7mm7k4b3br4wbqupaa /SourceSAS:query /DestSas:delegationkey /pattern:blobname /y /z:journalpath
What problem was encountered?
AzCopy Output : [2024/05/20 05:43:43][ERROR] The syntax of the command is incorrect. Invalid SAS token in parameter "DestSAS".
How can we reproduce the problem in the simplest way?
Can you try using user delegation key with 7.3.0 to see if that even supported with this specific version, I wasn't able to find clear documentation around this.
Have you found a mitigation/solution?
No

Thanks for reaching out to us!
The latest version of AzCopy is V10 and we don't support V7 anymore. Can you please try to upgrade to the latest version and again try the transfer?
You can find the download links on the public Microsoft documentation here Please reopen if the issue persists in v10.


Makes Sound on Enter or Escape

#96 is the same; I just wanted to share the fix for this. Please implement this, it is my biggest gripe with Zazu.
Versions

Zazu: 0.3.2
OS: macOS Sierra 10.12.2

@TGNYC this is an upstream issue with electron (electron/electron#2617) and a duplicate of #96. The code in @afaur's branch is mac specific and will slow down all actions in a noticeable way, so I don't think it's a great fix. There are steps to compile locally though if you want to use their code.

"... branch is mac specific ..."
The fix is only for mac because that is where the problem occurs, but there was a bug making it break functionality for anyone on a non-osx/darwin computer.  I was able to fix this with a code push.
"... and will slow down all actions in a noticeable way"
This is true (I did indicate that in my notes).
I would however note that there are some ways we could improve that:

Setup a background process that keeps track of the current alert volume on a timer.
Get the current alert volume when zazu starts up and use that as the volume we reset to.

This is still far from ideal, but I am unsure of electron resolving this issue.


Integrate OpenAI Function Calling API

Description

Introduced a new FuncConfig in config.py, including an extra field to add function information objects (Dict objects).
Implemented a basic docstring parser in util/functions, which is used to parse docstrings of functions into dictionaries to be passed to LMs.
Added new data classes for packing functions (currently only basic integer algebra and Wiki-based search)
Added new parameters in ChatAgent to control whether function calling is enabled. When function calling is enabled, information about any called functions will be recorded into FuncRecord objects (output in info) and added to messages (in FuncMessage)

examples/function_call/role_playing_with_function.py has a basic demo, which can print out the information of the called functions in each step.
https://drive.google.com/file/d/1U8CoqPBYWrXNwvRT-8QvK8vXtjP5_rnf/view?usp=sharing
Introduced quite many new classes and hope you could provide suggestions for any changes.
Motivation and Context
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.
close #187

[x] I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds core functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (update in the documentation)
[x] Example (update in the folder of example)

Implemented Tasks

[ ] Subtask 1
[ ] Subtask 2
[ ] Subtask 3

Checklist
Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

[x] I have read the CONTRIBUTION guide. (required)
[x] My change requires a change to the documentation.
[x] I have updated the tests accordingly. (required for a bug fix or a new feature)
[ ] I have updated the documentation accordingly.

@MorphlingEd Please address all comments and resolve them with "Resolve conversation" once done

will do this ASAP after carefully reading Tianqi's code and any further discussion with him. He has provided me with some further optimization on the code structure. Sorry for the late action as I am busy with packaging my stuffs in UK today but I will do this within today.

@MorphlingEd Please address all comments and resolve them with "Resolve conversation" once done

will do this ASAP after carefully reading Tianqi's code and any further discussion with him. He has provided me with some further optimization on the code structure. Sorry for the late action as I am busy with packaging my stuffs in UK today but I will do this within today.

No urge here, just a reminder

@Obs01ete I added more tests for testing ChatAgent, search_function etc. Also modified the function names and removed flake8 statement as you said. Now the coverage of test_chat_agent has achieved 99%. But I am not sure whether it is correct to test private method of a class explicitly (e.g. I directly tested update_message but not through step). I guess further I need to wait (and perhaps help) Tianqi for fixing the Python interpreter?

@Obs01ete I added more tests for testing ChatAgent, search_function etc. Also modified the function names and removed flake8 statement as you said. Now the statement coverage rate of class ChatAgent has achieved 99%. But I am not sure whether it is correct to test private method of a class explicitly (e.g. I directly tested update_message but not through step). I guess further I need to wait (and perhaps help) Tianqi for fixing the Python interpreter?

Thanks! You've added an impressive amount of tests. Testing a private method is fine. But you should never access private methods and fields in the core code. Yes, we do not use self._private_method_of_field notation yet, but we may move to it in the future. I am good with the MR in its current state. Please solve the failed tests and we can merge.
What is that issue with the failing test btw?

@Obs01ete I added more tests for testing ChatAgent, search_function etc. Also modified the function names and removed flake8 statement as you said. Now the statement coverage rate of class ChatAgent has achieved 99%. But I am not sure whether it is correct to test private method of a class explicitly (e.g. I directly tested update_message but not through step). I guess further I need to wait (and perhaps help) Tianqi for fixing the Python interpreter?

Thanks! You've added an impressive amount of tests. Testing a private method is fine. But you should never access private methods and fields in the core code. Yes, we do not use self._private_method_of_field notation yet, but we may move to it in the future. I am good with the MR in its current state. Please solve the failed tests and we can merge.
What is that issue with the failing test btw?

I have just checked it by myself and found the problem may be in the server of HuggingFace. When calling the HuggingFace tool (image_generator used in the current test), the server's response is 'Bad Gateway' and no valid information can be returned, resulting in decoding error locally.

@MorphlingEd I suggest you to fix the last issue so we are ready to merge

@lightaime please review this PR. Even though I am good with it, it is huge so please give it a look

Thanks for the great work @MorphlingEd @dandansamax @Obs01ete! I will look into it soon!

@MorphlingEd I suggest you to fix the last issue so we are ready to merge

Have done it and modified the example code to fit the new changes in role_play.

Thanks. Please do not merge it now. I will review it as soon as possible.

Sure.

@lightaime Hi, I have just modified the code and resolved many of the conversations above. But there is still one thing not that clear: about the typing for the functions to be considered by the model's function calling. @dandansamax Tianqi searched for relevant parameter settings and found the argument specification should follow the JSON schema and the type settings are different with Python. For example, I must use string and integer instead of str and int otherwise errors will raise during the schema validation. So if I need to do float addition, I guess I need to define another function called add_float with parameter type being number, which is the general number type in json schema (https://json-schema.org/understanding-json-schema/reference/numeric.html#number). But I think we can add a more diverse set of functions later as this PR is mainly for implementing this function calling mechanism.

@lightaime Hi, I have just modified the code and resolved many of the conversations above. But there is still one thing not that clear: about the typing for the functions to be considered by the model's function calling. @dandansamax Tianqi searched for relevant parameter settings and found the argument specification should follow the JSON schema and the type settings are different with Python. For example, I must use string and integer instead of str and int otherwise errors will raise during the schema validation. So if I need to do float addition, I guess I need to define another function called add_float with parameter type being number, which is the general number type in json schema (https://json-schema.org/understanding-json-schema/reference/numeric.html#number). But I think we can add a more diverse set of functions later as this PR is mainly for implementing this function calling mechanism.

Totally agree with this. Thanks!

Why are gradio app tests failing?
https://github.com/camel-ai/camel/actions/runs/5659852994/job/15334286171?pr=213

Why are gradio app tests failing? https://github.com/camel-ai/camel/actions/runs/5659852994/job/15334286171?pr=213

I am not sure.. The test fails just after Guohao merges master into this branch🤔but the error message seems to indicate problems not related to this branch.

BTW for the Wikipedia search. This is a package for it: https://pypi.org/project/wikipedia. Maybe we can use it in the future.


Error initializing WebDriver: Message: Failed to read marionette port

I installed firefox via apt, below step fixed it.
Step 1: Remove the Firefox Snap by running the following command in a new Terminal window:
sudo snap remove firefox
Step 2: Add the (Ubuntu) Mozilla team PPA to your list of software sources by running the following command in the same Terminal window:
sudo add-apt-repository ppa:mozillateam/ppa
Step 3: Next, alter the Firefox package priority to ensure the PPA/deb/apt version of Firefox is preferred. This can be done using a slither of code from FosTips (copy and paste it whole, not line by line):
echo '
Package: *
Pin: release o=LP-PPA-mozillateam
Pin-Priority: 1001
' | sudo tee /etc/apt/preferences.d/mozilla-firefox

Step 4: Since you’ll (hopefully) want future Firefox upgrades to be installed automatically, Balint Reczey shares a concise command on his blog that ensures it happens:
echo 'Unattended-Upgrade::Allowed-Origins:: "LP-PPA-mozillateam:${distro_codename}";' | sudo tee /etc/apt/apt.conf.d/51unattended-upgrades-firefox
Step 5: Finally, install Firefox via apt by running this command:
sudo apt install firefox
https://stackoverflow.com/questions/72374955/failed-to-read-marionette-port-when-running-selenium-geckodriver-firefox-a

I have fixed the issue, and now I can debug the program to verify if it is working correctly.


Allow ioki-objects to be used in array types

instead of requiring a hash. Similar to type :object.

@rmehner This is the fix for your problem with arrays.


Cannot find Mono SDK, it needs to be installed on the system.

I have Winbows10 Pro 64bit, VS2017, Mono<IP_ADDRESS>(x64)
, AS3.0 and Java Environment installed,
But I have a exception when try to run Embeddinator-4000: Cannot find Mono SDK, it needs to be installed on the system.
I have checked the Source code on ManagedToolchain.FindMonoPath();
But I still cant find out what is the problem.
-I have registry
\HKEY_LOCAL_MACHINE\SOFTWARE\Mono

And Valid value for SdkInstallRoot.
C:\Program Files\Mono\

This path is exist.
Expected Behavior
It should be fine.
Actual Behavior
Exception occur.
Environment
Windows10 Pro 64bit, tried with Administrator and ran on Administrator account.
Installed Embeddinator-4000 0.4.0 via NUGET

Embeddinator-4000.exe "C:\Projs\ProjectVanSales\ProjectVanSales\bin\Release\ProjectVanSales.dll" --gen=Java --platform=Android --outdir="C:\Projs\ProjectVanSales\output" -c

Build Logs
Parsing assemblies...
    Parsed 'ProjectVanSales.dll'
Processing assemblies...
Generating binding code...
    Generated: ProjectVanSales.h
    Generated: ProjectVanSales.c
    Generated: Mono.Android.h
    Generated: Mono.Android.c
    Generated: Java.Interop.h
    Generated: Java.Interop.c
    Generated: mscorlib.h
    Generated: mscorlib.c
    Generated: Xamarin.Android.Support.v7.RecyclerView.h
    Generated: Xamarin.Android.Support.v7.RecyclerView.c
    Generated: Xamarin.Android.Support.Fragment.h
    Generated: Xamarin.Android.Support.Fragment.c
    Generated: Xamarin.Android.Arch.Lifecycle.Common.h
    Generated: Xamarin.Android.Arch.Lifecycle.Common.c
    Generated: Realm.h
    Generated: Realm.c
    Generated: System.h
    Generated: System.c
    Generated: Xamarin.Android.Support.v7.AppCompat.h
    Generated: Xamarin.Android.Support.v7.AppCompat.c
    Generated: Xamarin.Android.Support.Compat.h
    Generated: Xamarin.Android.Support.Compat.c
    Generated: Xamarin.Android.Support.Core.Utils.h
    Generated: Xamarin.Android.Support.Core.Utils.c
    Generated: Xamarin.Android.Support.Core.UI.h
    Generated: Xamarin.Android.Support.Core.UI.c
    Generated: Xamarin.Android.Support.v7.CardView.h
    Generated: Xamarin.Android.Support.v7.CardView.c
    Generated: c-support.c
    Generated: c-support.h
    Generated: embeddinator.h
    Generated: glib.c
    Generated: glib.h
    Generated: mono-support.c
    Generated: mono-support.h
    Generated: mono_embeddinator.c
    Generated: mono_embeddinator.h
Compiling binding code...

Unhandled Exception: System.Exception: Cannot find Mono SDK, it needs to be installed on the system.
   at Embeddinator.Driver.<>c.<.cctor>b__54_0()
   at System.Lazy`1.CreateValue()
   at System.Lazy`1.LazyInitValue()
   at System.Lazy`1.get_Value()
   at Embeddinator.Driver.CompileNDK(IEnumerable`1 files)
   at Embeddinator.Driver.CompileNativeCode(IEnumerable`1 files)
   at Embeddinator.Driver.CompileCode()
   at Embeddinator.Driver.Run()
   at Embeddinator.CLI.Main(String[] args)

I had to install the 32bit Mono -> http://www.mono-project.com/download/stable/ ran into the same issue.

Any update on this

I assume most have moved onto DNNE as a replacement for this project - not to mention some of the new capabilities in .NET 6 + CoreRT's future to create native binaries.


Patch ganesha to skip over files when parsing mount table

fixes https://github.com/kubernetes-incubator/external-storage/issues/432
i'll try to get the patch in upstream ganesha as well, it is very small.

verified locally; merging...


Targetted teaching tips should close when it's target is unloaded

Similar to #1327 open question of if the animation should play or not.

I will fix this :)

Thanks!


Android back button/gesture takes to an empty screen

Description
After scanning a QR Code, it takes to the chat screen. When using the back button/gesture, it takes to an empty screen
Expected Behaviour
After scanning a QR Code, it takes to the chat screen. When using the back button/gesture, it takes to the main/home screen
Note:

Make sure the navigation stack is being manipulated correctly. Sometimes you may need to re-set the stack to a known state.

Checked on Android. works as intended.


Add Sprig functions to go-template

Sprig has a ton of useful functionality appropriate for text
templates and is commonly used with Go. Add it!
https://masterminds.github.io/sprig/

I also wonder if it would be useful to make go-template configurable to use html/template as well?


#1625: Relaxed renderer bail-out when iOS is inactive

On iOS we need to be careful about using the Metal primitives when the app is backgrounded.
We have a test that bails out from rendering when the app is in the background / inactive, but we believe that this is a bit to strict (see #1625 and originally #1257).
This commit fixes this by removing bailing out when the app is inactive - Metal can still render, and the original error message was showing errors when the app was backgrounded.
Verification:
Open animation example and pull down control center - the animation should continue when this PR is applied.
You can also test that the example in #1257 works as expected.
Fixes #1625

yes 🙌🏼


[libavif] Can't use static build after 1.1.1 update

CMakeLists.txt:
cmake_minimum_required(VERSION 3.10)
project(HelloWorld)
find_package(libavif CONFIG REQUIRED)
add_executable(HelloWorld helloworld.cpp)
target_link_libraries(HelloWorld PRIVATE avif)

helloworld.cpp:
#include <avif/avif.h>
#include <iostream>

int main() {
    const char* version = avifVersion();
    std::cout << "libavif version: " << version << std::endl;
    return 0;
}

vcpkg.json:
{
  "builtin-baseline": "e60236ee051183f1122066bee8c54a0b47c43a60",
  "overrides": [
    {
      "name": "libavif",
      "version": "1.1.1"
    }
  ],
  "dependencies": [
    {
      "name": "libavif",
      "features": [
        "dav1d"
      ]
    }
  ]
}

When trying to build in macOS results in the following error: helloworld.cpp:1:10: fatal error: 'avif/avif.h' file not found. I believe the same would happen in Linux, but not Windows (didn't try w/ this minimal project but that's what I was seeing with a much larger project that uses libavif), with the difference presumably being that the library is static in macOS/Linux. If the override in vcpkg.json is set to version 1.0.4#2, it works fine.
Comparing the CMake files in vcpkg_installed/arm64-osx/share/libavif from version 1.0.4#2 to 1.1.1 reveals that the following section disappeared:
set_target_properties(avif PROPERTIES
  INTERFACE_INCLUDE_DIRECTORIES "${_IMPORT_PREFIX}/include"
  INTERFACE_LINK_LIBRARIES "\$<\$<NOT:\$<CONFIG:DEBUG>>:${VCPKG_IMPORT_PREFIX}/lib/libdav1d.a>;\$<\$<CONFIG:DEBUG>:${VCPKG_IMPORT_PREFIX}/debug/lib/libdav1d.a>;\$<LINK_ONLY:yuv>;\$<LINK_ONLY:m>;\$<LINK_ONLY:Threads::Threads>"
)

This is easily veriffied. The last update dropped a cmake config patch, but upsteam still doesn't export include dirs.

The CMake config file is not working with features dav1d or aom.
Please use the pc file instead:
find_package(PkgConfig)
pkg_check_modules(libavif REQUIRED IMPORTED_TARGET libavif)
target_link_libraries(main PRIVATE PkgConfig::libavif)

It can be fixed...

Please test #42250.

Please test #42250.

Confirmed working. Thank you!


feat: added  label overrides on AddressCapture

Part of: #409
Impact: minor
Type: feature
Component
AddressCapture now has label overrides for when i18next will be implemented (see #409)
Breaking changes
No breaking chances, all added fields are optional
Testing

Add a new prop editButtonText to <AddressCapture />
Add the value "test" to editButtonText
Button should display "test" when test is given as a value to the prop. When the prop editButtonText is not added, it should default to the values given in default props.

🚀 Preview deployed
Built with commit f513d8be4b0ce9dbf6f7648c68d736211be5e43a
https://deploy-preview-443--stoic-hodgkin-c0179e.netlify.com

:tada: This PR is included in version 0.68.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Using lineno-start on code-block directive throws error

Using this code block:
..  code-block:: ruby
    :lineno-start: 10

    Some more Ruby code, with line numbering starting at 10.

The following warning is triggered:
/opt/project/vendor/phpdocumentor/guides-restructured-text/src/RestructuredText/Directives/CodeBlockDirective.php:87
Object of class phpDocumentor\Guides\RestructuredText\Parser\DirectiveOption could not be converted to int

@brotkrueml this PR should solve this: https://github.com/phpDocumentor/guides/pull/685


SingleThreadEventExecutor ignores startThread failures

Motivation:
When doStartThread throws an exception, e.g. due to the actual executor being depleted of threads and throwing in its rejected execution handler, the STEE ends up in started state anyway. If we try to execute another task in this executor, it will be queued but the thread won't be started anymore and the task will linger forever.
Modifications:

Ensure we not update the internal state if the startThread() method throws.
Add testcase

Result:
Fixes [#7483]

@rvansa PTAL as well

@rvansa PTAL again

Cherry-picked into 4.1 (5ad35a157cac27004b492703708ecebc4442a55a) ... 4.0 does not have the problem as it not accepts an Executor.


Refactor the setup code more maintainable by reducing the side-effects and globals

Since the idea is to support multiple k8s flavours it would be great if we can structure the code in way that reduces side effects of sourcing a bash library. E.g.
In the current code, we load both kind and microshift libraries when only one is  required. The sideffects of loading kind overflows into microshift. E.g. _output/generated-manifest etc.
The way I see this, we have 3 groups of bash related functions

common bootup script (main functions) that is generic across all clusters
common k8s utilties
cluster specific functions

I have a draft PR that implements the above. Note, its a draft and is created to gather feedback. I am happy to work with minishift maintainers (may worth adding a MAINTAINER file) to refactor that as well.

I suppose there are two discussion in this issue one is code refactor and another is:
do we need support minishift ? as we have microshift and kind already? @rootfs, wdyt?

I am not sure if CNCF should make an repo to all people to create a k8s cluster from any of k8s provider by their preferred ? @rootfs

I think what @sthaha wanted to mention is microshift instead of minishift. @sthaha Correct me if I am wrong

Sorry, my bad, @SamYuan1990 , what I meant was microshift (corrected now).
Thanks @vprashar2929 for pointing out 🙇

@SamYuan1990 I am going to close this as completely by #31 .


Update README

Updated the README to stop suggesting to work and push
on master. All new updates to the codebase should be i
proposed by branches.

Looks good.


Only 3D mag fusion is broken

If EKF2_MAG_TYPE = 2 (only 3D mag fusion) the estimator will continuously trigger yaw resets
https://github.com/PX4/ecl/blob/1378ec179717448404c74819871d149217350b19/EKF/control.cpp#L1542-L1545
since mag_align_complete is set to false here
https://github.com/PX4/ecl/blob/1378ec179717448404c74819871d149217350b19/EKF/control.cpp#L1378-L1378
To reproduce run
make px4_sitl gazebo, set EKF2_MAG_TYPE = 2 and restart simulation

Any idea when it was last functional?

No, I never used it before. Just wanted to test something in SITL and noticed that the vehicle never got GPS lock


@n on the

Hello @ajaniak ! I see that the attributes @n on the <p>s in my file DHARMA_CritEdSiksaKandangKaresian are now preventing the file to be validated. If I should no longer use @n, could you make the necessary global changes in my file? Thanks!

Dear @aditiagunawan,
Encoding @n on <p> where never allowed, see p. 32 of the guide.
Manuscripts don't have any schema yet and I have only starting working on them.
It is done


Write text for the Micro-Acquisition home page

Could use the following text as a starting point (all text below has already been translated)
Government of Canada Developers Exchange
About GC DevEx
The Government of Canada Developers Exchange (GC DevEx) is a micro-procurement platform where teams within the Government of Canada can post opportunities to developers who are eligible to work in Canada . The dollar value of these contracts can not exceed $10,000 CAD, including GST. This is one of a number of initiatives underway to make it easier for government and developers to work together.

Participating government departments
GC DevEx beta was started by Privy Council Office (PCO), and Treasury Board of Canada Secretariat (TBS), in collaboration with Public Services and Procurement Canada (PSPC).These departments are responsible for managing the beta site and evaluating the initiative.
Other federal departments who wish to use the GC DevEx Beta by contacting<EMAIL_ADDRESS>After this initiative has been evaluated, it may be expanded

Re-use this code
Other governments can re-use the code and concept for this initiative, which was developed by the Government of British Columbia. The code for the British Columbia Developers' Exchange was adapted to meet Treasury Board of Canada Secretariat (TBS) Web Standards and the Official Languages Act.
The modified code for GC DevEx Beta can also be re-used. With the exception of the federal identifier (AKA Canada logo), all parts of this website is licensed for re-use through the Apache License.
Whether you are part of a provincial, municipal, or national government elsewhere, you can fork the code on GitHub and set-up your own micro-procurement platform to work with developers in your community.
About page: https://beta.gcdevexchange.org/about
Why was GC DevEx Beta created?
GC DevEx Beta enables Government of Canada departments  to compensate developers to work with them on open source projects. mphasis on open source technologies encourages copying (forking) to enhance collaboration and reduce overall costs by encouraging re-use and adoption of existing tools where they exist.
The need for a micro-procurement platform was first identified by public engagement practitioners. Although many digital engagement tools exist, they do not necessarily comply with Government of Canada policies. The question this pilot seeks to answer is : “can we create a library of compliant, re-usable, cost-effective tools that enable departments and citizens to engage frequently and on complex issues?” The scope has since increased to serve the needs of other teams using open source technologies.
By focusing on small scale opportunities, we hope to increase the amount of government contracts to small and medium sized enterprises, civic technology community groups and entrepreneurs, in a way that adds value and encourages collaborative innovation within Canada.
This initiative fulfills a commitment under Canada's participation in the Open Government Partnership (OGP).

Also review and consider the text on the BC Digital Marketplace https://digital.gov.bc.ca/marketplace

PR opened on the devex-pages repo with the draft text.

Realized this should be in reviewing/pending not closed as I'd love to get comments on the content.  PR here: https://github.com/canada-ca/devex-pages/pulls


ICU detect CSV data with the incorrect encoding

Related https://github.com/CartoDB/support/issues/1808#issuecomment-432286551
https://github.com/brianmario/charlock_holmes/issues/38

Yes I'm going to do it after the review
El mar., 23 oct. 2018 20:32, Javier Torres<EMAIL_ADDRESS>escribió:

@javitonino commented on this pull request.
A bit hacky but 👍
But please, obey Hound plus update NEWS
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/CartoDB/cartodb/pull/14358#pullrequestreview-167572123,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtPeFv7-EXJpopD-nap_8eUOi5oRbXQks5un2CqgaJpZM4X15Et
.

Acceptance 🍏


Support for attributes values containing an equal sign in them

resolve #10

Awesome job @Rakoth.  Thanks for your help.


Target class [VoyagerController] does not exist after initial install.

Version information

Laravel: v8.12.3
Voyager: v1.4
PHP: v7.3.21
Database: MySQL 5.7.31

Description
I completed the install of Voyager on an existing Laravel application. The install all went perfectly fine up until opening the browser:
composer require tcg/voyager

Using version ^1.4 for tcg/voyager
./composer.json has been updated
Running composer update tcg/voyager
Loading composer repositories with package information
Updating dependencies
Lock file operations: 20 installs, 0 updates, 0 removals
  - Locking arrilot/laravel-widgets (3.13.1)
  - Locking composer/ca-bundle (1.2.8)
  - Locking composer/composer (2.0.7)
  - Locking composer/semver (3.2.4)
  - Locking composer/spdx-licenses (1.5.4)
  - Locking composer/xdebug-handler (1.4.5)
  - Locking doctrine/cache (1.10.2)
  - Locking doctrine/dbal (2.12.1)
  - Locking doctrine/event-manager (1.1.1)
  - Locking intervention/image (2.5.1)
  - Locking justinrainbow/json-schema (5.2.10)
  - Locking larapack/doctrine-support (v0.1.9)
  - Locking larapack/hooks (v1.0.12)
  - Locking larapack/voyager-hooks (v1.2.3)
  - Locking laravel/ui (v3.1.0)
  - Locking react/promise (v2.8.0)
  - Locking seld/jsonlint (1.8.3)
  - Locking seld/phar-utils (1.1.1)
  - Locking symfony/filesystem (v5.2.0)
  - Locking tcg/voyager (1.x-dev 5753a2c)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 20 installs, 0 updates, 0 removals
  - Downloading symfony/filesystem (v5.2.0)
  - Syncing tcg/voyager (1.x-dev 5753a2c) into cache
  - Installing composer/ca-bundle (1.2.8): Extracting archive
  - Installing composer/semver (3.2.4): Extracting archive
  - Installing composer/spdx-licenses (1.5.4): Extracting archive
  - Installing composer/xdebug-handler (1.4.5): Extracting archive
  - Installing doctrine/cache (1.10.2): Extracting archive
  - Installing doctrine/event-manager (1.1.1): Extracting archive
  - Installing justinrainbow/json-schema (5.2.10): Extracting archive
  - Installing symfony/filesystem (v5.2.0): Extracting archive
  - Installing seld/phar-utils (1.1.1): Extracting archive
  - Installing seld/jsonlint (1.8.3): Extracting archive
  - Installing react/promise (v2.8.0): Extracting archive
  - Installing composer/composer (2.0.7): Extracting archive
  - Installing larapack/hooks (v1.0.12): Extracting archive
  - Installing laravel/ui (v3.1.0): Extracting archive
  - Installing larapack/voyager-hooks (v1.2.3): Extracting archive
  - Installing doctrine/dbal (2.12.1): Extracting archive
  - Installing larapack/doctrine-support (v0.1.9): Extracting archive
  - Installing intervention/image (2.5.1): Extracting archive
  - Installing arrilot/laravel-widgets (3.13.1): Extracting archive
  - Installing tcg/voyager (1.x-dev 5753a2c): Cloning 5753a2c39f from cache
4 package suggestions were added by new dependencies, use `composer suggest` to see details.

Use the `composer fund` command to find out more!

php artisan voyager:install
Publishing the Voyager assets, database, and config files
Copied Directory [/vendor/tcg/voyager/publishable/database/seeds] To [/database/seeds]
Publishing complete.
Migrating the database tables into your application
Migrating: 2016_01_01_000000_add_voyager_user_fields
Migrated:  2016_01_01_000000_add_voyager_user_fields (40.65ms)
Migrating: 2016_01_01_000000_create_data_types_table
Migrated:  2016_01_01_000000_create_data_types_table (119.46ms)
Migrating: 2016_05_19_173453_create_menu_table
Migrated:  2016_05_19_173453_create_menu_table (89.06ms)
Migrating: 2016_10_21_190000_create_roles_table
Migrated:  2016_10_21_190000_create_roles_table (41.46ms)
Migrating: 2016_10_21_190000_create_settings_table
Migrated:  2016_10_21_190000_create_settings_table (31.06ms)
Migrating: 2016_11_30_135954_create_permission_table
Migrated:  2016_11_30_135954_create_permission_table (34.04ms)
Migrating: 2016_11_30_141208_create_permission_role_table
Migrated:  2016_11_30_141208_create_permission_role_table (133.90ms)
Migrating: 2016_12_26_201236_data_types__add__server_side
Migrated:  2016_12_26_201236_data_types__add__server_side (27.27ms)
Migrating: 2017_01_13_000000_add_route_to_menu_items_table
Migrated:  2017_01_13_000000_add_route_to_menu_items_table (22.29ms)
Migrating: 2017_01_14_005015_create_translations_table
Migrated:  2017_01_14_005015_create_translations_table (36.49ms)
Migrating: 2017_01_15_000000_make_table_name_nullable_in_permissions_table
Migrated:  2017_01_15_000000_make_table_name_nullable_in_permissions_table (41.40ms)
Migrating: 2017_03_06_000000_add_controller_to_data_types_table
Migrated:  2017_03_06_000000_add_controller_to_data_types_table (22.51ms)
Migrating: 2017_04_21_000000_add_order_to_data_rows_table
Migrated:  2017_04_21_000000_add_order_to_data_rows_table (24.89ms)
Migrating: 2017_07_05_210000_add_policyname_to_data_types_table
Migrated:  2017_07_05_210000_add_policyname_to_data_types_table (21.59ms)
Migrating: 2017_08_05_000000_add_group_to_settings_table
Migrated:  2017_08_05_000000_add_group_to_settings_table (24.08ms)
Migrating: 2017_11_26_013050_add_user_role_relationship
Migrated:  2017_11_26_013050_add_user_role_relationship (57.94ms)
Migrating: 2017_11_26_015000_create_user_roles_table
Migrated:  2017_11_26_015000_create_user_roles_table (145.31ms)
Migrating: 2018_03_11_000000_add_user_settings
Migrated:  2018_03_11_000000_add_user_settings (22.58ms)
Migrating: 2018_03_14_000000_add_details_to_data_types_table
Migrated:  2018_03_14_000000_add_details_to_data_types_table (25.35ms)
Migrating: 2018_03_16_000000_make_settings_value_nullable
Migrated:  2018_03_16_000000_make_settings_value_nullable (30.01ms)
Attempting to set Voyager User model as parent to App\User
Dumping the autoloaded files and reloading all new files
Adding Voyager routes to routes/web.php
Seeding data into the database
Copied File [/vendor/tcg/voyager/publishable/config/voyager.php] To [/config/voyager.php]
Copied Directory [/vendor/tcg/voyager/publishable/dummy_content/users] To [/storage/app/public/users]
Publishing complete.
Setting up the hooks
Copied File [/vendor/larapack/hooks/publishable/config/hooks.php] To [/config/hooks.php]
Publishing complete.
Hooks are now ready to use! Go ahead and try to "php artisan hook:install test-hook"
Adding the storage symlink to your public folder
The [/Users/cris/Sites/integrations/public/storage] link has been connected to [/Users/cris/Sites/integrations/storage/app/public].
The links have been created.
Successfully installed Voyager! Enjoy

After that, I created an admin and went to log in:
http://integrations.test/admin
This presented me with an error:
Illuminate\Contracts\Container\BindingResolutionException
Target class [VoyagerController] does not exist.

Screenshots

Any thoughts on why I am seeing this error? I have double checked all settings and they seem spot on. Database seeds have run, all tables created, etc...
Thanks

I have narrowed this down to what I think are the routing changes in Laravel 8. If I move the routes to the application level web.php fie, and change the routes to Laravel 8 formats, they work (mostly). A few other issues came up, and I am just thinking this isn't stable with Laravel 8 yet. Could I get confirmation on this?

@webmasterjunkie I tried to reproduce this error but The installation goes working fine for me on
Laravel: v8.17.2
Voyager : v1.4
PHP : v7.3.12

Voyager already uses full namespaces in its routes so there shouldn't be any problem and I cannot reproduce it.
@webmasterjunkie
Please check your voyager config file in case you set an empty values for voyager.controllers.namespace

Voyager already uses full namespaces in its routes so there shouldn't be any problem and I cannot reproduce it.
@webmasterjunkie
Please check your voyager config file in case you set an empty values for voyager.controllers.namespace

I'm having the same issue... I've installed voyager on top of my existing Laravel 8 application, I installed in on my local machine and everything went fine, I was able to access the admin and no other changes to my app.
So I created a branch then added the changes to the branch, went to my public site switched to the branch and attempted to run the composer require and artisan install commands, both completed successfully, but when I try to navigate to admin on the public site I get the error...
maybe because I created a branch with changes that the voyager installer creates? and then re running the install on the public site caused the issue?
I will try with a fresh branch on my public site and see if I can reproduce

I'm having the same issue... I've installed voyager on top of my existing Laravel 8 application, I installed in on my local machine and everything went fine, I was able to access the admin and no other changes to my app.
So I created a branch then added the changes to the branch, went to my public site switched to the branch and attempted to run the composer require and artisan install commands, both completed successfully, but when I try to navigate to admin on the public site I get the error...
maybe because I created a branch with changes that the voyager installer creates? and then re running the install on the public site caused the issue?
I will try with a fresh branch on my public site and see if I can reproduce

just fixed my issue by running
php artisan config:clear
I'm guessing I had stale config for some reason? ...
also the first time it worked I just served on my local machine with  - php artisan serve
on the public site (docker droplet) its being served by nginx via docker, so maybe the config doesn't get refreshed unless its called specifically?

just fixed my issue by running
php artisan config:clear
I'm guessing I had stale config for some reason? ...
also the first time it worked I just served on my local machine with  - php artisan serve
on the public site (docker droplet) its being served by nginx via docker, so maybe the config doesn't get refreshed unless its called specifically?

@joncrissey if config is cached no change will be seen until cache is refreshed manually.
I'm closing this issue since op is not providing feedback and cannot reproduce the error.

@joncrissey if config is cached no change will be seen until cache is refreshed manually.
I'm closing this issue since op is not providing feedback and cannot reproduce the error.


Code not compatible with babel

FYI, latest babel wouldn't compile this code:
https://github.com/d3/d3-array/blob/a947cbaaef2fb1ad5e129ef6d28c6232c2b784c9/src/cumsum.js#L1-L6
with this error:
ERROR in ./node_modules/d3-array/src/cumsum.js
Module build failed (from ./node_modules/babel-loader/lib/index.js):
SyntaxError: /xxx/node_modules/d3-array/src/cumsum.js: Only '=' operator can be used for specifying default value. (4:15)

  2 |   var sum = 0, index = 0;
  3 |   return Float64Array.from(values, valueof === undefined
> 4 |     ? v => (sum += +v || 0)
    |                ^
  5 |     : v => (sum += +valueof(v, index++, values) || 0));
  6 | }

It's probably babel's issue, but I thought it was worth reporting it here, as may be it is an issue with d3-array.

My bad! Apparently a duplicate of #147. Also see https://github.com/babel/babel/issues/11038

Just ran into the same error. #147 has been closed, but without any resolution. Upgrading Babel or downgrading d3-array is not an option for me, as I am using Meteor (which fixed Babel to a certain version) and react-globe that relies on<EMAIL_ADDRESS>and I wouldn't want to break it.
I would appreciate if the code could be rewritten without the assignment in the ternary operator.


Rideshare Skill Stub

Purpose
Adding a stub Rideshare skill and test project to start development of the experimental rideshare skill.
Changes
Two new projects, RideshareSkill and RideshareSkill.Tests, have been added. These are as-is fresh from installing via the Skill Template VSIX.
Tests
Yes - covered by stub tests installed from the VSIX.
Feature Plan
N/A
Checklist
General

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated the appropriate tests
[ ] I have updated related documentation

same as the other PR. if this is not against master, i'm not sure we should have people look at it because when you have to merge it to master people have to look at it again and it's very easy to miss things, if that makes sense.

same as the other PR. if this is not against master, i'm not sure we should have people look at it because when you have to merge it to master people have to look at it again and it's very easy to miss things, if that makes sense.

I'm going to challenge that. If the final merge to master ends up being small, then I could buy it - but I've seen too many cases where people end up building giant branches to be merged back to master. I don't think it's fair on reviewers to have to look at ginormous reviews, and can also lead to misses because less attention was paid in reviewing the changes, particularly if there is pressure to get checked in. I am much more of a fan of little and often.
Let me know if you disagree.

The PR template has a section called Feature Plan that has gone largely unused but I think that there are valid cases for it.

Child PRs mention that they are part of a larger feature
Parent PR references the Child PRs to show that code reviews for the individual components have already occurred
Making changes in a Sample & the SDK that require new packages published to pick up on said changes... (just another example)

I'm confused as to whether the peinnes/rideshare_master branch is going to be merged into next or master?

same as the other PR. if this is not against master, i'm not sure we should have people look at it because when you have to merge it to master people have to look at it again and it's very easy to miss things, if that makes sense.

I'm going to challenge that. If the final merge to master ends up being small, then I could buy it - but I've seen too many cases where people end up building giant branches to be merged back to master. I don't think it's fair on reviewers to have to look at ginormous reviews, and can also lead to misses because less attention was paid in reviewing the changes, particularly if there is pressure to get checked in. I am much more of a fan of little and often.
Let me know if you disagree.

Thanks Peter for the comment.
I disagree. The most important thing for PRs (I believe) is that every single PR needs to be guarded by certain checks (e.g. azure devops build). If we don't have the checks, there's no guarantee the PRs are good even though they are approved. (you can argue that the checks won't guarantee things either, but it's the next best thing and we're always improving it with test coverage etc). if we create PRs against a branch that doesn't have checks (private branches), these things will/might happen:

there's no checks running for them so there's no guarantee the changes are good
it's easy to slip commits through by simply 'git push'. i know people normally wouldn't do it, but if it's a public repo, we can't be sure
when you finally merge the big change into master/next branch that has check running, people wouldn't actually look at that PR again since they'll assume they've looked at all that's included, but there could easily be commits by #2

Even though the alternative is bigger PRs, i think we can all agree that the three things above are worse problems.
And IMHO bigger PRs are not always a problem, nor are they a problem we can't solve. i think we should always be able to divide big PRs into smaller atomic ones that make sense and work themselves (e.g. in phases). in most cases a better design needs to be done if that's not possible. and if not the PR owners can always add initial comments here and there in the PR to point people to different places in the PR to help them to look at a big one.
let me know what you think and feel free to sync up offline more about this.


[FLINK-17707][k8s] Support configuring replicas of JobManager deployment when HA enabled

What is the purpose of the change
At the moment, in the native K8s setups, we hard code the replica of Deployment to 1. However, when users enable the ZooKeeper HighAvailabilityServices or Kubernetes HA service, they would like to configure the replica of JobManager deployment also for faster recovery.
In #15248, we have added the documentation for how to start standby JobManagers for standalone Flink cluster on K8s. This PR tries to make replica of JobManager deployment configurable for native mode.
Brief change log

Support configuring replicas of JobManager deployment when HA enabled

Verifying this change

Add dedicated tests for the changes

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

cc @tillrohrmann  could you please have a look at your convenience?

Rebase latest master.

cc @xintongsong Could you please have a look?

Thanks for preparing the PR, @wangyang0918.
I'm afraid we are not ready for this feature ATM. As FLINK-21667 reveals, currently a standby RM can perform modifying actions on native Kubernetes deployment. I have not started working on FLINK-21667, because I'd rather not to make significant changes to the RM lifecycle management right before the 1.13 feature freeze.
I'd suggest to postpone this feature as well, marking it as blocked by FLINK-21667.

@xintongsong Thanks for your comments. Even though the standby only stop the terminated pod currently, but it is not a by-design behavior. The standby ResourceManagers should not perform the modifying actions. I agree with you that we could defer this PR after FLINK-21667.

Since the FLINK-21667 has been merged, I think this PR is ready for review. cc @xintongsong

Since the FLINK-21667 has been merged, I think this PR is ready for review. cc @xintongsong

@xintongsong Yes, this feature has been verified in a real K8s cluster. Actually, I think the Flink config option description is enough. But I will add a brief introduction in the native_kubernetes.md.

@xintongsong Thanks for your review. PR updated.


fix(avm): one too many range check rows

Please read contributing guidelines and remove this line.

#7499  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @IlyasRidhuan and the rest of your teammates on  Graphite


Add ADOT helm chart json schema

Issue #, if available: N/A
Description of changes: Add ADOT helm chart json schema
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm


Events not working

Hey there,
trying to implement custom color scheme for the datepicker, so I have to loop through all visible and enabled dates in order to assign css classes.
Tried to use the events opening and opened, but they don't seem to work.
I tried to do it like this:
$('#date').on('ab.datepicker.opening', function (datepicker) {
    console.log(datepicker);
});

Is this wrong? I don't get any errors it just does not execute.
Thanks in advance.
Best regards
Nick

Hi,
The ab.datepicker.opening and ab.datepicker.opened events are triggered on the calendar portion of the date picker
Best regards

Try this:
$('.datepicker-calendar').on('ab.datepicker.opening', function(e, datepicker) {
    if (datepicker == 'date') {
        console.log(datepicker);
    }
});

@eureka2 above solution is not working.
Tried both ways. i am using this as function.
datePicker = function () {
$(".datepicker").datepicker({
    markup: 'bootstrap4',
    inputFormat: ["dd/MM/yyyy"],
    outputFormat: 'dd/MM/yyyy',
    opening: function () {
        alert()
    }
});

$('.datepicker').on('ab.datepicker.opening', function () {
    alert('hi')
    var val = $(this).val();
    $(this).attr('title', val);
});

}


committing Whoa file

can't find the Whoa file since there' nothing left

The classic rm -rf command - nice one


Create search-results.js on VS CODE

WE NEED a search-results.js file created on VS CODE to house the JavaScript for the search results page of the project

Awaiting approval.


Adding new endpoints

What is the best way to add new endpoints to the client that the app/hubstorage apis already support?
For example: https://app.scrapinghub.com/api/v2/projects/206606/scripts

Should I add new modules to the client package or extend the methods in the legacy module?
Maybe I should submit a PR for refactoring the legacy module into the client package?

Thanks for raising this. Talking specifically about adding scripts endpoint, I don't think that it's worth implementing for now, because there's an intention to completely get rid of script concept, and stop handle it in a special way. So adding a new endpoint to drop it in a few months or so doesn't look like a good idea.
Talking about extending the client in a general case, the topic itself is a bit tricky. First of all, hubstorage client and legacy module are frozen, we don't want to evolve it or change, because there're still a lot of clients relying on it and even a minor change can lead to disaster.
A new client located in scrapinghub.client assembles logic from the both legacy clients and unifies it, so if we want to extend the library e.g. support new endpoints - for now it should be done on the scrapinghub.client level only.
Given that the new client is written on top of frozen legacy clients, it's not an easy task to extend it in general case, but something to keep in mind is that we're going to rework Scrapinghub API in the near future (we have it in our roadmap), to make it more sound and easier to use, and when it's done we'll start discussion about reworking the client completely.
I'm going to close the issue for now, but let me know if you have any thoughts/concerns/proposals  and we'll continue the discussion (here or in a private chat).


LUCENE-10592 Better estimate memory for HNSW graph

Better estimate memory used for OnHeapHnswGraph,
as well as add tests.
Also don't over-allocate arrays in NeighborArray.
Relates to #992

I ran a test using KnnGraphTester, setting IndexWriterConfig max buffer size to 250MB. I indexed 1M 256-dim docs (1K each, so 1GB in total) Results with 9.3:
4 segments
recall  latency nDoc    fanout  maxConn beamWidth       visited index ms
0.978    2.36   1000000 50      32      64      3977    476926

With 9.x, 7 segments got created
recall  latency nDoc    fanout  maxConn beamWidth       visited index ms
0.983    4.05   1000000 50      32      64      60      522040  1.00    post-filter

I wonder if we should consider rolling back the "build graph during indexing" change? It seems to make indexing take > 10% longer and of course requires more RAM, which will tend to make more and smaller segments; not a desirable outcome.

@msokolov Thanks for your feedback.
I have done a similar analysis comparing 9.3 branch with this change on glove-100-angular 1 million documents,  M:16 efConstruction:100
Results with 9.3:
IndexingChaing::ramBytesUsed() reports  497089200 bytes or 497MB
Results with current change
IndexingChaing::ramBytesUsed() reports  memory vectors: 497075904; memory graph: 379073392; so total: 876 Mb
So, you are right, much more memory used during indexing. We need at least 16 * M * number_nodes:

2 *M neighbours for each node on the lowest level * 8 bytes ( 4 bytes for neighbour node number + 4 bytes for neighbour score)
so indeed, if indexing memory buffer is set up less than that, we would end up with much more segments which is not desirable.

I wonder if we should consider rolling back the "build graph during indexing" change? It seems to make indexing take > 10% longer and of course requires more RAM, which will tend to make more and smaller segments; not a desirable outcome.

Thanks for suggestion.  I will discuss this with our team on Tuesday, and will get back to you.
One thing I wonder we did not observe longer total indexing time (combined indexing + refresh time). Is combined total indexing time + refresh time became larger for you?

One thing I wonder we did not observe longer total indexing time (combined indexing + refresh time). Did combined total indexing time + refresh time became larger for you?

The KnnGraphTester indexing time numbers count open a new IndexWriter, add all the documents, close the IndexWriter; there's no refresh.

I wonder if we should consider rolling back the "build graph during indexing" change? It seems to make indexing take > 10% longer and of course requires more RAM, which will tend to make more and smaller segments; not a desirable outcome.

Although ... the RAM needed for the graph was always required, even when building the graph during flush, it just wasn't accounted for I think. I suppose a possible way to improve the buffering situation would be to buffer the vectors in RAM and then on merge, write them out, freeing the on-heap copy, and while building the graph, access the vectors from disk

Woops I just reread @msokolov 's comment and it was not actually about buffering on disk, more about moving them to disk before starting to build the graph. Sorry for the confusion. I thought it was about writing them to disk at index time. But now I wonder: could we buffer vectors on disk with the approach of building the graph during indexing?

@msokolov

Although ... the RAM needed for the graph was always required, even when building the graph during flush, it just wasn't accounted for I think. I suppose a possible way to improve the buffering situation would be to buffer the vectors in RAM and then on merge, write them out, freeing the on-heap copy, and while building the graph, access the vectors from disk

Indeed, that how we do that in Lucene 9.3, using off-heap vector values to build graph
The problem with this is that building graph on flush would take a lot of time, which makes searches that needed updated changes unpredictably long.

@jpountz

could we buffer vectors on disk with the approach of building the graph during indexing?

We explored this, but could not find any way to do that.  To build a graph, we need to access to all vector values indexed so far.  If vectors are buffered in memory, this works.  But if we are to buffer vectors on disk, we can’t at the same time write vectors to this file and read vectors from it during the graph construction, as reading from unclosed index outputs is not possible.

@msokolov  Thanks for your feedback, and good ideas, we can experiment with them.
We've discussed within our team (including @jpountz  and @jtibshirani) and decided that we still would like to proceed with this change (building graph on indexing) for 9.4 release, as  we see benefits outweigh extra memory used.  For example, we see significant improvement in refresh time in our Elasticsearch benchmarks, which makes searches on updated data much faster and predictable:

For follow-ups (beyond 9.4 release), we can experiment with :

pre-flush flush (flushing a portion of vectors)
using data with less precision than integers and floats for storing neighbours' info in graph
some other ideas?


Basic PPR

This PR add basic support for PPR.
This is the PPR built into next standalone, this mean that nothing can be served from the CDN (except the prefetched rsc).
The html are served from the server every time

Yeah we had already everything in place, so it was very easy (I thought it would be a little harder though, but not by much)
The thing is, it's probably not worth it in a lot of cases. The S3 latency could make it totally worthless depending on what's prerendered. And you could end up paying a lot more, 1 S3 GET for every request instead of a few ms of a running lambda

Hmm shouldn't those static assets be generated w/ cache-control headers, something like s-maxage=1yearish, immutable. I would assume those static assets hit S3 only once and then stored at the CDN.

I must not fully understand the PPR architecture. I assumed the static shell parts are determined at build time. Then when the client makes a request, it streams back the shell that points to the static asset, then continues w/ the suspense boundary stuff.
I haven't dived into the source code to figure this out yet though.

That's basically that.
The only thing is that it does that in a single stream, and they don't provide us with only the resume endpoint (unless using minimal mode).
And to add to that, the first html shell is not always fully generated at build time, sometimes it is generated at runtime from some RSC.


Reviewing the definition of a Challenge Organization

Background
There are currently two types of organizations modeled in the registry:

Challenge Organization (e.g. DREAM, MICCAI): an organization that owns one or more challenges.
Challenge Sponsor (e.g. IBM, Kaiser Permanente): an organization that contributed to the organization of a challenge.

In this design, there is a strong link between a challenge and the organization that owns it. This relationship was visible in the url of a challenge (e.g. /dream/my-challenge) and used to identify the challenges that an organization can manage. In this design, a challenge is managed by a single organization.
Problems, Opportunity and Proposal
There are a few problems and opportunities of improvements with this design:

I propose to decouple the strong link between one "challenge organization" and a challenge. This leads to a few benefits:

Simplify the implementation of the registry for the private preview as we can virtually ignore the authorization layer.
The URL of a challenge will be more robust and shorter as described in the document Challenge Registry App Routes.

Two concepts of organizations - the challenge organizations and organizations that are sponsors - may be confusing.

The proposal is to place all organizations on the same foot and model them with an Organization schema.
This simplifies the implementation of the Challenge schema. Right now we have a property called Challenge.owner that links it to a challenge organization and a property named Challenge.sponsors that list the supporting organization. With the proposal, we would replace them by the property Challenge.organizations that includes all the contributing organizations.
A nice benefit of this approach is that we can then have an Organization page for "challenge organization" AND for any organizations that contributed to at least one challenge. For example, the registry would include a page for IBM that provides general information about the organization as well as the list of challenges that this organization contributed to.
The Organization search page (upcoming but already designed in the Figma mockup) would enable the user to search among all the organization and not just the challenge organizations. For example, a user may be interested in searching an organization that contributed a specific type of data or provided cloud resources. The results of these two searches could then return organizations such as Kaiser Permanente and IBM.
Using a single model for organizations also mean that search challenges and organizations becomes easier to implement and offer a greater flexibility. For example, it would then be possible to associate more than one "challenge organization" to one challenge. For example, the BraTS page would then list both DREAM and MICCAI as contributing organizations.
Cost of this proposal
This design greatly simplifies the implementation of the backend and frontend. The authorization code becomes an extra layer that we can ignore for the private preview.

@vpchung and @rrchai agreed to this proposal in the last meeting.