[nightly] [Android] Build issues with nightly

Describe the Bug
Every build was working normally with 3.2.0-3a28d48f50c4b5ad54ef96ca2c871bf3c7f51b3a.
Recently I tried updating to 3.2.0-c88c1cf470f4229dedf39dbb086f05bca60bce4c.
I can't get a successful build now.
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:mergeReleaseFirebaseJavaResource'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
   > More than one file was found with OS independent path 'META-INF/kotlin-audio_release.kotlin_module'.

* 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:mergeReleaseFirebaseJavaResource'.
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$3(ExecuteActionsTaskExecuter.java:186)
	at org.gradle.internal.Try$Failure.ifSuccessfulOrElse(Try.java:268)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:184)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:173)
	at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:109)
	at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
	at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:62)
	at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
	at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
	at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:62)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$call$2(DefaultBuildOperationExecutor.java:76)
	at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.callWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:54)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:76)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
	at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:41)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:411)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:398)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:391)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:377)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.lambda$run$0(DefaultPlanExecutor.java:127)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:191)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:182)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:124)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
Caused by: org.gradle.workers.internal.DefaultWorkerExecutor$WorkExecutionException: A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
	at org.gradle.workers.internal.DefaultWorkerExecutor$WorkItemExecution.waitForCompletion(DefaultWorkerExecutor.java:336)
	at org.gradle.internal.work.DefaultAsyncWorkTracker.waitForItemsAndGatherFailures(DefaultAsyncWorkTracker.java:142)
	at org.gradle.internal.work.DefaultAsyncWorkTracker.waitForItemsAndGatherFailures(DefaultAsyncWorkTracker.java:94)
	at org.gradle.internal.work.DefaultAsyncWorkTracker.waitForAll(DefaultAsyncWorkTracker.java:80)
	at org.gradle.internal.work.DefaultAsyncWorkTracker.waitForCompletion(DefaultAsyncWorkTracker.java:68)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$2.run(ExecuteActionsTaskExecuter.java:502)
	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$3.execute(DefaultBuildOperationRunner.java:75)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:71)
	at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.runWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:45)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:71)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:479)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:462)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.access$400(ExecuteActionsTaskExecuter.java:105)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution.executeWithPreviousOutputFiles(ExecuteActionsTaskExecuter.java:273)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution.execute(ExecuteActionsTaskExecuter.java:251)
	at org.gradle.internal.execution.steps.ExecuteStep.lambda$executeOperation$0(ExecuteStep.java:65)
	at org.gradle.internal.execution.steps.ExecuteStep.executeOperation(ExecuteStep.java:65)
	at org.gradle.internal.execution.steps.ExecuteStep.access$000(ExecuteStep.java:34)
	at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:47)
	at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:44)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:62)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$call$2(DefaultBuildOperationExecutor.java:76)
	at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.callWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:54)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:76)
	at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:44)
	at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:34)
	at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:72)
	at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:42)
	at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:53)
	at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:39)
	at org.gradle.internal.execution.steps.CancelExecutionStep.execute(CancelExecutionStep.java:44)
	at org.gradle.internal.execution.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:77)
	at org.gradle.internal.execution.steps.TimeoutStep.execute(TimeoutStep.java:58)
	at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:54)
	at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:32)
	at org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.execute(CaptureStateAfterExecutionStep.java:57)
	at org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.execute(CaptureStateAfterExecutionStep.java:38)
	at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:63)
	at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:30)
	at org.gradle.internal.execution.steps.BuildCacheStep.executeWithoutCache(BuildCacheStep.java:176)
	at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:76)
	at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:47)
	at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:43)
	at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:32)
	at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:39)
	at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:25)
	at org.gradle.internal.execution.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:102)
	at org.gradle.internal.execution.steps.SkipUpToDateStep.lambda$execute$0(SkipUpToDateStep.java:95)
	at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:55)
	at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:39)
	at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:83)
	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:96)
	at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:52)
	at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:83)
	at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:54)
	at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:74)
	at org.gradle.internal.execution.steps.SkipEmptyWorkStep.lambda$execute$2(SkipEmptyWorkStep.java:88)
	at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:88)
	at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:34)
	at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsStartedStep.execute(MarkSnapshottingInputsStartedStep.java:38)
	at org.gradle.internal.execution.steps.LoadExecutionStateStep.execute(LoadExecutionStateStep.java:46)
	at org.gradle.internal.execution.steps.LoadExecutionStateStep.execute(LoadExecutionStateStep.java:34)
	at org.gradle.internal.execution.steps.AssignWorkspaceStep.lambda$execute$0(AssignWorkspaceStep.java:43)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution$3.withWorkspace(ExecuteActionsTaskExecuter.java:286)
	at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:43)
	at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:33)
	at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:40)
	at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:30)
	at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:54)
	at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:40)
	at org.gradle.internal.execution.impl.DefaultExecutionEngine.execute(DefaultExecutionEngine.java:41)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$1(ExecuteActionsTaskExecuter.java:183)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:183)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:173)
	at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:109)
	at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
	at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:62)
	at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
	at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
	at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:62)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$call$2(DefaultBuildOperationExecutor.java:76)
	at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.callWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:54)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:76)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
	at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:41)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:411)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:398)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:391)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:377)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.lambda$run$0(DefaultPlanExecutor.java:127)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:191)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:182)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:124)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
Caused by: com.android.builder.merge.DuplicateRelativeFileException: More than one file was found with OS independent path 'META-INF/kotlin-audio_release.kotlin_module'.
	at com.android.builder.merge.StreamMergeAlgorithms.lambda$acceptOnlyOne$2(StreamMergeAlgorithms.java:85)
	at com.android.builder.merge.StreamMergeAlgorithms.lambda$select$3(StreamMergeAlgorithms.java:106)
	at com.android.builder.merge.IncrementalFileMergerOutputs$1.create(IncrementalFileMergerOutputs.java:88)
	at com.android.builder.merge.DelegateIncrementalFileMergerOutput.create(DelegateIncrementalFileMergerOutput.java:64)
	at com.android.build.gradle.internal.tasks.MergeJavaResourcesDelegate$run$output$1.create(MergeJavaResourcesDelegate.kt:236)
	at com.android.builder.merge.IncrementalFileMerger.updateChangedFile(IncrementalFileMerger.java:242)
	at com.android.builder.merge.IncrementalFileMerger.mergeChangedInputs(IncrementalFileMerger.java:203)
	at com.android.builder.merge.IncrementalFileMerger.merge(IncrementalFileMerger.java:80)
	at com.android.build.gradle.internal.tasks.MergeJavaResourcesDelegate.run(MergeJavaResourcesDelegate.kt:282)
	at com.android.build.gradle.internal.tasks.MergeJavaResRunnable.run(MergeJavaResRunnable.kt:81)
	at com.android.build.gradle.internal.tasks.Workers$ActionFacade.run(Workers.kt:242)
	at org.gradle.workers.internal.AdapterWorkAction.execute(AdapterWorkAction.java:57)
	at org.gradle.workers.internal.DefaultWorkerServer.execute(DefaultWorkerServer.java:63)
	at org.gradle.workers.internal.NoIsolationWorkerFactory$1$1.create(NoIsolationWorkerFactory.java:67)
	at org.gradle.workers.internal.NoIsolationWorkerFactory$1$1.create(NoIsolationWorkerFactory.java:63)
	at org.gradle.internal.classloader.ClassLoaderUtils.executeInClassloader(ClassLoaderUtils.java:97)
	at org.gradle.workers.internal.NoIsolationWorkerFactory$1.lambda$execute$0(NoIsolationWorkerFactory.java:63)
	at org.gradle.workers.internal.AbstractWorker$1.call(AbstractWorker.java:44)
	at org.gradle.workers.internal.AbstractWorker$1.call(AbstractWorker.java:41)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:62)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$call$2(DefaultBuildOperationExecutor.java:76)
	at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.callWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:54)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:76)
	at org.gradle.workers.internal.AbstractWorker.executeWrappedInBuildOperation(AbstractWorker.java:41)
	at org.gradle.workers.internal.NoIsolationWorkerFactory$1.execute(NoIsolationWorkerFactory.java:60)
	at org.gradle.workers.internal.DefaultWorkerExecutor.lambda$submitWork$2(DefaultWorkerExecutor.java:200)
	at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.runExecution(DefaultConditionalExecutionQueue.java:214)
	at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.runBatch(DefaultConditionalExecutionQueue.java:164)
	at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.run(DefaultConditionalExecutionQueue.java:131)
	... 3 more

Steps To Reproduce
Try to build with last nightly version.
Code To Reproduce
All I did was updating RNTP.
Replicable on Example App?
Can you replicate this bug in the React Native Track Player Example App?
I haven't tried this yet.
Environment Info:
Paste the results of npx react-native info
System:
    OS: macOS 12.6.3
    CPU: (10) x64 Apple M1 Max
    Memory: 29.75 MB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 14.15.0 - ~/.nvm/versions/node/v14.15.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v14.15.0/bin/yarn
    npm: 6.14.8 - ~/.nvm/versions/node/v14.15.0/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.11.3 - /Users/ramiro/.rbenv/shims/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
    Android SDK: Not Found
  IDEs:
    Android Studio: 2021.2 AI-212.5712.43.2112.8609683
    Xcode: 14.2/14C18 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.16 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: Not Found
    react-native: Not Found
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Paste the exact react-native-track-player version you are using 3.2.0-c88c1cf470f4229dedf39dbb086f05bca60bce4c
Real device? Or simulator? On simulator it's working fine. Can't build to test on a device.
What OS are you running? macOS Monterey 12.6.3
How I can Help
What can you do to help resolve this? I've been searching similar issues and tried solutions that didn't work.
Have you investigated the underlying JS or Swift/Android code causing this bug? Yes, but no clue on how to fix it.
Can you create a Pull Request with a fix? Not at the moment.

Try calling ./gradlew clean in your android directory

Try running ./gradlew clean in your android directory

Thank you for your answer. I did and got the same issue.

Looking at your logs it seems to be related to app:mergeReleaseFirebaseJavaResource which is not part of react native track player.. probably some kind of firebase related depedency

Looking at your logs it seems to be related to app:mergeReleaseFirebaseJavaResource which is not part of react native track player.. probably some kind of firebase related dependency

Worth saying that this only happens when I update RNTP, otherwise it's building fine. But I'll take a look, thank you.

Hmm there is indeed also this line which does point to rntp:
More than one file was found with OS independent path 'META-INF/kotlin-audio_release.kotlin_module'.
Perhaps try deleting that file?

How about using pick first instead: https://stackoverflow.com/a/44509662

Just tried with pickFirst. Same error.

Maybe it's worth asking: how are you upgrading? and if you are using yarn or npm?
...just guessing it might be a duplicate dependency problem caused by the way you are upgrading or by using both npm and yarn?

I don't use npm, only yarn. I'm updating by changing the version number in package.json and running yarn install. I have updated before by doing the same and didn't have this error. I even tried downgrading and it worked.

I'm open to try any ideas relly, so I tried this with the last release (3.2.0-4b83020b465d3e14f418e61e9f6043937d9410d5
Got the same error.

I'm open to trying any ideas really, so I tried this with the last release (3.2.0-4b83020b465d3e14f418e61e9f6043937d9410d5)
Got the same error.

Another thing I would try in your case is uninstalling the module and installing it again, with yarn commands.

I did yarn remove react-native-track-player, then yarn add react-native-track-player@nightly, then ./gradlew clean, then ./gradlew assembleRealease. Same error.

How does your yarn.lock file looks like? maybe it has accumulated different versions of RNTP?

@RamProg if you can reproduce this in the example project we can reopen this issue.


Fix missing peerDependency on react-dom

Closes #4934
✅ Pull Request Checklist:

[x] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:
Install package using Yarn Berry (2+). Observe warnings.
🧢 Your Project:

I've added to our script which checks all of our packages and found a few more that we'd missed. Thanks again for bringing it up.

@snowystinger Hmm, weird, I didn't get any other warnings besides the ones I found! Glad your script was able to though :D

Some are either part of the react-spectrum mono package, or aren't part of any mono package as they are pre-releases. I didn't want to forget about them later down the line. Hopefully this will keep us from having the same bug reopened :)


Linker Error

I fixed the compilation issues by doing #import <Foundation/Foundation.h> in some files. now I get a linker error
Undefined symbols for architecture armv7:
  "___isOSVersionAtLeast", referenced from:
      -[ATLApplicationListControllerBase _setUpSearchBar] in ATLApplicationListControllerBase.m.ee6620ba.o
      -[ATLApplicationSubtitleCell initWithStyle:reuseIdentifier:specifier:] in ATLApplicationSubtitleCell.m.ee6620ba.o
ld: symbol(s) not found for architecture armv7
clang-10: error: linker command failed with exit code 1 (use -v to see invocation)
make[3]: *** [/home/atrt7/theos/makefiles/instance/framework.mk:36: /home/atrt7/AltList/.theos/obj/armv7/AltList.framework/AltList] Error 1
rm /home/atrt7/AltList/.theos/obj/armv7/AltList.x.m
make[2]: *** [/home/atrt7/theos/makefiles/instance/framework.mk:36: /home/atrt7/AltList/.theos/obj/armv7/AltList.framework/AltList] Error 2
make[2]: *** Waiting for unfinished jobs....
==> Linking framework AltList (arm64)…
==> Generating debug symbols for AltList…
==> Stripping AltList (arm64)…
rm /home/atrt7/AltList/.theos/obj/arm64/AltList.x.m
make[1]: *** [/home/atrt7/theos/makefiles/instance/framework.mk:27: internal-framework-all_] Error 2
make: *** [/home/atrt7/theos/makefiles/master/rules.mk:117: AltList.all.framework.variables] Error 2```

probably has something to do with @available only working on macOS (sigh...), there is a possible fix for it here: https://github.com/theos/theos/issues/380

I should invest in a Mac lol

Making all for framework AltList…
==> Copying resource directories into the framework wrapper…
==> Copying public headers into the framework wrapper…
==> Preprocessing AltList.x…
==> Compiling AltList.x (armv7)…
In file included from :1:
/Users/azozzalfiras/opt/theos//Prefix.pch:11:11: fatal error:
'Foundation/Foundation.h' file not found
#import <Foundation/Foundation.h>
^~~~~~~~~~~~~~~~~~~~~~~~~
/Users/azozzalfiras/opt/theos//Prefix.pch:11:11: note: did not find header
'Foundation.h' in framework 'Foundation' (loaded from
'/System/Library/Frameworks')
1 error generated.

Making all for framework AltList…
==> Copying resource directories into the framework wrapper…
==> Copying public headers into the framework wrapper…
==> Preprocessing AltList.x…
==> Compiling AltList.x (armv7)…
In file included from :1:
/Users/azozzalfiras/opt/theos//Prefix.pch:11:11: fatal error:
'Foundation/Foundation.h' file not found
#import <Foundation/Foundation.h>
^~~~~~~~~~~~~~~~~~~~~~~~~
/Users/azozzalfiras/opt/theos//Prefix.pch:11:11: note: did not find header
'Foundation.h' in framework 'Foundation' (loaded from
'/System/Library/Frameworks')
1 error generated.

make sure you have a 13.0 sdk in $THEOS/sdks or change the sdk used here https://github.com/opa334/AltList/blob/main/Makefile#L3


Add dummy.go to istio stable

This patch adds dummy.go in third_party/istio-stable.
After this patch, other repo like knative/docs can pull the directory and
use install-istio.sh and manifest.
/cc @ZhiminXiang @JRBANCEL @mattmoor @tcnghia

https://github.com/knative/docs/pull/2889 tested this change. Especially these lines:

https://github.com/knative/docs/pull/2889/files#diff-69ef2e794e83216f7e132e4d4330e347R23-R25
https://github.com/knative/docs/pull/2889/files#diff-0bff8fdbdcedf4cfbdcab24558df0df2R22-R24


[BUG] $this->role is NULL

I got an strange bug.
I have an big DB (650k+) and connected it with Voyager.
What I did:

Installed Voyager
Created admin
Tried to browse admin (SUCCESS)
Tried to browse Database (FAIL)

I have an error in VoyagerUser Trait

When I dump the $this->role before IF statment - I see admin role object, it's ok. But on the next line (IF line) I get this error. Actually 2 times this functions works when I open Database page, so the first time I have an ROLE object and the second time I have NULL.
What I did:
I did a bad thing and added two lines of code (It's commented now)

When I remove these lines I get an error, when I enable it - every thing is perfect.
What is the problem? How can I refactor it so I dont have to write a code in the vendor?

I tried to override this function in my User model, but I get the same error if I remove my code from the vendor trait.
Any other solutions?

I honestly have no idea what your problem is.
Please use the issue template so we might understand you better.

@emptynick
https://github.com/the-control-group/voyager/issues/3962

Then I'm going to close this one.


DBZ-8375 Migrate rest of Debezium testsuite to async engine

https://issues.redhat.com/browse/DBZ-8375

DB2 test failu is not related.


Adaptive Dialogs. TextInput validation works for a single string only. Validation against a list of strings fails

Github issues should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.
Version
4.6.0-preview2
Describe the bug
Adaptive Dialogs. TextInput validation works for a single string only. Validation against a list of strings fails with an exception
To Reproduce
Steps to reproduce the behavior:
new TextInput()
{
Property = "turn.phoneSelection",
Prompt = new ActivityTemplate("[SelectPhone]"),
Validations = new List()
{
"equals(this.value,'Samsung')",
"equals(this.value,'Apple')",
"equals(this.value,'Huawei')"
},
InvalidPrompt = new ActivityTemplate("Sorry, {this.value} does not work. Can you give me a different brand name?"),
MaxTurnCount = 2,
AlwaysPrompt = true
},
Expected behavior
Expecting that the value validates against one from the list above
[bug]

@gbelenky This is by design. We process the validation expressions in the order they were specified, expect all validations to pass (if a list) in order for the input to be considered valid but fail validation as soon as one of the validation expressions fail.
For your specific use case, you could get this to work -
Validations = new List<string>()
 {
     "contains(createArray('samsung', 'apple', 'huawei'), toLower(this.value))"
 }

You can always use one of the many available pre-built functions as part of the common expression language


tests hang infinitely with 0.25.5 when dependency is missing, fail as expected on 0.25.4

Describe the bug
I have a codebase with a missing dependency where 0.25.4 fails as expected like this:

but 0.25.5 just hangs like this:

Reproduction
I can't share the repo, but if you are not able to reproduce on your own, I could prepare a repo for reproduction.
I think this happens when you try to load a dependency which is no specified in package.json, but it is in your node_modules.
System Info
System:
    OS: Linux 5.15 Ubuntu 22.04.1 LTS 22.04.1 LTS (Jammy Jellyfish)
    CPU: (24) x64 AMD Ryzen 9 5900X 12-Core Processor
    Memory: 25.73 GB / 62.74 GB
    Container: Yes
    Shell: 5.8.1 - /usr/bin/zsh
  Binaries:
    Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
    Yarn: 1.22.17 - ~/.yarn/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 108.0.5359.94
    Firefox: 107.0.1
  npmPackages:
    vite: ^3.2.4 => 3.2.5
    vitest: 0.25.5 => 0.25.5

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I can't share the repo, but if you are not able to reproduce on your own, I could prepare a repo for reproduction.
I think this happens when you try to load a dependency which is no specified in package.json, but it is in your node_modules.

Reproduction is always required. Please, don't make maintainers do extra work.

Reproduction is always required. Please, don't make maintainers do extra work.

I would not dream of it, I just thought some maintainer could be able to realize some recent commit could cause this without even trying to reproduce.
I tried to reproduce here: https://stackblitz.com/edit/vitest-dev-vitest-nva74f?file=vitest.config.ts
but failed. It runs ok on stackblitz.
For me it fails locally and on github CI too.
Can I keep the issue opened? Maybe someone else will be able to reproduce this issue. If I close this it is unlikely anyone would ever look at it even if they got a similar problem.

this is fixed in 0.25.6, thanks @sheremet-va


install: Return more user-friendly response on eexists

Most newcomers hit helm's 'feature' there deleted instalations are not really deleted.
Use-case
helm install  --name gitlab-ce-1 ./stable/gitlab-ce
helm delete gitlab-ce-1
helm list
helm install  --name gitlab-ce-1 ./stable/gitlab-ce
Error: a release named "gitlab-ce-1" already exists
There is a lot duplicated bugs in bugzilla which simply explains that packages
should be deleted with --pure flag. But such bugs appeared again and again
because this behavior is not obvious.
Let's help user to figure out what happens ASAP.

Again ci/circle fail. Is this expected?

Ok. I've updated the parent commit, so circleci is now happy.


Login moved from Django to Angular

Description:
#689
New imports / dependencies:

package

Unit Tests:

apps/volontulo/tests/views/test_auth.py

What tests do I need to run to validate this change:
Description of testing workflow and potential affected places.

@weronikafelczak generally speaking You need to:

Create proper /login route in Angular routing (see: https://github.com/CodeForPoznan/volontulo/blob/master/frontend/src/app/app.module.ts#L19)
Attach this route with newly created Angular component,
Create template for this component and most probably some css file
This template need to contain login form made in Angular
Business logic of this form need to be stored in mentioned above component
This component need to use AuthService as authorization provider (see: https://github.com/CodeForPoznan/volontulo/blob/master/frontend/src/app/auth.service.ts)
After creation of this route/component/tempalte You need to move all links to login from Django to Angular (see ANGULAR_ROOT in Django settings and djangoRoot in Angular)
Old login form need to be removed from login view or login view need to be removed at all from Django (if register form is already moved to Angular)
Old route for Django login (/o/login) need to be removed.

There a lot to do, but if You have done Angular tutorial, it's definetly in your reach. @Bosmanfrx or @radoslawroszkowiak will help You on todays meeting.

@weronikafelczak for unknown reason You have package.json.lock in this change. We don't use yarn, we use pretty old npm so it should not be generated.
I would say, that You use yarn or other npm not from container, but from your host environment.
You can ask @Bosmanfrx or @TrebuhD how to install dependencies inside docker container.

@weronikafelczak and You have multiple errors on Travis, see: https://travis-ci.org/CodeForPoznan/volontulo/builds/286648343

Codecov Report

Merging #692 into master will decrease coverage by 0.15%.
The diff coverage is 53.84%.

@@            Coverage Diff             @@
##           master     #692      +/-   ##
==========================================
- Coverage   91.77%   91.61%   -0.16%
==========================================
  Files          88       89       +1
  Lines        2661     2670       +9
  Branches        4        5       +1
==========================================
+ Hits         2442     2446       +4
- Misses        213      217       +4
- Partials        6        7       +1

Impacted Files
Coverage Δ

frontend/src/app/header/header.component.ts
50% <ø> (ø)
:arrow_up:

backend/apps/volontulo/tests/views/test_auth.py
100% <ø> (ø)
:arrow_up:

frontend/src/app/auth.service.ts
32% <20%> (-1.34%)
:arrow_down:

frontend/src/app/login/login.component.ts
75% <75%> (ø)

backend/apps/volontulo/views/offers.py
73.07% <0%> (+0.13%)
:arrow_up:

backend/apps/volontulo/models.py
78.75% <0%> (+0.68%)
:arrow_up:

Continue to review full report at Codecov.

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


UDP support coming?

Yeah, I had thought about this a while ago. Shouldn't be too difficult. What's your use case?

I have a program in a docker container that listens to udp

Any special requirements in terms of performance and throughput?

It would be nice if it could match nginx

What does that mean? Can you provide numbers?

Just a joke. As fast as possible is nice.

Not expecting nginx performance in immediate future

UDP proxy support is good for IoT. :)

Indeed

+1

It might come or it might not :P

I'll do it. Can't be that hard, can it? (famous last words)

As for use cases, I just came up with one. I'm planning on sending logs from my apps to logstash using GELF, and it uses UDP. Having Fabio in front of the Logstash cluster so I don't lose the logs while doing some maintentance or due to one node going down would be nice 👍

For information, i have a similary use case... and found this : http://gobetween.io/
It's just work... stable since one month... but not very active project.

Good to know, LordFPL. I'd rather not add another element to the mix, but if I have to, it's nice to see there are alternatives. But yeah, it doesn't seem to be very active, so I'll keep an eye on it just in case.
But if we had this and the GELF logger (PR 246), Fabio would be sending its logs through itself, hehehe.

@Verdoso Since UDP is a connectionless protocol fabio wouldn't buffer the data since it wouldn't know when data didn't get to the upstream server. I can have a look at the GELF logger in #246 and see if that is still ready to be merged.

Yes, I guess the balancing part is just using the consul stated to decide if one server should be sent or not packets. UDP being as it is, I doubt other proxies are doing more than that.
That could be enough. I'm checking also if going the tcp route would be performant enough.

I would like to respectfully ask if there was any progress on this issue (L4 UDP)?

I’m still in the middle of moving my family to another country and meeting a deadline. If someone from the community wants to jump in then this is a good opportunity. This should not be too difficult.
—
Frank Schröder

On 12. Jul 2018, at 06:30, pj<EMAIL_ADDRESS>wrote:
I would like to respectfully ask if there was any progress on this issue (L4 UDP)?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

This would be a really interesting solution for video game servers, especially with the ACLs we can set on remote IPs.  Being able to update in realtime which remote IPs should be permitted to even talk into a gameserver instance UDP port would be useful.  I'd seriously consider running all gameserver traffic through a Fabio instance running locally on a host.
Another use case is sending telemetry to statsd relays/servers (over UDP 8125, for instance).  Being able to provide high availability for those would make me sleep better at night ;)

Hey @magiconair was this still something you were interested in doing? I would really like this feature. Perhaps if you still don't have time I might find some time to work on it. I don't have a lot of experience with Go but I could try if you could point me in the right direction. Thank you :)

+1 would like to load balance UDP for Syslog, DNS, Kerberos.

Another use-case: I'm hoping to migrate a Minetest Server to my new Nomad + Consul Raspberry Pi cluster, which uses UDP.

+1 for UDP support

I just ran into this issue when I encountered my first service that uses UDP. My use-case was a Terraria server, which needs port 7777 on both TCP and UDP. The initial connection seems to be made using TCP, but then it stops there, unless I'm not routing it through fabio.

Quake

If nobody is working on this yet, I'd like to give it a try

I doubt anyone's working on it at the moment - it would be awesome if you could give it a go @mier85!

Would like UDP support for Consul + AlertManager mesh.
Forked...need time. @mier85 is maybe faster?

Any news?


load tree-sitter syntax parsers dynamically

See https://github.com/lapce/lapce/pull/481#pullrequestreview-967239975 and https://github.com/lapce/lapce/pull/481#issuecomment-1121609021

@jirutka I am :) but haven't started working on this yet, it's on my to-do list

Any progress on this?

I've started working on it but didn't had much time

Some food for thought. Can we compile the tree-sitter parsers into wasm modules and host them on a server for Lapce to download and use dynamically? Will the performance be acceptable?
As far as I understand it, to compile the parsers into native libraries on the target platform, i.e. .so on Linux, the end users will have to have the C toolchain. I think this is how Helix does. It could be a hurdle for those who use Lapce to write, say, JS or Python.

Tree-sitter parsers should be provided by (linux) distributions, as any other dependencies. For example, Alpine Linux already packages dozens of them.
My first reaction, I personally don’t like the idea of a text editor fetching some compiled code from the web. That said, if we look at them as plugins, Lapce providing some repository of verified and digitally signed WASM plugins, it does make sense.


Add support for used ips / port block allocations of a sourcenat rule

Hello,
Would it be possible to add support to show the amount of free port block allocations of an ip pool.
This is availble at the following ap and retuns the following items:
/api/v2/monitor/firewall/ippool?vdom=*&access_token=<token>
I am mainly interested in:
used: amount of port blocks used
total: amount of port blocks available
available(OPTIONAL): percentage (but not really needed as it can be calculated from 100-used/total)
natip_in_use: amount of ips in the pba in use
natip_total: amount of ips available in the pba pool
[
    {
        "http_method": "GET",
        "results": {
            "PBA_NAME": {
                "name": "PBA_NAME",
                "blocks": 8,
                "block_size": 128,
                "fixed_port": false,
                "pba_per_ip": 472,
                "used": 10,
                "total": 118472,
                "available": 99.991561889648438,
                "clients": 10,
                "natip_in_use": 1,
                "natip_total": 251
            }
        },
        "vdom": "Hotspot",
        "path": "firewall",
        "name": "ippool",
        "action": "",
        "status": "success",
        "serial": "serialhere",
        "version": "v7.0.11",
        "build": 489
    }
]

a 1:1 nat looks like this:
            "PUB_NAME": {
                "name": "PUB_NAME",
                "blocks": 1,
                "block_size": 60416,
                "fixed_port": true,
                "pba_per_ip": 1,
                "used": 1,
                "total": 1,
                "available": 0.0,
                "clients": 1,
                "natip_in_use": 1,
                "natip_total": 1
            },

@33Fraise33 I think this is possible, of course  @bluecmd decide on what to be included in the end. I would recommend that you try to implement it and make a pull request. I should be straight forward even if you are new to GO. @bluecmd has created a nice design of the fortigate exporter so you can just copy one of the "modules", e.g. https://github.com/bluecmd/fortigate_exporter/blob/master/pkg/probe/managed_switch.go in https://github.com/bluecmd/fortigate_exporter/tree/master/pkg/probe, and create your logic and then add it in https://github.com/bluecmd/fortigate_exporter/blob/master/pkg/probe/probe.go.

@33Fraise33 I think this is possible, of course @bluecmd decide on what to be included in the end. I would recommend that you try to implement it and make a pull request. It should be straight forward even if you are new to GO. @bluecmd has created a nice design of the fortigate exporter so you can just copy one of the "modules" as a starting point, e.g. https://github.com/bluecmd/fortigate_exporter/blob/master/pkg/probe/managed_switch.go in https://github.com/bluecmd/fortigate_exporter/tree/master/pkg/probe, and create your logic and then add it in https://github.com/bluecmd/fortigate_exporter/blob/master/pkg/probe/probe.go.

I did already implement some items in #214 but it was not really up to spec + it seems lots of MR's are currently stuck.

I'll try to make some time next week and go through the PRs that can be merged and try to review the ones that are pending. I appreciate people pushing for features, I've just been busy with other stuff.

The problem with PR #214 is that it's a large one with many smaller unralated things in it, making a minor issue in one of them block the whole PR.
I recommend you create a PR with this metric with tests, but nothing more. That way it should be an easy merge.

Hi @bluecmd I changed my PRs to be split up. I will now check if I can implement this feature request myself as well

:tada: This issue has been resolved in version 1.22.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


fix: Header label alignment fix

This PR fixes the header label alignment

Before
After

PR Checklist

[ ] I tested my changes on iOS and Android.
[ ] I added screenshots or videos to illustrate my changes.
[ ] I added Tests and Stories for my changes.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Need help with something? Have a look at our docs, or get in touch with us.

Actually, would it be possible to vertically align the icons to the top? They look a bit odd floating in the middle like that.

It looks a bit weird anyway but maybe we can improve this after our new Designer joins?

I mean go through the app and find things that potentially could be improved and address them all together


MTV-1537 | Optimalise the plan scheduler

Issue: When we start the warm migration with VM which has a lot of disks we wait for the whole VM to get migrated. We do not ignore the disks that has been already migrated. This can cause that when we have 2 VMs with 10 disks each and on each there is one larger disk the whole scheduler will be halted untill they finish. So even if the left 9 disks will be done no migration will be started.
Fix: Subtract the finished disks from the disk count.
Fixes: https://issues.redhat.com/browse/MTV-1537

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 13 lines in your changes missing coverage. Please review.

Project coverage is 16.26%. Comparing base (e3dbc9a) to head (4e53143).
Report is 4 commits behind head on main.

Files with missing lines
Patch %
Lines

pkg/controller/plan/scheduler/vsphere/scheduler.go
0.00%
13 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1088      +/-   ##
==========================================
- Coverage   16.27%   16.26%   -0.01%
==========================================
  Files         112      112
  Lines       19785    19793       +8
==========================================
  Hits         3220     3220
- Misses      16280    16288       +8
  Partials      285      285

Flag
Coverage Δ

unittests
16.26% <0.00%> (-0.01%)
:arrow_down:

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

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


[Suggestion] 1.20.1 Port

Not a bug, but a feature request; a port to 1.20.1? It's supposedly not too different to 1.19.4, as I've heard that "1.19.4 is basically a 1.20 snapshot".

It kinda is, I actually wanted to add 1.20 items in the current version, but j seem to have forgotten about this

Addressed with https://github.com/sa-shiro/Minecraft-Compressed-Blocks/commit/e28be9d121cf2a01adf23a73a02568b9250e7cc6


CPU utilization

IIRC when this ticket was created we collected CPU information not for the invocation or process, but for the container / VM. I believe we have since added process-level CPU utilization collection that's sampled at beginning and end of an invocation.
Profiling mostly solves the "in-between" case for per-invocation collection.

I am happy to close this, as I believe it's been resolved.


Poor performance with > 100 appointments in view

When displaying many appointments, the performance degrades pretty quickly

[ ] Optimize which components should be redrawn
[ ] Optimize logic to only perform calculations on the days/appointments that are being affected

Add @key to anywhere we're building components from a list

You should use Virtualize for a list of components. https://docs.microsoft.com/en-us/aspnet/core/blazor/components/virtualization?view=aspnetcore-5.0

Thanks for the suggestion @cptcrunchy but I'm not sure that'll be helpful in this case, that just unloads any components that aren't visible on the screen, I've already got a sort of method in place. The performance drop occurs when we're rendering 100s of components on the screen that NEED to be rendered.


Add feature:  '--verbose' key to jagger jenkins plugin for issue diagnostic purposes

That key should ask to print all actions the plugin do to the console.

@gd-sviatoslav wrong repo. see: https://github.com/griddynamics/jagger-jenkins-plugin


explain-where-bluebird-is-required

Where is the following dependency used?
"bluebird": "^3.4.1"

bluebird is a promise module. see its usage here: sqldb/index.js

search for this 'Bookshelf uses its own copy of the "bluebird" promise library' - http://bookshelfjs.org
if bookshelf comes with bluebird bundled-in why it was required to add it again?

I am not necessarily saying to remove bluebird from package.json just to understand what 'Bookshelf uses its own copy of the "bluebird" promise library' means and, if we leave it there because it will probably be useful later, what are the changes of getting "conflicts" with the bookshelfjs built in version.

understand, let me explain :)
when creating module, we shouldn't depend on other packages to define the dependency for us, even though they have it. The reason because:

What if in the future bookshelfjs decides to change their implementation to use other promise module? This will cause our app to break, because we assume bookshelfjs to use bluebird which might not be the case
This tells us we explicitly tells our app to depend on bluebird as one of our app dependency. in the future, if we decide to use other promise module, we can do so and need to update our package.json to refer to the new module such as 'q' module

If you worry about "conflict", worry not, because in this case, the promise doesn't has anything to do with bookshelf and use solely for one of the method. Plus, the way npm works is each package will have their own package version, in this case, bookshelfjs will refer to their own bluebird package version, and our app will refer to our own bluebird package. i.e. you can see in node_modules/bookshelfjs, they also have their own node_modules folder.
Hope that clears.


Add column names to lin_samples.csv

Add missing column names to lin_samples.csv
This will be done automatically with the updated script at #67
cc @joshmoore

The csv at https://raw.githubusercontent.com/ome/ome2024-ngff-challenge/main/samples/lin_samples.csv took a while for the cache to invalidate/update.
Now working well: NB: filtering by "Drosi" finds most of the samples:


BTC

I'm not sure what this issue is asking. Please use the issue templates when creating a new issue, or ensure your problem is clearly stated


Test refactoring

Resolves #37 #101

Please review @xstefank @The-Huginn

@petrberan perhaps you can have a look at #121 to resolve it here with additional test for the specified examples.

Changes resolved as advised @The-Huginn , you can have a look

@xstefank It should be ready for your review/approval


ERROR [RpcService] rpc error, Request failed with status code 503, {"jsonrpc":"1.0","id":1726048398876,"method":"getblockchaininfo","params":[]}

how to solve the issue with tracker ?

Start tracker dependency

opcatbugcloser

#25  not solved, what does this mean?


Docs.MS Release Updates for azure_mgmt_redis

Update docs metadata and targeting for release of azure_mgmt_redis

Docs Build status updates of commit 6df3c21:
:clock10: Full build: the average full build time is 197 min(s) 11 sec(s), this is based on the last 677 build(s) for this repository.

Docs Build status updates of commit 6df3c21:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/mgmt-redis-readme-pre.md
:warning:Warning
View (azure-python) View (azure-python-preview)
Details

docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.call_http.yml
:warning:Warning
View (azure-python)
Details

docs-ref-autogen/azure-functions/azure.yml
:warning:Warning
View (azure-python)
Details

ci-configs/packages-preview.json
:white_check_mark:Succeeded

docs-ref-services/mgmt-redis-readme-pre.md

Line 13: [Warning-h1-not-first] Markdown content is not allowed before {0}.
Line 13: [Warning-h1-not-first] Markdown content is not allowed before {0}.
Line 14: [Warning-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.
Line 14: [Warning-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.

docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.call_http.yml

[Warning-DuplicateUids] Uid(azure.durable_functions.tasks.call_http) has already been defined in docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.yml.

docs-ref-autogen/azure-functions/azure.yml

[Warning-DuplicateUids] Uid(azure) has already been defined in docs-ref-autogen/azure-functions-durable/azure.yml.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Closing in favor of this commit.


Added exhibitor TLS conf

Exhibitor modifications. See https://github.com/mesosphere/dcos-enterprise/pull/1422.
High Level Description
What features does this change enable? What bugs does this change fix? High-Level description of how things changed.
Related Issues

DCOS-17894 Encrypt & authenticate cross-Exhibitor communication (1.11).

Checklist for all PR's

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here: No new functionality.
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot Ready For Review

Ship-it was applied prematurely. See DCOS-19252.

It sounds like this PR is blocked by https://jira.mesosphere.com/browse/DCOS-18703? It switches
MASTER_SOURCE=exhibitor_uri to MASTER_SOURCE=master_list.
Doing so seems wrong: where does it get master_list from if the cluster is not using the static backend?

@mesosphere-mergebot bump-ee

@jgehrcke please close this now that https://github.com/dcos/dcos/pull/2098 was merged.


docs: A few enhancement ideas

Document that double-quotes are not valid characters on Windows. If you template a file/dir name and need to use quotes, use single quotes.
Document that templated file names must end with the configured template suffix anyway:

{% if thing %}this_file.jinja{% endif %}: bad
{% if thing %}this_file{% endif %}.jinja: good

Document that, contrary to files, directories don't have to (or must not? need to verify) end with the configured template suffix:

{% if thing %}this_dir{% endif %}: works OK

(related to the two previous points, maybe there are possible UX improvements to do?)
Document the available native Jinja2 extensions:

expression statement (too bad there's no link to actual use in this paragraph). Can be used to alter the context (answers, filters, etc.). The file containing such modifiers has to be handled first, so file name should be aaaa or something. The file should also be removed by a post-processing task. Better than that: use my copier-templates-extensions loader, which is easier to use 😛
loop controls
debug extension
more generally, the extensions page 🙂

Another idea: link to the site where you can get versioned docs

The "Creating a template" page also definitely lacks examples of template contents. I'll see if I can use the minimal example in the README to provide some more complete recipes.

I can add a dark/light theme switch button as well if you fancy it.

Both seem good enhancements, thanks!
The dark mode can't be automatic when the browser is dark?

Yes it can! It will detect the user preference and use that by default.

El jue, 6 de ene de 2022 a las 09:42:00 AM, Timothée Mazzucotelli
@.***> escribió:

Yes it can! It will detect the user preference and use that by
default.

cool!

A couple more ideas:

Version dropdown/link. I like https://squidfunk.github.io/mkdocs-material/setup/setting-up-versioning/ but maybe that's not applicable for us, as we use readthedocs. Maybe just a link in the header to https://readthedocs.org/projects/copier/ would be enough.
Correct version number in the "latest" version, fixing the problem explained in https://github.com/mkdocstrings/pytkdocs/issues/122.

Asked here: https://github.com/squidfunk/mkdocs-material/discussions/3439


Add DARTRange

https://github.com/Galileo88/DART-Project
https://forum.kerbalspaceprogram.com/index.php?/topic/205456-1120-dart-range-challenge-100-01-nov-2021/

This mod includes custom forks of several plugins. We have assurances from the authors that they won't conflict with the standard plugins. :crossed_fingers:

See Galileo88/DART-Project#5 for the remote AVC error.

SQUAD says they "have partnered with NASA and Galileo—creator of great ad-on such as Galieo’s Planet Pack and JNSQ—with a team of experienced KSP modders to bring you the possibility to recreate the DART mission in the KSP universe."
https://forum.kerbalspaceprogram.com/index.php?/topic/205463-nasa-dart-challenge/


Using WhichOneof when parsing a Value protobuf.

NOTE: Has #1461 as diffbase.
Relates to discussion in #1402.

LGTM


Create CVAT instance with analytics support

The documentation states

If your CVAT instance was created with analytics support, you can press the Analytics button in the dashboard and analytics and journals will be opened in a new tab.
(https://opencv.github.io/cvat/docs/manual/advanced/analytics/)

But there is no guide on how to create the instance with analytics support. Can someone give me a hint or make the documentation a bit clearer at this point?

@azhavoro
Could you please comment on that?

Never mind. I figured out there was a permission issue, after resolving that I was able to start the grafana docker and the analytics tab worked. :+1:

Hi，I cann't open analytics tab, and I guess the issue is also permission issue. Could you give some methods on how you resolved your permission issue?

There is also a bit more documentation here: https://opencv.github.io/cvat/docs/administration/advanced/analytics/
I saw that there was one permission error in the docker logs, I don't remember but maybe it was the grafana_conf.yml. Just edit the permissions and start again, it should work.

@zhouyuangan A few days ago, I cleared docker and reinstalled cvat. In this process, I did not do any steps other than the official requirements, and then it worked. However, after the GPU automatic update yesterday, the analysis interface could not be opened again....


Throws NREs in console on load as of v50 beta

As title says. Says failed to patch content.

This is a known issue, I'm considering deprecating this mod, because:

v50 has fixed the largest problems with shotgun hit registration, which is why the patches fail now.
Matty's AdditionalNetworking mod will hopefully fix the desync of the safety and ammo count that this mod contains networking patches for.

The only things that this mod does that I can think of at the moment which will still have an effect in v50 are:

It decreases the possibility of multiple blobs or enemy corpses in your area causing a non-registering shot (this is very unlikely in practice)/
It prevents blobs from making a bunch of angry sounds at once, which can be annoying but probably doesn't affect performance too much.

Whatever the case may be, I won't deprecating or updating it for v50 until that version of the game is considered stable by Zeekers.

The mod has been deprecated on the store for a while, but I forgot to come back and close this.


[Bug] How to improve the first frame response speed TTFT

Checklist

[X] 1. I have searched related issues but cannot get the expected help.
[X] 2. The bug has not been fixed in the latest version.
[X] 3. Please note that if the bug-related issue you submitted lacks corresponding environment info and a minimal reproducible demo, it will be challenging for us to reproduce and resolve the issue, reducing the likelihood of receiving feedback.

Describe the bug
Is there still room to improve the first frame response speed TTFT
I use 5 threads, each with 80000 tokens. The first frame response time after hitting the cache is 2-5 seconds. Do you have any optimization strategies
Currently, there is only one A800 graphics card available
Reproduction
Model: Qwen2__v5-14B-Structure-AWQ
Command: CUDA_VISIBLE_DEVICES=5 lmdeploy serve api_server /mnt/qwen2.5/qwen14bInt/Qwen/Qwen2___5-14B-Instruct-AWQ   --backend turbomind   --server-port 35551   --model-name qwenInt4   --model-format awq   --session-len 100000   --cache-block-seq-len 128 --enable-prefix-caching   --cache-max-entry-count 0.8 --log-level INFO  --quant-policy=4 --rope-scaling-factor 4.0 >> /mnt/qwen2.5/qwenInt4/qwen14btmp2.txt 2>&1
Environment
sys.platform: linux
Python: 3.10.14 (main, May 29 2024, 23:47:02) [GCC 11.4.0]
CUDA available: True
MUSA available: False
numpy_random_seed:<PHONE_NUMBER>
GPU 0,1,2,3,4,5,6,7: NVIDIA Graphics Device
CUDA_HOME: /usr/local/cuda
NVCC: Cuda compilation tools, release 12.1, V12.1.105
GCC: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
PyTorch: 2.3.1+cu121
PyTorch compiling details: PyTorch built with:
  - GCC 9.3
  - C++ Version: 201703
  - Intel(R) oneAPI Math Kernel Library Version 2022.2-Product Build 20220804 for Intel(R) 64 architecture applications
  - Intel(R) MKL-DNN v3.3.6 (Git Hash 86e6af5974177e513fd3fee58425e1063e7f1361)
  - OpenMP 201511 (a.k.a. OpenMP 4.5)
  - LAPACK is enabled (usually provided by MKL)
  - NNPACK is enabled
  - CPU capability usage: AVX512
  - CUDA Runtime 12.1
  - NVCC architecture flags: -gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_80,code=sm_80;-gencode;arch=compute_86,code=sm_86;-gencode;arch=compute_90,code=sm_90
  - CuDNN 8.9.2
  - Magma 2.6.1
  - Build settings: BLAS_INFO=mkl, BUILD_TYPE=Release, CUDA_VERSION=12.1, CUDNN_VERSION=8.9.2, CXX_COMPILER=/opt/rh/devtoolset-9/root/usr/bin/c++, CXX_FLAGS= -D_GLIBCXX_USE_CXX11_ABI=0 -fabi-version=11 -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -DNDEBUG -DUSE_KINETO -DLIBKINETO_NOROCTRACER -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -O2 -fPIC -Wall -Wextra -Werror=return-type -Werror=non-virtual-dtor -Werror=bool-operation -Wnarrowing -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-unused-parameter -Wno-unused-function -Wno-unused-result -Wno-strict-overflow -Wno-strict-aliasing -Wno-stringop-overflow -Wsuggest-override -Wno-psabi -Wno-error=pedantic -Wno-error=old-style-cast -Wno-missing-braces -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Wno-stringop-overflow, LAPACK_INFO=mkl, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, TORCH_VERSION=2.3.1, USE_CUDA=ON, USE_CUDNN=ON, USE_CUSPARSELT=1, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_GLOO=ON, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=1, USE_NNPACK=ON, USE_OPENMP=ON, USE_ROCM=OFF, USE_ROCM_KERNEL_ASSERT=OFF,

TorchVision: 0.18.1+cu121
LMDeploy: 0.5.3+
transformers: 4.44.0
gradio: 4.42.0
fastapi: 0.111.0
pydantic: 2.7.2
triton: 2.3.1
NVIDIA Topology:
        GPU0    GPU1    GPU2    GPU3    GPU4    GPU5    GPU6    GPU7    mlx5_0  mlx5_1  mlx5_2  mlx5_3  mlx5_4  mlx5_5  mlx5_6  mlx5_7       CPU Affinity    NUMA Affinity
GPU0     X      NV8     NV8     NV8     NV8     NV8     NV8     NV8     PXB     PXB     NODE    NODE    SYS     SYS     SYS     SYS 0-31,64-95       0
GPU1    NV8      X      NV8     NV8     NV8     NV8     NV8     NV8     PXB     PXB     NODE    NODE    SYS     SYS     SYS     SYS 0-31,64-95       0
GPU2    NV8     NV8      X      NV8     NV8     NV8     NV8     NV8     NODE    NODE    PXB     PXB     SYS     SYS     SYS     SYS 0-31,64-95       0
GPU3    NV8     NV8     NV8      X      NV8     NV8     NV8     NV8     NODE    NODE    PXB     PXB     SYS     SYS     SYS     SYS 0-31,64-95       0
GPU4    NV8     NV8     NV8     NV8      X      NV8     NV8     NV8     SYS     SYS     SYS     SYS     PXB     PXB     NODE    NODE32-63,96-127     1
GPU5    NV8     NV8     NV8     NV8     NV8      X      NV8     NV8     SYS     SYS     SYS     SYS     PXB     PXB     NODE    NODE32-63,96-127     1
GPU6    NV8     NV8     NV8     NV8     NV8     NV8      X      NV8     SYS     SYS     SYS     SYS     NODE    NODE    PXB     PXB 32-63,96-127     1
GPU7    NV8     NV8     NV8     NV8     NV8     NV8     NV8      X      SYS     SYS     SYS     SYS     NODE    NODE    PXB     PXB 32-63,96-127     1
mlx5_0  PXB     PXB     NODE    NODE    SYS     SYS     SYS     SYS      X      PIX     NODE    NODE    SYS     SYS     SYS     SYS
mlx5_1  PXB     PXB     NODE    NODE    SYS     SYS     SYS     SYS     PIX      X      NODE    NODE    SYS     SYS     SYS     SYS
mlx5_2  NODE    NODE    PXB     PXB     SYS     SYS     SYS     SYS     NODE    NODE     X      PIX     SYS     SYS     SYS     SYS
mlx5_3  NODE    NODE    PXB     PXB     SYS     SYS     SYS     SYS     NODE    NODE    PIX      X      SYS     SYS     SYS     SYS
mlx5_4  SYS     SYS     SYS     SYS     PXB     PXB     NODE    NODE    SYS     SYS     SYS     SYS      X      PIX     NODE    NODE
mlx5_5  SYS     SYS     SYS     SYS     PXB     PXB     NODE    NODE    SYS     SYS     SYS     SYS     PIX      X      NODE    NODE
mlx5_6  SYS     SYS     SYS     SYS     NODE    NODE    PXB     PXB     SYS     SYS     SYS     SYS     NODE    NODE     X      PIX
mlx5_7  SYS     SYS     SYS     SYS     NODE    NODE    PXB     PXB     SYS     SYS     SYS     SYS     NODE    NODE    PIX      X

Legend:

  X    = Self
  SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
  NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
  PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
  PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
  PIX  = Connection traversing at most a single PCIe bridge
  NV#  = Connection traversing a bonded set of # NVLinks

Error traceback
No response

prefilling is compute bound operation.
As far as I know, it take about one second to process 15,000 tokens. That's the upper bound right now


Problems interfacing with task export

In my computer -- and according to the taskwarrior documentation, task export outputs consits of json object per line, like this:
{"id":1,"description":"desc1","entry":"...","modified":"...","project":"divers","status":"pending","tags":["myTag"],"urgency":2.50137}
{"id":2,"description":"desc2","entry":"...","modified":"...","project":"divers","status":"pending","tags":["myTag"],"urgency":2.50137}
{"id":3,"description":"desc3","entry":"...","modified":"...","project":"divers","status":"pending","tags":["myTag2"],"urgency":2.50137}

Then, twui adds brackets around to make it looks like a json array, but it fails because it lacks a coma at the end of each object, and I got a [SyntaxError: Unexpected token {] message from the json parser (dunno why it seems to be working everywhere else, maybe my javascript version got a more rigid json parser).
The correct array is
[
{"id":1,"description":"desc1","entry":"...","modified":"...","project":"divers","status":"pending","tags":["myTag"],"urgency":2.50137},
{"id":2,"description":"desc2","entry":"...","modified":"...","project":"divers","status":"pending","tags":["myTag"],"urgency":2.50137},
{"id":3,"description":"desc3","entry":"...","modified":"...","project":"divers","status":"pending","tags":["myTag2"],"urgency":2.50137},
]

and the parser gets this (notice the absence of comas at the end of each line):
[
{"id":1,"description":"desc1","entry":"...","modified":"...","project":"divers","status":"pending","tags":["myTag"],"urgency":2.50137}
{"id":2,"description":"desc2","entry":"...","modified":"...","project":"divers","status":"pending","tags":["myTag"],"urgency":2.50137}
{"id":3,"description":"desc3","entry":"...","modified":"...","project":"divers","status":"pending","tags":["myTag2"],"urgency":2.50137}
]

There's a taskwarrior option (json.array) which enables to directly format output as a correct json array. I think it should be better to use it instead trying to build it manually to avoid those problems.

Thanks for the report and suggestion.

In the upcoming task v2.5.0, json.array is the default!

In your fix you changed JSON.parse('[' + value + ']').map(function(row) ... to raw.map(function(row) .... For me this throws "TypeError: raw.map is not a function". I never programmed in JavaScript, but shouldn't it be something like JSON.parse(value).map(function(row) ...? At least that's fixing it for me.


Update wrapper to latest nightly

with vanilla kotlin-compiler-embeddable

@bot-gradle test and merge

OK, I've already triggered a build for you.


Case error in RTClib.cpp

I was going a little nuts.  Using Arduino IDE 1.0, the compiler was complaining:
/usr/share/arduino/libraries/RTClib/RTClib.cpp:11:21: fatal error: arduino.h: No such file or directory
compilation terminated.
The error is in RTClib.h.  The following section attempts to include <arduino.h>:
#if ARDUINO > 22
#include <arduino.h>
#endif

This is a case error.  It should be:
#if ARDUINO > 22
#include <Arduino.h>
#endif

Merged fix. Thanks for the heads-up!

hai guys.i have a problem with tis code.i copied it on circuit digest but its giving me error.
attendance regiter.txt

Hai guys. i have a problem with tis code. i copied it on circuit digest but its giving me error. help me rectify that error.rectify it send it to<EMAIL_ADDRESS>


Missing letters/text when converting some pdf files to images

I was testing the conversion of various pdf files to images and found that sometimes text is missing (randomly) from the final produced image. These are more complex pdf files so that may be the reason, but it is still strange how only some of the text doesn't appear in the conversion.
The sample pdf files I have been using for testing were obtained online and here are two of the files that produce this issue:
Mississauga_Advantages.pdf
produces:

meanwhile:
pdf.pdf
produces:

I understand that this might be a deeper issue due to the complexity of the files themselves, just wanted to make this issue known.
Thanks

The glyphs display fine with the 1.8.13 desktop version. I remember such problems (trouble with type 1 fonts) with jdk 1.7. The bugs were gone with jdk 1.8. The PDFBox 2.0.* versions use their own code to render type 1 fonts.

Thanks for the observation @THausherr. At least I know the problem isn't isolated to my machine.

No, this is definitely a problem with the library.

Here is a reduced version of that file. It should display 995. If the bug still occurs, "9 5" should appear.
PDFBOXAndroid-92-reduced.pdf


Boot script timeout of 1 second - fconfig-linux.bin

I'd like to change the boot script timeout for my build to 1 second (down from the default 3 seconds) - so I need to change fconfig-linux.bin. This is a binary file and there are no instructions or make methods to generate this file. How can I change it?

Hi Ross!
The RedBoot config section is best created by RedBoot itself (with fconfig). Once you boot your system, you can use a shell and dd out the data and scp it to your flashbuilder host.
# debug sys sh
/ # cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00040000 00010000 "RedBoot"
mtd1: 00010000 00010000 "conf"
mtd2: 00fc0000 00010000 "linux.bk"
mtd3: 00fc0000 00010000 "linux"
mtd4: 00010000 00010000 "FIS_directory"
mtd5: 00010000 00010000 "RedBoot_config"
mtd6: 00010000 00010000 "Redundant_FIS"
mtd7: 10000000 00020000 "rootfs_data"
/ # dd if=/dev/mtd5 of=/tmp/fconfig.bin bs=64k
1+0 records in
1+0 records out

Thanks Lars!
Can I suggest adding a README file in the files directory with this information for future reference?
Regards,
Ross.


403 UncategorizedSiteWarning When running NPM install

Describe the bug
I am getting UncategorizedSiteWarning when running npm install --registry=https://ip:4873 --verbose
Where myip is the external ip address, not localhost or <IP_ADDRESS>. Using localhost and <IP_ADDRESS> works. I can also open the verdaccio webpage using the external ip address
To Reproduce
Steps to reproduce the behavior:

npm install --registry=https://ip:4873 --verbose

Expected behavior
Should not have any error.
Configuration File (cat ~/.config/verdaccio/config.yaml)
# path to a directory with all packages
storage: /home/patrick/.local/share/verdaccio/storage

# proxy
http_proxy: myproxy
https_proxy: myproxy
no_proxy: localhost,<IP_ADDRESS>

# server port
listen:
  - https://myip:4873

https:
  key: /home/patrick/.config/verdaccio/verdaccio-key.pem
  cert: /home/patrick/.config/verdaccio/verdaccio-cert.pem
  ca: /home/patrick/.config/verdaccio/verdaccio-csr.pem

# path to a directory with plugins to include
plugins: ./plugins

web:
  # WebUI is enabled as default, if you want disable it, just uncomment this line
  #enable: false
  title: Verdaccio

#auth:
#  htpasswd:
#    file: ./htpasswd
    # Maximum amount of users allowed to register, defaults to "+inf".
    # You can set this to -1 to disable registration.
    # max_users: 1000

# a list of other known repositories we can talk to
uplinks:
  npmjs:
    url: http://registry.npmjs.org/

packages:
  '@*/*':
    # scoped packages
    access: $all
    publish: $authenticated
    proxy: npmjs

  '**':
    # allow all users (including non-authenticated users) to read and
    # publish all packages
    #
    # you can specify usernames/groupnames (depending on your auth plugin)
    # and three keywords: "$all", "$anonymous", "$authenticated"
    access: $all

    # allow all known users to publish packages
    # (anyone can register by default, remember?)
    publish: $authenticated

    # if package is not available locally, proxy requests to 'npmjs' registry
    proxy: npmjs

# To use `npm audit` uncomment the following section
#middlewares:
#  audit:
#    enabled: false

# log settings
logs:
  - {type: stdout, format: pretty, level: trace}
  #- {type: file, path: verdaccio.log, level: info}

Debugging output
 npm info it worked if it ends with ok
npm verb cli [ '/home/patrick/.nvm/versions/node/v10.14.1/bin/node',
npm verb cli   '/home/patrick/.nvm/versions/node/v10.14.1/bin/npm',
npm verb cli   'install',
npm verb cli   '--registry=https://<IP_ADDRESS>:4873',
npm verb cli   '--verbose' ]
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm verb npm-session 9d7e75ae2437025a
npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm timing stage:loadCurrentTree Completed in 11ms
npm timing stage:loadIdealTree:cloneCurrentTree Completed in 0ms
npm timing stage:loadIdealTree:loadShrinkwrap Completed in 3ms
npm http fetch GET 403 https://<IP_ADDRESS>:4873/@webcomponents%2fwebcomponentsjs 316ms
npm http fetch GET 403 https://<IP_ADDRESS>:4873/@polymer%2fpolymer 322ms
npm http fetch GET 403 https://<IP_ADDRESS>:4873/@webcomponents%2fwebcomponentsjs 284ms
npm http fetch GET 403 https://<IP_ADDRESS>:4873/@polymer%2fpolymer 304ms
npm timing stage:rollbackFailedOptional Completed in 0ms
npm timing stage:runTopLevelLifecycles Completed in 823ms
npm verb stack Error: 403 UncategorizedSiteWarning<EMAIL_ADDRESS>npm verb stack     at fetch.then.res (/home/patrick/.nvm/versions/node/v10.14.1/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/fetch.js:42:19)
npm verb stack     at tryCatcher (/home/patrick/.nvm/versions/node/v10.14.1/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
npm verb stack     at Promise._settlePromiseFromHandler (/home/patrick/.nvm/versions/node/v10.14.1/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:512:31)
npm verb stack     at Promise._settlePromise (/home/patrick/.nvm/versions/node/v10.14.1/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:569:18)
npm verb stack     at Promise._settlePromise0 (/home/patrick/.nvm/versions/node/v10.14.1/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:614:10)
npm verb stack     at Promise._settlePromises (/home/patrick/.nvm/versions/node/v10.14.1/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:693:18)
npm verb stack     at Async._drainQueue (/home/patrick/.nvm/versions/node/v10.14.1/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:133:16)
npm verb stack     at Async._drainQueues (/home/patrick/.nvm/versions/node/v10.14.1/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:143:10)
npm verb stack     at Immediate.Async.drainQueues [as _onImmediate] (/home/patrick/.nvm/versions/node/v10.14.1/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:17:14)
npm verb stack     at runCallback (timers.js:705:18)
npm verb stack     at tryOnImmediate (timers.js:676:5)
npm verb stack     at processImmediate (timers.js:658:5)
npm verb cwd /home/patrick/xyz
npm verb Linux 4.15.0-20-generic
npm verb argv "/home/patrick/.nvm/versions/node/v10.14.1/bin/node" "/home/patrick/.nvm/versions/node/v10.14.1/bin/npm" "install" "--registry=https://myip:4873" "--verbose"
npm verb node v10.14.1
npm verb npm  v6.4.1
npm ERR! code E403
npm ERR! 403 UncategorizedSiteWarning<EMAIL_ADDRESS>npm verb exit [ 1, true ]
npm timing npm Completed in 68773ms

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/patrick/.npm/_logs/2018-12-04T21_59_34_767Z-debug.log

I can see you are having and issue but, without full context I cannot help you. Please elaborate your problem with all details you can add.

Sorry.. I have trouble posting the bug report. I have corrected the post with more information.

@pchuong I have no clue from that comes from, but I doubt that comes from verdaccio side.
I just notice your uplink uses http. Update to
uplinks:
  npmjs:
    url: https://registry.npmjs.org/

I tried both http and https for the unlink, result is the same.
I have enabled logging with trace setting. There is no request made it to the server. But when using localhost, I do see request coming into the server.

From: Juan Picado @jotadeveloper<EMAIL_ADDRESS>Sent: December 5, 2018 1:08:12 AM
To: verdaccio/verdaccio
Cc: Chuong, Patrick; Mention
Subject: [EXTERNAL] Re: [verdaccio/verdaccio] 403 UncategorizedSiteWarning When running NPM install (#1151)
@pchuonghttps://github.com/pchuong I have no clue from that comes from, but I doubt that comes from verdaccio side.
I just notice your uplink uses http. Update to
uplinks:
npmjs:
url: https://registry.npmjs.org/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/verdaccio/verdaccio/issues/1151#issuecomment-444370521, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABns9UJe0qhIFEYwEFkaYlzu6T3Kay-xks5u12LMgaJpZM4ZBmJ6.

Are your certificates valid ? Perhaps you must disable ca prop from npm config.

Have you tried https://verdaccio.org/docs/en/reverse-proxy#configuration-with-ssl ?

The verdaccio registry server is not behind a proxy, I am simply trying to experiment using the external ip address instead of localhost on the same machine. Note that I can access the verdaccio web interface from a browser on the same machine or another machine. So, I don't think reverse proxy is an issue.


Executing contract methods

Successfully connected Metamask with this library! Now, How do I establish web3 connection to my contract and call the contract's method. Can you please provide me some examples?

This is example of calling  transfer method of smart contract of BEP-20 token, which has parameters to, amount. Sample code has comments explaining.
But for more information on how to call any function of smart contract you have to dig this.

Thanks for the answer, by the way can it expose the method eth_signTypedData_v4? Currently I only find eth_signTypedData
https://docs.metamask.io/guide/signing-data.html#a-brief-history


Remove the reset password token after a successful change password

Currently, the reset pwd token/link can be used until the hard timeout or for a certain number of times.
Even if the password is successfully changed, the token/link can still be used.
This PR add the option to remove it (by default, it is not the case to be backward compatible).

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

This looks good but I don't think an option is necessary. You should instead remove the token forcefully if the token is expired. If the token, for example, is set to be used 3 times, you cannot remove it after it's used to reset the password as that would violate the policy. Removal should only be done if the token is in fact expired.

Before my changes, we could set a hard timeout for the reset pwd token.
My first change was to allow to use it a certain number of times instead of a hard timeout (cas.authn.pm.reset.number-of-uses property).
This second change is to remove the token after a successful password change (cas.authn.pm.reset.remove-token-after-successful-change property).
So this second change makes sense if you have set a hard timeout. You may want the link to be usable for 24 hours but want to be invalidated as soon as the password has been changed.
These options allow you to define the functional behavior of the reset password process.
I can revisit this PR or the previous one if you think something is wrong.

I understand the use case, but I sort of find it strange and at odds with the number-of-uses property. For example, what does it mean if:

token is set to last for 10 minutes
can be used 4 times
But it is deleted immediately after it's used (let's say the option is set to true to delete)

We could say this is misconfiguration, that if you attempt to delete the token after use, then number of uses can only be one. But I think we still need this setting because there are scenarios where the token is part of a link and anti-virus scans emails/links and "clicks" on the link and follows it.
Nonetheless, I think we need to remove the option to delete the token, and instead check the token per the defined expiration policy and remove only when policy says token has expired.
For example,

token is set to last for 20 seconds
can be used 2 times
When resetting the password, check the following:

if expiration-policy-for-token says token has now expired (because longer than 20 seconds, or number-of-uses > 2)
    delete the token here
end if

This allows the token to be deleted if the last-time-used is larger than 20 seconds, or if the token has been used twice already. The ideal setup could then be:

token is set to last for 2 minutes
can be used 1 times

...and with this, tokens will be immediately deleted after use.
If someone needs the token to be used 3 times within that 20 second window (even after it's been used successfully) then it's up to them to decide the behavior....and this is one less option to tweak anyway. (The token was always meant to be deleted immediately after use, so backward compatibility is not an issue here)

I should add that the behavior I am describing is consistent with how simple-mfa works with its own tokens. (and for that matter, how service tickets work)

In fact, using the link is different from successfully changing your password as you can click on the link and not change your password.
That said, it's close because if you click on the link, it's because you want to change your password.
I think I understand your thinking. What I propose is a bit inconsistent with the way we do things normally.
Current settings (timeout and number of uses) are exclusive while they could gather in a more general policy. I will propose a new PR for that.

Current settings (timeout and number of uses) are exclusive: sorry, I was wrong
From the code I submitted last time:
    protected ExpirationPolicy computeExpirationPolicy() {
        val reset = casProperties.getAuthn().getPm().getReset();
        val numberOfUses = reset.getNumberOfUses();
        val seconds = Beans.newDuration(reset.getExpiration()).toSeconds();

        if (numberOfUses >= 1) {
            LOGGER.debug("Password reset URL shall expire after [{}] uses and [{}] second(s)", numberOfUses, seconds);
            return new MultiTimeUseOrTimeoutExpirationPolicy(numberOfUses, seconds);
        }

        LOGGER.debug("Password reset URL shall expire in [{}] second(s)", seconds);
        return HardTimeoutExpirationPolicy.builder().timeToKillInSeconds(seconds).build();
    }

The current behavior is exactly what you want: the timeout and the number of uses are both taken into account if both are set (MultiTimeUseOrTimeoutExpirationPolicy).
The only caveat is that the timeout is an idle timeout when there is a number of uses while it is a hard timeout when there is no number of uses.
Do you want me to create a MultiTimeUseOrHardTimeoutExpirationPolicy to fix that? Thanks

I think that is a mistake; perhaps a major mistake. MultiTimeUseOrTimeoutExpirationPolicy should always be based on a hard timeout. IOW, we should be using the ticket's creation-time, and not the last-used-time in that policy. If I look at how MultiTimeUseOrTimeoutExpirationPolicy is used by various ticket expiration policies, it is evident that we should switch this to use a hard timeout and the ticket creation time.

You also should be doing this:
val request = WebUtils.getHttpServletRequestFromExternalWebflowContext(requestContext);
val resetToken = request.getParameter(PasswordManagementService.PARAMETER_PASSWORD_RESET_TOKEN);
val transientTicket = ticketRegistry.getTicket(resetToken, TransientSessionTicket.class);
if (transientTicket.getExpirationPolicy().isExpired(transientTicket)) { //this call could be improved; looks weird :)
    ticketRegistry.deleteTicket(transientTicket);
}

With the small addition of:
public interface TransientSessionTicket extends Ticket, TicketGrantingTicketAwareTicket {}

No setting.
Delete if the policy says we should delete.

Excellent! At least, this aborted change has focus our attention on this "mistake".
I will submit a PR to handle both (certainly tomorrow).

Thank you Jérôme!

Waiting for the build to pass on the new PR: https://github.com/apereo/cas/pull/5507


correctly pass service host name in eds update for service entries

Pass service.host.Name of instance while triggering eds updates for service entries
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@howardjohn PTAL, I fixed the second part that you have observed in https://github.com/istio/istio/issues/19961 - passing service host name correctly.
Will look at delete case also little later today.

@ramaraochavali: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
65dc2e1ae3613dcff3b2ef58f16b8ef9fae314fc
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio
7714e127418aa9889387fd3e27f4df643dd49780
link
/test pilot-multicluster-e2e_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test pilot-multicluster-e2e_istio

lgtm

sorry closed by mistake

@ramaraochavali: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
7714e127418aa9889387fd3e27f4df643dd49780
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test unit-tests_istio

@howardjohn can you please take a look at this and see if you have any further comments?


Update Bitwarden master password input to hide password

Description
Update Bitwarden master password input to hide password
Type of change

Bug fix / improvement for somebody else's extension. Extension author: @pomdtr

Screencast
Current behaviour

Updated behaviour

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing

Small spoiler, we will introduce specific password field very soon, so this feature could probably be not very actual 😉

Thanks for the contribution @AmayruN5 !
I think we should wait for the native password field type mentionned by @mattisssa, what do you think ?

@pomdtr Yes, we can wait for the native one.
I just was frustrated with seeing my master password every time I need to unlock the vault. And couldn't wait for native password input, so I modified the extension.
At least it could be a temporary solution for hiding a password. If somebody needs it.

Hi @AmayruN5 👋
Why wait? It should be easy to incorporate the new type when it's released 💯
I did a quick review, and it seems like it's actually sending the password as stars instead of the right password 😵💫 Did you test it yourself, could be that I'm mistaken.
Request a new review when you are ready, feel free to contact me here or at Slack if you have any questions.

@pernielsentikaer  Hello, thanks for your review.
Yes, I haven't copied the part related to sending a correct password value from my local version of the extension.
I closed PR because I realized an unexpected behavior of my solution. It can not handle a case when user deletes characters at some part of password (not from the end). Which may cause sending an incorrect password.
So I think it's better not to make any changes now and wait for the native password field.

I'll let it be up to you @AmayruN5 – if you can't solve it without using massive amount of time, it could be better closing and wait as stated 😄

There is now support for password in Form 😄


Click & collect support

Shipping methods could be extended to contain "Click and collect" option.

We've been thinking this around actualy, we're thinking about twisting around views to create a specific shipping method which lock down the address.
Any suggestion or pattern is welcomed.

A very good idea. Things to consider (through real experience):

Clearly specify that the order is not ready to pick up before they receive an order confirmation. Many expect the order to be ready right after they put in the order
Potential multiple pickup points
Custom pricing for pickup


How do I do Callbacks in Rhai

Hi I just started using Rhai. So far a great language to suit my needs.
I am trying to do callbacks like I do in Python.
print("Hi");
fn make_double(x){
 return 2*x
}
fn callback_test(num,func){
 print(func(num))
}
callback_test(32,make_double);
But this does not work. Gives the following error:
Hi thread 'main' panicked at 'Failed to evaluate: ErrorVariableNotFound("make_double", Position { line: 10, pos: 18 })', src/libcore/result.rs:1165:5 note: run with RUST_BACKTRACE=1environment variable to display a backtrace.
Version of Rhai used: 0.10.0 from crates.io
Can anyone please help me solve this?

This is not Python.  The make_double in your last statement is a variable called make_double, not the function.
Try:
print("Hi");

fn make_double(x){ 2*x }

fn callback_test(num,func){
    print(func.call(num))
}

callback_test(32, Fn("make_double"));

Thank you. I will try this.