Docker build fails on Windows 10

Docker engine version: 19.03.5
Docker Desktop version: <IP_ADDRESS>
I'm trying to build the project using Docker as described in the README, i.e. by running docker build -t ort . in the source directory with a Docker daemon running in the background. I'm on
Windows 10 (unfortunately) and I have tried to build with Git Bash and Powershell.
The build fails with the following error:
> Task :reporter-web-app:yarnBuild   [16/212]
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.$
-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.$
-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.$
-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.$
-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.$
-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.$
-linux-x64/bin/node)
yarn run v1.21.1
$ node scripts/build.js
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.$
-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.$
-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.$
-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.$
-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.$
-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.$
-linux-x64/bin/node)
Creating an optimized production build...
Browserslist: caniuse-lite is outdated. Please run next command `yarn upgrade caniuse-lite browserslist`
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with signal "SIGKILL".

> Task :reporter-web-app:yarnBuild FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':reporter-web-app:yarnBuild'.
> Process 'command '/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.BUILD FAILED in 18m 27s

Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings
45 actionable tasks: 45 executed
The command '/bin/sh -c scripts/set_gradle_proxy.sh &&     ./gradlew --no-daemon :cli:distTar' returned a non-zero code: 1

I can provide the full build log if needed.
Reading the comments on #2084, it seems Docker support on Windows is relatively new and using ORT with Docker on Windows is discouraged, but I would still apprecaite any support.
Thank you.
Uwe

Thanks a lot for your feedback. I will try the --stacktrace option on Monday when I'm back at work behind a corporate proxy. ;-)

Here's the build log with recorded with --stacktrace:
> Task :reporter-web-app:yarnBuild
yarn run v1.21.1
$ node scripts/build.js
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node)
Creating an optimized production build...
Browserslist: caniuse-lite is outdated. Please run next command `yarn upgrade caniuse-lite browserslist`
error Command failed with signal "SIGKILL".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

> Task :reporter-web-app:yarnBuild FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':reporter-web-app:yarnBuild'.
> Process 'command '/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node'' finished with non-zero exit value 1

* Try:
Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':reporter-web-app:yarnBuild'.
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$1(ExecuteActionsTaskExecuter.java:205)
	at org.gradle.internal.Try$Failure.ifSuccessfulOrElse(Try.java:263)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:203)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:184)
	at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:109)
	at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
	at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:62)
	at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
	at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
	at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:416)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:406)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$1.execute(DefaultBuildOperationExecutor.java:165)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:250)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:158)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:102)
	at org.gradle.internal.operations.DelegatingBuildOperationExecutor.call(DelegatingBuildOperationExecutor.java:36)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
	at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:41)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:372)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:359)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:352)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:338)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.lambda$run$0(DefaultPlanExecutor.java:127)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:191)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:182)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:124)
	at org.gradle.execution.plan.DefaultPlanExecutor.process(DefaultPlanExecutor.java:72)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph.executeWithServices(DefaultTaskExecutionGraph.java:189)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph.execute(DefaultTaskExecutionGraph.java:166)
	at org.gradle.execution.SelectedTaskExecutionAction.execute(SelectedTaskExecutionAction.java:41)
	at org.gradle.execution.DefaultBuildWorkExecutor.execute(DefaultBuildWorkExecutor.java:40)
	at org.gradle.execution.DefaultBuildWorkExecutor.access$000(DefaultBuildWorkExecutor.java:24)
	at org.gradle.execution.DefaultBuildWorkExecutor$1.proceed(DefaultBuildWorkExecutor.java:48)
	at org.gradle.execution.DryRunBuildExecutionAction.execute(DryRunBuildExecutionAction.java:49)
	at org.gradle.execution.DefaultBuildWorkExecutor.execute(DefaultBuildWorkExecutor.java:40)
	at org.gradle.execution.DefaultBuildWorkExecutor.execute(DefaultBuildWorkExecutor.java:33)
	at org.gradle.execution.IncludedBuildLifecycleBuildWorkExecutor.execute(IncludedBuildLifecycleBuildWorkExecutor.java:36)
	at org.gradle.execution.DeprecateUndefinedBuildWorkExecutor.execute(DeprecateUndefinedBuildWorkExecutor.java:39)
	at org.gradle.execution.BuildOperationFiringBuildWorkerExecutor$ExecuteTasks.run(BuildOperationFiringBuildWorkerExecutor.java:57)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:402)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:394)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$1.execute(DefaultBuildOperationExecutor.java:165)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:250)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:158)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:92)
	at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
	at org.gradle.execution.BuildOperationFiringBuildWorkerExecutor.execute(BuildOperationFiringBuildWorkerExecutor.java:42)
	at org.gradle.initialization.DefaultGradleLauncher.runWork(DefaultGradleLauncher.java:244)
	at org.gradle.initialization.DefaultGradleLauncher.doClassicBuildStages(DefaultGradleLauncher.java:154)
	at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:130)
	at org.gradle.initialization.DefaultGradleLauncher.executeTasks(DefaultGradleLauncher.java:110)
	at org.gradle.internal.invocation.GradleBuildController$1.execute(GradleBuildController.java:60)
	at org.gradle.internal.invocation.GradleBuildController$1.execute(GradleBuildController.java:57)
	at org.gradle.internal.invocation.GradleBuildController$3.create(GradleBuildController.java:85)
	at org.gradle.internal.invocation.GradleBuildController$3.create(GradleBuildController.java:78)
	at org.gradle.internal.work.DefaultWorkerLeaseService.withLocks(DefaultWorkerLeaseService.java:189)
	at org.gradle.internal.work.StopShieldingWorkerLeaseService.withLocks(StopShieldingWorkerLeaseService.java:40)
	at org.gradle.internal.invocation.GradleBuildController.doBuild(GradleBuildController.java:78)
	at org.gradle.internal.invocation.GradleBuildController.run(GradleBuildController.java:57)
	at org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActionRunner.java:31)
	at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
	at org.gradle.launcher.exec.BuildOutcomeReportingBuildActionRunner.run(BuildOutcomeReportingBuildActionRunner.java:63)
	at org.gradle.tooling.internal.provider.ValidatingBuildActionRunner.run(ValidatingBuildActionRunner.java:32)
	at org.gradle.launcher.exec.BuildCompletionNotifyingBuildActionRunner.run(BuildCompletionNotifyingBuildActionRunner.java:39)
	at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner$3.call(RunAsBuildOperationBuildActionRunner.java:51)
	at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner$3.call(RunAsBuildOperationBuildActionRunner.java:45)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:416)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:406)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$1.execute(DefaultBuildOperationExecutor.java:165)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:250)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:158)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:102)
	at org.gradle.internal.operations.DelegatingBuildOperationExecutor.call(DelegatingBuildOperationExecutor.java:36)
	at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner.run(RunAsBuildOperationBuildActionRunner.java:45)
	at org.gradle.launcher.exec.InProcessBuildActionExecuter$1.transform(InProcessBuildActionExecuter.java:50)
	at org.gradle.launcher.exec.InProcessBuildActionExecuter$1.transform(InProcessBuildActionExecuter.java:47)
	at org.gradle.composite.internal.DefaultRootBuildState.run(DefaultRootBuildState.java:80)
	at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:47)
	at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:31)
	at org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute(BuildTreeScopeBuildActionExecuter.java:42)
	at org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute(BuildTreeScopeBuildActionExecuter.java:28)
	at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:78)
	at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:52)
	at org.gradle.tooling.internal.provider.SubscribableBuildActionExecuter.execute(SubscribableBuildActionExecuter.java:60)
	at org.gradle.tooling.internal.provider.SubscribableBuildActionExecuter.execute(SubscribableBuildActionExecuter.java:38)
	at org.gradle.tooling.internal.provider.SessionScopeBuildActionExecuter.execute(SessionScopeBuildActionExecuter.java:68)
	at org.gradle.tooling.internal.provider.SessionScopeBuildActionExecuter.execute(SessionScopeBuildActionExecuter.java:38)
	at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:37)
	at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:26)
	at org.gradle.tooling.internal.provider.ParallelismConfigurationBuildActionExecuter.execute(ParallelismConfigurationBuildActionExecuter.java:43)
	at org.gradle.tooling.internal.provider.ParallelismConfigurationBuildActionExecuter.execute(ParallelismConfigurationBuildActionExecuter.java:29)
	at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:60)
	at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:32)
	at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:55)
	at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:41)
	at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:48)
	at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:32)
	at org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild(ExecuteBuild.java:68)
	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:37)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute(WatchForDisconnection.java:39)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute(ResetDeprecationLogger.java:27)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon.execute(RequestStopIfSingleUsedDaemon.java:35)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.create(ForwardClientInput.java:78)
	at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.create(ForwardClientInput.java:75)
	at org.gradle.util.Swapper.swap(Swapper.java:38)
	at org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute(ForwardClientInput.java:75)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.LogAndCheckHealth.execute(LogAndCheckHealth.java:50)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java:63)
	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:37)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:82)
	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:37)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:52)
	at org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:297)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
Caused by: org.gradle.process.internal.ExecException: Process 'command '/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node'' finished with non-zero exit value 1
	at org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:417)
	at org.gradle.process.internal.DefaultExecAction.execute(DefaultExecAction.java:38)
	at org.gradle.api.tasks.AbstractExecTask.exec(AbstractExecTask.java:66)
	at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:104)
	at org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:49)
	at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:42)
	at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:28)
	at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:727)
	at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:694)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$3.run(ExecuteActionsTaskExecuter.java:568)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:402)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:394)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$1.execute(DefaultBuildOperationExecutor.java:165)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:250)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:158)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:92)
	at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:553)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:536)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.access$300(ExecuteActionsTaskExecuter.java:109)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution.executeWithPreviousOutputFiles(ExecuteActionsTaskExecuter.java:276)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution.execute(ExecuteActionsTaskExecuter.java:265)
	at org.gradle.internal.execution.steps.ExecuteStep.lambda$execute$1(ExecuteStep.java:33)
	at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:33)
	at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:26)
	at org.gradle.internal.execution.steps.CleanupOutputsStep.execute(CleanupOutputsStep.java:63)
	at org.gradle.internal.execution.steps.CleanupOutputsStep.execute(CleanupOutputsStep.java:35)
	at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:49)
	at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:34)
	at org.gradle.internal.execution.steps.CancelExecutionStep.execute(CancelExecutionStep.java:43)
	at org.gradle.internal.execution.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:73)
	at org.gradle.internal.execution.steps.TimeoutStep.execute(TimeoutStep.java:54)
	at org.gradle.internal.execution.steps.CatchExceptionStep.execute(CatchExceptionStep.java:34)
	at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:44)
	at org.gradle.internal.execution.steps.SnapshotOutputsStep.execute(SnapshotOutputsStep.java:54)
	at org.gradle.internal.execution.steps.SnapshotOutputsStep.execute(SnapshotOutputsStep.java:38)
	at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:49)
	at org.gradle.internal.execution.steps.CacheStep.executeWithoutCache(CacheStep.java:153)
	at org.gradle.internal.execution.steps.CacheStep.executeAndStoreInCache(CacheStep.java:129)
	at org.gradle.internal.execution.steps.CacheStep.lambda$executeWithCache$2(CacheStep.java:107)
	at org.gradle.internal.execution.steps.CacheStep.lambda$executeWithCache$3(CacheStep.java:107)
	at org.gradle.internal.Try$Success.map(Try.java:162)
	at org.gradle.internal.execution.steps.CacheStep.executeWithCache(CacheStep.java:76)
	at org.gradle.internal.execution.steps.CacheStep.execute(CacheStep.java:66)
	at org.gradle.internal.execution.steps.CacheStep.execute(CacheStep.java:41)
	at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:44)
	at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:33)
	at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:38)
	at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:24)
	at org.gradle.internal.execution.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:92)
	at org.gradle.internal.execution.steps.SkipUpToDateStep.lambda$execute$0(SkipUpToDateStep.java:85)
	at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:55)
	at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:39)
	at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:76)
	at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:37)
	at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:36)
	at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:26)
	at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:94)
	at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:49)
	at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:79)
	at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:53)
	at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:74)
	at org.gradle.internal.execution.steps.SkipEmptyWorkStep.lambda$execute$2(SkipEmptyWorkStep.java:78)
	at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:78)
	at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:34)
	at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsStartedStep.execute(MarkSnapshottingInputsStartedStep.java:39)
	at org.gradle.internal.execution.steps.LoadExecutionStateStep.execute(LoadExecutionStateStep.java:40)
	at org.gradle.internal.execution.steps.LoadExecutionStateStep.execute(LoadExecutionStateStep.java:28)
	at org.gradle.internal.execution.impl.DefaultWorkExecutor.execute(DefaultWorkExecutor.java:33)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:192)
	... 125 more

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 6m 42s
45 actionable tasks: 45 executed

I hope this provides more insight for you. Please let me know if I can supply more info.
Thank you.

I just tried running docker build -t ort . on windows and got to step 9 and got the following
Reading state information...
E: Version '1.9.1-1' for 'composer' was not found
E: Version '6.13.4+ds-2' for 'npm' was not found
The command '/bin/sh -c apt-get update &&     apt-get install -y --no-install-recommends         curl         lib32stdc++6         openssh-client         cvs         git         mercurial         bundler=$BUNDLER_VERSION         cargo=$CARGO_VERSION         composer=$COMPOSER_VERSION         go-dep=$GO_DEP_VERSION         haskell-stack=$HASKELL_STACK_VERSION         npm=$NPM_VERSION         python-pip=$PYTHON_PIP_VERSION         python-setuptools         python3-pip=$PYTHON_PIP_VERSION         python3-setuptools         sbt=$SBT_VERSION     &&     rm -rf /var/lib/apt/lists/*'
returned a non-zero code: 100

Should not really matter that I'm running Docker on Windows in this case?
In the end what I really want is to run the Analyzers standalone. Having a separate build of that would be great.

@jeffmcaffer looks like some Debian Sid packages need to be updated again. I can do so once I am back from vacation.

The issue I had above is resolved by PR #2187 (not yet merged) BUT, I now have what appears to be a similar problem as @oova though I am running Ubuntu 18 using WSL2 on Windows. So I'm running full on linux under windows and docker in there. Everything goes swimmingly until I get to task 2 (Yarn install) for the reporter-web-app:yarnInstall task.
Then I get output that looks something like the following
> Task :reporter-web-app:yarnInstall
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node)
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node)
yarn install v1.21.1
/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node: /usr/lib/libstdc++.so.6: no version information available (required by /root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node)
[1/4] Resolving packages...
[2/4] Fetching packages...

> Task :spdx-utils:compileJava
> Task :spdx-utils:classes
> Task :spdx-utils:inspectClassesForKotlinIC
> Task :spdx-utils:jar

> Task :reporter-web-app:yarnInstall
info There appears to be trouble with your network connection. Retrying...

That goes on for a bit and then the following appears
> Task :reporter-web-app:yarnInstall
info If you think this is a bug, please open a bug report with the information provided in "/usr/local/src/ort/reporter-web-app/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
error An unexpected error occurred<EMAIL_ADDRESS>ESOCKETTIMEDOUT".
info There appears to be trouble with your network connection. Retrying...

> Task :analyzer:compileJava NO-SOURCE
> Task :analyzer:classes
> Task :analyzer:inspectClassesForKotlinIC
> Task :analyzer:jar
> Task :cli:compileKotlin
> Task :cli:compileJava NO-SOURCE
> Task :cli:classes
> Task :cli:inspectClassesForKotlinIC
> Task :cli:jar

> Task :reporter-web-app:yarnInstall
warning<EMAIL_ADDRESS>Invalid bin field for "mini-css-extract-plugin".
warning<EMAIL_ADDRESS>Invalid bin field for "url-loader".
warning<EMAIL_ADDRESS>Invalid bin entry for "sha.js" (in "sha.js").

> Task :reporter-web-app:yarnInstall FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':reporter-web-app:yarnInstall'.
> Process 'command '/root/.gradle/nodejs/node-v10.15.3-linux-x64/bin/node'' finished with non-zero exit value 1

* Try:
Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':reporter-web-app:yarnInstall'.
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$1(ExecuteActionsTaskExecuter.java:205)

I can confirm that my network is fine from the Ubuntu system. I get 200Mb/s download consistently and all other network operations appear fine so it is doubtful that it's actually a network problem. I can also confirm that the build always seems to fail on ant-design/icons and that file is both small (<1MB) and wget of that URL works fine (and takes 0.07s).
Something else is afoot here.

I had similar issues yesterday, also using Ubutut as a WSL2 - but not Docker. First, I had to add both the yarn and the npm registry's IP to the hosts file (otherwise DNS EAI_AGAIN issues), then had to repeat this installation step 3 or 4 times, until finally all packages had been successfully downloaded

Feels a bit different from my case as I'm able to do wget<EMAIL_ADDRESS>and ping npmjs.com. Are there other hosts you had to add?

nope, those were the only two. By similar issues, I meant the fact that I also saw ESOCKETTIMEDOUT for various yarn packages. After 3 or 4 retries, this installation step succeeded. In your case, does it always fail on the same package icons-2.0.1.tgz?

Seems to always fail on that one (I was not keeping rigorous track) and it always fails. It may just be that that one is the first it tries do download, even if it's doing them in parallel. It is not the first in the lock file but who knows how the resolution and ordering code works. I suppose I could figure out some network tracing to see what's happening...

Maybe try setting a higher yarn network timeout, non-ORT users seem to have similar issues https://github.com/dhis2/notes/issues/29

That could be it. I looked quickly but not being a gradle person, did not see an obvious place to put that command line option. Is there a high level place where that can be configured or should I be weaseling away in the guts of the gradle file for the reporting-web-app?

I believe there is no need to mess with Gradle here, @jeffmcaffer. Could you please check whether the branch at https://github.com/heremaps/oss-review-toolkit/pull/2196 solves your issue?


AppOpsX已被Google Play下架，已安装用户被提示：卸载有害应用，“AppOpsX”可能有害

I am getting the same warning. It began December 30, 2018 at approximately 11:45 AM EST. I am using version 1.25 of the app and have been for almost a year now. My device is a Samsung Galaxy S5 Neo. It was issued in Canada. The odd thing is my son has the exact same phone (make, model) which was acquired at the same time and place as mine. With the exception of a few games, the phones are identical (same setup, version, OS, apps) though he is not getting this message, even after several scans from Google Play Protect.

卸载理由不一样，Google 搞啥。

是的，我的Google Play Console账号都被停用了，已经发邮件反馈申诉了。应该和调用了系统hide api有关，这个在Android P上不允许。绝对没有加任何广告和泄露隐私的代码，这段时间有点忙我会抽空更新下。

没来得及看源码，用了appopsx之后每过段时间剪贴板就会复制一个支口令。卸载之后就好了，谁的锅？

没来得及看源码，用了appopsx之后每过段时间剪贴板就会复制一个支口令。卸载之后就好了，谁的锅？

可能是被电信运营商劫持。解决方法禁止支付宝读取剪切板。

@8enet play上下载的 下午试了appops 也有一样问题，卸载后就没事了

@LiJinChang 禁用就比较极端了 不找到是谁干的总觉得不放心，还是得折腾一下

This is foss. All the source code are there, you read the fine source and compile it.

退一步讲，哪个当JC的自己还会犯法？

应用控制器 <_<

抱歉开发者和其他各位，问题找到了。是无良网站的锅，复制的内容都是支付宝的吱口令


add newline to end of update message

this was annoying me but it's only an aesthetic change

Your commit history is still kinda broken, refork again and checkout new branches for every change instead of pulling.


Update SDK version and storage queue config

Changelog

Update Azure SDKs version
Add storage service component
Add storage queue terraform config

Re-create a new PR: https://github.com/saragluna/azure-spring-boot-sample/pull/2


[Unittest][C++] Fix call to ancient API

Related to #171

Coverage remained the same at 85.409% when pulling 0cf320d7dea23a8ef2ae282ab7cb63b674b7aa0e on fvalenza:topic/GeomUnittestAPIFix into 29ff6942b8373f7ed32652410cbd66aa5e576492 on stack-of-tasks:devel.


Remove contracts from the startup path

Seems like the reason for using Contract.Assert instead of
Debug.Assert in the startup path was that Debug.Assert won't work
because it's not low level enough (needs String.Empty to work).
Contract.Assert is still problematic when the condition is not met.
The right solution is to actually define a lower level Assert.

LGTM


Fix "creat issue" typo

In "Configuring private vulnerability reporting for a repository".

Why:
Fixes a typo.

What's being changed (if available, include any code snippets, screenshots, or gifs):
The text:

creat issue

is corrected to:

create issue

Check off the following:

[x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

@StevenMaude Thanks so much for opening a PR! I'll get this triaged for review :zap:


Dev methods fixes

Ticking off a variety of smaller to-dos from #15 :

Fixed adaptivity checks to not trigger for Heun etc.
Improved default method selection to not use SRK when that's not appropriate. (Strat etc.)
Updated test_sdeint.py to use pytest, and improved its test coverage.

The tests in test_sdeint.py are very numerous (~2000) covering all the common combinations of inputs, but are quick to run (~3 minutes); I felt it was best to be comprehensive on this central part of the library.
Thanks for your email btw - fortunately we've been doing different things, but I should have let you know!

I think we should also be able to merge problems.py and basic_sde.py now. I'd suggest keeping Ex1-4 and BasicSDE1-4. No pressure in doing it in this PR. I can also send in another PR on this issue.

I agree merging them makes sense. I've left them alone for now though.


change ip for presentation

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
http://guh.guru:8080/job/guh-webinterface-pull-request/20/
Test PASSed.


SubscriptionTreeItem's loadMoreChildrenImpl called twice when expanding subscription

Steps to reproduce in Azure Storage extension:

Set breakpoint at SubscriptionTreeItem.ts Line 27
Launch extension
Find a subscription that has an Azure Storage account and expand its tree item

Notice the breakpoint is triggered twice. Is this expected behaviour?

@EricJizbaMSFT do you know why this is happening?

I briefly looked into it and seems like the Azure Account extension might be sending an extra event that the subscriptions have changed (even though they haven't) soon after activation. Might be able to optimize this, but not sure if it's worth it


Yet another possible alternative to current header/body separation

BeaconBlock: {
    "parent_hash": 'hash32',
    "body": BeaconBlockBody
}

BeaconBlockBody: {
    'ancestor_hashes': ['hash32'],
    'state_root': 'hash32',
    'randao_reveal': 'hash32',
    'candidate_pow_receipt_root': 'hash32',
    'signature': ['uint384'],
    'attestations': [Attestation],
    'proposer_slashings': [ProposerSlashing],
    'casper_slashings': [CasperSlashing],
    'deposits': [Deposit],
    'exits': [Exit],
}

Rationale: now you can download an entire mini-chain with just 32 bytes per block.
I'm not sure whether or not I agree with doing this BTW, just wanted to raise it for discussion.

IMO chain of headers (or however it's called) would be useful if it would be feasible to check whether it's valid or not. Otherwise, it becomes unreliable. One of the applications of this mini-chain could be in fork handling which seems not so useful without reliability.
I am starting to think that chain of headers is not a valuable thing for the beacon chain. For example, it could not be verified without knowing all shard_committees_at_slots and validator_registry samples that were used to build this chain. Which looks pretty inefficient.

Considering most syncs will be from a known finalized slot

This assumption might require a separate discussion. The main question is how to prove that given finalized slot is a product of a sequence of valid state transitions originated from a certain initial_state?

@mkalinin  As far as I can see the only way we could verify would be to download all the blocks from genesis till the last finalized slot in order to determine that the state transitions were all valid.

I've described one possible efficient syncing scheme here:
https://notes.ethereum.org/s/BJPBa42TQ#Beacon-chain-sync
The general idea is that you'll be syncing primarily the changes in the validator set by obtaining a very sparse set of blocks where a super-majority of the validators known to you have signed a new validator_registry_delta_chain_tip hash. Once you know the latest validators, it's enough to obtain only the latest block, because through the slashing rules, the timestamp of the block (its slot number) and the signatures of the validators are enough to authenticate it.
We hope to run an experiment with a proof-of-concept implementation of this scheme in the December release of Nimbus.

Thanks @zah for sharing this scheme! Indeed, it looks pretty efficient, at least for light clients.
For those who don't want to stick with weak subjectivity, this scheme could be featured with additional accumulator for next_seed, e.g. seed_update_root, which is similar thing as validator_registry_delta_chain_tip. Then by downloading a chain of headers and requesting tips on validator set changes and seed updates (upon they are detected) it would be possible to get a consensus proof of validity of state that corresponds to the finalized slot.
This approach would require to store historical data like headers and tips, though. Not that big as a history of block bodies but still something that will be constantly growing.

@vbuterin Do you still want to make a case for this format?


Repeat Cycle Help

Hello. I have a question about the planner section. I have set up repeatable quests but I am not sure if it is bugged or if maybe im doing it wrong.
I set a start time, end time, repeat cycle time, ect. And when I click the npc a message says “quest will be activated in ___ seconds” but when it reaches that time it just resets the timer completely and no quest is available.
I wont appreciate the help and if you need more info id gladly give it. Thank you

Need to see what values you've set. Either copy/paste from quests.yml or take a screenshot of the editor in-game.
Also, see https://github.com/PikaMug/Quests/wiki/Beginner-‐-Planner

planner:
start: 28:3:2020:9:0:0:America/Toronto
end: 28:3:2020:8:59:59:America/Toronto
repeat: 86400
cooldown: 32400

Its not just this quest but its for all of them (including the one on the wiki page for an example daily quest)

The start date is March 28th @ 9:00 AM
The end date is March 28th @ 8:59 AM
You can't have a quest end before it starts. Either set your start date earlier, or your end date later.

If you don't want a quest to be available only on certain hours of the day, I just set the start date = now and the end date to year 9999, just with the cooldown I want (e.g. 120 seconds).


type of implicit definition needs to be given explicitly (http4s client)

Hi there, thanks for this project. Very happy so far.
We're trying to migrate to scala 3, and on of the things which came up was this.
I need to make this manual change to use a generated http4s client, in Implicits.scala
-    implicit val showString = build[String](Predef.identity)
-    implicit val showInt = build[Int](_.toString)
-    implicit val showLong = build[Long](_.toString)
-    implicit val showFloat = build[Float](_.toString)
-    implicit val showDouble = build[Double](_.toString)
-    implicit val showBigInt = build[BigInt](_.toString)
-    implicit val showBigDecimal = build[BigDecimal](_.toString)
-    implicit val showBoolean = build[Boolean](_.toString)
-    implicit val showLocalDate = build[java.time.LocalDate](_.format(java.time.format.DateTimeFormatter.ISO_DATE))
-    implicit val showOffsetDateTime = build[java.time.OffsetDateTime](_.format(java.time.format.DateTimeFormatter.ISO_OFFSET_DATE_TIME))
-    implicit val showJavaURL = build[java.net.URI](_.toString)
-    implicit val showUUID = build[java.util.UUID](_.toString)
+    implicit val showString: Show[String] = build[String](Predef.identity)
+    implicit val showInt: Show[Int] = build[Int](_.toString)
+    implicit val showLong: Show[Long] = build[Long](_.toString)
+    implicit val showFloat: Show[Float] = build[Float](_.toString)
+    implicit val showDouble: Show[Double] = build[Double](_.toString)
+    implicit val showBigInt: Show[BigInt] = build[BigInt](_.toString)
+    implicit val showBigDecimal: Show[BigDecimal] = build[BigDecimal](_.toString)
+    implicit val showBoolean: Show[Boolean] = build[Boolean](_.toString)
+    implicit val showLocalDate: Show[java.time.LocalDate] = build[java.time.LocalDate](_.format(java.time.format.DateTimeFormatter.ISO_DATE))
+    implicit val showOffsetDateTime: Show[java.time.OffsetDateTime] = build[java.time.OffsetDateTime](_.format(java.time.format.DateTimeFormatter.ISO_OFFSET_DATE_TIME))
+    implicit val showJavaURL: Show[java.net.URI] = build[java.net.URI](_.toString)
+    implicit val showUUID: Show[java.util.UUID] = build[java.util.UUID](_.toString)

my config
project/plugins.sbt
addSbtPlugin("dev.guardrail" % "sbt-guardrail" % "<IP_ADDRESS>")
build.sbt
      Compile / guardrailTasks += ScalaClient(
        ...file,
        framework = "http4s",
        pkg = "..."
      ),

@oyvindberg This should be fairly straightforward, if you've got time to take a crack at it, see here for where to get started.
We don't have a super great way to separate generation from integration tests currently, but if you do:
sbt> resetSample
sbt> runExample scala http4s
sbt> ++ 3.1.0 !
sbt> sample-http4s/Test/compile

that should (might?) give you enough in order to get going with compiling/running the regression suite under 3.1.x. Some changes in order to coerce 2.13 dependencies to be resolved for 3.1.x, but presumably you've got a good handle on how to do that (project definitions are here.


arch: nrf: Use SystemInit() from MDK in SoC initialization

Replace code that handles erratas and performs other SoC-specific
initialization, that was actually copied from SystemInit() provided
in MDK for particular SoCs, with a call to SystemInit().
Signed-off-by: Andrzej Głąbek<EMAIL_ADDRESS>

Nice! thanks for this, we really didn't need that code duplication.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@15ae4fa). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #8447   +/-   ##
=========================================
  Coverage          ?   64.61%
=========================================
  Files             ?      421
  Lines             ?    40296
  Branches          ?     6803
=========================================
  Hits              ?    26037
  Misses            ?    11126
  Partials          ?     3133

Continue to review full report at Codecov.

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

Updated the commit title in accordance with this comment.


Monitoring Activity Linked Treatment ID in Redux

Overview
This PR includes the following proposed change(s):
issue/#2121
Type of change

[ ] Added redux saga for retrieving treatment activities related to Monitoring activity type and sub type.
[ ] Populates the Linked Treatment ID auto-complete select input.
[ ] Removed old Treatment ID retrieval methods not related to redux action or saga operations.

How Has This Been Tested?
On going testing of:

[ ] Treatment IDs are loaded into the Linked Treatment ID auto-complete option items.
[ ] Treatment IDs are related to the Monitoring activity record type and sub type.
[ ] Selected Treatment ID is saved to the record.
[ ] Linked Treatment ID is loaded into the field from a saved record display.

Screenshots

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] New and existing unit tests pass locally with my changes

This push is WIP.
Issues to resolve:

[ ] Clear suggestedTreatmentIDs state store for non-monitoring record types on change.
[ ] Loading of saved records.  Click on a saved record and does not populate Linked Treatment ID and options are empty.


[DEV] Update design-tokens package to new package (post brand-evolution)

Closing as not planned this quarter as brand evolution roll out date has moved


Add functionality to create/update/delete monetary accounts

[x] Create monetary accounts
[ ] Update monetary accounts
[ ] Delete monetary accounts


Whitelist dialogue

Maybe we should show a dialogue when the bot receives a "hi" from a non whitelisted chat. This dialogue could show a "add 'sender name' to whitelist" button. This would be one more step towards a texteditor free configuration.
We should wait with this for #66.

This seems a bit unsafe to me.. What is the whitelist for, if anybody sending "hi" can add himself to it? IMHO, at least an admin of the bot would need to accept that user/chat-ID (asking for the admin mode #35 with some more improvements...).

I think we could make that work.
But then we would also need a blacklist in which the rejected chatid's would be stored.
@Trenar, the sender would have to be on site so that he can confirm himself by touching  'Confirm' on the TeleFrame screen.

But if he isn't on site but requests access and my grandma presses okay, not understanding what's happening? I'd prefer the admin to actively whitelist chat ids

Yes, I am familiar with the problem that technically less experienced people always like to confirm with "Yes I do". 🙈
But this feature has to be enabled in the config anyway and should not be active by default.


Added Examples + Made Custom Fitness Function

@marcjermaine-pontiveros Merged. Thank you so much for the pull.


json File

not have  _images.json files in dataset class

Hi, the tutorial is complete now. Please see this section to commence training.


Handle bfloat16 weights in disk offload

This PR handles a bug reported in #454 concerning bfloat16 and disk offload.
NumPy does not support bfloat16, so while storing those tensors on disk, we need to convert them back as float32 (can't convert them in float16 without losing precision). This not super efficient but it's the best we can offer until NumPy offers support for this dtype.
A new test is added to check the offload on disk with bfloat16 works. It doesn't need any specialized hardware since we don't do anything on the bfloat16 tensor.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Access to XMLHttpRequest at '' from origin '' has been blocked by CORS policy

Hi, When i use chrome browser without proxy, it works fine, but with Titanium Proxy it does not work for some requests:
Access to XMLHttpRequest at 'https://webapi.papara.com/validate/phone' from origin 'https://www.papara.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

I realized when i call website on Proxy, it respond like this:
Error 1020 Ray ID: 5fc49017a9ffe003 • 2020-12-04 09:39:54 UTC
Access denied
Cloudflare Ray ID: 5fc49017a9ffe003 • Your IP: x.x.x.x • Performance & security by Cloudflare

I solved it, it was because of Certification.
Now the problem is, when i use proxy, chrome shows a human verification.

If the proxy is running on a different public IP address, and if the website you are browsing uses Google ReCaptcha, it may flag your proxy IP as having poor reputation. Based on that ReCaptacha on site may ask you for human verification.
If that is the case, adding proxy forward headers may solve the issue. I am not sure.
https://systemoverlord.com/2020/03/25/security-101-x-forwarded-for-vs-forwarded-vs-proxy.html

I solved it, it was because of Certification. Now the problem is, when i use proxy, chrome shows a human verification.

Did you solve that issue?


why was alt+enter disabled

What is your question?
why

people use that and this is a really scuffed way of doing this either way, i thought i broke something in my branch at first. having alt+enter put you into full screen and then do this janky ass "panic and go back out of fullscreen" visual effect isn't exactly a good look for the engine
the new additions of having to exit the game to enable botplay and practice mode were annoying enough as is, not being able to toggle fullscreen without going all the way back into the options menu is worse, especially when trying to test things

-- looking into this further it seems like this was all done to "fix" the letterbox when you play at a different resolution??? but the graphics of everything are designed with 16:9 in mind so making the video taller like that will just cause more problems, and having a letterbox in 4:3 feels like a worthy sacrifice to have the ability to change the game's resolution to whatever you'd like??????????????
-- i'm sorry but this just isn't a good implementation at all, it makes the engine feel buggier

-- possibly a better way of handling what's trying to be done here: #3376


Azure Devops Virtual Agent - Please enter a valid email address ("efffdc56-fd4c-aeba-6cd3-d07aaf776d51")

When I'm trying to use the @regionmove flow in the Azure Devops Virtual Agent, I have the following error after entering my organization email<EMAIL_ADDRESS>in the region move form.

@sblais-nb  Thank you for the question.
If you can you provide a reference to the an article, I can assign this to an author for further review.
Otherwise, if this is a product-related issue, you can use Report a problem or Suggest a feature in the Azure DevOps community to solicit feedback from the product team.
Or, for additional support options, see:

Azure DevOps Support
Azure DevOps on StackOverflow

Closing this issue now.

The article is : https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/change-organization-location?view=azure-devops.
The link to the Azure Agent is : https://azuredevopsvirtualagent.azurewebsites.net/

@sblais-nb Thank you for the reference, assigning this to the author for review.
Please note our support is limited to the examples in the document.
For support on more user-specific scenarios, please refer to this post or try the following:

Azure DevOps Support
Azure DevOps community
Azure DevOps on StackOverflow

Hi @sblais-nb, Since this isn't a documentation issue, I'm closing it. But, since it's saying that your email address isn't valid, you may want to contact Support. Thank you.


3DPW data

Hello, thanks for the great work!
I tried to derive the same values as your 3DPW parsed data but I was unable to obtain the same values h36m_joints and smpl_joints.
I have a few questions:
(1) What are your inputs into the SMPL and H36M regressor?
(2) Was any translation applied?
(3) How did you obtain the root coordinate?
With regards to (3), I've attached a screenshot of my outputs from h36m regressor. They differ from your g-t h36m_joints by an offset, which seems to be the "root coordinate". However, I'm unable to find this "root" from the original dataset. I was wondering how did you derive it? This is the same for your g-t  smpl_joints

Hope to get your advice on this, thanks!

FYI, root_joint is either the first joint in SMPL or the average of left_hip and right_hip.

@wangzheallen Thanks for the reply. By "first joint in SMPL", do you mean the outputs from the SMPL regressor?
The first joint for my outputs from h36m regressor and smpl regressor were all zeros. However, in the author's provided g-t, the root joint of h36m_joints is [ 0.01080098 -0.25635168  0.0397297 ] and similarly, the root_joint of smpl_joints is [1.14881551 0.2267409  5.68205261], a non-zero value.
I can't seem to derive those root-joints or ground-truths for h36m_joints and smpl_joints from the raw 3DPW data. I was wondering if you have any idea on how to do that?

@Jeff-sjtu I used the same h36m regressor.
Unlike #43 , h36m_joints - h36m_joints root coordinate (I calculated) = h36m_joints - h36m_joints root coordinate (You provide) is the same. However, I am unable to obtain the exact h36m_joints root coordinate and smpl_joints root coordinate from yours. How did you obtain those root-coordinates from raw 3DPW data?
Thanks!


The action 'Pin to Quick Access' on the context menu is not localized for one file share folder

Storage Explorer Version: 1.37-dev (103)
Build Number: 20241128.3
Branch: main
Platform/OS: Windows11/Windows10/Linux Ubuntu 22.04/MacOS Sequoia 15.1(Apple M1 Pro)
Reproduce Languages: All
Architecture: arm64/x64/x64/arm64
How Found: From running test cases
Regression From: Not a regression
Steps to Reproduce

Launch Storage Explorer -> Open 'Settings' -> 'Application -> Regional Settings'.
Select '中文(简体)' -> Restart Storage Explorer.
Expand one storage account -> File Shares.
Create a file share -> Upload a folder.
Right click the folder -> Observe the actions on the context menu.
Check whether the action 'Pin to Quick Access' is localized.

Expected Experience
The action 'Pin to Quick Access' is localized.
Actual Experience
The action 'Pin to Quick Access' is not localized.

@RichardMSFT make sure this string is a resource. If it is, continue to monitor the translation status. You can close once a translated string is checked in and being used the by Standalone on main. Move to 1.38 if needed as well, this shouldn't block the overall feature.


fix(deps): update aws-sdk-go-v2 monorepo

This PR contains the following updates:

Package
Type
Update
Change

github.com/aws/aws-sdk-go-v2/config
require
patch
v1.27.18 -> v1.27.19

github.com/aws/aws-sdk-go-v2/credentials
require
patch
v1.17.18 -> v1.17.19

github.com/aws/aws-sdk-go-v2/service/ecr
require
patch
v1.28.5 -> v1.28.6

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

ℹ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

8 additional dependencies were updated

Details:

Package
Change

github.com/aws/aws-sdk-go-v2
v1.27.2 -> v1.28.0

github.com/aws/aws-sdk-go-v2/feature/ec2/imds
v1.16.5 -> v1.16.6

github.com/aws/aws-sdk-go-v2/internal/configsources
v1.3.9 -> v1.3.10

github.com/aws/aws-sdk-go-v2/internal/endpoints/v2
v2.6.9 -> v2.6.10

github.com/aws/aws-sdk-go-v2/service/internal/presigned-url
v1.11.11 -> v1.11.12

github.com/aws/aws-sdk-go-v2/service/sso
v1.20.11 -> v1.20.12

github.com/aws/aws-sdk-go-v2/service/ssooidc
v1.24.5 -> v1.24.6

github.com/aws/aws-sdk-go-v2/service/sts
v1.28.12 -> v1.28.13


Bug 1767954: Add CRDs to update and verify targets

Add "verify-codegen-crds" as a dependency to the "verify" target, and "update-codegen-crds" to the "update" target

/assign @tnozicka
this look right? It seems to work locally for me, and we're not dependent on the order that the verify check is run, just needs to run at some point


Empty tuple on ALB setup

Hello,
Getting this suddenly on v2.25.0 up to and including v2.35.0.
We are still on terraform 0.12.31.

Error: Invalid index

  on .terraform/modules/atlantis.alb/main.tf line 327, in resource "aws_lb_listener" "frontend_http_tcp":
 327:   load_balancer_arn = aws_lb.this[0].arn
    |----------------
    | aws_lb.this is empty tuple

The given key does not identify an element in this collection value.

Error: Invalid index

  on .terraform/modules/atlantis.alb/main.tf line 369, in resource "aws_lb_listener" "frontend_https":
 369:   load_balancer_arn = aws_lb.this[0].arn
    |----------------
    | aws_lb.this is empty tuple

The given key does not identify an element in this collection value.

closing for now - please feel free to provide more information and include a copy of your config so we can better help troubleshoot


Add Java 10 to the list of supported JVMs

We currently do not have any support for Java 10 in STF. So, STF breaks with the following exception once run with Java 10 :
04:38:39 GEN stderr Exception in thread "main" net.adoptopenjdk.stf.StfException: Unknown JVM release: linux_ppcle-64
Link to failure: https://ci.adoptopenjdk.net/view/System tests/job/openjdk10_hs_systemtest_ppc64le_linux/2/
The fix is to add support for Java version 10.

PR: https://github.com/AdoptOpenJDK/stf/pull/30

Personal build running with this change:https://ci.adoptopenjdk.net/view/work in progress/job/test_personal/175/console


ARROW-6271: [Rust] [DataFusion] Add example for running SQL against Parquet

A simple example for running SQL against a Parquet file.
Related to ARROW-6271.

@andyscho do you have a JIRA account, I wanted to assign the issue to you before merging?

@andyscho do you have a JIRA account, I wanted to assign the issue to you before merging?

@paddyhoran Yup. My username is the same as on Github. Please let me know if there are any problems.


User documentation?

Hi, firstly thanks for your work.
Now, what brings me here is that I don't understand how I am supposed to use this bridge.
Please note that I am new to matrix and the bridging concept, maybe I missed something but your readme explains how to link a steam account and that I did correctly.
What is missing now is: how do I initiate communication with a steam user? I tried the help command but I am quite lost.
Is there some guide explaining how to proceed please?

I'm in the same boat. You ever figure this out?

I'm in the same boat. You ever figure this out?

Not yet, from what people told me on the dedicated matrix room (#mx-puppet-bridge:sorunome.de) I should just be invited in a room whenever someone sends me a message on steam but that never worked. I'm still hoping I'll find some detailed steps.

Not yet, from what people told me on the dedicated matrix room (#mx-puppet-bridge:sorunome.de) I should just be invited in a room whenever someone sends me a message on steam but that never worked. I'm still hoping I'll find some detailed steps.

No yet. From what people told me in the dedicated matrix room (#mx-puppet-bridge:sorunome.de) I should be invited to a room whenever someone sends me a message but that never worked. I'm still hoping I'll find some detailed steps to making this work.

No yet. From what people told me in the dedicated matrix room (#mx-puppet-bridge:sorunome.de) I should be invited to a room whenever someone sends me a message but that never worked. I'm still hoping I'll find some detailed steps to making this work.

I have the same problem. linked steam but I dont get invited to rooms

I have the same problem. linked steam but I dont get invited to rooms

can you explain step by step how to set this up? check out my steps #45 there.


feat: exposing leasing company website

Closes #issue

Description
This exposes the leasing agent's company website field on the partners side
How Can This Be Tested/Reviewed?
Log in to the partner's site as an admin user
go to create a new listing
fill out all the info, including the newly exposed Company Website field
save the listing
verify the listing details page on the partner's side expose that information
go in and edit the listing, and verify that the company website info is there and available and its possible to change that info
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have reviewed the changes in a desktop view
[x] I have reviewed the changes in a mobile view
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I have assigned reviewers
[ ] I have run yarn generate:client and/or created a migration if I made backend changes that require them
[ ] I have exported any new pieces added to ui-components
[x] My commit message(s) is/are polished, and any breaking changes are indicated in the message and are well-described
[x] Commits made across packages purposefully have the same commit message/version change, else are separated into different commits

Reviewer Notes:
Steps to review a PR:

Read and understand the issue
Review the code itself from a style point of view
Pull the changes down locally and test that the acceptance criteria is met
Also review the acceptance criteria on the Netlify deploy preview (noting that these do not yet include any backend changes made in the PR)
Either explicitly ask a clarifying question, request changes, or approve the PR if there are small remaining changes but the PR is otherwise good to go

On Merge:
If you have one commit and message, squash. If you need each message to be applied, rebase and merge.

Hey @emilyjablonski this is ready for you to peep again

We might want to make a ticket to add the same validator to other URL fields like the custom app URL

Hey @seanmalbert this is ready for re-review

Hey @seanmalbert this should be ready for your 👀 again


HC-473: Expose publish_overwrite_ok in submit_job

Part of HC-473 work

we should bump the version in setup.py


Distributed PetClinic with Spring Cloud

I would like to provide a "Spring Cloud" branch for the application to show how to split existing monolithic application into microservices. Distributed vesion would be based on a codebase from "angularjs" branch . What do you guys think?

I Maciej. This could be a great idea but could you please wait one or two weeks? Indeed the angularjs branch will be move to another repository.

Thanks for your replay. Actually I'm almost finished with a basic version built with Spring Cloud Config, Eureka, Hystrix and Zuul. Of course I can wait with a pull request for the new repository. By the time it is created, I should be ready with adjusted Docker setup. You can assign a task to me.

You might want to look at #200 as well. That kind of modularization could be useful. if you are going to split the "monolith" (otherwise I can't see the point of introducing all the Spring Cloud stack).

Hi Dave, thanks for your comment. I already did something similar with Visit entity when I was trying to define bounded contexts. And yes, I'm going to split the monolith :)

Dave, you may see the Maciej's work here: https://github.com/spring-petclinic/spring-petclinic-microservices
Now that the Spring Cloud Petclinic has its own repo, we could close this question.

@dsyer any comments and suggestions are certainly welcome :) I think after some time I will refresh microservices branch from this master (for example get rid of a thin service layer).


ship locators

When we update the secrets for the pallet, this should ship the locators.
I don't know if this is using the change detection table but for one of the crates it should be.
I'll have to look back at your pr to add it otherwise let me know what you find when you review this.
Thanks!

secrets are updated on 🚜


Separate light client and relayer concerns

The current implementation of the relayer has quite a few mechanisms that could potentially be provided by the light client, for example header verification logic, notes about header verification with secondaries, store of headers, etc. We should clearly understand and define light client and relayer responsibilities and boundaries and what are the interaction points.

Redundant with #60 and #90


Duplicate members entries for Tier/Role

While investigating the results of the migration from https://github.com/opencollective/opencollective-api/pull/3060, I found that we have a lot of duplicated members that are not induced by this migration. The CONTRIBUTOR role (submit expense) seems to be the most affected by this.
SQL query to get duplicate members:
SELECT "MemberCollectiveId", "CollectiveId", "TierId", "role", COUNT(m.id)
FROM "Members" m
WHERE m."deletedAt" IS NULL
GROUP BY "MemberCollectiveId", "CollectiveId", "TierId", "role"
HAVING count(m.id) > 1

Expected behavior
There should be only one raw per group of:

"MemberCollectiveId", "CollectiveId", "TierId", "role"

Todo

[ ] Investigate on the source of the duplication to see if we're checking the existence of members correctly. editCollective may be to check first, as the Contributor are created from there
[ ] Create a migration to remove duplicate memberships. Keep the oldest one by default.

https://github.com/opencollective/opencollective-api/blob/fix/guest-collective/server/graphql/v1/mutations/expenses.js#L497 seems to be the origin of this issue - at least for the CONTRIBUTOR role. We're not checking if a member exists before creating a new one. As a result, https://opencollective.com/maureen-wilson has more than 200 member entries for https://opencollective.com/carlislechp
Duplicates for the ATTENDEE role seems to come from https://github.com/opencollective/opencollective-api/blob/fix/guest-collective/server/graphql/v1/mutations/orders.js#L545, same reason.
After that, we still have some duplicates for the HOST role that we need to understand.

https://github.com/opencollective/opencollective-api/blob/fix/guest-collective/server/graphql/v1/mutations/expenses.js#L497 seems to be the origin of this issue - at least for the CONTRIBUTOR role. We're not checking if a member exists before creating a new one. As a result, https://opencollective.com/maureen-wilson has more than 200 member entries for https://opencollective.com/carlislechp
Duplicates for the ATTENDEE role seems to come from https://github.com/opencollective/opencollective-api/blob/fix/guest-collective/server/graphql/v1/mutations/orders.js#L545, same reason.
After that, we still have some duplicates for the HOST role that we need to understand.

b82cb45 (#5424) should resolve the root cause


Missing file target/nrf52.cfg

I'm trying to flash PineTime from Raspberry Pi according to README.md, now I'm at step 8) Flash the bootloader. I know there is flash protection, so I'm trying to run script/nrf52-pi/flash-unprotect.sh at first and later flash-boot.sh but there is an error:
pi@raspberrypi:~/pinetime-rust-mynewt $ ./scripts/nrf52-pi/flash-boot.sh
+ openocd/bin/openocd -f scripts/nrf52-pi/swd-pi.ocd -f scripts/nrf52/flash-boot.ocd
Open On-Chip Debugger 0.10.0+dev-01130-g9d1b46f5 (2020-07-19-22:23)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'swd'
scripts/nrf52-pi/swd-pi.ocd:13: Error: Can't find target/nrf52.cfg
in procedure 'script'
at file "embedded:startup.tcl", line 26
at file "scripts/nrf52-pi/swd-pi.ocd", line 13

The target folder is stored in parent folder and its subfolders - not ~/pinetime-rust-mynewt/target/ but ~/openocd-spi/tcl/target/ - so find command can't look it up.

Hmmm we seem to be missing some steps... Perhaps you can refer to the latest instructions here:
https://lupyuen.github.io/pinetime-rust-mynewt/articles/mcuboot#select-the-openocd-interface-st-link-or-raspberry-pi-spi
There is a file scripts/config.sh that says which OpenOCD script to use.  Fo Pi, the file should contain...
#  Select Raspberry Pi as SWD Programmer
swd_device=scripts/nrf52-pi/swd-pi.ocd

Then the script to flash should be...
scripts/nrf52/flash-boot.sh

Instead of
scripts/nrf52-pi/flash-boot.sh

May I know where you got the instructions? I will have to update that doc. Thanks!

I'm following description on the https://github.com/lupyuen/pinetime-rust-mynewt page. I suppose its text from README.md

I have updated the doc. Thanks!

Closing this issue because pinetime-rust-mynewt has been revamped for educational use.


added tabbar images to the android project

the android demo threw an exception since it was missing the tabbar images

Strange. Thanks!


Rect2 size is negative, this is not supported error regularly toasting

Godot version
4.0 ed395c6b99915809347a87b0d65220c256d6ec3f
System information
Windows 10 64 bits GLES3 GeForce GTX 1060 6GB/PCIe/SSE2
Issue description
When I open about any project, the following error always gets printed and brought up by the toast system:
ERROR: Rect2 size is negative, this is not supported. Use Rect2.abs() to get a Rect2 with a positive size.
   at: Rect2::grow_individual (D:\PROJETS\INFO\GODOT\Engine\godot4_fork\core/math/rect2.h:243)

It even appears to be caused by the toast system itself when errors show up, but I'm not certain yet.
It occurs again when other errors get toasted, but I'm not sure what reproduces these. But so far I got it everytime when opening projects.
Steps to reproduce
Open any project
Minimal reproduction project
No response

Probably a regression from https://github.com/godotengine/godot/pull/37626

This happens because a StyleBox is drawn starting from a very thin rectangle:

Which is grown negatively and becomes a null-area rectangle:

And keeps being grown negatively afterward in the same function, making negative sizes appear:

Then the next call to grow_individual, which does start with a check for negative size, highlights the problem.
So ironically, the function that checks for this invalid state, allows such invalid state to occur.

If I try forcing grow_individual to never produce a negative-size rectangle (using the second snippet), this happens

I just tried the first snippet, seemed to work fine.
I then tried the second snippet, and Godot turned flat:


Build homepage

This may require some Django work by myself, to expose database information to the template, but I imagine the homepage will contain almost entirely static content.
Follows https://github.com/openstates/new-openstates.org/issues/45, where we determine what the content is, exactly.

Right now I have homepage as a extends of the base template. Especially if the homepage is particularly bespoke, this may not be the right decision.


Create Livestream Camera Subsystem.md

How would you like us to connect the camera without connecting it to a microcontroller? Through research, we've seen that we can use transmitters or potentially use wifi for live-streaming. Is it possible for us to use a camera that pairs with the raspberry pi or Arduino for live streaming?

How would you like us to connect the camera without connecting it to a microcontroller? Through research, we've seen that we can use transmitters or potentially use wifi for live-streaming. Is it possible for us to use a camera that pairs with the raspberry pi or Arduino for live streaming?

To obtain data from the camera and access the live stream, we utilize a mobile hotspot. By using the camera app on our phone, we can establish a connection between the app and the camera through the mobile hotspot. (We are not using the place's WIFI)


Naming disadvantages

Hi @blazeeboy ,
thank you for this interesting project!
I'm afraid of possible collisions with the new remacs port https://github.com/Wilfred/remacs by @Wilfred.
What do you think?

Oh yes that is correct, thanks for the heads up, I'm afraid I have to rename this project, better now than later.
Any suggestions for a name?

Don't know :) Rubymacs? Rumacs? Racs? EmacsR? Rove?
There're plenty of other ErsatzEmacs implementations...


[warn]: @param tag has unknown parameter name: move on C method

I have the follow C method in a Ruby C extension
/*
 * call-seq: initialize(move) -> IllegalMoveError
 *
 * Create a new instance of {IllegalMoveError}.
 * @param [String] move the illegal move.
 */
VALUE
illegal_move_error_initialize (VALUE class, VALUE move) {
  ...
}

When I run the command rake yard I get:
pyroblast:chess pioz$ rake yard
[warn]: @param tag has unknown parameter name: move
    in file `ext/chess.c' near line 38

The doc is correct, but how can I avoid this warning? I've try to use @!method but nothing change.
Environment details:

OS: OSX 10.12.6
Ruby version (ruby -v): ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin16]
YARD version (yard -v): yard 0.9.9

I have read the Contributing Guide.

Unfortunately you can't mix RDoc call-seq signature syntaxes alongside YARD tags. The solution here is to use full YARD syntax with @overload:
/*
 * @overload initialize(move)
 *   Create a new instance.
 *   @param [String] move the illegal move.
 */
VALUE
illegal_move_error_initialize (VALUE class, VALUE move) {
}

Ok, it seems more a workaround than a solution, but it works!
Thank you very much for your help!


feat: [UIE-8136] - IAM RBAC: add new users table component (part 1)

Description 📝
IAM RBAC - users table component.
Adds the component itself, which is a copy of an existing one in the Account, with some adjustments.
Second PR (part 2) will include the table for proxy users and the logic for deleting and filtering them.
Changes  🔄

new users table

Target release date 🗓
Dec 10, 2024 (dev)
Preview 📷
Include a screenshot or screen recording of the change.
:lock: Use the Mask Sensitive Data setting for security.
:bulb: Use <video src="" /> tag when including recordings in table.

Before
After

📷

 Author Checklists
As an Author, to speed up the review process, I considered 🤔
👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿  Providing accessibility support

[x] I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

[x] All unit tests are passing
[x] TypeScript compilation succeeded without errors
[x] Code passes all linting rules

thanks for the review, @mjac0bs!
sure, I won't remove this section with how to test in the future. In addition, I've fixed the linting warnings in my changes.


Update the roll-out section

@abchatra we have github in all editors now, right?

Probably chibi doesn't have it.


Render TODO as annotation

@opoudjis It sounds correct to render them annotations. However, in HTML can we have a way to display them inline?

As an interim solution because https://github.com/riboseinc/isodoc-style/issues/3 isn't getting done, or as a long-term solution?

I think the key point here is to embed the TODOs in the XML as semantic elements.
https://github.com/riboseinc/isodoc-style/issues/3 relates to the HTML output of these annotations?

Yes

TODO statements are not in fact natively recognised by Asciidoctor, even though my syntax highlighter does. Forcing Asciidoctor to recognise them seems not a good use of time, will review whether there is precedent for them being used in Asciidoctor at all.

No support currently in Asciidoctor for TODO blocks as a kind of distinct admonition: https://github.com/asciidoctor/asciidoctor/issues/1692
Since they are not natively part of Asciidoctor, I have to ask whether we should support them at all. I can grab any paragraph which starts with TODO: and treat it as a reviewer comment; I'm just not convinced I should. @ronaldtse?

We don't quite care about sticking to "Asciidoctor syntax"; it's just a parser to us. It would be great if we can parse those as comments.

Implemented. They are being rendered as reviewer comments; https://github.com/riboseinc/isodoc-style/issues/3 will need to be implemented for them to be displayed in HTML. But reviewer comment, not straight comments, are the right way to process these.


Improve the install generator to handle two- and three-tier database.yml config files

Resolves #204
@dhh: I'm not claiming this code is lovely, but I wanted to get a working implementation done quickly so that we can iterate on the code itself. Here are the key details:

load the YAML into a Ruby hash, resolving aliases, to get a clear picture of the configuration without resorting to weird string checks
work with the entire environment definition block so that find and replace can handle comments and additional config values seamlessly
have a fallback if we can't make sense of the file (I just append a comment with the contents that the user needs to integrate into the config file)
works with whatever indention the user currently has (tabs or spaces)
distinguishes between two and three tier configurations based on the present (or not) of the primary key in the configuration hash

I worked with a number of example database.yml files while testing the basic logic myself. Happy to add some test cases for any states you want to cover. If I were to lay out the basic matrix, it would be

sqlite vs other
2-tier vs 3-tier
cache db not present vs cache db already present

Your tests cover

sqlite, 2-tier, cache db not present
other, 3-tier, cache db already present

I can add any combinations you think are highest value.

Will review. But starting to think that maybe we should just have the installer spit out a "add this to production:" if the default file is anything but vanilla, and then folks can just add it themselves. Definitely a drawback of using configuration files that are meant for human editing!

In fact, maybe the right option here is actually to do the solid preconfiguration straight in Rails, so that delivers both the out of the box configuration and enables us to use db:system:change without problems. Then the installer can simply ask the user to add this block themselves when run directly.

I think that would prove much simpler in the long run. As you can see, mutating the database.yml file is just a deep problem space.
And given that Rails will own app generation and know whether Solid Cache/Queue is to be included, it can just spit out the appropriate database.yml. And this installer, as you said, becomes much dumber and just provides instructions on how to setup the database, if this installer is run independently of generating a Rails app.

Solved this via https://github.com/rails/rails/pull/52790/commits/cae25f3c2e5c7d09f90fceefd448ad8d819028f1 and https://github.com/rails/solid_cache/commit/0a36decd3e59c3cfab6efe67e42ba8bc910a7ed2. Appreciate you looking into this other approach! ✌

Excellent. Both look great.


refactor: split into multiple packages/modules

Checklist

[x] Ensure PR title matches the conventional commits format.

CodiumAI Agent Commands
As required run the following CodiumAI Agent commands:

Request PR review using @CodiumAI-Agent /review (and if required, request an incremental update with @CodiumAI-Agent /review -i)
Request PR improvement suggestions with @CodiumAI-Agent /improve --extended
Request PR update using @CodiumAI-Agent /describe

@CodiumAI-Agent /review

PR Analysis

🎯 Main theme: Refactoring the codebase for better modularity
📝 PR summary: This PR focuses on refactoring the codebase by splitting the existing code into multiple packages/modules. The TaskItem class and safe_get function have been moved to separate modules. The get_asana_task function has also been moved to a new module.
📌 Type of PR: Refactoring
🧪 Relevant tests added: Yes
🔒 Security concerns: No security concerns found

PR Feedback

💡 General suggestions: The PR is well-structured and the refactoring improves the modularity of the codebase. The code is cleaner and easier to maintain with the separation of concerns. Good job on moving the TaskItem class and safe_get function to their own modules. This makes the code easier to understand and test.

 🤖 Code feedback:

relevant file: ado_asana_sync/sync/asana.py
suggestion: Consider handling the ApiException in a more user-friendly way. Instead of just logging the error, you could re-raise a custom exception with a more descriptive message. This would make it easier for callers of the function to handle the error appropriately. [important]
relevant line: '+        _LOGGER.error("Exception when calling TasksApi->get_task: %s\n", e)'

relevant file: ado_asana_sync/sync/task_item.py
suggestion: The is_current method could be optimized by returning False immediately after finding a mismatch, instead of checking both conditions every time. [medium]
relevant line: '+        if (ado_task.rev != self.ado_rev or iso8601_utc(asana_task.modified_at) != self.asana_updated):'

relevant file: ado_asana_sync/utils/utils.py
suggestion: The safe_get function could be improved by adding type hints for the parameters. This would make the function signature more informative and help with code autocompletion in IDEs. [medium]
relevant line: '+def safe_get(obj, *attrs_keys):'

relevant file: tests/utils/test_utils.py
suggestion: Consider adding more test cases for the safe_get function, such as testing with an empty dictionary or an object without any attributes. This would help ensure the function behaves correctly in all scenarios. [medium]
relevant line: '+class TestSafeGet(unittest.TestCase):'

How to use

Tag me in a comment '@CodiumAI-Agent' and add one of the following commands:
/review [-i]: Request a review of your Pull Request. For an incremental review, which only considers changes since the last review, include the '-i' option.
/describe: Modify the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest improvements to the code in the PR. Extended mode employs several calls, and provides a more thorough feedback.
/ask <QUESTION>: Pose a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.

To edit any configuration parameter from configuration.toml, add --config_path=new_value
For example: /review --pr_reviewer.extra_instructions="focus on the file: ..."
To list the possible configuration parameters, use the /config command.

@CodiumAI-Agent /review -i

Incremental PR Review

⏮ Review for commits since previous PR-Agent review: Starting from commit https://github.com/danstis/ado-asana-sync/pull/127/commits/5d1f0a343b69c525e58d96b07b5d7ca39c0df38c

PR Analysis

🎯 Main theme: Refactoring and bug fixing of the codebase by splitting into multiple packages/modules.
📝 PR summary: This PR focuses on refactoring the codebase by splitting it into multiple packages/modules. It also includes some bug fixes and improvements, such as renaming variables for better readability, improving error handling, and updating function signatures for better clarity.
📌 Type of PR: Refactoring
🧪 Relevant tests added: No
🔒 Security concerns: No security concerns found

PR Feedback

💡 General suggestions: The PR has done a good job in refactoring the codebase into multiple packages/modules, which enhances the modularity and readability of the code. The renaming of variables and updating of function signatures also improve the clarity of the code. However, it would be beneficial to include unit tests to ensure the correctness of the code after refactoring.

 🤖 Code feedback:

relevant file: ado_asana_sync/sync/task_item.py
suggestion: Consider using more descriptive variable names. For instance, instead of using 'app' as a parameter name, a more descriptive name like 'application' could improve code readability. [medium]
relevant line: def find_by_ado_id(cls, app: App, ado_id: int) -> TaskItem | None:

relevant file: ado_asana_sync/sync/asana.py
suggestion: It's a good practice to handle exceptions as specifically as possible. Instead of catching a general ApiException, consider catching specific exceptions that you expect might be thrown in the try block. This can help in debugging and also prevent catching unexpected exceptions that might hide bugs. [medium]
relevant line: except ApiException as exception:

relevant file: ado_asana_sync/sync/sync.py
suggestion: It's recommended to avoid using 'None' as a return value from functions. This can lead to potential issues and make the code harder to understand. Consider using exceptions or error codes to indicate errors. [medium]
relevant line: def get_asana_workspace(app: App, name) -> str | None:

relevant file: ado_asana_sync/sync/sync.py
suggestion: It's a good practice to avoid using 'None' as a return value from functions. This can lead to potential issues and make the code harder to understand. Consider using exceptions or error codes to indicate errors. [medium]
relevant line: def get_asana_project(app: App, workspace_gid, name) -> str | None:

How to use

Tag me in a comment '@CodiumAI-Agent' and add one of the following commands:
/review [-i]: Request a review of your Pull Request. For an incremental review, which only considers changes since the last review, include the '-i' option.
/describe: Modify the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest improvements to the code in the PR. Extended mode employs several calls, and provides a more thorough feedback.
/ask <QUESTION>: Pose a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.

To edit any configuration parameter from configuration.toml, add --config_path=new_value
For example: /review --pr_reviewer.extra_instructions="focus on the file: ..."
To list the possible configuration parameters, use the /config command.

@CodiumAI-Agent /improve --extended

How to use PR-Agent

Tag me in a comment '@CodiumAI-Agent' and add one of the following commands:
/review [-i]: Request a review of your Pull Request. For an incremental review, which only considers changes since the last review, include the '-i' option.
/describe: Modify the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest improvements to the code in the PR. Extended mode employs several calls, and provides a more thorough feedback.
/ask <QUESTION>: Pose a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.

To edit any configuration parameter from configuration.toml, add --config_path=new_value
For example: /review --pr_reviewer.extra_instructions="focus on the file: ..."
To list the possible configuration parameters, use the /config command.


Update main.yml

Added Redhat-8 JSON and mdstring PHP packages to support Moodle installations on Redhat systems.

@buluma Awaiting your approval on the workflow. Should be good to go.


wps does not parse exception report when http code is not 200

A WPS service may return an exception message as XML response with HTTP code 500. OWSLib will raise a HTTP connection error but does not parse the WPS exception report:
conda/envs/birdy/lib/python3.6/site-packages/owslib/wps.py in _readFromUrl(self, url, data, method, username, password, headers, verify, cert)
    463             u = openURL(url, data, method='Post',
    464                         username=username, password=password,
--> 465                         headers=headers, verify=verify, cert=cert)
    466             return etree.fromstring(u.read())
    467

~/.conda/envs/birdy/lib/python3.6/site-packages/owslib/util.py in openURL(url_base, data, method, cookies, username, password, timeout, headers, verify, cert)
    194
    195     if req.status_code in [404, 500, 502, 503, 504]:    # add more if needed
--> 196         req.raise_for_status()
    197
    198     # check for service exceptions without the http header set

~/.conda/envs/birdy/lib/python3.6/site-packages/requests/models.py in raise_for_status(self)
    938
    939         if http_error_msg:
--> 940             raise HTTPError(http_error_msg, response=self)
    941
    942     def close(self):

HTTPError: 500 Server Error: INTERNAL SERVER ERROR for url: http://localhost:5000/wps

I've been getting some 502 errors from OWSLib talking to PyWPS (especially if the process fails about 30 seconds in), maybe related?


”Bruiu”, ”Gherdeal”, ”Șomartin” are listed in the drop-down menu

Description:
When user writes ”Bruiu”, ”Gherdeal”, ”Șomartin” the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Bruiu"

Expected results
The location appears in the drop-down menu as "Sat Bruiu, SIBIU (Bruiu)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Șomartin"

Expected results
The location appears in the drop-down menu as "Sat Șomartin, SIBIU (Bruiu)".