Unable to run build post upgrading to 0.71 and enabling new architecture in a hybrid application

Description
Execution failed for task ':app:buildCMakeDebug[x86_64]'.
> com.android.ide.common.process.ProcessException: ninja: Entering directory `/home/fad03mhr3/Desktop/Apps/new_arch_13jan/packages/react-native/android/app/.cxx/Debug/282a1w26/x86_64'
  [0/2] Re-checking globbed directories...
  [1/2] Re-running CMake...
  -- Configuring incomplete, errors occurred!
  See also "/home/fad03mhr3/Desktop/Apps/new_arch_13jan/packages/react-native/android/app/.cxx/Debug/282a1w26/x86_64/CMakeFiles/CMakeOutput.log".
  FAILED: build.ninja
  /home/fad03mhr3/Android/Sdk/cmake/3.18.1/bin/cmake --regenerate-during-build -S/home/fad03mhr3/Desktop/Apps/new_arch_13jan/node_modules/react-native/ReactAndroid/cmake-utils/default-app-setup -B/home/fad03mhr3/Desktop/Apps/new_arch_13jan/packages/react-native/android/app/.cxx/Debug/282a1w26/x86_64

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

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':app:buildCMakeDebug[x86_64]'.
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$1(ExecuteActionsTaskExecuter.java:147)
	at org.gradle.internal.Try$Failure.ifSuccessfulOrElse(Try.java:282)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:145)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:133)
	at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:77)
	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:56)
	at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)
	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:157)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
	at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:74)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:333)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:320)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:313)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:299)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.lambda$run$0(DefaultPlanExecutor.java:143)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:227)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:218)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:140)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
Caused by: org.gradle.internal.UncheckedException: com.android.ide.common.process.ProcessException: ninja: Entering directory `/home/fad03mhr3/Desktop/Apps/new_arch_13jan/packages/react-native/android/app/.cxx/Debug/282a1w26/x86_64'
[0/2] Re-checking globbed directories...
[1/2] Re-running CMake...
-- Configuring incomplete, errors occurred!
See also "/home/fad03mhr3/Desktop/Apps/new_arch_13jan/packages/react-native/android/app/.cxx/Debug/282a1w26/x86_64/CMakeFiles/CMakeOutput.log".
FAILED: build.ninja
/home/fad03mhr3/Android/Sdk/cmake/3.18.1/bin/cmake --regenerate-during-build -S/home/fad03mhr3/Desktop/Apps/new_arch_13jan/node_modules/react-native/ReactAndroid/cmake-utils/default-app-setup -B/home/fad03mhr3/Desktop/Apps/new_arch_13jan/packages/react-native/android/app/.cxx/Debug/282a1w26/x86_64

C++ build system [build] failed while executing:
    /home/fad03mhr3/Android/Sdk/cmake/3.18.1/bin/ninja \
      -C \
      /home/fad03mhr3/Desktop/Apps/new_arch_13jan/packages/react-native/android/app/.cxx/Debug/282a1w26/x86_64 \
      appmodules
  from /home/fad03mhr3/Desktop/Apps/new_arch_13jan/packages/react-native/android/app
CMake Warning at /home/fad03mhr3/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
  An old version of CMake is being used that cannot automatically detect
  compiler attributes.  Compiler identification is being bypassed.  Some
  values may be wrong or missing.  Update to CMake 3.19 or newer to use
  CMake's built-in compiler identification.
Call Stack (most recent call first):
  /home/fad03mhr3/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
  /home/fad03mhr3/Desktop/Apps/new_arch_13jan/packages/react-native/android/app/.cxx/Debug/282a1w26/x86_64/CMakeFiles/3.18.1-g262b901/CMakeSystem.cmake:6 (include)
  CMakeLists.txt:28 (project)

CMake Error at /home/fad03mhr3/Desktop/Apps/new_arch_13jan/packages/react-native/android/app/build/generated/rncli/src/main/jni/Android-rncli.cmake:6 (add_subdirectory):
  add_subdirectory given source
  "/home/fad03mhr3/Desktop/Apps/new_arch_13jan/node_modules/react-native-gesture-handler/android/build/generated/source/codegen/jni/"
  which is not an existing directory.
Call Stack (most recent call first):
  /home/fad03mhr3/Desktop/Apps/new_arch_13jan/node_modules/react-native/ReactAndroid/cmake-utils/ReactNative-application.cmake:106 (include)
  CMakeLists.txt:31 (include)

CMake Error at /home/fad03mhr3/Desktop/Apps/new_arch_13jan/packages/react-native/android/app/build/generated/rncli/src/main/jni/Android-rncli.cmake:8 (add_subdirectory):
  add_subdirectory given source
  "/home/fad03mhr3/Desktop/Apps/new_arch_13jan/node_modules/react-native-svg/android/build/generated/source/codegen/jni/"
  which is not an existing directory.
Call Stack (most recent call first):
  /home/fad03mhr3/Desktop/Apps/new_arch_13jan/node_modules/react-native/ReactAndroid/cmake-utils/ReactNative-application.cmake:106 (include)
  CMakeLists.txt:31 (include)

CMake Error at /home/fad03mhr3/Desktop/Apps/new_arch_13jan/node_modules/react-native/ReactAndroid/cmake-utils/ReactNative-application.cmake:109 (target_link_libraries):
  Cannot specify link libraries for target
  "react_codegen_rngesturehandler_codegen" which is not built by this
  project.
Call Stack (most recent call first):
  CMakeLists.txt:31 (include)

ninja: error: rebuilding 'build.ninja': subcommand failed
	at org.gradle.internal.UncheckedException.throwAsUncheckedException(UncheckedException.java:68)
	at org.gradle.internal.UncheckedException.throwAsUncheckedException(UncheckedException.java:41)
	at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:107)
	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:242)
	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:157)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:47)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:68)
	at org.gradle.api.internal.tasks.execution.TaskExecution.executeAction(TaskExecution.java:227)
	at org.gradle.api.internal.tasks.execution.TaskExecution.executeActions(TaskExecution.java:210)
	at org.gradle.api.internal.tasks.execution.TaskExecution.executeWithPreviousOutputFiles(TaskExecution.java:193)
	at org.gradle.api.internal.tasks.execution.TaskExecution.execute(TaskExecution.java:171)
	at org.gradle.internal.execution.steps.ExecuteStep.executeInternal(ExecuteStep.java:89)
	at org.gradle.internal.execution.steps.ExecuteStep.access$000(ExecuteStep.java:40)
	at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:53)
	at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:50)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)
	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:157)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
	at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:50)
	at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:40)
	at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:68)
	at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:38)
	at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:48)
	at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:36)
	at org.gradle.internal.execution.steps.CancelExecutionStep.execute(CancelExecutionStep.java:41)
	at org.gradle.internal.execution.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:74)
	at org.gradle.internal.execution.steps.TimeoutStep.execute(TimeoutStep.java:55)
	at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:51)
	at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:29)
	at org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.execute(CaptureStateAfterExecutionStep.java:61)
	at org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.execute(CaptureStateAfterExecutionStep.java:42)
	at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:60)
	at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:27)
	at org.gradle.internal.execution.steps.BuildCacheStep.executeWithoutCache(BuildCacheStep.java:180)
	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:59)
	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:36)
	at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:25)
	at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:36)
	at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:22)
	at org.gradle.internal.execution.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:110)
	at org.gradle.internal.execution.steps.SkipUpToDateStep.lambda$execute$2(SkipUpToDateStep.java:56)
	at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:56)
	at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:38)
	at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:73)
	at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:44)
	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.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:89)
	at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:50)
	at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:114)
	at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:57)
	at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:76)
	at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:50)
	at org.gradle.internal.execution.steps.SkipEmptyWorkStep.executeWithNoEmptySources(SkipEmptyWorkStep.java:249)
	at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:86)
	at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:54)
	at org.gradle.internal.execution.steps.RemoveUntrackedExecutionStateStep.execute(RemoveUntrackedExecutionStateStep.java:32)
	at org.gradle.internal.execution.steps.RemoveUntrackedExecutionStateStep.execute(RemoveUntrackedExecutionStateStep.java:21)
	at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsStartedStep.execute(MarkSnapshottingInputsStartedStep.java:38)
	at org.gradle.internal.execution.steps.LoadPreviousExecutionStateStep.execute(LoadPreviousExecutionStateStep.java:43)
	at org.gradle.internal.execution.steps.LoadPreviousExecutionStateStep.execute(LoadPreviousExecutionStateStep.java:31)
	at org.gradle.internal.execution.steps.AssignWorkspaceStep.lambda$execute$0(AssignWorkspaceStep.java:40)
	at org.gradle.api.internal.tasks.execution.TaskExecution$4.withWorkspace(TaskExecution.java:287)
	at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:40)
	at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:30)
	at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:37)
	at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:27)
	at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:44)
	at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:33)
	at org.gradle.internal.execution.impl.DefaultExecutionEngine$1.execute(DefaultExecutionEngine.java:76)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:144)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:133)
	at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:77)
	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:56)
	at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)
	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:157)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
	at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:74)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:333)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:320)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:313)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:299)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.lambda$run$0(DefaultPlanExecutor.java:143)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:227)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:218)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:140)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
Caused by: com.android.ide.common.process.ProcessException: ninja: Entering directory `/home/fad03mhr3/Desktop/Apps/new_arch_13jan/packages/react-native/android/app/.cxx/Debug/282a1w26/x86_64'
[0/2] Re-checking globbed directories...
[1/2] Re-running CMake...
-- Configuring incomplete, errors occurred!
See also "/home/fad03mhr3/Desktop/Apps/new_arch_13jan/packages/react-native/android/app/.cxx/Debug/282a1w26/x86_64/CMakeFiles/CMakeOutput.log".
FAILED: build.ninja
/home/fad03mhr3/Android/Sdk/cmake/3.18.1/bin/cmake --regenerate-during-build -S/home/fad03mhr3/Desktop/Apps/new_arch_13jan/node_modules/react-native/ReactAndroid/cmake-utils/default-app-setup -B/home/fad03mhr3/Desktop/Apps/new_arch_13jan/packages/react-native/android/app/.cxx/Debug/282a1w26/x86_64

C++ build system [build] failed while executing:
    /home/fad03mhr3/Android/Sdk/cmake/3.18.1/bin/ninja \
      -C \
      /home/fad03mhr3/Desktop/Apps/new_arch_13jan/packages/react-native/android/app/.cxx/Debug/282a1w26/x86_64 \
      appmodules
  from /home/fad03mhr3/Desktop/Apps/new_arch_13jan/packages/react-native/android/app
CMake Warning at /home/fad03mhr3/Android/Sdk/ndk/23.1.7779620/build/cmake/android-legacy.toolchain.cmake:416 (message):
  An old version of CMake is being used that cannot automatically detect
  compiler attributes.  Compiler identification is being bypassed.  Some
  values may be wrong or missing.  Update to CMake 3.19 or newer to use
  CMake's built-in compiler identification.
Call Stack (most recent call first):
  /home/fad03mhr3/Android/Sdk/ndk/23.1.7779620/build/cmake/android.toolchain.cmake:55 (include)
  /home/fad03mhr3/Desktop/Apps/new_arch_13jan/packages/react-native/android/app/.cxx/Debug/282a1w26/x86_64/CMakeFiles/3.18.1-g262b901/CMakeSystem.cmake:6 (include)
  CMakeLists.txt:28 (project)

CMake Error at /home/fad03mhr3/Desktop/Apps/new_arch_13jan/packages/react-native/android/app/build/generated/rncli/src/main/jni/Android-rncli.cmake:6 (add_subdirectory):
  add_subdirectory given source
  "/home/fad03mhr3/Desktop/Apps/new_arch_13jan/node_modules/react-native-gesture-handler/android/build/generated/source/codegen/jni/"
  which is not an existing directory.
Call Stack (most recent call first):
  /home/fad03mhr3/Desktop/Apps/new_arch_13jan/node_modules/react-native/ReactAndroid/cmake-utils/ReactNative-application.cmake:106 (include)
  CMakeLists.txt:31 (include)

CMake Error at /home/fad03mhr3/Desktop/Apps/new_arch_13jan/packages/react-native/android/app/build/generated/rncli/src/main/jni/Android-rncli.cmake:8 (add_subdirectory):
  add_subdirectory given source
  "/home/fad03mhr3/Desktop/Apps/new_arch_13jan/node_modules/react-native-svg/android/build/generated/source/codegen/jni/"
  which is not an existing directory.
Call Stack (most recent call first):
  /home/fad03mhr3/Desktop/Apps/new_arch_13jan/node_modules/react-native/ReactAndroid/cmake-utils/ReactNative-application.cmake:106 (include)
  CMakeLists.txt:31 (include)

CMake Error at /home/fad03mhr3/Desktop/Apps/new_arch_13jan/node_modules/react-native/ReactAndroid/cmake-utils/ReactNative-application.cmake:109 (target_link_libraries):
  Cannot specify link libraries for target
  "react_codegen_rngesturehandler_codegen" which is not built by this
  project.
Call Stack (most recent call first):
  CMakeLists.txt:31 (include)

ninja: error: rebuilding 'build.ninja': subcommand failed
	at com.android.build.gradle.internal.cxx.process.ExecuteProcessKt.execute(ExecuteProcess.kt:274)
	at com.android.build.gradle.internal.cxx.process.ExecuteProcessKt$executeProcess$1.invoke(ExecuteProcess.kt:106)
	at com.android.build.gradle.internal.cxx.process.ExecuteProcessKt$executeProcess$1.invoke(ExecuteProcess.kt:104)
	at com.android.build.gradle.internal.cxx.timing.TimingEnvironmentKt.time(TimingEnvironment.kt:32)
	at com.android.build.gradle.internal.cxx.process.ExecuteProcessKt.executeProcess(ExecuteProcess.kt:104)
	at com.android.build.gradle.internal.cxx.process.ExecuteProcessKt.executeProcess$default(ExecuteProcess.kt:84)
	at com.android.build.gradle.internal.cxx.build.CxxRegularBuilder.executeProcessBatch(CxxRegularBuilder.kt:331)
	at com.android.build.gradle.internal.cxx.build.CxxRegularBuilder.build(CxxRegularBuilder.kt:128)
	at com.android.build.gradle.tasks.ExternalNativeBuildTask$doTaskAction$$inlined$recordTaskAction$1.invoke(BaseTask.kt:70)
	at com.android.build.gradle.internal.tasks.Blocks.recordSpan(Blocks.java:51)
	at com.android.build.gradle.tasks.ExternalNativeBuildTask.doTaskAction(ExternalNativeBuildTask.kt:136)
	at com.android.build.gradle.internal.tasks.UnsafeOutputsTask$taskAction$$inlined$recordTaskAction$1.invoke(BaseTask.kt:65)
	at com.android.build.gradle.internal.tasks.Blocks.recordSpan(Blocks.java:51)
	at com.android.build.gradle.internal.tasks.UnsafeOutputsTask.taskAction(UnsafeOutputsTask.kt:61)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:104)
	... 115 more
Caused by: com.android.ide.common.process.ProcessException: Error while executing process /home/fad03mhr3/Android/Sdk/cmake/3.18.1/bin/ninja with arguments {-C /home/fad03mhr3/Desktop/Apps/new_arch_13jan/packages/react-native/android/app/.cxx/Debug/282a1w26/x86_64 appmodules}
	at com.android.build.gradle.internal.process.GradleProcessResult.buildProcessException(GradleProcessResult.java:73)
	at com.android.build.gradle.internal.process.GradleProcessResult.assertNormalExitValue(GradleProcessResult.java:48)
	at com.android.build.gradle.internal.cxx.process.ExecuteProcessKt.execute(ExecuteProcess.kt:269)
	... 132 more
Caused by: org.gradle.process.internal.ExecException: Process 'command '/home/fad03mhr3/Android/Sdk/cmake/3.18.1/bin/ninja'' finished with non-zero exit value 1
	at org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:414)
	at com.android.build.gradle.internal.process.GradleProcessResult.assertNormalExitValue(GradleProcessResult.java:46)
	... 133 more

Version
0.71
Output of npx react-native info
System:
OS: Linux 5.15 Ubuntu 22.04.1 LTS 22.04.1 LTS (Jammy Jellyfish)
CPU: (16) x64 12th Gen Intel(R) Core(TM) i7-1270P
Memory: 8.95 GB / 30.60 GB
Shell: 5.1.16 - /bin/bash
Binaries:
Node: 16.15.1 - ~/.nvm/versions/node/v16.15.1/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 8.11.0 - ~/.nvm/versions/node/v16.15.1/bin/npm
Watchman: Not Found
SDKs:
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Languages:
Java: Not Found
npmPackages:
@react-native-community/cli: Not Found
react: Not Found
react-native: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
Upated the version to 0.71 using upgrade helper, enabled new architecture and got stuck with cmake issue
Snack, code example, screenshot, or link to a repository
react{
root = file("../../../../")
reactNativeDir = file("../../../../node_modules/react-native")
codegenDir = file("../../../../node-modules/react-native-codegen")
cliFile = file("../../../../node_modules/react-native/cli.js")
debuggableVariants = ["dev"]
hermesCommand = "$rootDir/my-custom-hermesc/bin/hermesc"
}
// added the follwoing in build.gradle

This is not a blank project apparently, as I see react-native-gesture-handler and react-native-svg in your setup.
Are you able to create a smaller reproducer?

no, when I tried to create a fresh project it worked fined. I need to get this implemented in my current project

I need to get this implemented in my current project

We can't really help without a reproducer.
I believe you haven't properly updated your build.gradle files, could you share them (the one on android/build.gradle and android/app/build.gradle)?

@cortinico is there any explicit requirement for enabling new arch with libraries, I am facing concerns with the libraries
react-native-screens
react-native-svg
react-native-gesturehandler

@cortinico I'm also facing same issue with @react-native-community/datetimepicker

I removed @react-native-community/datetimepicker and app ran successfully.

@cortinico is there any explicit requirement for enabling new arch with libraries, I am facing concerns with the libraries

Yes there are:

Libs that are including Native Modules can easily be included even if you're running with New Architecture enabled

Libs that are including Native Components instead need to be adapted to be New Architecture compatible, as otherwise they will render as a purple box with a warning message.

I'm not sure what I'm dowing wrong either. I'm still getting Could not get unknown property 'ExtractJniAndHeadersTask' for project ':ReactAndroid'

i have the same issue with @nodejs-mobile-react-native

this issue is still reproducable in 0.71.4

Closing as we don't have a reproducer here, so we can't fix anything. Please opne a new issue, provide a reproducer and we can look into what's the specific failure

Getting this error while creating final release build
My system and project configuration
System:
OS: Windows 10 10.0.22621
CPU: (8) x64 Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz
Memory: 4.83 GB / 15.85 GB
Binaries:
Node: 16.16.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - ~\OneDrive\Documents\AllProjects\uk_android\pirkx-uk-new\node_modules.bin\yarn.CMD
npm: 8.11.0 - C:\Program Files\nodejs\npm.CMD
Watchman: 20220918.223204.0 - C:\ProgramData\chocolatey\bin\watchman.EXE
SDKs:
Android SDK: Not Found
Windows SDK:
AllowAllTrustedApps: Enabled
AllowDevelopmentWithoutDevLicense: Enabled
IDEs:
Android Studio: AI-212.5712.43.2112.8609683
Visual Studio: Not Found
Languages:
Java: 11.0.14 - C:\Program Files\Common Files\Oracle\Java\javapath\javac.EXE
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: 0.71.4 => 0.71.4
react-native-windows: Not Found
npmGlobalPackages:
react-native: Not Found

You have to install cmake and need to add the same to PATH variable as described in following comment.

Configure project :react-native-firebase_app
:react-native-firebase_app package.json found at<EMAIL_ADDRESS>:react-native-firebase_app:firebase.bom using default value: 33.5.1
:react-native-firebase_app:play.play-services-auth using default value: 21.2.0
:react-native-firebase_app package.json found at<EMAIL_ADDRESS>:react-native-firebase_app:version set from package.json: 21.6.1 (21,6,1 - 21006001)
:react-native-firebase_app:android.compileSdk using custom value: 35
:react-native-firebase_app:android.targetSdk using custom value: 34
:react-native-firebase_app:android.minSdk using custom value: 24
:react-native-firebase_app:reactNativeAndroidDir /Users/inno/Desktop/myappnew/node_modules/react-native/android

Configure project :react-native-firebase_ml
:react-native-firebase_ml package.json found at<EMAIL_ADDRESS>:react-native-firebase_app package.json found at<EMAIL_ADDRESS>:react-native-firebase_ml:firebase.bom using default value: 33.5.1
:react-native-firebase_ml package.json found at<EMAIL_ADDRESS>:react-native-firebase_ml:version set from package.json: 21.6.1 (21,6,1 - 21006001)
:react-native-firebase_ml:android.compileSdk using custom value: 35
:react-native-firebase_ml:android.targetSdk using custom value: 34
:react-native-firebase_ml:android.minSdk using custom value: 24
:react-native-firebase_ml:reactNativeAndroidDir /Users/inno/Desktop/myappnew/node_modules/react-native/android

Task :app:externalNativeBuildCleanDebug FAILED
Clean appmodules-x86
C/C++: CMake Error at /Users/inno/Desktop/myappnew/android/app/build/generated/autolinking/src/main/jni/Android-autolinking.cmake:17 (add_subdirectory):
C/C++:   add_subdirectory given source
C/C++:   "/Users/inno/Desktop/myappnew/node_modules/react-native-permissions/android/build/generated/source/codegen/jni/"
C/C++:   which is not an existing directory.
C/C++: Call Stack (most recent call first):
C/C++:   /Users/inno/Desktop/myappnew/node_modules/react-native/ReactAndroid/cmake-utils/ReactNative-application.cmake:86 (include)
C/C++:   CMakeLists.txt:31 (include)
C/C++: CMake Error at /Users/inno/Desktop/myappnew/node_modules/react-native/ReactAndroid/cmake-utils/ReactNative-application.cmake:89 (target_link_libraries):
C/C++:   Cannot specify link libraries for target "react_codegen_RNPermissionsSpec"
C/C++:   which is not built by this project.
C/C++: Call Stack (most recent call first):
C/C++:   CMakeLists.txt:31 (include)
C/C++: ninja: error: rebuilding 'build.ninja': subcommand failed

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:externalNativeBuildCleanDebug'.

com.android.ide.common.process.ProcessException: ninja: Entering directory `/Users/inno/Desktop/myappnew/android/app/.cxx/Debug/296726yn/x86'
[0/2] Re-checking globbed directories...
[1/2] Re-running CMake...
-- Configuring incomplete, errors occurred!
See also "/Users/inno/Desktop/myappnew/android/app/.cxx/Debug/296726yn/x86/CMakeFiles/CMakeOutput.log".
FAILED: build.ninja
/Users/inno/Library/Android/sdk/cmake/3.22.1/bin/cmake --regenerate-during-build -S/Users/inno/Desktop/myappnew/node_modules/react-native/ReactAndroid/cmake-utils/default-app-setup -B/Users/inno/Desktop/myappnew/android/app/.cxx/Debug/296726yn/x86

C++ build system [clean] failed while executing:
/Users/inno/Library/Android/sdk/cmake/3.22.1/bin/ninja
-C
/Users/inno/Desktop/myappnew/android/app/.cxx/Debug/296726yn/x86
clean
from /Users/inno/Desktop/myappnew/android/app
CMake Error at /Users/inno/Desktop/myappnew/android/app/build/generated/autolinking/src/main/jni/Android-autolinking.cmake:17 (add_subdirectory):
add_subdirectory given source
"/Users/inno/Desktop/myappnew/node_modules/react-native-permissions/android/build/generated/source/codegen/jni/"
which is not an existing directory.
Call Stack (most recent call first):
/Users/inno/Desktop/myappnew/node_modules/react-native/ReactAndroid/cmake-utils/ReactNative-application.cmake:86 (include)
CMakeLists.txt:31 (include)
CMake Error at /Users/inno/Desktop/myappnew/node_modules/react-native/ReactAndroid/cmake-utils/ReactNative-application.cmake:89 (target_link_libraries):
Cannot specify link libraries for target "react_codegen_RNPermissionsSpec"
which is not built by this project.
Call Stack (most recent call first):
CMakeLists.txt:31 (include)
ninja: error: rebuilding 'build.ninja': subcommand failed

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 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.10.2/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

getting this error how i can fix it


more correctly dedent strings

Motivation

For the included testcase in this PR, Sorbet was parsing things as:
s(:begin,
  s(:class,
    s(:const, nil, :Session), nil,
    s(:begin,
      s(:assign,
        s(:casgn, nil, :MAX_OBJS),
        s(:int, "849201")),
      s(:assign,
        s(:casgn, nil, :MAX_OBJS_MSG),
        s(:dstr,
          s(:str, "There are more than "),
          s(:begin,
            s(:const, nil, :MAX_OBJS)),
          # BUG: we dropped a space here
          s(:str, "objects!  Fire the missiles!
"))))),
  s(:send, nil, :p,
    s(:const,
      s(:const, nil, :Session), :MAX_OBJS_MSG)))

This not-quite-correct parsing of heredocs is fine for the static checker, but not so much for the compiler.
This PR cargo-cults the dedent logic from whitequark's parser:
https://github.com/whitequark/parser/blob/b87613d2b99733e1400f076675daf501c19ede93/lib/parser/builders/default.rb#L358-L380
https://github.com/whitequark/parser/blob/b87613d2b99733e1400f076675daf501c19ede93/lib/parser/lexer/dedenter.rb#L36-L79
into our parser.
Test plan

There's a compiler testcase, which is fine, but every other testcase we have passes, which was surprising to me -- I would have expected some whitequark tests to transition from disabled to enabled.  Or do I have to reimport the upstream parser to add any necessary testcases?  Not really sure what to do here.
cc @vinistock who has worked on this stuff in the past.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_KZ7dZUc37p1dHu
→ https://go/builds/bui_KZ7dw8SQ01XHjM

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_KZ9qYCQ2HTxY05
→ https://go/builds/bui_KZ9qyCRtaTy1I4

The initial test build linked above were green, but an actual push that tested the compiler failed
I added another compiler testcase and https://go/builds/bui_KZA1UNurKW75Cy should be good.


Fix the shims

We cannot change the API of the types in XCTest+Shims.swift. Everything in this file is meant to reproduce XCTest's API on non-Apple platforms.


fix: inject annotations for service

the v1beta3 need this fix ?

the v1beta3 need this fix ?

v1beta3 don't hava this problem


[BUG] Using invalid currency on invoice creation makes invoice created with no payments connected

Basically the title.
On our demo, when someone has created an invoice with currency="string" (not possible via admin, it's via API), it has been created and stuck in pending, as it has no payments because of the error.
When no currency found, rate from electrum returns NaN
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/uvicorn/protocols/http/httptools_impl.py", line 391, in run_asgi
    result = await app(self.scope, self.receive, self.send)
  File "/usr/local/lib/python3.6/site-packages/uvicorn/middleware/proxy_headers.py", line 45, in __call__
    return await self.app(scope, receive, send)
  File "/usr/local/lib/python3.6/site-packages/fastapi/applications.py", line 181, in __call__
    await super().__call__(scope, receive, send)  # pragma: no cover
  File "/usr/local/lib/python3.6/site-packages/starlette/applications.py", line 111, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/usr/local/lib/python3.6/site-packages/starlette/middleware/errors.py", line 181, in __call__
    raise exc from None
  File "/usr/local/lib/python3.6/site-packages/starlette/middleware/errors.py", line 159, in __call__
    await self.app(scope, receive, _send)
  File "/usr/local/lib/python3.6/site-packages/starlette/middleware/base.py", line 25, in __call__
    response = await self.dispatch_func(request, self.call_next)
  File "/app/main.py", line 30, in add_onion_host
    response = await call_next(request)
  File "/usr/local/lib/python3.6/site-packages/starlette/middleware/base.py", line 45, in call_next
    task.result()
  File "/usr/local/lib/python3.6/site-packages/starlette/middleware/base.py", line 38, in coro
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.6/site-packages/starlette/middleware/cors.py", line 86, in __call__
    await self.simple_response(scope, receive, send, request_headers=headers)
  File "/usr/local/lib/python3.6/site-packages/starlette/middleware/cors.py", line 142, in simple_response
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.6/site-packages/starlette/exceptions.py", line 82, in __call__
    raise exc from None
  File "/usr/local/lib/python3.6/site-packages/starlette/exceptions.py", line 71, in __call__
    await self.app(scope, receive, sender)
  File "/usr/local/lib/python3.6/site-packages/starlette/routing.py", line 566, in __call__
    await route.handle(scope, receive, send)
  File "/usr/local/lib/python3.6/site-packages/starlette/routing.py", line 227, in handle
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.6/site-packages/starlette/routing.py", line 41, in app
    response = await func(request)
  File "/usr/local/lib/python3.6/site-packages/fastapi/routing.py", line 183, in app
    dependant=dependant, values=values, is_coroutine=is_coroutine
  File "/usr/local/lib/python3.6/site-packages/fastapi/routing.py", line 133, in run_endpoint_function
    return await dependant.call(**values)
  File "/app/api/utils.py", line 320, in post
    obj = await self.custom_methods["post"](model, user)
  File "/app/api/crud.py", line 87, in create_invoice
    await update_invoice_payments(obj, wallets, discounts, task_wallets, store, product, promocode)
  File "/app/api/crud.py", line 98, in update_invoice_payments
    price = invoice.price / await coin.rate(invoice.currency)
  File "/usr/local/lib/python3.6/site-packages/bitcart/coins/btc.py", line 344, in rate
    return convert_amount_type(await self.server.exchange_rate(currency))
  File "/usr/local/lib/python3.6/site-packages/bitcart/utils.py", line 18, in convert_amount_type
    return Decimal(amount)
decimal.InvalidOperation: [<class 'decimal.ConversionSyntax'>]

Actually, it seems like something else is happening. Maybe server returned html instead of a valid number?

Probably is fixed now


CSS won't center

Hey,
I am programming an experiment using jsPsych. I am working on adjusting the CSS for the text and am not able to get the text to center in the middle of the screen vertically. Even if I try to cheat and add paragraphs to get it to appear lower on the screen (instead of at the top), the program automatically scrolls down so the text is at the top. Do you know why that may be happening and how I can fix it? I have a task that uses the html-keyboard-response plugin to present one word on the screen at a time.
Thanks!

Can you please provide a reproducible example, and include information and browser/OS?
Have you included the jspsych.css file?

I'm closing this. But happy to reopen if a reproducible example is added.


Setting the canvas to overlay mode should be on the docs!

Hello!
I've been toying around with the inventory and it's very cool! I'm very thankful for it!
I've had some weird behavior with the controller because my canvas was not in overlay mode, and I think it'd be nice to be in the docs!

Hi!
Thank you for your thoughts. Im curios what this weird behavor was?
Hopefully its something that can be fixed.

Hi,
I just managed to track down and fixed this issue, and the inventory is now tested using all three canvas render modes (Screen Space Overlay, Screen Space Camera and World Space)


Compress and remove base64 encoding on answer store

What is the context of this PR?
Tests showed that the latency of some datastores increased significantly with the payload of the data being saved to/retrieved from it. DynamoDB slowed down almost linearly with the size of the payload.
This PR seeks to reduce that payload using two changes:

Compress the questionnaire store prior to encryption
No longer base64-encode the data prior to encryption (this didn't appear to be beneficial and increased the size of the payload)

The changes have been implemented to be backwards compatible. Existing questionnaire stores (base64-encoded and not compressed) should be still be readable by the application but will be written back using the new format.
How to review

Manually test the application
Attempt to resume a survey that was started using the old format and ensure that it can still be completed

Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

Data size in DynamoDB looks good. LMS 5 person household creates a 10kb object.

Tested 2 business surveys.  Both of them start to finish in one go; And another start (old version), save, restart (new version), finish.
Not approving yet because I've not done more testing then that and I think it should be looked at a bit more throughly

I'll fix the versioning on here


Design and implement agent management client-side library

Create an implementation of the Client interface: https://github.com/open-telemetry/opamp-go/blob/main/client/client.go
We want to implement this as a library which makes it easy for the agents to adopt the agent management solution. The library will be used by the Collector but we want to make it independent so that it can be used by other agents as well.
Tasks todo:

[x] https://github.com/open-telemetry/opamp-go/issues/17
[x] https://github.com/open-telemetry/opamp-go/issues/10
[x] https://github.com/open-telemetry/opamp-go/issues/8
[x] https://github.com/open-telemetry/opamp-go/issues/11

All listed tasks are done. The rest can be filed as new issues.


feat: append name to codestar notification rule to allow creating a unique name

to allow multiple notifications module instances to be attached to the same codepipeline

@kjagiello edits by maintainers allowed

Hi @kjagiello friendly reminder to try the workflows again on this one

@kjagiello bump :)

Sorry for the long wait. Pushed the fixes now and everything seems to be working fine again now 👍 Thanks for your contribution!

Great, thanks @kjagiello !


AUTISTIC MORON

bruh


Fix the docs so that the constants API example works

The createConstants(obj) example was passing in an array, and it could be confusing.

Thanks!


Translate eloquent-mutators page

Source: https://github.com/laravel/docs/blob/5.2/eloquent-mutators.md

working on this.

Added via 371c5a742dc613a73db16c9f85549bd63cacf70c


Pass formData parameters as keyword arguments

As already commented in https://github.com/zalando/connexion/issues/132 this PR adds support to pass formData parameters as keyword parameters to function handlers.

@jvgutierrez thanks for the PR! Could you resolve the conflicts please?

@hjacobs done :)

:+1: LGTM


Support nat_ref and reg_ref

I suggest that nat_ref and reg_ref be supported in addition to the standard ref. The most developer-friendly would probably be as an option that can be set when specifying a route shield for a specific network.. The tags have around 100 000 uses on taginfo each.
Why I'm opening this issue is because this support is need to properly support rendering of the E-road network as well as (local to me) Swedish county routes.
The E-road network officially uses e.g. E 04 as the ref, but in many countries, the leading zero is omitted and this is specified with nat_ref=E 4 on the route relation. Another solution could be to leave out any leading zeroes.
County routes in Sweden are tagged with both ref and reg_ref, where the ref is a unique identifier consisting of the county letter and a number, while reg_ref is just the number and can be the same reference in another county. E.g this road which has ref=E 580 and reg_ref=580. Note also that the letter can be E which a ref-based renderer would take as being an E-road when it is not. This is thankfully avoided by relying on network tagging, but the shown number should still be reg_ref, not ref.
If any other countries make use of these or similar special ref tags, feel free to also add that to this discussion.

We want to render shields with the same ref value shown real world shield signs, and this is the same as the value that should be in ref on the route relation.  If the signs have E 580 then the route relation should have ref=E 04 if the signs just have 580 then it should be ref=580 and the network value is used to specify the proper shield design.
I took a look at the linked road on street view imagery and didn't see any shields at all, so it seems this case should probably be using unsigned_ref instead of ref.

I see your point. I'll rethink my approach to this and work with the OSM data.


Please allow release note animations speed to be adjusted and stopped

I find release notes very difficult to read with all those animations frantically flashing away trying to show me their exciting new features.  Especially when it's a handful of text between two large flashing images.  Often I give up, which is a shame really cos I'd really like to know what's new.
It would be very nice to be able to click on something to say "please shut up, I'm reading something else", and "you're too quick, please slow down".

Is this for the release notes on the website or in product?

In VSCode itself.  I think I can probably do all this within a browser, but in VSCode the animations have no controls.

Not sure what we can easily do here. They are using video tags to add the controls. All our release note animations are gifs (we don't ship support for showing video in VS Code)


Integrate bubble correction

Purpose
This PR integrates the bubble correction feature from ClimaCore into ClimaAtmos.
Closes #1211
Content

[x] Added a dedicated CLI option, called --bubble (for now) false by default
[x] Modified driver to include new functionality in the suitable configurations (i.e., not in column configuration), and added warning when used with non suitable configurations.
[x] Modified regular and longrun pipelines (most tests including bubble will be those with Float64, as with Float32 this functionality does not provide much benefit, if at all).

Review checklist
I have:

followed the codebase contribution guide: https://clima.github.io/ClimateMachine.jl/latest/Contributing/
followed the style guide: https://clima.github.io/ClimateMachine.jl/latest/DevDocs/CodeStyle/
followed the documentation policy: https://github.com/CliMA/policies/wiki/Documentation-Policy
checked that this PR does not duplicate an open PR.

In the Content, I have included

relevant unit tests, and integration tests,
appropriate docstrings on all functions, structs, and modules, and included relevant documentation.

[x] I have read and checked the items on the review checklist.

The code changes look fine to me. I haven't looked at how the solutions change (none of the jobs have mse tables). Also, why does this significantly impact the baroclinic wave (ρe_tot) equilmoist check conservation float64 test?

Yeah, I am surprised that this is actually making conservation worse. I am investigating again in ClimaCore. Trying to reproduce on simpler examples.

Currently investigating this in ClimaCore (see relevant issue). I have temporarily put this in Draft state until this is cleared in ClimaCore.

This passes the conservation check after the suggested fix in ClimaCore (see successful build). As soon as we tag the new release of ClimaCore, I will update this branch Manifest

This PR is ready to merge. CI passes

bors r+


make man: Unknown target name: "create an issue"

I just tried locating the manpage for rainbowstream, and was having some trouble locating it, so I decided to compile it myself to check. Here's what I did:

$ git clone git@github.com:orakaro/rainbowstream.git
# (suppressed: The usual git clone output)
$ cd rainbowstream/
$ make man
make: *** No rule to make target 'man'.  Stop.
$ cd docs/
$ make man
Makefile:12: *** The 'sphinx-build' command was not found. Make sure you have Sphinx installed, then set the SPHINXBUILD environment variable to point to the full path of the 'sphinx-build' executable. Alternatively you can add the directory with the executable to your PATH. If you don't have Sphinx installed, grab it from http://sphinx-doc.org/.  Stop.
$ pip install --user sphinx-build
Collecting sphinx-build
Could not find a version that satisfies the requirement sphinx-build (from versions: )
No matching distribution found for sphinx-build
$ pip install --user sphinx
# (suppressed: The usual pip install output)
$ make man
sphinx-build -b man -d _build/doctrees   . _build/man
Running Sphinx v1.6.3
making output directory...
loading pickled environment... not yet created
building [mo]: targets for 0 po files that are out of date
building [man]: all manpages
updating environment: 1 added, 0 changed, 0 removed
reading sources... [100%] index
/home/waldyrious/.local/src/rainbowstream/docs/index.rst:68: WARNING: Unknown target name: "create an issue".
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
writing... rainbowstream.1 { }
build succeeded, 1 warning.
Build finished. The manual pages are in _build/man.

I left the command sequence pretty much intact, so you can identify potential friction points for newcomers, but the crucial part (the one this issue is reporting) is the warning

/home/waldyrious/.local/src/rainbowstream/docs/index.rst:68: WARNING: Unknown target name: "create an issue".

I'm not sure how that can be fixed (otherwise I'd submit a PR), but hopefully it's not too hard. Cheers!

By the way, while attempting to render the man page I had just generated, I got two warnings, but I'm not sure that warrants a new bug -- let me know:
$ groff -man -Tascii rainbowstream.1
rainbowstream.1:36: warning: can't find character with input code 226
rainbowstream.1:36: warning: can't find character with input code 166
RAINBOWSTREAM(1)                 RainbowStream                RAINBOWSTREAM(1)

NAME
       rainbowstream - RainbowStream Documentation

       Terminal-based  Twitter Client. Realtime tweetstream, compose, search ,
       favorite  and much more fun directly from terminal.

(rest of output clipped)


implement UnregisterMultiple

This is an implementation of UnregisterMultiple. The main reason this is needed is that RegisterMultiple uses a convention to register each type as a named type with the full name of the type. Therefore if you had previous registered a type using...
container.RegisterMultiple<TInterface>(new [] { type });

...you would then have to unregister the type using...
container.Unregister<TInterface>(type.FullName);

This is a little unintuitive. This PR allows you to unregister the type using...
container.UnregisterMultiple<TInterface>(new [] { type });

...which is the same syntax that the type was originally registered.

Could you please resolve the merge conflicts and well get this merged.


Remove hardcoded references to non public sources

In the main page there are hardcoded references to sample files that do require you to access non public sources.

Not sure what you're referring to, can you point out an example

Oh you mean this warning
vTools failed to load source map: Could not load content for chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/browser-polyfill.js.map: System error: net::ERR_FILE_NOT_FOUND


use staticHashCode to fix problems on Android but could occur elsewhere

Fixes #1650

Not sure if this is relevant here, but in another project I once ran into a performance problem, because Objects.hash(Object...) was creating lots of temporary Object[] instances.

Apparently this was also a problem under mac OS

but in another project I once ran into a performance problem, because Objects.hash(Object...)

Yeah. It is kind of ugly that this is now the default for IntelliJ as hashing should be very fast and lightweight


be deploy failure to b3lvs0506

I am encountering this issue. Hopefully its not my environment causing this but it appears to be the other side of the fence?
be cap b3lvs0506 deploy HOSTFILTER=bp-pmdh-b3lvs-05.inf.bulletproof.net
  * executing `b3lvs0506'
    triggering start callbacks for `deploy'
  * executing `multistage:ensure'
  * executing `deploy'
  * executing `deploy:update'
 ** transaction: start
  * executing `deploy:update_code'
    executing locally: "git ls-remote git@github.com:bulletproofnetworks/ript-rules.git HEAD"
  * executing "git clone -q git@github.com:bulletproofnetworks/ript-rules.git /etc/firewall/releases/20151029115703 && cd /etc/firewall/releases/20151029115703 && git checkout -q -b deploy 17ea66418946d32d8e0b587bedfe1d4c54872c37 && (echo 17ea66418946d32d8e0b587bedfe1d4c54872c37 > /etc/firewall/releases/20151029115703/REVISION)"
    servers: ["bp-pmdh-b3lvs-05.inf.bulletproof.net"]
    [bp-pmdh-b3lvs-05.inf.bulletproof.net] executing command
    command finished in 7191ms
  * executing `deploy:finalize_update'
  * executing "chmod -R g+w /etc/firewall/releases/20151029115703"
    servers: ["bp-pmdh-b3lvs-05.inf.bulletproof.net"]
    [bp-pmdh-b3lvs-05.inf.bulletproof.net] executing command
    command finished in 143ms
  * executing `deploy:symlink'
  * executing "rm -f /etc/firewall/current && ln -s /etc/firewall/releases/20151029115703 /etc/firewall/current"
    servers: ["bp-pmdh-b3lvs-05.inf.bulletproof.net"]
    [bp-pmdh-b3lvs-05.inf.bulletproof.net] executing command
    command finished in 108ms
 ** transaction: commit
    triggering after callbacks for `deploy'
  * executing `deploy:post'
Diff the rules
  * executing "sudo -p 'sudo password: ' rbenv-exec ript rules diff /etc/firewall/current/firewalls/b3lvs0506/customers"
    servers: ["bp-pmdh-b3lvs-05.inf.bulletproof.net"]
    [bp-pmdh-b3lvs-05.inf.bulletproof.net] executing command
Password:
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net]
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] Looks like you found a bug in Ript around line 9 in /opt/rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/ript-0.8.7/lib/ript/dsl/primitives/nat.rb
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] Specifically, this is the exception raised:
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net]
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] undefined method `[]' for nil:NilClass
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net]
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] And here is the backtrace:
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net]
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /opt/rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/ript-0.8.7/lib/ript/dsl/primitives/nat.rb:98:in `block (4 levels) in rewrite'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /opt/rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/ript-0.8.7/lib/ript/dsl/primitives/nat.rb:98:in `map'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /opt/rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/ript-0.8.7/lib/ript/dsl/primitives/nat.rb:98:in `block (3 levels) in rewrite'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /opt/rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/ript-0.8.7/lib/ript/dsl/primitives/nat.rb:97:in `each'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /opt/rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/ript-0.8.7/lib/ript/dsl/primitives/nat.rb:97:in `block (2 levels) in rewrite'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /opt/rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/ript-0.8.7/lib/ript/dsl/primitives/nat.rb:96:in `each'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /opt/rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/ript-0.8.7/lib/ript/dsl/primitives/nat.rb:96:in `block in rewrite'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /opt/rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/ript-0.8.7/lib/ript/dsl/primitives/nat.rb:75:in `each'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /opt/rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/ript-0.8.7/lib/ript/dsl/primitives/nat.rb:75:in `rewrite'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /etc/firewall/current/firewalls/b3lvs0506/customers/intershop.rb:34:in `block in <top (required)>'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /opt/rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/ript-0.8.7/lib/ript/partition.rb:39:in `instance_eval'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /opt/rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/ript-0.8.7/lib/ript/partition.rb:39:in `initialize'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /opt/rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/ript-0.8.7/lib/ript/partition.rb:160:in `new'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /opt/rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/ript-0.8.7/lib/ript/partition.rb:160:in `partition'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /etc/firewall/current/firewalls/b3lvs0506/customers/intershop.rb:1:in `<top (required)>'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /opt/rbenv/versions/1.9.2-p290/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:53:in `require'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net]
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /opt/rbenv/versions/1.9.2-p290/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:53:in `require'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /opt/rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/ript-0.8.7/bin/ript:81:in `block in <top (required)>'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net]
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /opt/rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/ript-0.8.7/bin/ript:80:in `each'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /opt/rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/ript-0.8.7/bin/ript:80:in `<top (required)>'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net]
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /opt/rbenv/versions/1.9.2-p290/bin/ript:23:in `load'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] /opt/rbenv/versions/1.9.2-p290/bin/ript:23:in `<main>'
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net]
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] Please report this bug at http://github.com/bulletproofnetworks/ript
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net]
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net]
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net] Aborting.
 ** [out :: bp-pmdh-b3lvs-05.inf.bulletproof.net]
    command finished in 2494ms
failed: "env RBENV_ROOT=/opt/rbenv PATH=/opt/rbenv/bin/:$PATH /bin/bash -c 'sudo -p '\\''sudo password: '\\'' rbenv-exec ript rules diff /etc/firewall/current/firewalls/b3lvs0506/customers'" on bp-pmdh-b3lvs-05.inf.bulletproof.net

Hi @joshbynon-bp, check out this line in your commit.
It should read from "intershop temp",  intershop temp 2", "intershop temp 3".
Let me know (re-open) if you've got any further trouble with this :+1:

Hi @nerdyness,
Appreciate that! silly me.
@davidmckenzie you approved this


Bottle Detail Page

Still need to work on the layout there.
Maybe 3 total columns?

1st column with bottle info
2nd column with date info
3rd column with image

Responsiveness - 2nd column underneath the 1st.

Also add bottle type.

Adding to this:
Button on the right of the  has some funky positioning on mobile. It's too low and sits on top of the hr. There is a margin-top:0.4rem; style that I'm sure is just not playing well with responsiveness.
Additionally, when responsive, the button shows the list icon and then "'s List". Is there a way on mobile to just get it to show the icon instead of the icon and whatever text fits?

Add a placeholder image on the page if there is no image for the bottle.

Closing this out, creating new ticket for the remaining bits.


Add success message

Error scenarios are currently not bubbled up to the bubbletea program. Merging this for now but needs a bit of rework, please. Would appreciate your help @mxsdev.

@sourishkrout Can you give an example test case?

@sourishkrout Can you give an example test case?

Oh snap. I ran the API locally and made the rate-limiting ultra-sensitive. Lemme think if there's an easier way.

Here's the issue. Please note how when the error occurs, it's being handled inside the Bubbletea program and upon quitting the error does not bubble up. It's probably a bubbletea thing. Not super important @mxsdev.
https://github.com/stateful/runme/assets/250527/6444bc54-5ee2-466c-8c6d-30edbf8b315e


use Pathname#cleanpath instead of Chef::Util::PathHelper.cleanpath

Fixes build failures on windows comparing backslashed paths with forward slashed glob patterns using ::File.fnmatch?. This now ensures that the paths being compared have forward slashes.

:shipit:

:+1:


 It keeps deleting all my data no mattter what method of delete I try.
I'm able to retrieve a subset of my graph from rdfstore.js via the following query:
SELECT * {
    ?subject app:rhymesWith ?object .
    FILTER (?subject = "word" || ?object = "word")
}

However, when I try to delete what I would think is the same subset of triples:
DELETE WHERE {
     ?subject app:rhymesWith ?object .
     FILTER(?subject = "word" || ?object = "word")
}

It deletes all data in my graph. I  tried many other methods including  the RDF Interface API:
this.store.graph('app:graph', async (err, graph) => {
                const rdf = this.store.rdf;

                 //deleteGraph  here even has the correct number of triples to delete
                let deleteGraph = graph.match(
                    null,
                    rdf.createNamedNode(rdf.resolve("app:rhymesWith")),
                    rdf.createLiteral(word));

                this.store.delete(deleteGraph);
            });

I've even  used DELETE DATA to try to delete a single triplet without any pattern matching:
    let data = `"${triple.subject}" app:rhymesWith "${triple.object}"`;
   let query = `DELETE DATA { GRAPH app:graph { ${data} } } `;

    this.store.execute(query);

No matter what I do, any kind of delete attempt deletes all the data. Very upsetting as I have invested a  quite bit of time into writing and querying the data, now I cant  delete anything and have to rewrite the whole thing in a diff lib.  Is there any solution at all?

@parliament718 Did you work further on a solution to this problem?  We're looking into using rdfstore-js too and data-deletion would be an important feature.
Did you try stepping through the code to see what was wrong, or have you only tried different ways of deleting content?
If you have alternative libraries which allow us to do similar things, I'd like to hear about them too.

@parliament718 Did you work further on a solution to this problem?  We're looking into using rdfstore-js too and data-deletion would be an important feature.
Did you try stepping through the code to see what was wrong, or have you only tried different ways of deleting content?
If you have alternative libraries which allow us to do similar things, I'd like to hear about them too.

@madnificent unfortunately no, I did not find any solution nor insight into this bug. Sorry, but if you do please let me know!


When SSL terminates at proxy (apache, nginx) Gogs serves pages as 404

If one uses apache or nginx for SSL termination, then Gogs returns the correct page but with a status of HTTP/1.1 404 Not Found.
For example although the page below obviously works, it is served as a 404 page:
$ curl -I https://try.gogs.io
HTTP/1.1 404 Not Found
Server: nginx/1.6.2 (Ubuntu)
Date: Sun, 01 Feb 2015 16:01:28 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: lang=en-US; Path=/; Max-Age=2147483647
...

I think that due to this, go get can't reach public repos behind apache/nginx terminated SSL:
$ go get try.gogs.io/test/Test
package try.gogs.io/test/Test: unrecognized import path "try.gogs.io/test/Test"

On my Gogs' logs I see:
$ ./gogs web
2015/02/01 15:54:06 [T] Custom path: /home/git/gogs/custom
2015/02/01 15:54:06 [T] Log path: /home/git/gogs/log
2015/02/01 15:54:06 [I] Gogs <IP_ADDRESS>3 Beta
2015/02/01 15:54:06 [I] Log Mode: Console(Trace)
2015/02/01 15:54:06 [I] Cache Service Enabled
2015/02/01 15:54:06 [I] Session Service Enabled
2015/02/01 15:54:06 [I] Mail Service Enabled
2015/02/01 15:54:06 [I] Register Mail Service Enabled
2015/02/01 15:54:06 [I] Notify Mail Service Enabled
2015/02/01 15:54:06 [I] SQLite3 Enabled
2015/02/01 15:54:06 [I] Run Mode: Production
2015/02/01 15:54:06 [I] Listen: http://<IP_ADDRESS>:3000
[Macaron] Started GET / for <IP_ADDRESS>, <IP_ADDRESS>
[Macaron] Completed / 200 OK in 3.148545ms
[Macaron] Started HEAD / for <IP_ADDRESS>
[Macaron] Completed / 404 Not Found in 2.224472ms

Thanks your report!

I think that due to this, go get can't reach public repos behind apache/nginx terminated SSL:

go get meta should be enabled manually in repository settings page, so I guess you didn't do that as I lookup in the page source code of try.gogs.io/test/Test.

On my Gogs' logs I see:

Based on your log, GET returns 200 because it is been registered as route.
HEAD didn't, which means HEAD is not allowed in / path, so it returns 404, as my understanding, should never exists.

Ah, thank you! After some more tries I made it work, I'm not sure what I did wrong in the past times. Maybe some caching layer in my stack prevented my repos from getting immediately “go getable” after changing the setting.
Sorry for the false alarm. I love gogs!

@andmarios no problem, thank you!


Modified FATE to allow transactions to run to completion without interruption

FATE processes transactions in an interleaved piece-wise manner. In the case of a multi-step transaction, FATE could potentially execute a step of another transaction before executing the next step of the current transaction. This change enables the developer to indicate via a new method on the Repo interface that the transaction type should be run start to finish without being interrupted.

This is draft because I want to get early feedback on approach.

This approach will tie up a FATE thread.  Another possible approach is to have a ZooStore.reserve() prefer transactions that are in an IN_PROGRESS state over those that are SUBMITTED (those have never run).  However it seems like scanning for in progress work  could do a lot more ZK reads.

That is not exactly what I was thinking. Was thinking of prioritizing FATEs that have started running over those that have never run when choosing what to run next.

Ah, ok, I didn't get that from our conversation.

I like the approach in this PR, except that it ties up a thread and could lead all FATE threads sleeping in the worst case.

Yeah, I'm curious how many FATE ops are going to take advantage of this. I'm assuming SPLIT and MERGE as they require the tablet to be un-hosted, so you want them to run as fast as possible so that the tablets can be re-hosted.  It would be trivial to put in an escape path, say if we have received a non-zero response from isReady N times in a row.

@dlmarion You requested my review on this, but I feel like it's a bit outside my area of expertise. I'd be interested in a discussion sometime, to get a high level understanding of it, though, along with what's motivating it. Right now, I don't have any opinions on the approach one way or another.

@dlmarion You requested my review on this, but I feel like it's a bit outside my area of expertise. I'd be interested in a discussion sometime, to get a high level understanding of it, though, along with what's motivating it. Right now, I don't have any opinions on the approach one way or another.

@ctubbsii - I wasn't sure if you were familiar with the FATE code or not. I figured you may also have some input on the behavior change.

@dlmarion I might have some thoughts, but I think I'd need it explained to me at an elementary level first. Mostly, though, I'm just curious to learn a bit more about where you're headed with this. I'm thinking maybe we can post another video meet in Slack some time, and discuss it with anybody interested in joining.

Superceded by #4589


Add torch.float8_e4m3fn format dtype_byte_size

What does this PR do?
This PR adds the torch.float8_e4m3fn in dtype_byte_size function, so that we can calculate the memory required for this specific datatype

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Nice! Note we need a check here, this dtype was only added in torch 2.1.0: https://github.com/pytorch/pytorch/commit/b64bd4a5dd9ee21d269997c4a28f6389870cd540


Rearchitect code base to easily optionally support additional tasks

Rearchitect code base to easily optionally support additional tasks, like KotlinCompile, ScalaCompile, etc., without downloading dependencies that are unnecessary for a build, and without errors.
Originally used a ServiceLoader SPI until @oehme mentioned it performs poorly & is brittle.
Ignore service providers that fail to load because their Task isn't in the Gradle class path (e.g., if the Kotlin plugin isn't applied, the KotlinCompile won't be in the class path, so the service provider for it will fail to load, which must not cause an error in Gradle).

Closing, as this plugin is no longer maintained.
Please open an issue on https://github.com/gradle/gradle for enhancement requests on the native Module support in Gradle 6.4+.


Cannot open settings window on Windows 10

I was successfully using imageDeCap for some time, but with new system installation can't setup image saving folder, because:

Looks like some GC issue, did you have any problems with this in the past?

Interesting. Thanks for contacting me :o
The screenshot you linked looks like the current version (1.23).
And not the most recent one (1.24) I tried writing my own "installer" in
1.23 that made a copy of the program in %appdata%/imageDeCap instead of
using an actual, normal installer.
The problem you are having should be fixable by going into the settings of
(1.23), clicking uninstall then closing the program and starting it up
again.
Ill make sure to have the new version delete the old one when it installs :)
On 22 Aug 2017 11:32, "Solidogen"<EMAIL_ADDRESS>wrote:

I was successfully using imageDeCap for some time, but with new system
installation can't setup image saving folder, because:
[image: issue]
https://user-images.githubusercontent.com/20575586/29558713-408dccd6-872d-11e7-82c4-4e8516662478.png
Looks like some GC issue, did you have any problems with this in the past?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Stinger21/imageDeCap/issues/77, or mute the thread
https://github.com/notifications/unsubscribe-auth/AKoEOZF0qN9MyZVjUr63Xsyh_rcAjzN5ks5saqAcgaJpZM4O-Wxk
.

Thanks, 1.24 gets me access to settings. I found bugs in gif mode, I'll share them


fix datalake user-agent

Pull Request Checklist
Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:
See the detailed list in the contributing guide.

[x] C++ Guidelines
[x] Doxygen docs
[x] Unit tests
[x] No unwanted commits/changes
[x] Descriptive title/description

[x] PR is single purpose
[x] Related issue listed

[x] Comments in source
[x] No typos
[x] Update changelog
[x] Not work-in-progress
[x] External references or docs updated
[x] Self review of PR done
[x] Any breaking changes?

/azp run cpp - storage

/check-enforcer override

/check-enforcer override

/check-enforcer override

/check-enforcer reset

/check-enforcer override

/check-enforcer --help

/check-enforcer help

/check-enforcer override


In which place i can add my url prioritizing strategy in frontera,. i couldn't find any clear documentation related to that.

i have one classification code and  i want to apply that code to each url during crawling and based on that it should decide whether to follow that url or omit that.

https://frontera.readthedocs.io/en/latest/topics/custom_crawling_strategy.html#writing-custom-crawling-strategy


Add missing doneCh in the example for removeobjects

We do not need a doneCh this code to meant to drain out all objects. Once there are no more objects the objectsCh is closed automatically.

Its producing the issue in the code because of the usage of doneCh var.
On Fri, Mar 23, 2018, 09:36 Harshavardhana<EMAIL_ADDRESS>wrote:

We do not need a doneCh this code to meant to drain out all objects. Once
there are no more objects the objectsCh is closed automatically.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/minio/minio-go/pull/955#issuecomment-375558954, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AADUxTlTSB7dU0Dz_7cx1P_MvHnenRGTks5thJf7gaJpZM4SwN4P
.

Also this same code is being fixed by another PR #949

Sorry this PR accidentally got closed...


Add magic shortcuts: 'is', 'add'

class Person {

  protected name { set, get  };
  protected age { set, get };
  protected male = true { set, is };
  protected phone { add, get };
  protected email { add, get };
}

$person = new Person;
$person->setName('Julia');
$person->setAge(21);
$person->setMale(false);

$person
    ->addPhone('0123456789')
    ->addEmail('julia@example.com');

echo 'Name: ' . $person->getName() .
     'Age: ' . $person->getAge() .
     'Sex: ' . ($person->isMale() ? 'Male' : 'Female') .
     'Phone: ' . $person->getPhone() .
     'Email: ' . $person->getEmail();

@steffengy what do you think about this? https://github.com/phalcon/zephir/issues/417

Refs https://github.com/phalcon/zephir/issues/1121

@andresgutierrez what do you think about it?

Why exactly this is still not merged ?

@andresgutierrez @sergeyklay Well asking above question again i guess.

@Jurigag https://github.com/phalcon/zephir/issues/1121#issuecomment-154507884

Yea but THIS IS PR, meaning implemented, so why not merge it?

Because there are no enough quorum

Oh, okay.

also the implementation of adding is as alias for get is quite strange.
is should always explicitly return a boolean.
Before merging this we should also come to a consensus
on what "magic shortcuts" we want.
I do not want 100's of them, but do not see an issue with adding
some, which certainly would reduce boilerplate.
These uncertainties in terms of the design are the main reason
this is still not merged (and also the reason why this should not be merged
until these are resolved).

Originally there was only add "magic shortcuts" in this PR.
I asked about difference between is and get https://github.com/phalcon/zephir/issues/1121#issuecomment-177171607 @sergeyklay just said:

better than

so I just created an alias to get. I didn't know about uncertainties.

@steffengy do we need to use backend->fetchProperty for returning bool in is shortcut? https://github.com/mruz/zephir/blob/e94c202b9a690234d6d4dbdceb919bb066123eb8/Library/Statements/ReturnStatement.php#L73

@mruz depends if the generated code is different for ZE3.
since it currently isn't in any backend-specific class, I guess it's not.

@steffengy how about this implementation for the is?

Cc: @phalcon/zephir-team

Good idea.
But "add" does the same as "set" so there is no use
"is" should only return a boolean not a value : return (bool) === true
@sergeyklay

When I created it, set did not return anything, so I added add, is should return bool.

@sergeyklay I can't rebuild failed build https://travis-ci.org/phalcon/zephir/builds/425215861?utm_source=github_status&utm_medium=notification, could you? or do we still need that PR?


Added watchdog for ping going into the peer_client.

If no pings are seen coming from the cloud after 30sec disconnect ws and reconnect. Monkey patch is kinda shitty but I couldn't find another way with how spdy doesn't expose the abstract connection that emits ping. Still gotta at some tests.
What's your thoughts on this approach? @mdobson @kevinswiber

Looks like a good approach to me.

I think this is the best approach we can do today.  There may be a different option when we upgrade to the 2.0 branch of the spdy library.  Thanks for whipping this together.


crf notebook and complete example

A linear chain crf notebook and example.

Do we want to commit a more minimal .ipynb - maybe one that doesn't have cells that have already all been run?

I think it's helpful to include cells that have been run-- more instructive.
On Wed, Oct 14, 2020 at 2:41 AM Jacob Kahn<EMAIL_ADDRESS>wrote:

Do we want to commit a more minimal .ipynb - maybe one that doesn't have
cells that have already all been run?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/facebookresearch/gtn/pull/26#issuecomment-707935092,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZFLOYCXUXVIJLLJRHIC2LSKSNOXANCNFSM4SNKLBPQ
.

I agree, I think we should keep the cells. Then it will render properly in GitHub and can be read without needing to run it. (It's not working properly right now for some reason, I'll need to investigate this).


[Bug]: Extra check 7.173 is listed as 'check' instead of 'extra'

What happened?
When I list Prowler checks with ./prowler -l, extra check 7.173 returns as check7173 instead of extra7173. This obviously leads to a failure if you use that ID ./prowler -c check7173.
How to reproduce it
Steps to reproduce the behavior:

./prowler -l
./prowler -c check7173

Expected behavior
The list of checks should return 7.173 as [extra7173] Security Groups created by EC2 Launch Wizard
Screenshots or Logs

From where are you running Prowler?

Resource: Workstation VM
OS: Ubuntu 20.04
AWS-CLI Version [aws --version]: aws-cli/2.4.11
Prowler Version [./prowler -V]: Prowler 2.10.0-25May2022

Additional context
The value of CHECK_TITLE_extra7173 should be changed to [extra7173] Security Groups created by EC2 Launch Wizard to avoid confusion.

Hi @vigah, thank you for notifying this. We're going to review it!


Fix incorrect URL's in panel (multilang)

When using a multilingual website, the URL's generated in the table of this index field point to the localized URL's.
But these don't work in the panel (when not in the default language) -> they should route to the URL in the default language.

lgtm, thanks!

Yw. Thx for the plugin! 🙌🏻
On 23 November 2017 at 20:44:50, Jon Gacnik<EMAIL_ADDRESS>wrote:
lgtm, thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jongacnik/kirby-index-field/pull/14#issuecomment-346688725,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAd8CTrQ-dpwhM_vDUxxm4kAR0c_gwNUks5s5csxgaJpZM4QofVz
.


plug FTL into teams generic storage

when the dust has settled splitting into 3 files for generic, ftl, and lightspeed would be great


Swiper doesn't worked

Hello there, I'm currently using SwiperJS with a CDN together
After i made a simple configurations it gives me a error that I don't understand!
This is the image as follows:

And this is my workspace:

Hopefully, there's alternative solution for this :)

Hello there, I'm currently using SwiperJS with a CDN together
After i made a simple configurations it gives me an error that I don't understand!
This is the image as follows:

And this is my workspace:

Hopefully, there's an alternative solution for this :)


[BUG] Can't load the plugin on IdeaPad Duet (Android version)

I can't load the plugin on Chromebook IdeaPad Duet (Android version)
I tried to reinstall, do a clean Obsidian install... Nothing work.

I'm sorry, I don't have access to an Android device to debug this. v6.7.5 does load on my iPhone, and generally iOS is more restrictive. If you can give me any further information I can try to fix it.

Someone on the Obsidian discord just said they could install and enable the plugin on their Android 9 device.

Hello, I tried again after updating everything, it still does not load (on my smartphone (Android) it does load), I only have problem with my Chromebook (The Linux version of the app doesn't work either for this machine as on my PC it work fine (Arch Linux)
If I can give more detail, I will do

Do you know what version of Android it is running?

I think it's Android 9

Do you know what version of Android it is running?

I think it's Android 9

Is this still an issue? I haven’t found anyone be able to reproduce this.

This is now fixed. It seems to come and go as update are applied. For now it's fixed


Training Instance Segmentation with 4-band (RGBA) images

I am trying to train Cascade Mask RCNN using a custom dataset in COCO format with 4 channel .tif files.  There is only a single class in the dataset.  I am looking for advice on what changes I need to make to the config (and other places?) to accommodate the 4 band imagery?  Also are there any pre-trained models that I can start with that have 4 bands or will I need to start from scratch?  Thank you for your help!

Generally a 3 channel input will be hard coded in each backbone, e.g. darknet.py line 121.
Then the data loader might also need to be adjusted to load the .tif files and preserve their RGBA format.  The data loader may already handle .tif images, but will convert them to 3 channel numpy arrays by default.
I don't think there is any additional performance to be gained from using RGBA images, it's another way to represent an image that has some convenience benefits for photo editing, but it doesn't contain additional information over RGB.

@PeterVennerstrom Thanks for your reply!  This is helpful info and confirms what I have gleaned from other Issues on the repo.  The images I am working with are 4-channel tiffs. They have RGB + Thermal as a fourth band.
So if I understand, I should be able to train a model from scratch is I 1) modify the data loader to retain the 4th channel and 2) modify the backbone to receive input with 4 channels?
I am hoping to train an instance segmentation model and was going to start with the config for Cascade Mask-RCNN..  Any chance you (or anyone) could point me toward the correct modifications to the backbone to use 4-channel images?

Resnet has an in_channels argument which is set to 3 by default.

Feel free to reopen the issue if there is any question


Improve dev setup and change create_response method

This pull request includes several changes to improve the development environment configuration and refactor the API code. The key changes involve updating the development container setup, modifying the VS Code launch configuration, enhancing the API HTTP test file, refining the Dockerfile for the API, and refactoring the main API file to use a Pydantic model.
Development environment configuration:

.devcontainer/devcontainer.json: Added a postCreateCommand to install Python dependencies, forwarded port 8000, and added Docker run arguments to use the host network.
.vscode/launch.json: Updated the launch configuration to set the current working directory and formatted arguments for the Uvicorn server.

API enhancements:

api-test.http: Introduced the @Host variable for the base URL and added a new POST request example with JSON body for testing the API.

Dockerfile updates:

src/api/Dockerfile: Added steps to copy and install the azure_core package from a local wheel file and ensured dependencies are installed without cache.

Code refactoring:

src/api/main.py: Refactored the create_response endpoint to use a Pydantic ChatRequestModel for request validation and added a TODO comment for future improvements.

This PR is Awesome! Thank you @mcollier


Dynamic prompts (e.g. using a vector store for memory)

Hi @mistercrunch
Thanks for building this, it's sorely needed.
I noticed it's targeted at static prompts (You can write the prompt directly into the code).
This means it's useful for unit tests, but not e2e tests of prompts that load some of their text from a similarity search on a vector DB or other.
I think this could be easy to fix by adding another test case that relies on an external function or API call to call the LLM. Right now after skimming the code, my guess is that the PromptCase speaks directly to OpenAI and so there's no room for external calls to modify the prompt.
I think this would be a super useful feature as a lot of applications are being built with this architecture and have the same problem you're trying to solve as you build it for Preset. I'm happy to work on it as well if you think it's something you'd add to the repo.
class DynamicPromptCase:
      pass

# Later
from promtimize.prompts import DynamicPromptCase,
from promptimize import evals

def enhance(prompt: str) -> str:
    context = "I like the following music the most: Organize by Asake (Afrobeats), Ride by Twenty-One Pilots (Band)."
    return f"Use the following context to answer my question\n{context}\n{prompt}"

simple_prompts = [
    DynamicPromptCase(
        "name my personal favourite band", enhance, lambda x: evals.all_words(x, ["Twenty-One Pilots"])
    ),
]

A more general version of this could also let you swap out OpenAI entirely, so that the original PromptCase you have becomes a special case of the DynamicPromptCase with pre-defined values like OpenAI, and no enhancements, etc.


buildSrc plugin using AWS conflicts with impldep AWS

Just tried to create a plugin under buildSrc that updates an AWS Lambda function, and it fails with java.lang.NoSuchFieldError: DOCUMENT when deserializing response from the AWS service due to MarshallingType interface being found in org.gradle.internal.impldep.com.amazonaws.protocol, which is of an older version than I'm using in buildSrc (2.17.15).
The problem is similar to that of BouncyCastle, #16605
Using Gradle 7.1, Java 11, Ubuntu 21.04.

Do you have the source of that plugin available so we can reproduce the problem. Or maybe create a stripped down reproducible sample to make reproducing this issue?

buildSrc/main/kotlin/foo
package foo

import org.gradle.api.DefaultTask
import org.gradle.api.GradleException
import org.gradle.api.provider.Property
import org.gradle.api.tasks.Input
import org.gradle.api.tasks.TaskAction
import org.gradle.kotlin.dsl.property
import software.amazon.awssdk.services.lambda.LambdaClient

open class AwsLambdaUpdateCodeTask : DefaultTask() {
	@Input val functionName: Property<String> = project.objects.property()
	@Input val imageUri: Property<String> = project.objects.property()

	@TaskAction
	fun execute() {
		if (!functionName.isPresent)
			throw GradleException("functionName is mandatory")
		if (!imageUri.isPresent)
			throw GradleException("imageUri is mandatory")

		val client = LambdaClient.create()

                         // breaks here when deserializing first message due to using wrong class
                        // java.lang.NoSuchFieldError: DOCUMENT
			client.updateFunctionCode { req ->
				req.functionName(functionName.get())
				req.imageUri("bah")
			}

			client.waiter().waitUntilFunctionUpdated { req ->
				req.functionName(functionName.get())
			}

	}
}

package foo

import org.gradle.api.Plugin
import org.gradle.api.Project

class AwsPlugin : Plugin<Project> {
	override fun apply(project: Project) {
		project.tasks.register("updateLambdaImage", AwsLambdaUpdateCodeTask::class.java)
	}
}

buildSrc/build.gradle.kts
plugins {
	`kotlin-dsl`
}

repositories {
	mavenCentral()
}

dependencies {
	implementation(libs.aws.sdk.lambda)
}

gradlePlugin {
	plugins {
		create("awsLambda") {
			id = "foo"
			implementationClass = "foo.AwsPlugin"
		}
	}
}

Annoying. Prepped a separate repo for this and it works. Do you have any suggestions on how to continue troubleshooting? It fails reliably in my main repository.
I've added the same set of plugins without apply: false to the top script, but without using them, hoping that will load them, added similar dependencies {} to the only subproject that uses the buildSrc plugin described here.
The main projects is close to a hundred of modules (i've made one in the test proj) so it's not really possible to create something identical, but it doesn't feel like dependencies {} should be causing this right? Those shouldn't be in the build system class path?
If plugins don't load even if omitting apply: false, then perhaps that might not be enough to determine if any other plugin is to blame.
The test proj doesn't use version catalog, but tried removing it from the main repo for buildSrc and that didn't change anything.


fix standalone browser build

something about the "umd" setting in recent versions of rollup
just doesn't work properly
verified this fixes things as expected and allows browser users to not have to do styled.default anymore: https://codesandbox.io/s/9q3pm157jw
closes #1870

Have following errors with integration tests after this merge:
$ jest -c .jest.integration.json --runInBand --forceExit
 FAIL  integration-test/jest-styled-components.test.js
  ● Test suite failed to run

    Cannot find module '..' from 'jest-styled-components.test.js'

      1 | // @flow
      2 | import React from 'react'
    > 3 | import styled from '..'
        | ^
      4 | import renderer from 'react-test-renderer'
      5 | import 'jest-styled-components'
      6 |

      at Resolver.resolveModule (node_modules/jest-resolve/build/index.js:221:17)
      at Object.<anonymous> (integration-test/jest-styled-components.test.js:3:1)

 FAIL  integration-test/example.test.js
  ● Test suite failed to run

    Cannot find module '..' from 'devServer.js'

      13 |
      14 | const srcPath = __dirname.split('/example')[0] + '/src'
    > 15 |
         | ^
      16 | const hotBuild = () =>
      17 |   exec('npm run build:dist', (err, stdout, stderr) => {
      18 |     if (err) throw err

      at Resolver.resolveModule (node_modules/jest-resolve/build/index.js:221:17)
      at Object.<anonymous> (example/devServer.js:15:9)

 FAIL  integration-test/styled-components-no-tags.test.js
  ● Test suite failed to run

    Cannot find module 'styled-components' from 'styled-components-no-tags.test.js'

      1 | import React from 'react'
      2 | import styled, { css } from 'styled-components'
    > 3 | import renderer from 'react-test-renderer'
        |      ^
      4 |
      5 | jest.mock('styled-components', () =>
      6 |   require('../dist/styled-components-no-tags.cjs')

      at Resolver.resolveModule (node_modules/jest-resolve/build/index.js:221:17)
      at Object.<anonymous> (integration-test/styled-components-no-tags.test.js:3:6)

Test Suites: 3 failed, 3 total
Tests:       0 total
Snapshots:   0 total
Time:        2.826s
Ran all test suites.
Force exiting Jest

Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "test:integration" exited with 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.


Multiple Files Upload with InputFile

Description of bug
When I upload multiple files with FileInput component, the file-data atribute get only one base64 file.
To Reproduce
I have used the component as follow:
<ModalForm onSubmit={handleSubmitFiles} encType="multipart/form-data">
      <FileInput
        type="file"
        name="files"
        id="files"
        multiple
        onStartProgress={handleProgress}
      />
      <Button type="submit"> Enviar </Button>
    </ModalForm>

Expected behavior
I expected several files to be uploaded and this would allow proper formatting with FormData.
Screenshots

Did you tested without "multiple" config?
That could show us if something else is wrong

Hello @denisprado, how are you?
We've released Unform 2.0 🎉
With this, unform does not exposes a FileInput component anymore, neither any other pre built component, so the user must create it's own inputs before using unform itself, we explain this inside the migration guide.
After you upgrade to Unform 2.0, you can create a MultipleFileInput using this code:
import React, { useRef, useEffect }  from 'react';

import { useField } from '@unform/core';

interface Props {
  name: string;
}

type InputProps = JSX.IntrinsicElements['input'] & Props;

const MultipleFileInput: React.FC<InputProps> = ({ name, ...rest }) => {
  const inputRef = useRef<HTMLInputElement>(null);

  const { fieldName, registerField, defaultValue, error } = useField(name);

  useEffect(() => {
    registerField({
      name: fieldName,
      ref: inputRef.current,
      path: 'files',
      getValue(ref: HTMLInputElement) {
        return ref.files && Array.from(ref.files);
      },
      clearValue(ref: HTMLInputElement) {
        ref.value = '';
      },
    })
  }, [fieldName, registerField]);

  return (
    <>
      <input
        multiple
        type="file"
        ref={inputRef}
        {...rest}
      />
    </>
  );
};

export default MultipleFileInput;

If you have any further questions please let me know.
I'll close the issue for now but feel free to reopen it or create new ones :)


Introduce cross product operation (three dimensions)

Vector cross products are quite difficult to calculate, so scoping this to three-dimensional vectors seems sane.
Though, there does seem to be an algorithm for calculating them in more dimensions, so perhaps that is something for a later date.

If you're going that way... ^^ https://github.com/YPares/gaast


Is o-ran compliant ietf-netconf-acm available?

Hi is sample xml file to configure ietf-netconf-acm as per O-ran specificatin available to control user access?

We are not providing anything like that because we have no reason to. If anyone it should probably be O-RAN to provide this, ietf-netconf-acm is a standard module.

We are not providing anything like that because we have no reason to. If anyone it should probably be O-RAN to provide this, ietf-netconf-acm is a standard module.


Upgrade to latest dependencies

upgrade to latest dependencies
Fix unit tests
Parse flags

/cc @Vishal-Chdhry @matzew @creydr


Pagination added

Added pagination system with basic styling for the pagination component.

Sorry, I didn't notice the new commit on main

Alright, now it looks good to merge! Thanks a lot for your valuable contribution😄🚀

No it's not, go back to the previous commit.

Now I solved it

No it's not, go back to the previous commit.

Why? What happened?

I did not merge search-feature and add-pagination

Now I solved it locally but i can't push

I reverted the merge, you should be able to push now👍🏻

To revert-8-add-pagination from a new pull request?

Yes, you will have to raise a new PR now.

But I can't see my add-pagination branch


Small regression / bug in 2.6.6 for id generation

Version

Vue version: Latest 3.x

Description
The changes you've added in 2.6.6 for "Added ${id}-dropdown to dropdown DOM" made it so if the id isn't specified, it adds undefined.

My suggestion would be to generate a unique ID if you need to have it at all times (better option, like id="skdngrk3ls9-dropdown"), or / and to have a check if the id is passed before creating a new id.

hi @adamberecz do we even need an id here ?)
https://github.com/vueform/multiselect/blob/main/src/Multiselect.vue#L173
Suggestion:

remove if not specified
use some https://github.com/ai/nanoid for default generation.