[ +382 ms] Persisting file store
           [   +9 ms] Done persisting file store
           [  +12 ms] build succeeded.
           [  +17 ms] "flutter assemble" took 2.237ms.
           [   +4 ms] ensureAnalyticsSent: 0ms
           [   +1 ms] Running shutdown hooks
           [        ] Shutdown hooks complete
           [   +4 ms] exiting with code 0

           > Task :firebase_performance:compileDebugAidl NO-SOURCE
           > Task :firebase_performance:compileDebugRenderscript NO-SOURCE
           > Task :firebase_performance:generateDebugResources UP-TO-DATE
           > Task :firebase_performance:packageDebugResources UP-TO-DATE
           > Task :firebase_performance:parseDebugLibraryResources UP-TO-DATE
           > Task :firebase_performance:generateDebugRFile UP-TO-DATE
           > Task :firebase_performance:javaPreCompileDebug UP-TO-DATE
           > Task :firebase_performance:compileDebugJavaWithJavac UP-TO-DATE
           > Task :firebase_performance:extractDebugAnnotations UP-TO-DATE
           > Task :firebase_performance:mergeDebugGeneratedProguardFiles UP-TO-DATE
           > Task :firebase_performance:mergeDebugConsumerProguardFiles UP-TO-DATE
           > Task :firebase_performance:mergeDebugJavaResource UP-TO-DATE
           > Task :firebase_performance:transformClassesAndResourcesWithSyncLibJarsForDebug UP-TO-DATE
           > Task :firebase_performance:bundleDebugAar UP-TO-DATE
           > Task :firebase_performance:uploadArchives FAILED
           > Task :flutter:packLibsflutterBuildDebug UP-TO-DATE
           > Task :flutter:preBuild UP-TO-DATE
           > Task :flutter:preDebugBuild UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:preBuild UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:preDebugBuild UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:compileDebugAidl NO-SOURCE
           > Task :geolocator:preBuild UP-TO-DATE
           > Task :geolocator:preDebugBuild UP-TO-DATE
           > Task :google_maps_flutter:preBuild UP-TO-DATE
           > Task :google_maps_flutter:preDebugBuild UP-TO-DATE
           > Task :permission_handler:preBuild UP-TO-DATE
           > Task :permission_handler:preDebugBuild UP-TO-DATE
           > Task :permission_handler:compileDebugAidl NO-SOURCE
           > Task :url_launcher:preBuild UP-TO-DATE
           > Task :url_launcher:preDebugBuild UP-TO-DATE
           > Task :url_launcher:compileDebugAidl NO-SOURCE
           > Task :firebase_performance:bundleLibCompileDebug UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:packageDebugRenderscript NO-SOURCE
           > Task :geolocator:packageDebugRenderscript NO-SOURCE
           > Task :google_maps_flutter:packageDebugRenderscript NO-SOURCE
           > Task :permission_handler:packageDebugRenderscript NO-SOURCE
           > Task :url_launcher:packageDebugRenderscript NO-SOURCE
           > Task :flutter:compileDebugRenderscript NO-SOURCE
           > Task :flutter:checkDebugManifest UP-TO-DATE
           > Task :flutter:generateDebugBuildConfig UP-TO-DATE
           > Task :flutter:cleanPackageDebugAssets
           > Task :geolocator:compileDebugAidl NO-SOURCE
           > Task :google_maps_flutter:compileDebugAidl NO-SOURCE
           > Task :flutter:compileDebugAidl NO-SOURCE
           > Task :flutter:mergeDebugShaders UP-TO-DATE
           > Task :flutter:compileDebugShaders UP-TO-DATE
           > Task :flutter:generateDebugAssets UP-TO-DATE
           > Task :flutter:packageDebugAssets
           > Task :flutter:copyFlutterAssetsDebug
           > Task :flutter:generateDebugResValues UP-TO-DATE
           > Task :flutter:generateDebugResources UP-TO-DATE
           > Task :flutter:packageDebugResources UP-TO-DATE
           > Task :flutter:parseDebugLibraryResources UP-TO-DATE
           > Task :flutter:processDebugManifest UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:generateDebugResValues UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:compileDebugRenderscript NO-SOURCE
           > Task :flutter_plugin_android_lifecycle:generateDebugResources UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:packageDebugResources UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:parseDebugLibraryResources UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:checkDebugManifest UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:processDebugManifest UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:generateDebugRFile UP-TO-DATE
           > Task :geolocator:generateDebugResValues UP-TO-DATE
           > Task :geolocator:compileDebugRenderscript NO-SOURCE
           > Task :geolocator:generateDebugResources UP-TO-DATE
           > Task :geolocator:packageDebugResources UP-TO-DATE
           > Task :geolocator:parseDebugLibraryResources UP-TO-DATE
           > Task :geolocator:checkDebugManifest UP-TO-DATE
           > Task :geolocator:processDebugManifest UP-TO-DATE
           > Task :geolocator:generateDebugRFile UP-TO-DATE
           > Task :google_maps_flutter:generateDebugResValues UP-TO-DATE
           > Task :google_maps_flutter:compileDebugRenderscript NO-SOURCE
           > Task :google_maps_flutter:generateDebugResources UP-TO-DATE
           > Task :google_maps_flutter:packageDebugResources UP-TO-DATE
           > Task :google_maps_flutter:parseDebugLibraryResources UP-TO-DATE
           > Task :google_maps_flutter:checkDebugManifest UP-TO-DATE
           > Task :google_maps_flutter:processDebugManifest UP-TO-DATE
           > Task :google_maps_flutter:generateDebugRFile UP-TO-DATE
           > Task :permission_handler:generateDebugResValues UP-TO-DATE
           > Task :permission_handler:compileDebugRenderscript NO-SOURCE
           > Task :permission_handler:generateDebugResources UP-TO-DATE
           > Task :permission_handler:packageDebugResources UP-TO-DATE
           > Task :permission_handler:parseDebugLibraryResources UP-TO-DATE
           > Task :permission_handler:checkDebugManifest UP-TO-DATE
           > Task :permission_handler:processDebugManifest UP-TO-DATE
           > Task :permission_handler:generateDebugRFile UP-TO-DATE
           > Task :url_launcher:generateDebugResValues UP-TO-DATE
           > Task :url_launcher:compileDebugRenderscript NO-SOURCE
           > Task :url_launcher:generateDebugResources UP-TO-DATE
           > Task :url_launcher:packageDebugResources UP-TO-DATE
           > Task :url_launcher:parseDebugLibraryResources UP-TO-DATE
           > Task :url_launcher:checkDebugManifest UP-TO-DATE
           > Task :url_launcher:processDebugManifest UP-TO-DATE
           > Task :url_launcher:generateDebugRFile UP-TO-DATE
           > Task :flutter:generateDebugRFile UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:generateDebugBuildConfig UP-TO-DATE
           > Task :geolocator:generateDebugBuildConfig UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:javaPreCompileDebug UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:compileDebugJavaWithJavac UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:bundleLibCompileDebug UP-TO-DATE
           > Task :google_maps_flutter:generateDebugBuildConfig UP-TO-DATE
           > Task :geolocator:javaPreCompileDebug UP-TO-DATE
           > Task :geolocator:compileDebugJavaWithJavac UP-TO-DATE
           > Task :geolocator:bundleLibCompileDebug UP-TO-DATE
           > Task :google_maps_flutter:javaPreCompileDebug UP-TO-DATE
           > Task :google_maps_flutter:compileDebugJavaWithJavac UP-TO-DATE
           > Task :google_maps_flutter:bundleLibCompileDebug UP-TO-DATE
           > Task :permission_handler:generateDebugBuildConfig UP-TO-DATE
           > Task :permission_handler:javaPreCompileDebug UP-TO-DATE
           > Task :permission_handler:compileDebugJavaWithJavac UP-TO-DATE
           > Task :permission_handler:bundleLibCompileDebug UP-TO-DATE
           > Task :url_launcher:generateDebugBuildConfig UP-TO-DATE
           > Task :flutter:packageDebugRenderscript NO-SOURCE
           > Task :url_launcher:javaPreCompileDebug UP-TO-DATE
           > Task :url_launcher:compileDebugJavaWithJavac UP-TO-DATE
           > Task :url_launcher:bundleLibCompileDebug UP-TO-DATE
           > Task :flutter:javaPreCompileDebug UP-TO-DATE
           > Task :flutter:compileDebugJavaWithJavac UP-TO-DATE
           > Task :flutter:extractDebugAnnotations UP-TO-DATE
           > Task :flutter:mergeDebugGeneratedProguardFiles UP-TO-DATE
           > Task :flutter:mergeDebugConsumerProguardFiles UP-TO-DATE
           > Task :flutter:prepareLintJarForPublish UP-TO-DATE
           > Task :flutter:processDebugJavaRes NO-SOURCE
           > Task :flutter:mergeDebugJavaResource UP-TO-DATE
           > Task :flutter:transformClassesAndResourcesWithSyncLibJarsForDebug UP-TO-DATE
           > Task :flutter:mergeDebugJniLibFolders UP-TO-DATE
           > Task :flutter:mergeDebugNativeLibs UP-TO-DATE
           > Task :flutter:stripDebugDebugSymbols UP-TO-DATE
           > Task :flutter:transformNativeLibsWithSyncJniLibsForDebug UP-TO-DATE
           > Task :flutter:bundleDebugAar UP-TO-DATE
           > Task :flutter:uploadArchives
           > Task :flutter_plugin_android_lifecycle:extractDebugAnnotations UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:mergeDebugGeneratedProguardFiles UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:mergeDebugConsumerProguardFiles UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:mergeDebugShaders UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:compileDebugShaders UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:generateDebugAssets UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:packageDebugAssets UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:prepareLintJarForPublish UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:processDebugJavaRes NO-SOURCE
           > Task :flutter_plugin_android_lifecycle:mergeDebugJavaResource UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:transformClassesAndResourcesWithSyncLibJarsForDebug UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:mergeDebugJniLibFolders UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:mergeDebugNativeLibs UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:stripDebugDebugSymbols UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:transformNativeLibsWithSyncJniLibsForDebug UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:bundleDebugAar UP-TO-DATE
           > Task :flutter_plugin_android_lifecycle:uploadArchives
           > Task :geolocator:extractDebugAnnotations UP-TO-DATE
           > Task :geolocator:mergeDebugGeneratedProguardFiles UP-TO-DATE
           > Task :geolocator:mergeDebugConsumerProguardFiles UP-TO-DATE
           > Task :geolocator:mergeDebugShaders UP-TO-DATE
           > Task :geolocator:compileDebugShaders UP-TO-DATE
           > Task :geolocator:generateDebugAssets UP-TO-DATE
           > Task :geolocator:packageDebugAssets UP-TO-DATE
           > Task :geolocator:prepareLintJarForPublish UP-TO-DATE
           > Task :geolocator:processDebugJavaRes NO-SOURCE
           > Task :geolocator:mergeDebugJavaResource UP-TO-DATE
           > Task :geolocator:transformClassesAndResourcesWithSyncLibJarsForDebug UP-TO-DATE
           > Task :geolocator:mergeDebugJniLibFolders UP-TO-DATE
           > Task :geolocator:mergeDebugNativeLibs UP-TO-DATE
           > Task :geolocator:stripDebugDebugSymbols UP-TO-DATE
           > Task :geolocator:transformNativeLibsWithSyncJniLibsForDebug UP-TO-DATE
           > Task :geolocator:bundleDebugAar UP-TO-DATE
           > Task :geolocator:uploadArchives
           > Task :google_maps_flutter:extractDebugAnnotations UP-TO-DATE
           > Task :google_maps_flutter:mergeDebugGeneratedProguardFiles UP-TO-DATE
           > Task :google_maps_flutter:mergeDebugConsumerProguardFiles UP-TO-DATE
           > Task :google_maps_flutter:mergeDebugShaders UP-TO-DATE
           > Task :google_maps_flutter:compileDebugShaders UP-TO-DATE
           > Task :google_maps_flutter:generateDebugAssets UP-TO-DATE
           > Task :google_maps_flutter:packageDebugAssets UP-TO-DATE
           > Task :google_maps_flutter:prepareLintJarForPublish UP-TO-DATE
           > Task :google_maps_flutter:processDebugJavaRes NO-SOURCE
           > Task :google_maps_flutter:mergeDebugJavaResource UP-TO-DATE
           > Task :google_maps_flutter:transformClassesAndResourcesWithSyncLibJarsForDebug UP-TO-DATE
           > Task :google_maps_flutter:mergeDebugJniLibFolders UP-TO-DATE
           > Task :google_maps_flutter:mergeDebugNativeLibs UP-TO-DATE
           > Task :google_maps_flutter:stripDebugDebugSymbols UP-TO-DATE
           > Task :google_maps_flutter:transformNativeLibsWithSyncJniLibsForDebug UP-TO-DATE
           > Task :google_maps_flutter:bundleDebugAar UP-TO-DATE
           > Task :google_maps_flutter:uploadArchives
           > Task :permission_handler:extractDebugAnnotations UP-TO-DATE
           > Task :permission_handler:mergeDebugGeneratedProguardFiles UP-TO-DATE
           > Task :permission_handler:mergeDebugConsumerProguardFiles UP-TO-DATE
           > Task :permission_handler:mergeDebugShaders UP-TO-DATE
           > Task :permission_handler:compileDebugShaders UP-TO-DATE
           > Task :permission_handler:generateDebugAssets UP-TO-DATE
           > Task :permission_handler:packageDebugAssets UP-TO-DATE
           > Task :permission_handler:prepareLintJarForPublish UP-TO-DATE
           > Task :permission_handler:processDebugJavaRes NO-SOURCE
           > Task :permission_handler:mergeDebugJavaResource UP-TO-DATE
           > Task :permission_handler:transformClassesAndResourcesWithSyncLibJarsForDebug UP-TO-DATE
           > Task :permission_handler:mergeDebugJniLibFolders UP-TO-DATE
           > Task :permission_handler:mergeDebugNativeLibs UP-TO-DATE
           > Task :permission_handler:stripDebugDebugSymbols UP-TO-DATE
           > Task :permission_handler:transformNativeLibsWithSyncJniLibsForDebug UP-TO-DATE
           > Task :permission_handler:bundleDebugAar UP-TO-DATE
           > Task :permission_handler:uploadArchives
           > Task :url_launcher:extractDebugAnnotations UP-TO-DATE
           > Task :url_launcher:mergeDebugGeneratedProguardFiles UP-TO-DATE
           > Task :url_launcher:mergeDebugConsumerProguardFiles UP-TO-DATE
           > Task :url_launcher:mergeDebugShaders UP-TO-DATE
           > Task :url_launcher:compileDebugShaders UP-TO-DATE
           > Task :url_launcher:generateDebugAssets UP-TO-DATE
           > Task :url_launcher:packageDebugAssets UP-TO-DATE
           > Task :url_launcher:prepareLintJarForPublish UP-TO-DATE
           > Task :url_launcher:processDebugJavaRes NO-SOURCE
           > Task :url_launcher:mergeDebugJavaResource UP-TO-DATE
           > Task :url_launcher:transformClassesAndResourcesWithSyncLibJarsForDebug UP-TO-DATE
           > Task :url_launcher:mergeDebugJniLibFolders UP-TO-DATE
           > Task :url_launcher:mergeDebugNativeLibs UP-TO-DATE
           > Task :url_launcher:stripDebugDebugSymbols UP-TO-DATE
           > Task :url_launcher:transformNativeLibsWithSyncJniLibsForDebug UP-TO-DATE
           > Task :url_launcher:bundleDebugAar UP-TO-DATE
           > Task :url_launcher:uploadArchives
           203 actionable tasks: 12 executed, 191 up-to-date

[  +35 ms] Plugin project :url_launcher_macos not found. Please update settings.gradle.
           Plugin project :url_launcher_web not found. Please update settings.gradle.

           FAILURE: Build failed with an exception.

           * What went wrong:
           Execution failed for task ':firebase_performance:uploadArchives'.
           > Could not publish configuration 'archives'
              > Could not write to file '/Users/rafaelbarbosa/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_performance-0.4.1/android/build/poms/pom-default.xml'.

           * 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 5s

[  +11 ms] "flutter aar" took 6.203ms.
[  +14 ms] Gradle task assembleAarDebug failed with exit code 0.
[   +1 ms]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:14:3)
           #1      buildGradleAar (package:flutter_tools/src/android/gradle.dart:672:5)
           #2      _rootRunUnary (dart:async/zone.dart:1198:47)
           #3      _CustomZone.runUnary (dart:async/zone.dart:1100:19)
           #4      _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
           #5      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
           #6      Future._propagateToListeners (dart:async/future_impl.dart:725:32)
           #7      Future._completeWithValue (dart:async/future_impl.dart:529:5)
           #8      _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:40:15)
           #9      _completeOnAsyncReturn (dart:async-patch/async_patch.dart:311:13)
           #10     _DefaultProcessUtils.run (package:flutter_tools/src/base/process.dart)
           #11     _rootRunUnary (dart:async/zone.dart:1198:47)
           #12     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
           #13     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
           #14     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
           #15     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
           #16     Future._completeWithValue (dart:async/future_impl.dart:529:5)
           #17     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:40:15)
           #18     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:311:13)
           #19     _run (package:flutter_tools/src/base/error_handling_io.dart)
           #20     _rootRunUnary (dart:async/zone.dart:1198:47)
           #21     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
           #22     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
           #23     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
           #24     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
           #25     Future._completeWithValue (dart:async/future_impl.dart:529:5)
           #26     Future.wait.<anonymous closure> (dart:async/future.dart:414:23)
           #27     _rootRunUnary (dart:async/zone.dart:1198:47)
           #28     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
           #29     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
           #30     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
           #31     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
           #32     Future._completeWithValue (dart:async/future_impl.dart:529:5)
           #33     Future._asyncCompleteWithValue.<anonymous closure> (dart:async/future_impl.dart:567:7)
           #34     _rootRun (dart:async/zone.dart:1190:13)
           #35     _CustomZone.run (dart:async/zone.dart:1093:19)
           #36     _CustomZone.runGuarded (dart:async/zone.dart:997:7)
           #37     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:1037:23)
           #38     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
           #39     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
           #40     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
           #41     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:169:5)

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

This seems to point to a mistake in the build.gradle file. Can you check if there is anything missing or any typos?

I checked the build.gradle of the project and everything appears ok.
I even did another test. I created a new flutter_module and added only the dependencies:
  firebase_performance: 0.4.1
  firebase_core: 0.5.1

And by running the command flutter build aar displays the same error.

I have experienced the same problems as @RafaelBarbosatec, but using

firebase_auth: ^0.18.2

and separately with

cloud_firestore: ^0.14.2

I can reproduce the problem by creating a new module with

flutter create -t module --org com.example aar_example

and then running

flutter build aar

which failed with

Execution failed for task ':firebase_auth:uploadArchives'.
Could not publish configuration 'archives'
Could not write to file '/home/mark.melling/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.18.2/android/build/poms/pom-default.xml'.

@markusaksli-nc  Any other ideas of what it might be? Apparently it is not something isolated to firebase-performance.

Reproducible on the latest master 1.24.0-8.0.pre.149.

flutter doctor -v
[√] Flutter (Channel master, 1.24.0-8.0.pre.149, on Microsoft Windows [Version 10.0.19041.572], locale et-EE)
    • Flutter version 1.24.0-8.0.pre.149 at C:\Development\flutter_master
    • Framework revision 8e7748e74c (7 hours ago), 2020-11-08 20:32:04 -0800
    • Engine revision 0f7cdca65f
    • Dart version 2.12.0 (build 2.12.0-27.0.dev)

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at C:\Users\marku\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: C:\Users\marku\AppData\Local\JetBrains\Toolbox\apps\AndroidStudio\ch-0\201.6858069\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.7.7)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.7.30621.155
    • Windows 10 SDK version 10.0.18362.0

[√] Android Studio (version 4.1.0)
    • Android Studio at C:\Users\marku\AppData\Local\JetBrains\Toolbox\apps\AndroidStudio\ch-0\201.6858069
    • 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 1.8.0_242-release-1644-b01)

[√] IntelliJ IDEA Ultimate Edition (version 2020.2)
    • IntelliJ at C:\Users\marku\AppData\Local\JetBrains\Toolbox\apps\IDEA-U\ch-0\202.7660.26
    • 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

[√] Connected device (6 available)
    • SM G950F (mobile)           • ce12171c51cc001c03 • android-arm64  • Android 9 (API 28)
    • sdk gphone x86 arm (mobile) • emulator-5554      • android-x86    • Android 11 (API 30) (emulator)
    • Windows (desktop)           • windows            • windows-x64    • Microsoft Windows [Version 10.0.19041.572]
    • Web Server (web)            • web-server         • web-javascript • Flutter Tools
    • Chrome (web)                • chrome             • web-javascript • Google Chrome 86.0.4240.183
    • Edge (web)                  • edge               • web-javascript • Microsoft Edge 86.0.622.61

• No issues found!

Was able to reproduce this with most of the latest firebase plugins except from just firebase_core: ^0.5.2 on its own.

Is there any known workaround to this problem?

I had this problem two months ago， hope for a quick resolution

I had this problem two months ago， hope for a quick resolution

Any solution for that problem?

Hi guys, has anyone solved this problem?

This probelm is becoming increasingly problematic. My solution to date is to stay on an old version of the firebase plugins, but I can't do do this forever.
Given that basically you can't build an aar with the latest version of the firebase plugins I'm surprised there aren't more people like me that are affected by this issue.
Or may be there is a work around that I just don't know about.
Any help or suggestions much appreciated.

"Solved" with a workaround. Import the android directory as android project with Android studio. From there you can generate your aar (eg. by executing an assembleRelease/Debug). Hope it helps

Thanks @danimazzocchi, that was useful, taking the approach that I think you were suggesting I wasn't able to generated the POM file as well as the aar.
I decided to dig a bit deeper into what was causing the issue.
It turns out that the actual error is
Gradle fails to create POM with “The configuration to scope mapping is not unique.”
Which occurs in:
packages/flutter_tools/gradle/aar_init_script.gradle
Generally I'm happy not to know too much about gradle, as long as it works, life's too short! but it would have actually been useful in this case.
Anyway I hacked the script just so that scope mappings were different, this did result in me being able to build the aar along with the POM and this has now been successfully included in the app.

@markmelling how did you hack the script...?? enlighten us... I am also looking for a solution.

@Harshdeep4295  Bear in mind that I don't know what I'm doing, at least with gradle, all I did was make the priority different.
So, in packages/flutter_tools/gradle/aar_init_script.gradle, at the bottom of the function below rather than each mapping having the same priority (300) I added 100 for each. I hope that helps
void overrideDefaultPublishConfig(Project project, variant) {     String variantName = variant.name.capitalize()     Task bundle = project.tasks.findByName("bundle${variantName}Aar") // gradle:3.2.0     if (bundle == null) {         bundle = project.tasks.findByName("bundle${variantName}") // gradle:3.1.0     }     if (bundle == null) {         throw new GradleException("Can't generate AAR for variant ${variantName}.");     }     // Clear the current archive artifacts since the artifacts are based onandroid.defaultPublishConfig`.
project.configurations["archives"].artifacts.clear()
// Add the artifact that will be published.
project.artifacts.add("archives", bundle)
def scopeMappings = project.uploadArchives.repositories.mavenDeployer.pom.scopeMappings
// Clear the scope mappings added by AGP since they are based on the current `android.defaultPublishConfig`.
scopeMappings.mappings.clear()
// Add the new mappings.
int priority = 300
for (Configuration configuration : flattenConfiguration(variant.runtimeConfiguration)) {
    //scopeMappings.addMapping(/* priority = */ 300, configuration, "compile")
    scopeMappings.addMapping(/* priority = */ priority, configuration, "compile")
    priority = priority + 100
}

}
`

Hi @markmelling, It is working, but it hacks right, so we need to fix this root cause. Hope to get something on this. Also, can you give reference to how Gradle actually works so that I can dig a bit about fixing this one?

Hi @Harshdeep4295, I'm glad it worked, but as you say it is a true hack. Sorry, I really can't help on the gradle front, I've already wasted too much of my life delving into technologies that I rarely use.

I have the same issue with these plugins installed:
firebase:     dependency: transitive     description:       name: firebase       url: "https://pub.dartlang.org"     source: hosted     version: "9.0.1"   firebase_analytics:     dependency: transitive     description:       name: firebase_analytics       url: "https://pub.dartlang.org"     source: hosted     version: "8.0.2"   firebase_analytics_platform_interface:     dependency: transitive     description:       name: firebase_analytics_platform_interface       url: "https://pub.dartlang.org"     source: hosted     version: "2.0.0"   firebase_analytics_web:     dependency: transitive     description:       name: firebase_analytics_web       url: "https://pub.dartlang.org"     source: hosted     version: "0.3.0"
This is the error i got:
`FAILURE: Build completed with 2 failures.
       1: Task failed with an exception.
       -----------
       * What went wrong:
       Execution failed for task ':firebase_analytics:uploadArchives'.
       > Could not publish configuration 'archives'
          > Could not write to file

'/Users/daanporon/.pub-cache/hosted/pub.dartlang.org/firebase_analytics-8.0.2/android/build/poms/pom-default.xml'.
       * 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.
==============================================================================
       2: Task failed with an exception.
       -----------
       * What went wrong:
       Execution failed for task ':firebase_messaging:uploadArchives'.
       > Could not publish configuration 'archives'
          > Could not write to file

'/Users/daanporon/.pub-cache/hosted/pub.dartlang.org/firebase_messaging-9.1.3/android/build/poms/pom-default.xml'.
       * 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 12s`

I tried the fix from @danimazzocchi without any luck, afterwards i tried the hack from @markmelling and this one did work ...

@markmelling  - Thank you! This hack worked for me as well. Anyone know if this will be addressed in the next release?

Hey @markmelling, Is this hack still necessary with the latest plugins/stable version of gradle?

I can still see the issue. Build is getting failed with below error

.
Flutter doc:
`Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 2.10.1, on Microsoft Windows [Version 10.0.19043.1526], locale en-US)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.11.3)
[√] Android Studio (version 2020.3)
[√] VS Code (version 1.64.2)
[√] Connected device (4 available)
[√] HTTP Host Availability
• No issues found!`
Dependency used:
`dependencies:
flutter:
sdk: flutter
shared_preferences: ^2.0.8
objectbox: ^1.2.0
objectbox_flutter_libs: ^1.2.0
path_provider: ^2.0.5
mqtt_client: ^9.6.1
provider: ^6.0.1
logger: ^1.1.0
retrofit: ^2.2.0
built_value: ^8.1.2
dio: ^4.0.1
injectable: ^1.5.0
get_it: ^7.2.0
json_annotation: ^4.3.0
firebase_messaging: ^10.0.9
firebase_analytics: ^8.3.4
firebase_core: ^1.8.0
f_logs: ^2.0.0
connectivity: ^3.0.6
mime_type: ^1.0.0
file: ^6.1.2
http: ^0.13.4
http_interceptor: ^1.0.1
flutter_video_info: ^1.2.0
audioplayers: ^0.20.1
crypto: ^3.0.1`

@chandragupt1201 were you able to successfully integrate firebase_analytics?


depth_sensor camera matrix

I am looking to find the camera matrix for the depth_sensor using in pointnav_habitat_test.yaml to generate a point cloud from the depth image. I have seen #656 which points to the example for camera transforms which I think is trying to generate a camera matrix from just the hfov, however when using this matrix I get a nonsensical pointcloud. Using the primesenseDefault camera parameters I can get close but the point is still not correct. Following the linked tutorial I can get my depth sensor width, height and hfov, using commands like agent_config.sim_sensors.depth_sensor.hfov,  however I cant output focal lengths or principle points.
How do I get the depth_sensor camera matrix?

I have resolved this issue by manually computing the points per the tutorial linked above rather than an api call from open3d.


replace pkg/units with docker/go-units

see: https://github.com/docker/docker/pull/18682

To update to docker/go-units the GLOCKFILE needs to also be updated.


question about the DBNBeatTrackingProcessor、DBNDownBeatTrackingProcessor

In the training process, DBNBeatTrackingProcessor、DBNDownBeatTrackingProcessor are not used, the loss is calculated by the Demixed_DilatedTransformerModel and ground truth. but in the inference process, after the Demixed_DilatedTransformerModel, the actvition is passed to DBNBeatTrackingProcessor and DBNDownBeatTrackingProcessor.
I think there is a mismatch between training and inference. but seems all the beat prediction open source project use DBNBeatTrackingProcessor and DBNDownBeatTrackingProcessor after the activation? Have you tried simple use of the activation as the prediction mark?

In the training process, DBNBeatTrackingProcessor、DBNDownBeatTrackingProcessor are not used, the loss is calculated by the Demixed_DilatedTransformerModel and ground truth. but in the inference process, after the Demixed_DilatedTransformerModel, the actvition is passed to DBNBeatTrackingProcessor and DBNDownBeatTrackingProcessor. I think there is a mismatch between training and inference. but seems all the beat prediction open source project use DBNBeatTrackingProcessor and DBNDownBeatTrackingProcessor after the activation? Have you tried simple use of the activation as the prediction mark?

Usually, when training a beat-tracking model, the training target is to predict beat/downbeat activation from an input spectrogram. The activation can be regarded as a time sequence of likelihood (with continuous values in [0, 1]), representing the model's certainty about how likely each timestep is a beat/downbeat.
Based on the activation predicted by our model, at inference time, we additionally need a post-processing step to make a binary decision (discrete 0 and 1) at each timestep. Previous post-processing methods include thresholding (e.g., each timestep whose activation > 0.6 is a beat/downbeat), and peak-picking (i.e., each timestep whose activation is higher than both neighbors is a beat/downbeat). Unfortunately, however, the activation predicted by our model tends to be very noisy so neither thresholding nor peak-picking yields satisfactory performance. That is why we introduce DBN(Down)BeatTrackingProcessor here as the post-processor. It makes a global decision to determine discrete beat/downbeat and non-beat events based on dynamic programming. The DBNBeatTrackingProcessor and DBNDownBeatTrackingProcessor are not included in the training target because they are not differentiable (no gradient).

yes. I find most of the beat predict work use DBN as the postprocess.
I will close the issue.

another question.
the spleeter will split the music into vocals、accompaniment, piano、vocals、bass、drums、other according to the stems.
have you tried exclude vocals for the prediction.
because the vocals are mainly singing. the singing beat prediction and music prediction seems different in this paper: https://arxiv.org/abs/2208.14578.


Frames and Events only

Hello,
Thank you for this great package! I was playing around with my DAVIS camera and this package and I was having trouble trying to get frames and accumulated_events running in the gui. Only the dvs_renderer seems to be working. Any suggestions?
Thanks
Harsh

Did you find a solution for this?


Cherry pick Adding ability to parse float from number with leading decimal to active_release

Automatic cherry-pick of ece8a7c

Originally appeared in https://github.com/apache/arrow-rs/pull/831: Adding ability to parse float from number with leading decimal

Codecov Report

Merging #962 (7883476) into active_release (54023c8) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@                Coverage Diff                 @@
##           active_release     #962      +/-   ##
==================================================
+ Coverage           82.38%   82.39%   +0.01%
==================================================
  Files                 168      168
  Lines               48668    48670       +2
==================================================
+ Hits                40097    40104       +7
+ Misses               8571     8566       -5

Impacted Files
Coverage Δ

arrow/src/csv/reader.rs
90.02% <100.00%> (+0.02%)
:arrow_up:

arrow/src/array/transform/mod.rs
85.33% <0.00%> (+0.13%)
:arrow_up:

arrow/src/datatypes/datatype.rs
66.38% <0.00%> (+0.42%)
:arrow_up:

parquet_derive/src/parquet_field.rs
66.43% <0.00%> (+0.68%)
:arrow_up:

Continue to review full report at Codecov.

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


getDepsFromBundle does not work when using esbuild-node-externals

getDepsFromBundle assumes that all dependencies are present in the minified bundle. when using esbuild-node-externals, this is not the case as the nested dependencies are resolved from each dependency inside node_modules in separate require statements. As a result the list of dependencies passed to flatDep contains is incomplete and several libraries are not included in the .zip.
I believe this is why serverless-webpack creates a temporary project with the top-level dependencies in a package.json that it creates and runs npm / yarn install on that to get the full complete node_modules needed to support the bundle.

Did this PR resolve your issue? https://github.com/floydspace/serverless-esbuild/issues/103

Should be resolved by https://github.com/floydspace/serverless-esbuild/pull/267. Let me know if this isn't the case :)


Split JavaScript bundle into thrift and proto versions (BREAKING CHANGE)

This restores the -thrift.min.js version to very close to the size that
it was before proto was introduced.
Users will need to modify existing references to lightstep-tracer.min.js
to either lightstep-tracer-thrift.min.js or lightstep-tracer-proto.min.js.
If you would like to continue using Thrift you should also add the key/value
transport=thrift as an argument to your lightstep.Tracer initialization.
resolves #113

@lawnsea I would love to get your feedback on this PR. It addresses the size of the thrift javascript, restoring it to the original 70ish KB.

Because this is a breaking change, this will likely be the first time many folks become aware of the proto option.  As is the proto option actually does not work because by default proto uint64s are treated as javascript Numbers, but Numbers aren't big enough to handle large uint64s.  We probably want to updated the proto and regenerate as indicated in the solution to this issue: https://github.com/protocolbuffers/protobuf/issues/3666

It would be great if this worked not through global variables but through different entry points so self-bundling is possible (see also #138)

I.e. thrift and proto libraries should be removed automatically by tree shaking depending on what files are imported, not depending on what global variables are set.

@frenchfrywpepper I don't have any significant feedback on the PR other than 👏 that the bundle size is back to normal.


MSAL-Browser: Can't logout user. Logout function is not working properly.

Library

[ ]<EMAIL_ADDRESS>or<EMAIL_ADDRESS>[x]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
Description
Can't logout user by using logout function. The user will be re-authenticated automatically and there is no chance to change the user account or select different user account. I have to clear the browsing data - "Cookies and other site data" then i can change the user account.
I used the MSAL 2.0 typescript sample code
MSAL Configuration
// configuration from MSAL 2.0 typescript sample code
const MSAL_CONFIG: Configuration = {
    auth: {
        clientId: "client-id"
    },
    cache: {
        cacheLocation: "sessionStorage", // This configures where your cache will be stored
        storeAuthStateInCookie: false, // Set this to "true" if you are having issues on IE11 or Edge
    },
    system: {
        loggerOptions: {
            loggerCallback: (level, message, containsPii) => {
                if (containsPii) {
                    return;
                }
                switch (level) {
                    case LogLevel.Error:
                        console.error(message);
                        return;
                    case LogLevel.Info:
                        console.info(message);
                        return;
                    case LogLevel.Verbose:
                        console.debug(message);
                        return;
                    case LogLevel.Warning:
                        console.warn(message);
                        return;
                }
            }
        }
    }
};

Reproduction steps

User will see the signIn button at first time.

Click signIn button will need user to provide login info at first time.(use redirect login)

Login success

Click logout button, user will be redirected to website again and see the signIn button

Click signIn button, user will login immediately without provide any login info, and user can't select different account. It supposed to redirect user to the page like step2, and ask user to provide the credential info.

Have to clear the browsing data - cookie and  other site data then i can see the login page like step2

Expected behavior
The user should be logout and need to provide login information when the use visit the website again.
Browsers/Environment

[x] Chrome
[ ] Firefox
[x] Edge
[ ] Safari
[ ] IE
[ ] Other (Please add browser name here)

@pedoe You can prompt the user to login by passing prompt: "login" when invoking the login APIs:
msalInstance.loginPopup({
  prompt: "login" // "select_account" will force account selection
})

@jasonnutter But we should not force account selection or user login every time if user didn't logout from our portal right? Users should login immediately if they didn't click logout before. Use prompt: "login" will ask user to provide login info every time. Is there any way to clear all the user data when invoking logout API? Thanks!

@pedoe After clicking the logout button you should be redirected to the AAD signout page where you are given the option to select an account to sign out of. It's not clear from your description above if you went through this account selection process. Can you confirm?

I have the same problem of not being able to logout but I am using<EMAIL_ADDRESS>Also, it seems that the problem presents itself only for some users and not for others...

And after asking for logout I am not redirected to the aad signout page where you are given the option to select an account to sign out of.

@lemenhir This is why logout isn't working properly for you. Selecting the account on the aad signout page is how the service knows to clear the user's session data. Are you using AAD or B2C?

@lemenhir This is why logout isn't working properly for you. Selecting the account on the aad signout page is how the service knows to clear the user's session data. Are you using AAD or B2C?

I am using B2C

@lemenhir This is expected behavior when using B2C, you can read more about this here and in our FAQ

I am using AAD and still have the same issue. The logout request gets canceled when called by the msal logout function and i get redirected to localhost:44326/# , oddly when i copy the same url that is canceled and call it manualy by pasting it in the url bar, it works as expected.
https://login.microsoftonline.com/{authorityString}/oauth2/v2.0/logout?post_logout_redirect_uri=https%3A%2F%2Flocalhost%3A44326%2Fhome%2Fdashboard%2Fns&client-request-id=0366dc43-57e4-4ba6-8377-cd6f8d53ba3c
Let me know if need to add some additional information. I've used the angular10 sample as guideline.
"@azure/msal-browser": "^2.7.0",
"@angular/core": "~8.2.14",
"msal": "^1.4.4",

@iZagi Is there any error in the console or on the network request that might provide a clue as to why it gets cancelled? Are you perhaps trying to initiate logout from an iframe?
Also are you using<EMAIL_ADDRESS>or<EMAIL_ADDRESS>You mentioned both...

@tnorling we've migrated from msal 1.4.4 to msal-browser 2.7.0, i did recheck, we are using only msal-browser now, during a bit of research i've noticed we didnt use hashlocation strategy, after setting it to true, the logout started to work as intented. Is there a way to avoid using "useHash:true" in the router or its mandatory for the framework to work?

@iZagi "useHash:true" is not required for msal-angular to work. Can you clarify what is not working or not happening? Is it not redirecting to the logout url? Can you also try setting the post_logout_redirect_uri to your homepage?


DNS Server Configuration for Databrick Cluster VNet

Can you please point out if you have documented DNS server configuration for DataBricks Cluster VNet?
I encountered exactly error as posted in
https://forums.databricks.com/questions/29650/cluster-terminated-reason-network-configuration-fa.html
Once I switch from my customized DNS sever to Azure provided DNS server for the VNet, the cluster is successfully created.
Can you please clarify this is by design? we have to use Azure provided DNS server?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2eea9046-9156-2096-d59b-afbe816c7390
Version Independent ID: 7e667e9f-08f9-94fa-add5-346db61837ca
Content: What is Azure Databricks?
Content Source: articles/azure-databricks/what-is-azure-databricks.md
Service: azure-databricks
GitHub Login: @mamccrea
Microsoft Alias: mamccrea

@RonnieQuan This has been already documented here: Azure Databricks - Configure custom DNS .
If you want to use your own DNS for name resolution, you can do that with Azure Databricks workspaces deployed in your own virtual network. See the following Microsoft documents for more information about how to configure custom DNS for an Azure virtual network:

Name resolution that uses your own DNS server
Specify DNS servers

Hope this helps.

Thank you for the information, we created vnet subnets for our Databricks, and it's not working.
Let me review the document you shared to see if any findings.

@RonnieQuan  We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


[OP] Move sample op to operator_util, support source function

This PR enables a symbolic sampling operator under mx.sym.normal and mx.sym.uniform under unified operator API. This makes plugin sampler in the graph easier.
Changes to do in language APiS
The subsequent package should update the functions as in the python to change NDArray._random_uniform to NDArray._sample_uniform.
The previous registered _random_uniform is still there, but will be removed update the changes in R, julia and scala package follows up. Please reply to this issue after these packages are updates.
@pluskid @thirdwing @javelinjs

I will update R package after merging #2491

Will update scala soon.

Just double check.
_random_uniform has not been exported to the R side.

it is _sample_uniform, check the Rcpp export rule, could get renamed to internel.sample_uniform

It should be updated in #2520

Can u extend the support to double type or DType(need mshadow support)? Or give some hint on doing so.

the random currently do not yet support double type. Requires the random resources to be able to provide double number generators, which currently only provide a float one

You are calling the rand functions in mshadow/mshadow/random.h in sample_op-inh-h which does have double type support.


{{reports}}$(2)编号

in your file  MultipleRowTableRenderPolicyTest, I saw this
{{reports}}$(2) in template document, What does it mean?

Yes, I will enrich the relevant documentation in the next release.


Langrauge / Time Formats not changing from US

Checklist
Please make sure you have performed the following steps before opening a new bug ticket, change [ ] to [x] to mark it as done

[X] I have read and tried the steps outlined in the Troubleshooting Guide
[X] I have searched through existing issues.

Description

Using docker and when setting the following:
-e LC_ALL=en_GB.UTF-8
-e LANG=en_GB.UTF-8
This does not work, it keeps as en_US I have also tried the example on this link and still stays as en_US.
https://docs.lubelogger.com/International Locale
I have delete all files and rebuilt the container multiple times and tried other langurages but does not work.
Please note other docker containers run on this server and works perfect.
Platform

[X] Docker Image
[ ] Windows Standalone Executable

Browser Console Errors(F12)

Nothing to show on this
App/Container Console Error

Screenshots(optional)

en_US is just the default language, translations are not affected by the environment variables, those affect date and currency formats.
For translations, see https://docs.lubelogger.com/Translations

Afternoon,
Thanks for confirm that the en_US will not change directly.
After some more resets etc I have got the formatiing now showing correctly

Looking forward to moving my spreadsheet over to this system instead. CLosing case


Mark invalid completion bonuses

Live example:
Venom Sac relic records\item\animalrelics\01_multacts_venomsac.dbr
relics-CB-text.zip
Possible completion bonuses are defined in records\item\lootmagicalaffixes\animalrelics\01_multacts_venomsac.dbr:
Class,LootRandomizerTable,
randomizerName11,Records\Item\LootMagicalAffixes\AnimalRelics\Bonuses\Offensive_%Poison_01.dbr,
randomizerName3,Records\Item\LootMagicalAffixes\Suffix\Default\Offensive_Stun_01.dbr,
randomizerName5,Records\Item\LootMagicalAffixes\Suffix\Default\Offensive_ReducedProtection_02.dbr,
randomizerName7,Records\Item\LootMagicalAffixes\Prefix\Default\Offensive_DamagePoison_01.dbr,
randomizerName9,Records\Item\LootMagicalAffixes\Prefix\Default\Offensive_ReducedAttackSpeed_01.dbr,
randomizerWeight11,900,
randomizerWeight3,300,
randomizerWeight5,300,
randomizerWeight7,900,
randomizerWeight9,300,

But first entry Records\Item\LootMagicalAffixes\AnimalRelics\Bonuses\Offensive_%Poison_01.dbr does not exist, which means CB will be empty if it procs.
Proposal: test whether links exist and are valid, and mark invalid ones

I've marked this as an possible enhancement but it is low priority: TQVaultAE should (ideally) be able to trust the data from the game files.

I know that proposed feature is kinda out of Vault mainline, so marked it as "Proposal" beforehand.
Game database is ACTUALLY full of mistakes and we have to live with it. It is not about trust, it is about creating a tool to detect such mistakes. The quicker ones will be detected and reported to game devs, the quicker they will be fixed. Also do not forget about mods (Vault supports such), where database is created by users, and thus can carry even more mistakes.

Fair point.
I think having a diagnostic tool that could produce a bug report for the dev could be a first step. Displaying invalid entries could come after that, assuming they don't fix their database in a timely manner.

It's done with PR #462.
It shows on the following menu.

Prefix/Suffix
Relic completion bonus
Socketed relic completion bonus
Artifact completion bonus

Unknown/Orphan record

Record without translation tag

And if you want the full list incomplete records, activate this settings in TQVaultAE.exe.config

DebugEnabled = True
LootTableDebugEnabled = True

You wil see something like that in the log file of the tool.


Plugin Requires Brackets To Restart If Any Errors

Seems like if there is an Authentication Error, directory error, or timeout, the plugin requires brackets to be closed and reopened. A refresh down not work.

+1

+1

+1

fixed.


[Android] Fix scrolling behaviour in multiline Input.Text

Related Issue
Fixes #3693
Description
This changes fix the current behaviour of multiline Input.Text elements as it doesn't allow scrolling when the element is inside a tall card (tall enough so that the scrollbar indicators show up)
How Verified
This fix was tested manually and this is the result showing the new behavior

Microsoft Reviewers: Open in CodeFlow

@almedina-ms can we add this sample card to our list of samples ? @nesalang FYI. Do our existing Android Visualizer tools allow for testing of this card or are there app changes on Android that need to be made as well? Also can we test this out in this month's bugbash for all platforms (ios,Android, web, uwp etc) ?


Conda pkg dependency  on geos 3.3.x

Could the conda package be upgrade to depend on geos 3.4.x? I find basemap to be the last conda package to depend on the older 3.3.x versions and it creates some problems with gdal compiles, that usually want 3.4 these days.
thanks!

I don't control the conda package, and I agree, it is extremely annoying. I
don't know who to report this too, though.
On Tue, Apr 19, 2016 at 4:46 PM, K.-Michael Aye<EMAIL_ADDRESS>wrote:

Could the conda package be upgrade to depend on geos 3.4.x? I find basemap
to be the last conda package to depend on the older 3.3.x versions and it
creates some problems with gdal compiles, that usually want 3.4 these days.
thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/matplotlib/basemap/issues/286

Try the basemap from the conda-forge channel:
$ conda install -c conda-forge basemap
-Filipe
On Tue, Apr 19, 2016 at 5:51 PM, Benjamin Root<EMAIL_ADDRESS>wrote:

I don't control the conda package, and I agree, it is extremely annoying. I
don't know who to report this too, though.
On Tue, Apr 19, 2016 at 4:46 PM, K.-Michael Aye<EMAIL_ADDRESS>wrote:

Could the conda package be upgrade to depend on geos 3.4.x? I find
basemap
to be the last conda package to depend on the older 3.3.x versions and it
creates some problems with gdal compiles, that usually want 3.4 these
days.
thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/matplotlib/basemap/issues/286

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/matplotlib/basemap/issues/286#issuecomment-212122171

@kalefranz maybe knows. Yeah, will try the conda-forge one, but it says '1.08beta'?

nope, the conda-forge channel does not work with nomkl libraries. :(

conda create -n TEST -c conda-forge python=2.7 basemap nomkl works for me.
It is 1.0.8.dev0 because we needed https://github.com/matplotlib/basemap/pull/279

BTW @WeatherGod a new release would be nice :wink:

On my stable 3.5 env it insists on nomkl:
(stable)└─❱❱❱ conda install -c conda-forge basemap                                     +4823 14:56 ❰─┘
Fetching package metadata: ........
Solving package specifications: .........

Package plan for installation in environment /Users/klay6683/miniconda3/envs/stable:

The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    geos-3.4.2                 |                0         2.5 MB
    mkl-11.3.1                 |                0        99.1 MB
    numpy-1.10.4               |           py35_0         2.6 MB
    pyshp-1.2.3                |           py35_0          29 KB
    numexpr-2.5.2              |      np110py35_0         111 KB
    pyproj-<IP_ADDRESS>             |           py35_0         3.0 MB
    scipy-0.17.0               |      np110py35_0        11.8 MB
    scikit-learn-0.17.1        |      np110py35_0         3.6 MB
    basemap-1.0.8.dev0         |      np110py35_1        15.6 MB
    ------------------------------------------------------------
                                           Total:       138.3 MB

The following NEW packages will be INSTALLED:

    basemap:      1.0.8.dev0-np110py35_1
    mkl:          11.3.1-0
    pyproj:       <IP_ADDRESS>-py35_0
    pyshp:        1.2.3-py35_0

The following packages will be UPDATED:

    geos:         3.3.3-0                  --> 3.4.2-0
    numexpr:      2.5.2-np110py35_nomkl_0  [nomkl] --> 2.5.2-np110py35_0
    numpy:        1.10.4-py35_nomkl_0      [nomkl] --> 1.10.4-py35_0
    scikit-learn: 0.17.1-np110py35_nomkl_0 [nomkl] --> 0.17.1-np110py35_0
    scipy:        0.17.0-np110py35_nomkl_0 [nomkl] --> 0.17.0-np110py35_0

Proceed ([y]/n)? n

Interesting, when I add nomkl it works suddenly? Why is that so? I already have nomkl installed?

@ocefpaf, yeah, I think I should try a bugfix release. I kept seeing if I can find time for bigger changesets, but I keep volunteering for too many other things.
Anyone know a good reference for how to do a release to PyPi? And how to update readthedocs?

HI Benjamin:
I am not sure if this is the best way to release on PyPi, but here is the
way I do I for one of my projects (using twine).
https://github.com/guziy/pylibrmn/blob/master/upload_to_pypi.sh
Cheers
2016-04-19 21:21 GMT-04:00 Benjamin Root<EMAIL_ADDRESS>
@ocefpaf https://github.com/ocefpaf, yeah, I think I should try a
bugfix release. I kept seeing if I can find time for bigger changesets, but
I keep volunteering for too many other things.
Anyone know a good reference for how to do a release to PyPi? And how to
update readthedocs?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/matplotlib/basemap/issues/286#issuecomment-212195538

--
Sasha

Why is that so?

I had a suspicion that this had been improved in v4 of conda, which version are you using?
Anyway - sounds like you are able to use conda-forge's basemap. @WeatherGod - if you or anybody else who is maintaining Basemap would like access to that, please feel free to add a PR to https://github.com/conda-forge/basemap-feedstock/blob/master/recipe/meta.yaml#L37 adding your github handles. The conda-forge automation will add you to the team with write access, and updating the binaries on conda-forge is just a PR away :tada:
To raise issues with anaconda.org defaults packages, the tracker can be found at https://github.com/ContinuumIO/anaconda-issues.

@WeatherGod I am not sure if twine uploads the source distribution of only the wheels. I usually do this for a release:

create a branch and tag for the release on GitHub;
check the tag locally ;
python setup.py sdist --formats=gztar upload

(No user/pass b/c I have a .pypirc)

As I recall the issue with pypi was the package size of basemap? See #198
I don't know how far the new pypi infrastructure has come.
A new release would be welcome for Matplotlib too which is now depending on Basemap for the automatic docs build (the docs have a basemap example) 1.0.7 has issues with finding geos on Travis it would seem.

I agree with @jenshnielsen! It would be nice to split basemap into a data basemap and basemap-data packages. (We are doing that in conda-forge BTW, when you install basemap you won't get the intermediate, high, and fine resolutions. You need to install basemap-data to get that.)

@pelson I'm using conda 4.0.5, the most recent version.

@ocefpaf do you mean basemap-data-hires ?

@michaelaye

@kalefranz maybe knows. Yeah, will try the conda-forge one, but it says '1.08beta'?

Best place to get help for individual packages in the default conda repo is at https://github.com/ContinuumIO/anaconda-issues/.  File an issue there, then @csoja can help coordinate with @ilanschnell and/or other package maintainers.

Thank you, everybody for your inputs. I hope to start getting things to a point where I can put up a release candidate either this weekend or next weekend. If anybody wants to contribute a patch that makes it possible to split out basemap-data-hires, please contribute it. Any other downstream patches would be greatly appreciated, too.

I agree with @jenshnielsen! It would be nice to split basemap into a data basemap and basemap-data packages. (We are doing that in conda-forge BTW, when you install basemap you won't get the intermediate, high, and fine resolutions. You need to install basemap-data to get that.)

@ocefpaf I know I am coming six years later, but I am happy to notify that basemap is now (1.3.x) effectively split into three parts similarly to what is done in Anaconda: basemap, basemap-data and basemap-data-hires. The only difference is that the intermediate-resolution files are located in basemap-data instead of basemap-data-hires (to avoid the PyPI package size limit for basemap-data-hires). Hopefully this split in the main basemap repository will make life easier in the corresponding conda recipes.

Thanks for letting me know @molinav. I'm not actively maintaining the basemap-feedstock anymore but I can help out when there is a new release.

I think it is safe to close this issue. Since taking over the maintenance of basemap a couple of years ago:

The package has been split into basemap, basemap-data and basemap-data-hires and precompiled wheels for Windows and GNU/Linux are uploaded to PyPI regularly since 1.3.0.
For the upcoming 1.4.0 (in the next couple of days), I will also upload the precompiled wheels for MacOS manually to PyPI.
The basemap-feedstock for conda-forge is back to life, with packages for the major platforms (Windows, GNU/Linux, MacOS) on x64 plus MacOS on arm64, and updating the dependencies regularly (including GEOS, which currently points to 3.12.1).

To sum up, the most usual cases are completely covered both on PyPI and conda-forge, and users do not need to build basemap from source anymore.


Resource template add "createOrGet" action

Summary
add "createOrGet" action in resource template
Use Cases
I create resource template with retryStrategy, and delete resource pod, then then workflow fail for AlreadyExists

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Do you mean the executor pod is deleted but the created resource is still running? In this case, the executor could perhaps try to automatically get the already created resource instead of trying to re-create when retrying and then encounter AlreadyExists error. But there should at least be some option in case some users may still want to treat this as failure when the executor pod fails. Do you have any proposed way of doing this?

Do you mean the executor pod is deleted but the created resource is still running? In this case, the executor could perhaps try to automatically get the already created resource instead of trying to re-create when retrying and then encounter AlreadyExists error. But there should at least be some option in case some users may still want to treat this as failure when the executor pod fails. Do you have any proposed way of doing this?

I think we can add "createOrGet" action for not re-create when retrying and then encounter AlreadyExists error.

Would you like to contribute this feature?

Is this same as apply?


⚠ Spryr has degraded performance

In c86eba1, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 3942 ms

Resolved: Spryr performance has improved in 5314a64 after 7 minutes.


deadline saved from being lost on edit #77

Related Issue
Closes #77
Type of Change
Put x inside the square bracket to specify what type of change your PR is:

[x] Bug Fix

Description of Change
Deadline was lost on editing the task but now it will stay as default until updated.
Implementation Details
       hasDeadline = widget.task?.hasDeadline ?? false;     deadline = widget.task?.deadline;

Please resolve merge conflicts @Sanat-Jha and I will merge this

@pranavkonidena Merge conflicts resolved.


[INTEGRATION][DBT] Feature request: support dbt databricks as an adapter

dbt integration supports dbt-spark but not dbt-databricks.
The Databricks adapter is based on dbt-spark, what would be the impact of adding it as a supported adapter?
Have you considered it?

we've been working on a fork https://github.com/arosano-ext-addi/OpenLineage/tree/dbt/add-databricks-integration

@gvillafanetapia cool! Any problems you've encountered?

So far so good, we dodged the initial block.
We are getting an HTTP 400 response though, but this does not seem related to this library but to datakin implementation on Astronomer. They are looking into it.

I just got access to databricks. I can take a stab at testing it.

hi @RNHTTR 👋
So we tested again using our fork after the latest fixes in Astronomer and we are still getting HTTP error 400 Bad Request.
Let me know if you got the chance to test it. 🙏

@ext-gvillafane Sorry for the delay. Could you please try again? I think you should be able to get past the HTTP error 400 Bad Request now.


Error when trying to select "dataset" in [Refresh a dataset] action of [Power BI] connector.

Describe the Bug with repro steps
Logic app Standard
In Workflow -> designer

Click add action ([Refresh a dataset] action of [Power BI] connector)
Select [Workspace]
Select [Datasets] -> The error occurred, "e.charAt is not function"

The issue occurs only in the case of Standard Logic Apps new UI.

Standard Logic Apps Old UI

Consumption Logic Apps

What type of Logic App Is this happening in?
Standard (Portal)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos
No response
Browser
Edge
Additional context
No response

Hello @metakahash1,
I am having some trouble reproducing this error and need more information from you to continue fixing this. Please send this information to me through email at<EMAIL_ADDRESS>I need information from the console errors and the network calls.
To get this information please follow the instructions under "Collecting console errors" and "Collecting network logs in a HAR file" from our docs file found at this link. (https://purple-pebble-0e11de71e.1.azurestaticapps.net/tsg#collecting-console-errors)


Reuse matched params in menu

Now route matched parameters get to the menu at a rending. Before it wasn't. In Url view helper   it can be changed using parameter $reuseMatchedParams. How to be if $reuseMatchedParams is necessary in the menu, which rending with menu helper? Matched params in menu not always convenient and even disturbs. Really to create an separate route for each point of the menu? It is nonsense...

This issue has been closed as part of the bug migration program as outlined here - http://framework.zend.com/blog/2016-04-11-issue-closures.html


feat: Introduce ConnInfo helper/adapter

I created ConnInfo helper/adapter for Bun, Deno and CF Workers.
You can get client IP Address with Hono easier if we marge PR.
This provides runtime-less ConnInfo object.
For example, you can get IP Address on Bun:
import { Hono } from 'hono'
import { getConnInfo } from 'hono/bun'

const app = new Hono()

app.get('/', c => c.text(`Your ip address is ${getConnInfo(c).remote.address}!!`))

Bun.serve(app)

If you want to use Workers, replace import:
import { getConnInfo } from 'hono/cloudflare-workers'

In Deno:
import { getConnInfo } from 'https://deno.land/x/hono/helper.ts'

Author should do the followings, if applicable

[x] Add tests
[x] Run tests
[x] bun denoify to generate files for Deno

reference:

https://github.com/honojs/hono/issues/379
https://github.com/orgs/honojs/discussions/1439
https://github.com/orgs/honojs/discussions/1600
https://github.com/orgs/honojs/discussions/1187

@nakasyou
CI fails. Could you run bun run lint:fix (As you said on X, I might have made a mistake in configuring Prettier and ESLint)?

@yusukebe
If strings include single quote, CI fails due to Prettier or ESLint.
Prettier recommends "it's", but ESLint recommends 'it\'s'

Hey @nakasyou
Looks great! It's finished. This is a new feature, so I'm planning to release it in the next minor release, v4.4. So, I leave this PR not merged yet. Thanks!

Hello,
I tried to use:
import { getConnInfo } from 'https://deno.land/x/hono/helper.ts'

However, I get the following error. Is this because this is not yet available in v4.3.11? Is there a way I can use this with v4.3.11?
Module '"https://deno.land/x/hono/helper.ts"' has no exported member 'getConnInfo'.deno-ts(2305)

Thank you.

Hi @curioustolearn
Now deno.land/x is not used to publish the Deno module. Use the JSR package instead of it:
import { Hono } from 'jsr:@hono/hono'
import { getConnInfo } from 'jsr:@hono/hono/deno'


Must uncheck "Convert Z up to Y up" for use with three.js

Tested on Windows Firefox and Mac Chrome.
I have provided all working files and examples (including Blender file) here:
https://waistcoat.it/movecamera.zip
When exporting as .glb, if the "Convert Z up to Y up" is left checked, the camera animates correctly but traverses in the wrong direction (to the left). If unchecked, the camera moves forwards in the correct direction.
In the zip are two glb files:

movecamera-convertZchecked.glb
movecamera-convertZNOTchecked.glb

Simply swap the two filename references in the gltf.js file to see the results. The only change between these two files is the unchecking of the "Convert Z up to Y up" option.

Is there way to have option to setup those axis? Up and forward that depend which application that support default that different from way it setup. Example Godot Engine 3.0 which to work but it face other direction.

@Lightnet in glTF, +Y should always be up and +Z should always be forward. Anything else is an invalid glTF file, and the goal here is that Godot Engine should know what to expect and import correctly on their end. If that's not the case, you may want to file a bug with Godot.
The issue here is that the Blender exporter (or Blender itself) are not properly able to convert from Blender's coordinate system to glTF's.

Confirmed I get the same result in threejs and BabylonJS, so I think this is an exporter issue.

This isn't quite exact in the new exporter (https://github.com/KhronosGroup/glTF-Blender-IO/) but the result does match regardless of +Y/+Z settings, and it seems much closer. I think the remaining issue might have to do with camera perspective, and arguably that should be overridden in threeJS with the actual viewport size.
Closing for now but feel free to reopen in the new repo if things don't seem right.


Warnings when doing standalone kepler

What happened?
# rpm -qa | grep kepler
kepler-0.6.1-0.6.1.x86_64

but having such issue in logs
Nov 01 10:10:36 jitest51.novalocal kepler[25539]: E1101 10:10:36.958641   25539 utils.go:98] getCPUArch failure: open /var/lib/kepler/data/normalized_cpu_arch.csv: no such file or directory

What did you expect to happen?
no such error report
How can we reproduce it (as minimally and precisely as possible)?
start kepler independent process
Anything else we need to know?
No response
Kepler image tag

Kubernetes version

$ kubectl version
# paste output here

Cloud provider or bare metal

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Kepler deployment config

For on kubernetes:
$ KEPLER_NAMESPACE=kepler

# provide kepler configmap
$ kubectl get configmap kepler-cfm -n ${KEPLER_NAMESPACE}
# paste output here

# provide kepler deployment description
$ kubectl describe deployment kepler-exporter -n ${KEPLER_NAMESPACE}

For standalone:
put your Kepler command argument here

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

https://github.com/sustainable-computing-io/kepler/pull/1040


bash crash

Some bash execs can crash.
Bash has its' own memory allocation subsystem. Some distros enable bash memory alloc code, some don't.
The memory alloc used by bash is old. It is not thread safe. We create a situation where the periodic thread uses memory alloc in addition to bash and this can cause an issue.

When we re-direct bash malloc functions to glibc we no longer encounter segfaults or memory alloc issues.

Added integration test container "bash" that builds a bash executable both with and without its own memory subsystem.
This test runs a bash script in a relatively tight loop while setting SCOPE_SUMMARY_PERIOD=1, to make it likely that any issues with memory thread safety will be caught.
You can "test the test" by commenting out run_bash_mem_fix() in src/wrap.c, rebuilding the library, then running "docker-compose up bash".
One more note about things...  At the point in our constructor where run_bash_mem_fix() is called, we have not yet initialized things like our DBG() or scopeLog() functionality.  This means that the scopeLog() statements I added to src/bashmem.c will not be seen in out log output.  I considered removing these statements, but decided that they are still useful for clarity when reading, and even for debug (if someone wanted to set a breakpoint on scopeLog() for example).

Oh, and another note for what it's worth...  I wanted to understand if "dynamic programs defining their own memory subsystem" (like bash is doing here) is a common thing of if bash is pretty unique.  I ran this bash script on my ubuntu system and only found bash, for what that is worth.
#!/bin/bash

# for every directory in $PATH
for DIR in ${PATH//:/ }; do
    echo Searching $DIR...

    # for every file in the directory
    for FILE in $DIR/*;
    do
        # skip files that are not exectuable
        if [[ ! -x $FILE ]]; then
            continue
        fi

        # if malloc is defined by the executable, echo the file name
        if nm -D $FILE 2>/dev/null | grep " T malloc$"; then
            echo $FILE
        fi
    done
done


Caching / TTL

Do ya'll currently support a TTL or cache control within request? Are there any plans to or are there NPM modules that do caching with this?

No, request does not handle caching. There has been some opened issues about this over the years. The consensus by the authors / contributors seems to be having a separate module handle caching.
https://github.com/request/request/issues/1470 and https://github.com/request/request/issues/573 to name a few of the aforementioned issues which also links to some of the caching modules created so far.

That's an interesting decision. It seems very common in HTTP libraries to
include some sort of caching. A coworker of mine built this (since I asked
this question), and we've been using it, based on LRU -
https://www.npmjs.com/package/request-again
I do not know how to close the issue, but let's close it for now, since the
decision is a no caching in Request, thanks!
On Wed, May 27, 2015 at 12:22 PM, Phillip Johnsen<EMAIL_ADDRESS>wrote:

No, request does not handle caching. There has been some opened issues
about this over the years. The consensus by the authors / contributors
seems to be having a separate module handle caching.
#1470 https://github.com/request/request/issues/1470 and #573
https://github.com/request/request/issues/573 to name a few of the
aforementioned issues which also links to some of the caching modules
created so far.
--
Reply to this email directly or view it on GitHub
https://github.com/request/request/issues/1576#issuecomment-106003241.

--
[image: Giftnix]
Brandon Copley
Founder & CEO
t:<PHONE_NUMBER>
e<EMAIL_ADDRESS>

Would agree there's certainly room for the cache module to use in combination with request. I would really appreciate any thoughts from you related to caching in my newly opened issue https://github.com/request/request/issues/1604
Thanks for linking to request-again!


derived class has access to all virtual members

Earlier description was bit confusing as derived class doesn't have access to all the fields or properties. If this is in context to inheritance then it should mention public or protected access modifier. Since this article is related to polymorphism using Virtual keyword is more appropriate
Summary
Describe your changes here.
Fixes #Issue_Number (if available)

hi @BillWagner  Please review the PR

Thanks @dkj468
I've approved this PR, and I'll :shipit: as soon as the build completes. You should see the changes on the live site in the next day or so, on our regular publishing cycle.


[Documentation]: Missing 'help-wanted label' hyperlink updated

Notes for Reviewers
This PR fixes #11416
Signed commits

[X] Yes, I signed my commits.

🚀 Preview for commit 5a857a7c2905201066c042dcdcfc68d28c8ee8ec at: https://6698ca1b1755f066adc47833--meshery-docs-preview.netlify.app


checkhealth error

I'm working on MacOS with a new install of Neovim v0.9.1 from Homebrew and using LazyVim. I've added a file under .config/nvim/lua/plugins that is
{
   "amitds1997/remote-nvim.nvim",
   tag = "v0.0.1", -- It is recommended that you keep this pinned to a tag
   -- so that you do not pick up breaking changes
   dependencies = {
       "nvim-lua/plenary.nvim",
       "MunifTanjim/nui.nvim",
       "rcarriga/nvim-notify",
       -- This would be an optional dependency eventually
       "nvim-telescope/telescope.nvim",
   }
}

After this plugin installs and I run :checkhealth I get an error

I'm not sure where I put a config table when working with LazyVim. How do I go about getting this set up?

Could you try this?
{
   "amitds1997/remote-nvim.nvim",
   tag = "v0.0.1", -- It is recommended that you keep this pinned to a tag
   -- so that you do not pick up breaking changes
   dependencies = {
       "nvim-lua/plenary.nvim",
       "MunifTanjim/nui.nvim",
       "rcarriga/nvim-notify",
       -- This would be an optional dependency eventually
       "nvim-telescope/telescope.nvim",
   },
   config = true,
}

I also use lazy.nvim as the package manager which powers LazyVim too. And had no issue with it on v0.9.1. Only scenario I can imagine is that the setup() did not get called, in which case, config would indeed be nil.

I solved it by watching the YouTube video and adding to the setup function:
local remote_nvim = function()
  local util = require("remote-nvim.utils")
  require("remote-nvim").setup({
    -- Configuration for SSH connections made using this plugin
    ssh_config = {
      -- Binary with this name would be searched on your runtime path and would be
      -- used to run SSH commands. Rename this if your SSH binary is something else
      ssh_binary = "ssh",
      -- Similar to `ssh_binary`, but for copying over files onto remote server
      scp_binary = "scp",
      -- All your SSH config file paths.
      ssh_config_file_paths = { "$HOME/.ssh/config" },
      -- This helps the plugin to understand when the underlying binary expects
      -- input from user. This is useful for password-based authentication and
      -- key-based authentication.
      -- Explanation for each prompt:
      -- match - string - This would be matched with the SSH output to decide if
      -- SSH is waiting for input. This is a plain match (not a regex one)
      -- type - string - Takes two values "secret" or "plain". "secret" indicates
      -- that the value you would enter is a secret and should not be logged into
      -- your input history
      -- input_prompt - string - What is the input prompt that should be shown to
      -- user when this match happens
      -- value_type - string - Takes two values "static" and "dynamic". "static"
      -- means that the value can be cached for the same prompt for future commands
      -- (e.g. your password) so that you do not have to keep typing it again and
      -- again. This is retained in-memory and is not logged anywhere. When you
      -- close the editor, it is cleared from memory. "dynamic" is for something
      -- like MFA codes which change every time.
      ssh_prompts = {
        {
          match = "password:",
          type = "secret",
          input_prompt = "Enter password: ",
          value_type = "static",
          value = "",
        },
        {
          match = "continue connecting (yes/no/[fingerprint])?",
          type = "plain",
          input_prompt = "Do you want to continue connection (yes/no)? ",
          value_type = "static",
          value = "",
        },
      },
    },
    -- Installation script location on local machine (If you have your own custom
    -- installation script and you do not want to use the packaged install script.
    -- It should accept the same inputs as the packaged install script though)
    neovim_install_script_path = util.path_join(
      util.is_windows,
      util.get_package_root(),
      "scripts",
      "neovim_install.sh"
    ),
    -- Where should everything that Remote Neovim does on remote be stored. By
    -- default, it stores everything inside ~/.remote-nvim so as long as you
    -- delete that folder, you essentially wipe out everything that remote-nvim
    -- has over there.
    remote_neovim_install_home = util.path_join(util.is_windows, "~", ".remote-nvim"),
    -- Where is your personal Neovim config stored?
    neovim_user_config_path = util.path_join(util.is_windows, "~", ".config", "nvim"),
    local_client_config = {
      -- modify this function to override how your client launches
      -- function should accept two arguments function(local_port, workspace_config)
      -- local_port is the port on which the remote server is available locally
      -- workspace_config contains the workspace config. For all attributes present
      -- in it, see WorkspaceConfig in ./lua/remote-nvim/config.lua.
      -- See examples of callback in https://github.com/amitds1997/remote-nvim.nvim/wiki/Configuration-recipes
      callback = nil,
      -- [Subject to change]: These values may be subject to change, so there
      -- might be a breaking change. Right now, it uses the [plenary.nvim#win_float.percentage_range_window](https://github.com/nvim-lua/plenary.nvim/blob/267282a9ce242bbb0c5dc31445b6d353bed978bb/lua/plenary/window/float.lua#L138C25-L138C25)
      default_client_config = {
        col_percent = 0.9,
        row_percent = 0.9,
        win_opts = {
          winblend = 0,
        },
        border_opts = {
          topleft = "╭",
          topright = "╮",
          top = "─",
          left = "│",
          right = "│",
          botleft = "╰",
          botright = "╯",
          bot = "─",
        },
      },
    },
  })
end

return {
  "amitds1997/remote-nvim.nvim",
  tag = "v0.0.1",
  dependencies = {
    "nvim-lua/plenary.nvim",
    "MunifTanjim/nui.nvim",
    "rcarriga/nvim-notify",
    "nvim-telescope/telescope.nvim",
  },
  config = remote_nvim,
}

You can also just do
require('remote-nvim').setup({})

and it should work. These are the default options.

You can also just do
require('remote-nvim').setup({})

and it should work. These are the default options.

where should I write that line? in what file?

You can also just do
require('remote-nvim').setup({})

and it should work. These are the default options.

where should I write that line? in what file?

This is for an older version. The README instructions should set things up correctly. If you are facing any particular issues, could you open a new issue?


JsonSerializer does not honor the Options property

Describe the bug
The Manatee.Json.Serialization.JsonSerializer does not honor the configuration in the Options property.
To Reproduce
[Fact]
public void TestDateTimeCustomFormatToJson() {
	var date = new System.DateTime(1989, 4, 16, 13, 11, 20, 721, DateTimeKind.Utc);
	var serializer = new Manatee.Json.Serialization.JsonSerializer();
	// serializer.Options.DateTimeSerializationFormat = Manatee.Json.Serialization.DateTimeSerializationFormat.Iso8601;
	serializer.Options.CustomDateTimeSerializationFormat = "yyyy-MM-ddTHH:mm:ss.fffzzz";
	var actual = serializer.Serialize<System.DateTime>(date).ToString();
	var expected = "\"1989-04-16T13:11:20.721+00:00\"";
	Assert.Equal(expected, actual);
}

[Fact]
public void TestDateTimeCustomFormatFromJson() {
	var serializer = new Manatee.Json.Serialization.JsonSerializer();
	// serializer.Options.DateTimeSerializationFormat = Manatee.Json.Serialization.DateTimeSerializationFormat.Iso8601;
	serializer.Options.CustomDateTimeSerializationFormat = "yyyy-MM-ddTHH:mm:ss.fffzzz";

	var actual = serializer.Deserialize<System.DateTime>(
		Manatee.Json.JsonValue.Parse("\"1989-04-16T13:11:20.721+00:00\""));
	var expected = new System.DateTime(1989, 4, 16, 13, 11, 20, 721, DateTimeKind.Utc);
	Assert.Equal(expected.ToString(), actual.ToString());
}

Expected behavior
The dates where expected to follow the format specified.
Desktop (please complete the following information):

OS: Windows 10
.Net Target Core
Version 3.0

Additional context
Add any other context about the problem here.

You need to set
serializer.Options.DateTimeSerializationFormat = DateTimeSerializationFormat.Custom

Granted, the remark on that property "If a custom serializer for DateTime has been registered, this property will have no effect." isn't worded in the best way.

You need to set
serializer.Options.DateTimeSerializationFormat = DateTimeSerializationFormat.Custom;

I can update the property to auto-set the format to custom when a custom format is set as well.

Ok, thanks, now I got it working :) Yes that is probably a good idea :)
I have another question though, if I instead of Cusom I choose Iso8601 I would expect the output to be the same, according to your documentation:

// Summary:
//     Output conforms to ISO 8601 formatting: YYYY-MM-DDThh:mm:ss.sTZD (e.g. 1997-07-16T19:20:30.45+01:00)

But the following tests fail even though they follow the format specified above.
[Fact]
public void TestDateTimeCustomFormatToJson() {
	var date = new System.DateTime(1989, 4, 16, 13, 11, 20, 721, DateTimeKind.Utc);
	var serializer = new Manatee.Json.Serialization.JsonSerializer();
	serializer.Options.DateTimeSerializationFormat = Manatee.Json.Serialization.DateTimeSerializationFormat.Iso8601;

	var actual = serializer.Serialize<System.DateTime>(date).ToString();
	var expected = "\"1989-04-16T13:11:20.721+00:00\"";
	Assert.Equal(expected, actual);
}

[Fact]
public void TestDateTimeCustomFormatFromJson() {
	var serializer = new Manatee.Json.Serialization.JsonSerializer();
	serializer.Options.DateTimeSerializationFormat = Manatee.Json.Serialization.DateTimeSerializationFormat.Iso8601;

	var actual = serializer.Deserialize<System.DateTime>(
		Manatee.Json.JsonValue.Parse("\"1989-04-16T13:11:20.721+00:00\"")).ToUniversalTime();
	var expected = new System.DateTime(1989, 4, 16, 13, 11, 20, 721, DateTimeKind.Utc);
	Assert.Equal(expected.ToString(), actual.ToString());
}

Hm... looks like I have tests for the other formats, but not for ISO 8601.  Odd.  I'll add these.  Thanks.

I'm going to use the built-in .ToString("O") which is ISO 8601 formatting.  This results in a string that is 1989-04-16T13:11:20.7210000Z, not what you have, so you'll still want to use custom formatting if you want the TZ encoded.

I'm going to use the built-in .ToString("O") which is ISO 8601 formatting. This results in a string that is 1989-04-16T13:11:20.7210000Z, not what you have, so you'll still want to use custom formatting if you want the TZ encoded.

ok, have you released that? I would prefer to use ISO 8601 instead of a custom format.

I'm having some build issues due to some new schema tests. Working to resolve those, then I'll release.

This is resolved in v13


Revisiting issue - Accessing react component context in mapStateToProps()

I know this accessing react component like this:
connect((appState, ownProps, ownContext) => { ... })
has already been discussed.
i've read the following discussion https://github.com/reduxjs/react-redux/issues/289 which concluded with this statement from @jimbolla :

Until the day comes that React has a fully blessed context API, adding support for it is a maintenance liability for React Redux.

However ... Now React API Context is stable.
Is it the right time to request this feature from react-redux maintainers?

No, because the new context API is very different than the old context API.  Instead of a single global namespace, it's now Provider/Consumer pairs, and the consumer is used with a "render props" approach.  Nothing for us to do there.

Hi @markerikson
I read the v6 release notes:

switched from direct store subscriptions in components, to propagating store state updates via createContext

does it actually answer the request of this issue? i'm not quite sure i understood.

Yes, v6 uses createContext internally.


Pip Package Support for Python 3.10

Noticed that a recent issue added some support for Python 3.10, but I believe this hasn't been extended to the pip package. Running !pip install chai_lab gives me the following traceback on Colab:
ERROR: Ignored the following versions that require a different python version: 0.0.1 Requires-Python >=3.11
ERROR: Could not find a version that satisfies the requirement chai_lab (from versions: none)
ERROR: No matching distribution found for chai_lab

It seems more like a python version issue and like for 1st error pip may have find that chai_lab is only compatible with python version - Python 3.11 or the above, you can may well update your version.

you can install a new version:
pip install git+https://github.com/chaidiscovery/chai-lab.git

Hi Navvye, please use command posted by @Garhorne0813 for now, we'll publish a version with support of python3.10 on pypi soon.

new version on pypi should support python 3.10:
pip install chai_lab==0.1.0


dehydrated does not work with DigiCert ACMEv2 API - token value confusion between challenge types

The current code within sign_csr() that tries to determine the token to use with the selected challenge type seems to fail to pick the correct token.
If dehydrated is configured to perform dns-01 validation, but the ACME API returns all three challenge types (dns-01, tls-alpn-01, http-01) BUT with different token values for each, the token value from the last entry in the list is used.
e.g. the token value specific to the http-01 challenge is used by dehydrated as part of dns-01 (hook deploys DNS record), and the DigiCert ACMEv2 API when asked to verify that token (it's the http-01 NOT the dns-01 value) it goes ahead and correctly performs a check for http-01 token via HTTP instead of dns-01 via DNS.
The issue is in sign_csr() when it iterates over the list of challenges return in the JSON payload from this response,
`HTTP/1.1 200 OK
Server: nginx
Date: Wed, 27 May 2020 23:07:02 GMT
Content-Type: application/json
Content-Length: 892
Connection: keep-alive
Cache-Control: public, max-age=0, no-cache
Cache-Control: public, max-age=0, no-cache
Link: https://acme.digicert.com/v2/acme/account/SECRET_UNIQUE_ACCOUNT_VALUE;rel="up"
Location: https://acme.digicert.com/v2/acme/authz/SECRET_UNIQUE_ACCOUNT_VALUE/UNIQUE_REQUEST_VALUE
Replay-Nonce: NONCE_VALUE
X-Correlation-Id: F19D8DE2-CC90-52BC-0422-3BD27D01069F
X-Hostname: enrollme05.slc.digicert.com
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=31536000
{
"challenges": [
{
"status": "pending",
"token": "kea-gtCl0nnJqDHu05N3JD3s-zwQNiXU",
"type": "dns-01",
"url": "https://acme.digicert.com/v2/acme/challenge/SECRET_UNIQUE_ACCOUNT_VALUE/UNIQUE_REQUEST_VALUE/q2quuRXWzp8LhnLj"
},
{
"status": "pending",
"token": "4tUeO_9MxeWFl8pGflNQMxnBQV1xpT-2",
"type": "tls-alpn-01",
"url": "https://acme.digicert.com/v2/acme/challenge/SECRET_UNIQUE_ACCOUNT_VALUE/UNIQUE_REQUEST_VALUE/DilxB7yuGKKjXii4"
},
{
"status": "pending",
"token": "4ZDSajMX7nzWR2diVSs6alSCHQVlxuKJ",
"type": "http-01",
"url": "https://acme.digicert.com/v2/acme/challenge/SECRET_UNIQUE_ACCOUNT_VALUE/UNIQUE_REQUEST_VALUE/iH1RuwXGm4tHWU62"
}
],
"expires": "2020-05-29T17:07:00-06:00",
"identifier": {
"type": "dns",
"value": "sub.domain.tld"
},
"status": "pending",
"wildcard": false
}`

Example from Let's Encrypt, where token values are all the same... so the assumption that the last token value can be used.
`HTTP/1.1 200 OK
Server: nginx
Date: Wed, 27 May 2020 23:27:55 GMT
Content-Type: application/json
Content-Length: 818
Connection: keep-alive
Boulder-Requester: 13894319
Cache-Control: public, max-age=0, no-cache
Link: https://acme-staging-v02.api.letsencrypt.org/directory;rel="index"
Replay-Nonce: NONCE_VALUE
X-Frame-Options: DENY
Strict-Transport-Security: max-age=604800
{
"identifier": {
"type": "dns",
"value": "test1234.domain.tld"
},
"status": "pending",
"expires": "2020-06-03T23:27:54Z",
"challenges": [
{
"type": "http-01",
"status": "pending",
"url": "https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/ACCOUNT_ID/3YO5Sg",
"token": "B1Nsb3u9zGdG5acKyZwcce7c8ID53jT-pPHMitntIkM"
},
{
"type": "dns-01",
"status": "pending",
"url": "https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/59753864/f-0OxA",
"token": "B1Nsb3u9zGdG5acKyZwcce7c8ID53jT-pPHMitntIkM"
},
{
"type": "tls-alpn-01",
"status": "pending",
"url": "https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/59753864/OyavkQ",
"token": "B1Nsb3u9zGdG5acKyZwcce7c8ID53jT-pPHMitntIkM"
}
]
}`

Summary of issues found in DigiCert ACME API endpoint:

TAB characters included with spaces in body of response, e.g. inside JSON formatted content, have to update clean_json() function to replaces any instance of space and/or tab with single space
Even though challenge has been completed successfully, DigiCert ACMEv2 API may respond with "processing" instead of "pending", where Let's Encrypt will always respond with "pending"... "processing" is a valid status according to RFC8555 and seems to indicate the same thing... that the ACME client should back off and try again shortly.

Tested against both Let's Encrypt and DigiCert... DigiCert failing for somewhat expected reason now, e.g. no funds to use for cert.
`$ diff -u /usr/bin/dehydrated.latest /usr/bin/dehydrated
--- /usr/bin/dehydrated.latest	2020-05-28 13:34:00.485242030 +1000
+++ /usr/bin/dehydrated	2020-05-28 14:00:18.774128866 +1000
@@ -453,7 +453,7 @@
Remove newlines and whitespace from json
clean_json() {

tr -d '\r\n' | _sed -e 's/ +/ /g' -e 's/{ /{/g' -e 's/ }/}/g' -e 's/[ /[/g' -e 's/ ]/]/g'

tr -d '\r\n' | _sed -e 's/[ \t]+/ /g' -e 's/{ /{/g' -e 's/ }/}/g' -e 's/[ /[/g' -e 's/ ]/]/g'
}

Encode data as url-safe formatted base64
@@ -744,7 +744,7 @@
fi
 # Find challenge in authorization

challenges="$(echo "${response}" | _sed 's/."challenges": [({.})].*/\1/')"

challenges="$(echo "${response}" | get_json_array_value challenges)"
challenge="$(<<<"${challenges}" _sed -e 's/^[^[]+[(.+)]$/\1/' -e 's/}(, ({)|(]))/}'$'\n''\2/g' | grep ""${CHALLENGETYPE}"" || true)"
if [ -z "${challenge}" ]; then
allowed_validations="$(grep -Eo '"type": "[^"]+"' <<< "${challenges}" | grep -Eo ' "[^"]+"' | _sed -e 's/"//g' -e 's/^ //g')"
@@ -817,7 +817,7 @@
reqstatus="$(printf '%s\n' "${result}" | get_json_string_value status)"

while [[ "${reqstatus}" = "pending" ]]; do

while [[ "${reqstatus}" = "pending" ]] || [[ "${reqstatus}" = "processing" ]]; do
sleep 1
if [[ "${API}" -eq 2 ]]; then
result="$(signed_request "${challenge_uris[${idx}]}" "")"
$

$ rm -rf /etc/dehydrated/accounts/* /etc/dehydrated/certs/* /etc/dehydrated/chains/* /etc/dehydrated/archive/*
$ dehydrated --cron --accept-terms --config /etc/dehydrated/config_letsencrypt --hook /etc/dehydrated/hooks/dehydrated-lexicon
INFO: Using main config file /etc/dehydrated/config_letsencrypt
INFO: Using additional config file /etc/dehydrated/conf.d/local.sh

Generating account key...
Registering account key with ACME server...
Fetching account URL...
Processing test1234.domain.tld
Creating new directory /etc/dehydrated/certs/test1234.domain.tld ...
Signing domains...
Generating private key...
Generating signing request...
Requesting new certificate order from CA...
Received 1 authorizations URLs from the CA
Handling authorization for test1234.domain.tld
1 pending challenge(s)
Deploying challenge tokens...
deploy_challenge called: test1234.domain.tld, DcGPJRRvAZa3Z_3lX2sv-Clog4RyNLwU2ru_zc2SWUQ, YjbusyGcy3ofi2Ye-kEmDrkLSlWRHIsGFoTpn8PU6YA
Responding to challenge for test1234.domain.tld authorization...
Challenge is valid!
Cleaning challenge tokens...
clean_challenge called: test1234.domain.tld, DcGPJRRvAZa3Z_3lX2sv-Clog4RyNLwU2ru_zc2SWUQ, YjbusyGcy3ofi2Ye-kEmDrkLSlWRHIsGFoTpn8PU6YA
Requesting certificate...
Checking certificate...
Done!
Creating fullchain.pem...
Done!
$

$ dehydrated --cron --accept-terms --config /etc/dehydrated/config_digicert --hook /etc/dehydrated/hooks/dehydrated-lexicon
INFO: Using main config file /etc/dehydrated/config_digicert
INFO: Using additional config file /etc/dehydrated/conf.d/local.sh

Generating account key...
Registering account key with ACME server...
Fetching account URL...
Processing test1234.domain.tld
Creating new directory /etc/dehydrated/certs/test1234.domain.tld ...
Signing domains...
Generating private key...
Generating signing request...
Requesting new certificate order from CA...
Received 1 authorizations URLs from the CA
Handling authorization for test1234.domain.tld
1 pending challenge(s)
Deploying challenge tokens...
deploy_challenge called: test1234.domain.tld, 49G7ClNPmL0fxEeg-z_pocUtuoU8T_kl, _aeTvrwANeM-0J2i48LhRjqZMfT4XY75_mL21j41Yf0
Responding to challenge for test1234.domain.tld authorization...
Challenge is valid!
Cleaning challenge tokens...
clean_challenge called: test1234.domain.tld, 49G7ClNPmL0fxEeg-z_pocUtuoU8T_kl, _aeTvrwANeM-0J2i48LhRjqZMfT4XY75_mL21j41Yf0
Requesting certificate...
ERROR: An error occurred while sending post-request to https://acme.digicert.com/v2/acme/finalize/UNIQUE_VALUE/UNIQUE_VALUE (Status 500)

Details:
HTTP/1.1 100 Continue
HTTP/1.1 500 Internal Server Error
Server: nginx
Date: Thu, 28 May 2020 04:07:12 GMT
Content-Type: application/problem+json
Content-Length: 274
Connection: keep-alive
Cache-Control: public, max-age=0, no-cache
Replay-Nonce: NONCE_WAS_HERE
X-Correlation-Id: 5E3CDD4E-0370-10BC-4D80-2371F8A3D370
X-Hostname: enrollme03.slc.digicert.com
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=31536000
{"detail":"failed to request certificate, {"errors":[{"code":"insufficient_funds","message":"There are insufficient funds available in your account to complete this request.  Please deposit additional funds and try again."}]}","status":500,"type":"serverInternal"}
$`

@colin-stubbs Can you check my pull request? It's essentially a rebase of your patch to master (which uses json.sh).

I think this should be fixed by now, otherwise please comment or feel free to open a new issue.