Exception caught by widgets library

Restarted application in 1,924ms.
════════ Exception caught by widgets library ═══════════════════════════════════
The following assertion was thrown building KeyedSubtree-[GlobalKey#07810]:
Failed assertion: boolean expression must not be null
Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
https://github.com/flutter/flutter/issues/new?template=BUG.md

The relevant error-causing widget was
Hero
When the exception was thrown, this was the stack
#0      _RenderCustomClip.clipper=
#1      ClipPath.updateRenderObject
#2      RenderObjectElement.update
#3      SingleChildRenderObjectElement.update
#4      Element.updateChild
...
════════════════════════════════════════════════════════════════════════════════

Hi @sillicongbs
can you please provide your flutter doctor -v and flutter run --verbose?
Also, to better address the issue, would be helpful if you could post a minimal code sample to reproduce the problem
Thank you

Hi @sillicongbs
can you please provide your flutter doctor -v and flutter run --verbose?
Also, to better address the issue, would be helpful if you could post a minimal code sample to reproduce the problem
Thank you
PS E:\Personal WorkSpace\Android WorkSpace\app_login> flutter doctor -v
[√] Flutter (Channel stable, v1.12.13+hotfix.9, on Microsoft Windows [Version 10.0.18363.752], locale en-US)
• Flutter version 1.12.13+hotfix.9 at C:\flutter
• Framework revision f139b11009 (8 days ago), 2020-03-30 13:57:30 -0700
• Engine revision af51afceb8
• Dart version 2.7.2

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
• Android SDK at E:\Android Studio\SDK
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.3
• ANDROID_HOME = E:\Android Studio\SDK
• Java binary at: E:\Android Studio\android-studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
• All Android licenses accepted.
[√] Android Studio (version 3.6)
• Android Studio at E:\Android Studio\android-studio
• Flutter plugin version 45.0.1
• Dart plugin version 192.7761
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
[√] VS Code (version 1.43.2)
• VS Code at C:\Users\SENPAI\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.9.0
[√] Connected device (1 available)
• Android SDK built for x86 • emulator-5554 • android-x86 • Android 8.0.0 (API 26) (emulator)
• No issues found!
PS E:\Personal WorkSpace\Android WorkSpace\app_login> flutter run --verbose
[  +22 ms] executing: [C:\flutter] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +62 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] f139b11009aeb8ed2a3a3aa8b0066e482709dde3
[   +1 ms] executing: [C:\flutter] git describe --match v*.. --first-parent --long --tags
[  +48 ms] Exit code 0 from: git describe --match v*.. --first-parent --long --tags
[  +10 ms] v1.12.13+hotfix.9-0-gf139b1100
[   +9 ms] executing: [C:\flutter] git rev-parse --abbrev-ref --symbolic @{u}
[  +60 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [C:\flutter] git ls-remote --get-url origin
[  +41 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +85 ms] executing: [C:\flutter] git rev-parse --abbrev-ref HEAD
[  +42 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[ +120 ms] executing: E:\Android Studio\SDK\platform-tools\adb.exe devices -l
[  +29 ms] Exit code 0 from: E:\Android Studio\SDK\platform-tools\adb.exe devices -l
[        ] List of devices attached
emulator-5554          device product:sdk_gphone_x86 model:Android_SDK_built_for_x86 device:generic_x86 transport_id:1
[  +17 ms] E:\Android Studio\SDK\platform-tools\adb.exe -s emulator-5554 shell getprop
[  +65 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[   +5 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +3 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +349 ms] Generating E:\Personal WorkSpace\Android WorkSpace\app_login\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java
[  +58 ms] ro.hardware = ranchu
[  +60 ms] Using hardware rendering with device Android SDK built for x86. If you get graphics artifacts, consider enabling software rendering with
"--enable-software-rendering".
[  +28 ms] Launching lib\main.dart on Android SDK built for x86 in debug mode...
[  +14 ms] executing: E:\Android Studio\SDK\build-tools\29.0.3\aapt dump xmltree E:\Personal WorkSpace\Android
WorkSpace\app_login\build\app\outputs\apk\app.apk AndroidManifest.xml
[ +416 ms] Exit code 0 from: E:\Android Studio\SDK\build-tools\29.0.3\aapt dump xmltree E:\Personal WorkSpace\Android
WorkSpace\app_login\build\app\outputs\apk\app.apk AndroidManifest.xml
[   +1 ms] N: android=http://schemas.android.com/apk/res/android
E: manifest (line=2)
A: android:versionCode(0x0101021b)=(type 0x10)0x1
A: android:versionName(0x0101021c)="1.0.0" (Raw: "1.0.0")
A: android:compileSdkVersion(0x01010572)=(type 0x10)0x1c
A: android:compileSdkVersionCodename(0x01010573)="9" (Raw: "9")
A: package="com.axtonai.loginapp" (Raw: "com.axtonai.loginapp")
A: platformBuildVersionCode=(type 0x10)0x1c
A: platformBuildVersionName=(type 0x10)0x9
E: uses-sdk (line=7)
A: android:minSdkVersion(0x0101020c)=(type 0x10)0x10
A: android:targetSdkVersion(0x01010270)=(type 0x10)0x1c
E: uses-permission (line=14)
A: android:name(0x01010003)="android.permission.INTERNET" (Raw: "android.permission.INTERNET")
E: application (line=22)
A: android:label(0x01010001)="loginapp" (Raw: "loginapp")
A: android:icon(0x01010002)=@0x7f080000
A: android:name(0x01010003)="io.flutter.app.FlutterApplication" (Raw: "io.flutter.app.FlutterApplication")
A: android:debuggable(0x0101000f)=(type 0x12)0xffffffff
A: android:appComponentFactory(0x0101057a)="androidx.core.app.CoreComponentFactory" (Raw: "androidx.core.app.CoreComponentFactory")
E: activity (line=28)
A: android:theme(0x01010000)=@0x7f0a0000
A: android:name(0x01010003)="com.axtonai.loginapp.MainActivity" (Raw: "com.axtonai.loginapp.MainActivity")
A: android:launchMode(0x0101001d)=(type 0x10)0x1
A: android:configChanges(0x0101001f)=(type 0x11)0x40003fb4
A: android:windowSoftInputMode(0x0101022b)=(type 0x11)0x10
A: android:hardwareAccelerated(0x010102d3)=(type 0x12)0xffffffff
E: intent-filter (line=35)
E: action (line=36)
A: android:name(0x01010003)="android.intent.action.MAIN" (Raw: "android.intent.action.MAIN")
E: category (line=38)
A: android:name(0x01010003)="android.intent.category.LAUNCHER" (Raw: "android.intent.category.LAUNCHER")
E: meta-data (line=45)
A: android:name(0x01010003)="flutterEmbedding" (Raw: "flutterEmbedding")
A: android:value(0x01010024)=(type 0x10)0x2
[  +40 ms] executing: E:\Android Studio\SDK\platform-tools\adb.exe -s emulator-5554 shell -x logcat -v time -t 1
[  +52 ms] Exit code 0 from: E:\Android Studio\SDK\platform-tools\adb.exe -s emulator-5554 shell -x logcat -v time -t 1
[   +1 ms] --------- beginning of system
04-07 15:07:04.773 E/BatteryStatsService( 1670): modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0
mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}
[   +8 ms] executing: E:\Android Studio\SDK\platform-tools\adb.exe version
[   +2 ms] executing: E:\Android Studio\SDK\platform-tools\adb.exe -s emulator-5554 logcat -v time -T 04-07 15:07:04.773
[  +66 ms] Android Debug Bridge version 1.0.41
Version 29.0.6-6198805
Installed as E:\Android Studio\SDK\platform-tools\adb.exe
[  +33 ms] executing: E:\Android Studio\SDK\platform-tools\adb.exe start-server
[  +46 ms] Building APK
[  +18 ms] Running Gradle task 'assembleDebug'...
[  +15 ms] gradle.properties already sets android.enableR8
[  +26 ms] Using gradle from E:\Personal WorkSpace\Android WorkSpace\app_login\android\gradlew.bat.
[   +5 ms] executing: E:\Android Studio\android-studio\jre\bin\java -version
[  +96 ms] Exit code 0 from: E:\Android Studio\android-studio\jre\bin\java -version
[        ] openjdk version "1.8.0_212-release"
OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
OpenJDK 64-Bit Server VM (build 25.212-b04, mixed mode)
[   +2 ms] executing: E:\Android Studio\android-studio\jre\bin\java -version
[  +93 ms] Exit code 0 from: E:\Android Studio\android-studio\jre\bin\java -version
[        ] openjdk version "1.8.0_212-release"
OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
OpenJDK 64-Bit Server VM (build 25.212-b04, mixed mode)
[   +3 ms] executing: [E:\Personal WorkSpace\Android WorkSpace\app_login\android] E:\Personal WorkSpace\Android WorkSpace\app_login\android\gradlew.bat
-Pverbose=true -Ptarget=E:\Personal WorkSpace\Android WorkSpace\app_login\lib\main.dart -Ptrack-widget-creation=true -Pfilesystem-scheme=org-dartlang-root
-Ptarget-platform=android-x86 assembleDebug
[+3017 ms] Welcome to Gradle 5.6.2!
[   +1 ms] Here are the highlights of this release:
[   +1 ms]  - Incremental Groovy compilation
[        ]  - Groovy compile avoidance
[        ]  - Test fixtures for Java projects
[  +20 ms]  - Manage plugin versions via settings script
[   +1 ms] For more details see https://docs.gradle.org/5.6.2/release-notes.html
[ +761 ms] Starting a Gradle Daemon, 1 busy Daemon could not be reused, use --status for details
[+23802 ms] > Task :app:compileFlutterBuildDebug
[   +1 ms] [  +22 ms] executing: [C:\flutter] git -c log.showSignature=false log -n 1 --pretty=format:%H
[   +1 ms] [  +66 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +20 ms] [        ] f139b11009aeb8ed2a3a3aa8b0066e482709dde3
[   +1 ms] [        ] executing: [C:\flutter] git describe --match v*.. --first-parent --long --tags
[  +16 ms] [  +53 ms] Exit code 0 from: git describe --match v*.. --first-parent --long --tags
[   +1 ms] [        ] v1.12.13+hotfix.9-0-gf139b1100
[  +18 ms] [   +8 ms] executing: [C:\flutter] git rev-parse --abbrev-ref --symbolic @{u}
[   +1 ms] [  +43 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] [        ] origin/stable
[   +1 ms] [        ] executing: [C:\flutter] git ls-remote --get-url origin
[        ] [  +41 ms] Exit code 0 from: git ls-remote --get-url origin
[   +2 ms] [        ] https://github.com/flutter/flutter.git
[        ] [  +86 ms] executing: [C:\flutter] git rev-parse --abbrev-ref HEAD
[   +1 ms] [  +45 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] [        ] stable
[   +2 ms] [  +31 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[   +1 ms] [        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[  +13 ms] [        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] [   +5 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[  +13 ms] [        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[   +1 ms] [        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[   +1 ms] [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[   +1 ms] [ +104 ms] Initializing file store
[  +15 ms] [  +22 ms] Done initializing file store
[+1171 ms] [+1927 ms] kernel_snapshot: Starting due to {InvalidatedReason.inputChanged}
[   +1 ms] [  +12 ms] C:\flutter\bin\cache\dart-sdk\bin\dart.exe C:\flutter\bin\cache\artifacts\engine\windows-x64\frontend_server.dart.snapshot --sdk-rootC:\flutter\bin\cache\artifacts\engine\common\flutter_patched_sdk/ --target=flutter -Ddart.developer.causal_async_stacks=true -Ddart.vm.profile=false
-Ddart.vm.product=false
--bytecode-options=source-positions,local-var-info,debugger-stops,instance-field-initializers,keep-unreachable-code,avoid-closure-call-instructions
--enable-asserts --track-widget-creation --no-link-platform --packages E:\Personal WorkSpace\Android WorkSpace\app_login.packages --output-dill
E:\Personal WorkSpace\Android WorkSpace\app_login.dart_tool\flutter_build\b888e99ea4bb8a99f1e219afb4836d9e\app.dill --depfile E:\Personal
WorkSpace\Android WorkSpace\app_login.dart_tool\flutter_build\b888e99ea4bb8a99f1e219afb4836d9e\kernel_snapshot.d package:loginapp/main.dart
[+5997 ms] [+5991 ms] kernel_snapshot: Complete
[ +300 ms] [ +302 ms] invalidated build due to missing files: E:\Personal, WorkSpace\Android, WorkSpace\app_login\pubspec.yaml,
WorkSpace\app_login\assets\logo.png
[  +99 ms] [  +61 ms] debug_android_application: Starting due to {InvalidatedReason.inputChanged, InvalidatedReason.outputMissing,
InvalidatedReason.inputMissing}
[ +299 ms] [ +334 ms] debug_android_application: Complete
[   +2 ms] [   +7 ms] Persisting file store
[        ] [  +15 ms] Done persisting file store
[   +1 ms] [   +3 ms] build succeeded.
[        ] [  +18 ms] "flutter assemble" took 8,882ms.
[ +195 ms] > Task :app:packLibsflutterBuildDebug UP-TO-DATE
[   +2 ms] > Task :app:preBuild UP-TO-DATE
[   +1 ms] > Task :app:preDebugBuild UP-TO-DATE
[        ] > Task :app:compileDebugAidl NO-SOURCE
[  +96 ms] > Task :app:checkDebugManifest UP-TO-DATE
[   +2 ms] > Task :app:compileDebugRenderscript NO-SOURCE
[   +1 ms] > Task :app:generateDebugBuildConfig UP-TO-DATE
[        ] > Task :app:cleanMergeDebugAssets
[  +95 ms] > Task :app:mergeDebugShaders UP-TO-DATE
[   +1 ms] > Task :app:compileDebugShaders UP-TO-DATE
[   +1 ms] > Task :app:generateDebugAssets UP-TO-DATE
[  +95 ms] > Task :app:mergeDebugAssets
[ +399 ms] > Task :app:copyFlutterAssetsDebug
[   +1 ms] > Task :app:mainApkListPersistenceDebug UP-TO-DATE
[        ] > Task :app:generateDebugResValues UP-TO-DATE
[   +1 ms] > Task :app:generateDebugResources UP-TO-DATE
[  +98 ms] > Task :app:mergeDebugResources UP-TO-DATE
[        ] > Task :app:createDebugCompatibleScreenManifests UP-TO-DATE
[        ] > Task :app:processDebugManifest UP-TO-DATE
[        ] > Task :app:processDebugResources UP-TO-DATE
[ +597 ms] > Task :app:compileDebugKotlin UP-TO-DATE
[   +4 ms] > Task :app:javaPreCompileDebug UP-TO-DATE
[   +1 ms] > Task :app:compileDebugJavaWithJavac UP-TO-DATE
[   +1 ms] > Task :app:compileDebugSources UP-TO-DATE
[        ] > Task :app:processDebugJavaRes NO-SOURCE
[   +3 ms] > Task :app:mergeDebugJavaResource UP-TO-DATE
[ +118 ms] > Task :app:checkDebugDuplicateClasses UP-TO-DATE
[  +69 ms] > Task :app:transformClassesWithDexBuilderForDebug UP-TO-DATE
[  +19 ms] > Task :app:desugarDebugFileDependencies UP-TO-DATE
[  +80 ms] > Task :app:mergeExtDexDebug UP-TO-DATE
[   +8 ms] > Task :app:mergeDexDebug UP-TO-DATE
[        ] > Task :app:validateSigningDebug UP-TO-DATE
[        ] > Task :app:signingConfigWriterDebug UP-TO-DATE
[        ] > Task :app:mergeDebugJniLibFolders UP-TO-DATE
[  +22 ms] > Task :app:mergeDebugNativeLibs UP-TO-DATE
[  +66 ms] > Task :app:stripDebugDebugSymbols UP-TO-DATE
[+1698 ms] > Task :app:packageDebug
[   +1 ms] > Task :app:assembleDebug
[  +71 ms] BUILD SUCCESSFUL in 39s
[   +1 ms] 30 actionable tasks: 5 executed, 25 up-to-date
[ +362 ms] Running Gradle task 'assembleDebug'... (completed in 40.0s)
[  +27 ms] calculateSha: LocalDirectory: 'E:\Personal WorkSpace\Android WorkSpace\app_login\build\app\outputs\apk'/app.apk
[  +48 ms] calculateSha: reading file took 46us
[ +514 ms] calculateSha: computing sha took 512us
[  +12 ms] √ Built build\app\outputs\apk\debug\app-debug.apk.
[  +10 ms] executing: E:\Android Studio\SDK\build-tools\29.0.3\aapt dump xmltree E:\Personal WorkSpace\Android
WorkSpace\app_login\build\app\outputs\apk\app.apk AndroidManifest.xml
[  +21 ms] Exit code 0 from: E:\Android Studio\SDK\build-tools\29.0.3\aapt dump xmltree E:\Personal WorkSpace\Android
WorkSpace\app_login\build\app\outputs\apk\app.apk AndroidManifest.xml
[   +5 ms] N: android=http://schemas.android.com/apk/res/android
E: manifest (line=2)
A: android:versionCode(0x0101021b)=(type 0x10)0x1
A: android:versionName(0x0101021c)="1.0.0" (Raw: "1.0.0")
A: android:compileSdkVersion(0x01010572)=(type 0x10)0x1c
A: android:compileSdkVersionCodename(0x01010573)="9" (Raw: "9")
A: package="com.axtonai.loginapp" (Raw: "com.axtonai.loginapp")
A: platformBuildVersionCode=(type 0x10)0x1c
A: platformBuildVersionName=(type 0x10)0x9
E: uses-sdk (line=7)
A: android:minSdkVersion(0x0101020c)=(type 0x10)0x10
A: android:targetSdkVersion(0x01010270)=(type 0x10)0x1c
E: uses-permission (line=14)
A: android:name(0x01010003)="android.permission.INTERNET" (Raw: "android.permission.INTERNET")
E: application (line=22)
A: android:label(0x01010001)="loginapp" (Raw: "loginapp")
A: android:icon(0x01010002)=@0x7f080000
A: android:name(0x01010003)="io.flutter.app.FlutterApplication" (Raw: "io.flutter.app.FlutterApplication")
A: android:debuggable(0x0101000f)=(type 0x12)0xffffffff
A: android:appComponentFactory(0x0101057a)="androidx.core.app.CoreComponentFactory" (Raw: "androidx.core.app.CoreComponentFactory")
E: activity (line=28)
A: android:theme(0x01010000)=@0x7f0a0000
A: android:name(0x01010003)="com.axtonai.loginapp.MainActivity" (Raw: "com.axtonai.loginapp.MainActivity")
A: android:launchMode(0x0101001d)=(type 0x10)0x1
A: android:configChanges(0x0101001f)=(type 0x11)0x40003fb4
A: android:windowSoftInputMode(0x0101022b)=(type 0x11)0x10
A: android:hardwareAccelerated(0x010102d3)=(type 0x12)0xffffffff
E: intent-filter (line=35)
E: action (line=36)
A: android:name(0x01010003)="android.intent.action.MAIN" (Raw: "android.intent.action.MAIN")
E: category (line=38)
A: android:name(0x01010003)="android.intent.category.LAUNCHER" (Raw: "android.intent.category.LAUNCHER")
E: meta-data (line=45)
A: android:name(0x01010003)="flutterEmbedding" (Raw: "flutterEmbedding")
A: android:value(0x01010024)=(type 0x10)0x2
[  +11 ms] Stopping app 'app.apk' on Android SDK built for x86.
[   +3 ms] executing: E:\Android Studio\SDK\platform-tools\adb.exe -s emulator-5554 shell am force-stop com.axtonai.loginapp
[ +676 ms] executing: E:\Android Studio\SDK\platform-tools\adb.exe -s emulator-5554 shell pm list packages com.axtonai.loginapp
[+1675 ms] package:com.axtonai.loginapp
[   +3 ms] executing: E:\Android Studio\SDK\platform-tools\adb.exe -s emulator-5554 shell cat /data/local/tmp/sky.com.axtonai.loginapp.sha1
[  +51 ms] 263de4d6512bc2ec368b1257a1b05adbef57a56f
[   +1 ms] Installing APK.
[   +2 ms] executing: E:\Android Studio\SDK\platform-tools\adb.exe version
[  +49 ms] Android Debug Bridge version 1.0.41
Version 29.0.6-6198805
Installed as E:\Android Studio\SDK\platform-tools\adb.exe
[   +1 ms] executing: E:\Android Studio\SDK\platform-tools\adb.exe start-server
[  +30 ms] Installing build\app\outputs\apk\app.apk...
[   +1 ms] executing: E:\Android Studio\SDK\platform-tools\adb.exe -s emulator-5554 install -t -r E:\Personal WorkSpace\Android
WorkSpace\app_login\build\app\outputs\apk\app.apk
[+3863 ms] Performing Streamed Install
Success
[   +2 ms] Installing build\app\outputs\apk\app.apk... (completed in 3.9s)
[   +4 ms] executing: E:\Android Studio\SDK\platform-tools\adb.exe -s emulator-5554 shell echo -n 4697da1e2615b056b9e8a38adb30a09ae13645ee >
/data/local/tmp/sky.com.axtonai.loginapp.sha1
[ +111 ms] Android SDK built for x86 startApp
[  +13 ms] executing: E:\Android Studio\SDK\platform-tools\adb.exe -s emulator-5554 shell am start -a android.intent.action.RUN -f 0x20000000 --ez
enable-background-compilation true --ez enable-dart-profiling true --ez enable-checked-mode true --ez verify-entry-points true
com.axtonai.loginapp/com.axtonai.loginapp.MainActivity
[ +187 ms] Starting: Intent { act=android.intent.action.RUN flg=0x20000000 cmp=com.axtonai.loginapp/.MainActivity (has extras) }
[   +1 ms] Waiting for observatory port to be available...
[ +447 ms] D/FlutterActivity(12778): Using the launch theme as normal theme.
[   +5 ms] D/FlutterActivityAndFragmentDelegate(12778): Setting up FlutterEngine.
[  +26 ms] D/FlutterActivityAndFragmentDelegate(12778): No preferred FlutterEngine was provided. Creating a new FlutterEngine for this FlutterFragment.
[+1731 ms] Observatory URL on device: http://<IP_ADDRESS>:38997/NChSV32K_pM=/
[   +2 ms] executing: E:\Android Studio\SDK\platform-tools\adb.exe -s emulator-5554 forward tcp:0 tcp:38997
[  +67 ms] D/FlutterActivityAndFragmentDelegate(12778): Attaching FlutterEngine to the Activity that owns this Fragment.
[  +18 ms] 4937
[        ] Forwarded host port 4937 to device port 38997 for Observatory
[  +29 ms] Connecting to service protocol: http://<IP_ADDRESS>:4937/NChSV32K_pM=/
[  +47 ms] D/FlutterView(12778): Attaching to a FlutterEngine: io.flutter.embedding.engine.FlutterEngine@95ef4e7
[  +30 ms] D/FlutterActivityAndFragmentDelegate(12778): Executing Dart entrypoint: main, and sending initial route: /
[ +738 ms] Successfully connected to service protocol: http://<IP_ADDRESS>:4937/NChSV32K_pM=/
[   +6 ms] Sending to VM service: getVM({})
[  +20 ms] Result: {type: VM, name: vm, architectureBits: 32, hostCPU: Virtual CPU, operatingSystem: android, targetCPU: ia32, version: 2.7.2 (Mon Mar 23
22:11:27 2020 +0100) on "android_ia32", _profilerMode: VM, _nativeZoneMemoryUsage: 0, pid: 12778, startTime: 158...
[  +34 ms] Sending to VM service: getIsolate({isolateId: isolates/3492431685718687})
[  +41 ms] Sending to VM service: _flutter.listViews({})
[  +20 ms] Result: {type: FlutterViewList, views: [{type: FlutterView, id: _flutterView/0xa5903390, isolate: {type: @Isolate, fixedId: true, id:
isolates/3492431685718687, name: main.dart$main-3492431685718687, number:<PHONE_NUMBER>718687}}]}
[  +28 ms] DevFS: Creating new filesystem on the device (null)
[  +27 ms] Sending to VM service: _createDevFS({fsName: app_login})
[  +42 ms] Result: {type: Isolate, id: isolates/3492431685718687, name: main, number:<PHONE_NUMBER>718687, _originNumber:<PHONE_NUMBER>718687, startTime:
1586250520523, _heaps: {new: {type: HeapSpace, name: new, vmName: Scavenger, collections: 2, avgCollectionPeriodMillis...
[  +67 ms] Result: {type: FileSystem, name: app_login, uri: file:///data/user/0/com.axtonai.loginapp/code_cache/app_loginQCLIAN/app_login/}
[   +4 ms] DevFS: Created new filesystem on the device (file:///data/user/0/com.axtonai.loginapp/code_cache/app_loginQCLIAN/app_login/)
[   +7 ms] Updating assets
[ +188 ms] Syncing files to device Android SDK built for x86...
[   +4 ms] Scanning asset files
[   +6 ms] <- reset
[   +1 ms] Compiling dart to kernel with 0 updated files
[  +18 ms] C:\flutter\bin\cache\dart-sdk\bin\dart.exe C:\flutter\bin\cache\artifacts\engine\windows-x64\frontend_server.dart.snapshot --sdk-root
C:\flutter\bin\cache\artifacts\engine\common\flutter_patched_sdk/ --incremental --target=flutter -Ddart.developer.causal_async_stacks=true --output-dill
C:\Users\SENPAI\AppData\Local\Temp\flutter_tool.4276c237-78af-11ea-9be5-0c9d9240d761\app.dill --packages E:\Personal WorkSpace\Android
WorkSpace\app_login.packages -Ddart.vm.profile=false -Ddart.vm.product=false
--bytecode-options=source-positions,local-var-info,debugger-stops,instance-field-initializers,keep-unreachable-code,avoid-closure-call-instructions
--enable-asserts --track-widget-creation --filesystem-scheme org-dartlang-root
[  +23 ms] <- compile package:loginapp/main.dart
[ +106 ms] D/EGL_emulation(12778): eglMakeCurrent: 0xa80852a0: ver 2 0 (tinfo 0xa8083310)
[+7791 ms] Updating files
[ +304 ms] DevFS: Sync finished
[   +2 ms] Syncing files to device Android SDK built for x86... (completed in 8,256ms, longer than expected)
[   +1 ms] Synced 1.3MB.
[   +2 ms] Sending to VM service: _flutter.listViews({})
[   +5 ms] Result: {type: FlutterViewList, views: [{type: FlutterView, id: _flutterView/0xa5903390, isolate: {type: @Isolate, fixedId: true, id:
isolates/3492431685718687, name: main.dart$main-3492431685718687, number:<PHONE_NUMBER>718687}}]}
[  +16 ms] <- accept
[   +1 ms] Connected to _flutterView/0xa5903390.
[   +3 ms] �🔥  To hot reload changes while running, press "r". To hot restart (and rebuild state), press "R".
[   +1 ms] An Observatory debugger and profiler on Android SDK built for x86 is available at: http://<IP_ADDRESS>:4937/NChSV32K_pM=/
[        ] For a more detailed help message, press "h". To detach, press "d"; to quit, press "q".
[+48855 ms] I/flutter (12778): ══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
[   +1 ms] I/flutter (12778): The following assertion was thrown building KeyedSubtree-[GlobalKey#a5187]:
[        ] I/flutter (12778): Failed assertion: boolean expression must not be null
[  +36 ms] I/flutter (12778):
[   +2 ms] I/flutter (12778): Either the assertion indicates an error in the framework itself, or we should provide substantially
[   +2 ms] I/flutter (12778): more information in this error message to help you determine and fix the underlying cause.
[   +2 ms] I/flutter (12778): In either case, please report this assertion by filing a bug on GitHub:
[  +29 ms] I/flutter (12778):   https://github.com/flutter/flutter/issues/new?template=BUG.md
[   +2 ms] I/flutter (12778):
[  +35 ms] I/flutter (12778): The relevant error-causing widget was:
[   +2 ms] I/flutter (12778):   Hero file:///E:/Personal%20WorkSpace/Android%20WorkSpace/app_login/lib/pages/intro_page.dart:52:9
[   +1 ms] I/flutter (12778):
[        ] I/flutter (12778): When the exception was thrown, this was the stack:
[   +1 ms] I/flutter (12778): #0      _RenderCustomClip.clipper= (package:flutter/src/rendering/proxy_box.dart:1190:20)
[        ] I/flutter (12778): #1      ClipPath.updateRenderObject (package:flutter/src/widgets/basic.dart:845:9)
[   +2 ms] I/flutter (12778): #2      RenderObjectElement.update (package:flutter/src/widgets/framework.dart:5070:12)
[   +2 ms] I/flutter (12778): #3      SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5450:11)
[   +1 ms] I/flutter (12778): #4      Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[   +1 ms] I/flutter (12778): #5      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
[   +1 ms] I/flutter (12778): #6      Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
[  +35 ms] I/flutter (12778): #7      StatelessElement.update (package:flutter/src/widgets/framework.dart:4298:5)
[   +2 ms] I/flutter (12778): #8      Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[   +1 ms] I/flutter (12778): #9      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
[   +1 ms] I/flutter (12778): #10     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
[   +1 ms] I/flutter (12778): #11     ProxyElement.update (package:flutter/src/widgets/framework.dart:4557:5)
[   +1 ms] I/flutter (12778): #12     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[   +2 ms] I/flutter (12778): #13     SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5452:14)
[        ] I/flutter (12778): #14     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[   +1 ms] I/flutter (12778): #15     SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5452:14)
[  +34 ms] I/flutter (12778): #16     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[   +2 ms] I/flutter (12778): #17     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
[   +1 ms] I/flutter (12778): #18     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
[   +3 ms] I/flutter (12778): #19     StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
[   +5 ms] I/flutter (12778): #20     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[   +3 ms] I/flutter (12778): #21     RenderObjectElement.updateChildren (package:flutter/src/widgets/framework.dart:5161:32)
[  +28 ms] I/flutter (12778): #22     MultiChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5561:17)
[   +1 ms] I/flutter (12778): #23     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[   +1 ms] I/flutter (12778): #24     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
[  +26 ms] I/flutter (12778): #25     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
[   +2 ms] I/flutter (12778): #26     StatelessElement.update (package:flutter/src/widgets/framework.dart:4298:5)
[   +1 ms] I/flutter (12778): #27     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[        ] I/flutter (12778): #28     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
[        ] I/flutter (12778): #29     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
[  +28 ms] I/flutter (12778): #30     ProxyElement.update (package:flutter/src/widgets/framework.dart:4557:5)
[   +1 ms] I/flutter (12778): #31     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[        ] I/flutter (12778): #32     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
[   +1 ms] I/flutter (12778): #33     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
[        ] I/flutter (12778): #34     ProxyElement.update (package:flutter/src/widgets/framework.dart:4557:5)
[        ] I/flutter (12778): #35     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[        ] I/flutter (12778): #36     RenderObjectElement.updateChildren (package:flutter/src/widgets/framework.dart:5161:32)
[  +26 ms] I/flutter (12778): #37     MultiChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5561:17)
[   +3 ms] I/flutter (12778): #38     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[   +1 ms] I/flutter (12778): #39     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
[        ] I/flutter (12778): #40     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
[        ] I/flutter (12778): #41     StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
[   +1 ms] I/flutter (12778): #42     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[  +28 ms] I/flutter (12778): #43     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
[   +2 ms] I/flutter (12778): #44     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
[   +1 ms] I/flutter (12778): #45     ProxyElement.update (package:flutter/src/widgets/framework.dart:4557:5)
[   +1 ms] I/flutter (12778): #46     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[  +28 ms] I/flutter (12778): #47     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
[   +1 ms] I/flutter (12778): #48     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
[   +1 ms] I/flutter (12778): #49     StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
[   +1 ms] I/flutter (12778): #50     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[  +27 ms] I/flutter (12778): #51     SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5452:14)
[   +1 ms] I/flutter (12778): #52     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[   +1 ms] I/flutter (12778): #53     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
[   +1 ms] I/flutter (12778): #54     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
[   +2 ms] I/flutter (12778): #55     StatelessElement.update (package:flutter/src/widgets/framework.dart:4298:5)
[  +26 ms] I/flutter (12778): #56     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[   +1 ms] I/flutter (12778): #57     SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5452:14)
[   +1 ms] I/flutter (12778): #58     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[   +1 ms] I/flutter (12778): #59     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
[   +1 ms] I/flutter (12778): #60     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
[  +25 ms] I/flutter (12778): #61     StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
[   +2 ms] I/flutter (12778): #62     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[   +1 ms] I/flutter (12778): #63     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
[   +1 ms] I/flutter (12778): #64     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
[   +1 ms] I/flutter (12778): #65     StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
[  +24 ms] I/flutter (12778): #66     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[   +2 ms] I/flutter (12778): #67     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
[   +1 ms] I/flutter (12778): #68     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
[   +2 ms] I/flutter (12778): #69     ProxyElement.update (package:flutter/src/widgets/framework.dart:4557:5)
[   +1 ms] I/flutter (12778): #70     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[  +27 ms] I/flutter (12778): #71     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
[   +1 ms] I/flutter (12778): #72     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
[   +1 ms] I/flutter (12778): #73     ProxyElement.update (package:flutter/src/widgets/framework.dart:4557:5)
[   +1 ms] I/flutter (12778): #74     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[   +1 ms] I/flutter (12778): #75     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
[   +1 ms] I/flutter (12778): #76     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
[  +26 ms] I/flutter (12778): #77     StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
[   +1 ms] I/flutter (12778): #78     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
[   +1 ms] I/flutter (12778): #79     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
[   +1 ms] I/flutter (12778): #80     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
[   +1 ms] I/flutter (12778): #81     BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2432:33)
[   +1 ms] I/flutter (12778): #82     WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:773:20)
[  +26 ms] I/flutter (12778): #83     RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:283:5)
[   +1 ms] I/flutter (12778): #84     SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1102:15)
[   +1 ms] I/flutter (12778): #85     SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1041:9)
[   +1 ms] I/flutter (12778): #86     SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:957:5)
[   +1 ms] I/flutter (12778): #90     _invoke (dart:ui/hooks.dart:259:10)
[  +25 ms] I/flutter (12778): #91     _drawFrame (dart:ui/hooks.dart:217:3)
[   +2 ms] I/flutter (12778): (elided 3 frames from package dart:async)
[   +1 ms] I/flutter (12778):
[   +1 ms] I/flutter (12778): ════════════════════════════════════════════════════════════════════════════════════════════════════
[+4085 ms] I/flutter (12778): Another exception was thrown: 'package:flutter/src/widgets/framework.dart': Failed assertion: line 4701 pos 14:
'_dependents.isEmpty': is not true.
[  +45 ms] I/flutter (12778): Another exception was thrown: Duplicate GlobalKey detected in widget tree.
[  +19 ms] I/flutter (12778): Another exception was thrown: Looking up a deactivated widget's ancestor is unsafe.
[ +232 ms] I/flutter (12778): Another exception was thrown: 'package:flutter/src/widgets/framework.dart': Failed assertion: line 5540 pos 12:
'_children.contains(child)': is not true.
[  +23 ms] I/flutter (12778): Another exception was thrown: NoSuchMethodError: The getter 'userGestureInProgress' was called on null.
[  +62 ms] I/flutter (12778): Another exception was thrown: Duplicate GlobalKey detected in widget tree.
!
as per ur precious reply i have added doctor and verbose.
this thing is um getting this um the beginner on flutter. um trying to create a login with slider also um trying to attach when this happening.
step-1: launching app display then click bottom button.
step-2: Hero floating button not working as well as.
step-3: click back arrow its shows red screen display.

as i mentioned in comment when i click back arrow in second it appears 3rd red screen display what the exception i got as an issue i post.

Hi @sillicongbs
Can you please provide minimal reproducible sample?
Thank you

Hi @sillicongbs
Without additional information, we are unfortunately not sure how to resolve this issue. We are
therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the
bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


Review Poller Concurrency Design

It might be worth comparing notes on this stuff, we had a similar poller implementation in JustSaying 5 and moved away from it. I did a write-up about the problems it had, some of it was due to the implementation, but in general an eager check of "how many free workers do we have" the moment one has finished leads to choppy message consumption when there's back-pressure to work through, as well as all of the complications you are facing about keeping count accurately (which is essential).
The write-up is here (that ones more about the shared throttling mechanism we had) and discussion here (this describes the choppiness issue which is one of the factors that lead to a Channels based multiplexer).
We switched out to a mechanism that pre-fetches 1 batch lazily, with the message visibility renewal process you have it might be a better approach. I see you have the possibility to allow replacing the poller, it would be handy to us if the abstraction didn't necessitate the presence of an ActiveMessageCount.
What we have by default now essentially means as soon as 1 message is being processed from a batch, the next batch is fetched. The downside is naturally that you might take a message earlier than you are ready to process it, but again the visibility renewal takes care of that.
I'd also suggest reviewing the default visibility timeout and renewal values. 20 seconds and 18 for renewal might be cutting it fine. 30 and 25 gives a bit more room for error.

Originally posted by @slang25 in https://github.com/awslabs/aws-dotnet-messaging/issues/35#issuecomment-1517917915
I'd like to merge the PR that comment was left on sooner to fix a bug in the current implementation to unblock other areas of work, so creating this to track and discuss revisiting the poller design. DOTNET-6916 tracks this in the internal issue tracker.

We had an internal doc readout that explains how JustSaying manages concurrency during message handling and why did they move away from a concurrency strategy that is similar to what AWS Message Processing Framework for .NET uses currently.
JustSaying has a concept called SubscriptionGroups which is a collection of multiple SQS queues with the same shared configuration. By default, each queue has its own SubscriptionGroup. When a concurrency limit is set on a subscription group, this limit is shared across all SQS queues belonging to the same group. This means that if the concurrency limit is set to 10, then the combined maximum number of concurrently handled messages across all queues would be 10.
SubsciptionGroups are based on Channels based data structures.
Benefits of SubscriptionGroups
Subscription group offers throttled access to a shared resource that is being used by multiple handlers concurrently. Imagine a scenario in which you have several queues whose handlers all hit the same database. To be resilient under load, it's important to not overload the database by allowing too many requests through. Using subscription groups would put a concurrency limit that is shared across all handlers.
Drawbacks of Using Subscription Groups
Subscription groups induce a constant backpressure of messages that is governed by the WithPrefetch extension method. This controls the number of messages that should be read from SQS each time it makes a call. Each SQS queue within the group will prefetch 1 batch of messages during the first iteration. Subsequently, as soon as 1 message is being processed from a batch, the next batch is fetched pre-emptively.
The downside to this approach is that during each polling request, the user is receiving more messages than what can be consumed. These messages are buffered until a worker is available and their visibility is constantly being monitored and extended in the background. This can have business impact for customers since requests for extending visibility of messages are chargeable. This drawback was also mentioned in one of the PR comments left by a maintainer of JustSaying. Concurrency management in subscription groups is decoupled from the message polling logic. Concurrency limits will only restrict the number of handlers being invoked across all SQS queues but it does not influence the number of messages that will be fetched from SQS during each service call.
Additionally, messages that are polled from multiple SQS queues are buffered asynchronously and are interleaved. Since there are no guarantees on ordering of messages, JustSaying does not support FIFO handling of messages and also has an open GitHub issue about it.
Why did JustSaying opt to use a Channels based approach to concurrency management?
This GitHub issue outlines the concurrency related issues in JustSaying prior to V7. Below is a summary of it:
The had an interface called IMessageProcessingStrategy with the following members
int MaxWorkers { get; }
int AvailableWorkers { get; }
void StartWorker(Func<Task> action);
Task WaitForAvailableWorkers();

Imagine a scenario where a single instance IMessageProcessingStrategy was shared across 2 SQS pollers.

T0: AvailableWorkers is 0. Both pollers are blocked on WaitForAvailableWorkers()
T1: AvailableWorkers is set to 1 and both pollers attempt to read this value.
T2: Poller 1 reads the value first and requests SQS for 1 message and dispatches it for processing, decrementing AvailableWorkers to 0
T3: Poller 2 still has the stale value of AvailableWorkers in memory and requests 1 more message and eventually dispatches it for processing but also violates the concurrency limit.

They did not have a thread-safe way to maintain a count of AvailableWorkers across multiple SQS pollers and therefore moved away from it.
Conclusion
There are no user reported issues with the concurrency strategy currently used by AWS Message Processing Framework for .NET. It is stable with extensive test coverage around it. We currently do not plan to support setting a concurrency limit that is shared across multiple SQS queues and therefore have decided to stick to our current concurrency management startegy.


feat(words): add Autoware-related words

microautonomy: https://github.com/autowarefoundation/autoware-documentation/pull/21
modularizes: https://en.wiktionary.org/wiki/modularizes
runtimes: https://www.redhat.com/ja/products/application-runtimes

FYI @xmfcx This is how we add words to the dictionary.

CI isn't triggered... :thinking:

FYI @xmfcx This is how we add words to the dictionary.

Thanks!


rpm: ship different yml samples on RHEL vs CentOS

When building the RPM on CentOS, we will ship the all.yml.sample file and delete rhcs.yml.sample.
When building the RPM on RHEL, we will ship the rhcs.yml.sample file and delete all.yml.sample.

Well no because rhcs users would be asked to do so. So at the package level
sounds easier and less steps too
On Thu, 14 Sep 2017 at 14:31, Ken Dreyer<EMAIL_ADDRESS>wrote:

@ktdreyer commented on this pull request.
In ceph-ansible.spec.in
https://github.com/ceph/ceph-ansible/pull/1895#discussion_r139003388:

@@ -44,6 +44,13 @@ pushd %{buildroot}%{_datarootdir}/ceph-ansible
rm group_vars/common-coreoss.yml.sample

These untested playbooks are too unstable for users.
rm -r infrastructure-playbooks/untested-by-ci

%if 0%{?fedora} || 0%{?centos}

That is another option. Is that more or less confusing to users?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ceph/ceph-ansible/pull/1895#discussion_r139003388,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA3tX3THEPCqcbpZT8e2Feb2GmJJ8ptVks5siYz5gaJpZM4PX6yv
.

--
Cheers
––––––
Sébastien Han
Principal Software Engineer, Storage Architect
"Always give 100%. Unless you're giving blood."
Mail<EMAIL_ADDRESS>Address: 11 bis, rue Roquépine - 75008 Paris

Sure, I will defer to whichever option sounds better to you.

Thanks Ken. Please send a PR and we will take it from there.
On Thu, 14 Sep 2017 at 14:38, Ken Dreyer<EMAIL_ADDRESS>wrote:

Sure, I will defer to whichever option sounds better to you.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ceph/ceph-ansible/pull/1895#issuecomment-329601987,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA3tX1KNHTbg-S9vS804YOECPTe9Zp9xks5siY6igaJpZM4PX6yv
.

--
Cheers
––––––
Sébastien Han
Principal Software Engineer, Storage Architect
"Always give 100%. Unless you're giving blood."
Mail<EMAIL_ADDRESS>Address: 11 bis, rue Roquépine - 75008 Paris

Sure, I've submitted the alternate approach in https://github.com/ceph/ceph-ansible/pull/1900


mgmt, storage, regen from PR 29534

regen from https://github.com/Azure/azure-rest-api-specs/pull/29534
Previous regen didn't cover all instances of this maxpagesize change.
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
com.azure.resourcemanager:azure-resourcemanager-storage

I cannot get through the error
https://dev.azure.com/azure-sdk/public/_build/results?buildId=3898434&view=logs&j=08302e96-a521-55ec-4878-06d3e3995667&t=3fab0f3b-8042-51d0-0456-b1f18b054d77&l=304
The change is for new code, that should not affect any lib other than resourcemanager.

/check-enforcer override


Row DnD CodeSandbox Example not working:  Error:

Describe the bug
The React Table Row DnD example on CodeSandbox is not working.  I get console errors saying, "Cannot read property 'TARGET' of undefined."  The error appears to be on line 87, in the Row . component
To Reproduce
Steps to reproduce the behavior:

Go to 'https://codesandbox.io/s/github/tannerlinsley/react-table/tree/master/examples/row-dnd'
See error

Thanks in advance and thanks for the excellent React Table!
Screenshots

Desktop (please complete the following information):

OS: MacOS Mojave 10.14.16
Browser Chrome
Version Updating Google Chrome
Version 79.0.3945.130 (Official Build) (64-bit)

Found a fix.  I had to update the version of react-dnd in the package.json in the https://codesandbox.io/s/github/tannerlinsley/react-table/tree/master/examples/row-dnd example.
Replace the existing version for react-dnd in this package.json with the current version of react-dnd (in my case it was "^10.0.2") and it should work fine.

Would you submit a PR that applies this fix?

Would you submit a PR that applies this fix?

Put together a pull for this https://github.com/tannerlinsley/react-table/pull/1939

Now codesanbox example has access denied.
I see message "Request failed with status code 403"

Now codesanbox example has access denied.
I see message "Request failed with status code 403"

It's important to note that the url in the examples is hardcoded so If you're testing the pull by looking at the readme in my fork its going to send you to to tannerlinsley's master branch
To test my fix checking out my pull on codesandbox will get you to the fixed branch
As for the 403 This looks to be more an issue with codesandbox than this library, specifically codesandbox's ability to connect to git hub. There was a bit of down time recorded recently with git hub api requests
I was temporarily able to reproduce this error with codesandbox links from other libraries as well. Checking again it seems they have resolved.
examples of sandboxes that were giving me the same error:
https://codesandbox.io/s/github/react-dnd/react-dnd/tree/gh-pages/examples_hooks_js/00-chessboard
https://codesandbox.io/s/github/react-dnd/react-dnd/tree/gh-pages/examples_hooks_ts/04-sortable/simple
examples that were working:
https://codesandbox.io/s/react-new
https://codesandbox.io/s/yjzyzr29ov

Fixed


Mirgate to use new built-in control flow

Migrate to use a new built-in control flow to up runtime faster and drop the bundle size
AFTER

BEFORE

@gnaigaliot have you ran the schematic for this or you did this manually ?


Configure agent against VSTS use collection url is busted

You can configure agent use url with /defaultcollection
-- like https://tingms.visualstudio.com/defaultcollection/
Config will succeed, but the agent can't connect to message queue.
Current workaround: when config agent against VSTS, make sure use account url without /defualtcollection
-- like https://tingms.visualstudio.com

This is a server bug, a fix is checked-in will deploy to service within 2-3 weeks.


Collection.matching(be.present) returns True if empty

Following code
browser.all('.some-random-and-for-sure-is-not-presented-in-a-dom-class').matching(be.present)

returns True but it should be False
This leads to situations when
browser.all('.some-random-and-for-sure-is-not-presented-in-a-dom-class').should(be.present) passes
and
browser.all('.some-random-and-for-sure-is-not-presented-in-a-dom-class').should(be.absent) fails.

Hm... That's an interesting case...
Actually be.present is not a "collection condition", it is not supposed to
be called on browser.all(selector).should(HERE)
You even should get a warning in IDE like PyCharm.
To achieve what you want you are supposed to use have.size*
But the case is yet interesting... Maybe we should consider allowing users
to have conditions that can be called both on single element and collection
of elements. Just... This is pretty complicated thing to analyze and
investigate all edge cases. For this definitely not a bug... Yet I'll think
what to do to make API even more friendly and natural, yet powerful and
straightforward.
On Mon, Jan 2, 2023, 13:24 SanKolts @.***> wrote:

Following code
browser.all('.some-random-and-for-sure-is-not-presented-in-a-dom-class').matching(be.present)
returns
True
But it should be
False
This leads to situations when
browser.all('.some-random-and-for-sure-is-not-presented-in-a-dom-class').should(be.present)
passes
and
browser.all('.some-random-and-for-sure-is-not-presented-in-a-dom-class').should(be.absent)
fails.
—
Reply to this email directly, view it on GitHub
https://github.com/yashaka/selene/issues/465, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAO6ZHQTIGMZYIVIDWNWR5TWQK3HHANCNFSM6AAAAAATOXPIHI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Settings setting shortcut thing

fixes #254
Adds SettingsBaseModel.find_field and set_field to find and set a parameter name from anywhere within the nested Settings

Hello @richardjgowers! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file gufe/settings/models.py:

Line 66:80: E501 line too long (80 > 79 characters)

In [5]: class Foo(BaseModel):
   ...:     temp: FloatQuantity['kelvin']
   ...:

In [6]: f = Foo(temp='10 K')

In [7]: f
Out[7]: Foo(temp=<Quantity(10.0, 'kelvin')>)

In [8]: f = Foo(temp='10')
---------------------------------------------------------------------------
ValidationError                           Traceback (most recent call last)
Cell In[8], line 1
----> 1 f = Foo(temp='10')

File ~/mambaforge/envs/openfe_env/lib/python3.10/site-packages/pydantic/main.py:341, in pydantic.main.BaseModel.__init__()

ValidationError: 1 validation error for Foo
temp
  Cannot convert from 'dimensionless' (dimensionless) to 'kelvin' ([temperature]) (type=type_error.dimensionality; units1=dimensionless; units2=kelvin; dim1=dimensionless; dim2=[temperature]; extra_msg=)

@dwhswenson I'm not sure we have to be worried about stray strings on Quantities.  It will only "work" if the string is also valid as a Quantity, so not paths, and simple ints/floats are "upcasted" into Quantities easily.  I think you're rightly worried about bad variable names here (temperature is much better than temp for example), but that's not really made much worse by this feature

@richardjgowers : You've got the mistake I'm concerned about backwards. I'm worried about stray "quantities" on strings (when given as string). If I thought temp controlled temperature, but it actually controlled a tempfile name, I could easily do this:
In [1]: from pydantic import BaseModel

In [2]: class Foo(BaseModel):
   ...:     temp: str = "tempfile.dat"  # a filename
   ...:

In [3]: f = Foo(temp="10 K")

In [4]: f
Out[4]: Foo(temp='10 K')

That works just fine, and could lead to confusion and even incorrect science. Sure, it is user error, but we're giving them the gun and making it easier to point it at their foot.


General Issue: Increase test coverage for derive_param_exist_flag.R

Background Information
We need to increase test coverage for our functions. The below screenshot has the function and gap in test coverage that we need to write additional unit tests for derive_param_exist_flag.

Definition of Done
New tests written that covers the red gap area for derive_param_exist_flag.R.
Use devtools::test_coverage() to reproduce the report

Hey @jeffreyad  we keep these open till we merge everything into main


Add École 2600

Website: https://www.ecole2600.com

@valimero Please provide us with:

the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course.

Hello @philipto,
There is some information:

The school street address: Quai François Truffaut, 78180 Montigny-le-Bretonneux, France
URL of a an IT-related long-term course: https://www.ecole2600.com/#formation

@valimero Thank you for the clarification. Pull request merged.


reword FAU_GENs

to more closely mimic the CC Part 2.  but not too perfectly...

It mimics...maybe too perfectly.


[cxx-interop] Inject escapability for the C++ standard library

We only add conditional annotations because those do not break backward
compatibility (we might import span and similar view types as
non-escapable in the future). We inject these annotations in the
importer to make sure we have consistent behavior acress the different
standard library implementations. Once we can ship APINotes for the STL
and we have conditional escapability support in APINotes we can migrate
to that solution. But it is not possible as of today and Clang already
has precedent of injecting information for the STL with lifetimebound.
rdar://139065558

This needs to be rebased one https://github.com/swiftlang/swift/pull/77764 lands.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

I tried to look into the CI failure in Windows, and it is really odd. The names of the template parameters are missing where the assertion fails and the template seems to be imported as a module. I am redoing this PR to not to rely on the parameter names for the STL.

@swift-ci please smoke test


Mock server certificate DN for Register and Data Holder are the same

Describe the bug
Mock server certificate DN for Register and Data Holder are the same, which makes things a bit confusing. The certificates themselves are different, so that's good, but both CN's are called 'register.mock'.
Wouldn't it be more straight forward for the server certificate to have CN=mock-data-holder, or something along those lines?
To Reproduce
$ openssl x509 -subject -noout -in register.pem
subject=CN = register.mock, C = AU, ST = ACT, L = Canberra, O = ACCC, OU = CDR

$ openssl x509 -subject -noout -in server.pem
subject=CN = register.mock, C = AU, ST = ACT, L = Canberra, O = ACCC, OU = CDR

Thank you for getting in touch with us to raise this issue.
We have logged the issue and will include your suggestion in a future release.

Hi @ttomttom,
This issue has been rectified in our latest Mock Register production release v.1.3.2


Whisper resize file

Coverage remained the same at 88.734% when pulling 86a5fd7dc926e3f6777ee8f5ce489c989b7b3508 on eserte:whisper-resize-file into d5dc6a07d4bfe13a14db74b595740cdc22d18531 on graphite-project:master.

You can also use standard whisper-resize.py for a single file, you just need to provide schema as CLI parameter instead of a config file.
Not sure if need to merge that. @AlexAkulov ?

Advantage of using whisper-auto-resize is that it's not necessary to manually (= error prone) find the correct retention etc. schema from the config file, especially if there are many patterns.

True.


How to it with Multiple Database

Firstly I would like to thank you for writing such a clean dapper repository pattern, it really made my job easier, the reason I open this issue (not issue actually), I wanted to know is there any way I can use multiple database ? In the example I can see you are using "AddDbConnectionInstantiatorForRepositories" method, I have a use case to use multiple MySqlConnection in the application, any help/suggestions will be appreciated.

Hi! Thanks!
I have thought about this scenario too. If you have two MySQL connections, for example, both would have the same signature and I'm not sure how dependency injection handles this.. I think you would have an runtime error and might just need to have explicit constructors for dependency injection which would be a pain IMO. I think there is a better solution out there and I'm open to some ideas.. do you have any suggestions?

Hi,
Thanks for your response, I am looking for the best possible solution, I will do let you know once I come across a better solution to handle it.

@niteshkatare Can you try this method with this library? I think it will work: https://stackoverflow.com/a/48387767/997088


Waveshare 3.5 Pi2B+ Black screen

I built the config using the following configuration
sudo cmake -DSPI_BUS_CLOCK_DIVISOR=6 -DWAVESHARE35B_ILI9486=ON -DARMV7A=ON ..
Made sure I killed the fcb driver,
Below is my boot config
dtparam=audio=on
hdmi_force_hotplug=1
#max_usb_current=1
hdmi_group=2
hdmi_mode=1
hdmi_mode=87
hdmi_cvt 640 480 60 6 0 0 0
hdmi_drive=2
display_rotate=0
Also tried
hdmi_group=2
hdmi_mode=87
hdmi_cvt=320 240 60 1 0 0 0
hdmi_force_hotplug=1
after building and making the config it all seems to compile just fine with no errors.
When I then execute the driver the screen just stays black.
If i put the original LCD35B-show-V2 driver back reboot, retro pi shows up fine. If I then execute the fbcp-lil.. driver whilst the normal driver is running the screen turns off. So that atleast confirms that something is happening.
If you know what the issue could be I would GREATLY appreciate it.

Nevermind I removed all settings in the /boot/config.txt file and replaced it with
hdmi_group=2
hdmi_mode=87
hdmi_cvt=320 240 60 1 0 0 0
hdmi_force_hotplug=1

In #82 @Mootikins identified a problem that prevented ILI9341 displays from starting up in some cases. It is possible that the issue would affect ILI9486 as well. A fix was pushed in at https://github.com/juj/fbcp-ili9341/commit/b2eeec1de91dc6967e3331c37dcec0fcecb1b8b0, so you git pull or reclone to get the fix, may be worth a shot.
Though this reads like you were already able to resolve the issue, so I'll close this one up.


Rename manifest apply to install

Part of https://github.com/istio/istio/pull/25737 istioctl install
To keep it align with istioctl uninstall https://github.com/istio/istio/pull/25076

@shamsher31: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
f266f9d3d7a6d0a623fa5d98faffe3950130496a
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes_istio

@shamsher31: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
f266f9d3d7a6d0a623fa5d98faffe3950130496a
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test unit-tests_istio

/cherrypick release-1.7

@jwendell: new pull request created: #26167

In response to this:

/cherrypick release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Python extension fails to load when editing .py file at drive root. (Using circuitpython, this is required)

Use case
When using Adafruit's Circuitpython, the editing of .py files is a necessity at root level on a drive. (i.e. "P:\code.py")
Environment data

VS Code version: 1.55.2
Extension version: v2021.4.765268190
Windows 10 19042.928
Python version: Python 3.9.4 (tags/v3.9.4:1f2e308, Apr  4 2021, 13:27:16) [MSC v.1928 64 bit (AMD64)] on win32
Type of virtual environment used: n/a
Value of the python.languageServer setting: Pylance v2021.4.2

Expected behaviour
For the Python extension to load.
Actual behaviour
Python extension does not load. Rotating progresss indicator with "Python extension loading..." message. High CPU load and much thrashing of the hard drive.
Steps to reproduce:

Create a .py file at root level on any drive (Either Circuitpython drive or at root level on anything else at root level)
Edit said file in vs.code
Wait, forever. Witness hard drive thrashing with high CPU load. Extension fails to load. Thrashing seems to finish after a while.

Thanks for the bug report! We investigate issues in order based on priority and severity, which includes the impact it has on your ability to use the extension to do productive work, and the number of people affected. If other users come forward and leave a comment demonstrating they are seeing/reproducing the problem then we will raise this issue's priority.
If you think your issue is more of a question or configuration problem rather than a bug, please ask on Stack Overflow with the visual-studio-code and python labels for help.
Thanks for your understanding and patience!

I have the same problem. When I try to edit a .py file on the CIRCUITPY drive the python extension is stuck loading and I get a high CPU load warning.
After reading this issue I tried editing .py files on the root level of different drives and I get the same problem, but only if I open the root level folder (e.g. C:) in vscode. When I drag the file into vscode without opening the folder, the python extension loads normally.
I also get this problem when I edit a .py file in a different folder (e.g. Documents) and I add a root level folder to the workspace, the python extension stops working and is stuck loading. I can have many files from a root level folder open in vscode and the extension works, but as soon as I open a root level folder (doesn't have to be the same as the files location) in vscode, the extension crashes.
I guess the problem that is causing the python extension to fail is having a root level folder open in vscode. This is very annoying when editing circuitpython files, since these are always on root level.
I hope this will help and that the issue will get fixed soon.

Having the same issue: the Python extension will fail to load with either "Python extension loading..." or "Discovering Python Interpreters" notifications when trying to edit a .py file located on a drive's root directory.
That is a major issue for anyone developping CircuitPython code as the files have to reside on the device's root directory to support CircuitPython's inner loop development.
The failed loading of the Python extension prevents loading the CircuitPyton extension, which is a major hinderance.
Windows 11, clean install of VS Code, Python, Pylance and CircuitPython extensions only.


NIFI-3242: Avoid double scheduling of a task due to quartz imprecision

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

cc @markap14

@mgaido91 thanks for the fix! The code looks good to me. I do believe it addresses the issue. Kinda hard to verify a timing issue but I can verify that the logic appears correct and that everything still seems to work. +1 merged to master.


Getting clipboard error while using vagrant 2.26 with virtualbox 6.1.0

I get this error after following the steps mentioned in #178 and using @scoter-oracle 's solution
A customization command failed:

["modifyvm", :id, "--clipboard", "bidirectional"]

The following error was experienced:

#<Vagrant::Errors::VBoxManageError: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["modifyvm", "37c87f70-98ed-4729-bc37-29338849a4e0", "--clipboard", "bidirectional"]

Does anyone know how to solve this?

Hi, this is a Vagrant issue and we already shared the same to the Vagrant team.
The syntax has changed from "--clipboard" to "--clipboard-mode" in VirtualBox 6.1.
While waiting for a fix from the Vagrant team you can use:
VBoxManage modifyvm  --clipboard-mode disabled|hosttoguest|guesttohost|bidirectional

BTW, you can open an other issue to the Vagrant Project.

This is failing again under Vagrant 2.2.7 and Virtual Box 6.
A customization command failed:
["modifyvm", :id, "--clipboard-mode", "bidirectional"]
The following error was experienced:
#<Vagrant::Errors::VBoxManageError: There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["modifyvm", "4a38a623-f3f1-4464-a423-39d48c758a97", "--clipboard-mode", "bidirectional"]
Stderr: Oracle VM VirtualBox Command Line Management Interface Version 6.0.16
(C) 2005-2020 Oracle Corporation
All rights reserved.

VirtualBox 6.1 introduced the "--clipboard-mode" difference from "--clipboard".
We already managed it on VirtualBox and next release for VirtualBox 6.1 will accept both options.

VirtualBox 6.1.4 accepts both "--clipboard-mode" and "--clipboard" so the issue should be fixed in any case.


Add extern module attribute

A few points I want to comment on:

This copy-and-paste test tests only parsing, but I didn't see any attribute check for syscall case.
Doesn't the addition of module name to identifiers corrupt idMap? For example, I want a function/variable kernel32, won't they conflict with each other?
I changed the type of data to Identifier, and now syscall case uses index field as a syscall number, which is bad. I just think I misunderstood you somewhere. I thought about the union of Identifier and uint for data, but that's bad too.

A few points I want to comment on:
* This copy-and-paste test tests only parsing, but I didn't see any attribute check for syscall case.
Yea, the way it works right now would require generating an executable for linux, which I didn't do. Ideally needs a test too.
* Doesn't the addition of module name to identifiers corrupt idMap? For example, I want a function/variable kernel32, won't they conflict with each other?
No, because idMap is just used to intern strings for O(1) comparison on identifiers. Storing strings there is fine.
* I changed the type of data to Identifier, and now syscall case uses index field as a syscall number, which is bad. I just think I misunderstood you somewhere. I thought about the union of Identifier and uint for data, but that's bad too.
Isn't data supposed to be generic and low-level, like []u8 or something. It means we can place there anything, we just need a way for interpreting it.
Commented on that.

Forgot to mention, that you need to strip " on string literal, before putting it into idMap. Also, check the test output of driver.context.printAstSema = true; in tester. Did you figure out how to run single test?

Yeah, sure, I read the build/testing manual.  I didn't get to see the output for that exact test, because I corrected it. It brought another issue, though.


Problem  with Custom Architecture in PPO (get_action function)

Description:
I’m implementing a custom architecture for the PPO algorithm following this guide. After initializing custom evolvable actor and critic models, I create a population and start training. However, I encounter a ValueError related to the Simplex() constraint in Categorical distribution within the get_action function.
Code:
class MLPActor(nn.Module):
    def __init__(self, input_size, output_size):
        super().__init__()
        self.linear1 = nn.Linear(input_size, 64)
        self.linear2 = nn.Linear(64, output_size)
        self.relu = nn.ReLU()

    def forward(self, x):
        x = self.relu(self.linear1(x))
        return self.linear2(x)

class MLPCritic(nn.Module):
    def __init__(self, input_size, output_size):
        super().__init__()
        self.linear1 = nn.Linear(input_size, 64)
        self.linear2 = nn.Linear(64, output_size)
        self.relu = nn.ReLU()

    def forward(self, x):
        x = self.relu(self.linear1(x))
        return self.linear2(x)

# Initialization
actor = MLPActor(state_dim[0], action_dim)
evolvable_actor = MakeEvolvable(actor, input_tensor=torch.randn(state_dim[0]), device=device)
critic = MLPCritic(state_dim[0], 1)
evolvable_critic = MakeEvolvable(critic, input_tensor=torch.randn(state_dim[0]), device=device)

pop = create_population(algo="PPO", state_dim=state_dim, action_dim=action_dim, one_hot=one_hot,
                        net_config=None, actor_network=evolvable_actor, critic_network=evolvable_critic,
                        INIT_HP=INIT_HP, population_size=INIT_HP["POP_SIZE"], device=device)

# Training
trained_pop, pop_fitnesses = train_on_policy(
    env=env, env_name=env_name, algo="PPO", pop=pop,
    swap_channels=INIT_HP['CHANNELS_LAST'], max_steps=200000, evo_steps=10000,
    eval_steps=None, eval_loop=1, target=200., tournament=tournament,
    mutation=mutations, wb=False,
)

Error Message:
ValueError: Expected parameter probs (Tensor of shape (8, 3)) of distribution Categorical(probs: torch.Size([8,
3])) to satisfy the constraint Simplex(), but found invalid values:
tensor([[-1.2414,  0.7774,  1.4640],
        [-4.2800,  1.3044,  3.9756],
        [-2.9853,  1.2023,  2.7830],
        [-1.6700,  0.8740,  1.7960],
        [-1.5798,  0.8345,  1.7452],
        [-1.6246,  0.8406,  1.7839],
        [-2.1904,  0.9093,  2.2811],
        [-2.5390,  1.1135,  2.4254]])

Additional Information:
I suspect the issue is due to action_values not being normalized into a probability distribution before passing into Categorical.
Any suggestions on modifying get_action or ensuring action_values align with the requirements for a Categorical distribution would be appreciated.

Yep your suspicions are correct. You need to use a Softmax output activation if you're using PPO with discrete actions.

Yes, adding a softmax layer to the actor did help - an oversight on my part! Initially, I was confused by the lack of a softmax in get_action, but now I assume it's applied during the PPO initialization.
Btw, you might consider adding a complete tutorial to the "Using Custom Architecture" page in the documentation. And consider a more tricky architecture.

Done

If you would be interested in contributing a tutorial that would be really appreciated and we can support you!


Exporting additional modules pollutes localStorage

You can write to localStorage/sessionStorage via the dot-notation (localStorage.foo = 'bar';)
When exporting the storage, the additional modules are also passed onto that storage in the same way.
// src/index.js
// [...]

module.exports = storage
module.exports.isSupported = isSupported
module.exports.CookieStorage = CookieStorage
module.exports.MemoryStorage = MemoryStorage

Because of that the storage then ends up having the additional exports written to it as strings:

ah, of course. It seems like the only way around this would be to export a function:
import createStorage from 'local-storage-fallback'

const storage = createStorage()

or written another way
const storage = require('local-storage-fallback')()

The last option sounds the best, having to call a function everywhere it is imported is tedious and not that intuitive.
If exporting via storage (or similar) you can also use default exports at the same time when using the import/export syntax
export default storage
export { storage, isSupported, CookieStorage, MemoryStorage }

Agreed. I had issues before transpiling for web and ended up switching to module.exports but i'll give it a go.

@philipvonbargen fixed in 4.0.0 Thanks for the PR!


remove redundant state machines

How are you finding these? Do you have an analyzer that you are running or just manually combing through to find these?
I'd like to have some of these locally if so 😄


Update pureconfig, pureconfig-cats-effect to 0.17.3

About this PR
📦 Updates

com.github.pureconfig:pureconfig
com.github.pureconfig:pureconfig-cats-effect

from 0.17.2 to 0.17.3
📜 GitHub Release Notes - Changelog - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.pureconfig" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.github.pureconfig" }
}]

labels: library-update, early-semver-minor, semver-spec-patch, commit-count:1

Superseded by #199.


Cannot install on RPi

What OS are you using (uname -a, or Windows version)?
RPi Raspian
Linux pinkipi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
What programming language are you using (C/C++/Go/Rust)?
go
What did you expect to see and what you saw instead?

$ go get github.com/zserge/webview
pkg-config --cflags  -- gtk+-3.0 webkit2gtk-4.0
Package gtk+-3.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing gtk+-3.0.pc' to the PKG_CONFIG_PATH environment variable No package 'gtk+-3.0' found Package webkit2gtk-4.0 was not found in the pkg-config search path. Perhaps you should add the directory containing webkit2gtk-4.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'webkit2gtk-4.0' found
pkg-config: exit status 1

You have to install GTK, please read README.md carefully.

Perhaps you could say something like "Install GTK" in the getting started section for Go (at least, I cannot find anything like that there).

Sorry, I am not a user of Debian. But what I can tell you is that zserge uses gtk+ 3.0 and recommends that you use search engines for help. For example, how to install GTK using apt-get

I have installed libwebkit2gtk-4.0 (on Raspbian) and then it built ok and ran. You might want to add that to the install notes.


Add option to serve media files locally using nginx

Description
This PR proposes an example solution to issue #2449.
It allows selecting a local nginx instance to serve media files.
This is just a bare bones implementation that could serve as a base for serving media files.
I added an nginx container. This container has a volume mapped where django stores its media files. Routes and services are added in the traefik configuration to route {{domain.name}}/media/*
requests to the nginx instance which serves them.
Rationale
It makes deploying very simple and small scale projects easier as @demestav eloquently expressed in his issue.
Use case(s) / visualization(s)
When using AWS or GCP is not a good option. Serve the /media files using nginx.
/media/ --> nginx -----------|
django ---> uwsgi -----------o--> user
/static/ -> whitenoise ------|

Fix #2449
Closes #3260

@ArkadiuszMichalRys, I pulled your version and got the following error:
Creating my_awesome_project_django_1_499f9d077e92   ... error

ERROR: for my_awesome_project_django_1_499f9d077e92  Cannot create container for service django: invalid volume specification: 'my_awesome_project_production_django_media:my_awesome_project/media:rw': invalid mount config for type "volume": invalid mount path: 'my_awesome_project/media' mount path must be absolute

ERROR: for django  Cannot create container for service django: invalid volume specification: 'my_awesome_project_production_django_media:my_awesome_project/media:rw': invalid mount config for type "volume": invalid mount path: 'my_awesome_project/media' mount path must be absolute

Looks like there's a slash missing: services:django:volumes - production_django_media:my_awesome_project/media should be services:django:volumes - production_django_media:my_awesome_project/media.

@dahifi, thank you for the feedback. I will look into it. The two volume configurations you posted look identical so I guess there's a typo in the second one.

@dahifi, I should have tested my initial changes better. There were a few issues which should now be resolved.
This time I tested the generated files without modifying anything so I couldn't forget to commit any changes I made.

Hi ! Thank you, I was exactly looking for something like this. I tried your setup, but have you tried it on production with https enabled ? For now I couldn't find my media. I'm digging into Nginx.
Anyway, it's a good idea.

@sorasful Thank you for your suggestions! They were all justified so I implemented them as you suggested.

@sorasful Thank you for your suggestions! They were all justified so I implemented them as you suggested.

Great stuff, what's happened to this cool enhancement?

I think it might be because this seems like a very niche application. I just added it because I was using it for my own server. The repository seems to be aimed at more advanced deployments where you would really benefit from hosting the media on Amazon S3 or Google Cloud Storage.
I am happy to fix any issues in case there is something I need to add to get this merged.

I think it might be because this seems like a very niche application. I just added it because I was using it for my own server. The repository seems to be aimed at more advanced deployments where you would really benefit from hosting the media on Amazon S3 or Google Cloud Storage.
I am happy to fix any issues in case there is something I need to add to get this merged.

INHO, Cookiecutter leaves a hole by not providing an option for local media serving. @browniebroke What say you?

Thanks a lot! This was helpful to me.

Do we have news about this ? This could really be a great feature.

Thank you very much for this PR @arrys it helped me set this up for my project. Can you give advice on what needs to be further implemented so media links can only be accessed by logged in users?

Hopefully this helps you, @Braintelligence.
I don't know if this would be the best approach so take this with a grain of salt.
Depending on your requirements you might just make the file names hard to guess. This is not exactly secure, just a deterrent.
You could also try authentication based on subrequest results. This would be slightly more work to get implemented and might not suit your access control model.
As far as I know there is no easy way to serve the media files through nginx while using Djangos access control.
You could make Django serve the media files but this is discouraged by the Django developers.

@sorasful, @Afrowave, Is there something I should do?
There seems to be another take on this by @ghostforpy in a different pull request: #3260.
I am not entirely sure on how to proceed here.

I've updated this with the latest changes from master. I changed to using nginx as soon as cloud provider is none, which I think is pretty much what folks need?

I've updated the documentation, could folks proof read it and let me know whether what I wrote is clear, understandable, without typos, etc...? Thanks

Thanks for contributing this feature!


Treasury Dash v0.2 WIP PR

Goals:

current INDEX balances (amt, usd) for Analytics and Growth Working Groups
inflow and outflow charts for AWG and GWG
Txn-level pivotable data for AWG and GWG

@josephd8 I took into account the final feedback from Matt, let's merge this PR and close the issue


Upgrade webapp to use graphile-worker 0.14.0-rc.0

Setting the migration env var won't do anything (except output some warnings) if the migration has already been completed or if no migrations have been applied yet, i.e. on first start.
When multiple instances are started simultaneously, there is a chance of race conditions. Even though it's not possible to lock tables with Prisma, the internal graphile-worker migration won't happen if any locked jobs (< 4h) are detected. This should be enough to catch any issues.
If a worker errors and doesn't start due to this, a simple restart should fix it. I would prefer not to require a restart + unsetting the env var by default.
An option would be to use an alternative Postgres client just for this, which is also not desirable. But we may require this in future, depending on how we choose to add the custom SQL batching function.
Another option would of course be to go back to hard-requiring a restart and not starting any workers when the migration env var is set. It's ugly, but it works.
Production
Would recommend a slow but graceful shutdown to prevent having to use the env var. There should be no locked jobs on next start and the migration should complete without any issues.
If that isn't possible, set FAIL_LOCKED_JOBS_FOR_MIGRATION=true and temporarily switch to a single instance to perform the migration.
Also: Backups.
Closes #396
✅ Checklist

[x] I have followed every step in the contributing guide
[x] The PR title follows the convention.
[x] I ran and tested the code works
[x] More testing just to be safe
[x] Create migration docs

Testing
# Required for upgrading graphile-worker to v0.14 when graceful shutdown is impossible or impractical.
# FAIL_LOCKED_JOBS_FOR_MIGRATION=true

Upgrading with these instructions should be enough. Tested with and without any jobs in locked state. Also different versions and migration state.

Changelog

Upgrade to 0.14.0-rc.0
Rename CronItem.pattern to CronItem.match
Adjust parsers for SQL function call returns
Add env var to fail locked jobs on startup, so migration can proceed when graceful shutdown is not an option
Detect migration errors and advise re env var

Screenshots

💯

0.15.0 was released yesterday. The only change being that migration files are now embedded as strings. Just in case of unforeseen bugs, we should stay on 0.14.0-rc.0 for now.

Waiting for v0.16 release and #689 before finishing this up.


TaskWeaver UI frontend

Is your feature request related to a problem? Please describe.
Please provide insight how we can leverage chainlit or other UI enabled on TaskWeaver for demos

We are working on a frontend

Hi @amitlals we have developed a simple UI using chainlit for demonstration purpose. Please go to playground/UI for more information.


"Go back" doesn't go back to the original editor group

Issue Type: Bug

Create two editor groups (side by side)

group1: foo.cpp
group2: foo.cpp bar.cpp

Position the cursor somewhere in group2/foo.cpp

Ctrl-Tab to switch to group2/bar.cpp

"Go back" (Alt-Left Arrow)

Expected: switch to group2/foo.cpp with the previous cursor position
Actual: swtiching to group1/foo.cpp !
This is very frustrating, especially when group1 has other active editors (which would be deactivated and switched to foo.cpp)
VS Code version: Code 1.45.1 (5763d909d5f12fe19f215cbfdd29a91c0fa9208a, 2020-05-14T08:27:22.494Z)
OS version: Linux x64 4.15.0-101-generic
Remote OS version: Linux x64 5.3.0-51-generic

What is the duplicate issue # ? Thanks

Probably #9526

Thanks @gjsjohnmurray , #9526 seems a related, but different issue.
Maybe #88470? @bpasero, can you confirm? (and please note the duplicate issue # when adding the duplicate lablel in the future)

https://github.com/microsoft/vscode/issues/9526

Thank you for the clarification @bpasero!


TKE doesn't work

master-head(8/13)
Steps:

Create a TKE cluster with default value

Results:
Cluster failed to provision
More Info:
We can fix it by changing some default values. But the controller and scheduler status is red

Reproduction:
Cluster creation failed due to unavailable disk type/size. It succeeded after changing disk type/size.
There are multiple disk options provided by Tencent Cloud: LOCAL_BASIC/LOCAL_SSD/CLOUD_BASIC/CLOUD_PREMIUM/CLOUD_SSD.
Available options depend on the region & instance type. It may even be possible that none is available when the disk is sold out. The cloud provider UI suggests users choose another instance type in this case.

Can UI get that info dynamically? This is the related API grabbed from the console
Request URL: https://iaas.cloud.tencent.com/cgi/capi?i=cbs/DescribeCbsQuota&uin=xxx
Request Method: POST
#Request body
{
  "serviceType": "cbs",
  "action": "DescribeCbsQuota",
  "regionId": 8,
  "data": {
    "inquiryType": "INQUIRY_CVM_CONFIG",
    "payMode": "postPay",
    "deviceClass": [
      "VSHIO"
    ],
    "zoneIds": [
      800001
    ],
    "cpu": 4,
    "mem": 16
  }
}
#Response
{
  "data": {
    "code": 0,
    "message": "",
    "codeDesc": "Success",
    "detail": [
      {
        "available": 0,
        "throttleTime": "1998-11-11 00:00:00",
        "instanceFamily": "I1",
        "storageType": "cloudPremium",
        "deviceClass": "VSHIO",
        "diskType": "data",
        "payMode": "postPay",
        "maxiDiskSize": 16000,
        "miniDiskSize": 10,
        "zoneId": 800001
      },
      {
        "available": 0,
        "throttleTime": "1998-11-11 00:00:00",
        "instanceFamily": "I1",
        "storageType": "cloudPremium",
        "deviceClass": "VSHIO",
        "diskType": "root",
        "payMode": "postPay",
        "maxiDiskSize": 500,
        "miniDiskSize": 50,
        "zoneId": 800001
      },
      {
        "available": 0,
        "throttleTime": "1998-11-11 00:00:00",
        "instanceFamily": "I1",
        "storageType": "cloudSSD",
        "deviceClass": "VSHIO",
        "diskType": "data",
        "payMode": "postPay",
        "maxiDiskSize": 16000,
        "miniDiskSize": 100,
        "zoneId": 800001
      },
      {
        "available": 0,
        "throttleTime": "1998-11-11 00:00:00",
        "instanceFamily": "I1",
        "storageType": "cloudSSD",
        "deviceClass": "VSHIO",
        "diskType": "root",
        "payMode": "postPay",
        "maxiDiskSize": 500,
        "miniDiskSize": 50,
        "zoneId": 800001
      }
    ],
    "cbsQuota": 500000,
    "curStorageNum": 0
  },
  "message": "",
  "code": 0
}

Incorrect controller/scheduler unhealthy status is an upstream bug tracked in https://github.com/rancher/rancher/issues/11496

API doc: https://cloud.tencent.com/document/api/362/16318

Version: master master-head (8/28/19)
Confirmed fix. Different disk types can be queried according to different zones.


Add new feature

Hi @rafaelcamargo.
How are u buddy ?! :)
What's your idea to implement this type of terminal ?!
terminal emulator
so cute :D

lol, seems no to be an easy thing to put in practice. However, the closest thing about it that came up to my mind was the possibility to install different themes either for editor or terminal.
Regard the Retro Term, that's really cute 👏


Always call listenBefore hooks on browser navigation

Fixes #71

Dude, this is one of the cleanest PRs I have ever seen, @stevoland. Thank you! :clap:

Pleasure, thanks for your libraries


feat: add valibot validator

closes #73

Codecov Report
Attention: Patch coverage is 93.75000% with 8 lines in your changes missing coverage. Please review.

Project coverage is 68.61%. Comparing base (a8150ed) to head (0804760).
Report is 4 commits behind head on main.

Files
Patch %
Lines

src/utils.ts
0.00%
4 Missing :warning:

src/index.tsx
94.11%
3 Missing :warning:

src/valibot.ts
98.57%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##             main      #79       +/-   ##
===========================================
- Coverage   97.11%   68.61%   -28.51%
===========================================
  Files           3       10        +7
  Lines        2460     1370     -1090
  Branches      256      266       +10
===========================================
- Hits         2389      940     -1449
- Misses         71      424      +353
- Partials        0        6        +6

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


Undelegation period set to two weeks for the first two months after TokenStaking deployment

For the first two months after the deployment of TokenStaking contract, the undelegation period is two weeks and it goes back to two months once two months after the deployment passes.
The staking contract guarantees that an undelegated operator’s stakes will stay locked for a period of time after undelegation, and thus available as collateral for any work the operator is engaged in. Two weeks is the absolute minimum given that the beacon group's active time is also two weeks. Changing undelegation period does not affect keep-ecdsa deposits since the stake is locked by the sanctioned application until all deposits the given staker has are redeemed and keeps are closed.
Shorten undelegation period should allow less stressful onboarding of new stakers to the system as well as allow for faster migration in case a new staking contract is deployed.

@mhluongo I need an adult to review the numbers: 2 weeks for the first 2 months and 2 months after that?


@3x - Retina HD

Support only @2x - Retina, plz add @3x - Retina HD

In sprity v1.0.0 it is possible to generate multiple sprite with different resolutions. So please give it a try.


Work Package wp-em.csv

I would like to work on this please!

wp-em-results.csv

I completed this work package.

Results : wp-em_results.csv

I would like to work on this please!

Results of Phase 1
wp-em-results.csv

I completed this work package.

Result of Phase 2
Abhishek Arvindkumar-Upadhyay_HW3.csv

Results of Phase
wp-em-results.csv
2

Results of Phase 2
wp-em-results.csv


Expose show_progress_bar option for Hugging Face vectorizer

Currently, hf.embed() and hf.embed_many() always display the tqdm progress bar while building embeddings, even if it's just for one embedding.
# Embed a sentence
hf = HFTextVectorizer(model="sentence-transformers/all-MiniLM-L6-v2")
test = hf.embed("This is a test sentence.")

Ask: expose show_progress_bar parameter of the underlying HuggingFace model, so one can choose if to display a progress bar.
model = SentenceTransformer('sentence-transformers/all-MiniLM-L6-v2')
model.encode(["This is a test sentence."], show_progress_bar=False)

So one can do:
# Embed a sentence
hf = HFTextVectorizer(model="sentence-transformers/all-MiniLM-L6-v2")
test = hf.embed("This is a test sentence.", show_progress_bar=False)

We can accomplish this by exposing optional **kwargs on the .embed() + .embed_many() (and async variants). Each vectorizer would be responsible for parsing and passing through kwargs as needed. @antonum is this something you might be able to contribute if you're looking for a little OSS action ;) ?

Solved thanks to https://github.com/redis/redis-vl-python/pull/236


add vector similarity based labelling method to core library

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
After labelling some data, it would be cool to update and assign predictions to the most similar once programmatically.
Describe alternatives you've considered
N.A.
Additional context
import pandas as pd
import numpy as np
import argilla as rg

# Load annotated data and calculate average vector for each annotation
ds = rg.load("ray-summit", query="status: Validated")
df = ds.to_pandas()
df["vectors"] = df["vectors"].apply(lambda x: x.get("vector"))
df['avg_vector'] = df.vectors.apply(lambda x: pd.np.array(x))
avg = df.groupby('annotation')['avg_vector'].apply(np.mean)
avg_dict = avg.to_dict()

# Get most similar record for each annotation and update its prediction
for key in avg_dict:
    ds = rg.load("ray-summit", vector=("vector", avg_dict[key].tolist()))
    for rec in ds:
        pred = dict(rec.prediction)
        if sum(pred.values()) != 1:
            pred[key] = 1
        rec.prediction = list(pred.items())
    rg.log(ds, name="ray-summit", chunk_size=25)

Dani: "I think this kind of method should be included in the core library, I don't know where but it's worth thinking about it. maybe under argilla.labeling which was intended for programmatic methods"


glueValidateProgram Current framebuffer is invalid

Hello,
I am integrating GPUImage with RoysWriter, which is the Apple official sample code.
( https://developer.apple.com/library/ios/samplecode/RosyWriter/Introduction/Intro.html )
What I am trying to do is displaying the result from GPUImage on RosyWriterPreviewView,
but when I call GPUImagePicture::initWithImage,
I got "Current framebuffer is invalid" from glueValidateProgram in RosyWriterPreviewView and gets stuck on the last image from the camera.
If I comment out GPUImagePicture::initWithImage, the error is gone and RosyWriterPreviewView shows the image from the camera continuously.
I guess GPUImagePicture::initWithImage takes the controllability of Frame Buffer and never let it go. Is there any approach to take Frame Buffer back?
Please let me know if any problem and thank you for precious time on my question.

GPUImage can do everything RosyWriter does, so I see no need to have to integrate it with that project.
If you do wish to have the two work together, you'll need a GPUImageTextureInput or GPUImageTextureOutput (depending on which way you go), and will need to pass a texture between the two processing sides. RosyWriter and GPUImage will also need to have their OpenGL context within the same share group.
The cube example within GPUImage shows how to do this with an arbitrary OpenGL context.