Plugin uses or overrides a deprecated API  Warnings While Compiling Flutter Gallery To An APK

$ flutter build apk
Running "flutter packages get" in flutter_gallery...         1.1s
Initializing gradle...                                       2.4s
Resolving dependencies...                                   17.7s
Gradle task 'assembleRelease'...
Note: /Users/mit/dev/flutter/.pub-cache/hosted/pub.dartlang.org/video_player-0.6.4/android/src/main/java/io/flutter/plugins/videoplayer/VideoPlayerPlugin.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

$ flutter --version
Flutter 0.9.6-pre.35 • channel master • https://github.com/flutter/flutter.git
Framework • revision 2a8e35cc9c (2 days ago) • 2018-09-29 08:29:28 +0700
Engine • revision 0c2b6dc6e3
Tools • Dart 2.1.0-dev.6.0.flutter-2aac05fe10

Such warning still exist

flutter doctor -v
[√] Flutter (Channel stable, v1.12.13+hotfix.8, on Microsoft Windows [Version 10.0.19041.84], locale en-US)
    • Flutter version 1.12.13+hotfix.8 at C:\Code\flutter_stable
    • Framework revision 0b8abb4724 (4 weeks ago), 2020-02-11 11:44:36 -0800
    • Engine revision e1e6ced81d
    • Dart version 2.7.0

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at C:\Code\SDK
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = C:\Code\SDK
    • Java binary at: C:\Code\android-studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
    • All Android licenses accepted.

[√] Android Studio (version 3.6)
    • Android Studio at C:\Code\android-studio
    • Flutter plugin version 44.0.2
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)

[√] VS Code (version 1.43.0)
    • VS Code at C:\Users\Taha\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.8.1

[√] Connected device (1 available)
    • SM M305F • 32003c30dc19668f • android-arm64 • Android 10 (API 29)

• No issues found!

flutter build apk --verbose
[  +31 ms] executing: [C:\Code\flutter_stable\] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +83 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[   +1 ms] 0b8abb4724aa590dd0f429683339b1e045a1594d
[   +1 ms] executing: [C:\Code\flutter_stable\] git describe --match v*.*.* --first-parent --long --tags
[  +61 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long --tags
[        ] v1.12.13+hotfix.8-0-g0b8abb472
[  +18 ms] executing: [C:\Code\flutter_stable\] git rev-parse --abbrev-ref --symbolic @{u}
[  +55 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [C:\Code\flutter_stable\] git ls-remote --get-url origin
[  +51 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[ +107 ms] executing: [C:\Code\flutter_stable\] git rev-parse --abbrev-ref HEAD
[  +54 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[  +54 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[   +9 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[  +27 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +161 ms] Found plugin connectivity at C:\Code\flutter_stable\.pub-cache\hosted\pub.dartlang.org\connectivity-0.4.5+3\
[  +23 ms] Found plugin device_info at C:\Code\flutter_stable\.pub-cache\hosted\pub.dartlang.org\device_info-0.4.1+1\
[ +101 ms] Found plugin url_launcher at C:\Code\flutter_stable\.pub-cache\hosted\pub.dartlang.org\url_launcher-5.2.5\
[   +5 ms] Found plugin video_player at C:\Code\flutter_stable\.pub-cache\hosted\pub.dartlang.org\video_player-0.10.2+5\
[  +84 ms] Found plugin connectivity at C:\Code\flutter_stable\.pub-cache\hosted\pub.dartlang.org\connectivity-0.4.5+3\
[   +8 ms] Found plugin device_info at C:\Code\flutter_stable\.pub-cache\hosted\pub.dartlang.org\device_info-0.4.1+1\
[  +68 ms] Found plugin url_launcher at C:\Code\flutter_stable\.pub-cache\hosted\pub.dartlang.org\url_launcher-5.2.5\
[   +4 ms] Found plugin video_player at C:\Code\flutter_stable\.pub-cache\hosted\pub.dartlang.org\video_player-0.10.2+5\
[  +68 ms] Generating
C:\Code\flutter_stable\examples\flutter_gallery\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java
[ +112 ms] You are building a fat APK that includes binaries for android-arm, android-arm64, android-x64.
[   +2 ms] If you are deploying the app to the Play Store, it's recommended to use app bundles or split the APK to reducethe APK
           size.
[  +36 ms]     To generate an app bundle, run:
[   +2 ms]         flutter build appbundle --target-platform android-arm,android-arm64,android-x64
[   +1 ms]         Learn more on: https://developer.android.com/guide/app-bundle
[   +1 ms]     To split the APKs per ABI, run:
[  +23 ms]         flutter build apk --target-platform android-arm,android-arm64,android-x64 --split-per-abi
[   +1 ms]         Learn more on:  https://developer.android.com/studio/build/configure-apk-splits#configure-abi-split
[  +58 ms] Running Gradle task 'assembleRelease'...
[   +5 ms] gradle.properties already sets `android.enableR8`
[  +77 ms] Using gradle from C:\Code\flutter_stable\examples\flutter_gallery\android\gradlew.bat.
[  +10 ms] executing: C:\Code\android-studio\jre\bin\java -version
[ +133 ms] Exit code 0 from: C:\Code\android-studio\jre\bin\java -version
[   +2 ms] openjdk version "1.8.0_212-release"
           OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
           OpenJDK 64-Bit Server VM (build 25.212-b04, mixed mode)
[   +4 ms] executing: [C:\Code\flutter_stable\examples\flutter_gallery\android\]
C:\Code\flutter_stable\examples\flutter_gallery\android\gradlew.bat -Pverbose=true -Ptarget=lib\main.dart
-Ptrack-widget-creation=true -Pshrink=true -Ptarget-platform=android-arm,android-arm64,android-x64 assembleRelease
[ +751 ms] Welcome to Gradle 5.6.2!
[   +1 ms] Here are the highlights of this release:
[   +1 ms]  - Incremental Groovy compilation
[   +1 ms]  - Groovy compile avoidance
[   +1 ms]  - Test fixtures for Java projects
[   +1 ms]  - Manage plugin versions via settings script
[   +1 ms] For more details see https://docs.gradle.org/5.6.2/release-notes.html
[+36661 ms] > Task :app:compileFlutterBuildRelease
[   +1 ms] [  +41 ms] executing: [C:\Code\flutter_stable\] git -c log.showSignature=false log -n 1 --pretty=format:%H
[   +1 ms] [  +80 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] [        ] 0b8abb4724aa590dd0f429683339b1e045a1594d
[        ] [        ] executing: [C:\Code\flutter_stable\] git describe --match v*.*.* --first-parent --long --tags
[        ] [  +49 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long --tags
[        ] [        ] v1.12.13+hotfix.8-0-g0b8abb472
[        ] [  +10 ms] executing: [C:\Code\flutter_stable\] git rev-parse --abbrev-ref --symbolic @{u}
[  +17 ms] [  +49 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[  +12 ms] [        ] origin/stable
[   +1 ms] [        ] executing: [C:\Code\flutter_stable\] git ls-remote --get-url origin
[  +19 ms] [  +49 ms] Exit code 0 from: git ls-remote --get-url origin
[   +2 ms] [        ] https://github.com/flutter/flutter.git
[   +1 ms] [ +100 ms] executing: [C:\Code\flutter_stable\] git rev-parse --abbrev-ref HEAD
[   +1 ms] [  +51 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[   +1 ms] [        ] stable
[  +18 ms] [  +24 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[   +1 ms] [        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] [   +5 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[   +1 ms] [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[  +11 ms] [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[   +1 ms] [        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[        ] [ +169 ms] Initializing file store
[   +1 ms] [  +76 ms] kernel_snapshot: Starting due to {}
[  +13 ms] [  +31 ms] C:\Code\flutter_stable\bin\cache\dart-sdk\bin\dart.exe
C:\Code\flutter_stable\bin\cache\artifacts\engine\windows-x64\frontend_server.dart.snapshot --sdk-root
C:\Code\flutter_stable\bin\cache\artifacts\engine\common\flutter_patched_sdk_product/ --target=flutter
-Ddart.developer.causal_async_stacks=true -Ddart.vm.profile=false -Ddart.vm.product=true
--bytecode-options=source-positions --aot --tfa --packages C:\Code\flutter_stable\examples\flutter_gallery\.packages
--output-dill
C:\Code\flutter_stable\examples\flutter_gallery\.dart_tool\flutter_build\07a29a729adbaefb86ed3a3d484fb9ad\app.dill
--depfile
C:\Code\flutter_stable\examples\flutter_gallery\.dart_tool\flutter_build\07a29a729adbaefb86ed3a3d484fb9ad\kernel_snapshot.d package:flutter_gallery/main.dart
[+28573 ms] [+29085 ms] kernel_snapshot: Complete
[+1398 ms] [+1355 ms] invalidated build due to missing files:
C:\Code\flutter_stable\bin\cache\artifacts\engine\android-arm-release\windows-x64\gen_snapshot
[   +1 ms] [   +2 ms] aot_android_asset_bundle: Starting due to {}
[+1401 ms] [+1375 ms] invalidated build due to missing files:
C:\Code\flutter_stable\bin\cache\artifacts\engine\android-arm64-release\windows-x64\gen_snapshot
[   +4 ms] [  +30 ms] invalidated build due to missing files:
C:\Code\flutter_stable\bin\cache\artifacts\engine\android-x64-release\windows-x64\gen_snapshot
[+1004 ms] [ +976 ms] android_aot_release_android-x64: Starting due to {InvalidatedReason.inputChanged,
InvalidatedReason.inputMissing}
[  +28 ms] [   +7 ms] executing:
C:\Code\flutter_stable\bin\cache\artifacts\engine\android-x64-release\windows-x64\gen_snapshot --causal_async_stacks
--deterministic --snapshot_kind=app-aot-elf
--elf=C:\Code\flutter_stable\examples\flutter_gallery\.dart_tool\flutter_build\07a29a729adbaefb86ed3a3d484fb9ad\x86_64\app.so --strip
C:\Code\flutter_stable\examples\flutter_gallery\.dart_tool\flutter_build\07a29a729adbaefb86ed3a3d484fb9ad\app.dill
[  +10 ms] [   +1 ms] android_aot_release_android-arm: Starting due to {InvalidatedReason.inputChanged,
InvalidatedReason.inputMissing}
[   +2 ms] [   +2 ms] executing:
C:\Code\flutter_stable\bin\cache\artifacts\engine\android-arm-release\windows-x64\gen_snapshot --causal_async_stacks
--deterministic --snapshot_kind=app-aot-elf
--elf=C:\Code\flutter_stable\examples\flutter_gallery\.dart_tool\flutter_build\07a29a729adbaefb86ed3a3d484fb9ad\armeabi-v7a\app.so --strip --no-sim-use-hardfp --no-use-integer-division
C:\Code\flutter_stable\examples\flutter_gallery\.dart_tool\flutter_build\07a29a729adbaefb86ed3a3d484fb9ad\app.dill
[   +2 ms] [        ] android_aot_release_android-arm64: Starting due to {InvalidatedReason.inputChanged,
InvalidatedReason.inputMissing}
[   +1 ms] [   +2 ms] executing:
C:\Code\flutter_stable\bin\cache\artifacts\engine\android-arm64-release\windows-x64\gen_snapshot --causal_async_stacks
--deterministic --snapshot_kind=app-aot-elf
--elf=C:\Code\flutter_stable\examples\flutter_gallery\.dart_tool\flutter_build\07a29a729adbaefb86ed3a3d484fb9ad\arm64-v8a\app.so --strip
C:\Code\flutter_stable\examples\flutter_gallery\.dart_tool\flutter_build\07a29a729adbaefb86ed3a3d484fb9ad\app.dill
[   +3 ms] [  +15 ms] aot_android_asset_bundle: Complete
[+25249 ms] [+25261 ms] android_aot_release_android-x64: Complete
[  +95 ms] [ +128 ms] android_aot_bundle_release_android-x64: Starting due to {InvalidatedReason.inputChanged}
[        ] [  +26 ms] android_aot_bundle_release_android-x64: Complete
[        ] [  +12 ms] android_aot_release_android-arm64: Complete
[ +205 ms] [ +132 ms] android_aot_bundle_release_android-arm64: Starting due to {InvalidatedReason.inputChanged}
[   +1 ms] [  +22 ms] android_aot_bundle_release_android-arm64: Complete
[+3090 ms] [+3130 ms] android_aot_release_android-arm: Complete
[  +96 ms] [ +127 ms] android_aot_bundle_release_android-arm: Starting due to {InvalidatedReason.inputChanged}
[ +111 ms] [  +21 ms] android_aot_bundle_release_android-arm: Complete
[  +94 ms] [ +123 ms] _composite: Starting due to {}
[   +1 ms] [        ] _composite: Complete
[        ] [  +12 ms] Persisting file store
[        ] [  +30 ms] Done persisting file store
[        ] [   +8 ms] build succeeded.
[        ] [  +30 ms] "flutter assemble" took 62,286ms.
[+3000 ms] > Task :app:packLibsflutterBuildRelease
[   +2 ms] > Task :app:preBuild UP-TO-DATE
[        ] > Task :app:extractProguardFiles
[        ] > Task :app:preReleaseBuild
[        ] > Task :connectivity:preBuild UP-TO-DATE
[   +1 ms] > Task :connectivity:preReleaseBuild UP-TO-DATE
[   +2 ms] > Task :connectivity:compileReleaseAidl NO-SOURCE
[        ] > Task :device_info:preBuild UP-TO-DATE
[        ] > Task :device_info:preReleaseBuild UP-TO-DATE
[        ] > Task :device_info:compileReleaseAidl NO-SOURCE
[   +1 ms] > Task :url_launcher:preBuild UP-TO-DATE
[  +19 ms] > Task :url_launcher:preReleaseBuild UP-TO-DATE
[   +1 ms] > Task :url_launcher:compileReleaseAidl NO-SOURCE
[   +1 ms] > Task :video_player:preBuild UP-TO-DATE
[   +1 ms] > Task :video_player:preReleaseBuild UP-TO-DATE
[        ] > Task :video_player:compileReleaseAidl NO-SOURCE
[   +1 ms] > Task :app:compileReleaseAidl NO-SOURCE
[  +55 ms] > Task :connectivity:packageReleaseRenderscript NO-SOURCE
[   +6 ms] > Task :device_info:packageReleaseRenderscript NO-SOURCE
[   +2 ms] > Task :url_launcher:packageReleaseRenderscript NO-SOURCE
[   +1 ms] > Task :video_player:packageReleaseRenderscript NO-SOURCE
[        ] > Task :app:compileReleaseRenderscript NO-SOURCE
[   +1 ms] > Task :app:checkReleaseManifest
[   +1 ms] > Task :app:generateReleaseBuildConfig
[        ] > Task :connectivity:checkReleaseManifest
[   +1 ms] > Task :connectivity:compileReleaseRenderscript NO-SOURCE
[  +84 ms] > Task :connectivity:generateReleaseBuildConfig
[ +108 ms] > Task :connectivity:generateReleaseResValues
[   +1 ms] > Task :connectivity:generateReleaseResources
[  +93 ms] > Task :connectivity:packageReleaseResources
[ +393 ms] > Task :device_info:checkReleaseManifest
[   +1 ms] > Task :device_info:compileReleaseRenderscript NO-SOURCE
[        ] > Task :device_info:generateReleaseBuildConfig
[        ] > Task :connectivity:parseReleaseLibraryResources
[        ] > Task :device_info:generateReleaseResValues
[   +1 ms] > Task :device_info:generateReleaseResources
[ +103 ms] > Task :device_info:packageReleaseResources
[   +2 ms] > Task :connectivity:javaPreCompileRelease
[        ] > Task :url_launcher:checkReleaseManifest
[        ] > Task :url_launcher:compileReleaseRenderscript NO-SOURCE
[  +90 ms] > Task :url_launcher:generateReleaseBuildConfig
[  +15 ms] > Task :url_launcher:generateReleaseResValues
[ +130 ms] > Task :url_launcher:generateReleaseResources
[  +20 ms] > Task :url_launcher:packageReleaseResources
[  +68 ms] > Task :device_info:processReleaseManifest
[   +1 ms] > Task :device_info:javaPreCompileRelease
[  +84 ms] > Task :connectivity:processReleaseManifest
[  +83 ms] > Task :url_launcher:javaPreCompileRelease
[   +5 ms] > Task :device_info:parseReleaseLibraryResources
[        ] > Task :url_launcher:parseReleaseLibraryResources
[   +1 ms] > Task :video_player:checkReleaseManifest
[        ] > Task :video_player:compileReleaseRenderscript NO-SOURCE
[        ] > Task :video_player:generateReleaseBuildConfig
[        ] > Task :video_player:generateReleaseResValues
[        ] > Task :video_player:generateReleaseResources
[        ] > Task :url_launcher:processReleaseManifest
[   +1 ms] > Task :video_player:packageReleaseResources
[  +30 ms] > Task :device_info:generateReleaseRFile
[+1252 ms] > Task :device_info:compileReleaseJavaWithJavac
[   +2 ms] Note:
C:\Code\flutter_stable\.pub-cache\hosted\pub.dartlang.org\device_info-0.4.1+1\android\src\main\java\io\flutter\plugins\deviceinfo\DeviceInfoPlugin.java uses or overrides a deprecated API.
[  +18 ms] Note: Recompile with -Xlint:deprecation for details.
[   +1 ms] > Task :url_launcher:generateReleaseRFile
[ +472 ms] > Task :url_launcher:compileReleaseJavaWithJavac
[   +1 ms] Note: Some input files use or override a deprecated API.
[   +1 ms] Note: Recompile with -Xlint:deprecation for details.
[   +1 ms] > Task :connectivity:generateReleaseRFile
[ +203 ms] > Task :connectivity:compileReleaseJavaWithJavac
[   +4 ms] Note: Some input files use or override a deprecated API.
[   +1 ms] Note: Recompile with -Xlint:deprecation for details.
[        ] > Task :video_player:parseReleaseLibraryResources
[ +184 ms] > Task :connectivity:bundleLibCompileRelease
[  +25 ms] > Task :video_player:processReleaseManifest
[   +6 ms] > Task :device_info:bundleLibCompileRelease
[        ] > Task :url_launcher:bundleLibCompileRelease
[        ] > Task :app:cleanMergeReleaseAssets UP-TO-DATE
[   +1 ms] > Task :video_player:javaPreCompileRelease
[  +63 ms] > Task :app:mergeReleaseShaders
[  +38 ms] > Task :app:compileReleaseShaders
[   +6 ms] > Task :app:generateReleaseAssets
[   +1 ms] > Task :connectivity:mergeReleaseShaders
[        ] > Task :connectivity:compileReleaseShaders
[        ] > Task :connectivity:generateReleaseAssets
[        ] > Task :connectivity:packageReleaseAssets
[        ] > Task :device_info:mergeReleaseShaders
[        ] > Task :device_info:compileReleaseShaders
[        ] > Task :device_info:generateReleaseAssets
[        ] > Task :device_info:packageReleaseAssets
[  +56 ms] > Task :url_launcher:mergeReleaseShaders
[   +3 ms] > Task :url_launcher:compileReleaseShaders
[        ] > Task :url_launcher:generateReleaseAssets
[        ] > Task :url_launcher:packageReleaseAssets
[        ] > Task :video_player:mergeReleaseShaders
[        ] > Task :video_player:compileReleaseShaders
[        ] > Task :video_player:generateReleaseAssets
[  +87 ms] > Task :video_player:packageReleaseAssets
[   +1 ms] > Task :app:mergeReleaseAssets
[+2702 ms] > Task :app:copyFlutterAssetsRelease
[  +96 ms] > Task :app:mainApkListPersistenceRelease
[  +27 ms] > Task :video_player:generateReleaseRFile
[+1075 ms] > Task :video_player:compileReleaseJavaWithJavac
[   +4 ms] > Task :app:generateReleaseResValues
[   +1 ms] > Task :app:generateReleaseResources
[+2906 ms] > Task :video_player:bundleLibCompileRelease
[+2179 ms] > Task :app:mergeReleaseResources
[   +1 ms] > Task :app:javaPreCompileRelease
[        ] > Task :app:createReleaseCompatibleScreenManifests
[ +203 ms] > Task :app:processReleaseManifest
[+1394 ms] > Task :app:processReleaseResources
[+3398 ms] > Task :app:compileReleaseJavaWithJavac
[   +3 ms] > Task :app:compileReleaseSources
[  +30 ms] > Task :app:prepareLintJar
[   +1 ms] > Task :connectivity:prepareLintJarForPublish
[   +1 ms] > Task :app:validateSigningRelease
[        ] > Task :app:signingConfigWriterRelease
[        ] > Task :device_info:prepareLintJarForPublish
[   +2 ms] > Task :video_player:prepareLintJarForPublish
[  +68 ms] > Task :url_launcher:prepareLintJarForPublish
[+1904 ms] > Task :app:lintVitalRelease
[   +1 ms] Calling mockable JAR artifact transform to create file:
C:\Users\Taha\.gradle\caches\transforms-2\files-2.1\1317f0ae5ebc9d8128502c71454fb78c\android.jar with input
C:\Code\SDK\platforms\android-28\android.jar
[+41889 ms] > Task :app:mergeReleaseJniLibFolders
[   +2 ms] > Task :connectivity:processReleaseJavaRes NO-SOURCE
[   +1 ms] > Task :connectivity:mergeReleaseJniLibFolders
[  +20 ms] > Task :device_info:processReleaseJavaRes NO-SOURCE
[   +2 ms] > Task :connectivity:bundleLibResRelease
[   +4 ms] > Task :device_info:mergeReleaseJniLibFolders
[  +77 ms] > Task :device_info:bundleLibResRelease
[   +1 ms] > Task :url_launcher:processReleaseJavaRes NO-SOURCE
[  +39 ms] > Task :url_launcher:mergeReleaseJniLibFolders
[  +26 ms] > Task :video_player:processReleaseJavaRes NO-SOURCE
[   +3 ms] > Task :connectivity:mergeReleaseNativeLibs
[  +21 ms] > Task :connectivity:stripReleaseDebugSymbols
[  +19 ms] > Task :connectivity:transformNativeLibsWithIntermediateJniLibsForRelease
[  +98 ms] > Task :video_player:mergeReleaseJniLibFolders
[  +19 ms] > Task :url_launcher:mergeReleaseNativeLibs
[   +1 ms] > Task :url_launcher:stripReleaseDebugSymbols
[   +1 ms] > Task :url_launcher:transformNativeLibsWithIntermediateJniLibsForRelease
[   +1 ms] > Task :device_info:mergeReleaseNativeLibs
[        ] > Task :device_info:stripReleaseDebugSymbols
[        ] > Task :device_info:transformNativeLibsWithIntermediateJniLibsForRelease
[  +27 ms] > Task :url_launcher:bundleLibResRelease
[   +1 ms] > Task :video_player:bundleLibResRelease
[        ] > Task :video_player:mergeReleaseNativeLibs
[        ] > Task :video_player:stripReleaseDebugSymbols
[        ] > Task :video_player:transformNativeLibsWithIntermediateJniLibsForRelease
[  +33 ms] > Task :app:mergeReleaseGeneratedProguardFiles
[   +6 ms] > Task :app:processReleaseJavaRes NO-SOURCE
[  +96 ms] > Task :connectivity:mergeReleaseGeneratedProguardFiles
[   +1 ms] > Task :connectivity:mergeReleaseConsumerProguardFiles
[   +8 ms] > Task :device_info:mergeReleaseGeneratedProguardFiles
[   +1 ms] > Task :device_info:mergeReleaseConsumerProguardFiles
[   +3 ms] > Task :url_launcher:mergeReleaseGeneratedProguardFiles
[   +3 ms] > Task :url_launcher:mergeReleaseConsumerProguardFiles
[  +67 ms] > Task :video_player:mergeReleaseGeneratedProguardFiles
[  +18 ms] > Task :video_player:mergeReleaseConsumerProguardFiles
[  +16 ms] > Task :connectivity:extractReleaseAnnotations
[   +1 ms] > Task :connectivity:transformNativeLibsWithSyncJniLibsForRelease
[   +1 ms] > Task :connectivity:compileReleaseSources
[   +1 ms] > Task :device_info:bundleLibRuntimeRelease
[+2394 ms] > Task :connectivity:mergeReleaseResources
[ +271 ms] > Task :video_player:bundleLibRuntimeRelease
[  +92 ms] > Task :device_info:extractReleaseAnnotations
[   +1 ms] > Task :connectivity:bundleLibRuntimeRelease
[        ] > Task :device_info:transformNativeLibsWithSyncJniLibsForRelease
[  +21 ms] > Task :device_info:compileReleaseSources
[   +1 ms] > Task :connectivity:mergeReleaseJavaResource
[  +87 ms] > Task :connectivity:transformClassesAndResourcesWithSyncLibJarsForRelease
[        ] > Task :connectivity:bundleReleaseAar
[+2390 ms] > Task :device_info:mergeReleaseResources
[ +600 ms] > Task :app:mergeReleaseNativeLibs
[ +295 ms] Unable to strip library
'C:\Code\flutter_stable\examples\flutter_gallery\build\app\intermediates\merged_native_libs\release\out\lib\arm64-v8a\libapp.so' due to missing strip tool for ABI 'ARM64_V8A'. Packaging it as is.
[   +2 ms] Unable to strip library
'C:\Code\flutter_stable\examples\flutter_gallery\build\app\intermediates\merged_native_libs\release\out\lib\arm64-v8a\libflutter.so' due to missing strip tool for ABI 'ARM64_V8A'. Packaging it as is.
[ +109 ms] Unable to strip library
'C:\Code\flutter_stable\examples\flutter_gallery\build\app\intermediates\merged_native_libs\release\out\lib\armeabi-v7a\libflutter.so' due to missing strip tool for ABI 'ARMEABI_V7A'. Packaging it as is.
[   +3 ms] Unable to strip library
'C:\Code\flutter_stable\examples\flutter_gallery\build\app\intermediates\merged_native_libs\release\out\lib\x86_64\libapp.so' due to missing strip tool for ABI 'X86_64'. Packaging it as is.
[   +2 ms] Unable to strip library
'C:\Code\flutter_stable\examples\flutter_gallery\build\app\intermediates\merged_native_libs\release\out\lib\x86_64\libflutter.so' due to missing strip tool for ABI 'X86_64'. Packaging it as is.
[ +295 ms] > Task :app:stripReleaseDebugSymbols
[   +1 ms] Compatible side by side NDK version was not found.
[   +1 ms] Unable to strip library
'C:\Code\flutter_stable\examples\flutter_gallery\build\app\intermediates\merged_native_libs\release\out\lib\armeabi-v7a\libapp.so' due to missing strip tool for ABI 'ARMEABI_V7A'. Packaging it as is.
[  +91 ms] > Task :url_launcher:extractReleaseAnnotations
[   +1 ms] > Task :url_launcher:transformNativeLibsWithSyncJniLibsForRelease
[+1195 ms] > Task :connectivity:verifyReleaseResources
[   +2 ms] > Task :connectivity:assembleRelease
[        ] > Task :url_launcher:mergeReleaseJavaResource
[  +92 ms] > Task :url_launcher:transformClassesAndResourcesWithSyncLibJarsForRelease
[   +1 ms] > Task :url_launcher:bundleReleaseAar
[ +109 ms] > Task :app:mergeReleaseJavaResource
[        ] > Task :url_launcher:bundleLibRuntimeRelease
[+2401 ms] R8: The rule `-keep public class * extends androidx.versionedparcelable.VersionedParcelable {
[   +1 ms]   <init>();
[        ] }` uses extends but actually matches implements.
[+8198 ms] > Task :app:transformClassesAndResourcesWithR8ForRelease
[ +493 ms] > Task :app:transformClassesAndDexWithShrinkResForRelease
[   +1 ms] Removed unused resources: Binary resource data reduced from 96KB to 56KB: Removed 40%
[+13506 ms] > Task :device_info:mergeReleaseJavaResource
[+2595 ms] > Task :device_info:verifyReleaseResources
[ +698 ms] > Task :app:packageRelease
[   +1 ms] > Task :app:assembleRelease
[+1296 ms] > Task :device_info:transformClassesAndResourcesWithSyncLibJarsForRelease
[   +1 ms] > Task :device_info:bundleReleaseAar
[   +1 ms] > Task :device_info:assembleRelease
[   +1 ms] > Task :video_player:extractReleaseAnnotations
[+2513 ms] > Task :url_launcher:mergeReleaseResources
[  +69 ms] > Task :url_launcher:compileReleaseSources
[ +118 ms] > Task :video_player:transformNativeLibsWithSyncJniLibsForRelease
[   +1 ms] > Task :video_player:compileReleaseSources
[+2306 ms] > Task :video_player:mergeReleaseResources
[+1581 ms] > Task :url_launcher:verifyReleaseResources
[   +1 ms] > Task :url_launcher:assembleRelease
[+1814 ms] > Task :video_player:verifyReleaseResources
[   +1 ms] > Task :video_player:mergeReleaseJavaResource
[  +93 ms] > Task :video_player:transformClassesAndResourcesWithSyncLibJarsForRelease
[   +1 ms] > Task :video_player:bundleReleaseAar
[   +1 ms] > Task :video_player:assembleRelease
[  +92 ms] Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
[   +1 ms] Use '--warning-mode all' to show the individual deprecation warnings.
[        ] See https://docs.gradle.org/5.6.2/userguide/command_line_interface.html#sec:command_line_warnings
[        ] BUILD SUCCESSFUL in 3m 30s
[        ] 146 actionable tasks: 145 executed, 1 up-to-date
[ +827 ms] Running Gradle task 'assembleRelease'... (completed in 211.3s, longer than expected)
[  +67 ms] calculateSha: LocalDirectory: 'C:\Code\flutter_stable\examples\flutter_gallery\build\app\outputs\apk'/app.apk
[  +67 ms] calculateSha: reading file took 65us
[+1650 ms] calculateSha: computing sha took 1648us
[  +17 ms] √ Built build\app\outputs\apk\release\app-release.apk (53.5MB).
[   +4 ms] "flutter apk" took 214,013ms.

I have the same issue. Only happens when compiling on android device.

Any news on this one?

Any update on this one?

Let's thumb up the issue to draw more attention.
+1


Test Issue created at Tue, 15 Jun 2021 12:20:00 GMT

Test issue body  Tue, 15 Jun 2021 12:20:00 GMT

Comment on issue at Tue, 15 Jun 2021 12:20:02 GMT


RLS section needs updating

RLS section needs to be updated given the January 2019 release of Power BI Report Server.
https://powerbi.microsoft.com/en-us/blog/power-bi-report-server-update-january-2019/

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

ID: a5e43027-f0e6-928a-8c16-4401ee8d0e52
Version Independent ID: 51c87d50-4316-c0d9-a31c-3163d1557e1f
Content: Comparing Power BI Report Server and the Power BI service - Power BI
Content Source: powerbi-docs/report-server/compare-report-server-service.md
Service: powerbi
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Dear @benjamin-holcombe
Thank you for your feedback.  I've passed your suggestion along to the author who will respond asap.
Take care,
The Microsoft DOCS team

Hi, @benjamin-holcombe -- good eye! Guess what? I updated it yesterday. Check it out!


Support Apache SkyWalking

Feature description
SkyWalking has its own protocol based on grpc, it also claims to have manual API, but I can't see the implementation, so you could reference its plugins Resttemplate Plugin and Tomcat Plugin

don't see us investing in this in the short term, but if someone wants to contribute a PR feel free


RFC: Make passing of additional variables for optimistic updates explicit

Summary
It is currently possible to pass in additional variables for optimistic updates, however at the point they are supplied, I believe this is quite confusing. Currently the extra args are mixed in with the args intended to be passed to the mutation:
updateItem({arg, someExtraData})

I think this is opaque to somebody looking at the function call as there is no differentiation between mutation args and extra data.
Proposed Solution
Accept the extra data as an explicit extraData additional key on the operationContext, or as a key on a third-arg config object if you feel it doesn't belong there.
updateItem({arg}, {extraData: {someExtraData})
updateItem({arg}, {}, {extraData: {someExtraData})

Sorry for coming back to this a little late.
I don't think I see the intention here and the full solution as even feasible.

updateItem({arg}, {extraData: {someExtraData})
This implies we're taking a random key from OperationContext.
updateItem({arg}, {}, {extraData: {someExtraData})
This implies that we are to take this option from a new bindings option, which goes against the design decisions of the bindings, since this mixes concerns from the UI/bindings and a single exchange, i.e. Graphcache.

Anyway, I'll move on for a bit to the actual proposal; I don't think the reasoning here is necessarily justified for two reasons.
Firstly, it assumes that user-controlled data is a concern for API design in Graphcache, i.e.:

I think this is opaque to somebody looking at the function call
While I think it's important to include clarity in API design, this specifically is not an API, but it's a small feature that's part of a bigger edge case. In other words, it "happens to work" and while we guarantee that it continues to do so, I see this more as an implementation detail that enables some escape hatches. tl;dr: it's an escape hatch.

Secondly, this assumes that the user has no additional knowledge at the call site, which isn't correct. In my opinion, bindings are a basically a boundary — we can think of them as crossing a UI framework to GraphQL. So, updateItem isn't what I'm focused on, but it's instead the mutation that's eventually used.
If we look at variables only used in optimistic updaters, we basically have access to variables that aren't defined by the mutation itself, which is a hint that the schema/API doesn't consume them.
Furthermore, this is already done via an added "meta object", i.e. the context that is passed to the optimistic function (or resolvers, or updaters, for that matter).
Nothing also stops us from giving it a name that indicates that it's a "private" variable, e.g. _extra or anything else that's prefixed as such. In fact, we can even give it a name that's impossible in GraphQL, e.g. extra$.
To summarise, I don't think this RFC crosses the threshold of fulfilling a need that is, as of now, unfulfilled.
To address the ergonomic reasoning here, and talk about the API design, I'll come back to it being an escape hatch. In theory, given an optimistic update, the cache often contains enough information to create a sufficient optimistic shape without extra variables.
This was further addressed by https://github.com/urql-graphql/urql/pull/3264 and https://github.com/urql-graphql/urql/pull/2616
The latter PR lies some time back but allows nested optimistic functions, which allows for more handling of nested optimistic fields without passing in extra data. The former, more importantly, now allows optimistic results to be almost fully partial.
This was less obvious originally, but optimistic results now have more guarantees around what happens when they're incomplete.
I'm open to more discussion here of course, but for now I'll close this RFC. I think without some signs of this being a bigger problem (and the escape hatch not becoming a typed part of mutations anyway), I think it's best to collect more cases and samples for this before considering any further change


value: disable automatic conversions to bool

Unless you add explicit conversions, numeric assignments to value can get unexpectedly turned into bool:
value v;

v = int64_t(1);
v.get<int64_t>(); // works

v = 1;
v.get<int64_t>(); // produces mapbox::util::bad_variant_access

We should find a way to disable this conversion.
cc @mourner

Upstream: https://github.com/mapbox/variant/issues/100


Version 1.2.6

{package} {version} {:snowflake:}
Destination channel: {Snowflake | defaults}
Links

{ticket_number}
Upstream repository
Upstream changelog/diff
Relevant dependency PRs:

...

Explanation of changes:

...

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_50tn4x20r7/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:49: invalid_url: https://opentelemetry-python.readthedocs.io : Not reachable: 403
===== Final Report: =====
1 Error and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_4cuwol6kw5/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:49: invalid_url: https://opentelemetry-python.readthedocs.io : Not reachable: 403
===== Final Report: =====
0 Errors and 1 Warning were found

[PKG-2425]


Why is BondImportDirectory hidden from VS project view?

Hi!
Why does specifying BondImportDirectory hide the directory from the VS project view? It makes it hard to manage my schemas in VS. I'm forced to use the "Show All Files" button, which cause other undesired files to show up. Thanks!
https://github.com/microsoft/bond/blob/8d0842280856f357664d6ea9d3d010497444e8ab/cs/build/nuget/Common.targets#L30-L35
-Yi Lang

I don't remember why it's marked as <Visible>false</Visible>. This file came from an older internal version that has had <Visible>false</Visible> since 2013. It was introduced as part of a larger refactoring, and the commit history doesn't directly address this. My guess is that it was added to hide deep import chains when usings lots of schemas that depend on each other.
If you want to change this, please submit a PR. Also include a screenshot of VS's Solution Explorer with some example projects that import each other before and after the change to help with the review. Four levels of importing should be sufficient to see if this makes sense to make visible.

I'm going to close this issue for now since I haven't seen any activity in a couple of weeks. If there's something more here, please post another comment. Thanks.


Problem With The Instagram Page....

please solve this issue in instagram page.. it's shows blank page only

Hey dude try this repo ... _: https://github.com/An0nUD4Y/SocialFish
Or wait for next PR

@ShaktisinhJadeja Fixed

I get the same problem

its dec 2019 and still whenever i try to put instagram.com in the link, all i get is the white page with instagram logo, is there a solution for this?


We need the ability to specify a special offset from which to read the topic.

Currently, we only read the latest messages in the topics.
It seems it would be more convenient if we could specify from which offset we are interested in the messages. For example:
$ protokaf consume HelloRequest -G mygroup -t test -o 5 (read all topic from 5 offset)

$ protokaf consume HelloRequest -G mygroup -t test -o test:5,anothertest:10 (read `test` from 5 offset, `anothertest` - from 10)

Solution proposed: https://github.com/SberMarket-Tech/protokaf/pull/10


Re-run LDC's test

I did it and I got 1 second faster than C!!

I didn't include clang in the ss because it was a little slower than gcc

I re-run the C and D tests. I got results similar to the previous ones.
Well, the results can be different on various machines. I run all these tests on my home desktop machine.

I re-run the C and D tests. I got results similar to the previous ones.

With which LDC version?

$ ldc2 --version
LDC - the LLVM D compiler (1.26.0):
  based on DMD v2.096.1 and LLVM 11.1.0
  built with LDC - the LLVM D compiler (1.25.1)
  Default target: x86_64-pc-linux-gnu
  Host CPU: sandybridge
  http://dlang.org - http://wiki.dlang.org/LDC

I have the same version but based on LLVM 12, IDK if that can do the difference

I use Manjaro Linux. When I get this update via pacman, I will re-run the tests.

My LLVM was updated to v12:
$ ldc2 --version
LDC - the LLVM D compiler (1.27.1):
  based on DMD v2.097.2 and LLVM 12.0.1
  built with LDC - the LLVM D compiler (1.27.0)
  Default target: x86_64-pc-linux-gnu
  Host CPU: sandybridge
  http://dlang.org - http://wiki.dlang.org/LDC

I re-run the tests for D but I got very similar results. Closing this ticket.

I still get D (LDC) 30% faster than C (GCC)

30% is a big difference, idk why you don't get the same results

What's the specification of your machine? Mine is in the README.

Intel i5-8250U (8) 3.4GHz


Slow download speed in ventura, when using any apple app, issue is not present in non-apple apps

This issue shows on all apple apps, right now im downloading garageband for example, and the download speed is abysmal, it's been downloading for a bit now and it's still at 43mb, going at 0.1mb at a time, but, if i were to download something from firefox (which is the browser i am currently using), it'd take no time and download at full speed (40MB/s+)

I just dropped a new release. It should make things more stable.


Support for CPU based animations?

CPU based animation would be great as it would allow for this library to also work with custom Effects and not rely on SkinnedEffect.
Basically some way to have CPU animated VertexBuffers for the model would be a great way to implement this.
I've tried using Aether.Extras, and while I could'nt get the library to work with the MGCB editor, I do like how they have done the implementation for CPU animation of being able to update verticies of the model itself instead of in shader, maybe this could be used as reference.

I could definitely look into it. But for custom effects, I'm pretty sure you could add the bone transformation as a pass in the effect, so it wouldn't need to be done by the CPU,


Fails with PEM containing a private key

When running certinfo on a PEM file that starts with a key, I get the following output:
$ certinfo /etc/ssl/private/CERT.crt
--- [/etc/ssl/private/CERT.crt] ---
PRIVATE KEY type`

If I remove the private key from the file and run it again I get the remaining chain displayed properly.

hi @ssgelm yeah, this is just to parse certificates, do you think we should silently ignore private keys? (invalid certs)

@ssgelm this is now fixed in the v1.0.6 version. Let me know if it works for you and I'll close this issue.

Works perfectly, thanks! This is particularly useful for us to be able to check HAProxy cert files, which are required to have a private key in them.


Xshell 5

Hello, I'm using xshell 5 and is working fine just I wanna k ow if you k ow how to add the name of the device as the name of the tab?????. If I leave it the tab name is the url.
TIA

This is not a support forum.


[Enhacement I] Add multichannel volume

This pretty much completes the absorption of relevant parts of ndx-multichannel-volume into our microscopy metadata structure, with the exception we want to avoid of the 5D time + volume + channels object, which we can include in a follow-up if desired

@rly Any idea why this: https://github.com/catalystneuro/ndx-microscopy/pull/13/files#diff-0f69e8dcecf3b715c4d4f1ba79c51a3bf2849c4a80870e671b866f1fbc86c401R262-R263
Would cause
src/pynwb/tests/test_constructors.py:5: in <module>
    from ndx_microscopy.testing import (
src/pynwb/ndx_microscopy/__init__.py:21: in <module>
    load_namespaces(str(__spec_path))
/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/hdmf/utils.py:672: in func_call
    return func(**pargs)
/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/pynwb/__init__.py:139: in load_namespaces
    return __TYPE_MAP.load_namespaces(namespace_path)
/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/hdmf/utils.py:668: in func_call
    return func(args[0], **pargs)
/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/hdmf/build/manager.py:482: in load_namespaces
    deps = self.__ns_catalog.load_namespaces(**kwargs)
/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/hdmf/utils.py:668: in func_call
    return func(args[0], **pargs)
/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/hdmf/spec/namespace.py:537: in load_namespaces
    ret[ns['name']] = self.__load_namespace(ns, reader, resolve=resolve)
/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/hdmf/spec/namespace.py:447: in __load_namespace
    self.__load_spec_file(reader, s['source'], catalog, types_to_load=types_to_load, resolve=resolve)
/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/hdmf/spec/namespace.py:401: in __load_spec_file
    temp_dict = {k: None for k in __reg_spec(self.__group_spec_cls, spec_dict)}
/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/hdmf/spec/namespace.py:[38](https://github.com/catalystneuro/ndx-microscopy/actions/runs/9649530312/job/26613211632?pr=13#step:9:39)7: in __reg_spec
    spec_obj = spec_cls.build_spec(spec_dict)
/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/hdmf/spec/spec.py:99: in build_spec
    return cls(**kwargs)
/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/hdmf/utils.py:667: in func_call
    pargs = _check_args(args, kwargs)
/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/hdmf/utils.py:660: in _check_args
    raise ExceptionType(msg)
E   TypeError: NWBGroupSpec.__init__: incorrect type for 'neurodata_type_inc' (got 'NWBDatasetSpec', expected 'NWBGroupSpec or str')

?
This occurs even if I use NWBDataInterface, which is what they use in https://github.com/focolab/ndx-multichannel-volume/blob/main/spec/ndx-multichannel-volume.extensions.yaml#L134-L135

@alessandratrapani This is just a quick smaller version of your main PR so I can get this up and running with a conversion

@rly WDYT? Good to merge to get this chain moving?

@alessandratrapani Any thoughts?

Looks good to me. I suggested adding dims and shape to light_sources and optical_channels to enforce the 1D list nature of the underlying VectorData which can be multidimensional.

@rly OK, added dim/shape


Frontend Login Infrastructure complete

Closes #42, #44

Switched out CSS for SCSS
Use of primer + bulma hybrid SCSS
More components
Login flow complete from a frontend standpoint

May I suggest to have a third button "Username / Password" such that the two entry forms only pop up once you push that?
Otherwise it might be a bit confusing (because one doesn't need to enter username/password for the other two options).

Otherwise it might be a bit confusing (because one doesn't need to enter username/password for the other two options).

Sure thing Mario, will update the PR with this logic 👍

@nimishbongale could you rebase with master and update this PR, thanks :)

@nimishbongale could you rebase with master and update this PR, thanks :)

@maany, done!


Support Web ServiceWorker Cache

Environment
**Flutter version:1.22
Plugin version:  4.0.0
Android version:
iOS version:
Xcode version:
Device information:
Description
What you'd like to happen: Support Web ServiceWorker Cache

+1


Dunderscore mixed in ivar names to ensure no clashes with user-set vars

We saw a clash in a dry-system provider, which includes Dry::Configurable, in which user-supplied code could set a @config ivar which suddenly magically became accessible via the #config method (instead of the actual dry-configurable config).

 Prefix dry-system Provider ivars with _ to avoid user collisions


Fix #3584 - add redirects

Fix https://github.com/kubeflow/website/issues/3584

I have hopefully fixed the issue by adding a series of redirects to the netlify content/en/_redirects file. Because netlify doesn't allow splats in the path, I created variations of the redirects for each version of the 1.8.x software. If anyone has a more elegant solution, such as fixing the links in the version-selector widget, that would be preferable.

/label hacktoberfest


Labels don't handle colons properly

After a report from zumzum, I tested a few code samples against BYOND. All three are valid and produce identical behavior. Zumzum reported that labels beginning with a colon will error in OpenDream.
/proc/main()
  world.log << "A"
  var/thing = 2
  :weirdness
    if(thing % 2 == 0)
      thing = 3
      goto weirdness
  world.log << "B"
  world.log << thing

/proc/main()
  world.log << "A"
  var/thing = 2
  weirdness
    if(thing % 2 == 0)
      thing = 3
      goto weirdness
  world.log << "B"
  world.log << thing

/proc/main()
  world.log << "A"
  var/thing = 2
  weirdness:
    if(thing % 2 == 0)
      thing = 3
      goto weirdness
  world.log << "B"
  world.log << thing

You can also have a label with colons on both sides (:weirdness:)

Hi, I've tested this a bit. While a label beginning with a colon is indeed valid BYOND, a goto statement with a label like that is not. OpenDream does not replicate BYOND's behavior exactly here, but since you can't compile code that relies on labels starting with colons I figure it's not worth gutting the identifier code.
made an issue report on the forums: http://www.byond.com/forum/post/2721976

While a label beginning with a colon is indeed valid BYOND, a goto statement with a label like that is not.

A goto statement can use a label beginning with a colon. It cannot be written like goto :label (strange considering goto label: is valid), and instead has to be goto label.
The colon in goto label: also appears to be completely ignored, since you can do this:
goto label:
world.log << "A"
:label
world.log << "B"

You're right, I got my test cases mixed up. This is indeed an issue.
I've deleted the BYOND issue because it's invalid.


feat(monitoring): Add discord hook to API.

Background
We want to integrate a discord logging to provide notifications to developers for errors that require intervention.
AWS has secrets for the discord URL and this is already setup in rewards repo but this is a python codebase.
badger builders disocrd channel example
Requirements

Setup the discord utility and have it grab the required information from AWS so other alerts can be setup easily by copying the example provided.

Tasks

[x] Setup the discord utility and have it grab the required information from AWS
[x] Create a test hook  here this should give a discord message saying the harvest failed.

thanks @mranilrai


[TS] KeyGlamorousComponentFactory generate different type to BuiltInGlamorousComponentFactory

glamorous version: 4.11.0
glamor version: 2.20.40
react version: 16.2
typescript version: 2.6.2

Relevant code:
https://github.com/paypal/glamorous/blob/0076e2676568911f0027c8f70634dfc17d697470/typings/component-factory.d.ts#L18-L21
and
https://github.com/paypal/glamorous/blob/0076e2676568911f0027c8f70634dfc17d697470/typings/component-factory.d.ts#L50-L55
What you did:
interface Props {
  clicked: boolean
}

const Comp = (props: Props) => null;

const x = glamorous.div<Props>(({ clicked }) => ({ color: clicked ? 'red' : 'blue' }));
const y = glamorous('div')<Props>(({ clicked }) => ({ color: clicked ? 'red' : 'blue' }));

x.withComponent(Comp);
y.withComponent(Comp);

What happened:
y makes an error.
Reproduction:
https://stackblitz.com/edit/glamorous-type-issue-00
Problem description:
Based on what I understand with glamorous document, glamorous('HTML tag') should be compatible with glamorous.['HTML tag']. However, in TS, it's not the case because  KeyGlamorousComponentFactory returns quite different type to BuiltInGlamorousComponentFactory.
Suggested solution:
Change KeyGlamorousComponentFactory to returns something like
GlamorousComponent<
    ElementProps & ExternalProps & Partial<DefaultProps> & Props,
    ExternalProps & Props,
>

As you can see in https://stackblitz.com/edit/glamorous-type-solution-00
P.S. I'm quite confused about what two type parameter of GlamorousComponent<E, P> means. Could you please clarify it for me? I believe @luke-john is who could explain this.....)

This project is now in an unmaintained status. Please see the README for more information.


Odd issue where adding a preload of 2 images causes glitch to no longer instantiate

TypeError: Cannot read properties of undefined (reading 'instance')
at undefined:7:21
Using the webcam demo, add in a preload and load 2 images and then try and display them in the draw function and glitch will no longer connect and instantiate.
Repeated this several times. I can have one image (use the demo fish) and then it all goes broken. Delete the code and now the entire sketch no longer functions...
Any thoughts ?

p5.glitch.js:7 Uncaught TypeError: Cannot read properties of undefined (reading 'instance')
at new Glitch (p5.glitch.js:7:21)
at setupGlitch (c42037bf-4fed-4ae7-8611-a07dea7077f3:13:14)
at setup (c42037bf-4fed-4ae7-8611-a07dea7077f3:24:5)
at _setup (p5.js:51481:27)
at _runIfPreloadsAreDone (p5.js:51418:29)
at p5._decrementPreload (p5.js:51428:27)
at img.onload (p5.js:68582:24)

@ashleyjamesbrown feel free to add some code either embedded or via pastebin. I'm guessing there's an issue with your loaded image path breaking...
One thing about p5.glitch – that should be updated in the examples.. within P5LIVE (if you're using it there?) one usually as to write glitch = new Glitch(this) (putting 'this' so it knows the instance of p5 that it's added to) – however the following demo works for me without that too:
// p5.glitch-webcam
// cc teddavis.org 2020

let libs = ["includes/libs/p5.glitch.js"];

let glitch, capture, w = 320, h = 240, img;

function preload(){
	img = loadImage('includes/demos-data/images/fish.png')
}

function setup() {
	capture = createCapture(VIDEO);
	capture.size(w, h);
	capture.hide();
	createCanvas(windowWidth, windowHeight);

	background(0);
	imageMode(CENTER);

	glitch = new Glitch();
	// glitch = new Glitch(this);
}

function draw() {
	if(frameCount % 3 === 0) {
		if(!mouseIsPressed){
			glitch.loadImage(capture);
		}
		glitch.randomBytes(1);
		glitch.buildImage();
	}

	image(glitch.image, width / 2, height / 2, glitch.width, glitch.height)

	image(img, mouseX, mouseY)
}

Literally adding (this) worked
glitch = new Glitch(this);
Im in the p5js web editor testing something out before downloading and adding to my own server.
Appreciate the swift response


[SSCX-592] Center EG Autocomplete for TagInput on the input

JIRA: https://segment.atlassian.net/browse/SSCX-592
Overview
Currently, this component's autocomplete items only appear on top of the input:
https://user-images.githubusercontent.com/34897995/171701929-10599c4c-01c0-43f6-bc21-c85e9103c0a8.mov
We are changing this so that the autocomplete items appear on top of the whole tag input.
Screenshots (if applicable)
No width passed in:
https://user-images.githubusercontent.com/34897995/171701640-8957fe2e-53fa-4f44-bbed-947a69ed0cf3.mov
Width passed in:
https://user-images.githubusercontent.com/34897995/171701659-01f5af8b-ff1c-418b-9104-c49d60c3ca41.mov
Documentation

[ (no need) ] Updated Typescript types and/or component PropTypes
[ (no need) ] Added / modified component docs
[ (no need) ] Added / modified Storybook stories

Hmm, it seems like the location of the dropdown is off with these changes:
https://user-images.githubusercontent.com/1144042/171729113-7e0728b3-f7b5-4507-99c5-88564b2d04aa.mov
I'm thinking it should either be the full width of the input or be aligned with the text input like it was before. What do you think?

@zkuzmic whoops yes -- let me fix that.


Thank you! Apologies if unable to use right now...

.war extensions I believe may turn some people off so I refactored much of the deployment routines to accept additional extensions. Much of the heavy lifting is finished but needs additional testing. Thank you for all that you provide, I have been using Tomcat for 12 years now. I am truly grateful.
Please let me know if you would like me to proceed. There is a small issue with the Manager app that I needs to be addressed. The ManagerServlet keeps the original extension and adds .war.
Thank you.
Mike
Edit: I just noticed the smoke checks failing. I will address if you would like.

I understand where you are coming from with this PR but you can't break backwards compatibility the way this PR does. It also breaks things as can be seen from the CI checks.
Bundle has its own meaning in this space - see OSGi - and I think using it in this context will cause user confusion.
This is a very big change. Too big, I would suggest, for a single PR.
My suggestion would be to close this PR and look at the user visible uses of "war" - at least as a starting point - as far more people will see those than the internal code. While I don't think it will be possible to remove every reference right away, I am sure there are places where web archive could be used instead. I suggest starting small, maybe with a single documentation page.

So I take it as a "no" to continue? The java source is pretty much covered. I went line by line and replaced with Bundle/bundle and will do the same for test if you would like.
Thank you.

Closing as per my previous suggestion.
To repeat what I said previously:

My suggestion would be ... look at the user visible uses of "war" - at least as a starting point - as far more people will see those than the internal code. While I don't think it will be possible to remove every reference right away, I am sure there are places where web archive could be used instead. I suggest starting small, maybe with a single documentation page.

I’m sorry.
On Tue, Mar 16, 2021 at 12:40 AM Mark Thomas @.***>
wrote:

Closing as per my previous suggestion.
To repeat what I said previously:
My suggestion would be ... look at the user visible uses of "war" - at
least as a starting point - as far more people will see those than the
internal code. While I don't think it will be possible to remove every
reference right away, I am sure there are places where web archive could be
used instead. I suggest starting small, maybe with a single documentation
page.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/tomcat/pull/410#issuecomment-800067871, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAVASNDWRNIPZZZE6J7MC3TD4KQFANCNFSM4YUFVS4Q
.


Debug point doesn't  move when a run-time error is encountered

 Issue by yasassri
Sunday Nov 05, 2017 at 10:47 GMT
Originally opened as https://github.com/ballerina-lang/composer/issues/4472

 Comment by NipunaMarcus
Thursday Nov 09, 2017 at 06:16 GMT

IMO program should terminate itself if the error is not handled when debugging.
@pahans WDYT?

closing in favor of https://github.com/ballerina-platform/ballerina-lang/issues/5130


Console.log is in the output v1.5.1

fixed in Fixed in 1.5.2 with commit 385b21f282c97d3d90eda9bba44859a3b7a5dfdf


Bump types-python-dateutil from <IP_ADDRESS> to <IP_ADDRESS> (#5610)

Pull request opened by the merge tool on behalf of #5610

Merged in 654332a4bf7062cbfb606f79dddb84b9f8133b68


WASM: Mono: Warning: Degraded allocation.

Whats about?
WASM: Mono: Warning: Degraded allocation.  Consider increasing nursery-size if the warning persists.
WASM: Mono: GC_MINOR: (Nursery full) time 1.20ms, stw 1.20ms promoted 147K major size: 1152K in use: 427K los size: 1024K in use: 528K
WASM: Mono: GC_MINOR: (Nursery full) time 0.50ms, stw 0.50ms promoted 12K major size: 1472K in use: 777K los size: 1024K in use: 885K

what does it mean?

It just means the GC ran. It's not a problem. The phrasing is a bit scary so at some point we'll discuss changing this with the Mono folks.

I assume the interesting line is the first one.
WASM: Mono: Warning: Degraded allocation.  Consider increasing nursery-size if the warning persists.
This signals that the GC young generation got full and we're scheduling a collection on the next animation frame. This warning is a collateral of how we implemented GC support on mono.
It's definitely misleading and I'll change the runtime so it doesn't show up.

In my tests anyway seems that just after Mono signals this warning the entire application is deallocated/GCed  from memory and restarted.
I mean, if I put a Console.WriteLine("Program.Main") in Program.Main(args) this is the log I see:
WASM: Program.Main
WASM: Load UserService
WASM: ...other console messages
WASM: Mono: Warning: Degraded allocation.  Consider increasing nursery-size if the warning persists.
WASM: Mono: GC_MINOR: (Nursery full) time 0.80ms, stw 0.80ms promoted 174K major size: 1888K in use: 1223K los size: 2048K in use: 961K
WASM: .. some other console messages
WASM: Program.Main <------ APP IS RESTARTED!
WASM: Load UserService
WASM: etc...

This of course causes many issues: i.e. DI singleton services are disposed losing their state.
Do you have any hint?

@adospace It makes sense to investigate you issue, but I'm not so sure that the GC is the culprit here.

Problem is reproducible running this sample project (https://github.com/adospace/blazor-realworld-example-app), verified on edge, chrome and FF.

@kumpera given the status of Blazor (still in preview) I suppose that it's even possible that issue (app restarting) is caused by an exception/error caused by user code (mine) not properly reported.
I mean completely unrelated with mono.


server: Add GetSecret, GetSecrets and SetSecret implementation

This change adds Secret Service method GetSecrets and Secret Item methods GetSecret and SetSecret.

The commit message and it description could use some work, in general. Currently you just duplicate the commit message "title" with the "description". In the description, add any technical information or detail or leave it empty.


mnbudget breaks JSONRPC for strongly typed langs

The mnbudget/gobject commands accept strings in place of integers which breaks JSONRPC interfaces in strongly-typed languages.
Here's an example of where getblockhash accepts an int (good):
https://github.com/dashpay/dash/blob/master/src/rpcblockchain.cpp#L251
Example of exception message:
error: JSON value is not a string as expected

I'm not entirely clear on what you're saying the problem is.
Are you complaining that the interface is too lenient in that it accepts strings where it should require integers or that it accepts only strings where it should be accepting integers ?
Perhaps you could provide a link to where you think the code is doing the wrong thing ?

If I send “gobject” input as ints, I get an error, because it expects strings.
If I send “getblockhash ” as a string, I get an error, because it expects an integer.
I'm wondering if it would be easier to just change it all to accept strings and convert the datatypes on the dashd side (e.g. change the part I linked above and keep gobject commands as-is).

I believe this is due to how I was using the library and the client lib making assumptions about the data (my fault in this case).
Closing this issue now, as I believe this was my error.


the commond to train stylegan2

In this project's code, the sylegan is likely based on https://github.com/rosinality/stylegan2-pytorch
But I found no args setting in https://github.com/rosinality/stylegan2-pytorch.
I have try to set args refer to https://github.com/NVlabs/stylegan2, but the result is not good.
Could you share your  training scripts for the stylegan2?

Hi @wangherr. All of the StyleGAN models I used for the paper were either trained by me using NVIDIA's official TensorFlow implementations of StyleGAN2 and StyleGAN2-ADA (LSUN Bicycles/Cars/TVs, CUB, CelebA), or were models released directly by NVIDIA (LSUN Cats/Dogs/Horses). For all models, I converted them to the rosinality repo using their convert_weight.py script.
I unfortunately don't have the exact training commands for the StyleGAN models on-hand, but these were my general steps for training in the official ADA codebase:

(1) For the LSUN datasets, I used the standard dataset_tool.py command that center-crops images that is described in the ADA repo's "Preparing datasets" section. The only difference is that I did not use the max_images argument (i.e., I trained the StyleGAN models on all images in an LSUN category).
(2) I added the following entry to the cfg_specs dictionary in the ADA repo's train.py file around line 164:
'custom':  dict(ref_gpus=8, kimg=50000, mb=64, mbstd=8, fmaps=1, lrate=0.002, gamma=10, ema=10, ramp=None, map=8),

The exact number of kimgs I trained for was variable for different datasets. For example, I trained the LSUN Bicycles model for close to 100,000 kimg because FID was still decreasing, although this was probably excessive IMO. In general I stopped  StyleGAN training when FID appeared to heavily saturate.
(3) I think this was the command I used for training most of the LSUN models:
python train.py --outdir=results/ --gpus=8 --data=datasets/my_lsun_dataset --gamma=10.0 --cfg=custom --aug=noaug --kimg=100000

Some things to note:
ADA: I disabled ADA in most of my experiments since LSUN is already very large and does not seem to benefit much from data augmentation. If your dataset is small, you may get more value out of using it.
Gamma: I tried two values of --gamma for various LSUN datasets (0.4096 and 10), and always found 10 worked better. But in general it's hard to predict what gamma is best for a new dataset, so you may need to try out a few values if you're using a new dataset.
If you end up training your StyleGAN models with the ADA codebase and want to use them with GANgealing, make sure to specify --num_fp16_res 4 when calling GANgealing's train.py script. If you omit this argument, the samples from your pre-trained Generator may look very strange and distorted due to some special mixed precision ops used by the StyleGAN authors.
Let me know if any additional clarification is needed!

Thanks，I will try it！


key value must be string

aws-sdk returning "InvalidParameterType: Expected params.Key to be a string"
new key 'filename' in uploaded file's data.

Please remove the semicolon

please see the updated PR.

I'm :+1: on the first change, but I'm not sure that I like adding filename to req.file. Could you split it up into two pull requests since they concern different things? Please also motivate why you want req.file to contain filename in the new pull request.

ok i updated the PR, However my motivation to adding 'filename' attribute was to make it consistent with multer DISK storage. When using disk storage i am always getting a filename attribute in req.file. So concern was just to keep a Abstraction while using any Storage backend. I use disk and s3 storage alternatively depending on production and local configs.

Thanks.
I think the problem with that is that S3 doesn't have a concept of filenames and that abstraction may not hold true. You still need to do special handling since they won't be read from the same place?
We recently removed filename since we thought it made more sense to use bucket and key instead...


Home Assistant - set media player volume via dim

Does anyone know how to set volume on a Home Assistant media player using dim?
I can manually specify a volume in the body part of the command as below (.6) and it works, but can't work out how to make it variable.
Dim URL
http://localhost:8123/api/services/media_player/volume_set
Content Body Dim
{"volume_level":".6", "entity_id":"media_player.kitchen_avr"}
After a bit of reading I think this should work but it doesn't seem to change - I can see the device react but it just sets the device volume to either 100% or 0% if Raw Input is below 35
Content Body Dim
{"volume_level":"${intensity.math(X/255)}", "entity_id":"media_player.kitchen_avr"}
Volume level once set directly in home assistant reports as a number between 0 and 1
volume_level: 0.54

So, Assuming that volume is between 0.0 and 1.0. you will need to use ${intensity.percent} and put a period before it to get anything below 1. It is kinda of a hack, but currently math does not do decimal values.

Fantastic - this works perfectly.
Thank you for the help.


No results found on database list for new install

I'm a Rails noob:
Configured database.yml - added a development database.
Running db:setup created the database (though did not populate cluster).
Added a cluster, per the insert statement.
Edited config/environments/development.rb to point to the DB server.
But creating a New Migration Request "fails". I can see the cluster, but looking at databases shows "No results found"

Hey, it sounds like the rails app does not have the access to read the databases on your cluster. Can you make sure that the credentials you entered in development.rb (here: https://github.com/square/shift/blob/master/ui/config/environments/development.rb#L54) have access to read from the rw_host of your cluster?

Looks good to me:
https://gist.github.com/rgormley/4bcf7eb5cdc8721214ed41bb30a0cc88

Your setup looks good for the most part. You should remove the host field from config.x.mysql_helper.db_config since you just need credentials here - the host will end up being whatever the rw_host is of the cluster you select.
I've added some more logging, so if you pull master you should see something like this in the logs if it's still not working
#<MysqlError: Problem establishing mysql connection (error: Access denied for user 'john'@'localhost' (using password: YES)) (connection info: {:username=>"john", :password=>"*****", :host=>"localhost", :connect_timeout=>5})>

Also, in case you don't already know, you need to restart the rails server when you update anything in the config directory.

Okay, progress made.
Removed host from config.x.mysql_helper.db_config.
RW Host is definitely the DB servers IP address (not local), but still:
#<MysqlError: Problem establishing mysql connection (error: Access denied for user 'shift'@'localhost' (using password: YES)) (connection info: {:username=>"shift", :password=>"*****", :host=>"localhost", :connect_timeout=>5})>

when I look at the database list. It's reading the cluster list correctly from the DB (I renamed the cluster and it reflected that change).
And with some hunting I see the issue: ui/app/services/mysql_helper.rb is hardcoded to 'localhost' for dev and test.
I took the liberty of creating a PR for this, feel free to accept or reject as to how it reflects methodology: https://github.com/square/shift/pull/35

oh duh, sorry, I should have noticed that. I'll go ahead and merge your PR

Awesome, appreciate the help - migrations are running smoothly.


Add composite ConfigStore to combine multiple ConfigStore

In some repositories, we used multiple ConfigStores to store feature flags, for example, in eventing kafka broker, we use the Eventing core feature flags store and the EKB feature flags store

Changes

Add composite ConfigStore to combine multiple ConfigStore

Do you see
	for _, s := range stores {
		ctx = s.ToContext(ctx)
	}

being used often in different reconcilers?

This can be reused everywhere we have multiple config stores (config stores being mainly configmaps), a service example could be: config-features and config-network in the case one reconciler depends on both

in the case one reconciler depends on both

Not sure if we have a scenario in Serving but ok I see how this can be useful.

/lgtm
/hold for @dprotaso if he has any objections

/unhold
@dprotaso I'm merging this as I don't see objections here

/test unit-tests

/test unit-tests


RequestTelemetry.Url is null when processing a POST request in Azure

Repro Steps
We are implementing a custom processor by implementing ITelemetryProcessor because we want to avoid sending telemetry when the path of the url starts with a certain string.
Here's a code snippet of the class implementing ITelemetryProcessor:
public void Process(ITelemetry item)
{
    if (item is RequestTelemetry requestTelemetry
        && requestTelemetry.Url.PathAndQuery.StartsWith("/certain-string", StringComparison.OrdinalIgnoreCase))
    {
        return;
    }

    // ...
}

This is how we register it on application startup:
protected void Application_Start()
{
    // ...

    var builder = TelemetryConfiguration.Active.TelemetryProcessorChainBuilder;
    builder.Use(next => new FilterUrlProcessor(next));
    builder.Build();

    // As per https://github.com/Microsoft/ApplicationInsights-dotnet/issues/549#issuecomment-302795845
    foreach (var processor in TelemetryConfiguration.Active.TelemetryProcessors)
    {
        if (processor is ITelemetryModule telemetryModule)
        {
            telemetryModule.Initialize(TelemetryConfiguration.Active);
        }
    }
}

Actual Behavior
We are getting a null reference exception because requestTelemetry.Url is null when all these cases have been met:

Application runs in Azure
The request is a POST

POST requests on a local IIS instance have a filled requestTelemetry.Url property, same goes for GET requests in local and Azure environments. HttpContext.Current.Request.Url is never null.
Behavior has changed since we upgraded to AI v2.7.2 (from v2.5.1) and .NET v4.7.2 (from v4.6.2).
Expected Behavior
RequestTelemetry.Url should be populated with the url of the current request, on all environments for all kind of requests (POST, GET, ...).
Version Info
SDK Version : v2.7.2
.NET Version :	v4.7.2
How Application was onboarded with SDK(VisualStudio/StatusMonitor/Azure Extension) : VS - NuGet packages
OS : Azure Api Service
Hosting Info (IIS/Azure WebApps/ etc) : Azure Api Service

Does Telemetry.Url have to be null in the fix to #898? Given that it’s an intermediate request , what if we had it default to “/“
The reason is that it’s a surprising change to have code that “works” suddenly throw nullref exceptions just from updating the SDK version. In my case I’d have to add a null check to multiple services that included the original request filtering processor.
Would you accept a patch that defaults these to non null values?

@anblanco sorry to hear it caused null reference exception and you had to update several services to fix it. We'll be happy to accept a contribution to default Url to '/' in case of intermediate request.
In general, we cannot guarantee that Url is filled (e.g. for non-Http request telemetry it could be null), i.e. please always expect default value (null) on this or any other property.

@TimothyMothra could I ever expect a response here?


onPressEvent does not emit an EventItem

I found out, that the onPressEvent event does not has an EventItem inside its props.
This is the structure from the calendar-kit:
export interface EventItem {
  /** Unique ID for the event. */
  id: string;
  /** Start date of the event. (ISOString) */
  start: string;
  /** End date of the event. (ISOString) */
  end: string;
  /** Title of the event */
  title?: string;
  /** Background color of the event */
  color?: string;
  /** Container style of the event */
  containerStyle?: StyleProp<ViewStyle>;
  [key: string]: any;
}

This is the structure it actually emits:
export interface EventItem {
  /** Unique ID for the event. */
  id: string;
  /** Start date of the event. (Date) */
  start: Date;
  /** End date of the event. (Date) */
  end: Date;
  /** Title of the event */
  title?: string;
  /** Background color of the event */
  color?: string;
  /** Container style of the event */
  containerStyle?: StyleProp<ViewStyle>;
  [key: string]: any;
}

It is a JavaScript Date object and not a string.
I found out because i want to pass an event through a navigator and it said it has unserializable props (start and end).
Here's proof:
I can execute Date Object functions of the prop of the onPressEvent handler:

TypeScript states an error but the code is working fine, because the start property is a Date object.

Version 2.0.0 has been released, try it out with the new version.
Currently, there is no documentation for version 2.0.0, but I will update it in the next few days. In the meantime, you can follow the example code if you want to use the library early.


Source code refactoring - Extract Method/Variable

Hi,
It would be nice if there will be an option to refactor brightscript code.
It will improve the quality and maintainability of the project by restructuring the code while not modifying the runtime behavior.
Thanks,
Aviad A

It's definitely on the roadmap! The issue right now is that we don't have variable or function tracking, so we wouldn't have a safe way to refactor.
The language server branch is slowly working its way there though...so hopefully this will be possible in the near future.


Table Exporting

Can you make it so we can also export tables with this module?

Exporting to what format?
A format that's then importable by EasyTable on another server, or a more readable format?

The first option. That way I can save and back up tables individually.

Good idea, I'll add it to the list, thanks.

Just released in 1.3.1, thanks for the suggestion!


Removed no-longer-needed #includes

I went through and removed most of the dead includes, and also augmented the signal handler to include the name of the signal - a Ctrl-C now prints [SIGNAL]: Received signal 2 (Interrupt), exiting instead of [SIGNAL]: Received signal 2, exiting.

LGTM


feature: Added sphere of influence function

Fixes #128
My contribution is licensed under the MIT license.

Coverage increased (+0.01%) to 91.736% when pulling 5c2f6ca18e525e5bafcd73acf6ef56286007163e on SebstianNiemann/sphereOfInfluence into 7f3c3f8b40bee5245d888589dbd76cddbd5d28ab on master.


Use k8s secrets  for passwords

Why don't you use k8s secrets to store passwords?
As a user of a product, I would like to connect the same k8s secret to an application and to an clickhouse cluster

These items are already in TODO list, however, with no specific implementation dates so far.

implemented in 0.14.0

@sunsingerus could you share some links with CHI examples how to use this feature?

In CHOP config file one can specify not only plan username/password, but also namespace/name of the secret where passwords are located. Credentials from the secret takes precedence in case both options provided. In case no secret provied, operator fallback to old approcah with plaintest credentials.

One more note - operator configuration can be presented as ConfigMap, there is no need to modify files backed in Docker image

Fixed in https://github.com/Altinity/clickhouse-operator/releases/tag/0.14.0


Revert "Use the remaining half bit in the refcount to bypass ObjC deallocation overhead"

Unfortunately there were subtle interactions with ObjC weak references to Swift objects. Reverting now to unbreak stuff while we add the necessary stuff to libobjc to fix it.
Fixes rdar://problem/52066498
This reverts commit e3da6c30b09cd55798b5bd0d82fbe54348f0b448.

@swift-ci please test and merge

Where’s the “sad approval” button?


Skip deleting blob if it doesn't already exist (GC).

Our internal distribution has an error when GC.
failed to garbage collect: failed to delete blob sha256:95e929640ddfa42b86b2fdf1a488fb8d4baa186a1407a554ac3532a9770ec00c: filesystem: Path not found: /docker/registry/v2/blobs/sha256/95/95e929640ddfa42b86b2fdf1a488fb8d4baa186a1407a554ac3532a9770ec00c

This PATH existed in the backup immediately before GC execution.
In other words, inconsistency occurred during GC execution.
I don't know the cause, but we can avoid this problem by skipping if blob doesn't already exist.
updated

I don't know the cause, but we can avoid this problem by skipping if blob doesn't already exist.

I (We) found the cause.
We executed GC with nohup, because GC tasks a lot of time.
At that time,  it seems that We accidentally ran the process twice.
However, whatever the cause, there is no need to occur an error trying to remove a blob that has already disappeared.
Signed-off-by: cappyzawa<EMAIL_ADDRESS>

@caervs Could you review this if you have time, please?

I tried to add a test case but I couldn't do it...

Although this change appears safe, its also a fix for a problem that was caused by user error. I am in favour of closing.
I'll give it a week for any comments.

Closing as above.


Team update - Jun 28, 2023

This is a @Quansight-Labs/czi-a11y-grant team sync 🎉🎉🎉! This is a way for the Team Members to provide status reports on what they've been up to this week and request help and attention for things they are working on. This issue will be closed at the end of the day.
Copy and paste the template below, and answer questions as you wish!

Response Template
**Thanks I'd like to give 🙌**
- So-and-so helped me out a lot with foo...

**Updates from last week :heavy_check_mark:**
- I worked towards deliverable: <link-to-deliverable>

**Challenges I faced and things I'd like assistance with 🙏**
- I had a hard time figuring out ...

**My availability for next week**
- I'll be off on foo day...

**Important items for discussion 💬**
- I have a question about goal <link-to-goal>
- Can @foo give a comment on issue #NN ?
- I opened #NN for discussion, please chime in
- I need to discuss foo

:mag: Needs Triage
The Needs Triage issues require an initial assessment and labeling.
No issues need triage! 🎉
:dart: Project boards
Please make sure the boards reflect the current status of the project.
Jupyter a11y grant project

Updates from last week :heavy_check_mark:

Waiting review for notebook authoring guidelines https://github.com/jupyter/accessibility/pull/127
Merged for the ARIA and WCAG intro https://github.com/jupyter/accessibility/pull/126
Made the first release of JupyterLab-accessible-themes - https://pypi.org/project/jupyterlab-accessible-themes/
Sent invites to Tania for PyPI maintainers
Created recipe for the package - https://github.com/conda-forge/staged-recipes/pull/23183
Opened and merged https://github.com/Quansight-Labs/jupyterlab-accessible-themes/pull/58
Add review changes in PR for Github dark - https://github.com/Quansight-Labs/jupyterlab-accessible-themes/pull/53
Made the internship plan - https://docs.google.com/document/d/19Cr468MmiV0Lq68A_f5rLVO4-mD590P9AmjjgioyLVQ/edit?usp=sharing
Made PR for the 400% Zoom audit documentation - https://github.com/jupyter/accessibility/pull/133

Challenges I faced and things I'd like assistance with 🙏

I'm ok

My availability for next week

I'm here

Important items for discussion 💬

Do we want the intern to be in our sync meetings? Or should we only invite him to the group a11y meeting?
I still don't have any reply for external feedback about the notebook authoring guidelines, I need to do some thinking to see how we can move that PR to something that we want to have in the docs

Thanks I'd like to give 🙌
Thanks to the whole team for their patience with me as I get back to the project.
Updates from last week :heavy_check_mark:

#184 I picked up writing the results again this week. Still aiming for an end of week PR.
#147 The second test results and test 3 planning (tests not run) were reviewed and merged. This means I just need to link to these results elsewhere in the ecosystem to finish the project.
#173 picked up the jupyter/accessibility #127 for notebook authoring practices to give another review based on verbal feedback. This is still in progress.

Challenges I faced and things I'd like assistance with 🙏

I don't have anything right now.

My availability for next week

I will be here all week.

Important items for discussion 💬

I want to check in on my next steps with everyone else to make sure I didn't miss and direction changes in the meantime. Please let me know if I'm blocking you.

Notes:
@isabela-pf

she's back!
writing up more results from JupyterLab user testing, stretch goal: end of week pr
will be submitting PRs to create links to the STScI work - grant deliverable has two parts: 1. make results public 2. link to results
wondering if anything happened during Camp Quansight with creating an accessibility notebook; whether any thing happened there that needs to be taken into account for the grant documentation deliverable

@steff456
- Stephannie reached out to a couple of people individually; we need to try and do an "open" call at Quansight to reach out to folks
- the checklist seems usable to verify/audit notebooks rather than being a resource that folks could use to write better or more accessible notebooks
- need to debug the build and release of jupyterlab-accessible-themes
- internship plan looks good - suggestion to try Gitpod for docs if needing to avoid setting a development environment
- will work on fixing issues in https://github.com/Quansight-Labs/jupyterlab-accessible-themes/issues/56
@gabalafou
- will focus on the grant deliverables
- was planning to work on ARIA improvements for notebooks; this will be put on hold in favour of grant deliverables
- got back to his TAB trap PR


Should there be so many unlabelled areas?

I'm close to having a debugged version of blackstack working in docker containers on our fork of the project at https://github.com/BritishGeologicalSurvey/blackstack now.
However I'm seeing the annotator server fall over because the SQL JOIN is returning empty, the cause is that many of the areas in my set of test documents have not got labels - about 80% of them. Some of the test docs are intentionally low quality. Is this expected and is the best thing to do to limit the query to only labelled areas, or to track down the cause of no area labelling?

Is the join you are referring to this one - https://github.com/UW-Deepdive-Infrastructure/blackstack/blob/master/annotator/server.py#L197 ?

That's the one, it's the ON area_labels.area_id line that it fails to return data on ( without querying for the label and only up to the first join it ran ok)
I had roughly 1k labels for roughly 5k areas in the test set...

Interesting...that query is intended to fetch only the areas that have been labeled in order to show p values while tagging areas.
I'm assuming the labels you have for areas are stored in the area_labels table?


[DC-395] Add timestamp and folder name to html report, remove CSV warning

Adds timestamp and folder name to the html report. Removes warning for not specifying source format as CSV

Merging this PR.


Implement node filter in Vue 3, which should be reusable to be used in the explorer, dedicated views

Work in Progress (WIP):

Currently working on implementing the node table component.
The goal is to make it responsive and globally accessible for reusability.

verified working fine with all options


change float to include max value, add optional parameter for excluding it

It is imposible link?

yes i was reading about it yesterday, apparently it is. I'll leave it like it is and delete this issue for the moment. I might come up with a different idea at some point. Thank you.


Neo-scan and Neo-tracker out of sync; Not be able to transfer token

Hi. I tried to transfer my token from NEON wallet.  The transaction failed.
The token disappeared from my wallet and it has never been received at the destination wallet.
Neo-scan and Neo-tracker showed different amount of token (out of sync).
Neo-scan
https://neoscan.io/address/AXGVFLfPJPUsNTNubcPPpgHHT97RJ3twKo
Neo-tracker
https://neotracker.io/address/AXGVFLfPJPUsNTNubcPPpgHHT97RJ3twKo
Tx Hash:
c9c2cf126b9b4bb1e00b40b4aa23387fe68e3b2fcdeebd230ab2816b5b52e2de
What could I do to recover my fund?  Thank you for your help.

Hello @tongcw your funds are not "lost" they just will not show up in neoscan or neon wallet.
The problem is our notifications servers did not receive the nep5 transfer notification properly
http://notifications1.neeeo.org/v1/notifications/block/2930307
http://notifications4.neeeo.org/v1/notifications/block/2930307
(One of the server got it and not the other)
To solve the problem you can use your private key with another neo wallet, you should see your funds. I will update this issue when the notification servers are running properly again.

Thank you @adrienmo.   Is my understanding correct that the fund has been successfully transferred to the receiver's wallet?  I tried signing into different wallet with private key (e.g. O3) but still none of this token or transaction shown in the Tx history section.

fixed with resync


Emergency Location

Under emergency address, Could you include how to validate a location with Suite Numbers. For Example  " Suite A & B 12345 North Main Street, Redmond, WA 98052"

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

ID: 634810fc-7a47-f794-7803-9f3941d664dd
Version Independent ID: 52587955-5054-a003-6d03-948ce02838dd
Content: Plan emergency calling, emergency addresses, emergency call routing, dynamic emergency calling - Microsoft Teams
Content Source: Teams/what-are-emergency-locations-addresses-and-call-routing.md
Service: msteams
GitHub Login: @CarolynRowe
Microsoft Alias: crowe

@rickleye  Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@rickleye thank you for reaching out and helping improve MS Docs. It seems the article has been updated recently so please let me know if you need further assistance.

@rickleye Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


COSBETA-NONE: Add logging for metrics from DB

Add a regular job to log metrics from DB. We will probably add more metrics to this in future.

This is really the first half of this work. The second half is picking up these logs from Kibana and creating visualizations from these numbers. This might involve more changes, but we won't be able to tell until we get these initial changes on to INT.


Cmake error

I don't konw how to solve this problem, give me some advice please. thanks
CMake Error at /home/zyl/catkin_ws/devel/share/crazyflie_cpp/cmake/crazyflie_cppConfig.cmake:113 (message):
Project 'crazyflie_cpp' specifies
'/home/zyl/catkin_ws/src/crazyflie_ros/crazyflie_cpp/include' as an include
dir, which is not found.  It does neither exist as an absolute directory
nor in
'/home/zyl/catkin_ws/src/crazyflie_ros/crazyflie_cpp//home/zyl/catkin_ws/src/crazyflie_ros/crazyflie_cpp/include'.
Check the issue tracker 'https://github.com/whoenig/crazyflie_ros/issues'
and consider creating a ticket if the problem has not been reported yet.
Call Stack (most recent call first):
/opt/ros/melodic/share/catkin/cmake/catkinConfig.cmake:76 (find_package)
crazyflie_ros/crazyflie_driver/CMakeLists.txt:7 (find_package)
-- Configuring incomplete, errors occurred!
See also "/home/zyl/catkin_ws/build/CMakeFiles/CMakeOutput.log".
See also "/home/zyl/catkin_ws/build/CMakeFiles/CMakeError.log".
Invoking "cmake" failed

Looks like you are missing the git submodules. Try git submodule init and git submodule update.

Looks like you are missing the git submodules. Try git submodule init and git submodule update.

I tried that, but a new problem occurred.
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
USB_LIB
    linked by target "crazyflie_cpp" in directory /root/crazyflie_ws/src/crazyflie_ros/crazyflie_cpp

-- Configuring incomplete, errors occurred!
See also "/root/crazyflie_ws/build/CMakeFiles/CMakeOutput.log".
See also "/root/crazyflie_ws/build/CMakeFiles/CMakeError.log".
Invoking "cmake" failed

By the way, I am trying to implement this project in docker, and I see that this error seems to be related to USB, so I am considering whether it can be implemented in docker. My code to generate the container
docker run -it --name testusb --privileged -v /dev/bus/usb:/dev/bus/usb 【IMAGE】 /bin/bash

I want to know if this error is related to docker, if it doesn't matter, I sincerely hope you can tell me the solution, if it is related to the characteristics of docker, then I will try other methods, thank you very much!

Looks like you are missing the git submodules. Try git submodule init and git submodule update.

I tried that, but a new problem occurred.
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
USB_LIB
    linked by target "crazyflie_cpp" in directory /root/crazyflie_ws/src/crazyflie_ros/crazyflie_cpp

-- Configuring incomplete, errors occurred!
See also "/root/crazyflie_ws/build/CMakeFiles/CMakeOutput.log".
See also "/root/crazyflie_ws/build/CMakeFiles/CMakeError.log".
Invoking "cmake" failed

By the way, I am trying to implement this project in docker, and I see that this error seems to be related to USB, so I am considering whether it can be implemented in docker. My code to generate the container
docker run -it --name testusb --privileged -v /dev/bus/usb:/dev/bus/usb 【IMAGE】 /bin/bash

I want to know if this error is related to docker, if it doesn't matter, I sincerely hope you can tell me the solution, if it is related to the characteristics of docker, then I will try other methods, thank you very much!

I used
apt install libusb-1.0-0-dev

catkin_make successfully.
Thank you for your reading this issue

Thanks for the update!


AutoBleem vs PCS_MODDING

Hi soarqin.
Looks like you have exactly same ideas as my ideas on AutoBleem (get rid of c#, repair cue files, match covers using iso9660 ... even my v0.1 was pure C like your one, I switched to C++ later on to have a bit cleaner code),  ... how about joining forces  ?
Regards,
screemerpl

This is just a experimental project written for interest for improving my play with PSC, not a long-term plan.
But I have also joined madmonkey's project(he invited me on reddit) which has the same target, lol.
Anyhow this project is licensed under MIT so you can just use any codes if you like, I can also do some contributions to your project if I do have time but might not able to team up.


[BUG] Broken interface

On my system the interface seems to be pretty broken. Any ideas how I could troubleshoot this? Thanks! (Awesome tool by the way!)

I would say that's a video driver issue.
Try disabling hardware acceleration in Options > Application > Disable hardware acceleration.

That solves it, thank you!


Edit display typing

Part of refactoring the helper.service.ts
Added types to the edit display and helper.service.ts

Branch contains a flacky bug that shows up sometimes for the debugTreeGuardedCopyReport command from cypress tests


workikng on new flow

Changes

Comments

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#371
#370  👈
#368
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @chrisaddy and the rest of your teammates on  Graphite


Add Client / Mutual Authenication for s2nc Integrations Tests

Problem:
we currently test client authentication in s_client tests but not in s_server tests
Proposed Solution:
Add integration test coverage to client authentication to s2nc
we currently have some support in
https://github.com/awslabs/s2n/blob/d5b71d63b372b51b3119d1c23cee218bd7c9d76d/tests/unit/s2n_optional_client_auth_test.c
https://github.com/awslabs/s2n/blob/a6ffda44ef66da05e568c49ab32d3b524254cf6b/tls/s2n_handshake_io.c#L943

@NLMalloy Is this part of the test you put together?


Meteor 1.8 and @babel >= 7.0.0

Running with meteor 1.8 throws an error like:

While loading plugin static-assets from package nathantreid:static-assets:
module.js:547:15: Cannot find module
'C:\Users\Lilian\AppData\Local.meteor\packages\meteor-tool\1.8.0\mt-os.windows.x86_64\dev_bundle\lib\node_modules@babel\runtime\helpers\builtin\extends'
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.require (C:\tools\isobuild\bundler.js:2083:22)
at makeInstallerOptions.fallback (packages/modules-runtime.js:651:18)
at require (packages/modules-runtime.js:244:16)
at options.js (:47:16)
at fileEvaluate (packages/modules-runtime.js:343:9)
at require (packages/modules-runtime.js:238:16)
at :320:1
at :327:3

Updating from:
  use: [
<EMAIL_ADDRESS><EMAIL_ADDRESS>  ],

to
  use: [
<EMAIL_ADDRESS><EMAIL_ADDRESS>  ],

solves the issue.

Thanks! I'll get this fixed soon.

Just an update - I've been extremely busy of late and haven't been able to get to this yet. It's still on my radar!

This is resolved in<EMAIL_ADDRESS>


[stable/fluentd-elasticsearch] - Can not reach Elasticsearch cluster

Is this a request for help?:
Maybe, or it maybe a bug
Version of Helm and Kubernetes:
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}

K8 Version
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.1", GitCommit:"d4ab47518836c750f9949b9e0d387f20fb92260b", GitTreeState:"clean", BuildDate:"2018-04-12T14:14:26Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Which chart:
stable/fluentd-elasticsearch
What happened:
I ran  helm install --name fluentd-elasticsearch stable/fluentd-elasticsearch and when I checked the pod logs I could see, repeating:

Elasticsearch cluster ({:host=>\"elasticsearch-client\", :port=>9200, :scheme=>\"http\"})!"
2018-08-28 02:58:18 +0000 [warn]: [elasticsearch] bad chunk is moved to /tmp/fluentd-buffers/backup/worker0/elasticsearch/5747601af1357391618c9d3d41f86ed4.log
2018-08-28 02:58:21 +0000 [warn]: [elasticsearch] failed to write data into buffer by buffer overflow action=:block
2018-08-28 02:58:22 +0000 [warn]: [elasticsearch] got unrecoverable error in primary and no secondary error_class=Fluent::Plugin::ElasticsearchOutput::ConnectionFailure error="Can not reach Elasticsearch cluster ({:host=>\"elasticsearch-client\", :port=>9200, :scheme=>\"http\"})!"
2018-08-28 02:58:22 +0000 [warn]: [elasticsearch] bad chunk is moved to /tmp/fluentd-buffers/backup/worker0/elasticsearch/5747601c49495a3fbef6f6f7c8f7e9a8.log

What you expected to happen:
I didnt expect to see the above
How to reproduce it (as minimally and precisely as possible):
Probably just run  helm install --name fluentd-elasticsearch stable/fluentd-elasticsearch and check the logs in the pods.

I'm having the same issue as you...

Just focusing on the 1st and 4th lines
Elasticsearch cluster ({:host=>\"elasticsearch-client\", :port=>9200, :scheme=>\"http\"})!"
2018-08-28 02:58:22 +0000 [warn]: [elasticsearch] got unrecoverable error in primary and no secondary error_class=Fluent::Plugin::ElasticsearchOutput::ConnectionFailure error="Can not reach Elasticsearch cluster ({:host=>\"elasticsearch-client\", :port=>9200, :scheme=>\"http\"})!"
Have you got an elastic search cluster running?
Is it accessible at http://elasticsearch-client:9200 ?

I'm having the same issues, is there any solution for this?
2018-12-04 13:28:21 +0000 [warn]: [elasticsearch] bad chunk is moved to /tmp/fluentd-buffers/backup/worker0/elasticsearch/57b4cdf0b8ce38ecca4d1abf3bb73159.log 2018-12-04 13:28:52 +0000 [warn]: [elasticsearch] Could not push logs to Elasticsearch, resetting connection and trying again. read timeout reached 2018-12-04 13:28:54 +0000 [info]: [elasticsearch] Connection opened to Elasticsearch cluster => {:host=>"mon-es-elasticsearch-client", :port=>9200, :scheme=>"http"} 2018-12-04 13:29:25 +0000 [warn]: [elasticsearch] Could not push logs to Elasticsearch, resetting connection and trying again. read timeout reached 2018-12-04 13:29:29 +0000 [info]: [elasticsearch] Connection opened to Elasticsearch cluster => {:host=>"mon-es-elasticsearch-client", :port=>9200, :scheme=>"http"} 2018-12-04 13:29:59 +0000 [warn]: [elasticsearch] got unrecoverable error in primary and no secondary error_class=Fluent::Plugin::ElasticsearchOutput::ConnectionFailure error="Could not push logs to Elasticsearch after 2 retries. read timeout reached"


Added TokenAuthScheme, TokenAuth and TokenAuthSlice

Part of #7
Added TokenAuthScheme, TokenAuth and TokenAuthSlice and some tests.

@g4s8 please, take a look/merge

@g4s8 please, merge


fix: 修正切换工具后, 因产生重复result而导致无法删除结果的问题

sourceID的判定 undefined 和 '' 可是为相等。

:tada: This PR is included in version 1.0.0-alpha.1 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.1 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.1 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.1 :tada:
The release is available on:

GitHub release
v1.0.0-alpha.1

Your semantic-release bot :package::rocket: