text:
[BUG] Windows - Flutter : Couldn't find any new signed apk files

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

I tried to upload my flutter bundle to the playstore. All the fastlane process end without error except a little message  Couldn't find any new signed apk files... which is weird because I would upload a bundle. And, i didn't see the new uploaded bundle inside my playstore account into internal test page...
Help please :) !
Command executed

$> flutter build appbundle
$> cd android
$> bundle exec fastlane android beta

Complete output when running fastlane, including the stack trace and command used

 [✔] �
[20:58:39]: ------------------------------
[20:58:39]: --- Step: default_platform ---
[20:58:39]: ------------------------------
[20:58:39]: Driving the lane 'android beta' �
[20:58:39]: ---------------------------
[20:58:39]: --- Step: bundleRelease ---
[20:58:39]: ---------------------------
[20:58:39]: $ C:/Users/CENSORED_FOR_THE_GITHUB_ISSUE/template/android/gradlew bundleRelease -p .
[20:58:40]: ▸ > Configure project :app
[20:58:40]: ▸ WARNING: The option setting 'android.enableR8=true' is deprecated.
[20:58:40]: ▸ It will be removed in version 5.0 of the Android Gradle plugin.
[20:58:40]: ▸ You will no longer be able to disable R8
[20:58:41]: ▸ > Task :app:cleanMergeReleaseAssets
[20:58:41]: ▸ > Task :app:preBuild UP-TO-DATE
[20:58:41]: ▸ > Task :app:extractProguardFiles UP-TO-DATE
[20:58:41]: ▸ > Task :app:preReleaseBuild UP-TO-DATE
[20:58:41]: ▸ > Task :app:mergeReleaseShaders UP-TO-DATE
[20:58:41]: ▸ > Task :app:compileReleaseShaders NO-SOURCE
[20:58:41]: ▸ > Task :app:generateReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :app:compileFlutterBuildRelease
[20:58:44]: ▸ > Task :app:packLibsflutterBuildRelease UP-TO-DATE
[20:58:44]: ▸ > Task :device_info:preBuild UP-TO-DATE
[20:58:44]: ▸ > Task :device_info:preReleaseBuild UP-TO-DATE
[20:58:44]: ▸ > Task :device_info:mergeReleaseShaders UP-TO-DATE
[20:58:44]: ▸ > Task :device_info:compileReleaseShaders NO-SOURCE
[20:58:44]: ▸ > Task :device_info:generateReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :device_info:packageReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_analytics:preBuild UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_analytics:preReleaseBuild UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_analytics:mergeReleaseShaders UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_analytics:compileReleaseShaders NO-SOURCE
[20:58:44]: ▸ > Task :firebase_analytics:generateReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_analytics:packageReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_core:preBuild UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_core:preReleaseBuild UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_core:mergeReleaseShaders UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_core:compileReleaseShaders NO-SOURCE
[20:58:44]: ▸ > Task :firebase_core:generateReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_core:packageReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :flutter_inappwebview:preBuild UP-TO-DATE
[20:58:44]: ▸ > Task :flutter_inappwebview:extractProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :flutter_inappwebview:preReleaseBuild UP-TO-DATE
[20:58:44]: ▸ > Task :flutter_inappwebview:mergeReleaseShaders UP-TO-DATE
[20:58:44]: ▸ > Task :flutter_inappwebview:compileReleaseShaders NO-SOURCE
[20:58:44]: ▸ > Task :flutter_inappwebview:generateReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :flutter_inappwebview:packageReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :google_mobile_ads:preBuild UP-TO-DATE
[20:58:44]: ▸ > Task :google_mobile_ads:preReleaseBuild UP-TO-DATE
[20:58:44]: ▸ > Task :google_mobile_ads:mergeReleaseShaders UP-TO-DATE
[20:58:44]: ▸ > Task :google_mobile_ads:compileReleaseShaders NO-SOURCE
[20:58:44]: ▸ > Task :google_mobile_ads:generateReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :google_mobile_ads:packageReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :path_provider:preBuild UP-TO-DATE
[20:58:44]: ▸ > Task :path_provider:preReleaseBuild UP-TO-DATE
[20:58:44]: ▸ > Task :path_provider:mergeReleaseShaders UP-TO-DATE
[20:58:44]: ▸ > Task :path_provider:compileReleaseShaders NO-SOURCE
[20:58:44]: ▸ > Task :path_provider:generateReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :path_provider:packageReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :shared_preferences:preBuild UP-TO-DATE
[20:58:44]: ▸ > Task :shared_preferences:preReleaseBuild UP-TO-DATE
[20:58:44]: ▸ > Task :shared_preferences:mergeReleaseShaders UP-TO-DATE
[20:58:44]: ▸ > Task :shared_preferences:compileReleaseShaders NO-SOURCE
[20:58:44]: ▸ > Task :shared_preferences:generateReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :shared_preferences:packageReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :sqflite:preBuild UP-TO-DATE
[20:58:44]: ▸ > Task :sqflite:preReleaseBuild UP-TO-DATE
[20:58:44]: ▸ > Task :sqflite:mergeReleaseShaders UP-TO-DATE
[20:58:44]: ▸ > Task :sqflite:compileReleaseShaders NO-SOURCE
[20:58:44]: ▸ > Task :sqflite:generateReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :sqflite:packageReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :url_launcher:preBuild UP-TO-DATE
[20:58:44]: ▸ > Task :url_launcher:preReleaseBuild UP-TO-DATE
[20:58:44]: ▸ > Task :url_launcher:mergeReleaseShaders UP-TO-DATE
[20:58:44]: ▸ > Task :url_launcher:compileReleaseShaders NO-SOURCE
[20:58:44]: ▸ > Task :url_launcher:generateReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :url_launcher:packageReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :video_player:preBuild UP-TO-DATE
[20:58:44]: ▸ > Task :video_player:preReleaseBuild UP-TO-DATE
[20:58:44]: ▸ > Task :video_player:mergeReleaseShaders UP-TO-DATE
[20:58:44]: ▸ > Task :video_player:compileReleaseShaders NO-SOURCE
[20:58:44]: ▸ > Task :video_player:generateReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :video_player:packageReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :wakelock:preBuild UP-TO-DATE
[20:58:44]: ▸ > Task :wakelock:preReleaseBuild UP-TO-DATE
[20:58:44]: ▸ > Task :wakelock:mergeReleaseShaders UP-TO-DATE
[20:58:44]: ▸ > Task :wakelock:compileReleaseShaders NO-SOURCE
[20:58:44]: ▸ > Task :wakelock:generateReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :wakelock:packageReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :webview_flutter:preBuild UP-TO-DATE
[20:58:44]: ▸ > Task :webview_flutter:preReleaseBuild UP-TO-DATE
[20:58:44]: ▸ > Task :webview_flutter:mergeReleaseShaders UP-TO-DATE
[20:58:44]: ▸ > Task :webview_flutter:compileReleaseShaders NO-SOURCE
[20:58:44]: ▸ > Task :webview_flutter:generateReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :webview_flutter:packageReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:preBuild UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:preReleaseBuild UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:mergeReleaseShaders UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:compileReleaseShaders NO-SOURCE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:generateReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:packageReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_flutter:preBuild UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_flutter:preReleaseBuild UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_flutter:mergeReleaseShaders UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_flutter:compileReleaseShaders NO-SOURCE
[20:58:44]: ▸ > Task :wonderpush_flutter:generateReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_flutter:packageReleaseAssets UP-TO-DATE
[20:58:44]: ▸ > Task :app:mergeReleaseAssets
[20:58:44]: ▸ > Task :video_player:compileReleaseAidl NO-SOURCE
[20:58:44]: ▸ > Task :video_player:compileReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :video_player:generateReleaseBuildConfig UP-TO-DATE
[20:58:44]: ▸ > Task :video_player:generateReleaseResValues UP-TO-DATE
[20:58:44]: ▸ > Task :video_player:generateReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :video_player:packageReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :video_player:parseReleaseLocalResources UP-TO-DATE
[20:58:44]: ▸ > Task :video_player:processReleaseManifest UP-TO-DATE
[20:58:44]: ▸ > Task :video_player:generateReleaseRFile UP-TO-DATE
[20:58:44]: ▸ > Task :video_player:javaPreCompileRelease UP-TO-DATE
[20:58:44]: ▸ > Task :video_player:compileReleaseJavaWithJavac UP-TO-DATE
[20:58:44]: ▸ > Task :video_player:mergeReleaseGeneratedProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :video_player:exportReleaseConsumerProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :sqflite:compileReleaseAidl NO-SOURCE
[20:58:44]: ▸ > Task :sqflite:compileReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :sqflite:generateReleaseBuildConfig UP-TO-DATE
[20:58:44]: ▸ > Task :sqflite:generateReleaseResValues UP-TO-DATE
[20:58:44]: ▸ > Task :sqflite:generateReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :sqflite:packageReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :sqflite:parseReleaseLocalResources UP-TO-DATE
[20:58:44]: ▸ > Task :sqflite:processReleaseManifest UP-TO-DATE
[20:58:44]: ▸ > Task :sqflite:generateReleaseRFile UP-TO-DATE
[20:58:44]: ▸ > Task :sqflite:javaPreCompileRelease UP-TO-DATE
[20:58:44]: ▸ > Task :sqflite:compileReleaseJavaWithJavac UP-TO-DATE
[20:58:44]: ▸ > Task :sqflite:mergeReleaseGeneratedProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :sqflite:exportReleaseConsumerProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :device_info:compileReleaseAidl NO-SOURCE
[20:58:44]: ▸ > Task :device_info:compileReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :device_info:generateReleaseBuildConfig UP-TO-DATE
[20:58:44]: ▸ > Task :device_info:generateReleaseResValues UP-TO-DATE
[20:58:44]: ▸ > Task :device_info:generateReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :device_info:packageReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :device_info:parseReleaseLocalResources UP-TO-DATE
[20:58:44]: ▸ > Task :device_info:processReleaseManifest UP-TO-DATE
[20:58:44]: ▸ > Task :device_info:generateReleaseRFile UP-TO-DATE
[20:58:44]: ▸ > Task :device_info:javaPreCompileRelease UP-TO-DATE
[20:58:44]: ▸ > Task :device_info:compileReleaseJavaWithJavac UP-TO-DATE
[20:58:44]: ▸ > Task :device_info:mergeReleaseGeneratedProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :device_info:exportReleaseConsumerProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :wakelock:compileReleaseAidl NO-SOURCE
[20:58:44]: ▸ > Task :wakelock:compileReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :wakelock:generateReleaseBuildConfig UP-TO-DATE
[20:58:44]: ▸ > Task :wakelock:generateReleaseResValues UP-TO-DATE
[20:58:44]: ▸ > Task :wakelock:generateReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :wakelock:packageReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :wakelock:parseReleaseLocalResources UP-TO-DATE
[20:58:44]: ▸ > Task :wakelock:processReleaseManifest UP-TO-DATE
[20:58:44]: ▸ > Task :wakelock:generateReleaseRFile UP-TO-DATE
[20:58:44]: ▸ > Task :wakelock:compileReleaseKotlin UP-TO-DATE
[20:58:44]: ▸ > Task :wakelock:javaPreCompileRelease UP-TO-DATE
[20:58:44]: ▸ > Task :wakelock:compileReleaseJavaWithJavac UP-TO-DATE
[20:58:44]: ▸ > Task :wakelock:mergeReleaseGeneratedProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :wakelock:exportReleaseConsumerProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:compileReleaseAidl NO-SOURCE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:compileReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:generateReleaseBuildConfig UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:generateReleaseResValues UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:generateReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:packageReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:parseReleaseLocalResources UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:processReleaseManifest UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:generateReleaseRFile UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:javaPreCompileRelease UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:compileReleaseJavaWithJavac UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:mergeReleaseGeneratedProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:exportReleaseConsumerProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :google_mobile_ads:compileReleaseAidl NO-SOURCE
[20:58:44]: ▸ > Task :google_mobile_ads:compileReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :google_mobile_ads:generateReleaseBuildConfig UP-TO-DATE
[20:58:44]: ▸ > Task :google_mobile_ads:generateReleaseResValues UP-TO-DATE
[20:58:44]: ▸ > Task :google_mobile_ads:generateReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :google_mobile_ads:packageReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :google_mobile_ads:parseReleaseLocalResources UP-TO-DATE
[20:58:44]: ▸ > Task :google_mobile_ads:processReleaseManifest UP-TO-DATE
[20:58:44]: ▸ > Task :google_mobile_ads:generateReleaseRFile UP-TO-DATE
[20:58:44]: ▸ > Task :google_mobile_ads:javaPreCompileRelease UP-TO-DATE
[20:58:44]: ▸ > Task :google_mobile_ads:compileReleaseJavaWithJavac UP-TO-DATE
[20:58:44]: ▸ > Task :google_mobile_ads:mergeReleaseGeneratedProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :google_mobile_ads:exportReleaseConsumerProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :url_launcher:compileReleaseAidl NO-SOURCE
[20:58:44]: ▸ > Task :url_launcher:compileReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :url_launcher:generateReleaseBuildConfig UP-TO-DATE
[20:58:44]: ▸ > Task :url_launcher:generateReleaseResValues UP-TO-DATE
[20:58:44]: ▸ > Task :url_launcher:generateReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :url_launcher:packageReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :url_launcher:parseReleaseLocalResources UP-TO-DATE
[20:58:44]: ▸ > Task :url_launcher:processReleaseManifest UP-TO-DATE
[20:58:44]: ▸ > Task :url_launcher:generateReleaseRFile UP-TO-DATE
[20:58:44]: ▸ > Task :url_launcher:javaPreCompileRelease UP-TO-DATE
[20:58:44]: ▸ > Task :url_launcher:compileReleaseJavaWithJavac UP-TO-DATE
[20:58:44]: ▸ > Task :url_launcher:mergeReleaseGeneratedProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :url_launcher:exportReleaseConsumerProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_core:compileReleaseAidl NO-SOURCE
[20:58:44]: ▸ > Task :firebase_analytics:compileReleaseAidl NO-SOURCE
[20:58:44]: ▸ > Task :firebase_core:packageReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :firebase_analytics:compileReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :firebase_analytics:generateReleaseBuildConfig UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_analytics:generateReleaseResValues UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_analytics:generateReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_analytics:packageReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_analytics:parseReleaseLocalResources UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_analytics:processReleaseManifest UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_core:compileReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :firebase_core:generateReleaseResValues UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_core:generateReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_core:packageReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_core:parseReleaseLocalResources UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_core:processReleaseManifest UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_core:generateReleaseRFile UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_analytics:generateReleaseRFile UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_analytics:javaPreCompileRelease UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_core:generateReleaseBuildConfig UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_core:javaPreCompileRelease UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_core:compileReleaseJavaWithJavac UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_core:bundleLibCompileToJarRelease UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_analytics:compileReleaseJavaWithJavac UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_analytics:mergeReleaseGeneratedProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_analytics:exportReleaseConsumerProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :flutter_inappwebview:compileReleaseAidl NO-SOURCE
[20:58:44]: ▸ > Task :flutter_inappwebview:compileReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :flutter_inappwebview:generateReleaseBuildConfig UP-TO-DATE
[20:58:44]: ▸ > Task :flutter_inappwebview:generateReleaseResValues UP-TO-DATE
[20:58:44]: ▸ > Task :flutter_inappwebview:generateReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :flutter_inappwebview:packageReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :flutter_inappwebview:parseReleaseLocalResources UP-TO-DATE
[20:58:44]: ▸ > Task :flutter_inappwebview:processReleaseManifest UP-TO-DATE
[20:58:44]: ▸ > Task :flutter_inappwebview:generateReleaseRFile UP-TO-DATE
[20:58:44]: ▸ > Task :flutter_inappwebview:javaPreCompileRelease UP-TO-DATE
[20:58:44]: ▸ > Task :flutter_inappwebview:compileReleaseJavaWithJavac UP-TO-DATE
[20:58:44]: ▸ > Task :flutter_inappwebview:mergeReleaseGeneratedProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :flutter_inappwebview:exportReleaseConsumerProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :webview_flutter:compileReleaseAidl NO-SOURCE
[20:58:44]: ▸ > Task :webview_flutter:compileReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :webview_flutter:generateReleaseBuildConfig UP-TO-DATE
[20:58:44]: ▸ > Task :webview_flutter:generateReleaseResValues UP-TO-DATE
[20:58:44]: ▸ > Task :webview_flutter:generateReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :webview_flutter:packageReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :webview_flutter:parseReleaseLocalResources UP-TO-DATE
[20:58:44]: ▸ > Task :webview_flutter:processReleaseManifest UP-TO-DATE
[20:58:44]: ▸ > Task :webview_flutter:generateReleaseRFile UP-TO-DATE
[20:58:44]: ▸ > Task :webview_flutter:javaPreCompileRelease UP-TO-DATE
[20:58:44]: ▸ > Task :webview_flutter:compileReleaseJavaWithJavac UP-TO-DATE
[20:58:44]: ▸ > Task :webview_flutter:mergeReleaseGeneratedProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :webview_flutter:exportReleaseConsumerProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :path_provider:compileReleaseAidl NO-SOURCE
[20:58:44]: ▸ > Task :path_provider:compileReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :path_provider:generateReleaseBuildConfig UP-TO-DATE
[20:58:44]: ▸ > Task :path_provider:generateReleaseResValues UP-TO-DATE
[20:58:44]: ▸ > Task :path_provider:generateReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :path_provider:packageReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :path_provider:parseReleaseLocalResources UP-TO-DATE
[20:58:44]: ▸ > Task :path_provider:processReleaseManifest UP-TO-DATE
[20:58:44]: ▸ > Task :path_provider:generateReleaseRFile UP-TO-DATE
[20:58:44]: ▸ > Task :path_provider:javaPreCompileRelease UP-TO-DATE
[20:58:44]: ▸ > Task :path_provider:compileReleaseJavaWithJavac UP-TO-DATE
[20:58:44]: ▸ > Task :path_provider:mergeReleaseGeneratedProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :path_provider:exportReleaseConsumerProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_flutter:compileReleaseAidl NO-SOURCE
[20:58:44]: ▸ > Task :wonderpush_flutter:compileReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :wonderpush_flutter:generateReleaseBuildConfig UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_flutter:generateReleaseResValues UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_flutter:generateReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_flutter:packageReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_flutter:parseReleaseLocalResources UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_flutter:processReleaseManifest UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_flutter:generateReleaseRFile UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_flutter:javaPreCompileRelease UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_flutter:compileReleaseJavaWithJavac UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_flutter:mergeReleaseGeneratedProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_flutter:exportReleaseConsumerProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :shared_preferences:compileReleaseAidl NO-SOURCE
[20:58:44]: ▸ > Task :shared_preferences:compileReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :shared_preferences:generateReleaseBuildConfig UP-TO-DATE
[20:58:44]: ▸ > Task :shared_preferences:generateReleaseResValues UP-TO-DATE
[20:58:44]: ▸ > Task :shared_preferences:generateReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :shared_preferences:packageReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :shared_preferences:parseReleaseLocalResources UP-TO-DATE
[20:58:44]: ▸ > Task :shared_preferences:processReleaseManifest UP-TO-DATE
[20:58:44]: ▸ > Task :shared_preferences:generateReleaseRFile UP-TO-DATE
[20:58:44]: ▸ > Task :shared_preferences:javaPreCompileRelease UP-TO-DATE
[20:58:44]: ▸ > Task :shared_preferences:compileReleaseJavaWithJavac UP-TO-DATE
[20:58:44]: ▸ > Task :shared_preferences:mergeReleaseGeneratedProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :shared_preferences:exportReleaseConsumerProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_core:mergeReleaseGeneratedProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_core:exportReleaseConsumerProguardFiles UP-TO-DATE
[20:58:44]: ▸ > Task :app:checkReleaseDuplicateClasses UP-TO-DATE
[20:58:44]: ▸ > Task :app:compileReleaseAidl NO-SOURCE
[20:58:44]: ▸ > Task :device_info:packageReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :firebase_analytics:packageReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :flutter_inappwebview:packageReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :google_mobile_ads:packageReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :path_provider:packageReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :shared_preferences:packageReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :sqflite:packageReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :url_launcher:packageReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :video_player:packageReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :wakelock:packageReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :webview_flutter:packageReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:packageReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :wonderpush_flutter:packageReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :app:compileReleaseRenderscript NO-SOURCE
[20:58:44]: ▸ > Task :app:generateReleaseBuildConfig UP-TO-DATE
[20:58:44]: ▸ > Task :device_info:writeReleaseAarMetadata UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_analytics:writeReleaseAarMetadata UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_core:writeReleaseAarMetadata UP-TO-DATE
[20:58:44]: ▸ > Task :flutter_inappwebview:writeReleaseAarMetadata UP-TO-DATE
[20:58:44]: ▸ > Task :google_mobile_ads:writeReleaseAarMetadata UP-TO-DATE
[20:58:44]: ▸ > Task :path_provider:writeReleaseAarMetadata UP-TO-DATE
[20:58:44]: ▸ > Task :shared_preferences:writeReleaseAarMetadata UP-TO-DATE
[20:58:44]: ▸ > Task :sqflite:writeReleaseAarMetadata UP-TO-DATE
[20:58:44]: ▸ > Task :url_launcher:writeReleaseAarMetadata UP-TO-DATE
[20:58:44]: ▸ > Task :video_player:writeReleaseAarMetadata UP-TO-DATE
[20:58:44]: ▸ > Task :wakelock:writeReleaseAarMetadata UP-TO-DATE
[20:58:44]: ▸ > Task :webview_flutter:writeReleaseAarMetadata UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:writeReleaseAarMetadata UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_flutter:writeReleaseAarMetadata UP-TO-DATE
[20:58:44]: ▸ > Task :app:checkReleaseAarMetadata UP-TO-DATE
[20:58:44]: ▸ > Task :app:copyFlutterAssetsRelease
[20:58:44]: ▸ > Task :app:generateReleaseResValues UP-TO-DATE
[20:58:44]: ▸ > Task :app:generateReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :app:processReleaseGoogleServices UP-TO-DATE
[20:58:44]: ▸ > Task :app:mergeReleaseResources UP-TO-DATE
[20:58:44]: ▸ > Task :app:createReleaseCompatibleScreenManifests UP-TO-DATE
[20:58:44]: ▸ > Task :app:extractDeepLinksRelease UP-TO-DATE
[20:58:44]: ▸ > Task :device_info:extractDeepLinksRelease UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_analytics:extractDeepLinksRelease UP-TO-DATE
[20:58:44]: ▸ > Task :firebase_core:extractDeepLinksRelease UP-TO-DATE
[20:58:44]: ▸ > Task :flutter_inappwebview:extractDeepLinksRelease UP-TO-DATE
[20:58:44]: ▸ > Task :google_mobile_ads:extractDeepLinksRelease UP-TO-DATE
[20:58:44]: ▸ > Task :path_provider:extractDeepLinksRelease UP-TO-DATE
[20:58:44]: ▸ > Task :shared_preferences:extractDeepLinksRelease UP-TO-DATE
[20:58:44]: ▸ > Task :sqflite:extractDeepLinksRelease UP-TO-DATE
[20:58:44]: ▸ > Task :url_launcher:extractDeepLinksRelease UP-TO-DATE
[20:58:44]: ▸ > Task :video_player:extractDeepLinksRelease UP-TO-DATE
[20:58:44]: ▸ > Task :wakelock:extractDeepLinksRelease UP-TO-DATE
[20:58:44]: ▸ > Task :webview_flutter:extractDeepLinksRelease UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_fcm_flutter:extractDeepLinksRelease UP-TO-DATE
[20:58:44]: ▸ > Task :wonderpush_flutter:extractDeepLinksRelease UP-TO-DATE
[20:58:45]: ▸ > Task :app:processReleaseMainManifest UP-TO-DATE
[20:58:45]: ▸ > Task :app:processReleaseManifest UP-TO-DATE
[20:58:45]: ▸ > Task :app:processReleaseManifestForPackage UP-TO-DATE
[20:58:45]: ▸ > Task :app:processReleaseResources UP-TO-DATE
[20:58:45]: ▸ > Task :device_info:bundleLibCompileToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :firebase_analytics:bundleLibCompileToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :flutter_inappwebview:bundleLibCompileToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :google_mobile_ads:bundleLibCompileToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :path_provider:bundleLibCompileToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :shared_preferences:bundleLibCompileToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :sqflite:bundleLibCompileToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :url_launcher:bundleLibCompileToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :video_player:bundleLibCompileToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :wakelock:bundleLibCompileToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :webview_flutter:bundleLibCompileToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :wonderpush_fcm_flutter:bundleLibCompileToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :wonderpush_flutter:bundleLibCompileToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :app:compileReleaseKotlin UP-TO-DATE
[20:58:45]: ▸ > Task :app:javaPreCompileRelease UP-TO-DATE
[20:58:45]: ▸ > Task :app:compileReleaseJavaWithJavac UP-TO-DATE
[20:58:45]: ▸ > Task :app:mergeReleaseGeneratedProguardFiles UP-TO-DATE
[20:58:45]: ▸ > Task :app:processReleaseJavaRes NO-SOURCE
[20:58:45]: ▸ > Task :device_info:processReleaseJavaRes NO-SOURCE
[20:58:45]: ▸ > Task :device_info:bundleLibResRelease NO-SOURCE
[20:58:45]: ▸ > Task :firebase_analytics:processReleaseJavaRes NO-SOURCE
[20:58:45]: ▸ > Task :firebase_analytics:bundleLibResRelease NO-SOURCE
[20:58:45]: ▸ > Task :firebase_core:processReleaseJavaRes NO-SOURCE
[20:58:45]: ▸ > Task :firebase_core:bundleLibResRelease NO-SOURCE
[20:58:45]: ▸ > Task :flutter_inappwebview:processReleaseJavaRes NO-SOURCE
[20:58:45]: ▸ > Task :flutter_inappwebview:bundleLibResRelease NO-SOURCE
[20:58:45]: ▸ > Task :google_mobile_ads:processReleaseJavaRes NO-SOURCE
[20:58:45]: ▸ > Task :google_mobile_ads:bundleLibResRelease NO-SOURCE
[20:58:45]: ▸ > Task :path_provider:processReleaseJavaRes NO-SOURCE
[20:58:45]: ▸ > Task :path_provider:bundleLibResRelease NO-SOURCE
[20:58:45]: ▸ > Task :shared_preferences:processReleaseJavaRes NO-SOURCE
[20:58:45]: ▸ > Task :shared_preferences:bundleLibResRelease NO-SOURCE
[20:58:45]: ▸ > Task :sqflite:processReleaseJavaRes NO-SOURCE
[20:58:45]: ▸ > Task :sqflite:bundleLibResRelease NO-SOURCE
[20:58:45]: ▸ > Task :url_launcher:processReleaseJavaRes NO-SOURCE
[20:58:45]: ▸ > Task :url_launcher:bundleLibResRelease NO-SOURCE
[20:58:45]: ▸ > Task :video_player:processReleaseJavaRes NO-SOURCE
[20:58:45]: ▸ > Task :video_player:bundleLibResRelease NO-SOURCE
[20:58:45]: ▸ > Task :wakelock:processReleaseJavaRes NO-SOURCE
[20:58:45]: ▸ > Task :wakelock:bundleLibResRelease UP-TO-DATE
[20:58:45]: ▸ > Task :webview_flutter:processReleaseJavaRes NO-SOURCE
[20:58:45]: ▸ > Task :webview_flutter:bundleLibResRelease NO-SOURCE
[20:58:45]: ▸ > Task :wonderpush_fcm_flutter:processReleaseJavaRes NO-SOURCE
[20:58:45]: ▸ > Task :wonderpush_fcm_flutter:bundleLibResRelease NO-SOURCE
[20:58:45]: ▸ > Task :wonderpush_flutter:processReleaseJavaRes NO-SOURCE
[20:58:45]: ▸ > Task :wonderpush_flutter:bundleLibResRelease NO-SOURCE
[20:58:45]: ▸ > Task :app:mergeReleaseJavaResource UP-TO-DATE
[20:58:45]: ▸ > Task :device_info:bundleLibRuntimeToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :firebase_analytics:bundleLibRuntimeToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :firebase_core:bundleLibRuntimeToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :flutter_inappwebview:bundleLibRuntimeToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :google_mobile_ads:bundleLibRuntimeToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :path_provider:bundleLibRuntimeToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :shared_preferences:bundleLibRuntimeToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :sqflite:bundleLibRuntimeToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :url_launcher:bundleLibRuntimeToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :video_player:bundleLibRuntimeToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :wakelock:bundleLibRuntimeToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :webview_flutter:bundleLibRuntimeToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :wonderpush_fcm_flutter:bundleLibRuntimeToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :wonderpush_flutter:bundleLibRuntimeToJarRelease UP-TO-DATE
[20:58:45]: ▸ > Task :app:minifyReleaseWithR8 UP-TO-DATE
[20:58:45]: ▸ > Task :app:processApplicationManifestReleaseForBundle UP-TO-DATE
[20:58:45]: ▸ > Task :app:bundleReleaseResources UP-TO-DATE
[20:58:45]: ▸ > Task :app:shrinkReleaseResources UP-TO-DATE
[20:58:45]: ▸ > Task :app:mergeReleaseJniLibFolders UP-TO-DATE
[20:58:45]: ▸ > Task :device_info:mergeReleaseJniLibFolders UP-TO-DATE
[20:58:45]: ▸ > Task :device_info:mergeReleaseNativeLibs NO-SOURCE
[20:58:45]: ▸ > Task :device_info:stripReleaseDebugSymbols NO-SOURCE
[20:58:45]: ▸ > Task :device_info:copyReleaseJniLibsProjectOnly UP-TO-DATE
[20:58:45]: ▸ > Task :firebase_analytics:mergeReleaseJniLibFolders UP-TO-DATE
[20:58:45]: ▸ > Task :firebase_analytics:mergeReleaseNativeLibs NO-SOURCE
[20:58:45]: ▸ > Task :firebase_analytics:stripReleaseDebugSymbols NO-SOURCE
[20:58:45]: ▸ > Task :firebase_analytics:copyReleaseJniLibsProjectOnly UP-TO-DATE
[20:58:45]: ▸ > Task :firebase_core:mergeReleaseJniLibFolders UP-TO-DATE
[20:58:45]: ▸ > Task :firebase_core:mergeReleaseNativeLibs NO-SOURCE
[20:58:45]: ▸ > Task :firebase_core:stripReleaseDebugSymbols NO-SOURCE
[20:58:45]: ▸ > Task :firebase_core:copyReleaseJniLibsProjectOnly UP-TO-DATE
[20:58:45]: ▸ > Task :flutter_inappwebview:mergeReleaseJniLibFolders UP-TO-DATE
[20:58:45]: ▸ > Task :flutter_inappwebview:mergeReleaseNativeLibs NO-SOURCE
[20:58:45]: ▸ > Task :flutter_inappwebview:stripReleaseDebugSymbols NO-SOURCE
[20:58:45]: ▸ > Task :flutter_inappwebview:copyReleaseJniLibsProjectOnly UP-TO-DATE
[20:58:45]: ▸ > Task :google_mobile_ads:mergeReleaseJniLibFolders UP-TO-DATE
[20:58:45]: ▸ > Task :google_mobile_ads:mergeReleaseNativeLibs NO-SOURCE
[20:58:45]: ▸ > Task :google_mobile_ads:stripReleaseDebugSymbols NO-SOURCE
[20:58:45]: ▸ > Task :google_mobile_ads:copyReleaseJniLibsProjectOnly UP-TO-DATE
[20:58:45]: ▸ > Task :path_provider:mergeReleaseJniLibFolders UP-TO-DATE
[20:58:45]: ▸ > Task :path_provider:mergeReleaseNativeLibs NO-SOURCE
[20:58:45]: ▸ > Task :path_provider:stripReleaseDebugSymbols NO-SOURCE
[20:58:45]: ▸ > Task :path_provider:copyReleaseJniLibsProjectOnly UP-TO-DATE
[20:58:45]: ▸ > Task :shared_preferences:mergeReleaseJniLibFolders UP-TO-DATE
[20:58:45]: ▸ > Task :shared_preferences:mergeReleaseNativeLibs NO-SOURCE
[20:58:45]: ▸ > Task :shared_preferences:stripReleaseDebugSymbols NO-SOURCE
[20:58:45]: ▸ > Task :shared_preferences:copyReleaseJniLibsProjectOnly UP-TO-DATE
[20:58:45]: ▸ > Task :sqflite:mergeReleaseJniLibFolders UP-TO-DATE
[20:58:45]: ▸ > Task :sqflite:mergeReleaseNativeLibs NO-SOURCE
[20:58:45]: ▸ > Task :sqflite:stripReleaseDebugSymbols NO-SOURCE
[20:58:45]: ▸ > Task :sqflite:copyReleaseJniLibsProjectOnly UP-TO-DATE
[20:58:45]: ▸ > Task :url_launcher:mergeReleaseJniLibFolders UP-TO-DATE
[20:58:45]: ▸ > Task :url_launcher:mergeReleaseNativeLibs NO-SOURCE
[20:58:45]: ▸ > Task :url_launcher:stripReleaseDebugSymbols NO-SOURCE
[20:58:45]: ▸ > Task :url_launcher:copyReleaseJniLibsProjectOnly UP-TO-DATE
[20:58:45]: ▸ > Task :video_player:mergeReleaseJniLibFolders UP-TO-DATE
[20:58:45]: ▸ > Task :video_player:mergeReleaseNativeLibs NO-SOURCE
[20:58:45]: ▸ > Task :video_player:stripReleaseDebugSymbols NO-SOURCE
[20:58:45]: ▸ > Task :video_player:copyReleaseJniLibsProjectOnly UP-TO-DATE
[20:58:45]: ▸ > Task :wakelock:mergeReleaseJniLibFolders UP-TO-DATE
[20:58:45]: ▸ > Task :wakelock:mergeReleaseNativeLibs NO-SOURCE
[20:58:45]: ▸ > Task :wakelock:stripReleaseDebugSymbols NO-SOURCE
[20:58:45]: ▸ > Task :wakelock:copyReleaseJniLibsProjectOnly UP-TO-DATE
[20:58:45]: ▸ > Task :webview_flutter:mergeReleaseJniLibFolders UP-TO-DATE
[20:58:45]: ▸ > Task :webview_flutter:mergeReleaseNativeLibs NO-SOURCE
[20:58:45]: ▸ > Task :webview_flutter:stripReleaseDebugSymbols NO-SOURCE
[20:58:45]: ▸ > Task :webview_flutter:copyReleaseJniLibsProjectOnly UP-TO-DATE
[20:58:45]: ▸ > Task :wonderpush_fcm_flutter:mergeReleaseJniLibFolders UP-TO-DATE
[20:58:45]: ▸ > Task :wonderpush_fcm_flutter:mergeReleaseNativeLibs NO-SOURCE
[20:58:45]: ▸ > Task :wonderpush_fcm_flutter:stripReleaseDebugSymbols NO-SOURCE
[20:58:45]: ▸ > Task :wonderpush_fcm_flutter:copyReleaseJniLibsProjectOnly UP-TO-DATE
[20:58:45]: ▸ > Task :wonderpush_flutter:mergeReleaseJniLibFolders UP-TO-DATE
[20:58:45]: ▸ > Task :wonderpush_flutter:mergeReleaseNativeLibs NO-SOURCE
[20:58:45]: ▸ > Task :wonderpush_flutter:stripReleaseDebugSymbols NO-SOURCE
[20:58:45]: ▸ > Task :wonderpush_flutter:copyReleaseJniLibsProjectOnly UP-TO-DATE
[20:58:45]: ▸ > Task :app:mergeReleaseNativeLibs UP-TO-DATE
[20:58:45]: ▸ > Task :app:stripReleaseDebugSymbols UP-TO-DATE
[20:58:45]: ▸ > Task :app:buildReleasePreBundle UP-TO-DATE
[20:58:45]: ▸ > Task :app:collectReleaseDependencies UP-TO-DATE
[20:58:45]: ▸ > Task :app:configureReleaseDependencies UP-TO-DATE
[20:58:45]: ▸ > Task :app:parseReleaseIntegrityConfig UP-TO-DATE
[20:58:45]: ▸ > Task :app:packageReleaseBundle UP-TO-DATE
[20:58:45]: ▸ > Task :app:validateSigningRelease UP-TO-DATE
[20:58:45]: ▸ > Task :app:signReleaseBundle UP-TO-DATE
[20:58:45]: ▸ > Task :app:bundleRelease UP-TO-DATE
[20:58:45]: ▸ Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
[20:58:45]: ▸ Use '--warning-mode all' to show the individual deprecation warnings.
[20:58:45]: ▸ See https://docs.gradle.org/6.5/userguide/command_line_interface.html#sec:command_line_warnings
[20:58:45]: ▸ BUILD SUCCESSFUL in 5s
[20:58:45]: ▸ 293 actionable tasks: 4 executed, 289 up-to-date
[20:58:45]: Couldn't find any new signed apk files...
[20:58:45]: ----------------------------------
[20:58:45]: --- Step: upload_to_play_store ---
[20:58:45]: ----------------------------------
+---------------------------------+----------------------------------------------------+
|                              Summary for supply 2.179.0                              |
+---------------------------------+----------------------------------------------------+
| track                           | internal                                           |
| skip_upload_changelogs          | true                                               |
| skip_upload_images              | true                                               |
| skip_upload_screenshots         | true                                               |
| package_name                    | CENSORED_FOR_THE_GITHUB_ISSUE                               |
| release_status                  | completed                                          |
| metadata_path                   | ./fastlane/metadata/android                        |
| json_key                        | ....\my_archive_folder\ci-cd\CENSORED_FOR_THE_GITHUB_ISSUE.json |
| skip_upload_apk                 | false                                              |
| skip_upload_aab                 | false                                              |
| skip_upload_metadata            | false                                              |
| validate_only                   | false                                              |
| check_superseded_tracks         | false                                              |
| timeout                         | 300                                                |
| deactivate_on_promote           | true                                               |
| ack_bundle_installation_warning | false                                              |
+---------------------------------+----------------------------------------------------+
[20:58:47]: Preparing to upload for language 'en-US'...
[20:58:47]: Preparing to upload for language 'fr-FR'...
[20:58:48]: Uploading all changes to Google Play...
[20:58:49]: Successfully finished the upload to Google Play
+------+----------------------+-------------+
|             fastlane summary              |
+------+----------------------+-------------+
| Step | Action               | Time (in s) |
+------+----------------------+-------------+
| 1    | default_platform     | 0           |
| 2    | bundleRelease        | 6           |
| 3    | upload_to_play_store | 3           |
+------+----------------------+-------------+
[20:58:49]: fastlane.tools finished successfully �

Environment

  ✅ fastlane environment ✅
Stack

Key
Value

OS
UNKNOWN

Ruby
2.7.2

Bundler?
true

Git
git version 2.28.0.windows.1

Installation Source
C:/tools/ruby27/bin/fastlane

Host
Unknown  ()

Ruby Lib Dir
C:/tools/ruby27/lib

OpenSSL Version
OpenSSL 1.1.1g  21 Apr 2020

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

System Locale

Variable
Value

LANG

LC_ALL
C.UTF-8
✅

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

default_platform(:android)

platform :android do
  desc "Runs all the tests"
  lane :test do
    gradle(task: "test")
  end

  desc "Submit a new Beta Build"
  lane :beta do
    gradle(task: 'bundle', build_type: 'Release')
    #versions = google_play_track_version_codes(track: "internal")
    #version_code = versions[0]

    upload_to_play_store(
     track: 'internal',
     skip_upload_changelogs: true,
     skip_upload_images: true,
     skip_upload_screenshots: true,
    )

    # sh "your_script.sh"
    # You can also use other beta testing services here
  end

  desc "Deploy a new version to the Google Play"
  lane :deploy do
    #gradle(task: 'bundle', build_type: 'Release')
    #upload_to_play_store
  end
end

`./fastlane/Appfile`
json_key_file("..\\..\\my_archive_folder\\ci-cd\\CENSORED_FOR_THE_GITHUB_ISSUE.json") # Path to the json secret file - Follow https://docs.fastlane.tools/actions/supply/#setup to get one
package_name("CENSORED_FOR_THE_GITHUB_ISSUE") # e.g. com.krausefx.app

fastlane gems

Gem
Version
Update-Status

fastlane
2.179.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.4.0

rake
13.0.3

CFPropertyList
3.0.3

public_suffix
4.0.6

addressable
2.7.0

artifactory
3.0.15

atomos
0.1.3

aws-eventstream
1.1.1

aws-partitions
1.435.0

aws-sigv4
1.2.3

jmespath
1.4.0

aws-sdk-core
3.113.0

aws-sdk-kms
1.43.0

aws-sdk-s3
1.93.0

babosa
1.0.4

bundler
2.1.4

claide
1.0.3

colored
1.2

colored2
3.1.2

highline
1.7.10

commander-fastlane
4.4.6

declarative
0.0.20

declarative-option
0.1.0

digest-crc
0.6.3

unf_ext
0.0.7.7

unf
0.1.4

domain_name
0.5.20190701

dotenv
2.7.6

emoji_regex
3.2.2

excon
0.79.0

faraday-net_http
1.0.1

multipart-post
2.0.0

ruby2_keywords
0.0.4

faraday
1.3.0

http-cookie
1.0.3

faraday-cookie_jar
0.0.7

faraday_middleware
1.0.0

fastimage
2.2.3

gh_inspector
1.1.3

jwt
2.2.2

memoist
0.16.2

multi_json
1.15.0

os
1.1.1

signet
0.15.0

googleauth
0.16.0

httpclient
2.8.3

mini_mime
1.0.3

uber
0.1.0

representable
3.0.4

retriable
3.1.2

google-api-client
0.38.0

rexml
3.2.4

webrick
1.7.0

google-apis-core
0.3.0

google-apis-iamcredentials_v1
0.2.0

google-apis-storage_v1
0.3.0

google-cloud-env
1.5.0

google-cloud-errors
1.1.0

google-cloud-core
1.6.0

google-cloud-storage
1.31.0

json
2.5.1

mini_magick
4.11.0

naturally
2.2.1

plist
3.6.0

rubyzip
2.3.0

security
0.1.3

simctl
1.6.8

slack-notifier
2.3.2

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

nanaimo
0.3.0

xcodeproj
1.19.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.1

generated on: 2021-03-26

I found what was missing to upload my bundle so i'm happy :) ! (But warning message saying couldn't find apk still here)
I think this is missing from the documentation to upload a bundle: ruby aab: '../build/app/outputs/bundle/release/app-release.aab',
upload_to_play_store(
     track: 'internal',
     aab: '../build/app/outputs/bundle/release/app-release.aab',
     skip_upload_changelogs: true,
     skip_upload_images: true,
     skip_upload_screenshots: true,
    )


text:
Fastlane "increment_build_number" not working after update Fastlane or xcode...

Hi!
Just updated both Fastlane and Xcode to the latest version and both increment_build_number and increment_version_number are not working anymore... It doesn't throw an error, it just doesn't update.
The xcode project hasn't been changed at all... The code is pretty straight forward:
increment_version_number version_number: $build_number```

### Complete fastfile:

```ruby
platform :ios do

	desc "Test!"
	lane :test do

		# This doesn't require any thing, because it is all done in the "Before all lane"
		set_info_plist_value(path: './Roadmap-Info.plist', key: 'CFBundleIdentifier', value: "$(PRODUCT_BUNDLE_IDENTIFIER)")

		# Set identifier
		update_app_identifier(
		  xcodeproj: 'Roadmap.xcodeproj', # Optional path to xcodeproj, will use the first .xcodeproj if not set
		  plist_path: 'Roadmap-Info.plist', # Path to info plist file, relative to xcodeproj
		  app_identifier: 'com.demo.test' # The App Identifier
		)

        increment_build_number build_number: '6.1.2'

        increment_version_number version_number: '20160322'
	end

    # After no errors!
    after_all do |lane|

		p "We finished succesfuly!"

    end

    # Error!
    error do |lane, exception|
	    puts "We crashed.... Send me an e-mail!"
        # Do something!
    end
end

Output:
[15:05:18]: ------------------------------------
[15:05:18]: --- Step: increment_build_number ---
[15:05:18]: ------------------------------------
[15:05:18]: $ cd /Users/roadmap/Documents/MobiPoweriOS && agvtool new-version -all 6.1.2
[15:05:18]: ▸ Setting version of project Roadmap to:
[15:05:18]: ▸ 6.1.2.
[15:05:19]: ▸ Also setting CFBundleVersion key (assuming it exists)
[15:05:19]: ▸ Updating CFBundleVersion in Info.plist(s)...
[15:05:19]: ▸ Cannot find "Roadmap.xcodeproj/../				<key>INFOPLIST_FILE</key>"
[15:05:19]: --------------------------------------
[15:05:19]: --- Step: increment_version_number ---
[15:05:19]: --------------------------------------
[15:05:19]: $ cd /Users/roadmap/Documents/MobiPoweriOS && agvtool new-marketing-version 20160323
[15:05:20]: ▸ Setting CFBundleShortVersionString of project Roadmap to:
[15:05:20]: ▸ 20160323.
[15:05:20]: ▸ Updating CFBundleShortVersionString in Info.plist(s)...
[15:05:20]: ▸ Cannot find "Roadmap.xcodeproj/../				<key>INFOPLIST_FILE</key>"

Environment
fastlane version (fastlane -v): 1.67.0
xcode version: 7.3
Do you use bundler, rbenv or rvm? RVM

Hi @mcactive. Thanks for letting us know. Can you edit to include your fast file?
Follow the template here: https://github.com/fastlane/fastlane/blob/master/ISSUE_TEMPLATE.md
Also, what version of Xcode are you using?
Thanks!

Hi!
Yeah, I've stripped the Fastfile to exclude all the errors and even the simplest doesn't work. I've edited the post!
Xcode version is the latest, 7.3

@mcactive I found a similar issue from a long time ago about a bug with cocapods. Are you using cocapods?  Could you check your agvtool https://github.com/CocoaPods/CocoaPods/issues/613?

@i2amsam Hi Sam, yes, we are using cocoapods and using the cocoapods action in Fastlane as well.
The file appears to be XML instead of the OpenStep format.. Is there an easy way to fix it?

@mcactive does this solution work? https://github.com/CocoaPods/CocoaPods/issues/613#issuecomment-9695254 it seems like a cocapods issue rather than a fastlane issue.

@i2amsam you're right... Saving something in xcode and running only
cd /Users/mcactive/Documents/Project && agvtool new-version -all 6.1.2
works...
But it's weird if it is a cocoapods issue as it always worked and after updating fastlane and xcode it broke... Should I make an issue at CocoaPods?

@mcactive I agree, super weird.  I don't see anything in the fastlane release that seems suspicious, and we didn't run into it with an updated xCode, let's see if anyone else reports it.

@i2amsam updating to the beta version of cocoapods fixed the issue. This also installs "xcodeproj" beta which fixes a bug in Xcode 7.3:
1.0.0.beta.3
@segiddins segiddins released this 29 days ago · 3 commits to master since this release

Bug Fixes

Fix ASCII .xcodeproj serialization with Xcode 7.3.

Ran into the same issue. We're using Cocoapods as well, but it isn't part of our fastlane flow. However, I do have a custom action that use the Xcodeproj gem that is used internally by Cocoapods in order to modify the project to swap out app icons, fonts, etc.
Based on your current finding I would suspect that a change in the xcodeproj structure in Xcode 7.3 has caused an incompatibility with the Xcodeproj gem.
For now I'm working around the issue by having the increment_build_number and increment_version_number actions be executed first in my lane. I had initially tried to get around the issue by running my custom action after those above two actions, but was still running into conflicts. Once I moved the two increment actions above update_project_team, update_info_plist, and update_app_identifier then things begun to work fine.

@vfog I think you are exactly right. I'm seeing the same, and not using cocoapods.

@mcactive @vfog I've verified updating to xcodeproj 1.0.0 beta 3 fixes this for me. I am not using cocoapods.
Fastlane may need to bump the minimum version of xcodeproj to resolve this.

@mcactive I believe this one should be reopened until its resolved.

Didn't know fastlane also used Xcodeproj gem. Will reopen it until further notice.

You can see a few requires here:
https://github.com/fastlane/fastlane/search?p=1&q=xcodeproj&utf8=%E2%9C%93

Look like its defined here.
I think this needs to be bumped to minimum 1.0.0-beta3

@mcactive and @kcharwood Thanks! :+1: I put a comment over in #3945, it appears we won't be able to bump our min version because that would put fastlane in conflict with cocoapods 0.39 which is still working ok for Xcode 7.2 users. Eek.  I'd like to close this and track it in the other issue if that sounds right to you folks.

@kcharwood I'm closing this issue out so we can track on the other ticket. Thanks for working with us!

You can put the Fastfile in a subdir =>  Dir_where_xcodeproj/Fastlane/Fastfile

source: gharchive/issue

authors: StrangeDays TKBurner i2amsam kcharwood mcactive vfog

repo: fastlane/fastlane

license: MIT

license_type: permissive

license_source: github-api


text:
increment_version_number & increment_build_number

Scenario:
I have two target: one is main target, the other is test target.
when I want to increase the version number and build number, I mean the main target's, but these two actions change all target.
can these actions expose more params like :target ? although I can workaround to use update_info_plist action.

I would recommend using the workaround if you can as that's not something that is on our radar.

authors: MickeyHub vpolouchkine


text:
Removed * from fastlane docs for required parameters

This led to confusion, in particular when a default value is set anyway

via @irace

:ship: it

@KrauseFx Can you please shed some more light on how this action is expected to work?
When using Crashlytics for crash reporting only (distributing through TestFlight), I have this build phase configured:

However, I still see this.

I expected I would need to use the upload_symbols_to_crashlytics action to fix this – but you are saying it should Just Work without any Fastlane actions at all?

source: gharchive/pull-request

authors: KrauseFx irace mfurtak


text:
updep: dep ensure -v -update

Like https://github.com/fatih/color/pull/86
BTW that branch ^ can be deleted now.

Hi @fenollp
Is there are reason we need to update the deps? Does it fixes something? I'm usually not in favor of changing it unless it's fixes a bug or improves the package

Alright, I'm closing this as I think it's not needed. Thanks for opening it though,  please feel free to reopen if the dep update is needed. Thanks.

authors: fatih fenollp

repo: fatih/color

license: mit

license_source: bigquery


text:
Transform arbitrary unicode characters in e-invoice XML to acceptable format to avoid XML validation errors

Is your feature request related to a problem? Please describe.
When invoice fields contains hieroglyphic characters (maybe other non-latin too) e-invoice sending failed with XML validation error (HTTP 422, Unprocessable Entity) like:
 {"error":{"message":"Validation XML",
        "validation_result":{
            "xml_errors":[
                "Nei dati del Cessionario Committente (cliente), il campo Nome non \u00e8 nel formato valido",
                "Nei dati del Cessionario Committente (cliente), il campo Cognome non \u00e8 nel formato valido",
                "Nei dati del Cessionario Committente (cliente), il campo Comune non \u00e8 nel formato valido"
]}}}

Describe the solution you'd like
Automatically transform non-latin unicode characters (if any) in e-invoice (XML content?) to the format accepted by the remote service (SDI?).
Guess it's \uXXXX notation, maybe by json.dumps(dict, ensure_ascii=True).
Describe alternatives you've considered
Maybe mangling ei_raw for the fields with non-latin characters.

Hi @vmspike
we suggest you perform this operation while preparing the ei_raw, instead of while during the JSON dumps. Is it possible for you?
Thanks
Mauro

Hi @valmoz, thank you for reply!
It should be a way to get rid of this error on our side, and I've started to investigate it.
Will continue if you not going to approve this feature request.
Other non- e-invoice FIC parts (which I know) work with unicode just fine.
So for my mind this task looks more suitable for the SDK itself, that's why I've opened this issue,  it's just data format/encoding conversion for tightly related service (with not clear format requirements, that ascii \u???? conversion is just my assumption).
It would decrease complexity of the code for the end user and amount of hacks, such convenience is an advantage of using SDK, so thought you may consider it to be useful for other users too.

Hi @vmspike
I think this is not a problem of the SDK itself but of the XML validation functionality on the API side.
If you want to be sure if the problem is on the SDK side or the API side you can try to obtain the generated JSON as explained here and try to send it with the API Reference.
Also, if you want to verify the e-invoice instead of directly sending it you can use the Verify e-invoice XML functionality as explained here; this functionality uses the same verification functionality without actually sending the invoice to the SDI, so it could be useful for testing.
Thanks
Mauro

authors: valmoz vmspike


text:
Feature Request: Add support to Seed Data to the Database

Problem
I know the focus of the lib is to support migration schemas, and does NOT intended to support any kind of data migration.
But today once my database is created for the first time I seed some data, which was part of my migration scripts once using faunadb-migrate lib.
Request:
Support Seed Data to be part of the migration scripts, in this case is not possible to auto-generated a down script automatically so my propose is to support seed data scripts where the up and down scripts should be typed by the developer.
Current Workaround:
Based on Fwitter I create a populate scripts this can support my data seed, this force me to keep out of my CI/CD pipeline for simplicity and the developers execute it manually if the database was created by the first time.
Here the scripts if someone would like to use:

Create a js script to populate your database:

Example: https://gist.github.com/brunosmm/50f707f2e5fe2e3baf25d61b426850b3

Add a new folder seed to hold the scripts:

Create the scripts using the model from faunadb-migrate with up and down:

Example: https://gist.github.com/brunosmm/dba3798b5f868a2c24aaf815d906ba1c

Add to the npm package a new script:

Execute using npm or yarn:
yarn populate FAUNA_ADMIN_KEY

@fauna-brecht, If I add an FQL script in a migrations folder to run together with some create/update scripts to populate data in some docs, would that run? Or the tool only execute FQL with UPDATE/CREATE and so on?

It would not work, we would need a different approach for data. I still think seed data doesn't really fit the migrations problem.
Should the seed data run every time or only on a specific migration? Should it be 'unseeded' if you roll back?
So I'm guessing you are rather looking for data migrations and not necessarily seed data? Is that correct?

Indeed this is more like a data migration than seed but should be linked with some DB migration and coupled with specifics UDF/Index.
What I am missing is more about the data structure, like we decide to add a new object structure in some collection from now on, but means the docs that were created before does not have it and if I execute my index search would not work since some objects have this and others not, here a good example https://fauna-community.slack.com/archives/CM29P7A81/p1622078419077100.
So what I would like is, once I create this new Index/UDF who use some new data from the docs be able to execute a script together to add a default value to the other docs but this would need to be executed together with the migration and only once.
The rollback is a good point since is not a SQL DB and the data does not need to follow a specific structure would not need to Update the object to remove it, but ideally would be the best scenario to not keep unnecessary data. In this case, rollback cannot be created automatically and would need to be defined by the user.

authors: brunosmm fauna-brecht

repo: fauna-labs/fauna-schema-migrate


text:
Ridiculous huge amount of time left for pokemons

In the previous picture you can see that 2 pokemons have a huge amount of time left to expire, while others have a normal amount of time left to expire. There's a few more like this in the area.
As the problem is not crashing, or malfunctioning I didn't know what type of log to include in the Issue.

See #260.

authors: LuissRicardo chezbgone

repo: favll/pogom


text:
Export of overloaded functions and operators

It seems like Fay is not correctly exporting some infix operators and functions like return. I have a simple Parser library, where (as we have no type classes) I export e.g. bind directly and use it in desugared style. However, the bind operator does not work outside the module, whereas inside it works and once I change the (>>=) operator to the name bind it compiles correctly. Btw GHC compiles the file in all variants (for the Haskell server side implementation).
Unable to compile Fay module "Cdn/FtpBrowser":

ghc:
fay-shared/Shared/Cdn/FtpBrowser.hs:54:76: error:
    parse error on input ‘P.>>=’

CallStack (from HasCallStack):
  error, called at ./Yesod/Fay.hs:505:3 in yesod-fay-0.8.2-EnznqQxANr7EJSLbxziD2P:Yesod.Fay

Similarly I cannot export a function named return:
Unable to compile Fay module "Cdn/FtpBrowser":

unable to resolve qualified names (this might be a bug):P.return

If  I change the name it works. Are there different keywords in Fay?

Unqualified issues worked.

repo: faylang/fay


text:
Tiny self-toss to creeps can result into stucking each other.

Reported by MouJiaoZi:

As much as I try, I cannot reproduce it. Closing for now.

authors: AtroCty Shushishtok


text:
Chapter 10: Discrepancy between problem statement and Keras implementation in timeseries_dataset_from_array()

Description:
Reading the section 10 Deep learning for timeseries, there appears to be a potential discrepancy between the problem statement and the actual implementation.
Problem Statement:
The problem statement, as described in section 10.2.1, outlines a scenario where temperature data and other variables for 5 days, sampled once per hour, are provided. The objective is to predict the temperature 24 hours ahead.
Concern:
According to the problem statement, there are 120 samples in 5 days (24 samples per day). The dataset should consist of sequences representing 5 days of data, with each sequence containing a maximum of 120 samples.
Keras Implementation:
However, when utilizing the timeseries_dataset_from_array() function with parameters sampling_rate = 6 and sequence_length = 120, it generates sequences corresponding to 30 days (4 samples per day). This seems to deviate from the problem statement's objective of predicting temperature with data from 5 days, not 30.
Proposed Solution:
One potential solution could be adjusting the sequence_length parameter to 20. This adjustment would ensure that sequences contain data from 5 consecutive days (4 samples per day using sampling_rate = 6), aligning with the problem statement's requirements.
Request for Clarification:
I'd appreciate clarification on whether my analysis is accurate and if the implementation aligns with the intended problem statement. If not, guidance on how to correctly utilize the timeseries_dataset_from_array() function for the specified problem would be valuable.
Thank you for your attention to this matter.

The original data contains 6 sets of data per hour. So sampling_rate=6 means 1 set of data per hour. The book description is correct.

authors: juandevprojects shenchenbing


text:
Save activation output to disk

Hi,
I want to save the activation output from inside a step function. How can this be done in keras?

Refer to he FAQ for retrieving the activation of an intermediate layer:
https://keras.io/getting-started/faq/#how-can-i-obtain-the-output-of-an-intermediate-layer
Once you have the activation values (in the form of a numpy array), you can save it, e.g., with np.save.

authors: dr-costas kgrm

repo: fchollet/keras


text:
subprocess options broken with pathos change

this merge allowed redirection of java output:
https://github.com/fcollman/render-python/pull/71
since the pathos cut commit https://github.com/fcollman/render-python/commit/d6bc7c5f0b99b93ce58319351fda48b087f10c2c
it breaks:
renderapi.client.import_tilespecs_parallel(outputname,tspecs,sharedTransforms=shared_tforms,render=ingestconn,close_stack=False,stderr=stdeo,stdout=stdeo)
  File "<decorator-gen-36>", line 2, in import_tilespecs_parallel
  File "build/bdist.linux-x86_64/egg/renderapi/client.py", line 50, in renderclientaccess
  File "build/bdist.linux-x86_64/egg/renderapi/client.py", line 377, in import_tilespecs_parallel
  File "/home/danielk/anaconda2/envs/emaligner/lib/python2.7/multiprocessing/pool.py", line 253, in map
    return self.map_async(func, iterable, chunksize).get()
  File "/home/danielk/anaconda2/envs/emaligner/lib/python2.7/multiprocessing/pool.py", line 572, in get
    raise self._value
ValueError: I/O operation on closed file

this line is now missing, but adding it back in did not fix the problem:
https://github.com/RussTorres/render-python/blob/3774b4c73020a3b5cefcadbad3de10ec50429df3/renderapi/client.py#L487

The problem here is that filehandlers don't stay open (object repr is <closed file '<uninitialized file>', mode '<uninitialized file>' at 0x7f0ed2a15390>) with the new multiprocessing implementation.  I'm not sure what the best way to handle this is -- we can work around it with initializers and globals on a per-process basis or I can push forward on allowing external multiprocessing pool libraries (reintroducing pathos as an option.)

I think this is addressed by #87 @djkapner why don't you try it out, if you are happy you can close the issue.

Also worth noting: using a multiprocess.pool.ThreadPool with an __enter__ and __exit__ will keep the filehandlers open as it doesn't need to fork.  I'm not sure how well this works for all our use cases (GIL limited), but it could be useful to avoid the pathos dependency assuming java is doing the heavy lifting.

authors: RussTorres djkapner fcollman

repo: fcollman/render-python


text:
feat: removing the test GitHub profiles.

Deleting the two contributors that were used as example.

Duplicate of #66

authors: Yudi gustavobecelli

repo: fct-coders/hacktoberfest-presencas


text:
Colored highlighting of lines with keywords in Output panel.

As described in https://github.com/fdorg/flashdevelop/issues/563

Thank you grapefrukt!
We like the idea behind this feat but we think another implementation would be better and and the same time get rid of the current int coloring as it sometimes causes undesired partial removals of traces among another issues.
We need to think this thru little more but we will address this in FD5.

Done to FD5.

authors: Meychi grapefrukt

repo: fdorg/flashdevelop


text:
Fix auto selector when using Wayland

Prior to this change, rofi-rbw only checked in wayland if rofi is installed and tried immediately to use it, even when not in X. Thus auto-choosing the selector in wayland does not work.

Hey, thanks for the PR! 🙂
The problem is that there is at least one rofi fork for Wayland, so we cannot simply filter for Xorg.

Hmm, I see. Is this fork worth it, that the autoselector does not work on wayland, when the original rofi installed? I mean this is the autoselector, which should work for most cases, in my opinion. For other cases, there is still the configuration file.

Or do you have any suggestions to improve?

I personally use that fork on both X and Wayland, so I see some benefit to the way things are 😉

I mean this is the autoselector, which should work for most cases, in my opinion.

I totally agree that it should work as well as it can. But excluding the rofi fork is clearly wrong (it does work, after all). I would also guess that the number of people who have rofi installed but use Wayland is rather small. What do you think?
And finally, rofi (and its fork) is still by far the selector with the most features, so I would want to prefer it over other, less fancy ones.
Maybe we can check whether it's the fork or the original rofi by calling rofi -version? The fork return Version: 1.7.5+wayland2, so if we can find wayland in there, it is supported?

On second thought, my need for this change hs vanished. I had simply Xwayland not running... I would close this.

authors: fdw mbrunnen

repo: fdw/rofi-rbw


text:
required() of value false throws fieldname is null

When trying to require boolean fields, value false should not thow an error.
Haven't found any related issues.
It's independent PR.

Thank you!

authors: antarasi eddyystop

repo: feathers-plus/feathers-hooks-common


text:
Support printing features and returning keys when getting features from registry

Description

Provide function to show features details (including keys) in json format and return a [feature_name] = [typed keys] dict when 'get_features_from_registry'

How was this PR tested?

Tested locally, and got log like below:

Modified one of existing test cases to print out features details and to return key dicts

Does this PR introduce any user-facing changes?

[ ] No. You can skip the rest of this section.
[ ] Yes. Make sure to clarify your proposed changes.

LGTM, thanks @enya-yx for this!

authors: enya-yx xiaoyongzhu

repo: feathr-ai/feathr


text:
Explicitly use Bundler 1.17.3

Fixes #19

We're using our fork of this buildpack in our apps and I confirmed that this fixed our failing builds for us this morning.

Thanks for your contribution and documentation of the investigation!

authors: febeling nickgsc

repo: febeling/webpack-rails-buildpack


text:
add IxData struct to handle write and read bytes

[x] Add a struct to handle writing and reading bytes
[x] add methods to handle optional pubkey writing to ix buffer
[x] this will help to avoid few cus if we have multiple optional fileds in ix data and we have to check each parent field if its optional and then write to buffer accordingly

@Nagaprasadvr Thanks for your contribution. While the idea of a helper struct is very nice, unfortunately it will use more compute units than the "manual" way due to the capacity checks and incrementing the size counter. At the same time the main benefit it provides is that we don't need to manually keep track of the size, but it is probably something that we will be doing anyway because we need to determine the size to allocated the array.
The overall idea of the instruction builders is to be as lightweight as possible, since they will be used in your program on-chain.

Makes sense thanks for the review closing thks !

authors: Nagaprasadvr febo

repo: febo/pinocchio


text:
Include git hash in UI

For cases like #510 it would be great to see the git hash at first glance so we know which version we are dealing with. I did the same for Webimint in the footer to always know what is deployed:

Is anyone currently working on implementing the display of the git hash in the user interface? If not, I would be interested in contributing to this issue.

I'm not aware of anyone working on it, feel free to open a PR :)

WIP 👍

Hi, you can change the status to closed, the solution is merged.

authors: elsirion kleyberthsantos

repo: fedimint/ui


text:
🛑 무리 네트워크 is down

In 097e8f3, 무리 네트워크 (https://muri.network/api/v1/instance/activity) was down:

HTTP code: 403
Response time: 673 ms

Resolved: 무리 네트워크 is back up in 6fa98f3 after 20 minutes.

repo: fediverses-kr/upptime-api


text:
feat(settings): added auto-detect direnv program

Hi, I want to add a simple new thing: auto-detect direnv program.
On startup plugin can detect direnv program in currect PATH variable. If plugin can't find file, then return default empty string(previous version of default value in direnvSettingPath).
Also I changed:

exported nix-shell configuration to shell.nix file (it's helpful for non-flake users)
changed channels option from publishPlugin, because plugin SDK change channels option to val

Hi, thanks for your contribution!
I'm not quit sure I understand the reasoning. If direnv is found in $PATH it would also be correctly resolved by the call to GeneralCommandLine.createProcess() which in turn calls GeneralCommandLine.validateAndPrepareCommandLineForLocalRun().
It looks like you too use Nix(OS) so the path would probably change rather often without having much value.
Am I missing something?

I could a better explenations why I want to add this a little feature. My bad. So, my causes to create the PR was problem with finding direnv execution. In previous versions of jetbrains products(I use Golang, Intellij, Pycharms and more), I had a problem with detecting direnv in $PATH variable. It was in versions between 2022-2023. I solved this problem when I set a manually path to direnv executable so I thought, plugin can autodetect aboslute path to direnv.
I did double check, if this problem exists on my currect NixOS configuration and Goland version(I using 2024.1). The anwser is... no, problem solved even I removed aboslute path to direnv. Perhaps, it was bug on my OS so this feature is unnecessary if my main problem doesn't exist.
I can closed this PR but before that, I have a question to you. I think add a command to plugin, that reload envrioment varaiables(aka. executes direnv reload). For me, it's a bit annoying when I changes something in my shell.nix file and I have to relaunch Intellij or Golang just to load my a new version of program or environment variables. What do you think? Is it worth or not?

authors: Wittano fehnomenal

repo: fehnomenal/intellij-direnv


text:
Unable to run server on any port other than default

💬 Questions and Help
Running using docker-compose, setting port to something like 30002 in the yaml file and also changing it in options.json file, when restarting the image, it resets back to port 30000.  How would I run an instance using a different port?
foundry:
    container_name: fvtt
    image: felddy/foundryvtt:release
    restart: "unless-stopped"
    volumes:
      - '/data/docker/foundryvtt:/data'
    environment:
      - FOUNDRY_PASSWORD=password
      - FOUNDRY_USERNAME=user
      - FOUNDRY_ADMIN_KEY=anotherpassword
    ports:
      - "30002:30002/tcp"
    network_mode: host

Got it to work by removing the
mode:host

Glad you got it working!  🎉
Don't hesitate to me know if you have any other questions about the project.

authors: felddy kalebr

repo: felddy/foundryvtt-docker


text:
🛑 PasImpCh is down

In 8c797ad, PasImpCh ($SITE_PASIMPCH) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PasImpCh is back up in d673050 after 1 hour, 28 minutes.

repo: felipesbs/bitrate-uptime


text:
Log-Files

Siehe Tabelle "OriGami-LogFiles.pdf"

Ergebnisse Auswertung "Navigationsaufgaben", "Selbst-Lokalisation" und "Infos"

Bei "Waypoint_reached" benötige ich die gleichen Infos wie bei "OK_clicked": Aktuelle Position und Blickrichtung (bei Erscheinen der Bestätigung, dass das Ziel erreicht wurde) inkl. GPS accuracy, MapViewpoint...
Bei "Informationen" drückt der Nutzer ja ebenfalls "OK". Hier benötige ich ebenfalls das OK_clicked-Event mit all den zugehörigen Infos wie bei den Navigationsaufgaben mit Eingabebestätigung.
Ein weiterer Reiter zur Bewegung des Spielers während einer Aufgabe wird benötigt (d.h. die Bewegungs- und Blickrichtungsdaten des Spielers zwischen Aufgabeninitialisierung und Aufgabenlösung)... Bisher sind diese Daten ja nur isoliert unter "Waypoints" zu finden.
Neben "Waypoints" und "Events" wäre noch eine Aufführung aller Klick-Events hilfreich (d.h., wann hat der Nutzer wohin auf die Karte, Buttons usw. geklickt. Lässt sich das umsetzen?

Ergebnisse Auswertung "Objekt-Lokalisation" und "Richtungssuche"
folgt noch...

Unklares (bitte kurze Erklärung)

Wofür steht "_id"?

Das ist die ID des Tracks. Jeder Track bekommt eine eindeutige ID

Bei Waypoints sagen mir unter "position" die Punkte "heading" und "speed" nichts.

Das sind die Richtungs- und Geschwindigkeitsdaten die ich vom GPS Modul bekomme

Der Punkt "mapViewpoint" sagt mir ebenfalls nichts.

"mapViewport" beschreibt die aktuelle einstellung der Karte. Das beinhaltet Bounding Box, Zoom, Rotation und Tilt
Allgemeines

Angabe der Uhrzeit stimmt nicht

Das ist UTC Zeit und ist die Zeit als das der Track zum Server geladen wurde

Grundlegende Infos zum Spiel: Die Spiele-Name wird nicht angezeigt. Alle wichtigen Infos zum Spiel sollten oberhalb von "waypoints" aufgeführt werden ("name" und "time" (Start- und Endzeitpunkt des Spiels)...).

Das ist Absicht. Damit Daten nicht doppelt gespeichert werden, wird nur die referenz (id von game) zum Spiel im track gespeichert. Den Namen habe ich jetzt aber trotzdem hinzugefügt. Start und Ende des Spiels wurden hinzugefügt.

INIT_TASK: Ein weiterer großer Unterpunkt pro Aufgabe (auch bei "Information") wird benötigt (z.B. "players_movement") und zwar zur Bewegung des Spielers während der Aufgabe (d.h. die Bewegungs- und Blickrichtungsdaten des Spielers zwischen Aufgabeninitialisierung und Aufgabenlösung)... Bisher sind diese Daten ja nur isoliert unter "Waypoints" zu finden.

TBD

ON_OK_CLICKED: (z.B. bei Selbstlokalisation, Objektlokalisation, Navigation zur Zielfahne mit Eingabebestätigung usw.) benötige ich die Info darüber, ob die Lösung des Spielers als richtig oder falsch durchgegangen ist.

Ist eingebaut

Bei ON_MAP_CLICKED benötige ich zusätzlich die Info über aktuelle Position und Blickrichtung.

position ist die GPS Position und clickPosition die Karten Klick Position

Neben "Waypoints" und "Events" wäre noch eine Aufführung aller Klick-Events hilfreich (d.h., wann hat der Nutzer wohin auf die Karte, Buttons usw. geklickt).

Ok und Map clicks sind schon in events
Navigationsaufgaben

Bei WAYPOINT_REACHED benötige ich die gleichen Infos wie bei "OK_CLICKED": Aktuelle Position und Blickrichtung (bei Erscheinen der Bestätigung, dass das Ziel erreicht wurde) inkl. GPS accuracy, MapViewpoint...

Ist eingebaut

Manchmal tritt WAYPOINT_REACHED zweimal hintereinander auf. Fehler?

Informationen

Bei "Informationen" drückt der Nutzer ja ebenfalls "OK". Hier benötige ich ebenfalls das OK_CLICKED-Event mit all den zugehörigen Infos wie bei den Navigationsaufgaben mit Eingabebestätigung.

Ist eingebaut
Themenaufgaben

Die Menge an Daten auf das Wesentliche reduzieren: So ist es z.B. nicht wichtig, für jede Themenaufgabe unter "developer" oder unter "items" angezeigt zu bekommen, welche weiteren Einstellungsmöglichkeiten theoretisch möglich gewesen wären. Wie bei den Navigationsaufgaben reicht hier alles zur gewählten Aufgabe. Unter "question-type" wird außerdem unter "settings" immer "answer-type" angeführt. Aber "answer-type" ist auch noch einmal ein eigener Punkt. Der große Oberpunkt "answers" scheint ebenfalls überflüssig zu sein.

Die neuen Aufgaben sind jetzt kleiner.

Antworttyp: "...antwortet durch Auswahl aus Fotos (Multiple Choice)" Hier fehlen die angeklickten Antworten (event: PHOTO_SELECTED oder so ähnlich) sowie seine aktuelle Position und Blickrichtung. Wenn sich der Spieler mehrfach korrigiert, bevor er OK drückt, soll dies auch angezeigt werden.

Ist jetzt eingebaut

Antworttyp: "... mit der Aufnahme eines Fotos" Hier fehlt das Foto des Nutzers (neues event: PHOTO_TAKEN oder so ähnlich) sowie seine Position und Blickrichtung während der Fotoaufnahme.

Ist jetzt eingebaut

In den "Settings" von "Richtungssuche" stehen nur die Daten zu "Direction". Kann es sein, dass man im Einstellungsscreen (wenn der rote Pfeil gesetzt wird) gar keinen Ort festlegt, sondern ausschließlich eine Richtung? Wie unter Issue #54 angemerkt, soll der Spieleentwickler ab jetzt aber eine Position UND eine Blickrichtung festlegen.

Ist jetzt eingebaut

Alles, was hier nicht mehr aufgeführt ist, habe ich überprüft und funktioniert.

Grundlegende Infos zum Spiel: Die Spiele-Name wird nicht angezeigt. Alle wichtigen Infos zum Spiel sollten oberhalb von "waypoints" aufgeführt werden ("name" und "time" (Start- und Endzeitpunkt des Spiels)...).

Das ist Absicht. Damit Daten nicht doppelt gespeichert werden, wird nur die referenz (id von game) zum Spiel im track gespeichert. Den Namen habe ich jetzt aber trotzdem hinzugefügt. Start und Ende des Spiels wurden hinzugefügt.

CreatedAt ist nicht die Startspielzeit, sondern das Ende des Spiels...

INIT_TASK: Ein weiterer großer Unterpunkt pro Aufgabe (auch bei "Information") wird benötigt (z.B. "players_movement") und zwar zur Bewegung des Spielers während der Aufgabe (d.h. die Bewegungs- und Blickrichtungsdaten des Spielers zwischen Aufgabeninitialisierung und Aufgabenlösung)... Bisher sind diese Daten ja nur isoliert unter "Waypoints" zu finden.

TBD

ON_OK_CLICKED: (z.B. bei Selbstlokalisation, Objektlokalisation, Navigation zur Zielfahne mit Eingabebestätigung usw.) benötige ich die Info darüber, ob die Lösung des Spielers als richtig oder falsch durchgegangen ist.

Ist eingebaut

Muss ich noch nachsehen...

Manchmal tritt WAYPOINT_REACHED zweimal hintereinander auf. Fehler?

Antworttyp: "...antwortet durch Auswahl aus Fotos (Multiple Choice)" Hier fehlen die angeklickten Antworten (event: PHOTO_SELECTED oder so ähnlich) sowie seine aktuelle Position und Blickrichtung. Wenn sich der Spieler mehrfach korrigiert, bevor er OK drückt, soll dies auch angezeigt werden.

Ist jetzt eingebaut

Muss ich noch nachsehen...
....
Sind alle Map-Feature Einstellungen drin?

Alles passt, außer:

[ ]  Antworttyp "MAP_DIRECTION" und "MAP_POINT": Unter "ON_OK_CLICKED" fehlt die geklickte Position des Spielers und/ oder der geklickte Winkel des Spielers (und das bei jedem Aufgabentyp!)
[ ] Antworttyp "Multiple Choice": Bei allen Aufgabentypen sollte das angeklickte Foto auch unter dem Event "PHOTO_SELECTED" angeben werden.
[ ] TRUE und FALSE (richtig/ falsch gelöst) sollte auch beim Antworttyp ON_MAP_CLICKED angezeigt werden (bei allen Aufgabentypen)

[ ] In meinem R File werden die durch den Spielentwickler gesetzten Winkel nicht wiedergefunden
[ ] Sowie der Question Type
[ ] Und das durch den Spieler geklickte Foto...

Hast du die Namen der Daten verändert? Oder fehlen die Daten jetzt ganz?

Ich habe jetzt nochmal überprüft, ob ich mit den Daten arbeiten kann. Folgendes fehlt:

[ ] TRUE und FALSE (richtig/ falsch gelöst) sollte auch beim Antworttyp ON_MAP_CLICKED angezeigt werden (bei allen Aufgabentypen) --> Das ist tatsächlich sehr wichtig. Kannst du eine Evaluation der geklickten, aber nicht bestätigten Lösungen im Hintergrund vornehmen?

authors: JaninaBistron felixerdy

repo: felixerdy/origami


text:
Add new configuration option to leave a jsconfig.json file as-is during startup

This would resolve issue #47 by allowing users to disable the jsconfig.json update logic

Thank you!

Glad to help out.  Any thoughts on when you might cut a new release with this change?

@felixrieseberg any chance we can get this fix as a new release soon?

@felixrieseberg is there anything blocking a new release with this included?

authors: csetera felixrieseberg jeanduplessis vladucu

repo: felixrieseberg/vsc-ember-cli


text:
error: cannot borrow *r as mutable more than once at a time

since the Request is mutable, how can i use r.form().get("something") twice or more?

Can I have some code examples?

@fengsp
fn hello(r: &mut Request) -> PencilResult {
     let delay = r.form().get("delay").unwrap();

    let action = r.form().get("action").unwrap();
    Ok(Response::from("jjjj"))
}

@saggit Just clone it:
let delay = r.form().get("delay").unwrap().clone();

@fengsp  thanks for your quick relay, i will try it later.

authors: fengsp saggit

repo: fengsp/pencil


text:
Improve performance for lots of thumbnails?

Hi,
Would it be possible to introduce some methods in order to improve the performance of the image viewer - for example, I am trying to load the image viewer with about 800 images. Would it be possible to defer or lazy load the thumbnails which are not yet visible when first invoked? There is another javascript image viewer which offers this functionality:
http://galleria.io/docs/references/optimize/#lazy-load-thumbnails
See points 3 and 6 in the above link.
Please let me know what you think. Thanks for your image viewer!

Just download the images page by page, and each time one page images loaded, call the update method to add them to the viewer.

Thanks for your reply..

We managed to find a way to lazy load the thumbnails using the following lightweight jquery plugin: http://luis-almeida.github.io/unveil/
Initially, the 800 thumbnails on the page are hidden and they each have a common placeholder image. We are then calling unveil function on a subset of the images (about 21 images) which goes to replace the placeholder image with the actual image. As the user navigates the thumbnails, the thumbnails are being replaced with their actual images URLs too.

@nabeygun How did you do that? Can you share example code? Unfortunately I could not.
@fengyuanchen  Also when I update, the viewer always turn first image. Is this normal?

@yavuz Unfortunately, I cannot show my example code but I can try to explain through the changes. We used the unveil jquery plugin in the following manner:
In viewer.js, we edited the constructor function Viewer(element, options) { to add the below line:
    this.unveilImages = false;
Then, we edited the renderList function to insert the below code:
      // Unveil jQuery plugin is being used for lazy loading of thumbnail images.
      // A maximum of 20 thumbnails will be loaded upon opening of the Image Viewer.
      // As user navigates using Next/Previous buttons, further thumbnails will be loaded asynchronously.
      if (this.unveilImages) {
    	  if (this.length >= 20) {
    		  var elements;
    		  if (i <= 9) {
    			  elements = $("img.lazyImage").slice(0, 20);
    		  } else {
    			  elements = $("img.lazyImage").slice(i - 10, i + 10);
    		  }
    		  elements.unveil();
    	  } else {
    		  $("img.lazyImage").unveil();
    	  }
      }

We added the following new function too:
    toggleUnveil : function() {
    	this.unveilImages = true;
    },

We edited the existing function initList to add the class lazyImage and attribute data-src when rendering the images:
```
list.push(
'' +
'<img' +
' class="lazyImage" ' +
' data-src="' + dataSrc + '"' +
' src="' + src + '"' +
' data-action="view"' +
' data-index="' +  i + '"' +
' data-original-url="' +  (url || src) + '"' +
' alt="' +  alt + '"' +
'>' +
''
);
where dataSrc is obtained via a call:
`var dataSrc = this.getAttribute('data-actualurl') || src;
`

In our calling code, we have to a reference to the files _viewer.js_ and _jquery.unveil.js_. Then our javascript call is:

$j(function($) {
var modalViewerOptions = {
url: 'data-original',
shown: function(e) {
$(this).viewer('toggleUnveil');
}
};
// show 'modal' image viewer
$('#invokeImageViewer').on('click', function(e) {
	e.preventDefault();
	$('#hiddenThumbs').viewer(modalViewerOptions).viewer('show');
});

});
An actual thumbnail image:
`<img src="commonImage.png" data-actualurl="actualThumbnailImage.png"  alt="Image description" data-original="actualFullSizeImage.png"/>`

Hope that helps you get started.

authors: fengyuanchen nabeygun yavuz

repo: fengyuanchen/viewer


text:
[BUG] Quick sliding to the top and bottom, do not adjust this method "onPageChanged"

Quick sliding, do not adjust this method "onPageChanged"

I can confirm that there is an issue with the 'onPageChanged' handler.
Describe the bug
The 'onPageChanged' callback (PagerContent.swift:232) is not called in the event of gestures followed quickly by each other. Therefore, the app is not able to react on index change updates.
To Reproduce

Quick Drag Gesture from right to left followed instantly by a second one.

Expected behavior
'onPageChanged' handler will be called on every page index change.
Environment:
OS: iOS 16
SwiftUIPager 2.5.0
Additional context
The SwiftUIPager detects both Drag Gestures and finishes both with 'onDragGestureEnded' (PagerContent.swift:373). The 'onAnimationCompleted' (PagerContent.swift:227) observer triggers only once, which is totally fine. But the second 'onDragGestureEnded' call sets self.pagerModel.pageIncrement = 0. Therefore, the following 'onAnimationCompleted' observation won't trigger the 'onPageChanged' callback.

We really need this change. For now we're pointing to the forked commit (thank you @geraldvoit !!!) but we would really like to have the fix in an official release of the library. Is there any chance this will happen?

Hello, @fermoya. Can you create a new release of the library with this fix, please🙏

authors: JingChen1 PatrickGaissert alpha-moisol geraldvoit

repo: fermoya/SwiftUIPager


text:
C# language guide for Spin

Add a C# language guide for Spin

cc @itowlson

See linear.app's Developer Docs team for more information.

First draft of C# content has been placed in the following PR
https://github.com/fermyon/developer/pull/432

authors: mikkelhegn radu-matei tpmccallum

repo: fermyon/developer


text:
Implement CustomLogPipes for Spin Logging/IO: The Return

That's exactly right. If you have your WasiFiles already, you can call ModuleIoRedirects::new directly, and pass that to prepare_component. (At least, you'll be able to if that PR is accepted.)
WAGI does this in a very simple form because it needs different behaviour for stdin, and a slightly different interaction with the buffer for stdout. It's really valuable to know that this is more broadly useful as a public customisation point though!

To provide an update on this from #438 (and maybe close that issue soon), it turns out that I couldn't really make the current architecture use our own pipes — As previously implied, the meat and potatoes of logging is done in execute:
https://github.com/fermyon/spin/blob/c3ff7d90fe115daa3fa85ce3e626c738e7baef76/crates/http/src/spin.rs#L19-L59
It's there that capture_io_to_memory, prepare_component (that receives redirects), and, subsequently, redirect_to_mem_buffer are called.
Considering our builder is set w/ with_engine(), as per:
https://github.com/fermyon/spin/blob/1fbfb23b4e96a580d6d4f4b6d617e916974493f1/crates/engine/src/lib.rs#L103-L119
I tried emulating the work done in execute in the build stage similar to how the store does it:
https://github.com/fermyon/spin/blob/0f51ad0b86b798ae18cb4f211f0c3fcfbbe9a156/crates/engine/src/lib.rs#L304-L316
... but, nothing came of it as execute would eventually run and override/never access my RuntimeContext WASI context data.
All and all, this PR allows users to set CustomLogPipes when creating their ExecutionContextConfiguration — these CustomLogPipes are later accessed by execute and passed in to capture_io_to_memory (which has a side-effect on prepare_component) providing a good and needed override of Spin's default settings.
EDIT: For ease of review, I remade this PR ~ my rebases to fix sign-off issues made the previous one (i.e., #471) kind of messy

Yes, our previous discussion involved an assumption that you'd be in a position to call the preparation methods directly.  If you want to simply host the trigger, then indeed those are not available to you.  But I agree, you should be able to host the trigger/executor and decide how to handle the guest component input/output.
The solution in this PR exposes an architectural flaw (or, more kindly, limitation) in my original 'follow' design, and it would be good to correct that now rather than continue down that same path.  My error was putting too much policy in the executor, and too much implementation in the engine.  I think we should flip that around and take policy as far as possible out of the executor, and place it into the executor host (spin up by default, but a custom host in your case).  Implementation could remain in the engine, or go elsewhere - current implementations are very bound to specific policies.
What this might look like will take some more thought, but roughly I'm thinking:

Engine: defines the abstractions it needs (may be as little as ModuleIoRedirects) for wiring up to the module at execution time
Something else: provides helpers for constructing ModuleIoRedirects around streams, pipes, files, memory and whatever, and for composing those
Host: policy: looks at the command line and manifest, and sets up appropriate factories for ModuleIoRedirects using the helpers or its own custom implementation
Trigger/executor: uses the given factory to instantiate ModuleIoRedirects on a per-request basis (overriding where appropriate e.g. WAGI's stdout handling), calls a flush method afterwards so buffered output can be written to file.  It makes no policy choices of its own!

As part of this we could consider whether guest output should be written to log files as it is emitted.  The buffering of logs into memory before dumping en bloc to a file may have been influenced by WAGI; I don't know if it's still desirable for it to be that way.  (There may be reasons like all the logs for a request being together though.)
These are very vague thoughts, and represent a significant change without a crisp definition.  The sketch above moves significant preparation out of the executor, and we may want to review other parts of the preparation pipeline alongside it.  What you have here looks fine from a first skim over, and if you just want to get something working then fair enough!

To be clear, I really appreciate what you've done here!  What prompted the above was reflecting on the architecture you are working within, not on any disagreement with what you're doing or how you're doing it.  I'm really happy to see this PR!

Hey, @itowlson ~ Thank you for your review!
I'm sorry for taking a while to reply, I've actually been working on trying out an implementation following your spec. Anyway, how does this (i.e., below) sound?
In terms main types, we'll have the following:

a RedirectPipes type (previously ModuleIoRedirects) that contains the stdin, stdout, and stderr pipes,
a RedirectReadHandles type (same as before), and
a ModuleIoRedirects type that contains our RedirectPipes and RedirectReadHandles — I think this would be good because the Redirect* types are sort of intertwined.

In terms of functions, we'll add the following:

a new method to RedirectReadHandles that will perform part of redirect_to_mem_buffer's function of creating the locks.
a new method to ModuleIoRedirects that creates an instance in its' default way (i.e., calling RedirectReadHandles's new method and then following the steps that redirect_to_mem_buffer follows currently).
a new_from_files method to ModuleIoRedirects that will create an instance from files/pipes/whatever specified by the user.

Next up, we can create an enum called ModuleIoRedirectsType w/ values Default, and FromFiles(CustomLogPipes). This can be added as a field to the ExecutionContextConfiguration struct (or as a new parameter to the host like follow), so the user can specify if they want to override spin's default host implementation w/ their own files.
With this set, the executor can check the engine.config for the ModuleIoRedirectsType and, in a match, call the appropriate new* method, and have its' results be passed to prepare_component, and save_output_to_logs.

P.S. I think that Arc::try_unwrap() here is not going to work, so this is sort of broken, but... It should give an idea of how I was thinking the code could be structured under your spec, @itowlson!
~let me know what you think!

I've fixed the issues that I've brought up w/ this latest commit, @itowlson ~ SOOO... You should be good to go for reviewing the implementation of custom log pipes under your spec (e.g., using ModuleIoRedirect factories, and so on).

Sorry for the slow cycle on the CI.  For some reason we still have to approve you as a 'first time contributor' each time.  Hopefully this will go away once it's merged.  Aiming to take a look tomorrow (so, uh, sorry about the slow cycle on that too).

@Mossaka ~ I've addressed all the changes you requested in my latest push

@itowlson ~ I've made a new push where I addressed all the items I marked as "done ✅". If those look good to you, feel free to "Resolve conversation" them! There are a couple of items we are still discussing, so I'll be waiting your replies there before taking any action ;)

By the way our CI enforces cargo fmt and cargo clippy gates - given that we are still stuck in manual approval to get CI feedback, I thought I'd better flag you to run those so you're not circling around on build failures from small mechanical stuff!

Ugh, I'm sorry, @danbugs - we need you to sign the commits.  (And thanks GitHub for not flagging this until after all the other checks had passed.)

Ugh, I'm sorry, @danbugs - we need you to sign the commits. (And thanks GitHub for not flagging this until after all the other checks had passed.)

Hmmm~ That's odd, I did sign my commits. The DCO bot even confirms it:

What am I missing, @itowlson ?

They need to be GPG verified commits as well as the DCO signature.  See https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification

@itowlson ~ thank you for your patience, done ✅

Also, given that we merge commits, could you please only keep the useful commits?
Thanks!

@radu-matei ~ done ✅
P.S. from 23 commits down to 4!

authors: danbugs itowlson radu-matei

repo: fermyon/spin


text:
Select Multiple Countries

Is there a way using this package to select multiple countries from the list at the same time?
I have the requirement that multiple countries may be selected from the dropdown at the same time. can this be achieved ?

Yes it can be achieved but not at the current version.
I'll try to work on it if I'll have some free time this week, for the mean time, you can fork this repository and add those functionalities.

Ok. Thanks for your reply & continued work.


text:
Support named groups

This pull request adds support for named groups (at least it parses them correctly).

I'm thinking about it and it might be possible to preserve that name inside the pattern object and serialise it out later, provided the pattern hasn't been destroyed/refactored during a reduce() call. The same may be true of non-capturing groups, come to that. Other special groups may be tricker though.
A possible problem may be dealing with this case when the pattern is a top-level entity in the lego object. (foo) reduces to foo, but what does (?<name>foo) reduce to?

I think captured groups and named groups behavior quite similar. Because in case of (foo) we can't just reduce it to foo because we will lose group[1]. If we want just optimize our regular expression, but keep exactly same matches output then we can't remove groups in any way (except non-capturing ones).
It may be an option for reduce to prevent ungrouping or method for lego object to remove all groups (replace them with non-capturing groups).
I'm personally used this library for regexp analyzing (to find regular expressions which can produce wrong matches). So in my case it doesn't matter if group explicitly present or not in result lego object.

authors: ferno mirasrael

repo: ferno/greenery


text:
Add (BETA) to window title

Also fix a bug: fix relative paths to the default torrents.

:+1:

authors: dcposch feross

repo: feross/webtorrent-app


text:
Add support for variables

Hi,
Would it be conceivable to make ssz-size / ssz-max accept variable names that would get inserted in the generated code, instead of hardcoded values?
The idea behind this is that the Ethereum spec comes with configurable variables, and it's currently impossible (or at least quite complicated and repetitive) to write code that can be compatible with multiple presets at the same time.
For example, I'd like to be able to write something like this:
type ExecutionPayload struct {
	Withdrawals   []*Withdrawal           `ssz-max-var:"MAX_WITHDRAWALS_PER_PAYLOAD" ssz-var-pkg: config`
}

And it would then generate the file with MAX_WITHDRAWALS_PER_PAYLOAD in place of the hardcoded 16, as well as import the config package (although that might already be doable automatically?).
I'm guessing this could introduce some overhead in cases where calculations are required for buffer indexes etc, but for extremely high performance apps it would still be possible to use the current way.

Hello! Thank you for the proposal.
This is not something I am planning to do in the short term for two reasons. Unfortunately, the changes in the code generator to support this feature are not trivial to do.

authors: ferranbt filoozom

repo: ferranbt/fastssz


text:
dynamic drink button

Currently DrinkButton operates entirely PreClick. It could instead be event driven, watching bag updates, and always be up-to-date on the item that it wants to use next. This would facilitate making the action button dynamic based on available water.

A simpler approach might simply be a macro with a series of /use item:nnn commands.

... except that this would require using a macro slot as opposed to arbitrary macrotext.

repo: ferronn-dev/ferronnizer


text:
Typo

If you call it without arguments, it will tell you:

Error, provide at least one of the following arguments: --query or --file
The correct argument appears to be --doi-file (not --file)

Hi,
sorry for the late reply, but PyPaperBot had been on standby until now.
I've decided to resume development to improve it.
I've created a Telegram channel where you can suggest improvements, report bugs, or request custom data mining scripts. Feel free to join if you're interested with the following LINK
Thanks!


text:
Fix CFrame Datatype for Rotation

This PR addresses #15, using the solution sent by @Tom-atoes, which was provided by user Arkiuma.
I modified the solution to change f32NoAlloc to writef32NoAlloc. I am not sure why this was like that, but from my understanding, that's what it should be.

lgtm

authors: HooferDevelops ffrostfall

repo: ffrostfall/ByteNet


text:
Criar Canvas

Nessa issue deve ser feito:
Criar quadro canvas do produto.

issue duplicada


text:
Documentação de Conclusão do Projeto.

Descrição:
Documentação que dará um panorama geral do projeto, juntamente com as melhoras da equipe alinhada com os Roadmaps (Arquitetura, SM, DevOps) definidos durante a primeira fase do projeto, explicitando erros de gerência, esforços gastos e pontos atingidos
Critérios de Aceitação

[ ] Documento revisado
[ ] Documento fazendo link com os Roadmaps iniciais
[ ] Explicitação de Resultados.
[ ] Explicitação de Esforços.
[ ] Explicitação de Erros cometidos.

Tarefas
Seção para tarefas de Issues mais complexas. As tarefas devem garantir o perfeito funcionamento da Issue.

[ ] Criar documento
[ ] Linkar com Roadmaps
[ ] Mostrar Resultados
[ ] Mostrar Erros
[ ] Mostrar Esforços
[ ] Revisar documento

Documento sendo criado na Brach eps_docs