[Bug]: SharePlus Can not build the app

Platform
Android 12
Plugin
share_plus
Version
10.0.0
Flutter SDK
3.22.3
Steps to reproduce
Change from Version 9.0.0 to 10.0.0
Then it bring this error
Back to 9.0.0 and it works fine.
Code Sample
No response
Logs
/myapp/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java:114: error: cannot find symbol
      flutterEngine.getPlugins().add(new dev.fluttercommunity.plus.share.SharePlusPlugin());
                                                                        ^
  symbol:   class SharePlusPlugin
  location: package dev.fluttercommunity.plus.share
1 error

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

Flutter Doctor
[✓] Flutter (Channel stable, 3.22.3, on macOS 14.6 23G80 darwin-x64, locale
    de-DE)
    • Flutter version 3.22.3 on channel stable at
      /Users/tobiasschiek/Documents/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision b0850beeb2 (3 weeks ago), 2024-07-16 21:43:41 -0700
    • Engine revision 235db911ba
    • Dart version 3.4.4
    • DevTools version 2.34.3

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/tobiasschiek/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      17.0.11+0-17.0.11b1207.24-11852314)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15F31d
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2024.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      17.0.11+0-17.0.11b1207.24-11852314)

[✓] Android Studio (version 2021.2)
    • Android Studio at /Users/tobiasschiek/Library/Application
      Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/212.5712.43.2112.8815526
      /Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      11.0.12+0-b1504.28-7817840)

[✓] VS Code (version 1.91.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.92.0

[✓] Connected device (3 available)
    • sdk gphone x86 (mobile) • emulator-5554 • android-x86    • Android 11 (API
      30) (emulator)
    • macOS (desktop)         • macos         • darwin-x64     • macOS 14.6
      23G80 darwin-x64
    • Chrome (web)            • chrome        • web-javascript • Google Chrome
      126.0.6478.183

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Checklist before submitting a bug

[X] I searched issues in this repository and couldn't find such bug/problem
[X] I Google'd a solution and I couldn't find it
[X] I searched on StackOverflow for a solution and I couldn't find it
[X] I read the README.md file of the plugin
[X] I'm using the latest version of the plugin
[X] All dependencies are up to date with flutter pub upgrade
[X] I did a flutter clean
[X] I tried running the example project

It is an issue with cache, which happens from time to time with different Flutter packages. Did you really try flutter clean?

It is an issue with cache, which happens from time to time with different Flutter packages. Did you really try flutter clean?

Yes, multiple times

@tschiekdev
@vbuberen
Same Error.
> Task :share_plus:lintAnalyzeDebug
e: /Users/alfaiz/.gradle/caches/transforms-3/c73366e0a1d502d00a43c7307810b254/transformed/jetified-core-ktx-1.13.1/jars/classes.jar!/META-INF/core-ktx_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/alfaiz/.gradle/caches/transforms-3/b3f8404806f995870bc064645b7b0136/transformed/core-1.13.1/jars/classes.jar!/META-INF/core_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/alfaiz/.gradle/caches/transforms-3/17d249546db99b14993c391afcc83a3f/transformed/lifecycle-livedata-core-2.6.2/jars/classes.jar!/META-INF/lifecycle-livedata-core_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/alfaiz/.gradle/caches/transforms-3/1bede775978eb7924a8964bc8304b438/transformed/lifecycle-livedata-2.6.2/jars/classes.jar!/META-INF/lifecycle-livedata_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/alfaiz/.gradle/caches/transforms-3/7800575b951cdbcc8be86875e40b9ed6/transformed/lifecycle-viewmodel-2.6.2/jars/classes.jar!/META-INF/lifecycle-viewmodel_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/alfaiz/.gradle/caches/transforms-3/dbf9f3d0b7d9a82aa22add4d6e8c2f0c/transformed/lifecycle-runtime-2.6.2/jars/classes.jar!/META-INF/lifecycle-runtime_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/alfaiz/.gradle/caches/modules-2/files-2.1/androidx.lifecycle/lifecycle-common/2.6.2/10f354fdb64868baecd67128560c5a0d6312c495/lifecycle-common-2.6.2.jar!/META-INF/lifecycle-common.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/alfaiz/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.8.22/636bf8b320e7627482771bbac9ed7246773c02bd/kotlin-stdlib-1.8.22.jar!/META-INF/kotlin-stdlib-jdk7.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/alfaiz/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.8.22/636bf8b320e7627482771bbac9ed7246773c02bd/kotlin-stdlib-1.8.22.jar!/META-INF/kotlin-stdlib.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/alfaiz/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.8.22/636bf8b320e7627482771bbac9ed7246773c02bd/kotlin-stdlib-1.8.22.jar!/META-INF/kotlin-stdlib-jdk8.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/alfaiz/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-common/1.8.22/1a8e3601703ae14bb58757ea6b2d8e8e5935a586/kotlin-stdlib-common-1.8.22.jar!/META-INF/kotlin-stdlib-common.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/alfaiz/Development/bagndash-mobile/build/share_plus/.transforms/4d9a3ac0ce73ecc622da224a84177590/transformed/out/jars/classes.jar!/META-INF/share_plus_debug.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.
e: /Users/alfaiz/Development/bagndash-mobile/build/share_plus/tmp/kotlin-classes/debug/META-INF/share_plus_debug.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.

> Task :share_plus:lintReportDebug
Wrote HTML report to file:///Users/alfaiz/Development/bagndash-mobile/build/share_plus/reports/lint-results-debug.html

> Task :shared_preferences_android:lintAnalyzeDebug
e: /Users/alfaiz/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.9.10/72812e8a368917ab5c0a5081b56915ffdfec93b7/kotlin-stdlib-1.9.10.jar!/META-INF/kotlin-stdlib.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.
e: /Users/alfaiz/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.9.10/72812e8a368917ab5c0a5081b56915ffdfec93b7/kotlin-stdlib-1.9.10.jar!/META-INF/kotlin-stdlib-jdk8.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.
e: /Users/alfaiz/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.9.10/72812e8a368917ab5c0a5081b56915ffdfec93b7/kotlin-stdlib-1.9.10.jar!/META-INF/kotlin-stdlib-jdk7.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.
e: /Users/alfaiz/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-common/1.9.10/dafaf2c27f27c09220cee312df10917d9a5d97ce/kotlin-stdlib-common-1.9.10.jar!/META-INF/kotlin-stdlib-common.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.
e: /Users/alfaiz/Development/bagndash-mobile/build/shared_preferences_android/.transforms/a8a031801fea084749791f5c21a87617/transformed/out/jars/classes.jar!/META-INF/shared_preferences_android_debug.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.
e: /Users/alfaiz/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/2.0.0/b48df2c4aede9586cc931ead433bc02d6fd7879e/kotlin-stdlib-2.0.0.jar!/META-INF/kotlin-stdlib.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.
e: /Users/alfaiz/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/2.0.0/b48df2c4aede9586cc931ead433bc02d6fd7879e/kotlin-stdlib-2.0.0.jar!/META-INF/kotlin-stdlib-jdk8.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.
e: /Users/alfaiz/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/2.0.0/b48df2c4aede9586cc931ead433bc02d6fd7879e/kotlin-stdlib-2.0.0.jar!/META-INF/kotlin-stdlib-jdk7.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.
e: /Users/alfaiz/Development/bagndash-mobile/build/shared_preferences_android/tmp/kotlin-classes/debug/META-INF/shared_preferences_android_debug.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.

> Task :share_plus:lintDebug FAILED
Lint found 2 errors, 4 warnings. First failure:

/Users/alfaiz/.pub-cache/hosted/pub.dev/share_plus-10.0.0/android/src/main/kotlin/dev/fluttercommunity/plus/share/Share.kt:148: Error: Call requires API level 24 (current min is 19): java.lang.Iterable#forEach [NewApi]
        resInfoList.forEach { resolveInfo ->
                    ~~~~~~~

The full lint text report is located at:
  /Users/alfaiz/Development/bagndash-mobile/build/share_plus/intermediates/lint_intermediate_text_report/debug/lint-results-debug.txt

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':share_plus:lintDebug'.
> Lint found errors in the project; aborting build.

  Fix the issues identified by lint, or create a baseline to see only new errors:

android {
lint {
baseline = file("lint-baseline.xml")
}
}

For more details, see https://developer.android.com/studio/write/lint#snapshot

* 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 ':share_plus:lintDebug'.
      at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$1(ExecuteActionsTaskExecuter.java:142)
      at org.gradle.internal.Try$Failure.ifSuccessfulOrElse(Try.java:282)
      at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:140)
      at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:128)
      at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:77)
      at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
      at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:51)
      at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
      at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
      at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
      at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
      at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)
      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
      at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
      at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
      at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:69)
      at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:327)
      at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:314)
      at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:307)
      at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:293)
      at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:417)
      at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:339)
      at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
      at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
Caused by: java.lang.RuntimeException: Lint found errors in the project; aborting build.

Fix the issues identified by lint, or create a baseline to see only new errors:

android {
lint {
baseline = file("lint-baseline.xml")
}
}

For more details, see https://developer.android.com/studio/write/lint#snapshot
        at com.android.build.gradle.internal.lint.AndroidLintWorkAction$Companion.maybeThrowException(AndroidLintWorkAction.kt:226)
        at com.android.build.gradle.internal.lint.AndroidLintTextOutputTask.doTaskAction(AndroidLintTextOutputTask.kt:104)
        at com.android.build.gradle.internal.tasks.NonIncrementalTask$taskAction$$inlined$recordTaskAction$1.invoke(BaseTask.kt:66)
        at com.android.build.gradle.internal.tasks.Blocks.recordSpan(Blocks.java:51)
        at com.android.build.gradle.internal.tasks.NonIncrementalTask.taskAction(NonIncrementalTask.kt:97)
        at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
        at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:125)
        at org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:58)
        at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:51)
        at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:29)
        at org.gradle.api.internal.tasks.execution.TaskExecution$3.run(TaskExecution.java:236)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:47)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:68)
        at org.gradle.api.internal.tasks.execution.TaskExecution.executeAction(TaskExecution.java:221)
        at org.gradle.api.internal.tasks.execution.TaskExecution.executeActions(TaskExecution.java:204)
        at org.gradle.api.internal.tasks.execution.TaskExecution.executeWithPreviousOutputFiles(TaskExecution.java:187)
        at org.gradle.api.internal.tasks.execution.TaskExecution.execute(TaskExecution.java:165)
        at org.gradle.internal.execution.steps.ExecuteStep.executeInternal(ExecuteStep.java:89)
        at org.gradle.internal.execution.steps.ExecuteStep.access$000(ExecuteStep.java:40)
        at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:53)
        at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:50)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
        at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:50)
        at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:40)
        at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:68)
        at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:38)
        at org.gradle.internal.execution.steps.CancelExecutionStep.execute(CancelExecutionStep.java:41)
        at org.gradle.internal.execution.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:74)
        at org.gradle.internal.execution.steps.TimeoutStep.execute(TimeoutStep.java:55)
        at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:51)
        at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:29)
        at org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.executeDelegateBroadcastingChanges(CaptureStateAfterExecutionStep.java:124)
        at org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.execute(CaptureStateAfterExecutionStep.java:80)
        at org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.execute(CaptureStateAfterExecutionStep.java:58)
        at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:48)
        at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:36)
        at org.gradle.internal.execution.steps.BuildCacheStep.executeWithoutCache(BuildCacheStep.java:181)
        at org.gradle.internal.execution.steps.BuildCacheStep.lambda$execute$1(BuildCacheStep.java:71)
        at org.gradle.internal.Either$Right.fold(Either.java:175)
        at org.gradle.internal.execution.caching.CachingState.fold(CachingState.java:59)
        at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:69)
        at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:47)
        at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:36)
        at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:25)
        at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:36)
        at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:22)
        at org.gradle.internal.execution.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:110)
        at org.gradle.internal.execution.steps.SkipUpToDateStep.lambda$execute$2(SkipUpToDateStep.java:56)
        at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:56)
        at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:38)
        at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:73)
        at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:44)
        at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:37)
        at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:27)
        at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:89)
        at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:50)
        at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:114)
        at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:57)
        at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:76)
        at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:50)
        at org.gradle.internal.execution.steps.SkipEmptyWorkStep.executeWithNoEmptySources(SkipEmptyWorkStep.java:254)
        at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:91)
        at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:56)
        at org.gradle.internal.execution.steps.RemoveUntrackedExecutionStateStep.execute(RemoveUntrackedExecutionStateStep.java:32)
        at org.gradle.internal.execution.steps.RemoveUntrackedExecutionStateStep.execute(RemoveUntrackedExecutionStateStep.java:21)
        at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsStartedStep.execute(MarkSnapshottingInputsStartedStep.java:38)
        at org.gradle.internal.execution.steps.LoadPreviousExecutionStateStep.execute(LoadPreviousExecutionStateStep.java:43)
        at org.gradle.internal.execution.steps.LoadPreviousExecutionStateStep.execute(LoadPreviousExecutionStateStep.java:31)
        at org.gradle.internal.execution.steps.AssignWorkspaceStep.lambda$execute$0(AssignWorkspaceStep.java:40)
        at org.gradle.api.internal.tasks.execution.TaskExecution$4.withWorkspace(TaskExecution.java:281)
        at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:40)
        at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:30)
        at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:37)
        at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:27)
        at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:44)
        at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:33)
        at org.gradle.internal.execution.impl.DefaultExecutionEngine$1.execute(DefaultExecutionEngine.java:76)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:139)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:128)
        at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:77)
        at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
        at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:51)
        at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
        at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
        at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
        at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:69)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:327)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:314)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:307)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:293)
        at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:417)
        at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:339)
        at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
        at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)

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

BUILD FAILED in 5m 52s

Your error is different from the one reported.
And again, like yesterday with another plugin, your project has an old version. This time it is Kotlin as it is seen in the error logs.
Please use Google to search for reasons of an error and don't tag people in unrelated issues.

@tschiekdev
Can you build the example app of the plugin?
As I said earlier it is an issue with the build cache that you have. Can you also check the share_plus_platform_interface version in your project also updated? It can be done by looking at the pubspec.lock file.

You can also try to perform a flutter pub cache repair to clean the installation of the packages in your system cache. See dart pub cache for more info.

@tschiekdev
Can you build the example app of the plugin?
As I said earlier it is an issue with the build cache that you have. Can you also check the share_plus_platform_interface version in your project also updated? It can be done by looking at the pubspec.lock file.

Thanks for the hint. Deleting the pubspeck.lock-file helped. It works now.

For me, none work until I deleted ~/.gradle.


Can't close all scripts if some are unsaved

Godot version:

3.2.4 rc3 / dd1881a
Issue description:

When there is an unsaved script on your script list, using Close All or Close Others will stop on that script. The unsaved dialog will interrupt closing scripts, so you have to use it again.
This is especially problematic with built-in scripts, which tend to ask you to save changes even if they are unmodified.
Steps to reproduce:

Open few scripts
Modify 1 of them (or 2 for best effect)
Right click script list and Close All
Not all scripts are closed, because of the dialog

Hello,
This seems to be the desired behavior:
for (int i = child_count - 1; i >= 0; i--) {
  ...
  // Maybe there are unsaved changes
  if (se->is_unsaved()) {
    _ask_close_current_unsaved_tab(se);
    continue;
  }
  ...
}

But maybe opening popup before closing the scripts in which the unsaved files are listed with the possibility to :

save all
save nothing
cancel the action

Would be a better alternative ? Like what Visual Studio does ?

When you close all scene tabs, editor switches to each unsaved tab and separately asks what to do. Also VS Code does the same. So this is what I would expect. Right not Script Editor stops closing tabs on first popup.


Feature request: Flatten event metadata into the json

Currently event metadata is put into the log message like field=value, it would be nice to have something similar to tracing_subscriber's flatten so that the metadata is sent as part of the JSON and can then be used with Datadog's filtering.
If this is something that would be accepted as a PR, I can work on this in 3-4 weeks.

Hi,
i think that's a great idea and should be easy to implement.
Would you put the key-value-pairs in the top level of the json or in some form of nested structure?
I think both ways to enable us to filter by the key.

I added it into version 2.2.0


added httptrace redirects handling

#23

I was thinking whether we should consider each redirect as a new request and report them independently.

Wouldn't that become very confusing, though we can still go ahead with it and display the breakdown for each request. What do you suggest?


createTextEditorDecorationType rendering or line height calculation goes wrong when Windows 10 scaling is not 100%.

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.62.3 (user setup)
OS Version: Windows 10 Pro (21H1), Build 19043.1348

Steps to Reproduce:
As you can see, Blockman extension renders the blocks very well when scaling is 100%, but when the Windows scaling is anything other than 100%, the horizontal 1px gaps appear somehow.
To be more clear: Blockman does not render one block as an entire HTML div, it renders one block line by line, which means it creates a div for each line, and these divs must be exactly the height of a line, so they will touch each other perfectly and so there will be illusion of entire block. It works fine when Windows scaling is 100%, but when it's not 100%, 1px horizontal gaps appear.
Blockman calculated line height by this instruction:
https://github.com/microsoft/vscode/issues/125341#issuecomment-854812591
Currently Blockman is just using simple CSS height: 100%; value to achieve line height for each line.
And it seems, achieving exact line height does not work very well when Windows scaling is other than 100%.
My monitor is classic 1920x1080, so I can keep 100% scaling, but this is a big problem for people who have 4K monitors, they need to set Windows scaling to about 150-200%.

@alexdima, things changed very positively. After the version 1.66 update (with Electron 17) of VS Code, this issue (strange horizontal lines) seems mostly fixed.
I tested on 3 Windows machines and 1 Mac OS machine, and the issue seems like 99.9% fixed, yeah, the 0.1% is about very rare horizontal lines, like I may see one or two lines in rare edge case scenarios of some very abnormal zooming settings.
Also, as you can see here:
https://github.com/leodevbro/vscode-blockman/issues/52
https://github.com/leodevbro/vscode-blockman/issues/75
at least 4 people confirmed that it is fixed. So far only one person reported that it is not fixed enough for his/her machine.
I'm not sure whether this issue should be closed or not. Maybe it needs some more investigation.

I will close this since there's nothing more planned here from our side.


Improve error messaged by dropping untagged enums

Untagged enums do not provide good error messages and likely never will,
given that there are multiple PRs which are just completely ignored
(serde#2376 and
serde#1544).
Instead using content::de the untagged enums can be replaced by custom
buffering. The error messages for OneOrMany and PickFirst now look
like this, including the original failure for each variant.
OneOrMany could not deserialize any variant:
  One: invalid type: map, expected u32
  Many: invalid type: map, expected a sequence

PickFirst could not deserialize any variant:
  First: invalid type: string "Abc", expected u32
  Second: invalid digit found in string

The implementations of VecSkipError and DefaultOnError are updated
too, but should not result in any visible changes.

bors r+


Allow components to be references

this to allow for cases where bundlers or node need explicit references and can't resolve dynamic imports (import(r.component))
e.g.
{ path: '/', component: () => HomePage },
{ path: '/about', component: () => import('/about') }

this may break the nested routing - open to feedback

This should be fine I think we leave the string for lazy and we directly put the Component.. no need for the extra function wrapper. I will merge this and make the small change.


Run / Open File

If possible to run / execute / open a file with browser, then there is an option to
a) Run / Open file when done downloading
b) Prompt to run / open the file when done downloading
c) Clicking the file name to Run / Open the file (Finished/Stopped Section)

AriaNg cannot know whether the download path exists. You can use AriaNg Native if you want to open download path by clicking the path in AriaNg Native.

It is possible but i don't know why author is responding with something no body wants , another heavy electron app, i tried executing URI of my downloads folder it opens finder in macOS

It is possible but i don't know why author is responding with something no body wants , another heavy electron app, i tried executing URI of my downloads folder it opens finder in macOS

this is a issue of AriaNg, not AriaNg Native. AriaNg is a pure web page, and AriaNg Native is built with electron.


Empty fd_pread fails when it should succeed

Subject of the issue
Calling fd_pread with a 0-length iovs is a no-op on host Linux and other Wasm runtimes (Wasmtime, Wasmer, Node) while WAMR fails with inval (28).
Test case
fn main() {
    unsafe {
        let fd = wasi::path_open(
            3,
            0,
            "a",
            wasi::OFLAGS_CREAT,
            wasi::RIGHTS_FD_SEEK | wasi::RIGHTS_FD_READ,
            0,
            0,
        )
        .unwrap();

        let iovs = [];

        wasi::fd_pread(fd, &iovs, 0).unwrap();
    }
}

Your environment
Tested with HEAD on Linux and Darwin amd64.
Steps to reproduce
Run the example above.
Expected behavior
It should not panic and fd_pread into an empty buffer should be no-op.
Actual behavior
The code panics with iwasm. But not other runtimes.

It should not panic and fd_pread into an empty buffer should be no-op.

i tend to disagree.
EINVAL for iovcnt==0 comes from posix. https://pubs.opengroup.org/onlinepubs/9699919799/functions/readv.html
wasm3 and toywasm fail with inval. (as i expect)
i feel it's a bug in the "other runtimes" you tested.

That's a good point. I was looking at Linux man pread and missed the POSIX requirement.


Style webpage according to Figma file

Style the application based on the designs on Figma

I can do this

Is there a specific background that makes it hard to read?

If you can see the cards are kind of hard to read. also the navbar contents are kind of overflowing or something.

This is the updated commit: https://deploy-preview-92--mlh-prep-22-nov-prep-2-project.netlify.app/

Great! looks amazing


Fix misspelling of "performs" each time it appears

 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.


Use azure-core-test APIs to manage getting HttpClient in test

Use APIs from TestBase to get the HttpClient used in generated test code. These APIs will use the proper HttpClient implementation based on the environment setup when azure-sdk-for-java runs tests.

No changes needing a change description found.

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs


wip travis build tweaks

note to self: try splitting compile and test - use zinc for compile - will require some memory profile tweaks

removing the milestone - this shouldn't hold up the release

Are the changes in the PR OBE now?


stage1/init: incorrect ppid written when using --private-net

When using --private-net, init.go uses exec.Cmd to start nspawn (instead of syscall.Exec), but continues set ppid to os.Getpid(). This causes stage0:enter to fail, as it chooses the incorrect process ns to enter.
PR with potential fix: #1003

Fixed by #1003. Thanks!


Add in-memory provider for testing purposes

Hello,
I find this project amazing and so well implented. To bad noone made an inmemory implementation of the innerworkings.
Yes, there are some mocks and stuff in the test projects. But It'd be nice to have at least something pre-made, well-tested, to use in our unit tests.
I will try to implemented everything myself, but I'm adding this issue just in case someone already did or just as a reminder/feature-request.
PS: If I get something working I'll push it to some repo to see how well made is and maybe it can be the start point of the implementation.
Cheers

Post a link to your implementation when it's done and we might implement something similar in the project.

That's a good idea, I'll add a new data provider: OpenCQRS.Store.EF.InMemory

Sorry I didnt reply earlier.
I'm halfway done on mine.  But I'm sure your implementation might be better!
Ill share what I have in this pastebin https://pastebin.com/Zps93Wqj
Will expire in 2 weeks! Dont want people seening my RUSH OUT code. xD
I did copy-pasta Event, Aggregate, and Command documents from mongo provider project. C:
I'm currently observing how ICommandStore and IEventStore works.  Very Simple, I like it.
Main thing here is just a InMemoryStore, which I merged from both stores. Even forgot to move up List<EventDocument> Events.
I havent even started with the bus stuff.
There are a couple of design thingies I found, but i might open a separate issue about them. (Sync and Async methods)

Sorry I didnt reply earlier.
I'm halfway done on mine.  But I'm sure your implementation might be better!
Ill share what I have in this pastebin https://pastebin.com/Zps93Wqj
Will expire in 2 weeks! Dont want people seening my RUSH OUT code. xD
I did copy-pasta Event, Aggregate, and Command documents from mongo provider project. C:
I'm currently observing how ICommandStore and IEventStore works.  Very Simple, I like it.
Main thing here is just a InMemoryStore, which I merged from both stores. Even forgot to move up List<EventDocument> Events.
I havent even started with the bus stuff.
There are a couple of design thingies I found, but i might open a separate issue about them. (Sync and Async methods)

Thanks for your contribution, look forward to seeing your project.

@lucabriguglia did you check my pastebin? Can you tell me if my implementation is going the right way?

Got it working. I'll try to PR it this weekend! Need to clean up the code and some refactoring.

You know, i was thinking that maybe it's better to add the EF In-memory provider, and call it a day? xP
Good part is that I got a good look into the internals :)

Yeap, EF is good for integrations tests. But my memory store fits better for unit testing aggrates without the need for entity framework.
I'd love to use both!

I'll have a look as soon as I can.

@andreujuanc your link is broken

Added in memory database provider for entity framework in the Dev branch: https://github.com/OpenCQRS/OpenCQRS/tree/Dev/src/OpenCqrs.Store.EF.InMemory

It's a good start :-)

Do you mind share with us an example of a unit test using it?

I know it's a bit crude, but this way, using a memorystore instead of a inmemory EF DB, My domain can be tested without incorporating any especific implementation on how i'll store the data.
That way is not just faster, but migration free.
Here's a small peek of a PoC design i'm working on.
        [Fact]
        public async Task EditItem()
        {
            var (repository, container, dispatcher) = Setup();

            var text = "Testing";
            var newItem = new ItemCommands.NewItem(text, false);

            await dispatcher.SendAndPublishAsync<ItemCommands.NewItem, Item>(newItem);
            //var status = await handler.HandleAsync(newItem);

            var SavedItem = await repository.GetViewModelById(newItem.AggregateRootId);

            var editText = "Testing 2";
            var editItem = new ItemCommands.EditItem(SavedItem.Id, editText);
            await dispatcher.SendAndPublishAsync<ItemCommands.EditItem, Item>(editItem);

            SavedItem = await repository.GetViewModelById(newItem.AggregateRootId);
            Assert.Equal(SavedItem.Text, editText);
            Assert.Equal(SavedItem.Id, newItem.AggregateRootId);

        }

        private  (ItemRepositoryInMemory, MyIoC, Dispatcher) Setup()
        {
            var repository = new ItemRepositoryInMemory();
            var store = new InMemoryStore(new VersionService());
            var busdistpacher = new Core.Tests.Mocks.InMemoryBusMessageDispatcher();

            var container = new MyIoC((new[] { typeof(Item) }).Select(x => x.Assembly).ToArray());
            container.Register<IItemsRepository>(() => repository);

            container.Register<IEventStore>(() => store);
            container.Register<ICommandStore>(() => store);
            container.Register<IBusMessageDispatcher>(() => busdistpacher);
            container.Register<IResolver>(() => container);

            container.Register(typeof(Repository<Item>));
            container.Register(typeof(CommandSender));

            container.Register(typeof(EventFactory));
            container.Register(typeof(HandlerResolver));
            container.Register(typeof(EventPublisher));
            container.Register(typeof(QueryProcessor));

            container.Register<Dispatcher>();
            container.Build();

            var dispatcher = container.Resolve<Dispatcher>();

            return (repository, container, dispatcher);
        }

NOTE: please do not rate my unittest skills! 👅

In memory database provider added in Version 5.3


kepub page numbers doubled on some conversions

some epubs when converted to kepub have double the page numbers, but the first half of the pages are ignored by my Kobo Clara Color, the device jumps from page 1 to half way through the total.
The pages don't seem to be there unless I use the slider at the bottom of the screen and go back into the part that was jumped by the kobo. The pages are not blank and it is as if the book has been doubled even thought the file size is not

Is the TOC in the same order as the spine?

yes I have checked the TOC order, I managed to fix the issue if I manually save the TOC in calibre after renaming all the html files.
I also asked other users on reddit
https://www.reddit.com/r/kobo/comments/1eulj05/kepub_files_with_double_page_count/
and found this on mobile read
https://www.mobileread.com/forums/showthread.php?t=361011


Move 'ns not found' into mongo adapter.

'ns not found' is a mongo implementation detail, it should exist in the mongo adapter.

Current coverage is 92.92%

Merging #1541 into master will increase coverage by +0.03% as of 67dae46

@@            master   #1541   diff @@
======================================
  Files           87      87
  Stmts         5506    5501     -5
  Branches      1022    1021     -1
  Methods          0       0
======================================
- Hit           5115    5112     -3
  Partial          9       9
+ Missed         382     380     -2

Review entire Coverage Diff as of 67dae46

Powered by Codecov. Updated on successful CI builds.


Table incorrectly throwing Exception instead of None when no selection

Expected Behavior

When you check the selection of a Table that hasn't got a selection, None is returned, as that's what https://toga.readthedocs.io/en/latest/reference/widgets/table.html says should happen.

Current Behavior

Instead, a AttributeError is thrown:
Traceback (most recent call last):
  File "_ctypes/callbacks.c", line 234, in 'calling callback function'
  File "/Users/geoffc/venv/toga-experiment/lib/python3.6/site-packages/rubicon/objc/runtime.py", line 1033, in _objc_method
    result = f(py_self, *args)
  File "/Users/geoffc/git/toga/src/cocoa/toga_cocoa/widgets/button.py", line 14, in onPress_
    self.interface.on_press(self.interface)
  File "/Users/geoffc/git/toga/src/core/toga/handlers.py", line 61, in _handler
    result = handler(interface, **extra)
  File "table-selection-exception", line 6, in button_handler
    print("Selection: {}".format(table.selection.column_1))
  File "/Users/geoffc/git/toga/src/core/toga/widgets/table.py", line 92, in selection
    return self._selection
AttributeError: 'Table' object has no attribute '_selection'

Steps to reproduce

Save this script:

import toga

table = toga.Table(['Column 1'])

def button_handler(widget):
    print("Selection: {}".format(table.selection.column_1))

def build(app):
    box = toga.Box()

    table.data.insert(0, 'foo')
    table.data.insert(0, 'baa')
    box.add(table)

    button = toga.Button('Print Selection', on_press=button_handler)
    button.style.padding = 50
    button.style.flex = 1
    box.add(button)

    return box

def main():
    return toga.App('First App', 'org.pybee.helloworld', startup=build)

if __name__ == '__main__':
    main().main_loop()

Run it, python example-script

Without clicking "foo" or "baa", click the button. You will see an exception thrown.

Your Environment

Python Version (list the specific version number)

$ python
Python 3.6.3 (default, Nov 29 2017, 07:34:08)
[GCC 4.2.1 Compatible Apple LLVM 8.1.0 (clang-802.0.42)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import toga
>>> toga.__version__
'0.3.0.dev8'

Operating System and Version (select from the following and list the specific version number; if your OS is not listed, list that as well)

[x] macOS - version: 10.13.3 (High Sierra)
[ ] Linux - distro:   - version:
[ ] Windows - version:
[ ] Other - name:  - version:

Toga Target (the type of app you are trying to generate)

[ ] android
[x] cocoa
[ ] django
[ ] gtk
[ ] iOS
[ ] tvOS
[ ] watchOS
[ ] winforms
[ ] win32
[ ] Other (please specify)

Fixed in #403


Per-Subscription Discounts

The mock library doesn't seem to take into account that discounts can be applied per-subscription. I ran into this when subscription.discount was a NoMethodError, but it may also appear when creating a subscription (it should take the coupon param).
https://stripe.com/docs/api#create_subscription

Yes, I have confirmed that passing a coupon param to Stripe::Subscription.create does not work as expected.  No discount is applied to the subscription


Users should be able to filter out paths and we should have a list of paths to exclude

Currently we get bogged down in SxS a lot, and its just junk.  We should filter this out and make it optional to turn this filter off.  At the same time, we could take a list of strings as args and skip those too, speeding up the crawl

We do now provide the option to bail a share #56


[ijg-libjpeg] update to 9e

Fix #24338
update ijg-libjpeg to 9e
no feature needs to test.

Thanks for the update!


NodePort for cp-zookeeper and cp-schema-registry

Currently it is possible to set cp-kafka to run with NodePort instead of ClusterIP, but there is no way to do the same for the zookeeper and schema registry services.
Is there a workaround which would allow me to expose these services to the localhost? Or would it be possible to add such a feature?

For SR and ZK you can write your own Service resources with NodePort or any other required types.  I wouldn't suggest to open ZK to access it from outside if you have not reasons to make ZK accessible from from outside.

This is only for local development purposes, where I am running my application directly in the IDE, and would like to connect to the cp-helm-charts that are running on my local machines kubernetes cluster.
As I would prefer to keep the same port configuration, I have been attempting this suggested solution with services of type LoadBalancer with same port as targetport.
Sadly it doesn't seem to be working. Although the ports are exposed and the kafka/schema-registry/zookeeper seem to be reachable, they aren't accepting the connection from my application (Java/Spring).
Am I missing any specific settings to allow connections from outside the kubernetes cluster?

missing any specific settings to allow connections from outside the kubernetes cluster

Does this help? https://strimzi.io/blog/2019/04/17/accessing-kafka-part-1/


RT-1.2: Updating BGP peer config to have V4 and V6 routes to respective neighbor

When IPv4/IPv6 (AfiSafi) is enabled for all neighbors. The IPv6 routes are received from the ATE over IPv4 and IPv6 peer.
The IPv6 routes received over IPv4 peer are considered active based on the route selection over NextHop (::ffff:<IP_ADDRESS>), as all the other parameter for the IPv6 routes is same between the IPv4 and IPv6 peer.
These IPv6 routes show up as Active under the IPv4 peer, but in RT-1.2 script expects these active routes under IPv6 peer in "verifyPrefixesTelemetryV6" function.
Thus to make sure script meets test requirement of ipv6 routes are exchanged over ipv6 neighbor, and similarly ipv4 routes over ipv4 neighbor, we need to disable inheritance of the other not-required protocol family under neighbor configuration.

"This code is a Contribution to the OpenConfig Feature Profiles project ("Work") made under the Google Software Grant and Corporate Contributor License Agreement ("CLA") and governed by the Apache License 2.0. No other rights or licenses in or to any of Nokia's intellectual property are granted for any other purpose. This code is provided on an "as is" basis without any warranties of any kind."

Can you help add a few words describing the motivation of why making the suggestions (is it required by the README test plan)?

Hi Xiao @xw-g
This change is needed to align with the inheritance model discussed in openconfig/public#774 -> in the current code both IPv4 and IPv6 are enabled on a protocol level, so in a per-neighbor config we want to disable inheritance of the other protocol family (i.e. keep v4 peers enabled with ipv4-unicast afi/safi and v6 peers with ipv6-unicast afi/safi only)
We also introduce the same logic in another pr #1059

Can you help add a few words describing the motivation of why making the suggestions (e.g. the current code does not meet the test plan README, or is it just about some vendor OS behaviors?). Thanks.

Updated PR description with more details and also updated README file with test specifics.

@xw-g, was there any updates on the pre-submit/merge efforts?

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 57.081%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1181

Relevant Lines:
2069

💛  - Coveralls

b/271889146 finished the internal presubmit test. merging it now.

/gcbrun


Optimize h

The child of #187.

Things to explore:

[ ] Better bench use cases. @jbucaran ideas?
[ ] Node constructors (https://github.com/hyperapp/hyperapp/pull/187#issuecomment-294316864)
[ ] Recycling.

Other h out there:

preact: https://github.com/developit/preact/blob/master/src/h.js
react: https://github.com/facebook/react/blob/5c6a496d98b80d19d851c2ec3a56d760b7118a50/src/isomorphic/classic/element/ReactElement.js#L180
inferno: https://github.com/infernojs/inferno/blob/master/packages/inferno-create-element/src/index.ts

Refs:

Why 2 for loops: https://github.com/hyperapp/hyperapp/pull/187#issuecomment-294339008

I'll increase coverage when we validate the code before.

Are we ok with this implementation?
If so, I can add tests to get 100% coverage and merge it.
As discussed with @jbucaran node constructors and recycling will be introduced in another PR.

@ngryman Thanks, but did you run these changes through the js-framework-benchmarks? That's the indicator I've used before making "big" changes that could affect performance. I know you are trying to improve h here, so I am optimistic.
Let me know the results if and when you have them! 👍

@ngryman Did ever have a chance to run these through the benchmarks? 🤔 I'd really like to make a decision here! 👋😄

@jbucaran Hey I gave you the result on Slack 15 days ago 😋
They were approx 7% better, which is not a game changer, but I didn't expect more from h.

@jbucaran We could also gain bytes and perf if this babel issue is resolved: https://github.com/babel/babel/issues/2034#issuecomment-294189475
The guy seemed open to a PR for this. I might get some free time next week, I think I'm gonna push this, it would also make lots of library authors happier.

They were approx 7% better, which is not a game changer,

7% is actually quite a lot

@ngryman  That JSX transform fix would be great.  When I first looked at 'h()', that arguments stuff struck me as really strange!

@ngryman Those results looked great, so I setup js-frameworks-benchmarks again from scratch and here are my results using the h.js currently on master VS your h.js (I made them both use the same app.js to avoid false positives).

But like @SkaterDad is saying, that JSX transform fix would be really great.
Not sure what else to do.

I ran it --count 5, which took a while and the results were better:

@jbucaran I'm trying to understand, you are comparing 0.11.0 with 0.9.1. Where is the optimized h? Those two versions have lots of other additions.

@ngryman Ignore the labels:

0.11.0 === master app.js + nygrman's h.js
0.9.1 === master app.js + master h.js

@jbucaran Surprised, I'll take a look. The fact that the impact is not visible enough in this benchmark wouldn't surprise me, but your first batch of result is very... interesting :D

I've run several benchmarks, several times and got the same results for both implementations. I still can't explain why 0.11 is the same and 0.9 had a real gap between the two.
I have to admit that starting optimization passes with h was not the best idea. I've done it because it was quick and fun. But it does not really bring a lot to the table right now... I kind of expected that, but I was hoping for a slight perf boost like I measured in 0.9.
I should have started elsewhere: normalizing vnodes.
The proposed implementation is faster because potentially optimizable by the JIT. Currently in a real world use case, we don't leverage that optimization because our vnodes are of several shapes, ... and we have bigger problems.
When we will have a "typed" vtree, we'll probably have a little performance boost from this PR, mainly in animations where h could potentially become hot. But again, this will be tiny.
I would propose to focus on normalizing our vnodes and recycle them (because we are generating tons of garbage right now) and revisit this PR later when those optimizations are done.


Latex barrier bugs

There have been a number of attempts at fixing barriers in the latex drawer (https://github.com/Qiskit/qiskit-terra/pull/1727, https://github.com/Qiskit/qiskit-terra/pull/1534, https://github.com/Qiskit/qiskit-terra/pull/1361), but there are still bugs.
from qiskit import *
qasm = """
OPENQASM 2.0;
include "qelib1.inc";
qreg q[7];
cx q[1],q[6];
barrier q[1],q[4],q[5],q[6];
u3(1.8,-0.5,0.4) q[1];
cx q[0],q[1];
"""
circ = QuantumCircuit.from_qasm_str(qasm)
circ.draw(output='latex')

Bug 1: The barrier should only be on qubits 1, 4, 5, 6 -- but it is on qubits 1 to 4.
Bug 2: It cuts through the U3 gate.

Hi, I want to try this issue.
Bug 2:

One possible solution is to set the horizontal offset value in \barrier. This bug will not occur with a smaller box (H gate for ex.).
Another solution is to make U3 gate use 2 columns. The first column will have \qw. This way
U3 box will not overlap with barrier column.
I tested both. Please suggest if you have any other idea.

Hi, I think this has to depend on the width of the gate in question. It's not just U3, it happens with other gates such as U1 and U2 as well. So I'm good with any solution that works but it should not hardcode to certain gates and be general. Thanks.

Details of the problem - for barrier one column space (say A) is allocated. But in the circuit image, barrier location (where it appears)  depends on the next column (say B) width - -0.95em from the center of the B. Boxed gates with single characters won't overlap, but for others, there will be overlap.
The proper fix is to place the barrier in the column space allocated for it using offset value arg, which is in em unit.
I am not sure how to map column width(in characters) to offset value, so that solution is generic.
What I have in mind - If op is multi-character gate and previous column contains barrier, set
offset= -4.0em elseoffset = -1.65em (lesser value).
One plus is fix will be local (All change happens in one place).
@ajavadia What do you suggest?

Thanks for the explanation!
There is one more idea - When barrier op is present, add \qw in a new column, but append  \barrier[0em]{*} to the previous column. This way barrier location would be fixed.
@mtreinish What is your opinion on this?

I raised a PR to test the changes. I tested manually with simple circuits (few found in previous bug reports) and so far good. Also tried circuits in this link - qiskit/advanced/terra/3_advanced_circuit_visualization.ipynb. I didn't find any issue.
Fix added here - https://github.com/Qiskit/qiskit-terra/blob/master/qiskit/visualization/latex.py#L626-L634 and https://github.com/Qiskit/qiskit-terra/blob/master/qiskit/visualization/latex.py#L743-L753 can be removed right? Can you point me where test circuits for those changes can be found?


MLIL mappings from HLIL are absent

The mappings from HLIL instructions to MLIL instructions is not correctly maintained, meaning that trying to fetch the MLIL instruction from HLIL will always fail from the API. The mapping is maintained during early HLIL optimization but lost during AST construction.
This also breaks the value and possible_values APIs.

The affected APIs have been temporarily disabled to throw an exception instead of simply returning incorrect results. They will be reenabled once the issue is fixed.

Fixed in build 2242


Player Image

Hi, I have some problems trying to get the player Image, could you help me please?
I've started now with c# and I'm not used to :)
Thx

var imageBytes = await client.GetPlayerImageAsync(auctionInfo);
:+1:

Yes, that's what I've found, but I don't know how to use it TT

lol > byte[] > Format: PNG
Then you can choice to save byte[] to file or display it on your application.

I do it like this without the toolkit:
string futdbplayerImage = @"https://fifa15.content.easports.com//fifa/fltOnlineAssets/B488919F-23B5-497F-9FC0-CACFB38863D0/2016/fut/items/images/players/web/";

WebClient client = new WebClient();
Image playerImage = GetImage(futdbplayerImage + playerStrings[1] + ".png");
PIC_Player.Image = playerImage;


Support --rolling with --end-date for statusduration.

The logic goes that we look for all issues that transitioned into the target
state before or during the query period, excluding any which transitioned out
of the state before it.
This required updates to the way the duration is calculated which assumed that
"today" was a suitable substitute for the end date.  The end of the query
period is used instead.

Looks good to me. Feel free to merge.


AWS Lambda Dockerfile steps to reduce package size have no effect

Problem description
The AWS Lamdbda Dockerfile ( deployment/aws/lambda/Dockerfile) has a section "# Reduce package size and remove useless files". However, these do not actually reduce the final package size because they are on separate lines and therefore in separate image layers. What actually happens in this case is the files exist in an "earlier" layer, and when they are deleted in a subsequent layer, they're simply not visible to that layer, but the size of all the layers combined is still the same.
Expected Output
Image size reduction steps actually reduce the size of the image.
The easiest way to do this is to put all of the pip install and removal commands in the same RUN command, and concatenate them with && and line break escapes \
Environment Information
Os, Python version, ...

Nevermind, I see that this is only being used to build it, and then the CDK commands copy out of the the image.


[stable/consul] Consul 1.0.0

I'm hoping this resolves #1892. I'd like to get a few more people to test this out before merging.
We've run a 5 pod cluster at work with this configuration, and it seemed to survive a Kubernetes upgrade without issue.
With the release of consul 1.0.0, the raft protocol now defaults to v3 which seems to handle changing IPs much better.
In addition to bumping the consul image tag to 1.0.0, these changes also:

Add pod anti-affinity to ensure that we don't schedule 2 pods on the same node as this defeats the purpose.
Use a rolling update strategy for updating consul's stateful set.
Add a pod disruption budget so that scheduled cluster maintenance doesn't take down the consul service.

/ok-to-test

@jonstacks Has enough testing been done so you would feel comfortable merging?

@mattfarina,
We've done some pretty good testing and these changes have been working for us, but I was hoping a few others could also try it out and report if they have any problems.
I have some concerns that this PR might break some people.

With the addition of the pod anti-affinity, it will ensure that pods for the stateful set aren't scheduled on the same node. I'm fairly certain that consul already has its own check to ensure that you aren't running 2 copies on the same node, but I'm not certain.
I don't know how other people are administering their clusters, but the pod disruption budget should prove useful. Since doing math in charts is quite difficult, you have to specify the maxUnavailable in the values.yaml. The default should be fine for people running a 3 pod cluster, but if running more, you might want to up it. If you don't want this at all, you'd have to set maxUnavailable to false.
Upgrading to consul 1.0.0 changes the consul API. Working with some of the people on our dev teams, they had to change the API calls they were making as some of routes are more strict on HTTP method. See Upgrade specifics

With these things in mind, I'm thinking it might be appropriate to bump the major version of the chart, but am curious what others think as well.
For context, we are running a 5 pod cluster in GKE and haven't had any issues after upgrading to 1.0.0. We've seen better stability and are pretty confident when doing a rolling kubernetes version upgrade. Like I mentioned before, the only gotcha we've experienced is the change in the consul API.

One minor nit - the README still states that the default ImageTag is v0.7.5.

I would also suggest changing requiredDuringSchedulingIgnoredDuringExecution to preferredDuringSchedulingIgnoredDuringExecution.  Otherwise this enforces a hard requirement that cluster size > Replicas.

@MikeSchuette,
Good catch, I'll update the README to reflect the change.
For requiredDuringSchedulingIgnoredDuringExecution vs preferredDuringSchedulingIgnoredDuringExecution I would think that for consul you would want the former. I'd think that pod anti-affinity must be enforced, otherwise you risk the chance of a single node failure taking down the service via loss of quorum. I was following an example in the kubernetes docs for tolerating node failure. While the example was for zookeeper, I'd assume we'd want the same semantics for consul.

required is a better production option, but it means that you can't test cluster creation/etc on minikube.  Making it an option would provide a compromise, as the Zookeeper chart does.

Installing with antiAffinity: soft on Helm 2.7.2 yields:
Error: error validating "": error validating data: [field spec.template.spec.affinity.podAntiAffinity.preferredDuringSchedulingIgnoredDuringExecution[0].weight for v1.WeightedPodAffinityTerm is required, field spec.template.spec.affinity.podAntiAffinity.preferredDuringSchedulingIgnoredDuringExecution[0].podAffinityTerm for v1.WeightedPodAffinityTerm is required, found invalid field labelSelector for v1.WeightedPodAffinityTerm, found invalid field topologyKey for v1.WeightedPodAffinityTerm]

The schema for preferred is different from required.  See https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#an-example-of-a-pod-that-uses-pod-affinity or the Zookeeper chart.

@MikeSchuette,
I thought I had pushed it to a separate branch, but I guess not. I'm still testing those changes, but thanks for catching that! I'm hoping to have that fixed and tested by the end of the day.

I've tested both the default option of using "hard" anti-affinity, in addition to "soft" anti-affinity. They should be good to go now.

@jonstacks can you ping me or the maintainers when you think this is ready for us to look at merging?

cc: @lachie83 just to loop you in since you're listed as the maintainer.

I verified installation with soft anti-affinity.  LGTM.

while installing with helm install --name consul stable/consul
i get the error
error validating data: found invalid field updateStrategy for v1beta1.StatefulSetSpec
ive  ran helm update repo and same problem.

@asafab can you provide the output of the following commands?

helm version
kubectl version

helm version
Client: &version.Version{SemVer:"v2.5.0", GitCommit:"012cb0ac1a1b2f888144ef5a67b8dab6c2d45be6", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.5.0", GitCommit:"012cb0ac1a1b2f888144ef5a67b8dab6c2d45be6", GitTreeState:"clean"}

kubectl version
Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.3", GitCommit:"2c2fe6e8278a5db2d15a013987b53968c743f2a1", GitTreeState:"clean", BuildDate:"2017-08-03T07:00:21Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.7", GitCommit:"095136c3078ccf887b9034b7ce598a0a1faff769", GitTreeState:"clean", BuildDate:"2017-07-05T16:40:42Z", GoVersion:"go1.7.6", Compiler:"gc", Platform:"linux/amd64"}

@asafab thank you for providing those details.
Your Kubernetes cluster is running v1.6.7. StatefulSet at API version apps/v1beta1 didn't support updateStrategy in 1.6. That was introduced in Kubernetes 1.7. This is the root of the problem.
The Charts repo currently only supports the current and last minor versions of Kubernetes (currently 1.8 sand 1.7) Changing APIs like this are one of the reason. We hope to expand to the current and previous 2 minor versions when we a good way to support all 3 versions and have some checking for all versions.
In the next year, as the workload APIs become more stable, we should be able to offer better support.

thank you for the detailed answer.  👍


feat: Create a GitHub data source using the new Project structure

This is a follow-up to #75, and huge step toward enabling #43.
This converts the GitHub querying code to use the new ProjectCollection/Project/Finding data structures.
I also included commented-out code in internal/scan.go that I used to prove this out. That is ultimately what will lead to the full enablement of #43.

Note: I did not yet write any tests for this, and I'm sure codecov is going to complain about that. I will get to that, but I wanted to get this code up since it's large and exciting!


Error while bundling

Describe the bug
Gradle fails to bundle package.
To Reproduce
Steps to reproduce the behavior:

start any empty react-native projects
run npm i @blackbox-vision/react-native-mercadopago-px as explained in https://react-native-mercadopago-px.blackbox-vision.tech/docs/install
run-android fails with gradle error:
`error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup.
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081

FAILURE: Build failed with an exception.

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

Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
Could not find com.mercadopago.android.px:checkout:4.45.0.
Searched in the following locations:
- https://repo.maven.apache.org/maven2/com/mercadopago/android/px/checkout/4.45.0/checkout-4.45.0.pom
- file:/Users/luchux/.m2/repository/com/mercadopago/android/px/checkout/4.45.0/checkout-4.45.0.pom
- file:/Users/luchux/Devel/compartir/node_modules/react-native/android/com/mercadopago/android/px/checkout/4.45.0/checkout-4.45.0.pom
- file:/Users/luchux/Devel/compartir/node_modules/jsc-android/dist/com/mercadopago/android/px/checkout/4.45.0/checkout-4.45.0.pom
- https://dl.google.com/dl/android/maven2/com/mercadopago/android/px/checkout/4.45.0/checkout-4.45.0.pom
- https://www.jitpack.io/com/mercadopago/android/px/checkout/4.45.0/checkout-4.45.0.pom
Required by:
project :app > project :blackbox-vision_react-native-mercadopago-px

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

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

BUILD FAILED in 6s
at makeError (/Users/luchux/Devel/compartir/node_modules/@react-native-community/cli-platform-android/node_modules/execa/index.js:174:9)
at /Users/luchux/Devel/compartir/node_modules/@react-native-community/cli-platform-android/node_modules/execa/index.js:278:16
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async runOnAllDevices (/Users/luchux/Devel/compartir/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/runOnAllDevices.js:106:5)
at async Command.handleAction (/Users/luchux/Devel/compartir/node_modules/react-native/node_modules/@react-native-community/cli/build/index.js:192:9)

info Run CLI with --verbose flag for more details.
`
Expected behavior
gradle should build well.
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Version [e.g. 22]

Additional context
Add any other context about the problem here.
Dependencies
Add the name and version of all dependencies of your project.

@luchux would you mind to create a repo for case reproduction? I'm not able to replicate the issue from our example application in the library.

Ok Will try again with a blank new project and see what happens.
Cheers.
On Wed, Nov 3, 2021 at 4:42 AM Jonatan E. Salas @.***>
wrote:

@luchux https://github.com/luchux would you mind to create a repo for
case reproduction? I'm not able to replicate the issue from our example
application in the library.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/BlackBoxVision/react-native-mercadopago-px/issues/56#issuecomment-958951654,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALIISDC6RUBXZE37WU5NQLUKENYZANCNFSM5G2XXBTA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@luchux thanks! let me know if it works, and if it doesn't work please share to me the repo so I can lookup and find a fix for it!

Hello @JonatanSalas @luchux I have a same error, how I can fix it? Thanks


[SPARK-39548][SQL] CreateView Command with a window clause query hit a wrong window definition not found issue

What changes were proposed in this pull request?

In the inline CTE code path, fix a bug that top down style unresolved window expression check leads to mis-clarification of a defined window expression.
Move unresolved window expression check in project to CheckAnalysis.

Why are the changes needed?

This bug fails a correct query.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

UT

R: @cloud-fan

Can one of the admins verify this patch?


Position tooltip relative to highlighted data item

What problem does this feature solve?
Using tooltip position callback, one can position the tooltip relative to the mouse or bounding container, but it does not expose any information about the highlighted data item or its position.
What does the proposed API look like?
series-line.tooltip.position = function (point: Array, params: Object|Array.<Object>, dom: HTMLDomElement, rect: Object, size: Object, itemRect: Object)

I wasn't quiet follow, could you be more specific? Actually, tooltip's position wasn't easy......

@susiwen8 Sure. I want to position the tooltip relative to (near to) a highlighted data item (shown with red arrow) instead of relative to the mouse (shown with red circle).

Ok, I see, 5.0 will solve this
https://github.com/apache/incubator-echarts/pull/12947

@susiwen8 How did 5.0 solve this? The documentation for tooltip.position is word-for-word the same as v4.

I am having the same problem. @Bilge did you figure this out?

No. Devs offered a vapour solution and the bot closed it.

@susiwen8 can we reopen this issue? Because tooltip.position does not solve it.


Use c_free for memory that has been allocated with c_malloc and c_calloc

I was compiling the osqp_mex function against an already compiled osqp version (similar to what was described in https://github.com/oxfordcontrol/osqp-matlab/issues/27), and my MATLAB was crashing because quantities that were allocated with c_malloc and c_calloc were then freed with mxFree.
While the direct use of  c_malloc and c_calloc  can be converted to the corresponding mx** allocator by defining MATLAB  for the osqp_mex compilation unit, this was not possible for the allocation done via csc_matrix, as fhat function is compiled as part of OSQP and whose definition can't be changed.
Changing to use c_free for freeing all the memory that was allocated with  c_malloc and c_calloc fixes the problem, and works as expected even if MATLAB is defined, as in the case of the official build procedure for the MATLAB bindings.

I updated the PR with a new commit ( https://github.com/traversaro/osqp-matlab/commit/09faf01f42f7a73fac0b03332e6b0f6976a943c8 ) as it turns out that there were other mismatched calls (c_malloc/mxFree), as reported in https://github.com/ami-iit/osqp-matlab-cmake-buildsystem/issues/5 .
With this changes, I was able to run the complete test suite (without codegen tests).


Closes #1

Updated validations.py python script.
Fixed the behaviour of validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

will fix the edit

have fixed the issue


Can not add conda executable in pycharm-ce

Description
Can not add conda executable in pycharm-ce.
Already did everything described in README.

Versions
❯ pixi --version
pixi 0.26.1
❯ pixi list | grep pixi-pycharm
pixi-pycharm                          0.0.6      unix_1234567_0         8.6 KiB    conda  pixi-pycharm-0.0.6-unix_1234567_0.conda

PyCharm version: PyCharm 2024.1.4 (Community Edition)
PC-241.18034.82，2024年6月25日 构建
17.0.11+1-b1207.24 amd64
VM: OpenJDK 64-Bit Server VM，JetBrains s.r.o.
Platform: Debian 12
Linux zjc-office 6.1.0-23-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.99-1 (2024-07-15) x86_64 GNU/Linux
Logs
Attempting to run: ['info', '--envs', '--json']
Traceback (most recent call last):
  File "/home/zjc/python_works/seiser_pixi/.pixi/envs/default/libexec/conda", line 165, in <module>
    sys.exit(main(args))
             ^^^^^^^^^^
  File "/home/zjc/python_works/seiser_pixi/.pixi/envs/default/libexec/conda", line 139, in main
    conda_info_envs_json()
  File "/home/zjc/python_works/seiser_pixi/.pixi/envs/default/libexec/conda", line 79, in conda_info_envs_json
    "envs": pixi_envs(),
            ^^^^^^^^^^^
  File "/home/zjc/python_works/seiser_pixi/.pixi/envs/default/libexec/conda", line 57, in pixi_envs
    platform = pixi_json(["info", *std_pixi_args()])["platform"]
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/zjc/python_works/seiser_pixi/.pixi/envs/default/libexec/conda", line 53, in pixi_json
    return json.loads(pixi([*cmd, "--json"]))
                      ^^^^^^^^^^^^^^^^^^^^^^
  File "/home/zjc/python_works/seiser_pixi/.pixi/envs/default/libexec/conda", line 22, in pixi
    out = subprocess.check_output(["pixi", *cmd])
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/zjc/python_works/seiser_pixi/.pixi/envs/default/lib/python3.11/subprocess.py", line 466, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/zjc/python_works/seiser_pixi/.pixi/envs/default/lib/python3.11/subprocess.py", line 548, in run
    with Popen(*popenargs, **kwargs) as process:
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/zjc/python_works/seiser_pixi/.pixi/envs/default/lib/python3.11/subprocess.py", line 1026, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/home/zjc/python_works/seiser_pixi/.pixi/envs/default/lib/python3.11/subprocess.py", line 1955, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'pixi'

https://github.com/pavelzw/pixi-pycharm/issues/16#issuecomment-2066359437 might fix this. Where is your pixi installed? If it's in ~/.pixi/bin/pixi, #20 is the issue which I should fix at some point.

#16 (comment) might fix this. Where is your pixi installed? If it's in ~/.pixi/bin/pixi, #20 is the issue which I should fix at some point.

Thank you very much! I found the solution works in #16 , I installed as default in ~/.pixi. Sorry to bother you, have a nice day.


[FLINK-34383][Documentation] Modify the comment with incorrect syntax

What is the purpose of the change
There is an error in the syntax of the comment for the class PermanentBlobCache
Brief change log
modify the comment in class PermanentBlobCache
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

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

Documentation

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

@flinkbot run azure

@flinkbot run azure

@zhuzhurk,hi,this is my first time participating in an Apache project,could you help me review this PR and give me some advice? thanks a lot.

Thanks for participating in the community work! @lxliyou001
Usually we will avoid creating individual JIRAs and PRs for this kind of typos to avoid polluting the commit history, as long as it does not confuse or mislead users/developers.
To participate in Flink community work , You can find starter tasks in JIRA[1].
Or you may take a task from the release testing of Flink 1.19 [2]. It is very important for the release of Flink.
[1] https://issues.apache.org/jira/browse/FLINK-34419?jql=project %3D FLINK AND status in (Open%2C "In Progress"%2C Reopened) AND labels %3D starter
[2] https://issues.apache.org/jira/browse/FLINK-34285


LD_LIBRARY_PATH setting per folder

Is it possible to set LD_LIBRARY_PATH and launch julia with per folder saved settings? Currently I start a terminal , set LD_LIBRARY_PATH and connect to it.

I develop code that calls cpp libraries and the LD_LIBRARY_PATH may need to change in different projects.

you want to have LD_LIBRARY_PATH as an environment variable, or just pass it as an command line args for julia startup ?
If former, you can set it before launching Atom or setting it in your init script.
If latter, you can just use ARGUMENTS config under Julia Options.

in different projects.

for that purpose, you need to use this pacakge: https://github.com/harmsk/atomic-management
but it can make your Atom startup slow.


updating maven version

Version 3.3.3 is no longer available at http://www.us.apache.org/dist/maven/maven-3. Upgrading to the latest version.

LGTM

LGTM


API: Add extension information the Node message.

Report extension information in the Node message.
Risk Level: Low
Testing: Unit Tests
Docs Changes: N/A
Release Notes: N/A
Fixes: #8332
Signed-off-by: Yan Avlasov<EMAIL_ADDRESS>

This PR is to discuss how to best add versioning and categorization to the extension registry so it can be added to the Node message. Specifically:

do we need to have "canonical" category for the extensions, expressed as enum in the Node proto. This would be broad buckets, like network and http filter, stats sink, cred provider, etc. The existing category is a free form string.
Would it be better to have common base interface for all factories where the "getter" for the version and potentially canonical category can be added. Without the base class it is difficult to retrieve factory specific attributes in a generic manner.

@jpeach @alexburnos @mattklein123 @markdroth @ramaraochavali anything else that needs to be done here before we can land this PR? I'd like to see this intercept 1.13.0, which will be cut near start of Jan.

LGTM, this is great, but it would be nice to also have an e2e test, e.g. something like ads_integration_test that validates some example of what the Node looks like on the wire.
/wait

I will need to figure this one out.

LGTM, this is great, but it would be nice to also have an e2e test, e.g. something like ads_integration_test that validates some example of what the Node looks like on the wire.
/wait

done

@yanavlasov the coverage failure looks real (I thought it was a flake at first and kicked it). Can you take a look? Thanks.

Can you merge master just to make sure we don't have any v3alpha transition issues?
/wait

@yanavlasov LGTM, but format CI check is still failing.

I'm going to merge this as is, since the envoy-macos check is known to be broken.


try running nightly in CI at checkin

Try to run only nightly tests from Jenkins.

Pull request was successful experiment to get nightly tests to run during CI.


make build timeout for xcodebuilds match swift packages

Pull Request Description

When we build swift packages, our timeout is 3600, we should match that with xcodebuilds. All our spurious timeouts are occurring on xcodebuilds because the previous default isn't enough.

@swift-ci test


Language Guide overview

For the Language Guide section it would be great to have an overview page of what languages have SDK support, and what SDK features are available in each of those languages. This could also be used to direct users to the repositories with samples and templates for the SDKs.

+1 and call out any discrepancies between spin local and spin cloud

Would a page like the following example be acceptable?

For example, where each word like "Docs" would be a hyperlink to the actual docs. We could also link to code examples i.e. fermyon/examples area etc.
For now this could be manually updated by writing markdown, which is probably fine seeings how the table is not going to be that big/complex at the minute.

If so we could take advantage of the fact that Bartholomew will accept HTML and just maintain using code such as the following:
title = "Language Guide Overview"
template = "common_main"
date = "2022-01-01T00:00:01Z"
[extra]

---

Spin SDK - Language Guide
Overview

<colgroup>
<col style="width: 20%" />
<col style="width: 20%" />
<col style="width: 20%" />
<col style="width: 20%" />
<col style="width: 20%" />
</colgroup>

Language
HTTP Trigger
Redis Trigger
Outbound HTTP
Outbound Redis

Go
Local
 Cloud
 Docs
 Blog
Local
 Cloud
 Docs
 Blog
Local
 Cloud
 Docs
 Blog
Local
 Cloud
 Docs
 Blog

Javascript
Local
 Cloud
 Docs
 Blog
Local
 Cloud
 Docs
 Blog
Local
 Cloud
 Docs
 Blog
Local
 Cloud
 Docs
 Blog

Python
Local
 Cloud
 Docs
 Blog
Local
 Cloud
 Docs
 Blog
Local
 Cloud
 Docs
 Blog
Local
 Cloud
 Docs
 Blog

Rust
Local
 Cloud
 Docs
 Blog
Local
 Cloud
 Docs
 Blog
Local
 Cloud
 Docs
 Blog
Local
 Cloud
 Docs
 Blog

@vdice has collaborated and generated the following Language Guide Overview; thank you so much Vaughn!!!
https://fermyontech-my.sharepoint.com/:x:/g/personal/vaughn_dice_fermyon_com/EY4KT-8I05xKoYpByWlWyhsBok_qHJr6Iyu8ffjmM8_Tyw
This can now be converted to the format which we talked about last week i.e. a multi-language code block style layout that lists each of the features in each of the language tabs.

Once formatted this can go on the developer docs site as a separate menu item under the Spin - Language Guides section (with its own page that is linked to from the aforementioned menu)

Made the decision in Spin 1.0 meeting to use multi-tab code blocks and add each of the features inside each separate tab in the holistic code block.
Also made the decision to add a separate but prominent feedback-link/feedback-mention for users to provide feedback (in case they are having issues or want to get a point across).

First draft of markdown file is at PR https://github.com/fermyon/developer/pull/457

Added and merged at https://github.com/fermyon/developer/pull/457


Buggy manual keeper setup config

I was trying to setup a clickhouse-keeper based on deploy/clickhouse-keeper/clickhouse-keeper-manually with both 3 nodes and 1 node.
Setup fails 100% of the times for latest:alpine (currently, v24.4).
+ NAME=clickhouse-keeper
+ ORD=0
+ MY_ID=1
++ clickhouse-keeper-client --history-file=/dev/null -h clickhouse-keeper.default.svc.cluster.local -p 2181 -q 'get /keeper/config'
Coordination::Exception: All connection tries failed while connecting to ZooKeeper. nodes: <IP_ADDRESS>:2181
Poco::Exception. Code: 1000, e.code() = 111, Connection refused (version <IP_ADDRESS>8 (official build)), <IP_ADDRESS>:2181
Poco::Exception. Code: 1000, e.code() = 111, Connection refused (version <IP_ADDRESS>8 (official build)), <IP_ADDRESS>:2181
Poco::Exception. Code: 1000, e.code() = 111, Connection refused (version <IP_ADDRESS>8 (official build)), <IP_ADDRESS>:2181

I tried downgrading to v23.12, it will keep crashing one by one for 3 nodes.
What is currently the proper config?

v23.9 seems to work, at least peers aren't crashing constantly.

So I tried scaling STS down to 0 replicas and then scaling it back up to 3 replicas, it will fail to boot itself because peer-0 will fail to connect to peer-1 and peer-2.
It's unreasonable to expect the cluster to be always alive, I think keeperTeardown.sh is not working properly?

We are open to pull requests, this is hard to debug keeperTeardown.sh

I mean, I’m using the exact same setup from the examples.
I’ll try to debug more some other time, but this setup is not even functioning properly, so I’m filing the issue for others lest they waste their weekend for nought.

Apparently, this setup does work, but takes a lot of time to reach consensus.
E.g: 3 node cluster with OrderedReady policy will take about 3-4 minutes for the first 2 peers to boot and agree on the ring membership before the third pod can start, so all in all about 6 minutes for the cluster to become alive.


Remove bufferline dependency

I found that yazi.nvim only uses one file from bufferline.nvim, so I added that file here to make the package self-contained. Could you please merge this PR if it looks good? Thanks!

It's a good idea. Thanks!

Actually, I realized I should not be using bufferline for adjusting colors due to license conflicts. It seems to be licensed under GPLv3 while this project is MIT. It would require re-licensing this project as GPLv3, which I think I don't have the right to as I don't hold the copyright to all the code (some of it is written by others).
In my experience not many care about license violations until significant money is involved, but it would be better to avoid any issues altogether. Dealing with software licenses does not really "spark joy" for me, so I would prefer not having to do that at all. As a side note, the popular LazyVim might be in violation too 🤔
I think a good alternative implementation might be available here https://github.com/catppuccin/nvim/blob/main/lua/catppuccin/utils/colors.lua with the MIT license.
I think I will refactor the code to use that instead. Still, it will probably be a good idea to embed and the implementation and strip it down to the bare minimum.

I think I can still use this PR to make the future change, so I'll keep this open for now.

Okay I think I was able to trim down everything to the bare minimum. Thanks for the idea!


Simplify connector protocol

Finish the Simplify Connector Protocol epic, https://github.com/WallarooLabs/wallaroo/issues/2956.  Includes:

#2932, code changes
#2933 and #2934, (mostly) docs changes

Replaced by PR #2983


Login Failed - An error occurred while logging into Studio. Please login on the website or try again later.

Whenever I press Launch Studio, it launches but gives me this error.
Login Failed - An error occurred while logging into Studio. Please login on the website or try again later.
I only changed a fast flag ("HideProxySettings": "False") since I'm trying to load up fiddler to pick up studio traffic.

Uses the latest version


Make multiple demo users

We should have two or three users to demo with - for this, we can either make fake data or select different days from my data.

We only need one demo user, but we should change the data that we're drawing from.


Add operations for account to CLI

Adds a command to request all operations relating to a given account
to the CLI application.
Fixes #163
Is there a GIF that reflects how this work made you feel?

@correlator @kbacha can you guys take another look at this? Thanks!

@kbacha can you take a look at this refactor? Took me a bit of Rust-y try and error to figure out the indent level–aware nesting, but in the end, the solution I got was pretty simple.