Issue while building apk, but works fine on iOS Simulator and Android Emulator

I am having problem when I build apk. app in iOS Simulator works good. Please suggest solution
Steps to Reproduce
flutter build apk
You are building a fat APK that includes binaries for android-arm,
android-arm64, android-x64.
If you are deploying the app to the Play Store, it's recommended to use app
bundles or split the APK to reduce the APK size.
    To generate an app bundle, run:
        flutter build appbundle --target-platform
        android-arm,android-arm64,android-x64
        Learn more on: https://developer.android.com/guide/app-bundle
    To split the APKs per ABI, run:
        flutter build apk --target-platform
        android-arm,android-arm64,android-x64 --split-per-abi
        Learn more on:
        https://developer.android.com/studio/build/configure-apk-splits#configur
        e-abi-split
Running Gradle task 'assembleRelease'...

                                                                                FAILURE: Build failed with an exception.                                                                                * Where:                                                                        Script '/Users/sravan/Documents/FlutterSDK/flutter/packages/flutter_tools/gradle/flutter.gradle' line: 904
                                                                                * What went wrong:                                                              Execution failed for task ':app:compileFlutterBuildRelease'.                    > Process 'command '/Users/sravan/Documents/FlutterSDK/flutter/bin/flutter'' finished with non-zero exit value 1
                                                                                * Try:                                                                          Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
                                                                                * Get more help at https://help.gradle.org                                                                                BUILD FAILED in 2m 1s                                                           Running Gradle task 'assembleRelease'...                                        Running Gradle task 'assembleRelease'... Done                     123.0s (!)
Gradle task assembleRelease failed with exit code 1

Using following dependencies
dependencies:
  flutter:
    sdk: flutter
  persistent_bottom_nav_bar: ^2.1.0
  http: ^0.12.2
  smooth_star_rating: ^1.1.1
  sigv4: ^4.1.1
  provider: ^4.3.2+2
  amplify_core: '<1.0.0'
  amplify_auth_cognito: '<1.0.0'
  video_player: ^1.0.1
  chewie: ^0.12.0
  dots_indicator: ^1.2.0
  flutter_svg: ^0.18.0

flutter doctor -v
[✓] Flutter (Channel stable, 1.22.6, on Mac OS X 10.15.7 19H15 darwin-x64,
    locale en-IN)
    • Flutter version 1.22.6 at /Users/sravan/Documents/FlutterSDK/flutter
    • Framework revision 9b2d32b605 (3 weeks ago), 2021-01-22 14:36:39 -0800
    • Engine revision 2f0af37152
    • Dart version 2.10.5

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/sravan/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4, Build version 11E146
    • CocoaPods version 1.10.0

[!] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

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

[✓] Connected device (1 available)
    • iPhone 11 (mobile) • E26C98BD-9E81-4272-99F3-50D2756A89C3 • ios •
      com.apple.CoreSimulator.SimRuntime.iOS-13-4 (simulator)

Flutter build appbundle --verbose gives the following output

```
  [ +160 ms] executing: [/Users/sravan/Documents/FlutterSDK/flutter/] git -c
  log.showSignature=false log -n 1 --pretty=format:%H
  [  +73 ms] Exit code 0 from: git -c log.showSignature=false log -n 1
  --pretty=format:%H
  [   +1 ms] 9b2d32b605630f28625709ebd9d78ab3016b2bf6
  [        ] executing: [/Users/sravan/Documents/FlutterSDK/flutter/] git tag
  --points-at HEAD
  [  +76 ms] Exit code 0 from: git tag --points-at HEAD
  [        ] 1.22.6
  [  +20 ms] executing: [/Users/sravan/Documents/FlutterSDK/flutter/] git
  rev-parse --abbrev-ref --symbolic @{u}
  [   +7 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
  [        ] origin/stable
  [        ] executing: [/Users/sravan/Documents/FlutterSDK/flutter/] git
  ls-remote --get-url origin
  [   +6 ms] Exit code 0 from: git ls-remote --get-url origin
  [        ] https://github.com/flutter/flutter.git
  [  +79 ms] executing: [/Users/sravan/Documents/FlutterSDK/flutter/] git
  rev-parse --abbrev-ref HEAD
  [   +7 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
  [        ] stable
  [  +17 ms] executing: sw_vers -productName
  [  +25 ms] Exit code 0 from: sw_vers -productName
  [   +1 ms] Mac OS X
  [   +1 ms] executing: sw_vers -productVersion
  [  +18 ms] Exit code 0 from: sw_vers -productVersion
  [        ] 10.15.7
  [        ] executing: sw_vers -buildVersion
  [  +35 ms] Exit code 0 from: sw_vers -buildVersion
  [        ] 19H15
  [   +1 ms] executing: sysctl hw.optional.arm64
  [  +16 ms] Exit code 1 from: sysctl hw.optional.arm64
  [        ] sysctl: unknown oid 'hw.optional.arm64'
  [ +240 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required,
  skipping update.
  [        ] 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.
  [   +8 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required,
  skipping update.
  [   +1 ms] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping
  update.
  [   +3 ms] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping
  update.
  [   +5 ms] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required,
  skipping update.
  [   +1 ms] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required,
  skipping update.
  [   +1 ms] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required,
  skipping update.
  [   +1 ms] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required,
  skipping update.
  [  +24 ms] Artifact Instance of 'MaterialFonts' is not required, skipping
  update.
  [        ] Artifact Instance of 'GradleWrapper' is not required, skipping
  update.
  [        ] Artifact Instance of 'AndroidMavenArtifacts' is not required,
  skipping update.
  [   +7 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required,
  skipping update.
  [   +1 ms] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping
  update.
  [   +1 ms] Artifact Instance of 'FlutterWebSdk' is not required, skipping
  update.
  [        ] Artifact Instance of 'FlutterSdk' is not required, skipping update.
  [        ] 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.
  [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required,
  skipping update.
  [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required,
  skipping update.
  [        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required,
  skipping update.
  [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping
  update.
  [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping
  update.
  [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping
  update.
  [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping
  update.
  [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping
  update.
  [        ] Artifact Instance of 'FontSubsetArtifacts' is not required, skipping
  update.
  [ +151 ms] Found plugin amplify_auth_cognito at
  /Users/sravan/Documents/FlutterSDK/flutter/.pub-cache/hosted/pub.dartlang.org/am
  plify_auth_cognito-0.0.1-dev.4/
  [  +12 ms] Found plugin amplify_core at
  /Users/sravan/Documents/FlutterSDK/flutter/.pub-cache/hosted/pub.dartlang.org/am
  plify_core-0.0.1-dev.4/
  [  +56 ms] Found plugin import_js_library at
  /Users/sravan/Documents/FlutterSDK/flutter/.pub-cache/hosted/pub.dartlang.org/im
  port_js_library-1.0.2/
  [ +138 ms] Found plugin video_player at
  /Users/sravan/Documents/FlutterSDK/flutter/.pub-cache/hosted/pub.dartlang.org/vi
  deo_player-1.0.1/
  [  +11 ms] Found plugin video_player_web at
  /Users/sravan/Documents/FlutterSDK/flutter/.pub-cache/hosted/pub.dartlang.org/vi
  deo_player_web-0.1.4+1/
  [  +10 ms] Found plugin wakelock at
  /Users/sravan/Documents/FlutterSDK/flutter/.pub-cache/hosted/pub.dartlang.org/wa
  kelock-0.2.1+1/
  [   +7 ms] Found plugin wakelock_web at
  /Users/sravan/Documents/FlutterSDK/flutter/.pub-cache/hosted/pub.dartlang.org/wa
  kelock_web-0.1.0+3/
  [ +237 ms] Found plugin amplify_auth_cognito at
  /Users/sravan/Documents/FlutterSDK/flutter/.pub-cache/hosted/pub.dartlang.org/am
  plify_auth_cognito-0.0.1-dev.4/
  [   +4 ms] Found plugin amplify_core at
  /Users/sravan/Documents/FlutterSDK/flutter/.pub-cache/hosted/pub.dartlang.org/am
  plify_core-0.0.1-dev.4/
  [  +40 ms] Found plugin import_js_library at
  /Users/sravan/Documents/FlutterSDK/flutter/.pub-cache/hosted/pub.dartlang.org/im
  port_js_library-1.0.2/
  [  +43 ms] Found plugin video_player at
  /Users/sravan/Documents/FlutterSDK/flutter/.pub-cache/hosted/pub.dartlang.org/vi
  deo_player-1.0.1/
  [   +3 ms] Found plugin video_player_web at
  /Users/sravan/Documents/FlutterSDK/flutter/.pub-cache/hosted/pub.dartlang.org/vi
  deo_player_web-0.1.4+1/
  [   +5 ms] Found plugin wakelock at
  /Users/sravan/Documents/FlutterSDK/flutter/.pub-cache/hosted/pub.dartlang.org/wa
  kelock-0.2.1+1/
  [  +11 ms] Found plugin wakelock_web at
  /Users/sravan/Documents/FlutterSDK/flutter/.pub-cache/hosted/pub.dartlang.org/wa
  kelock_web-0.1.0+3/
  [  +35 ms] Generating
  /Users/sravan/Documents/FlutterWorkspace/InfinityIT/infinity_it/android/app/src/
  main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
  [  +74 ms] executing: /usr/bin/xcodebuild -version
  [ +898 ms] Exit code 0 from: /usr/bin/xcodebuild -version
  [        ] Xcode 11.4
             Build version 11E146
  [  +71 ms] Running Gradle task 'bundleRelease'...
  [   +3 ms] gradle.properties already sets `android.enableR8`
  [   +6 ms] Using gradle from
  /Users/sravan/Documents/FlutterWorkspace/InfinityIT/infinity_it/android/gradlew.
  [   +1 ms]
  /Users/sravan/Documents/FlutterWorkspace/InfinityIT/infinity_it/android/gradlew
  mode: 33261 rwxr-xr-x.
  [ +123 ms] executing: /usr/bin/plutil -convert json -o - /Applications/Android
  Studio.app/Contents/Info.plist
  [  +27 ms] Exit code 0 from: /usr/bin/plutil -convert json -o -
  /Applications/Android Studio.app/Contents/Info.plist
  [        ] {"CFBundleName":"Android
  Studio","JVMOptions":{"ClassPath":"$APP_PACKAGE\/Contents\/lib\/bootstrap.jar:$A
  PP_PACKAGE\/Contents\/lib\/extensions.jar:$APP_PACKAGE\/Contents\/lib\/util.jar:
  $APP_PACKAGE\/Contents\/lib\/jdom.jar:$APP_PACKAGE\/Contents\/lib\/log4j.jar:$AP
  P_PACKAGE\/Contents\/lib\/trove4j.jar:$APP_PACKAGE\/Contents\/lib\/jna.jar","JVM
  Version":"1.8*,1.8+","MainClass":"com.intellij.idea.Main","Properties":{"idea.pa
  ths.selector":"AndroidStudio4.1","idea.executable":"studio","idea.platform.prefi
  x":"AndroidStudio","idea.vendor.name":"Google","idea.home.path":"$APP_PACKAGE\/C
  ontents"}},"NSDesktopFolderUsageDescription":"An application in Android Studio
  requests access to the user's Desktop
  folder.","LSArchitecturePriority":["x86_64"],"CFBundleVersion":"AI-201.8743.12.4
  1.6858069","CFBundleDevelopmentRegion":"English","NSCameraUsageDescription":"An
  application in Android Studio requests access to the device's
  camera.","CFBundleDocumentTypes":[{"CFBundleTypeName":"Android Studio Project
  File","CFBundleTypeExtensions":["ipr"],"CFBundleTypeRole":"Editor","CFBundleType
  IconFile":"studio.icns"},{"CFBundleTypeName":"All
  documents","CFBundleTypeExtensions":["*"],"CFBundleTypeOSTypes":["****"],"CFBund
  leTypeRole":"Editor","LSTypeIsPackage":false}],"NSSupportsAutomaticGraphicsSwitc
  hing":true,"CFBundlePackageType":"APPL","CFBundleIconFile":"studio.icns","NSHigh
  ResolutionCapable":true,"CFBundleShortVersionString":"4.1","NSMicrophoneUsageDes
  cription":"An application in Android Studio requests access to the device's
  microphone.","CFBundleInfoDictionaryVersion":"6.0","CFBundleExecutable":"studio"
  ,"NSLocationUsageDescription":"An application in Android Studio requests access
  to the user's location
  information.","LSRequiresNativeExecution":"YES","CFBundleURLTypes":[{"CFBundleTy
  peRole":"Editor","CFBundleURLName":"Stacktrace","CFBundleURLSchemes":["idea"]}],
  "CFBundleIdentifier":"com.google.android.studio","LSApplicationCategoryType":"pu
  blic.app-category.developer-tools","CFBundleSignature":"????","LSMinimumSystemVe
  rsion":"10.8","NSDocumentsFolderUsageDescription":"An application in Android
  Studio requests access to the user's Documents
  folder.","NSDownloadsFolderUsageDescription":"An application in Android Studio
  requests access to the user's Downloads
  folder.","NSNetworkVolumesUsageDescription":"An application in Android Studio
  requests access to files on a network volume.","CFBundleGetInfoString":"Android
  Studio 4.1, build AI-201.87<IP_ADDRESS>58069. Copyright JetBrains s.r.o., (c)
  2000-2020","NSRemovableVolumesUsageDescription":"An application in Android
  Studio requests access to files on a removable volume."}
  [  +19 ms] executing: /Applications/Android
  Studio.app/Contents/jre/jdk/Contents/Home/bin/java -version
  [ +168 ms] Exit code 0 from: /Applications/Android
  Studio.app/Contents/jre/jdk/Contents/Home/bin/java -version
  [        ] openjdk version "1.8.0_242-release"
             OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
             OpenJDK 64-Bit Server VM (build 25.242-b3-6222593, mixed mode)
  [   +3 ms] executing:
  [/Users/sravan/Documents/FlutterWorkspace/InfinityIT/infinity_it/android/]
  /Users/sravan/Documents/FlutterWorkspace/InfinityIT/infinity_it/android/gradlew
  -Pverbose=true -Ptarget-platform=android-arm,android-arm64,android-x64
  -Ptarget=lib/main.dart -Ptrack-widget-creation=true -Pshrink=true
  -Ptree-shake-icons=true bundleRelease
  [+2360 ms] > Task :app:cleanMergeReleaseAssets UP-TO-DATE
  [ +270 ms] > Task :amplify_auth_cognito:preBuild UP-TO-DATE
  [        ] > Task :amplify_auth_cognito:preReleaseBuild UP-TO-DATE
  [        ] > Task :amplify_auth_cognito:mergeReleaseShaders UP-TO-DATE
  [        ] > Task :amplify_auth_cognito:compileReleaseShaders UP-TO-DATE
  [        ] > Task :amplify_auth_cognito:generateReleaseAssets UP-TO-DATE
  [        ] > Task :amplify_auth_cognito:packageReleaseAssets UP-TO-DATE
  [        ] > Task :amplify_core:preBuild UP-TO-DATE
  [   +3 ms] > Task :amplify_core:preReleaseBuild UP-TO-DATE
  [        ] > Task :amplify_core:mergeReleaseShaders UP-TO-DATE
  [        ] > Task :amplify_core:compileReleaseShaders UP-TO-DATE
  [        ] > Task :amplify_core:generateReleaseAssets UP-TO-DATE
  [        ] > Task :amplify_core:packageReleaseAssets UP-TO-DATE
  [        ] > Task :app:preBuild UP-TO-DATE
  [        ] > Task :app:extractProguardFiles UP-TO-DATE
  [        ] > Task :app:preReleaseBuild UP-TO-DATE
  [        ] > Task :app:mergeReleaseShaders UP-TO-DATE
  [        ] > Task :app:compileReleaseShaders UP-TO-DATE
  [        ] > Task :app:generateReleaseAssets UP-TO-DATE
  [+1987 ms] > Task :app:compileFlutterBuildRelease
  [        ] [ +154 ms] executing: [/Users/sravan/Documents/FlutterSDK/flutter/]
  git -c log.showSignature=false log -n 1 --pretty=format:%H
  [        ] [  +44 ms] Exit code 0 from: git -c log.showSignature=false log -n 1
  --pretty=format:%H
  [        ] [        ] 9b2d32b605630f28625709ebd9d78ab3016b2bf6
  [        ] [        ] executing: [/Users/sravan/Documents/FlutterSDK/flutter/]
  git tag --points-at HEAD
  [        ] [  +15 ms] Exit code 0 from: git tag --points-at HEAD
  [        ] [        ] 1.22.6
  [        ] [  +11 ms] executing: [/Users/sravan/Documents/FlutterSDK/flutter/]
  git rev-parse --abbrev-ref --symbolic @{u}
  [        ] [   +6 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic
  @{u}
  [        ] [        ] origin/stable
  [        ] [        ] executing: [/Users/sravan/Documents/FlutterSDK/flutter/]
  git ls-remote --get-url origin
  [        ] [   +5 ms] Exit code 0 from: git ls-remote --get-url origin
  [        ] [        ] https://github.com/flutter/flutter.git
  [        ] [  +50 ms] executing: [/Users/sravan/Documents/FlutterSDK/flutter/]
  git rev-parse --abbrev-ref HEAD
  [        ] [  +10 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
  [        ] [        ] stable
  [        ] [  +83 ms] Artifact Instance of 'AndroidMavenArtifacts' is not
  required, skipping update.
  [        ] [        ] 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.
  [        ] [   +3 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.
  [        ] [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not
  required, skipping update.
  [        ] [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not
  required, skipping update.
  [        ] [        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not
  required, skipping update.
  [        ] [  +22 ms] Artifact Instance of 'MaterialFonts' is not required,
  skipping update.
  [        ] [        ] Artifact Instance of 'GradleWrapper' is not required,
  skipping update.
  [        ] [        ] Artifact Instance of 'AndroidMavenArtifacts' is not
  required, skipping update.
  [        ] [        ] 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.
  [        ] [        ] Artifact Instance of 'FlutterSdk' is not required,
  skipping update.
  [        ] [        ] 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.
  [        ] [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not
  required, skipping update.
  [        ] [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not
  required, skipping update.
  [        ] [        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not
  required, skipping update.
  [        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required,
  skipping update.
  [        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required,
  skipping update.
  [        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required,
  skipping update.
  [        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required,
  skipping update.
  [        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required,
  skipping update.
  [        ] [        ] Artifact Instance of 'FontSubsetArtifacts' is not
  required, skipping update.
  [        ] [ +157 ms] Initializing file store
  [        ] [  +14 ms] Done initializing file store
  [        ] [ +116 ms] Skipping target: gen_localizations
  [        ] [ +798 ms] Skipping target: kernel_snapshot
  [        ] [   +5 ms] aot_android_asset_bundle: Starting due to {}
  [ +774 ms] [ +902 ms] Manifest contained wildcard assets. Inserting missing file
  into build graph to force rerun. for more information see #56466.
  [ +200 ms] [ +275 ms] Running command:
  /Users/sravan/Documents/FlutterSDK/flutter/bin/cache/dart-sdk/bin/dart
  --disable-dart-dev
  /Users/sravan/Documents/FlutterSDK/flutter/bin/cache/artifacts/engine/darwin-x64
  /const_finder.dart.snapshot --kernel-file
  /Users/sravan/Documents/FlutterWorkspace/InfinityIT/infinity_it/.dart_tool/flutt
  er_build/509d5557e18eea8e88c0a3883be0a45a/app.dill --class-library-uri
  package:flutter/src/widgets/icon_data.dart --class-name IconData
  [+1900 ms] [+1825 ms] Skipping target: android_aot_release_android-arm64
  [   +2 ms] [   +3 ms] Skipping target: android_aot_release_android-x64
  [   +1 ms] [   +4 ms] Skipping target: android_aot_release_android-arm
  [        ] [   +1 ms] Persisting file store
  [        ] [  +34 ms] Done persisting file store
  [  +96 ms] [  +36 ms] Target aot_android_asset_bundle failed:
  IconTreeShakerException: ConstFinder failure: Error: Error when reading
  '../../../FlutterSDK/flutter/bin/cache/artifacts/engine/darwin-x64/const_finder.
  dart.snapshot': No such file or directory
  [  +12 ms]            To disable icon tree shaking, pass --no-tree-shake-icons
  to the requested flutter build command
  [   +1 ms]            #0      IconTreeShaker._findConstants
  (package:flutter_tools/src/build_system/targets/icon_tree_shaker.dart:279:7)
  [        ]
  [        ]            #1      IconTreeShaker._getIconData
  (package:flutter_tools/src/build_system/targets/icon_tree_shaker.dart:120:51)
  [        ]            #2      IconTreeShaker.subsetFont
  (package:flutter_tools/src/build_system/targets/icon_tree_shaker.dart:181:36)
  [        ]
  [        ]            #3      copyAssets.
  (package:flutter_tools/src/build_system/targets/assets.dart:96:37)
  [   +1 ms]
  [        ]            #4      copyAssets.
  (package:flutter_tools/src/build_system/targets/assets.dart)
  [        ]            #5      MappedIterator.moveNext
  (dart:_internal/iterable.dart:392:20)
  [        ]            #6      Future.wait (dart:async/future.dart:406:26)
  [        ]            #7      copyAssets
  (package:flutter_tools/src/build_system/targets/assets.dart:80:16)
  [        ]            #8      _rootRunUnary (dart:async/zone.dart:1198:47)
  [        ]            #9      _CustomZone.runUnary
  (dart:async/zone.dart:1100:19)
  [        ]            #10     _FutureListener.handleValue
  (dart:async/future_impl.dart:143:18)
  [        ]            #11     Future._propagateToListeners.handleValueCallback
  (dart:async/future_impl.dart:696:45)
  [   +1 ms]            #12     Future._propagateToListeners
  (dart:async/future_impl.dart:725:32)
  [        ]            #13     Future._completeWithValue
  (dart:async/future_impl.dart:529:5)
  [        ]            #14     _AsyncAwaitCompleter.complete
  (dart:async-patch/async_patch.dart:40:15)
  [        ]            #15     _completeOnAsyncReturn
  (dart:async-patch/async_patch.dart:311:13)
  [        ]            #16     ManifestAssetBundle.build
  (package:flutter_tools/src/asset.dart)
  [        ]            #17     _rootRunUnary (dart:async/zone.dart:1198:47)
  [        ]            #18     _CustomZone.runUnary
  (dart:async/zone.dart:1100:19)
  [   +1 ms]            #19     _FutureListener.handleValue
  (dart:async/future_impl.dart:143:18)
  [   +1 ms]            #20     Future._propagateToListeners.handleValueCallback
  (dart:async/future_impl.dart:696:45)
  [   +1 ms]            #21     Future._propagateToListeners
  (dart:async/future_impl.dart:725:32)
  [   +1 ms]            #22     Future._completeWithValue
  (dart:async/future_impl.dart:529:5)
  [   +1 ms]            #23     _AsyncAwaitCompleter.complete
  (dart:async-patch/async_patch.dart:40:15)
  [   +1 ms]            #24     _completeOnAsyncReturn
  (dart:async-patch/async_patch.dart:311:13)
  [   +1 ms]            #25     loadPackageConfigWithLogging
  (package:flutter_tools/src/dart/package_map.dart)
  [   +1 ms]            #26     _rootRunUnary (dart:async/zone.dart:1198:47)
  [   +1 ms]            #27     _CustomZone.runUnary
  (dart:async/zone.dart:1100:19)
  [   +1 ms]            #28     _FutureListener.handleValue
  (dart:async/future_impl.dart:143:18)
  [   +1 ms]            #29     Future._propagateToListeners.handleValueCallback
  (dart:async/future_impl.dart:696:45)
  [   +1 ms]            #30     Future._propagateToListeners
  (dart:async/future_impl.dart:725:32)
  [   +1 ms]            #31     Future._completeWithValue
  (dart:async/future_impl.dart:529:5)
  [        ]            #32     _AsyncAwaitCompleter.complete
  (dart:async-patch/async_patch.dart:40:15)
  [        ]            #33     _completeOnAsyncReturn
  (dart:async-patch/async_patch.dart:311:13)
  [   +1 ms]            #34     readAnyConfigFileUri
  (package:package_config/src/package_config_io.dart)
  [   +1 ms]            #35     _rootRunUnary (dart:async/zone.dart:1198:47)
  [        ]            #36     _CustomZone.runUnary
  (dart:async/zone.dart:1100:19)
  [        ]            #37     _FutureListener.handleValue
  (dart:async/future_impl.dart:143:18)
  [   +1 ms]            #38     Future._propagateToListeners.handleValueCallback
  (dart:async/future_impl.dart:696:45)
  [   +1 ms]            #39     Future._propagateToListeners
  (dart:async/future_impl.dart:725:32)
  [   +1 ms]            #40     Future._completeWithValue
  (dart:async/future_impl.dart:529:5)
  [   +1 ms]            #41     Future._asyncCompleteWithValue.
  (dart:async/future_impl.dart:567:7)
  [   +1 ms]            #42     _rootRun (dart:async/zone.dart:1190:13)
  [        ]            #43     _CustomZone.run (dart:async/zone.dart:1093:19)
  [        ]            #44     _CustomZone.runGuarded
  (dart:async/zone.dart:997:7)
  [   +1 ms]            #45     _CustomZone.bindCallbackGuarded. (dart:async/zone.dart:1037:23)
  [   +1 ms]            #46     _microtaskLoop
  (dart:async/schedule_microtask.dart:41:21)
  [        ]            #47     _startMicrotaskLoop
  (dart:async/schedule_microtask.dart:50:5)
  [        ]            #48     _runPendingImmediateCallback
  (dart:isolate-patch/isolate_patch.dart:118:13)
  [        ]            #49     _RawReceivePortImpl._handleMessage
  (dart:isolate-patch/isolate_patch.dart:169:5)
  [  +28 ms] [ +183 ms] "flutter assemble" took 4,341ms.
  [ +105 ms] [  +20 ms]
  [  +11 ms]            #0      throwToolExit
  (package:flutter_tools/src/base/common.dart:14:3)
  [   +3 ms]            #1      AssembleCommand.runCommand
  (package:flutter_tools/src/commands/assemble.dart:238:7)
  [   +2 ms]            #2      _rootRunUnary (dart:async/zone.dart:1198:47)
  [   +1 ms]            #3      _CustomZone.runUnary
  (dart:async/zone.dart:1100:19)
  [   +1 ms]            #4      _FutureListener.handleValue
  (dart:async/future_impl.dart:143:18)
  [        ]            #5      Future._propagateToListeners.handleValueCallback
  (dart:async/future_impl.dart:696:45)
  [   +1 ms]            #6      Future._propagateToListeners
  (dart:async/future_impl.dart:725:32)
  [   +3 ms]            #7      Future._completeWithValue
  (dart:async/future_impl.dart:529:5)
  [        ]            #8      _AsyncAwaitCompleter.complete
  (dart:async-patch/async_patch.dart:40:15)
  [   +1 ms]            #9      _completeOnAsyncReturn
  (dart:async-patch/async_patch.dart:311:13)
  [        ]            #10     FlutterBuildSystem.build
  (package:flutter_tools/src/build_system/build_system.dart)
  [        ]            #11     _rootRunUnary (dart:async/zone.dart:1198:47)
  [        ]            #12     _CustomZone.runUnary
  (dart:async/zone.dart:1100:19)
  [        ]            #13     _FutureListener.handleValue
  (dart:async/future_impl.dart:143:18)
  [        ]            #14     Future._propagateToListeners.handleValueCallback
  (dart:async/future_impl.dart:696:45)
  [        ]            #15     Future._propagateToListeners
  (dart:async/future_impl.dart:725:32)
  [   +1 ms]            #16     Future._completeWithValue
  (dart:async/future_impl.dart:529:5)
  [        ]            #17     _AsyncAwaitCompleter.complete
  (dart:async-patch/async_patch.dart:40:15)
  [        ]            #18     _completeOnAsyncReturn
  (dart:async-patch/async_patch.dart:311:13)
  [   +2 ms]            #19     _BuildInstance.invokeTarget
  (package:flutter_tools/src/build_system/build_system.dart)
  [   +2 ms]            #20     _rootRunUnary (dart:async/zone.dart:1198:47)
  [        ]            #21     _CustomZone.runUnary
  (dart:async/zone.dart:1100:19)
  [        ]            #22     _FutureListener.handleValue
  (dart:async/future_impl.dart:143:18)
  [        ]            #23     Future._propagateToListeners.handleValueCallback
  (dart:async/future_impl.dart:696:45)
  [  +39 ms]            #24     Future._propagateToListeners
  (dart:async/future_impl.dart:725:32)
  [   +1 ms]            #25     Future._completeWithValue
  (dart:async/future_impl.dart:529:5)
  [   +3 ms]            #26     Future.wait.
  (dart:async/future.dart:414:23)
  [  +13 ms]            #27     _rootRunUnary (dart:async/zone.dart:1198:47)
  [        ]            #28     _CustomZone.runUnary
  (dart:async/zone.dart:1100:19)
  [  +66 ms]            #29     _FutureListener.handleValue
  (dart:async/future_impl.dart:143:18)
  [   +1 ms]            #30     Future._propagateToListeners.handleValueCallback
  (dart:async/future_impl.dart:696:45)
  [   +6 ms]            #31     Future._propagateToListeners
  (dart:async/future_impl.dart:725:32)
  [   +4 ms]            #32     Future._completeWithValue
  (dart:async/future_impl.dart:529:5)
  [   +3 ms]            #33     _AsyncAwaitCompleter.complete
  (dart:async-patch/async_patch.dart:40:15)
  [   +1 ms]            #34     _completeOnAsyncReturn
  (dart:async-patch/async_patch.dart:311:13)
  [        ]            #35     _BuildInstance.invokeTarget
  (package:flutter_tools/src/build_system/build_system.dart)
  [   +1 ms]            #36     _rootRunUnary (dart:async/zone.dart:1198:47)
  [   +1 ms]            #37     _CustomZone.runUnary
  (dart:async/zone.dart:1100:19)
  [   +2 ms]            #38     _FutureListener.handleValue
  (dart:async/future_impl.dart:143:18)
  [   +2 ms]            #39     Future._propagateToListeners.handleValueCallback
  (dart:async/future_impl.dart:696:45)
  [  +40 ms]            #40     Future._propagateToListeners
  (dart:async/future_impl.dart:725:32)
  [  +11 ms]            #41     Future._completeWithValue
  (dart:async/future_impl.dart:529:5)
  [   +3 ms]            #42     Future.wait.
  (dart:async/future.dart:414:23)
  [   +2 ms]            #43     _rootRunUnary (dart:async/zone.dart:1198:47)
  [        ]            #44     _CustomZone.runUnary
  (dart:async/zone.dart:1100:19)
  [  +10 ms]            #45     _FutureListener.handleValue
  (dart:async/future_impl.dart:143:18)
  [   +3 ms]            #46     Future._propagateToListeners.handleValueCallback
  (dart:async/future_impl.dart:696:45)
  [   +6 ms]            #47     Future._propagateToListeners
  (dart:async/future_impl.dart:725:32)
  [   +7 ms]            #48     Future._completeWithValue
  (dart:async/future_impl.dart:529:5)
  [   +3 ms]            #49     _AsyncAwaitCompleter.complete
  (dart:async-patch/async_patch.dart:40:15)
  [  +33 ms]            #50     _completeOnAsyncReturn
  (dart:async-patch/async_patch.dart:311:13)
  [   +1 ms]            #51     _BuildInstance._invokeInternal
  (package:flutter_tools/src/build_system/build_system.dart)
  [        ]            #52     _rootRunUnary (dart:async/zone.dart:1198:47)
  [   +8 ms]            #53     _CustomZone.runUnary
  (dart:async/zone.dart:1100:19)
  [   +1 ms]            #54     _FutureListener.handleValue
  (dart:async/future_impl.dart:143:18)
  [   +1 ms]            #55     Future._propagateToListeners.handleValueCallback
  (dart:async/future_impl.dart:696:45)
  [   +1 ms]            #56     Future._propagateToListeners
  (dart:async/future_impl.dart:725:32)
  [   +1 ms]            #57     Future._completeWithValue
  (dart:async/future_impl.dart:529:5)
  [   +1 ms]            #58     _AsyncAwaitCompleter.complete
  (dart:async-patch/async_patch.dart:40:15)
  [   +1 ms]            #59     _completeOnAsyncReturn
  (dart:async-patch/async_patch.dart:311:13)
  [   +2 ms]            #60     Node.computeChanges
  (package:flutter_tools/src/build_system/build_system.dart)
  [   +1 ms]            #61     _rootRunUnary (dart:async/zone.dart:1198:47)
  [   +1 ms]            #62     _CustomZone.runUnary
  (dart:async/zone.dart:1100:19)
  [  +10 ms]            #63     _FutureListener.handleValue
  (dart:async/future_impl.dart:143:18)
  [  +16 ms]            #64     Future._propagateToListeners.handleValueCallback
  (dart:async/future_impl.dart:696:45)
  [   +1 ms]            #65     Future._propagateToListeners
  (dart:async/future_impl.dart:725:32)
  [  +14 ms]            #66     Future._completeWithValue
  (dart:async/future_impl.dart:529:5)
  [   +1 ms]            #67     _AsyncAwaitCompleter.complete
  (dart:async-patch/async_patch.dart:40:15)
  [   +1 ms]            #68     _completeOnAsyncReturn
  (dart:async-patch/async_patch.dart:311:13)
  [        ]            #69     FileStore.diffFileList
  (package:flutter_tools/src/build_system/file_store.dart)
  [   +5 ms]            #70     _rootRunUnary (dart:async/zone.dart:1198:47)
  [        ]            #71     _CustomZone.runUnary
  (dart:async/zone.dart:1100:19)
  [   +1 ms]            #72     _FutureListener.handleValue
  (dart:async/future_impl.dart:143:18)
  [   +1 ms]            #73     Future._propagateToListeners.handleValueCallback
  (dart:async/future_impl.dart:696:45)
  [   +1 ms]            #74     Future._propagateToListeners
  (dart:async/future_impl.dart:725:32)
  [   +1 ms]            #75     Future._completeWithValue
  (dart:async/future_impl.dart:529:5)
  [        ]            #76     Future.wait.
  (dart:async/future.dart:414:23)
  [        ]            #77     _rootRunUnary (dart:async/zone.dart:1198:47)
  [        ]            #78     _CustomZone.runUnary
  (dart:async/zone.dart:1100:19)
  [        ]            #79     _FutureListener.handleValue
  (dart:async/future_impl.dart:143:18)
  [   +1 ms]            #80     Future._propagateToListeners.handleValueCallback
  (dart:async/future_impl.dart:696:45)
  [   +1 ms]            #81     Future._propagateToListeners
  (dart:async/future_impl.dart:725:32)
  [        ]            #82     Future._completeWithValue
  (dart:async/future_impl.dart:529:5)
  [   +1 ms]            #83     _AsyncAwaitCompleter.complete
  (dart:async-patch/async_patch.dart:40:15)
  [   +1 ms]            #84     _completeOnAsyncReturn
  (dart:async-patch/async_patch.dart:311:13)
  [   +1 ms]            #85     FileStore._hashFile
  (package:flutter_tools/src/build_system/file_store.dart)
  [   +1 ms]            #86     _rootRunUnary (dart:async/zone.dart:1198:47)
  [   +2 ms]            #87     _CustomZone.runUnary
  (dart:async/zone.dart:1100:19)
  [   +1 ms]            #88     _FutureListener.handleValue
  (dart:async/future_impl.dart:143:18)
  [   +1 ms]            #89     Future._propagateToListeners.handleValueCallback
  (dart:async/future_impl.dart:696:45)
  [   +1 ms]            #90     Future._propagateToListeners
  (dart:async/future_impl.dart:725:32)
  [   +2 ms]            #91     Future._complete
  (dart:async/future_impl.dart:519:7)
  [   +2 ms]            #92     Stream.last.
  (dart:async/stream.dart:1327:20)
  [   +1 ms]            #93     _rootRun (dart:async/zone.dart:1182:47)
  [        ]            #94     _CustomZone.run (dart:async/zone.dart:1093:19)
  [        ]            #95     _CustomZone.runGuarded
  (dart:async/zone.dart:997:7)
  [        ]            #96     _BufferingStreamSubscription._sendDone.sendDone
  (dart:async/stream_impl.dart:410:13)
  [        ]            #97     _BufferingStreamSubscription._sendDone
  (dart:async/stream_impl.dart:420:15)
  [        ]            #98     _DelayedDone.perform
  (dart:async/stream_impl.dart:630:14)
  [   +1 ms]            #99     _StreamImplEvents.handleNext
  (dart:async/stream_impl.dart:730:11)
  [   +1 ms]            #100    _PendingEvents.schedule.
  (dart:async/stream_impl.dart:687:7)
  [        ]            #101    _rootRun (dart:async/zone.dart:1182:47)
  [        ]            #102    _CustomZone.run (dart:async/zone.dart:1093:19)
  [        ]            #103    _CustomZone.runGuarded
  (dart:async/zone.dart:997:7)
  [        ]            #104    _CustomZone.bindCallbackGuarded. (dart:async/zone.dart:1037:23)
  [   +1 ms]            #105    _rootRun (dart:async/zone.dart:1190:13)
  [        ]            #106    _CustomZone.run (dart:async/zone.dart:1093:19)
  [        ]            #107    _CustomZone.runGuarded
  (dart:async/zone.dart:997:7)
  [   +2 ms]            #108    _CustomZone.bindCallbackGuarded. (dart:async/zone.dart:1037:23)
  [        ]            #109    _microtaskLoop
  (dart:async/schedule_microtask.dart:41:21)
  [   +3 ms]            #110    _startMicrotaskLoop
  (dart:async/schedule_microtask.dart:50:5)
  [   +2 ms]            #111    _runPendingImmediateCallback
  (dart:isolate-patch/isolate_patch.dart:118:13)
  [   +1 ms]            #112    _RawReceivePortImpl._handleMessage
  (dart:isolate-patch/isolate_patch.dart:169:5)
  [   +1 ms] FAILURE: Build failed with an exception.
  [        ] * Where:
  [        ] Script
  '/Users/sravan/Documents/FlutterSDK/flutter/packages/flutter_tools/gradle/flutte
  r.gradle' line: 904
  [        ] * What went wrong:
  [        ] Execution failed for task ':app:compileFlutterBuildRelease'.
  [        ] > Process 'command
  '/Users/sravan/Documents/FlutterSDK/flutter/bin/flutter'' finished with non-zero
  exit value 1
  [        ] * Try:
  [        ] Run with --stacktrace option to get the stack trace. Run with --info
  or --debug option to get more log output. Run with --scan to get full insights.
  [   +1 ms] * Get more help at https://help.gradle.org
  [        ] BUILD FAILED in 7s
  [   +3 ms] [   +9 ms] ensureAnalyticsSent: 3ms
  [        ] [   +5 ms] Running shutdown hooks
  [        ] [        ] Shutdown hooks complete
  [        ] [        ] exiting with code 1
  [   +1 ms] > Task :app:compileFlutterBuildRelease FAILED
  [        ] 11 actionable tasks: 1 executed, 10 up-to-date
  [ +370 ms] Running Gradle task 'bundleRelease'... (completed in 9.0s)
  [  +31 ms] "flutter appbundle" took 11,007ms.
  [  +17 ms] Gradle task bundleRelease failed with exit code 1
  [   +3 ms]
             #0      throwToolExit
  (package:flutter_tools/src/base/common.dart:14:3)
             #1      buildGradleApp
  (package:flutter_tools/src/android/gradle.dart:416:7)
             #2      _rootRunUnary (dart:async/zone.dart:1198:47)
             #3      _CustomZone.runUnary (dart:async/zone.dart:1100:19)
             #4      _FutureListener.handleValue
  (dart:async/future_impl.dart:143:18)
             #5      Future._propagateToListeners.handleValueCallback
             (dart:async/future_impl.dart:696:45)
             #6      Future._propagateToListeners
  (dart:async/future_impl.dart:725:32)
             #7      Future._completeWithValue (dart:async/future_impl.dart:529:5)
             #8      _AsyncAwaitCompleter.complete
  (dart:async-patch/async_patch.dart:40:15)
             #9      _completeOnAsyncReturn
  (dart:async-patch/async_patch.dart:311:13)
             #10     _DefaultProcessUtils.stream
             (package:flutter_tools/src/base/process.dart)
             #11     _rootRunUnary (dart:async/zone.dart:1198:47)
             #12     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
             #13     _FutureListener.handleValue
  (dart:async/future_impl.dart:143:18)
             #14     Future._propagateToListeners.handleValueCallback
             (dart:async/future_impl.dart:696:45)
             #15     Future._propagateToListeners
  (dart:async/future_impl.dart:725:32)
             #16     Future._completeWithValue (dart:async/future_impl.dart:529:5)
             #17     Future._asyncCompleteWithValue.
             (dart:async/future_impl.dart:567:7)
             #18     _rootRun (dart:async/zone.dart:1190:13)
             #19     _CustomZone.run (dart:async/zone.dart:1093:19)
             #20     _CustomZone.runGuarded (dart:async/zone.dart:997:7)
             #21     _CustomZone.bindCallbackGuarded.
             (dart:async/zone.dart:1037:23)
             #22     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
             #23     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
             #24     _runPendingImmediateCallback
             (dart:isolate-patch/isolate_patch.dart:118:13)
             #25     _RawReceivePortImpl._handleMessage
             (dart:isolate-patch/isolate_patch.dart:169:5)
[ +210 ms] ensureAnalyticsSent: 196ms
[   +6 ms] Running shutdown hooks
[        ] Shutdown hooks complete
[   +1 ms] exiting with code 1
</details>

@sravanpabolu
Looking at the log you provided, it shows below:
Target aot_android_asset_bundle failed:   IconTreeShakerException: ConstFinder failure: Error: Error when reading   '../../../FlutterSDK/flutter/bin/cache/artifacts/engine/darwin-x64/const_finder.   dart.snapshot': No such file or directory
Can you try flutter build apk --no-tree-shake-icons and see if it works ?

Hi @darshankawar , Thank you for replying. After I raised this issue, I have switched between dev and stable branches and upgraded flutter/dart sdk. Updated packages too. now I am not able to reproduce this issue. I will keep trying and will reopen this issue and comment back, if I see this issue again. Closing the issue for now.


Codecov Fixes from Codecov Support

What is the context of this PR?
Steve from Codecov support as provided this PR to resolve issues we are experiencing with codecov. There was no need to install the python package, the bash script manages the whole process.
How to review
Verify that Travis CI correctly uploads codecov coverage and it is reported in PRs.
Who worked on the PR
@stevepeak (Codecov Support)

Thank you @collisdigital feel free to ping me if you have questions. I'll be happy to review any issue or help answer questions.
Extra credit: there is a lot of customization available to Codecov. Learn more at http://docs.codecov.io/docs/codecov-yaml

Current coverage is 78.42% (diff: 100%)

No coverage report found for master at 75db9ec.

Powered by Codecov. Last update 75db9ec...932c857

@stevepeak we also have
- coverage report --fail-under=77

on line 23, is that correct?

@stevepeak also codecov is setup as an integration to GitHub but isn't available as a status check (see above; only Travis CI is there); we previously had it listed as a status check (not sure how we enabled it now since I cannot see it as an option in the repo settings anymore) but it wasn't being reported correctly (hence blocking the PR from being merged.
Does codecov support being a status check on PRs and if so, do you have any idea why it isn't available for this repo?

@collisdigital this is now handled by Commit Status API: http://docs.codecov.io/docs/commit-status

@collisdigital status did not post because the current use @warrenbailey is being used to set the status and got a denied access to GH API's. See this article on how to set a new bot http://docs.codecov.io/docs/team-bot

Thanks @stevepeak I've changed the config as suggested and also raised a separate PR for some tweaks based on the docs you pointed at #420. Hopefully that will solve this issue.

LGTM 👍


Update OGC Implementing/Compliant Product Details

Since this SDK supports now OGC API - Features - Part 3: Filtering and the Common Query Language (CQL), the next step would  be to update the OGC Implementing/Compliant Product Details listed here and here.

As of December 2021, OGC API - Features - Part 3 is not available on the feature list of its spec implementation page.

I will leave this issue and revisit it once the spec draft is approved.
But I can update https://github.com/opengeospatial/ogcapi-features/blob/master/implementations/README.adoc#implementations.

Ah ok, I see.
Very cool. 👍


Use decorator for prerequisites

This would be more pythonic I think

Closing. Wouldn't make enough of an impact to justify implementing it.


[BUG] txAdmin tries to execute custom ban message as command

txAdmin/FXServer versions:
FXServer: 4985, txAdmin: v4.9.0
Describe the bug
If you set up a custom locale.json and edit the ban message txAdmin tries to execute messages in a new line as command.
To Reproduce
Steps to reproduce the behavior:

Set up a custom locale.json
Edit the ban messages so that there is a \n and something afterwards in it
Restart txAdmin
Ban someone
Take a look at the console
See, that txAdmin tried to execute everything after the \n

Expected behavior
That txAdmin does not try to execute things after the \n
Screenshots
Console:

locale.json:

It's in German but I think it shows the bug pretty good
Additional context
None

Thanks for reporting this issue.
Will be available in tomorrow's update.


lodash is imported globaly when importing ANYTHING from 'native-base'

packages versions
"native-base": "^2.1.5",
"react": "16.0.0-alpha.12",
"react-native": "0.45.1",
expected behaviour
import { List } from 'native-base'
const something = _.noop
-> error: Can't find variable: _
actual behaviour
import { Icon } from 'native-base'
const something = _.noop
-> it just works... even without including lodash in the code... native-base somehow include it globaly...that should not be the case

I have reproduced as well.
Also I have found it works as expected if I import from NativeBase directory cloned referring to Contributing to NativeBase.
I guess the code exporting lodash to global is included in dist directory that is created by npm run transpile.
So this might be due to babel configuration when transpiling ( like  lodash/lodash#1798 ).

@marxus85 @horiuchie Can you check this with NativeBase 2.7.1?

I tried the above snippet
import { Icon } from 'native-base'
const something = _.noop
I get Cannot find variable:_


Resolved issues with instance schema naming not aligned with api

Schema naming for natIP and networkIP were incorrectly named natIp and networkIp.
Not an issue with the actual API requests, however having a matching schema makes it a lot easier to troubleshoot the problem.

Great catch, would you mind to update the instance template and managed instance group templates+schemas?

@ocsig @t04glovern Ping

I could only find a reference in the managed instance template. I've updated accordingly :)


Support hashed passwords

Coverage remained the same at 27.94% when pulling 42922e6ea20825417b990892a169fc256603391a on palourde:support-hashed-passwords into babcb699bdbcc71914238291f088e9c6f46d7fe9 on sensu:master.


az vm create gives warning about default public IP SKU changing even when no public IP is being created

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command
az vm create
Describe the bug
When creating a VM without a public IP address, you get this irrelevant warning:

It is recommended to use parameter "--public-ip-sku Standard" to create new VM with Standard public IP. Please note that the default public IP used for VM creation will be changed from Basic to Standard in the future.

Since that change won't affect VMs created with no public IP address, that warning in this case is just noise.
To Reproduce
az vm create [...] --public-ip-address ""
Expected behavior
Since no public IP address is being created, there should be no message saying the type of public IP address that is being created is going to change.
Environment summary
Cloud Shell bash
Additional context
This warning comes from here: https://github.com/Azure/azure-cli/blob/5352ca83cfeca436b8fa5dc16a06831bf61bff2c/src/azure-cli/azure/cli/command_modules/vm/custom.py#L913-L920

Thank you for opening this issue, we will look into it.


Module/liftover/1.1

This is an updated version of the module. It includes several modification, please see CHANGELOG. It is also addressing issue #154.

Thank you Lakshay!
I have removed the bedtools environment file since I later opted for the shell sort and do not need it included in the module. I have also updated the comment in the config file to reflect the latest changes. The Python version should not cause issues, since we do not share an environment between modules/rules.

Thank you Lakshay!
I have removed the bedtools environment file since I later opted for the shell sort and do not need it included in the module. I have also updated the comment in the config file to reflect the latest changes. The Python version should not cause issues, since we do not share an environment between modules/rules.


Provide wheels for googleapis-common-protos==1.5.3, google-apitools==0.5.21

While attempting to deploy this AWS Lambda, I get:
(data-store) ~/data-store/daemons/dss-sync (master): domovoi deploy
Creating deployment package.

Could not install dependencies:
future==0.16.0
cloud-blobstore==2.1.1
wrapt==1.10.11
jsonpickle==0.9.6
MarkupSafe==1.0
googleapis-common-protos==1.5.3
httplib2==0.11.0
itsdangerous==0.24
google-apitools==0.5.21
pycparser==2.18
inflection==0.3.1
PyYAML==3.12
You will have to build these yourself and vendor them in
the chalice vendor folder.

Your deployment will continue but may not work correctly
if missing dependencies are not present. For more information:
http://chalice.readthedocs.io/en/latest/topics/packaging.html

http://chalice.readthedocs.io/en/latest/topics/packaging.html says: "Specifically all pure python packages as well as all packages that upload wheel files for the manylinux1_x86_64 platform will be automatically installable."
So it appears that googleapis-common-protos==1.5.3, google-apitools==0.5.21 don't have manylinux1_x86_64 wheels.
Please provide these wheels -- it will make deploying AWS Lambda easier for any deployment that uses them.

@melissachang Unfortunately, those projects aren't managed here.  Please create issues in their respective trackers:

https://github.com/googleapis/googleapis
https://github.com/google/apitools

Note that both googleapis-common-protos and google-apitools are both pure-Python distributions AFAICT.

/cc @lukesneeringer for the googleapis-common-protos
Also keep in mind apitools is not supported at all.


Drawables per shop

Be possible to choose drawables individually by store. For example having an exclusive luxury clothing store.

Interesting suggestion @Im-Kayun. But I'm afraid that implementing such a system, requires me to do a major rewrite of not just the whole clothing store system, but also the client JS part as well (except for the UI). I will add an enhancement tag to this but unfortunately won't make it a priority as of now. Might eventually do it, but nothing very soon

Also, it kind of looks like a duplicate of #23

hey there - i also would like to group stores the way i like.
deminified your js, but cant realy use it
is there a way to get the original js file? would like to change it the way i like, open a pr and if you like it you can merge it


spawning scenarios

Explore marginal effects of spawning schedule aspects (duration, frequency, timing, synchrony) on current potential harvest
options

[ ] spawn twice?

[ ] seasonality of spawning

[ ] duration

[ ] Add monthly stock-recruit relationship to merge all spawning variants together


use horners method in DISC instead of calculating so many powers and polynomials

Describe the bug
the disc method has a lot of power and polynomials. IMO whenever possible, polynomials should use Horner's method which is already implemented in np.polyval but is easy to reimplement if needed.
To Reproduce
https://github.com/pvlib/pvlib-python/blob/8b98768818ee5ad85d9479877533651a2e9dc2cd/pvlib/irradiance.py#L1405-L1422
0.512 - 1.56*kt + 2.286*kt2 - 2.222*kt3

becomes
0.512 - kt * (1.56 + kt * (2.286 - 2.222 * kt))

or
np.polyval([-2.222, 2.286, -1.56, 0.512], kt)

Expected behavior
a few math tricks like this (atan2, log1p, Horner's method, etc.) are musts for efficiency and numerical stability.
Versions:

pvlib.__version__: 0.8.1

np.polyval([-2.222, 2.286, -1.56, 0.512], kt)

is more readable to me than the nested parentheses.
I'd be interested to see the performance difference.

I'm open to a PR that includes an asv test for efficiency and a regular test for precision. Keep in mind that _disc_kn is used within a loop in gti_dirint.
For anyone that comes across this issue when trying to understand why disc doesn't produce results that are as accurate as you like: this is not the cause of your problem. Search the pvlib google group and stack overflow tag for previous explanations.

by the numbers, Horner's is 2x faster which np.polyval is 50% slower:
In [32]: am = np.linspace(1.5, 6.0, 40)

In [33]: Knc = 0.866 - 0.122*am + 0.0121*am**2 - 0.000653*am**3 + 1.4e-05*am**4

In [34]: np.allclose(Knc, 0.866 + am*(-0.122 + am*(0.0121 + am*(-0.000653 + 1.4e-05*am))))
Out[34]: True

In [35]: np.allclose(Knc, np.polyval(p, am))
Out[35]: True

In [36]: %timeit 0.866 - 0.122*am + 0.0121*am**2 - 0.000653*am**3 + 1.4e-05*am**4
10.9 µs ± 259 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)

In [37]: %timeit np.polyval(p, am)
16 µs ± 128 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)

In [38]: %timeit 0.866 + am*(-0.122 + am*(0.0121 + am*(-0.000653 + 1.4e-05*am)))
4.67 µs ± 40 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)

since kt2 and kt3 are already pre-calculated and reused in a, b, and c I don't expect there to be any more time to be gained there, so really it's just Knc that could be 2x faster using Horner's. Tough call. Not worth it?

Good info about np.polyval, convenient but slower than doing it ourselves.  In this case, performance > readability.

Not worth it?

It's a small effort to improve a frequently-used function so I'd say yes, worth it.

I counted and surprisingly, there are the same flops in the existing kt, kt2, kt3 code than in Horner's, in fact, there are exactly 3 more, because it's unnecessary to pre-calculate kt, kt2, kt3 when using Horner's
By the numbers:
In [3]: kt = np.linspace(0.1, 0.9, 90)

In [4]: %paste
def test1(kt):
    kt2 = kt * kt  # about the same as kt ** 2
    kt3 = kt2 * kt  # 5-10x faster than kt ** 3

    bools = (kt <= 0.6)
    a = np.where(bools,
              0.512 - 1.56*kt + 2.286*kt2 - 2.222*kt3,
              -5.743 + 21.77*kt - 27.49*kt2 + 11.56*kt3)
    b = np.where(bools,
              0.37 + 0.962*kt,
              41.4 - 118.5*kt + 66.05*kt2 + 31.9*kt3)
    c = np.where(bools,
              -0.28 + 0.932*kt - 2.048*kt2,
              -47.01 + 184.2*kt - 222.0*kt2 + 73.81*kt3)
    return a, b, c

## -- End pasted text --

In [7]: a, b, c = test1(kt)

In [9]: %paste
def test2(kt):
    bools = (kt <= 0.6)
    a = np.where(bools,
              0.512 + kt*(-1.56 + kt*(2.286 - 2.222*kt)),
              -5.743 + kt*(21.77 + kt*(-27.49 + 11.56*kt)))
    b = np.where(bools,
              0.37 + 0.962*kt,
              41.4 + kt*(-118.5 + kt*(66.05 + 31.9*kt)))
    c = np.where(bools,
              -0.28 + kt*(0.932 - 2.048*kt),
              -47.01 + kt*(184.2 + kt*(-222.0 + 73.81*kt)))
    return a, b, c

## -- End pasted text --

In [10]: x, y, z = test2(kt)

In [11]: np.allclose(a,x)
Out[11]: True

In [12]: np.allclose(b,y)
Out[12]: True

In [13]: np.allclose(c,z)
Out[13]: True

In [14]: %timeit test2(kt)
23.3 µs ± 348 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)

In [15]: %timeit test2(kt)
23.9 µs ± 462 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)

In [16]: %timeit test1(kt)
26.2 µs ± 179 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)

In [17]: %timeit test1(kt)
27.3 µs ± 661 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)

Surprise! Horners is about 10% faster for this part of the DISC too!

Miscellaneous observations:

Since kt is in the range 0-1 I would not expect numerical issues with any evaluation method.  Air mass in the range 1-40 should be fine too.
For speed, you could also look into using np.dot with the factors.
The average scientist or student exploring the inner workings of pvlib will probably find the original easiest to understand.
Thinking about code clarity, you could consider changing the name bools to is_cloudy.

Great feedback!

the average scientist or student exploring the inner workings of pvlib will probably find the original easiest to understand.

Possibly true,  but I feel a bit like Horner's method,  log1p, & arctan2 are tools od the trade like unit tests,  Sphinx doc RST markup, Git, etc., that contributors & students of scientific computing must learn

Thinking about code clarity, you could consider changing the name bools to is_cloudy

I agree

For speed, you could also look into using np.dot with the factors.

When I test np.dot or np.linalg.norm or np.polyval they're usually slower than just x*x + y*y but I think readability is important, so maybe depends on usage.


Meshable probably shouldn't require Default

          `Meshable` probably shouldn't require `Default`, but imo the shapes should have (consistent) defaults. It can be useful at least for prototyping, and an editor (like Unity, Godot etc.) would need some defaults for shapes anyway

Originally posted by @Jondolf in https://github.com/bevyengine/bevy/pull/11688#discussion_r1480456669

I think this might've been a misunderstanding, as Meshable already doesn't seem to require Default now that I'm double-checking. So this doesn't seem to be an actual issue and can probably be closed?
(extra context: https://github.com/bevyengine/bevy/pull/11688#discussion_r1481858675)


fix: mockito package changes for v4.4.0

Packages were moved between Mockito v3 and v4, so imports needed to be changed.

Import change for upgrading Mockito -- no review needed


Use ng-annotate

You can get rid of explicit dependency injection array notation, removing a lot of boilerlate code. The module gulp-ng-annotate does it automatically for you.
Extra: using wildcard globs to select all files instead of specifying each one.
On your gulpfile.coffee:
var ngAnnotate = require('gulp-ng-annotate');

gulp.task('concat-uglify-js', function() {
  return gulp.src('assets/js/*.js')
    .pipe(concat('angular-filemanager.min.js'))
    .pipe(ngAnnotate())
    .pipe(uglify())
    .pipe(gulp.dest(dst))
});

This will automatically convert all DI functions into array syntax, this way you only have to declare your modules normally:
angular.module('FileManagerApp').controller('FileManagerCtrl',
    function($scope, $translate, $cookies, fileManagerConfig, Item, FileNavigator, FileUploader) {

Hi @weisk I like the idea to use this wildcard instead of specifying each file.
Regarding ngAnnotate, I'm used to use the dependency injection specifying the name first as string..
I prefer to continue this way and prevent to use another gulp plugin...
If its right for you, you can send a pull request with the concat-uglify-js task wildcard modification..
Thanks!!

Gulp plugins are free! They don't increase the library size, just for development :p
As you wish though, I'll make the PR soon.

:+1:  great!

Done at https://github.com/joni2back/angular-filemanager/commit/978039430cc899e4dd9981e78036cd5fd7cc4a43


update the model spec in the predictor

Add option for fast model.
For fast model, add confidence interval. A confidence interval is an option in which we call the slow model.

Fixed,


Do not append \n for PROCESS since that output has all of the delim…

…iters and can be chunked not per line.
Checklist

[x] I have filed an issue about this change and discussed potential changes with the maintainers.
[ ] I have received the approval from the maintainers to make this change.
[x] This is not a stylistic, refactoring, or cleanup change.

Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See
the Contributions section in the README for more
details.
Discussion thread for this change
Issue number: 7145
Description of this change

can we close this #7145 now?

can we close this #7145 now?

Yes!


Issue with Running server

Have an issues with running server...:
For the record, package.json looks like in a sample:
{
  "name": "web-sever",
  "version": "1.0.0",
  "scripts": {
    "start": "ws"
  }
}

When I trying to run in terminal, here what I get:
local-user-mac:ws local-user$ npm start

><EMAIL_ADDRESS>start /Users/local-user/work/ws
> ws

sh: ws: command not found

npm ERR! Darwin 13.4.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.1
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: `ws`
npm ERR! Exit status 127
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'ws'.
npm ERR! This is most likely a problem with the web-sever package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     ws
npm ERR! You can get their info via:
npm ERR!     npm owner ls web-sever
npm ERR! There is likely additional logging output above.

Is ws definitely npm installed in the project?
On 3 Apr 2015 18:08, "Michael"<EMAIL_ADDRESS>wrote:

Have an issues with running server...:
For the record, package.json looks like in a sample:
{
"name": "web-sever",
"version": "1.0.0",
"scripts": {
"start": "ws"
}
}
When I trying to run in terminal, here what I get:
local-user-mac:ws local-user$ npm start

<EMAIL_ADDRESS>start /Users/local-user/work/ws> ws

sh: ws: command not found
npm ERR! Darwin 13.4.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.1
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: ws
npm ERR! Exit status 127
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'ws'.
npm ERR! This is most likely a problem with the web-sever package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     ws
npm ERR! You can get their info via:
npm ERR!     npm owner ls web-sever
npm ERR! There is likely additional logging output above.
—
Reply to this email directly or view it on GitHub
https://github.com/75lb/local-web-server/issues/14.

i just tested this and it works fine for me..


Skip team auth for URL verification requests

URL verification requests are teamless, so we cannot verify our connectivity to them.

Thanks, you're right. I just merged the fix based on yours (sorry, I wanted to have your commit in history but I failed). I will ship a new version.

I just released version 3.2.5. Thanks for pointing this issue out.

No prob. 🙂 Just glad to have the fix in one way or the other.


test(userservice.test.ts): adding missing tests and fixing deletion test

Coverage increased (+8.3%) to 100.0% when pulling 5114877b9ba6a9377dbb50dd51b2554b975a5f7f on test/missing-tests into 3adbe930d80d1d296555ab89d0d309ba3ef19e0d on main.


Add &border_radius param

add border-radius in card that can be set like 15px.

Replace line no. 182 in card.php
from >
with  >

Replace line no. 182 in card.php
from > <rect width='495' height='195'/>
with  > <rect width='495' height='195' rx='15'/>

That looks good for the roundness, I think it makes the border color less visible though.
I might recommend instead changing the place that it currently has rounding, but make it customizable and do some shifting to make sure the border color is visible, in other words, changing the path on 191-192 to a rounded rectangle like this:
- <path d='M 4.5 0 L 490.5 0 C 492.984 0 495 2.016 495 4.5 L 495 190.5 C 495 192.984 492.984 195 490.5 195 L 4.5 195 C 2.016 195 0 192.984 0 190.5 L 0 4.5 C 0 2.016 2.016 0 4.5 0 Z'
-       style='stroke: {$theme["border"]}; fill: {$theme["background"]};stroke-miterlimit:10;rx: 4.5;'/>

+ <rect style='stroke: {$theme["border"]}; fill: {$theme["background"]}; x: 0.5px; y: 0.5px; rx: {$borderRadius}; width: calc(100% - 1px); height: calc(100% - 1px);'/>

As far as reading the parameter, you can see examples in the generateCard function, similar to how it is done for locale, date_format, etc. Here's an example of one way to do it:
// read border_radius parameter, default to 4.5 if not set
$borderRadius = $params["border_radius"] ?? "4.5";

You can also do the same in the generateErrorCard function.
It would also be nice if you could update the demo site with the new field and add unit tests. Feel free to let me know if you have any questions or need help with anything.

What if he uses dark theme >>> https://nps-github-readme-streak-stats.herokuapp.com/?user=DenverCoder1&theme=blue-green&hide_border=true

Replace line no. 182 in card.php
from > <rect width='495' height='195'/>
with  > <rect width='495' height='195' rx='15'/>

That looks good for the roundness, I think it makes the border color less visible though.
I might recommend instead changing the place that it currently has rounding, but make it customizable and do some shifting to make sure the border color is visible, in other words, changing the path on 191-192 to a rounded rectangle like this:
- <path d='M 4.5 0 L 490.5 0 C 492.984 0 495 2.016 495 4.5 L 495 190.5 C 495 192.984 492.984 195 490.5 195 L 4.5 195 C 2.016 195 0 192.984 0 190.5 L 0 4.5 C 0 2.016 2.016 0 4.5 0 Z'
-       style='stroke: {$theme["border"]}; fill: {$theme["background"]};stroke-miterlimit:10;rx: 4.5;'/>

+ <rect style='stroke: {$theme["border"]}; fill: {$theme["background"]}; x: 0.5px; y: 0.5px; rx: {$borderRadius}; width: calc(100% - 1px); height: calc(100% - 1px);'/>

As far as reading the parameter, you can see examples in the generateCard function, similar to how it is done for locale, date_format, etc. Here's an example of one way to do it:
// read border_radius parameter, default to 4.5 if not set
$borderRadius = $params["border_radius"] ?? "4.5";

You can also do the same in the generateErrorCard function.
It would also be nice if you could update the demo site with the new field and add unit tests. Feel free to let me know if you have any questions or need help with anything.

I am asking where is the paat of code where u r taking parameters from link and storing it
// read border_radius parameter, default to 4.5 if not set
$borderRadius = $params["border_radius"] ?? "4.5";

👆tried this but got error on line 15 at column 48: error parsing attribute name

You can check out border radius here >>>> https://nps-github-readme-streak-stats.herokuapp.com/?user=DenverCoder1&theme=blue-green&hide_border=true&border_radius=20
Demo site >>> https://nps-github-readme-streak-stats.herokuapp.com/demo

You can check out border radius here >>>> https://nps-github-readme-streak-stats.herokuapp.com/?user=DenverCoder1&theme=blue-green&hide_border=true&border_radius=20
Demo site >>> https://nps-github-readme-streak-stats.herokuapp.com/demo

Looks good, but as I mentioned earlier it should be changed in the other place instead (191-192)  because that's where the border stroke is applied.
https://nps-github-readme-streak-stats.herokuapp.com/?user=DenverCoder1&theme=blue-green&border_radius=20&border=f00

This is what it does if you apply it to the clipPath instead of the actual rectangle.
The suggestion I put earlier makes it so the border is more visible and works with border radius 0 since it replaces the old rounding effect.

FIXED try now...
You can check out border radius here >>>> https://nps-github-readme-streak-stats.herokuapp.com/?user=DenverCoder1&theme=blue-green&hide_border=true&border_radius=200
Demo site >>> https://nps-github-readme-streak-stats.herokuapp.com/demo


Fix resolution setting

In the conversion from extension to website, the resolution setting was severed between captureDesktop.js and onAccessApproved.js.

Note that we have removed the resolution related code from the project in #77 , so here's the relevant commit for future retrieval if necessary/desired.

Done in c3a3b8f0c0aa41c4e96c611465dc40749f4ff315


chore: release v0.54.0

Release https://github.com/Kong/go-kong/pull/430

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 59.40%. Comparing base (8006a79) to head (95116d6).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #434      +/-   ##
==========================================
- Coverage   59.44%   59.40%   -0.05%
==========================================
  Files          71       71
  Lines        4392     4392
==========================================
- Hits         2611     2609       -2
- Misses       1170     1171       +1
- Partials      611      612       +1

Flag
Coverage Δ

2.1
?

2.2
47.49% <ø> (-0.85%)
:arrow_down:

2.3
48.31% <ø> (-0.67%)
:arrow_down:

2.4
48.13% <ø> (-0.89%)
:arrow_down:

2.5
18.92% <ø> (-30.11%)
:arrow_down:

2.6
?

2.7
50.06% <ø> (-0.67%)
:arrow_down:

2.8
50.06% <ø> (-0.67%)
:arrow_down:

3.0
54.00% <ø> (-0.67%)
:arrow_down:

3.1
54.96% <ø> (-1.35%)
:arrow_down:

3.2
55.19% <ø> (-1.17%)
:arrow_down:

3.3
55.71% <ø> (-0.64%)
:arrow_down:

3.4
57.58% <ø> (-0.67%)
:arrow_down:

3.5
55.14% <ø> (-0.76%)
:arrow_down:

3.6
55.14% <ø> (-0.89%)
:arrow_down:

community
38.09% <ø> (-5.36%)
:arrow_down:

enterprise
58.06% <ø> (ø)

integration
59.40% <ø> (-0.05%)
:arrow_down:

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

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


Inconsistent keyboard focus in dark /high contrast mode

What
"as I carry on tabbing though there is no keyboard focus shown at all now in this top section that underline and border has disappeared."
Where
Throughout the site. Demonstrated in high contrast in Windows.
TODO

[ ] Check if this is also an issue on Macs
[ ] Make sure focus is shown on Windows in high contrast / dark mode
[ ] Make sure focus is shown on Macs in high contrast / dark mode if necessary

Background
From the Hassell Inclusion accessibility audit August 2023.
Dovetail: https://proficient-wallaby-dpwd.dovetailapp.com/insights/Dark-mode-high-contrast-mode-handles-keyboard-focus-inconsistently-jfyRsfZBLyScODrsIdBeP
WCAG fail
Miro board: https://miro.com/app/board/uXjVMjsL5YE=/

There is nothing to show that any of the top sections are selected in high contrast on Windows.


Extend MonoIdentity Refaster rule

After applying EPS on a repository, I've noticed essentially the following interesting pattern:
Mono.<Void>empty().flux().next()

Mono#flux() converts the Mono to a Flux as-is.
Flux#next() however simply takes the first element in the Flux or returns empty without any side-effects (contrary to Flux#single()).

So, this is practically a no-op.
Suggested commit message
Extend `MonoIdentity` Refaster rule (#465)

By flagging expressions of the form `mono.flux().next()`.

Nice @werli :rocket:!

@Stephan202 & @rickie insane review speed, thanks!


feat: makes it optional whether to parse runes.

related to #423
This PR changes the parser to allow opt-in/out of Rune parsing. (However, it requires Svelte v5.)
The main changes are:

Added a new option svelteFeatures.runes to control whether runes are parsed.
Added a new option parserOptions.svelteConfig to specify svelte.config.js.
If not specified, some config will be statically parsed from the svelte.config.js file.
If there is no option in svelteFeatures.runes, it will read the compilerOptions.runes in svelte.config.js.
If <svelte:options runes={...}> is present, it determines whether to prioritize them and parse Runes.
Change the parser service to provide svelteParseContext, to make that information available to the eslint-plugin.

I think the next issue can be solved by telling the compiler whether it should parse in rune mode.

~~https://github.com/sveltejs/eslint-plugin-svelte/issues/652~~

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

160 of 163 (98.16%)  changed or added relevant lines in 10 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 91.501%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/parser/globals.ts
7
8
87.5%

src/svelte-config/parser.ts
78
80
97.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
2949

Relevant Lines:
3131

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

160 of 163 (98.16%)  changed or added relevant lines in 10 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 91.501%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/parser/globals.ts
7
8
87.5%

src/svelte-config/parser.ts
78
80
97.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
2949

Relevant Lines:
3131

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

160 of 163 (98.16%)  changed or added relevant lines in 10 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 91.482%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/parser/globals.ts
7
8
87.5%

src/svelte-config/parser.ts
78
80
97.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
2949

Relevant Lines:
3131

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

196 of 215 (91.16%)  changed or added relevant lines in 10 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.5%) to 90.864%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/parser/globals.ts
7
8
87.5%

src/scope/index.ts
5
7
71.43%

src/svelte-config/parser.ts
116
132
87.88%

Totals

Change from base Build<PHONE_NUMBER>:
-0.5%

Covered Lines:
2985

Relevant Lines:
3183

💛  - Coveralls

I realized that it would be better to have svelte.config.js specified in eslint.config.js rather than statically analyzing svelte.config.js. I will make that change.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

207 of 236 (87.71%)  changed or added relevant lines in 10 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.0%) to 90.411%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/parser/globals.ts
7
8
87.5%

src/scope/index.ts
5
7
71.43%

src/svelte-config/parser.ts
125
151
82.78%

Totals

Change from base Build<PHONE_NUMBER>:
-1.0%

Covered Lines:
2996

Relevant Lines:
3204

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

207 of 236 (87.71%)  changed or added relevant lines in 10 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.0%) to 90.411%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/parser/globals.ts
7
8
87.5%

src/scope/index.ts
5
7
71.43%

src/svelte-config/parser.ts
125
151
82.78%

Totals

Change from base Build<PHONE_NUMBER>:
-1.0%

Covered Lines:
2996

Relevant Lines:
3204

💛  - Coveralls

I have a question.
Both runes mode and legacy mode can use store right?
Can you tell me more details why this PR can solve below?

https://github.com/sveltejs/eslint-plugin-svelte/issues/652

https://svelte-5-preview.vercel.app/#H4sIAAAAAAAAE2VR227DIAz9FQtNaqJGvbymSaR9x9hDSsjElhgEptuE-PcJ0iaV9mRzjo3tcwIb1SQdq98Cw36WrGavxrCK0a9JD3eTE0lWMae9FQlpnLDKUMeRk5qNtgQBTP8hIcJo9Qy7w9GRtnJ3SSWTJBDaI0ELL456ksWpTAxyGj0KUhpBobBylkhFCSExnNKPB2-G1FBgCW33YDhZSd7i9uY09NTXgIcUYQ_nBxMvSxbLe7Kssm_hnIHIsTluB2EzqFuXa2oIOcbmmLA7lbaqIbzk7dKwjb56Io2gUUxKfLVhvSlmqTLq0rilsGMVm_WgRiUHVpP1MlarBVm_zYRP92zAKvq3VdRfp034xawn9VH-5Fqh0dFiUru2FQEW2U6Q5fm_0Hv8A7R7ehQfAgAA

Added a new option parserOptions.svelteConfig to specify svelte.config.js.

This is just my opinion but, in 99% of cases, compilerOptions.runs is defined statically in svelte.config.js.
So I think it's enough to parse svelte.config.js statically by default.
And we will use svelteFeatures.runes only if the value is explicitly specified in eslint config.

Hmm... I guess I misunderstood something.
This PR doesn't solve https://github.com/sveltejs/eslint-plugin-svelte/issues/652.
I thought that telling the compiler the runes mode correctly would solve the problem, but it didn't :sweat:

This is just my opinion but, in 99% of cases, compilerOptions.runs is defined statically in svelte.config.js.
So I think it's enough to parse svelte.config.js statically by default.
And we will use svelteFeatures.runes only if the value is explicitly specified in eslint config.

You are right about the compilerOptions.runs.
However, we think that in the future we might want to access more than just compilerOptions.runs, so I thought it made sense to add this option now.
For example, the following issue in eslint-plugin-svelte can be easily resolved if we have access to onwarn.
https://github.com/sveltejs/eslint-plugin-svelte/issues/311
For example, we can get the correct routes information even without the following settings:
https://sveltejs.github.io/eslint-plugin-svelte/user-guide/#settings-svelte-kit
Currently, the parser does not use any information other than compilerOptions.runs. However, I think that in the future it may.
Also we can also use it from parserServices to share svelte.config.js information with eslint-plugin rules.

However, we think that in the future we might want to access more than just compilerOptions.runs, so I thought it made sense to add this option now.

Agreed!
How about mimic the logic with vite-plugin-svelte?
https://github.com/sveltejs/vite-plugin-svelte/blob/main/docs/config.md#config-file
As default, user don't need to configure parserOptions.svelteConfig but automatically read the file.
If user use special file name, then user can configure parserOptions.svelteConfig or configure svelteFeatures .xxx as inline option.
It would be convenient for users if fewer settings could be made.
And svelte users may easier to understand if there are similar rules across the Svelte ecosystem.

As default, user don't need to configure parserOptions.svelteConfig but automatically read the file.

Unfortunately, currently the eslint custom parser cannot load ESMs because it needs to run synchronously, so svelte.config.js cannot be loaded inside the parser.
See https://github.com/eslint/eslint/issues/15475

Ah I forgot this😅.

@baseballyama
With this change, we might still be missing some features 😓
I have a question. Will the Svelte core parser automatically parse runes as runes when they are used, even without compilerOptions.runes?
If so, this parser needs to be handled the same way.

Ahh, yeah, you are right.
If there is rune symbol in .svelte / .svelte.js file, compiler will automatically enable rune mode for the component.
If compilerOptions.runes is true, apply rune mode compulsorily. (So we can not use export let xxx anymore.)
If compilerOptions.runes is false, the compiler doesn't use runes. (So if there is $derived or some runes, $derived will be behave as normal variable.)

I'm fixing.


[Bug]: Hit viewer not showing hits.

Version of the software
0.2.4
Operating system
Windows 10
Browser / Native
Chrome 100
What happened?
This happens quite frequently when there is a lot of custom/to check hits, the hit viewer simply does not show any data and you have to scroll all the way down to view hits which at times the scroll bar just goes back up and it takes about 10 minutes for me to be able to view the hits. Its the most annoying thing in OB2 currently. This exists for atleast 3 months now.
Relevant LoliCode if needed
No response

Also it seems that one of the hit viewer height elements keeps on changing between 2 numbers all the time.

Changing width and height css code seems to fix this.

just try to enable this option in your OB settings to view logs in your job section

Changing width and height css code seems to fix this.

i don't understand dude

Bruh, i already have that enabled thats not what this issue is about.
When you run a job for a while and the job displays multiple tocheck, custom hits and what not the hit viewer bugs out and nothing is shown.

Changing width and height css code seems to fix this.

i don't understand dude

Once again this is a bug report, not a how to enable this or that question.

I will definitely check this out, thanks. Does the CSS change you mentioned have any side effects (e.g. regarding the layout) or can it be implemented directly for everyone in the source of OB2?

There is side effects to this yes.

Oh and scrolling becomes a bit weird idk how to really explain it.

Add this to your CSS as temporary fix:
div.job-viewer-hits {   height: auto; }

Closing this as the new web client is completely remade from scratch and shouldn't have this issue


Fix RaveledParamsMap dtypes

The dtype of parameters can change as they get successively raveled and unraveled. This is problematic when sampling from the posterior distribution of a model whose observation distribution is discrete. In this PR we add a property to RaveledParamsMap that keeps track of dtypes.

The test that fails is unrelated to the current PR, it seems related to a recent change in scan_perform.pyx.


Calico incompatible ipset protocol version not resolved with iptables proxy-mode

Current Behavior
calico-node version v3.28.2 or v3.29.1 doesn't start in some Ubuntu 24.04.1 hosts:
calico-node-2t826                          1/1     Running   0          14m   <IP_ADDRESS>   aspb03
calico-node-578bz                          0/1     Running   0          14m   <IP_ADDRESS>   aspb01
calico-node-6ksgm                          0/1     Running   0          14m   <IP_ADDRESS>   aspb11
calico-node-dgkjf                          1/1     Running   0          14m   <IP_ADDRESS>   aspb12
calico-node-fgtb8                          1/1     Running   0          14m   <IP_ADDRESS>   aspb02
This error is reporting in the not ready calico-node pods
2024-12-03 12:02:08.747 [ERROR][2546] felix/ipsets.go 671: Bad return code from 'ipset list cali40this-host'. error=exit status 1 family="inet" stderr="ipset v7.11: Kernel and userspace incompatible: settype hash:ip with revision 6 not supported by userspace.\n"
2024-12-03 12:02:08.747 [ERROR][2546] felix/ipsets.go 1062: Failed to read ipset cali40this-host error=exit status 1 family="inet"

2024-12-03 12:02:08.749 [PANIC][2546] felix/ipsets.go 379: Failed to update IP sets after multiple retries. family="inet"
panic: (*logrus.Entry) 0xc000e9c460

goroutine 180 [running]:
github.com/sirupsen/logrus.(*Entry).log(0xc0003944d0, 0x0, {0xc000593cb0, 0x30})
	/go/pkg/mod/github.com/sirupsen/logrus@v1.9.3/entry.go:260 +0x485
github.com/sirupsen/logrus.(*Entry).Log(0xc0003944d0, 0x0, {0xc000ba9c60?, 0x5?, 0xc000a40360?})
	/go/pkg/mod/github.com/sirupsen/logrus@v1.9.3/entry.go:304 +0x48
github.com/sirupsen/logrus.(*Entry).Panic(...)
	/go/pkg/mod/github.com/sirupsen/logrus@v1.9.3/entry.go:342
github.com/projectcalico/calico/felix/ipsets.(*IPSets).ApplyUpdates(0xc000119c00)
	/go/src/github.com/projectcalico/calico/felix/ipsets/ipsets.go:379 +0x52b
github.com/projectcalico/calico/felix/dataplane/linux.(*InternalDataplane).apply.func1({0x3d18e10?, 0xc000119c00?})
	/go/src/github.com/projectcalico/calico/felix/dataplane/linux/int_dataplane.go:2289 +0x37
created by github.com/projectcalico/calico/felix/dataplane/linux.(*InternalDataplane).apply in goroutine 125
	/go/src/github.com/projectcalico/calico/felix/dataplane/linux/int_dataplane.go:2288 +0xb2a

All the nodes are identical and deployed with the same VM template and is a fresh cluster installation
Context
 I can't use Calico in my Kubernetes cluster

Your Environment

Calico version 3.28.2 or 3.29.1
Calico dataplane (iptables, windows etc.) iptables
Orchestrator version (e.g. kubernetes, mesos, rkt): Kubernetes 1.30.6
Operating System and version: Ubuntu 24.04.1 LTS
kube-proxy IPtables mode
Kernel: 6.8.0-49-generic

Kube-proxy is using ipset version 7.16
calico is using ipset version 7.11
Nothing or I don't find anything that is using ipset version 6

Seems like we'll need to update: 7.16 introduces some new fields (bitmask), and if kube-proxy is using them then things will break.  We'll try and get this changed asap.

Hi guys;
Finally I recreated all the cluster (nodes included) and deploy another one and in the two cases calico is deployed correctly. I think that something was wrong in the bootstraping process of the first cluster that left both nodes corrupt
I process to close the issue.
FYI, my cluster is deployed with RKE2 but with cni parameter to none. After I deployed calico via helm with tigera-operator
Thanks for your help.

Hi guys;
Finally I recreated all the cluster (nodes included) and deploy another one and in the two cases calico is deployed correctly. I think that something was wrong in the bootstraping process of the first cluster that left both nodes corrupt
I process to close the issue.
FYI, my cluster is deployed with RKE2 but with cni parameter to none. After I deployed calico via helm with tigera-operator
Thanks for your help.


Can't get metrics: ValueError: env prometheus_multiproc_dir is not set or not a directory

I have a SeldonDeployment referencing a custom image with a custom inference runtime.
After I deploy it to k8s (EKS), I see in the pod's description that metrics should be available on port 6000 of the model's container. Also in the container's logs I see:
Metrics server running on http://<IP_ADDRESS>:6000
Prometheus scraping endpoint can be accessed on http://<IP_ADDRESS>:6000/prometheus

But I can't scrape them neither by using PodMonitor (Target is down) nor by just running curl ...:6000/prometheus - I get internal error: ValueError: env prometheus_multiproc_dir is not set or not a directory. Am I missing something in the config? Also, why is it 6000 when in the docs here it says it should be 8082 by default?
Deployment's definition:
Name:         deployment-id
Namespace:    namespace-name
Labels:       app.kubernetes.io/managed-by=Helm
Annotations:  meta.helm.sh/release-name: chart-name
              meta.helm.sh/release-namespace: namespace-name
API Version:  machinelearning.seldon.io/v1
Kind:         SeldonDeployment
Metadata:
  Creation Timestamp:  2024-02-07T19:32:42Z
  Generation:          1
  Resource Version:    513990675
  UID:                 3007eb6d-6b09-45f7-9152-e99329e1e612
Spec:
  Predictors:
    Component Specs:
      Hpa Spec:
        Max Replicas:  3
        Metrics:
          Resource:
            Name:                        cpu
            Target Average Utilization:  70
          Type:                          Resource
        Min Replicas:                    1
      Spec:
        Containers:
          Image:              custom-image
          Image Pull Policy:  Always
          Name:               model-name
          Resources:
            Limits:
              Cpu:     1
              Memory:  6000M
            Requests:
              Cpu:     1
              Memory:  6000M
        Termination Grace Period Seconds:  1
    Graph:
      Name:                  model-name
      Service Account Name:  seldon-manager
      Type:                  MODEL
    Name:                    model
    Replicas:                1
  Protocol:                  v2

I figured out the reason. I'll leave the information here for now, in case it'll be helpful for anybody else.
I had seldon-core package installed in the image as a leftover from previous experiments with seldon deployments. Its version was 1.18.0 (latest for v1 at the time). As one of its requirements, it references package prometheus-client<0.9.0 and >=0.7.1 so it prevents anything higher than 0.8.0 to be installed. But that version only checks env var prometheus_multiproc_dir(in lower case) as can be seen here. MLServer version 1.3.5 sets up this variable in upper case, as can be seen here. So prometheus-client should be of version >=0.10.0 to check both cases. Removing seldon-core package allows it to be installed in version 0.17.0.

I figured out the reason. I'll leave the information here for now, in case it'll be helpful for anybody else.
I had seldon-core package installed in the image as a leftover from previous experiments with seldon deployments. Its version was 1.18.0 (latest for v1 at the time). As one of its requirements, it references package prometheus-client<0.9.0 and >=0.7.1 so it prevents anything higher than 0.8.0 to be installed. But that version only checks env var prometheus_multiproc_dir (in lower case) as can be seen here. MLServer version 1.3.5 sets up this variable in upper case, as can be seen here. So prometheus-client should be of version >=0.10.0 to check both cases. Removing seldon-core package allows it to be installed in version 0.17.0.


Replace CFRoute Valid/Invalid with the Ready condition

Is there a related GitHub Issue?
#3304

What is this change about?
Based on PR https://github.com/cloudfoundry/korifi/pull/3303
The Ready status condition is becoming the standard for Korifi
resources, therefore let's get rid of the Valid and Invalid
conditions in favour of the Ready one. Thus the CFRoute status
reconciliation code could be significantly simplified as we already have
the readyConditionBuilder utility in place.
Noone seems to care about Valid/Invalid status conditions, noone
cares about the Ready condition as well. However, having a standard
Ready condition is good (see #2098)
While being here, CFRoute.Status.Description and
CFRoute.Status.CurrentStatus are removed (as
again, noone cares) - hopefully this is not an incompatible change. If
anyone ever gets interested whether the route is OK, they should check
the Ready condition instead.

Does this PR introduce a breaking change?
No

Acceptance Steps
No functional change

Tag your pair, your PM, and/or team
@cloudfoundry/wg-cf-on-k8s

I haven't had a chance to look at the change itself too deeply yet (plan on doing so later today), but wanted to share some context around the original design here.
https://github.com/cloudfoundry/korifi/issues/102
The Valid/Invalid status conditions were added to make this easier to debug by human users which is why you wouldn't see any code references or anything checking them. We found that in live environments that users may have permissions to view a CFRoute, but not resources from the underlying ingress implementation (e.g. Contour HTTPProxy) so we wanted to surface errors up to a place that they could actually see.
I think it is fine to consolidate this type of information under the Ready conditions, but want to make sure we're still able to provide that same information to the user somewhere.
cc @davewalter who wrote that original issue

The motivation of replacing Valid/Invalid conditions on routes with Ready is that being valid is actually true/false/unknown. This fits quite well into a single condition with its three states - True/False/Uknown. Having two conditions brings 9 states alltogether, 6 of them simply not making sense.
I kind of feel that the name of the condition - Ready - might not have the semantics of Valid (like in being correct) but correctness should be guaranteed by validators. When a route is valid and usable, then this is what Ready stands for. If it is unusable, then it is not ready and the condition message and reason should provide details on what the issue is.
As per ergonomics - whether users are looking into a single condition, or two - I don't think it matters so much. A single condition just makes the code simpler.


Breakpoint continuation of the feasibility

I wonder if there is a way to implement breakpoint continuation

see https://blog.csdn.net/a78270528/article/details/77678840
SeaweedFS already supports Range request.