Android local engine profile build fails: AOT snapshotter exited with code 254

description
Running with a local engine and debug build works fine, when trying to use a profile build it doesn't though.  Usually this sort of error is caused when the host and device builds don't match.  I verified that they both have been built.  Another explanation is using an old version of the framework with a new version of the engine, I'm using the version of the engine specified in the engine.version file.
steps to reproduce
flutter --local-engine=android_profile_arm64 --local-engine-host=host_profile_arm64 --local-engine-src-path=/Users/aaclarke/dev/engine/src/ build apk --profile -v

doctor
[!] Flutter (Channel [user-branch], 3.24.0-1.0.pre.424, on macOS 14.5 23F79 darwin-arm64, locale en)
    ! Flutter version 3.24.0-1.0.pre.424 on channel [user-branch] at /Users/aaclarke/dev/flutter
      Currently on an unknown channel. Run `flutter channel` to switch to an official channel.
      If that doesn't fix the issue, reinstall Flutter by following instructions at https://flutter.dev/setup.
    ! Upstream repository unknown source is not a standard remote.
      Set environment variable "FLUTTER_GIT_URL" to unknown source to dismiss this error.
    • Framework revision d6e4555494 (2 hours ago), 2024-08-03 02:46:24 +0530
    • Engine revision 353c6b237b
    • Dart version 3.6.0 (build 3.6.0-109.0.dev)
    • DevTools version 2.38.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

error
[+4294 ms] [+6024 ms] kernel_snapshot_program: Complete
[ +800 ms] [ +783 ms] native_assets: Starting due to {}
[        ] [  +11 ms] No packages with native assets. Skipping native assets compilation.
[        ] [        ] Writing native_assets.yaml.
[        ] [   +6 ms] Writing /Users/aaclarke/dev/flutter/dev/benchmarks/macrobenchmarks/.dart_tool/flutter_build/d318029ee6cde7e2a98e27d5a4120296/native_assets.yaml
done.
[        ] [        ] native_assets: Complete
[        ] [        ] kernel_snapshot_native_assets: Starting due to {InvalidatedReasonKind.inputChanged: The following inputs have updated contents:
/Users/aaclarke/dev/flutter/dev/benchmarks/macrobenchmarks/.dart_tool/flutter_build/d318029ee6cde7e2a98e27d5a4120296/native_assets.yaml,/Users/aaclarke/dev/flutter/dev/
benchmarks/macrobenchmarks/.dart_tool/package_config_subset,/Users/aaclarke/dev/flutter/packages/flutter_tools/lib/src/build_system/targets/common.dart,/Users/aaclarke/
dev/engine/src/out/android_profile_arm64/flutter_patched_sdk/platform_strong.dill,/Users/aaclarke/dev/engine/src/out/host_profile_arm64/dart-sdk/bin/dart,/Users/aaclark
e/dev/engine/src/out/host_profile_arm64/dart-sdk/bin/dartaotruntime,/Users/aaclarke/dev/engine/src/out/host_profile_arm64/dart-sdk/bin/snapshots/frontend_server_aot.dar
t.snapshot}
[        ] [        ] kernel_snapshot_native_assets: Complete
[        ] [        ] kernel_snapshot: Starting due to {InvalidatedReasonKind.inputChanged: The following inputs have updated contents:
/Users/aaclarke/dev/flutter/dev/benchmarks/macrobenchmarks/.dart_tool/flutter_build/d318029ee6cde7e2a98e27d5a4120296/program.dill,/Users/aaclarke/dev/flutter/dev/benchm
arks/macrobenchmarks/.dart_tool/flutter_build/d318029ee6cde7e2a98e27d5a4120296/native_assets.dill}
[        ] [   +9 ms] kernel_snapshot: Complete
[        ] [        ] android_aot_profile_android-arm64: Starting due to {}
[        ] [   +1 ms] targetingApplePlatform = false
[        ] [        ] extractAppleDebugSymbols = true
[        ] [        ] Will strip AOT snapshot during build.
[        ] [        ] executing: /Users/aaclarke/dev/engine/src/out/android_profile_arm64/clang_x64/gen_snapshot --deterministic --snapshot_kind=app-aot-elf
--elf=/Users/aaclarke/dev/flutter/dev/benchmarks/macrobenchmarks/.dart_tool/flutter_build/d318029ee6cde7e2a98e27d5a4120296/arm64-v8a/app.so --strip
/Users/aaclarke/dev/flutter/dev/benchmarks/macrobenchmarks/.dart_tool/flutter_build/d318029ee6cde7e2a98e27d5a4120296/app.dill
[        ] [        ] aot_android_asset_bundle: Starting due to {}
[ +100 ms] [ +127 ms] shaderc command: [/Users/aaclarke/dev/engine/src/out/host_profile_arm64/impellerc, --sksl, --runtime-stage-gles, --runtime-stage-vulkan, --iplr,
--sl=/Users/aaclarke/dev/flutter/dev/benchmarks/macrobenchmarks/build/app/intermediates/flutter/profile/flutter_assets/shaders/ink_sparkle.frag,
--spirv=/Users/aaclarke/dev/flutter/dev/benchmarks/macrobenchmarks/build/app/intermediates/flutter/profile/flutter_assets/shaders/ink_sparkle.frag.spirv,
--input=/Users/aaclarke/dev/flutter/packages/flutter/lib/src/material/shaders/ink_sparkle.frag, --input-type=frag,
--include=/Users/aaclarke/dev/flutter/packages/flutter/lib/src/material/shaders, --include=/Users/aaclarke/dev/engine/src/out/host_profile_arm64/shader_lib]
[  +99 ms] [  +33 ms] Can't load Kernel binary: Invalid kernel binary format version.
[   +2 ms] [   +1 ms] Dart snapshot generator failed with exit code 254
[        ] [   +3 ms] Running command: /Users/aaclarke/dev/engine/src/out/host_profile_arm64/dart-sdk/bin/dart --disable-dart-dev
/Users/aaclarke/dev/engine/src/out/host_profile_arm64/gen/const_finder.dart.snapshot --kernel-file
/Users/aaclarke/dev/flutter/dev/benchmarks/macrobenchmarks/.dart_tool/flutter_build/d318029ee6cde7e2a98e27d5a4120296/app.dill --class-library-uri
package:flutter/src/widgets/icon_data.dart --class-name IconData --annotation-class-name _StaticIconProvider --annotation-class-library-uri
package:flutter/src/widgets/icon_data.dart
[ +793 ms] [ +858 ms] Running font-subset: /Users/aaclarke/dev/engine/src/out/host_profile_arm64/font-subset
/Users/aaclarke/dev/flutter/dev/benchmarks/macrobenchmarks/build/app/intermediates/flutter/profile/flutter_assets/fonts/MaterialIcons-Regular.otf
/Users/aaclarke/dev/flutter/bin/cache/artifacts/material_fonts/MaterialIcons-Regular.otf, using codepoints 57490 62832 57706 58332 58727 58372 984246
[ +202 ms] [ +221 ms] Font asset "MaterialIcons-Regular.otf" was tree-shaken, reducing it from 1645184 to 1676 bytes (99.9% reduction). Tree-shaking can be disabled by
providing the --no-tree-shake-icons flag when building your app.
[        ] [   +4 ms] aot_android_asset_bundle: Complete
[+1000 ms] [ +946 ms] Persisting file store
[        ] [   +5 ms] Done persisting file store
[        ] [   +6 ms] Target android_aot_profile_android-arm64 failed: Exception: AOT snapshotter exited with code 254
[        ]            #0      AndroidAot.build (package:flutter_tools/src/build_system/targets/android.dart:253:7)
[        ]            <asynchronous suspension>
[        ]            #1      _BuildInstance._invokeInternal (package:flutter_tools/src/build_system/build_system.dart:875:9)
[        ]            <asynchronous suspension>
[        ]            #2      Future.wait.<anonymous closure> (dart:async/future.dart:534:21)
[        ]            <asynchronous suspension>
[        ]            #3      _BuildInstance.invokeTarget (package:flutter_tools/src/build_system/build_system.dart:813:32)
[        ]            <asynchronous suspension>
[        ]            #4      FlutterBuildSystem.build (package:flutter_tools/src/build_system/build_system.dart:635:16)
[        ]            <asynchronous suspension>
[        ]            #5      AssembleCommand.runCommand (package:flutter_tools/src/commands/assemble.dart:328:32)
[        ]            <asynchronous suspension>
[        ]            #6      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1408:27)
[        ]            <asynchronous suspension>
[        ]            #7      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
[        ]            <asynchronous suspension>
[        ]            #8      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
[        ]            <asynchronous suspension>
[        ]            #9      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:421:9)
[        ]            <asynchronous suspension>
[        ]            #10     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
[        ]            <asynchronous suspension>
[        ]            #11     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:364:5)
[        ]            <asynchronous suspension>
[        ]            #12     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:130:9)
[        ]            <asynchronous suspension>
[        ]            #13     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
[        ]            <asynchronous suspension>
[        ]            #14     main (package:flutter_tools/executable.dart:93:3)
[        ]            <asynchronous suspension>
[        ] [   +1 ms]
[        ]            #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
[        ]            #1      AssembleCommand.runCommand (package:flutter_tools/src/commands/assemble.dart:345:7)
[        ]            <asynchronous suspension>
[        ]            #2      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1408:27)
[        ]            <asynchronous suspension>
[        ]            #3      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
[        ]            <asynchronous suspension>
[        ]            #4      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
[        ]            <asynchronous suspension>
[        ]            #5      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:421:9)
[        ]            <asynchronous suspension>
[        ]            #6      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
[        ]            <asynchronous suspension>
[        ]            #7      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:364:5)
[        ]            <asynchronous suspension>
[        ]            #8      run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:130:9)
[        ]            <asynchronous suspension>
[        ]            #9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
[        ]            <asynchronous suspension>
[        ]            #10     main (package:flutter_tools/executable.dart:93:3)
[        ]            <asynchronous suspension>
[        ] FAILURE: Build failed with an exception.
[        ] * What went wrong:
[        ] Execution failed for task ':app:compileFlutterBuildProfile'.
[        ] > Process 'command '/Users/aaclarke/dev/flutter/bin/flutter'' finished with non-zero exit value 1
[        ] * Try:
[        ] > Run with --debug option to get more log output.
[        ] > Run with --scan to get full insights.
[        ] > Get more help at https://help.gradle.org.
[        ] * Exception is:
[        ] org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':app:compileFlutterBuildProfile'.
[        ] 	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$1(ExecuteActionsTaskExecuter.java:130)
[        ] 	at org.gradle.internal.Try$Failure.ifSuccessfulOrElse(Try.java:293)
[        ] 	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:128)
[        ] 	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:116)
[        ] 	at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
[        ] 	at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:51)
[        ] 	at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
[        ] 	at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:74)
[        ] 	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.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:209)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:166)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
[        ] 	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
[        ] 	at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:42)
[        ] 	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:331)
[        ] 	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:318)
[        ] 	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.lambda$execute$0(DefaultTaskExecutionGraph.java:314)
[        ] 	at org.gradle.internal.operations.CurrentBuildOperationRef.with(CurrentBuildOperationRef.java:85)
[        ] 	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:314)
[        ] 	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:303)
[        ] 	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:459)
[        ] 	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:376)
[        ] 	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
[        ] 	at org.gradle.internal.concurrent.AbstractManagedExecutor$1.run(AbstractManagedExecutor.java:48)
[        ] 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
[        ] 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
[        ] 	at java.base/java.lang.Thread.run(Unknown Source)
[        ] Caused by: org.gradle.process.internal.ExecException: Process 'command '/Users/aaclarke/dev/flutter/bin/flutter'' finished with non-zero exit value 1
[        ] 	at org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:442)
[        ] 	at org.gradle.process.internal.DefaultExecAction.execute(DefaultExecAction.java:38)
[        ] 	at org.gradle.process.internal.DefaultExecActionFactory.exec(DefaultExecActionFactory.java:202)
[        ] 	at org.gradle.api.internal.project.DefaultProject.exec(DefaultProject.java:1196)
[        ] 	at org.gradle.api.internal.project.DefaultProject.exec(DefaultProject.java:1191)
[        ] 	at org.gradle.api.Project$exec$8.call(Unknown Source)
[        ] 	at BaseFlutterTask.buildBundle(flutter.groovy:1687)
[        ] 	at BaseFlutterTask$buildBundle.callCurrent(Unknown Source)
[        ] 	at FlutterTask.build(flutter.groovy:1825)
[        ] 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[        ] 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
[        ] 	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
[        ] 	at java.base/java.lang.reflect.Method.invoke(Unknown Source)
[        ] 	at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:125)
[        ] 	at org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:58)
[        ] 	at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:51)
[        ] 	at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:29)
[        ] 	at org.gradle.api.internal.tasks.execution.TaskExecution$3.run(TaskExecution.java:244)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:166)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:47)
[        ] 	at org.gradle.api.internal.tasks.execution.TaskExecution.executeAction(TaskExecution.java:229)
[        ] 	at org.gradle.api.internal.tasks.execution.TaskExecution.executeActions(TaskExecution.java:212)
[        ] 	at org.gradle.api.internal.tasks.execution.TaskExecution.executeWithPreviousOutputFiles(TaskExecution.java:195)
[        ] 	at org.gradle.api.internal.tasks.execution.TaskExecution.execute(TaskExecution.java:162)
[        ] 	at org.gradle.internal.execution.steps.ExecuteStep.executeInternal(ExecuteStep.java:105)
[        ] 	at org.gradle.internal.execution.steps.ExecuteStep.access$000(ExecuteStep.java:44)
[        ] 	at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:59)
[        ] 	at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:56)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:209)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:166)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
[        ] 	at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:56)
[        ] 	at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:44)
[        ] 	at org.gradle.internal.execution.steps.CancelExecutionStep.execute(CancelExecutionStep.java:42)
[        ] 	at org.gradle.internal.execution.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:75)
[        ] 	at org.gradle.internal.execution.steps.TimeoutStep.execute(TimeoutStep.java:55)
[        ] 	at org.gradle.internal.execution.steps.PreCreateOutputParentsStep.execute(PreCreateOutputParentsStep.java:50)
[        ] 	at org.gradle.internal.execution.steps.PreCreateOutputParentsStep.execute(PreCreateOutputParentsStep.java:28)
[        ] 	at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:67)
[        ] 	at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:37)
[        ] 	at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:61)
[        ] 	at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:26)
[        ] 	at org.gradle.internal.execution.steps.CaptureOutputsAfterExecutionStep.execute(CaptureOutputsAfterExecutionStep.java:69)
[        ] 	at org.gradle.internal.execution.steps.CaptureOutputsAfterExecutionStep.execute(CaptureOutputsAfterExecutionStep.java:46)
[        ] 	at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:40)
[        ] 	at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:29)
[        ] 	at org.gradle.internal.execution.steps.BuildCacheStep.executeWithoutCache(BuildCacheStep.java:189)
[        ] 	at org.gradle.internal.execution.steps.BuildCacheStep.lambda$execute$1(BuildCacheStep.java:75)
[        ] 	at org.gradle.internal.Either$Right.fold(Either.java:175)
[        ] 	at org.gradle.internal.execution.caching.CachingState.fold(CachingState.java:62)
[        ] 	at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:73)
[        ] 	at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:48)
[        ] 	at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:46)
[        ] 	at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:35)
[        ] 	at org.gradle.internal.execution.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:75)
[        ] 	at org.gradle.internal.execution.steps.SkipUpToDateStep.lambda$execute$2(SkipUpToDateStep.java:53)
[        ] 	at java.base/java.util.Optional.orElseGet(Unknown Source)
[        ] 	at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:53)
[        ] 	at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:35)
[        ] 	at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:37)
[        ] 	at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:27)
[        ] 	at org.gradle.internal.execution.steps.ResolveIncrementalCachingStateStep.executeDelegate(ResolveIncrementalCachingStateStep.java:49)
[        ] 	at org.gradle.internal.execution.steps.ResolveIncrementalCachingStateStep.executeDelegate(ResolveIncrementalCachingStateStep.java:27)
[        ] 	at org.gradle.internal.execution.steps.AbstractResolveCachingStateStep.execute(AbstractResolveCachingStateStep.java:71)
[        ] 	at org.gradle.internal.execution.steps.AbstractResolveCachingStateStep.execute(AbstractResolveCachingStateStep.java:39)
[        ] 	at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:65)
[        ] 	at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:36)
[        ] 	at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:105)
[        ] 	at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:54)
[        ] 	at org.gradle.internal.execution.steps.AbstractCaptureStateBeforeExecutionStep.execute(AbstractCaptureStateBeforeExecutionStep.java:64)
[        ] 	at org.gradle.internal.execution.steps.AbstractCaptureStateBeforeExecutionStep.execute(AbstractCaptureStateBeforeExecutionStep.java:43)
[        ] 	at org.gradle.internal.execution.steps.AbstractSkipEmptyWorkStep.executeWithNonEmptySources(AbstractSkipEmptyWorkStep.java:125)
[        ] 	at org.gradle.internal.execution.steps.AbstractSkipEmptyWorkStep.execute(AbstractSkipEmptyWorkStep.java:56)
[        ] 	at org.gradle.internal.execution.steps.AbstractSkipEmptyWorkStep.execute(AbstractSkipEmptyWorkStep.java:36)
[        ] 	at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsStartedStep.execute(MarkSnapshottingInputsStartedStep.java:38)
[        ] 	at org.gradle.internal.execution.steps.LoadPreviousExecutionStateStep.execute(LoadPreviousExecutionStateStep.java:36)
[        ] 	at org.gradle.internal.execution.steps.LoadPreviousExecutionStateStep.execute(LoadPreviousExecutionStateStep.java:23)
[        ] 	at org.gradle.internal.execution.steps.HandleStaleOutputsStep.execute(HandleStaleOutputsStep.java:75)
[        ] 	at org.gradle.internal.execution.steps.HandleStaleOutputsStep.execute(HandleStaleOutputsStep.java:41)
[        ] 	at org.gradle.internal.execution.steps.AssignMutableWorkspaceStep.lambda$execute$0(AssignMutableWorkspaceStep.java:35)
[        ] 	at org.gradle.api.internal.tasks.execution.TaskExecution$4.withWorkspace(TaskExecution.java:289)
[        ] 	at org.gradle.internal.execution.steps.AssignMutableWorkspaceStep.execute(AssignMutableWorkspaceStep.java:31)
[        ] 	at org.gradle.internal.execution.steps.AssignMutableWorkspaceStep.execute(AssignMutableWorkspaceStep.java:22)
[        ] 	at org.gradle.internal.execution.steps.ChoosePipelineStep.execute(ChoosePipelineStep.java:40)
[        ] 	at org.gradle.internal.execution.steps.ChoosePipelineStep.execute(ChoosePipelineStep.java:23)
[        ] 	at org.gradle.internal.execution.steps.ExecuteWorkBuildOperationFiringStep.lambda$execute$2(ExecuteWorkBuildOperationFiringStep.java:67)
[        ] 	at java.base/java.util.Optional.orElseGet(Unknown Source)
[        ] 	at org.gradle.internal.execution.steps.ExecuteWorkBuildOperationFiringStep.execute(ExecuteWorkBuildOperationFiringStep.java:67)
[        ] 	at org.gradle.internal.execution.steps.ExecuteWorkBuildOperationFiringStep.execute(ExecuteWorkBuildOperationFiringStep.java:39)
[        ] 	at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:46)
[        ] 	at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:34)
[        ] 	at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:48)
[        ] 	at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:35)
[        ] 	at org.gradle.internal.execution.impl.DefaultExecutionEngine$1.execute(DefaultExecutionEngine.java:61)
[        ] 	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:127)
[        ] 	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:116)
[        ] 	at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
[        ] 	at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:51)
[        ] 	at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
[        ] 	at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:74)
[        ] 	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.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:209)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:166)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
[        ] 	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
[        ] 	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
[        ] 	at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:42)
[        ] 	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:331)
[        ] 	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:318)
[        ] 	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.lambda$execute$0(DefaultTaskExecutionGraph.java:314)
[        ] 	at org.gradle.internal.operations.CurrentBuildOperationRef.with(CurrentBuildOperationRef.java:85)
[        ] 	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:314)
[        ] 	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:303)
[        ] 	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:459)
[        ] 	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:376)
[        ] 	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
[        ] 	at org.gradle.internal.concurrent.AbstractManagedExecutor$1.run(AbstractManagedExecutor.java:48)
[        ] 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
[        ] 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
[        ] 	at java.base/java.lang.Thread.run(Unknown Source)
[        ] BUILD FAILED in 9s
[        ] [   +5 ms] "flutter assemble" took 9,189ms.
[        ] [        ] ensureAnalyticsSent: 0ms
[        ] [        ] Running 1 shutdown hook
[        ] [        ] Shutdown hooks complete
[        ] [        ] exiting with code 1
[        ] > Task :app:compileFlutterBuildProfile FAILED
[        ] Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
[        ] You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
[        ] For more on this, please refer to https://docs.gradle.org/8.9/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
[        ] 6 actionable tasks: 1 executed, 5 up-to-date
[        ] Watched directory hierarchies: [/Users/aaclarke/dev/flutter/packages/flutter_tools/gradle,
/Users/aaclarke/dev/flutter/dev/benchmarks/macrobenchmarks/android]
[   +8 ms] Running Gradle task 'assembleProfile'... (completed in 10.0s)
[   +1 ms] "flutter apk" took 10,631ms.
[   +1 ms] Gradle task assembleProfile failed with exit code 1
[        ]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
           #1      AndroidGradleBuilder.buildGradleApp (package:flutter_tools/src/android/gradle.dart:492:9)
           <asynchronous suspension>
           #2      AndroidGradleBuilder.buildApk (package:flutter_tools/src/android/gradle.dart:220:5)
           <asynchronous suspension>
           #3      BuildApkCommand.runCommand (package:flutter_tools/src/commands/build_apk.dart:141:5)
           <asynchronous suspension>
           #4      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1408:27)
           <asynchronous suspension>
           #5      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
           <asynchronous suspension>
           #6      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
           <asynchronous suspension>
           #7      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:421:9)
           <asynchronous suspension>
           #8      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
           <asynchronous suspension>
           #9      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:364:5)
           <asynchronous suspension>
           #10     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:130:9)
           <asynchronous suspension>
           #11     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
           <asynchronous suspension>
           #12     main (package:flutter_tools/executable.dart:93:3)
           <asynchronous suspension>

[        ] ensureAnalyticsSent: 0ms
[        ] Running 2 shutdown hooks
[   +1 ms] Shutdown hooks complete
[        ] exiting with code 1

The error is caused by a version mismatch, most likely between android_profile_arm64 and host_profile_arm64 local engines:
[        ] [        ] executing: /Users/aaclarke/dev/engine/src/out/android_profile_arm64/clang_x64/gen_snapshot --deterministic --snapshot_kind=app-aot-elf
--elf=/Users/aaclarke/dev/flutter/dev/benchmarks/macrobenchmarks/.dart_tool/flutter_build/d318029ee6cde7e2a98e27d5a4120296/arm64-v8a/app.so --strip
/Users/aaclarke/dev/flutter/dev/benchmarks/macrobenchmarks/.dart_tool/flutter_build/d318029ee6cde7e2a98e27d5a4120296/app.dill

...

[  +99 ms] [  +33 ms] Can't load Kernel binary: Invalid kernel binary format version.

This error means that /Users/aaclarke/dev/engine/src/out/android_profile_arm64/clang_x64/gen_snapshot is not compatible with /Users/aaclarke/dev/flutter/dev/benchmarks/macrobenchmarks/.dart_tool/flutter_build/d318029ee6cde7e2a98e27d5a4120296/app.dill which should be built with a host version of the engine (that part of the log was omitted from the issue).
I would suggest doing clean builds of both engine variants from the same sources and running flutter clean before building the app.

I figured it out.  That invocation is the correct one for an x86_64 mac.  On arm64 you need to use the host_profile build, not the host_profile_arm64 build.


fix: Regenerate outdated lockfile

When running npm install in root, I got this error message:

npm ERR! code E401
npm ERR! 401 Unauthorized - GET<EMAIL_ADDRESS>- authentication token not provided

Removing package-lock.json and running npm i again fixes this.

Thank you!


Change PlanBuilder::orderBy to accept ORDER BY SQL clauses

PlanBuilder::orderBy used to require the caller to specify two lists:  indices
of sorting keys and corresponding sort orders. The new API takes a list of
ORDER BY SQL clauses making it easier to use when writing as well as
reading code.
Before: .orderBy({0, 1}, {core::kAscNullsLast, core::kAscNullsLast}, false)
After: .orderBy({"l_returnflag", "l_linestatus"}, false)

FYI, @9prady9


Houdini Shelves Manager: Shelf is not created without specifying shelf set name

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior:
In Houdini, Shelf creation doesn't require a shelf set name.
however Shelves Manager won't create a shelf without adding a shelf set name

Expected Behavior:
Missing Shelf set name shouldn't stop shelf creation.
Version
3.16.4-nightly.2
What platform you are running OpenPype on?
Windows
Steps To Reproduce:

create a shelf by adding tools (like screenshot above)
Launch Houdini and try to find your new shelf
Alternatively, you can check default.shelf contents

Are there any labels you wish to add?

[X] I have added the relevant labels to the bug report.

Relevant log output:
No response
Additional context:
Here's an example script that you can use.
import hou
hou.ui.displayMessage("Hello There!")

If you want to create shelf be adding tools, then you should add a Shelf Set Name to avoid this issue.


sinfo does not show the right amount of server members

@pedall you can close this issue. It's being picked up already here: #1433


Bundle generates duplicate schemas for nested external $ref

Describe the bug
The bundle command creates duplicate schemas depending on how the spec is structured.
To Reproduce
Steps to reproduce the behavior:

Extract bundle-refs.zip, which contains 2 equivalent OpenAPI specs

refs-issue and refs-ok define the same API, but refs-issue uses an external $ref for the /vendor path

Run redocly bundle refs-ok@latest -o dist/refs-ok.yaml

This succeeds with no warnings

Run redocly bundle refs-issue@latest -o dist/refs-issue.yaml

This succeeds with a warning that it created a duplicate vendor-2 schema

Expected behavior
I expected the bundle command to produce the same output for both input specs
Logs

OpenAPI definition

OpenAPI 3.0 (minimal specs to reproduce are included in attached zip file)
Redocly Version(s)
1.0.0-beta.121
Node.js Version(s)

Additional context

I poked around a little and found that changing this line of bundle.ts from:
components = root.components = root.components || {};

to:
components = {};
root.components = root.components || {};

I can successfully bundle both of the example specs attached to this issue.  That's not a good change--it breaks a bunch of other stuff--but it seems like this line is somehow delaying or bypassing the resolution of $refs that are inside root.components.  Is there some way to force resolution of $refs in root.components before walking the rest of the document?

I believe this is related to https://github.com/Redocly/redocly-cli/issues/658 and https://github.com/Redocly/redocly-cli/issues/929


DOM does not update when returning to the previous page

Version
3.0.2
Reproduction link
https://github.com/Ercan93/for-vue3-issue
Steps to reproduce

Add new content About.vue on editor
View About page on browser
Click Home on header
Click browser previous button
See the old content of the About page

What is expected?
When the previous button is clicked in the browser, the updated content of the About page should appear.
What is actually happening?
When the previous button is clicked in the browser, old content of the About page appears.

Gif of steps to reproduce:

Video of steps to reproduce:
https://github.com/Ercan93/for-vue3-issue/blob/main/src/assets/vue3-issue.mp4

I wanna say this is as expected.

@edison1105  Virtual DOM not working with router?

I am not sure. awkward 😆.

It's HMR

This is probably a vue router bug related to HMR with lazy loaded pages bceause they are cached

do i need to open this issue in vue-router/next?


Python language worker (for integration testing) build for the v3.x-dev branch fails

The pipeline that builds the Python language worker for the v3.x-dev branch has been falling since mid-August 2022. Building this component is a prerequisite to build the Core Tools for integration testing. As a result, integration testing for V3 is blocked. For the time being, I will remove the Python language worker from integration testing to unblock the test pass. Once the build is working again, I will add it back.

This error is fixed with the above PR and builds are succeeding now.


Share and embed links on full showcase pages not working

As reported in https://github.com/datahq/datahub-qa/issues/226
Acceptance criteria

[x] I can copy share/embed links from full showcase page

Tasks

[x] identify the source of the bug in showcase-js repo + analysis
[x] implement the fix in showcase-js
[x] implement the route in the frontend
[x] deploy

Analysis
At the first sight, it looked like the problem is with incorrectly generated URLs, e.g., when you visit https://datahub.io/core/finance-vix/v/50, the share link would be https://datahub.io/core/finance-vix/v/50/view/0, however, we want users to be able to share views per specific revision. So the fix should take place in the frontend repo instead of showcase-js repo.
Another thing to consider is which URL would be more readable and clear, compare following 2 options:

https://datahub.io/core/finance-vix/view/0?v=50 - in the params we also can have ?v=latest
https://datahub.io/core/finance-vix/v/50/view/0

The first option is definitely more readable and clear + it's easy to build a URL by hand when you need it. Therefore, we want to implement it.

FIXED - check https://datahub.io/core/finance-vix/v/50


[DOC] Dashboards - Dashboard new site page and content

What do you want to do?

[ ] Request a change to existing documentation
[X] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
Adding new site page related to the TOC restructure; adding new subpage on creating your first dashboard
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.

New content on creating your first dashboard will support the college student contributor initiative

Done. See https://opensearch.org/docs/latest/dashboards/dashboard/index/


No trades found! Try running zenbot backfill...

Is it too soon to try the 4.x branch?
I'd like to make a few tests on the 4.x branch, but I can't run a simulation on it:
no trades found! try running `zenbot backfill gdax.BTC-EUR` first

If I do that, zenbot seems to correctly backfill all the needed data, but then I'm having that error again when I try to launch a simulation.

Have you tried providing the zenbot sim command with date parameters?
zenbot sim --days 7
or
zenbot sim --start <timestamp> --end <timestamp>
where timestamp is in epoch time format.

zenbot sim --days 7 worked, thanks!

@ToX82 : So how does it perform? (like comparing to 3.x)

Well that's an interesting question indeed. And I don't have an answer :)
Anyway, I have ran a simulation on the 4.x versions right now, and these are the results.
I didn't test version 3.x too much honestly so I don't know if this is performing better, but I think that the 3.x version was more aggressive with the trading.
{ days: 7,
  strategy: 'trend_ema',
  sell_stop_pct: 0,
  buy_stop_pct: 0,
  profit_stop_enable_pct: 10,
  profit_stop_pct: 1,
  max_sell_loss_pct: 25,
  max_slippage_pct: 2,
  buy_pct: 99,
  sell_pct: 99,
  markup_pct: 0,
  currency_capital: 1000,
  asset_capital: 0,
  order_adjust_time: 30000,
  rsi_periods: 14,
  end:<PHONE_NUMBER>000,
  start:<PHONE_NUMBER>000,
  stats: false,
  selector: 'gdax.BTC-USD',
  mode: 'sim',
  period: '1h',
  min_periods: 36,
  trend_ema: 34,
  buy_rate: 0,
  sell_rate: 0,
  max_buy_duration: 1,
  max_sell_duration: 1 }
end balance 1083.06 (8.31%)
buy hold 1031.66 (3.17%)
vs. buy hold 4.98%
17 trades over 8 days (avg 2.13 trades/day)

I've tried...
I like the way how it works...
My results are:
{ strategy: 'trend_ema',
sell_stop_pct: 0,
buy_stop_pct: 0,
profit_stop_enable_pct: 10,
profit_stop_pct: 1,
max_sell_loss_pct: 25,
max_slippage_pct: 2,
buy_pct: 99,
sell_pct: 99,
markup_pct: 0,
days: 90,
currency_capital: 1000,
asset_capital: 0,
order_adjust_time: 30000,
rsi_periods: 14,
end:<PHONE_NUMBER>000,
start:<PHONE_NUMBER>000,
stats: false,
selector: 'gdax.BTC-EUR',
mode: 'sim',
period: '1h',
min_periods: 36,
trend_ema: 34,
buy_rate: 0,
sell_rate: 0,
max_buy_duration: 1,
max_sell_duration: 1,
oversold_rsi_periods: 14,
oversold_rsi: 0 }
end balance 1844.12 (84.41%)
buy hold 1643.07 (64.31%)
vs. buy hold 12.24%
178 trades over 89 days (avg 2.00 trades/day)

I was curious and did some more tests, for your same period (89 days), but using BTC-USD. The end balance seems to be ~40% more...
end balance 2202.58 (120.26%)
buy hold 1681.17 (68.12%)
vs. buy hold 31.02%
185 trades over 89 days (avg 2.08 trades/day)

Another test, with BTC-EUR
end balance 1812.70 (81.27%)
buy hold 1618.94 (61.89%)
vs. buy hold 11.97%
178 trades over 89 days (avg 2.00 trades/day)

That's a good reason to use BTC-USD pair;)
btw....
use this:
c.order_adjust_time = 10000
Works better for me

Just as a data point I am trying to create a good ETH strategy code base from 4.x currently simulation is showing about +5% as opposed to about 84% buy and hold. Hehheh. ETH has been so volatile it might be inevitable.

I'd suggest to continue this great stuff over at the discord:
https://discord.gg/ZdAd2gP
As there is no longer an issue here I'll be closing it for now.


Update Read the Docs Python version to 3.8

Fixes #32.

Didn't see that this was already merged before posting changes.


testSideInputUnbounded completion and timeout race

https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow/1739/testReport/junit/org.apache.beam.sdk.transforms/SplittableDoFnTest/testSideInputUnbounded/
https://pantheon.corp.google.com/dataflow/jobsDetail/locations/us-central1/jobs/2018-12-26_17_37_02-9764896340592912014?project=apache-beam-testing
Job timed out at 600 seconds, had successfully completed and was cleaning up when canceled.
Imported from Jira BEAM-6323. Original Jira may contain additional context.
Reported by: apilloud.

There's only one instance of this test failing in Jenkins history and that was a correlated failure with other tests, due to a quota issue: https://ci-beam.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow/8440/testReport/junit/org.apache.beam.sdk.transforms/SplittableDoFnTest/testSideInputUnbounded/
java.lang.RuntimeException: Workflow failed. Causes: The quota check has failed., Requested quota metric In Use Addresses is currently unavailable.
	at org.apache.beam.runners.dataflow.TestDataflowRunner.run(TestDataflowRunner.java:141)
	at org.apache.beam.runners.dataflow.TestDataflowRunner.run(TestDataflowRunner.java:93)
	at org.apache.beam.runners.dataflow.TestDataflowRunner.run(TestDataflowRunner.java:55)
	at org.apache.beam.sdk.Pipeline.run(Pipeline.java:323)
	at org.apache.beam.sdk.testing.TestPipeline.run(TestPipeline.java:399)
	at org.apache.beam.sdk.testing.TestPipeline.run(TestPipeline.java:335)
	at org.apache.beam.sdk.transforms.SplittableDoFnTest.testSideInput(SplittableDoFnTest.java:451)
	at org.apache.beam.sdk.transforms.SplittableDoFnTest.testSideInputUnbounded(SplittableDoFnTest.java:433)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)


Including zone3 in setup crashes plugin (using valid zone3-enabled set8 models)

When I select a model from the config list that supports Zone3 (set8) and restart Homebridge I receive the following error:
[37m[1/4/2022, 10:48:52 PM] [39m[31mTypeError: Cannot read property 'power' of undefined[39m
[31m    at new OnkyoAccessory (/usr/local/lib/node_modules/homebridge-onkyo/index.js:140:40)[39m
[31m    at /usr/local/lib/node_modules/homebridge-onkyo/index.js:37:22[39m
[31m    at Array.forEach (<anonymous>)[39m
[31m    at OnkyoPlatform.createAccessories (/usr/local/lib/node_modules/homebridge-onkyo/index.js:30:13)[39m
[31m    at new OnkyoPlatform (/usr/local/lib/node_modules/homebridge-onkyo/index.js:23:8)[39m
[31m    at /usr/local/lib/node_modules/homebridge/src/server.ts:440:40[39m
[31m    at Array.forEach (<anonymous>)[39m
[31m    at Server.loadPlatforms (/usr/local/lib/node_modules/homebridge/src/server.ts:372:27)[39m
[31m    at Server.start (/usr/local/lib/node_modules/homebridge/src/server.ts:159:29)[39m

This happens on every single model that I tried from "set8" (I tried about 15 from the list). I also attempted the same with zone3 and zone4 using models in set10, with exactly the same results.
If I change a functioning zone2 receiver (from set8), updating the zone from zone2 to zone3, the functioning receiver then starts throwing the same error above. This is the same basic error that I get when I have zone2 in the config of a model that is not zone2-enabled, just that this time I've made sure I was using a valid model.
Any ideas what might be wrong? It's been driving me insane.
Thanks in advance!

The error has slightly changed, but the effect is still the same. Adding any model # with a valid zone3 in the config file results in the plugin crashing Homebridge and an endless cycle of restarting.
[6/4/2022, 1:09:03 PM] [Onkyo] ************************************************************** [6/4/2022, 1:09:03 PM] [Onkyo]   homebridge-onkyo version 2022.18.1 [6/4/2022, 1:09:03 PM] [Onkyo]   GitHub: https://github.com/ToddGreenfield/homebridge-onkyo  [6/4/2022, 1:09:03 PM] [Onkyo] ************************************************************** [6/4/2022, 1:09:03 PM] [Onkyo] start success... [6/4/2022, 1:09:03 PM] TypeError: Cannot read properties of undefined (reading 'power')     at new OnkyoAccessory (/usr/local/lib/node_modules/homebridge-onkyo/index.js:140:40)     at /usr/local/lib/node_modules/homebridge-onkyo/index.js:37:22     at Array.forEach (<anonymous>)     at OnkyoPlatform.createAccessories (/usr/local/lib/node_modules/homebridge-onkyo/index.js:30:13)     at new OnkyoPlatform (/usr/local/lib/node_modules/homebridge-onkyo/index.js:23:8)     at /usr/local/lib/node_modules/homebridge/src/server.ts:442:40     at Array.forEach (<anonymous>)     at Server.loadPlatforms (/usr/local/lib/node_modules/homebridge/src/server.ts:374:27)     at Server.start (/usr/local/lib/node_modules/homebridge/src/server.ts:161:29)


Editor crash when changing to big zoom in Script editor

Godot version:
3.1 f2cc969
OS/device including version:
Windows 10
Issue description:
When I zoom script editor to max(685%) and I try to zoom out, then editor crash without backtrace with this error
ERROR: get: FATAL: Index p_index=2 out of size (size()=2)
   At: ./core/cowdata.h:149

Steps to reproduce:

Zoom script editor to 400%-700%
Try to zoom to 100%

I could reproduce it only once (the first time) so far, console spammed with:
[...]
 Try increasing 'message_queue_size_kb' in project settings.
   At: core/message_queue.cpp:56.
Failed method: FileSystemDock:_tree_thumbnail_done target ID: 7452
Object was deleted while awaiting a callback
Object was deleted while awaiting a callback
Object was deleted while awaiting a callback
Object was deleted while awaiting a callback
[...]

I tried to reproduce this in Ubuntu 18.10 but I was unable to do this.
It looks to be only Windows issue

It works in 0cff752, probably fixed by #24447


Correction for raw affiliation Aeres University of Applied Sciences; LR - Animal Nutrition

Correction needed for raw affiliation Aeres University of Applied Sciences; LR - Animal Nutrition
raw_affiliation_name: Aeres University of Applied Sciences; LR - Animal Nutrition
new_rors: 03jnx2c74
previous_rors:
works_examples: W2990383221;W3044117929
contact: b7b5b70f14f00be3b18a42b95cb04ac1:f08f19631d79e3eb @ aeres.nl

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


dev-dependencies

This tool doesnt appear to remove unneeded dev-dependencies.
Is that feasible to perform, perhaps opt-in?

Hi! Thanks for opening an issue, yeah it's likely possible to do. It would require a bit of fine-tuning the directories that are being searched: dev-dependencies may be used in tests/, benches/, and maybe a few others, while non dev-dependencies would not, as far as I know.
Do you want to try to take a stab at it?

Sure.

Actually, with https://github.com/OpenAPITools/openapi-generator/pull/13835 merged, I don't have a reason to be trimming dev-dependencies, so I wont be working on this.


Diagnostic collector for lakeFS

Design and implement diagnostics collect for lakeFS.
Collect requirements and update a design document first.

collect data from lakeFS daemon
collect schema version information
collect tables and index sizes
dump everything into an archive for easy transport

The first PR handles the part that collects information from the database.
The data we collect helps in finding issues related to schema version, gives size information and etc.
Additional information from the running service still need to be collected in order to integrate the information as part of the diagnostics.

Closing this one, when new requirements on data we need to collect will be added, we will open an issue and implement.


js: reduced bundle size

With the migration to webpack 4, the latest uglify plugin stopped
removing comments by default and some unnecessary files were being
included.

Moment.js was replaced with dayjs
Webpack bundle analyzed was added to be used when necessary to analyze
bundle content

Unfortunately bundle is still big but that's because vue-multiselect was
introduced and lots of templates were migrated to .vue files.
Signed-off-by: Vítor Avelino<EMAIL_ADDRESS>

Next step regarding this topic is to split the bundle into two chunks: vendors and application.

This failing was killing me inside and I had to go with an approach I didn't like but I'd say it's good enough for now. If we get in trouble in the future we can get back to this.
momentjs is awesome but unfortunately a bazooka for what we've been doing.


fixed problems with import in python3.5

I trying to import code in script runned in python3.5:
from asrclient import client

I had messages about import errors. It was unable to import some submodules
from transport import Transport

So there some fix.

Thank you!


Allow rulesDir config to be an array of directories

This opens up the possibility of sourcing rules from third parties or npm packages without implementing plugin support.
Even though we will probably implement plugin support in the future, I can't see any downsides to letting stricter accept multiple rules directories until plugins exist.

Coverage increased (+0.3%) to 52.402% when pulling 7a3567de4ed7fea9139c69a2670a0c2ba6ed7967 on Blasz:multipleRuleDirs into d4f53760be614c15cd233b40c0cbd734adb123da on stricter:master.


Make [AmoDownloads] test more reliable

Close #3156

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

  Generated by :no_entry_sign: dangerJS against 2d78ca695170edd1c9829a4b4bb4506f03e49caa


Templates Issue: TypeError: Cannot read properties of null (reading 'state_on')

Which version of Room Card?
1.08.04
Describe the bug
When trying to use the templates as described in the wiki, an error appears in the preview window:
To Reproduce
n/a
Expected behavior
After adding the template code as provided by the wiki, I would expect the icon to turn yellow when the entities state is 'on'
Screenshots

Desktop (please complete the following information):

OS: macOS 14.5 (23F79)
Browser Chrome
Version 127.0.6533.120 (Official Build) (arm64)

Additional context
Without templating, the icon turns yellow without any issues (just using the normal styles method per entity).
YAML
type: custom:room-card
title: BATHROOM
entity: light.bathroom_lights_group
show_state: false
tap_action:
  action: navigate
  navigation_path: /dashboard-rooms/bathroom
templates:
  - name: test_template
    template:
      show_icon: true
      state_color: true
      icon:
      template:
        styles: >
          if (entity.state == 'on') return 'color: yellow';

entities:
  - entity: light.shellyswitch25_c8c9a3759e8b_channel_1
    name: Ceiling
    template: test_template

More info:
If I indent the template under icon then the error goes away but the icon does not change color:
templates:
  - name: test_template
    template:
      show_icon: true
      state_color: true
      icon:
        template:
          styles: |
            if (entity.state == 'on') return 'color: yellow';

Please check the state value. Because it gets parsed to javascript I'm sure it's a different value or a typo.

It is not. It is "on". I have checked. Please reopen this issue. And please don't consider it closed until we have confirmed it fixed.
Closing the issue so abruptly does not promote community engagement or support in my opinion

Why arent you using : https://github.com/marcokreeft87/room-card/wiki/Configuration#icon-conditions ?

@lennon101 Why did you request removal of this card from hacs? It works fine and has received updates when necessary.
I'm sorry if you had a bad experience with it but why spoil the fun for everyone else too?
@ludeeus Please reconsider the removal of this card!

I'm am hoping this might get some attention.
https://github.com/hacs/integration/issues/4248
I feel this was done in haste to punish this repository.


Update DB seed to use InTransit box state for all boxes in Sent shipment

Query all relevant boxes by:
SELECT d.id,d.box_id,b.box_state_id,s.id,s.state \
FROM shipment_detail as d \
LEFT JOIN shipment as s ON d.shipment_id = s.id \
LEFT JOIN stock as b on d.box_id = b.id
WHERE s.state = "Sent";

and update the entries in the DB dump (6 rows).

cf. also https://github.com/boxwise/dropapp/pull/559

 2.0 Add InTransit box state


Refactor use memento pattern to turn on/off warning bar

Move each component into a single file module

Codecov Report
Base: 86.21% // Head: 86.20% // Decreases project coverage by -0.01% :warning:

Coverage data is based on head (b5b7336) compared to base (d7ed512).
Patch coverage: 97.35% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #105      +/-   ##
==========================================
- Coverage   86.21%   86.20%   -0.02%
==========================================
  Files          80       73       -7
  Lines        3018     3029      +11
  Branches      462      467       +5
==========================================
+ Hits         2602     2611       +9
- Misses        321      322       +1
- Partials       95       96       +1

Flag
Coverage Δ

unittests
86.20% <97.35%> (-0.02%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/pyfx/view/common/frame.py
61.21% <86.66%> (+2.54%)
:arrow_up:

src/pyfx/view/components/help_popup.py
94.80% <95.65%> (ø)

src/pyfx/view/components/autocomplete_popup.py
94.44% <95.83%> (ø)

src/pyfx/app.py
96.84% <100.00%> (+0.06%)
:arrow_up:

src/pyfx/view/components/__init__.py
100.00% <100.00%> (ø)

src/pyfx/view/components/json_browser.py
100.00% <100.00%> (ø)

src/pyfx/view/components/query_bar.py
96.84% <100.00%> (ø)

src/pyfx/view/keymapper/keymapper.py
89.36% <100.00%> (ø)

src/pyfx/view/view_frame.py
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


bug(MatDatePicker): displays wrong german dates

Reproduction
StackBlitz: https://stackblitz.com/edit/angular-azy5l8?file=src/main.ts
Steps to reproduce:
If I type a date like 8.6.20 using the German date format then on OnBlur it is changed to 6.8.2020.

If I type a date like 16.12.2020  using the German date format then it will be invalid. It seems that the day is interpreted as a month.

Expected Behavior
The date is displayed as it was entered.
Environment

Angular: 9.2.4
CDK/Material: 9.2.4
Browser(s): Chrome 83.0.4103.106
Operating System: Windows 10

Found it: https://github.com/angular/components/issues/18112


Server rejects new connections after a bad connect

Hi,
After a bad connect, the server rejects all new connections. This can be replicated by using the SSL server and then connecting to it with putty.
Simple fix though :)
Replace all the occurrences of  "return" with "continue" in the while loop of AcceptConnections.
thanks
Mike

Still had issues with the SSL version getting stuck while waiting for a connection to finish - which would never finish.
Resolved by changing AuthenticateAsServer to BeginAuthenticateAsServer :)

Thanks @MrMikeJJ for both of these, I'll incorporate now and update Github and Nuget both!

Hi @MrMikeJJ for the BeginAuthenticateAsServer, can you submit a pull request?  I'd like to see your implementation.  Thanks!

Sure. Will be a few days though, i will have to redo this without the other changes which I did for my use case. And won't be near the computer I did this on until Tuesday.


Fix PED Documentation Bugs

Codecov Report

Merging #203 (3a04da8) into master (b96471d) will not change coverage.
The diff coverage is 0.00%.

@@            Coverage Diff            @@
##             master     #203   +/-   ##
=========================================
  Coverage     51.56%   51.56%
  Complexity      604      604
=========================================
  Files           125      125
  Lines          2612     2612
  Branches        336      337    +1
=========================================
  Hits           1347     1347
  Misses         1182     1182
  Partials         83       83

Impacted Files
Coverage Δ

.../java/seedu/edrecord/logic/commands/CdCommand.java
0.00% <0.00%> (ø)

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 b96471d...3a04da8. Read the comment docs.


How do I fix the random number seed?

I found that when running nerfacto, the results of each eval set were different, with a PSNR fluctuation of approximately 0.3 dB. I don't know how to express this result in my paper,

Duplicate #1641


XamMac needs .app/Contents/MonoBundle/OpenTK.dll manually replaced

Post-build, within the Debug/Release folder:
cp OpenTK.dll TestEtoGl.XamMac.app/Contents/MonoBundle/
Then the app will run.
Haven't figured out why the OpenTK.dll library in the bin folder isn't packaged in the app properly.

I don't have a perfect solution to offer, but I dug into this a couple days ago and learned some things that might be useful to someone at some point.
As you've seen, the correct version of OpenTK is copied to the build output folder, just not packed into the ultimate .app bundle. It can be brute forced on a command line, or that cp line could be turned into a post build step, though at least in my case the latter option required an external console, which in turn doesn't close automatically and you either have to constantly close the leftover terminal windows or end up with a cascade of them on screen.
The approach I settled on was a new MSBuild target, set to run after the Build target, as such:
<Target Name="ReplaceOpenTK" AfterTargets="Build">
    <ItemGroup>
        <OpenTK Include="$(TargetDir)\OpenTK.*" />
    </ItemGroup>
    <Copy SourceFiles="@(OpenTK)" DestinationFolder="$(OutputAppPath)\Contents\MonoBundle" />
</Target>

See it in context here. The target builds a list named OpenTK, comprised of everything in the output directory matching that name, including the PDB, the .dll.config, and of course the DLL itself, then just crams it into the .app bundle, overwriting everything inside already. No need for an external console, no orphan terminal windows, nice and clean.
I haven't figured out how to avoid the Xamarin OpenTK reference in the first place, but I have figured out where it gets added. I was able to dump diagnostic build output to a text file for easy searching by building at the command line with this:
msbuild -verbosity:diagnostic Path/To/Project.csproj > builddiagnostic.txt
Having seen that the undesirable OpenTK.dll packed into the output .app was 665KB in size, I tried to find out where it was coming from. "Search this Mac" didn't help, presumably because the location wasn't indexed, but poking around that massive diagnostic build log showed me that in my case the file was being copied from here:
/Library/Frameworks/Xamarin.Mac.framework/Versions/Current/lib/x86_64/full
There are other copies, too, in lib/reference/full and some nearby directories, but the 665KB file was only in that location. Searching the build log for full/OpenTK.dll got me only one result: there's a build task named "Mmp" that's a child of a build target called "_CompileToNative", and during that task, the pernicious Xamarin OpenTK insinuates itself into our .app bundles.
How one would avoid referencing the undesirable library in the first place, I don't know, but this sledgehammer of a technique seems to be working for my project. I'm able to reference the proper version in Visual Studio for Mac, get Intellisense and everything, and then build the project, replace the files without manual intervention, and run/debug the project without issue.
Reading through this OpenTK issue, or digging through the Xamarin.Mac repo, might shed some light on things, but I didn't have much luck myself. The Xamarin project makes it clear where _CompileToNative is, as well as a couple things for Mmp (here and here), but I'm hard pressed to say how much more there is to it than those three, and I couldn't piece all that stuff together into a more elegant solution, I'm sorry to say.


Extension issue

Issue Type: Bug
Extension Name: bracket-pair-colorizer-2
Extension Version: 0.2.0
OS Version: Windows_NT x64 10.0.19042
VSCode version: 1.53.1

:warning: We have written the needed data into your clipboard. Please paste! :warning:
{
	"messages": [],
	"activationTimes": {
		"codeLoadingTime": 69,
		"activateCallTime": 21,
		"activateResolvedTime": 10,
		"activationReason": {
			"startup": true,
			"extensionId": {
				"value": "CoenraadS.bracket-pair-colorizer-2",
				"_lower": "coenraads.bracket-pair-colorizer-2"
			},
			"activationEvent": "*"
		}
	},
	"runtimeErrors": [
		{
			"name": "Error",
			"message": "Cannot invoke loadWASM more than once."
		}
	]
}

@saumyakraj Please close this as it's a duplicate of #295. Use that thread instead of creating a new one.


ConfigurationItemFactory - Skip unneeded RegisterExtendedItems on .NET Core

And other unsupported platforms. See also #2970

Thanks!


use c++ includes for the int64 support

this previously broke e.g. with PCH builds using cotire

I added TR1 support.

Thanks I'd appreciate it if you could add support for bare C++03, using inttypes.h.
We've always supported C++03 and I do not think there is a necessity to change the requirements.

Hm, since there is no way to detect presence of TR1, this now relies on the fact that C99 headers are present.
One could reason that the extern "C" version should be sufficient on its own but i seem to be hitting a bug in clang here, and having <cinttypes> in C++11+ seems to be a viable workaround.

Thank you for the changes. I think that the code is now fine, hence merged.
It is my understanding that with the changes, the code should work in C++11, while preserving the existing behavior when C++03 is used. That's strictly an improvement, and I'm happy with that. Thank you!


Check for required packages in package_facts

This does not require sudo/root access in contrast to the package module

@richm thanks for your suggestions, they're squashed into this commit.

[citest]


Two Modals on one page causes both modals to open

If two modals with two different open buttons are on one page, it causes both modals to open when using the second button.  I thought the issue was creating unique open trigger data attributes, but I tested this and it still causes both modals to open when using the second button.  Would you have a solution to this?

@jotchon Thanks for opening this issue. Its hard for me to debug this without actually seeing the code. Seems to be that there might be a case of duplicate modal IDs.
If that is not the case, could you please create a simple test case on codepen?

Closing due to inactivity.


aio.core: Add directory utils

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>

v temp WIPping while i add docstrings

temp reWIPping again for some last-minute refactoring

waiting for #247

apologies for force push i had too many conflicts between branches, so cleaned up pr


InaccessibleObjectException when extracting public property of JVM class in Java 16+

Describe the bug
AssertJ throws an exception when attempting to "extract" a public property of a built-in Java class in (at least) Java 16 and above. For older versions it just gives a warning. Note this is not the same as previous bugs which resulted in the FAQ entry. As written in that entry:

AssertJ features requiring private fields introspection

But this test case is accessing a public getter method on a public class. Secondly, the workaround given in the FAQ has to be updated for this particular case to work because you need to add a new flag: --add-opens java.base/com.sun.crypto.provider=ALL-UNNAMED. There are likely many other such cases that aren't covered by the flags specified in the FAQ. I've added some analysis at the end and a possible fix.

assertj core version: 3.23.1
java version: OpenJDK Runtime Environment AdoptOpenJDK-16.0.1+9 (build 16.0.1+9) or OpenJDK Runtime Environment Temurin-19+36 (build 19+36)
test framework version: TestNG 7.6.1
os (if relevant): macOS 10.15.7

Test case reproducing the bug
    @Test
    public void minimalTestCase() throws Exception {
        var keyPair = KeyPairGenerator.getInstance("DiffieHellman").generateKeyPair();
        var pub = keyPair.getPublic();
        assertThat(pub)
                .extracting("params", as(type(DHParameterSpec.class)))
                .isNotNull();
    }

Analysis
The root cause appears to be org.assertj.core.util.introspection.Introspection#getPropertyGetter which always calls getter.setAccessible(true) even if the method is already accessible. Calling setAccessible results in an immediate access error in Java 16+, even if the method is public. I suggest that, if we cannot avoid calling setAccessible, that we catch any InaccessibleObjectException from this method and simply try to call the getter anyway in that case.
        try {
            try {
                // force access for static class with public getter
                getter.setAccessible(true);
            } catch (InaccessibleObjectException e) {
                // Might already be public - attempt access anyway
            }
            getter.invoke(target);
        } catch (Exception t) {
            throw new IntrospectionError(..., t);
        }

The only trouble I see is that InaccessibleObjectException only exists since Java 9, so you might need to catch (Exception e) instead and then examine the class name. (Java 9 also has getter.canAccess(target) which may be a better approach, but again would require reflection).

Thanks for the detailed report, @NeilMadden! We'll look into it.
This is also related to #2363 and I believe we should rethink how to handle such general cases instead of having type-specific handling.


fix(alert): update icon postion  in alert

before

after

This wouldn't fix the issue. I already explained the problem with Firefox in this issue #627.
If you want to fix this you can change make these changes in the alert.tsx file (remember to update both styles):
const alertVariants = cva(
- "relative w-full rounded-lg border p-4 [&:has(svg)]:pl-11 [&>svg+div]:translate-y-[-3px] [&>svg]:absolute [&>svg]:left-4 [&>svg]:top-4 [&>svg]:text-foreground",
+ "relative w-full rounded-lg border p-4 [&>svg+div]:translate-y-[-3px] [&>svg]:absolute [&>svg]:left-4 [&>svg]:top-4 [&>svg]:text-foreground [&>svg~*]:pl-7",

After changing both files you need to build the registry by running:
pnpm build:registry

(Thanks to @adham-coding for the hint)

Be careful. You have updated only one of the themes and once you built the registry also files that you haven't changed got updated (I assume you're on Windows).
Also don't update the pnpm-lock.yaml please.

@dan5py thanks for the guidance


Derived Measures: HANA does not support CAPTION syntax for calculated measures and throws syntax error.

Line 305 of the derived measure factory:
    calculatedMeasure += ",\nCAPTION = \"" + metadata.MEASURE_CAPTION + "\"";

generates a CAPTION for the calculated measure. But HANA does not like it one bit:
Error: The XML for Analysis provider encountered an error (XMLAnalysisError.0x80000003)
Error: Error in XMLA Statement: Error occurred while executing a MDX statement. The error message is: Syntax Error : ...
CAPTION = "Actual percentage of parent"<<< (Source: XML for Analysis Provider, Code:<PHONE_NUMBER>)
Obviously we shouldn't just yank out this code because HANA doesn't swallow it, however it would be cool to make it configurable whether the caption was generated as part of the MDX, and possibly whether to handle the caption on the UI end instead.

Closing for now. The developer/integrator will need to configure xavier to disable/enable these properties, but the support is there and the current bootstrap avoids the issue for HANA.


Update username to become case sensitive

Now username is all lower case, right?

yes. forget to close this issue. ps.


Support running on offline devices

Description
This allows Node-RED and nodes to be loaded from a local cache rather than being installed from npmjs.org each time the project snapshot is updated.
Related Issue(s)

part of #45
Checklist

[x] I have read the contribution guidelines
[ ] Suitable unit/system level tests have been added and they pass
[x] Documentation has been updated

[ ] Upgrade instructions
[x] Configuration details
[ ] Concepts

Labels

[ ] Backport needed? -> add the backport label
[ ] Includes a DB migration? -> add the area:migration label

Tthere is exactly the same wording in the doc update for the flowoforge project as well


FIX: Display the correct name in submissions page

Problem
Currently, the correct name is not being displayed when viewing submissions.

When a user creates a submission, only the following data is accessible (for the moment):
input CreateSubmissionInput {
  googleMapsUrl: String
  healthcareProfessionalName: String
  spokenLanguages: [Locale!]
  notes: String
}

Success
The correct name should be displayed when viewing submissions.
Requirements

[ ] Debug the issue to ensure the correct information is displayed.

Implementation notes
[Suggest how this might be implemented.]

@Anissa3005, I'd love to work on this, but I'm unable to find where I can view or edit the submission. Currently, I can only add a doctor. That's all I can do for now.


Error on adding external PDF file to response

Describe the bug
When I send a request to get a pdf file from postman, I get this error:
{
    "type": "https://stoplight.io/prism/errors#UNKNOWN",
    "title": "Cannot find serializer for application/pdf",
    "status": 500,
    "detail": ""
}

I was following their procedure to add external file to response from here
To Reproduce
my yaml file looks like this:
responses:
        200:
          description: Requested Report in PDF format
          content:
            application/pdf:
              schema:
                type: string
                format: binary
              example:
                sampleFile:
                  summary: A sample file
                  externalValue: 'A valid url of pdf file`
```

@AhsanShuvo
That is a know limitation. In particular:

We do not support the externalValue in OpenAPI (yet) #1155
We do not support returning binary files

We want to support this, but it's not exactly our top priority at the moment.
I'm closing this as a duplicate of #1155

Two years on, why has this not been implemented yet? I need this. Is there perhaps a workaround?


⬆ Upgrading react

For #4

@girishsawant999 I'm not sure why the github actions are failing, can you help me with that?


fix: remove redundant calls from PreFetch

In every DependencyClient we have, MatchingVersions() is just a call to Versions() plus semver matching, which is computationally expensive. It also was being called on every edge of the pre-fetched graphs.
Removed it to reduce CPU usage and hopefully improve performance with Maven resolution / Guided Remediation.
I've also skipped fetching things with MavenDependencyOrigin set (e.g. dependencyManagement dependencies) since there's potentially hundreds of them.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 67.10%. Comparing base (3653a1d) to head (56d3821).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1456      +/-   ##
==========================================
- Coverage   67.27%   67.10%   -0.18%
==========================================
  Files         192      192
  Lines       18144    18131      -13
==========================================
- Hits        12207    12167      -40
- Misses       5291     5315      +24
- Partials      646      649       +3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

I'm not exactly sure - it would help CPU usage and the number of goroutines running, but I'm not sure how this translates to run time.

Do you know how much this could improve the performance?
but I'm not sure how this translates to run time.

For my specific use case, on my specific machine (sample repo I was using to debug), performance is:
v1.9.0: ~2 min
v1.9.1: ~12 min
#1436: ~8 min
This PR: ~8min

I added another change to this PR that should hopefully reduce the number of calls for Maven specifically.

I added another change to this PR that should hopefully reduce the number of calls for Maven specifically.

Much faster, even more than 1.9.0! Thanks!

I will note I'm getting more extraction errors on some repos (such as https://github.com/SpringCloud/spring-cloud-gray) though. I'm not a big Maven dev, so I'm not sure which is valid/right.
Scanning dir /tmp/spring-cloud/
Error during extraction: (extracting as vcs/gitrepo) worktree not available in a bare repository
Error during extraction: (extracting as java/pomxml) failed resolving {Maven:cn.springcloud.gray:spring-cloud-gray-client[Concrete:${revision}] {}}: failed parsing version constraint 'Maven:org.springframework:spring-jcl[Requirement:]': invalid `>` in `>=0.0.0`
Error during extraction: (extracting as java/pomxml) failed resolving {Maven:cn.springcloud.gray:spring-cloud-gray-client-netflix[Concrete:${revision}] {}}: failed parsing version constraint 'Maven:org.springframework:spring-jcl[Requirement:]': invalid `>` in `>=0.0.0`
Scanned /tmp/spring-cloud/spring-cloud-gray-code-component/pom.xml file and found 1 package
Scanned /tmp/spring-cloud/spring-cloud-gray-core/pom.xml file and found 1 package
...

Hmm those errors seems like it would have been introduced in v1.9.1 - might need to look into that further.


updated hiedr2mosaic to not remove flat files if the keep flag is true

Description
changes hiedr2mosaic.py to retain (not remove) output files from hijitreg calls.
Related Issue
none
Motivation and Context
I wanted to inspect the flat files/replicate some jitter plots for hirise images I have seen out there that I believe are directly produced from these files. For a more complete way to debug hiedr2mosaic it makes sense to keep these files anyways, so it looks like this was just an oversight.
How Has This Been Tested?
nope but I doubt anything is wrong with it
Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist:
doesn't look like anything from the checklist applies
Licensing:
This project is released under the LICENSE.

I dedicate any and all copyright interest in my contributions in this pull request to the public domain.  I make this dedication for the benefit of the public at large and to the detriment of my heirs and successors. I intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this contribution under copyright law.

Ross, you are welcome to pull it in any time you wish.


Latest release breaks img2img

On CUDA enabled devices, attempting to execute img2img results in:
Expected all tensors to be on the same device, but found at least two devices, cpu and cuda:0! (when checking argument for argument index in method wrapper_gather)

Investigating...

Thanks for the report. Looking into it.

The check in ddim/plms that ensures the device is on cuda that was removed in the PR is the cause of the regression... guess this needs to be here, just needs an additional check

Thanks, I've backed out the changes to ddims. Since plms sampler is not currently used in img2img, I have kept the PR changes to plms.py.


Alpimaps sets brightness to minimum on startup and I cannot see anything

I wanted to try Alpimaps, but every time I open the app the screen goes very dark, as if the brightness was set to the minimum (or even lower?) and it's really hard to see anything. I have managed to tap on some buttons but I don't see any option to change the brightness, so I cannot try the app.
I have tried deleting cache and data, and reinstalling the app, both from F-Droid and github. It keeps happening every single time.
My device is a FairPhone 4 running iodéOS 3.4 (based on Android 12).

@nach0 wow actually did not know some people were testing this! Can you tell me which version you installed? I ll try to reproduce

Well, yes. I saw a new maps app in F-Droid that could be useful for hikes, so I decided to give it a try.
So far I have tested versions <IP_ADDRESS> and <IP_ADDRESS>, and had the same problem with both. As additional information, I mentioned that my OS is iodéOS 3.4 (based on Android 12), it is quite close to LineageOS 19, so it is fairly degoogled (has no Google Play services, but has microG). In case this information is useful.

@nach0 OK. Thanks! I use los toi son we should get around the same behaviors. I will look into it.
I should mention that is app.is a bit particular in the sense that it is best used with offline generated data. It can work with offline map,hill shades, contours, hiking routes,  routing, geocoding....
The idea is you can generate those maps yourself so that you never need anything else.
I ll share the repo where I explain how to generate stuff

That sounds great!
I already use Organic Maps and OsmAnd with offline maps. And I am diving into getting gpx files to plan routes and maybe editing them beforehand, so I thought I'd give Alpimaps a try and see how it works for those things. It sounds like it will be a good match :)

@nach0 here is it the repo explaining how to generate data https://github.com/Akylas/alpimaps_data_generator
It is not "easy" but doable.
I can also generate for your country if you want. I already have France and Italy but i could generate others.

I'm happy to report that with the latest update (<IP_ADDRESS>) the bug with the very dark display is gone. Now I'm ready to try the app.

@nach0 thanks for reporting this I wanted to tell you :) not sure you still had the app installed :)


How to put named functions on the stack without calling them?

The examples for the &i and use functions both show how to import functions from another file that puts these functions onto the stack:
&i "example.ua"
double ← use "double" .
square ← use "square"
square double 5

However, the examples don't show the contents of example.ua, so I don't exactly know how to export these functions there. It seems that I'm supposed to put the named functions into an array onto the stack in example.ua, but I don't know how to put functions onto the stack without calling them. I tried it like this:
# example.ua
double = *2
double

and like this:
# example.ua
double = *2
[double]

but these both throw Error: Stack was empty when evaluating argument 2.
I can put the function on the stack by doing this:
# example.ua
double = *2
[(double)]

but then it's wrapped in an anonymous function and not named anymore.
How can I get this to work?

This is a bug.
For now, you can export double_double from your module.

Fixed in 3df5817

Could you still add a tutorial how to do it? Because with your fix from 3df5817 your double_double workaround doesn't work anymore and neither do the other methods I tried before.

It is working correctly for me.
Can you show the code that's not working?

This is the simplest example I could come up with:
For this code it works:
echo ← ⍥(&p &sc)∞

(echo)

But this doesn't work:
echo ← (⍥(&p &sc)∞)

(echo)

This shows (⍥(&p&sc)∞) in watch mode.
However, I wrapped the function I want to export in parens, because the older version of uiua would throw an Stack was empty when evaluating array argument 1 error otherwise, but the version compiled from the newest commit doesn't throw that error anymore, so I can get it to work.
Still, it would be nice if exporting also worked for functions wrapped in parens.

Also, if I'm not mistaken, there is another problem with exporting functions right now: You can only export functions with the same signature (or is there a way around that?). Maybe use could be reworked to just look at all bindings in the imported files instead of only the named functions on the stack?

Okay, I think I've fixed it.
I've removed the restriction about functions put into arrays having to have compatible signatures in 7e9c66ac87bc. I believe that restriction is from when the signature checker was less sophisticated.
I've made it so that binding a function value overwrites the function's name in 24c4496abfcb.
This should now work with use properly.
echo ← (⍥(&p &sc)∞)
(echo)

It should be noted that the example you gave:
echo ← ⍥(&p &sc)∞
(echo)

never actually terminates or binds anything, since you have an infinite loop.

Okay, I think I've fixed it.
I've removed the restriction about functions put into arrays having to have compatible signatures in 7e9c66a. I believe that restriction is from when the signature checker was less sophisticated.

Yes, that seems to work now.
However, now it seems to be impossible to call imported functions with more than 1 output. Let's say, I have the following file:
# foobar.ua
foo ← (|0.2 1 2)
bar ← (|0.3 3 4 5)
foo_bar

I've tried the following ways to call foo:
# main.ua
&i "../uiua/foo.ua"
foo ← use "foo"
foo
# prints '(foo)'

# main.ua
&i "../uiua/foo.ua"
foo ← use "foo"
!foo
# Only functions with 1 output may be explicitly called, but the function foo has 2 outputs

You can no longer put things on the stack on a line before a binding where you want them to be used.
You must either bind the imported module to a name to use later, or import on the same line as the binding.
So you can do
m ← &i "../uiua/foo.ua"
foo ← use "foo" m
foo

or
foo ← use "foo" &i "../uiua/foo.ua"
foo


KBFS basically nonexistent now, worked before

Hello there!
I installed KBFS on an instance of Ubuntu 14.04 a couple of days ago. I was able to successfully look at others' /keybase/public directories and even write my own index.md last night, but now, it doesn't work. Namely, there is no directory structure in /keybase at all.
ubuntu in ~(ruby-2.3.0) λ cd /keybase
ubuntu in /keybase(ruby-2.3.0) λ sudo ls -al
total 8
drwxrwxrwx  2 root root 4096 Apr 24 00:30 .
drwxr-xr-x 23 root root 4096 Apr 24 01:10 ..
ubuntu in /keybase(ruby-2.3.0) λ cd /keybase/public/readyp1
cd: no such file or directory: /keybase/public/readyp1
ubuntu in /keybase(ruby-2.3.0) λ cd /keybase/public/chris
cd: no such file or directory: /keybase/public/chris

I don't have access to a Windows/Mac machine at the moment, so I can't try dropping anything in there. What should I do?
my log id: 5e253f5060682886b6032d1c

Just realized something - if it means anything, just after it was working, I did a sudo reboot before going to sleep, which may have messed things up.

Does run_keybase help?
I also see this: /opt/keybase/Keybase: error while loading shared libraries: libnotify.so.4: cannot open shared object file: No such file or directory

Yes, it works again! Is there a way for me to have it run run_keybase on boot?

Actually, I lied (sorry). /keybase/public and /keybase/private exist, along with a /keybase/kbfs.nologin.txt, but attempting to cd anywhere in public results in the terminal hanging and having to be manually closed out. run_keybase displays the usual, but keybase login literally does nothing and goes back to the prompt: I would tell you what exit code occurs, but $? doesn't work for some reason.

It's probably trying to use the GUI, which isn't working because of the libnotify error.
Is this a desktop machine or a headless server?

Headless - like I said, worked fine before.

Try keybase unlock

That was successful, but attempting to cd /keybase/public/readyp1 still hung the terminal, resulting in me manually closing the terminal out. At this rate, should I just uninstall it and reinstall?

Probably no need to reinstall, likely something fixable.  Can you try keybase log send again and report the log ID?

It's df28f30b95610a255f5ab51c
Also, I just noticed when I ran it that it gave me a couple of errors at the top:
▶ WARNING error opening log "/home/ubuntu/.cache/keybase/keybase.updater.log": open /home/ubuntu/.cache/keybase/keybase.updater.log: no such file or directory
▶ WARNING error opening log "/home/ubuntu/.cache/keybase/keybase.start.log": open /home/ubuntu/.cache/keybase/keybase.start.log: no such file or directory

Hi @tcby45, is it working now?  It looks like to me that you successfully unlocked your key when you ran keybase unlock, but then KBFS was in a exponential backoff where it was waiting about 90 seconds in between connection attempts.  You tried to access /keybase/public/readyp1 within that 90 seconds, and it hung.  But after that, it looks like KBFS successfully connected to the backend server, so I'd expect future accesses to work.
Clearly this is a bad user experience, and we should try to short-circuit that backoff algorithm somehow once the key is unlocked.
Also, for what it's worth, it looks like you shell is very aggressive about looking stuff up in $PWD.  Basically every letter of every command you type ends up being a KBFS lookup, which is probably going to be very slow for you.  You might want to disable those parts of your shell, including having . in your $PATH, while you're roaming around KBFS.


Flutter 1.0 will come?

We're not aiming for a specific date.  You can track the Flutter 1.0 milestone https://github.com/flutter/flutter/milestones/Flutter 1.0 to get a sense for what we'd like to accomplish before 1.0.  GitHub says we're 39% of the way there, but I'd take that number with a big grain of salt.  :)

Can finish Android or IOS Flutter 1.0 first? Just like React Native. That should make more developers involved in the project.

Developers should feel welcome and encouraged to get involved in the project regardless of the quality bar we'd like to hit for 1.0.


pin b2sdk version

The code uses internal API (like B2RawApi) and therefore b2sdk's versioned should be pinned.

I think you need to pin to a minor version, b2-sdk-python==1.9.0, if you are using the private api.


Compile error for Windows tool with mingw on Linux

Godot version:
3.2-beta 40d1486cb3
OS/device including version:
Linux mint 19.2, gcc (Ubuntu 8.3.0-6ubuntu1~18.04.1) 8.3.0
Issue description:
[100%] Linking Program        ==> bin/godot.windows.opt.tools.64.exe
modules/libmodules.windows.opt.tools.64.a(register_module_types.gen.windows.opt.tools.64.o):register_module_types.gen.cpp:(.text+0x14): undefined reference to `register_camera_types()'
modules/libmodules.windows.opt.tools.64.a(register_module_types.gen.windows.opt.tools.64.o):register_module_types.gen.cpp:(.text+0xe4): undefined reference to `unregister_camera_types()'
collect2: error: ld returned 1 exit status
scons: *** [bin/godot.windows.opt.tools.64.exe] Error 1
scons: building terminated because of errors.

Steps to reproduce:
clean by scons p=windows --clean
delete all *.a, *.o, *.d
scons p=windows
Minimal reproduction project:

This is caused by #33992 camera code move, probably something else should be cleaned too (*.gen.* files, scons db, git clean -dfx).
I can build for Windows using gcc and clang MinGW toolchains without any issues.

oh... i didn't know that git clean -dfx removes all untracked files, including my custom modules... :sob:

also deleted *.gen.* files and did git clean -dfx.
but I got still the same error.

I found that there is an error message at start.
$ scons -j 14 platform=windows bits=64 verbose=no target=release_debug debug_symbols=no
scons: Reading SConscript files ...
Configuring for Windows: target=release_debug, bits=64
Using Mingw

scons: warning: Ignoring missing SConscript 'modules/camera/SCsub'
File "/mnt/dev/godot/modules/SCsub", line 17, in <module>

@bruvzg do you have any clue?

oh... renaming SCSub to SCsub at https://github.com/godotengine/godot/tree/master/modules/camera fixed this issue...
cc @bruvzg


Add ockam sub command to create a vault without creating a node

Currently
We create a file based vault when a node is created.
ockam node create n1
cat ~/.config/ockam/vault.json

The json file contains serialized vault data.
This is how a simple file based vault can be created and then used to manage identities etc.
https://github.com/build-trust/ockam/blob/4659eed3b84d339d9590f9dca71d64dd62c15b90/implementations/rust/ockam/ockam_api/src/nodes/service/vault.rs#L38-L39
However currently we've set it up so a vault belongs to a node and is controlled by a service running in the node.
See:

https://github.com/build-trust/ockam/blob/develop/implementations/rust/ockam/ockam_command/src/node/create.rs#L271-L276
https://github.com/build-trust/ockam/blob/develop/implementations/rust/ockam/ockam_api/src/nodes/service/services.rs#L21-L40

This is an artificial constraint created in the ockam_command and ockam_api crates. The ockam create allows creating any number of vaults - they can be file based or based on some cryptographic hardware.
Desired
We want decouple management for vaults from nodes (when using ockam command)
ockam vault create v1

should create a new file based vault and place the file for it in
CONFIG_DIR/vaults/v1/vault.json

In separate issues we'll create commands to delete and list vaults, along with using vaults to create/manage identities and attaching vaults to a node.

We love helping new contributors!
If you have questions or need help as you work on your first Ockam contribution, please leave a comment on this discussion.
If you're looking for other issues to contribute to, checkout this discussion and labels -  https://github.com/build-trust/ockam/labels/good first issue or https://github.com/build-trust/ockam/labels/help wanted

Hi @mrinalwadhwa I will work on this one.

Awesome thank you! Let me know if you have any questions

Hi @mrinalwadhwa Please review my PR


outer_resample! slower than necessary

The benchmark for outer_resample! takes 5ms, whereas resampling should be faster according to the benchmark for likelihood_indices (even if that misses the actual resampling step). So we should benchmark likelihood_resample! and then use the resampling algorithm from there also in outer_resample!.

This is going to be fixed by commit 40033e5 when #19 will be merged.


Skip creating a subscription replication snapshot if no messages have been published after the topic gets activated on a broker

Motivation
There's a bug in replicated subscriptions snapshotting. Snapshots get continuously created after a topic gets activated and before new messages are published. This is a gap in the logic introduced in #11922.
Additional context
The intention of the #10292 and #11922 changes were to pause replication snapshots when there are no new messages.
These changes were made to address #6437 and as an alternative to #7299 changes.
Modifications

Add condition to skip creating snapshots when the lastDataMessagePublishedTimestamp is 0.
Modify existing test case testReplicationSnapshotStopWhenNoTraffic to verify that snapshots aren't published before messages have been published.
[x] doc-not-needed

I was also considering a fix where a single snapshot would be created after topic activation instead of skipping the snapshotting completely. @merlimat what is your recommendation for the fix?

@merlimat @codelipenghui Please review

@merlimat @codelipenghui @Technoboy- PTAL

This PR was not merged to release/2.9.4 but added release/2.9.4 label.


Add Cart backend route

Cart Management

Add to Cart:

Endpoint: api/cart/add
Description: Add a product to the user's cart.

View Cart:

Endpoint: api/cart/view
Description: View the user's cart with all items.

Remove from Cart:

Endpoint: api/cart/remove/[id]
Description: Remove an item from the cart.

#17  fixes it


pull request for e2e test at 01/17/2017 22:45:09

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Release v1.0.0

addons: Allow editing of addon parameters
addons: Accept numeric parameters as floats
upgrade: Display datetime format in error output
upgrade: Display upgrade state whenever showing existing upgrades
login: Update URL for integration environment
addons: Allow installation parameters in CLI
ingress: Better message when deleting non-existent ingress
versions: Align version list with cluster creation
Add missing region flags
idp: Allow schema-less hosted domains on Google IDP
addons: Disallow editing addons without parameters
addons: Disallow editing params of a non-ready addon
addons: Use integer for numeric params
logs: Report better errors for incompatible installation states
machinepools: Display default machine pool as Default
clusters: Remove count flag
machinepools: Allow editing labels and taints
addons: Check existence of addon installation before installing
addons: Send empty string when CIDR is nil
machinepool: Skip autoscaling prompt when setting replicas
machinepool: Error out on invalid min-replica
cluster-admin: Format the success message
flags: Fix description of cluster flags
edit-cluster: Skip interactive mode if any flag is set
login: Print link to get new token on expired session
flag: Remove unnecessary flags
interactive: Remove flag from global create
addons: Enforce interactive mode if required params are missing
version: Align sort with OCM version list
users: Disallow grant and revoke on cluster-admin
describe: Add cluster network configuration

/lgtm

/lgtm