Background messaging not working

Background handler is registered in main as documented.
Foreground message is received fine, however when I switch app to background and send same message, it fails:
Launching lib\main.dart on moto g 10 in debug mode...
Running Gradle task 'assembleDebug'...
√ Built build\app\outputs\flutter-apk\app-debug.apk
I/flutter (20692): [IMPORTANT:flutter/shell/platform/android/android_context_vk_impeller.cc(60)] Using the Impeller rendering backend (Vulkan).
Debug service listening on ws://<IP_ADDRESS>:56366/he5bnByKkyE=/ws
Syncing files to device moto g 10...
I/flutter (20692): main
D/ANH     (20692): Network 179 is available.
D/ANH     (20692): Network has been connected.
D/ANH     (20692): Network 180 is available.
I/Choreographer(20692): Skipped 175 frames!  The application may be doing too much work on its main thread.
I/flutter (20692): Opened App: {data: {}}
D/ProfileInstaller(20692): Installing profile for com.deonic.sodium
D/FANH    (20692): message received
I/flutter (20692): onMessage (foreground) : {data: {}, id: 0:1734990257426322%db4081c0db4081c0, body: message body}
I/flutter (20692): app state changed !!!!: AppLifecycleState.inactive
I/flutter (20692): app state changed !!!!: AppLifecycleState.hidden
I/flutter (20692): app state changed !!!!: AppLifecycleState.paused
I/FA      (20692): Application backgrounded at: timestamp_millis:<PHONE_NUMBER>702
D/FANH    (20692): message received
W/FirebaseMessaging(20692): Missing Default Notification Channel metadata in AndroidManifest. Default value will be used.
I/FANH Worker(20692): Creating background FlutterEngine instance.
I/AdrenoVK-0(20692): QUALCOMM build          : 436a040394, Ie3251bda9d
I/AdrenoVK-0(20692): Build Date              : 10/14/20
I/AdrenoVK-0(20692): Shader Compiler Version : EV<IP_ADDRESS>
I/AdrenoVK-0(20692): Local Branch            :
I/AdrenoVK-0(20692): Remote Branch           :
I/AdrenoVK-0(20692): Remote Branch           :
I/AdrenoVK-0(20692): Reconstruct Branch      :
I/AdrenoVK-0(20692): Build Config            : S P 10.0.7 AArch64
I/AdrenoVK-0(20692): Driver Path             : /vendor/lib64/hw/vulkan.adreno.so
I/flutter (20692): [IMPORTANT:flutter/shell/platform/android/android_context_vk_impeller.cc(60)] Using the Impeller rendering backend (Vulkan).
E/WM-WorkerWrapper(20692): Work [ id=f0947439-28d3-46f2-88a5-bccc913e5075, tags={ com.tangrainc.azure_notification_hub.AzRemoteMessageBackgroundWorker } ] failed because it threw an exception/error
E/WM-WorkerWrapper(20692): java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Expedited WorkRequests require a Worker to provide an implementation for
E/WM-WorkerWrapper(20692):  getForegroundInfo()
E/WM-WorkerWrapper(20692): 	at androidx.work.impl.utils.futures.AbstractFuture.getDoneValue(AbstractFuture.java:515)
E/WM-WorkerWrapper(20692): 	at androidx.work.impl.utils.futures.AbstractFuture.get(AbstractFuture.java:474)
E/WM-WorkerWrapper(20692): 	at androidx.work.impl.WorkerWrapper$2.run(WorkerWrapper.java:316)
E/WM-WorkerWrapper(20692): 	at androidx.work.impl.utils.SerialExecutorImpl$Task.run(SerialExecutorImpl.java:96)
E/WM-WorkerWrapper(20692): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
E/WM-WorkerWrapper(20692): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
E/WM-WorkerWrapper(20692): 	at java.lang.Thread.run(Thread.java:923)
E/WM-WorkerWrapper(20692): Caused by: java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Expedited WorkRequests require a Worker to provide an implementation for
E/WM-WorkerWrapper(20692):  getForegroundInfo()
E/WM-WorkerWrapper(20692): 	at androidx.work.impl.utils.futures.AbstractFuture.getDoneValue(AbstractFuture.java:515)
E/WM-WorkerWrapper(20692): 	at androidx.work.impl.utils.futures.AbstractFuture.get(AbstractFuture.java:474)
E/WM-WorkerWrapper(20692): 	at androidx.work.impl.WorkerWrapper$1.run(WorkerWrapper.java:298)
E/WM-WorkerWrapper(20692): 	at android.os.Handler.handleCallback(Handler.java:938)
E/WM-WorkerWrapper(20692): 	at android.os.Handler.dispatchMessage(Handler.java:99)
E/WM-WorkerWrapper(20692): 	at android.os.Looper.loop(Looper.java:250)
E/WM-WorkerWrapper(20692): 	at android.app.ActivityThread.main(ActivityThread.java:7806)
E/WM-WorkerWrapper(20692): 	at java.lang.reflect.Method.invoke(Native Method)
E/WM-WorkerWrapper(20692): 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
E/WM-WorkerWrapper(20692): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:958)
E/WM-WorkerWrapper(20692): Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Expedited WorkRequests require a Worker to provide an implementation for
E/WM-WorkerWrapper(20692):  getForegroundInfo()
E/WM-WorkerWrapper(20692): 	at androidx.work.impl.utils.futures.AbstractFuture.getDoneValue(AbstractFuture.java:515)
E/WM-WorkerWrapper(20692): 	at androidx.work.impl.utils.futures.AbstractFuture.get(AbstractFuture.java:474)
E/WM-WorkerWrapper(20692): 	at androidx.work.impl.utils.WorkForegroundRunnable$1.run(WorkForegroundRunnable.java:100)
E/WM-WorkerWrapper(20692): 	... 7 more
E/WM-WorkerWrapper(20692): Caused by: java.lang.IllegalStateException: Expedited WorkRequests require a Worker to provide an implementation for
E/WM-WorkerWrapper(20692):  getForegroundInfo()
E/WM-WorkerWrapper(20692): 	at androidx.work.Worker.getForegroundInfo(Worker.java:127)
E/WM-WorkerWrapper(20692): 	at androidx.work.Worker$2.run(Worker.java:100)
E/WM-WorkerWrapper(20692): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
E/WM-WorkerWrapper(20692): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
E/WM-WorkerWrapper(20692): 	at java.lang.Thread.run(Thread.java:923)
I/WM-WorkerWrapper(20692): Worker result FAILURE for Work [ id=f0947439-28d3-46f2-88a5-bccc913e5075, tags={ com.tangrainc.azure_notification_hub.AzRemoteMessageBackgroundWorker } ]

I tried the same scenario using your main.dart code and got same failure symptoms:
Launching lib\main.dart on moto g 10 in debug mode...
Running Gradle task 'assembleDebug'...
√ Built build\app\outputs\flutter-apk\app-debug.apk
Installing build\app\outputs\flutter-apk\app-debug.apk...
I/flutter (24759): [IMPORTANT:flutter/shell/platform/android/android_context_vk_impeller.cc(60)] Using the Impeller rendering backend (Vulkan).
Debug service listening on ws://<IP_ADDRESS>:57782/vrVZjwEMqVo=/ws
Syncing files to device moto g 10...
I/flutter (24759): main
D/ANH     (24759): Network 179 is available.
D/ANH     (24759): Network has been connected.
I/flutter (24759): Opened App: {data: {}}
I/Choreographer(24759): Skipped 183 frames!  The application may be doing too much work on its main thread.
D/ProfileInstaller(24759): Installing profile for com.deonic.sodium
I/ANH     (24759): updated installation
D/ANH     (24759): Network 180 is available.
D/FANH    (24759): message received
I/flutter (24759): onMessage: {data: {}, id: 0:1734991428426225%db4081c0db4081c0, body: message body}
I/FA      (24759): Application backgrounded at: timestamp_millis:<PHONE_NUMBER>268
D/FANH    (24759): message received
W/FirebaseMessaging(24759): Missing Default Notification Channel metadata in AndroidManifest. Default value will be used.
I/FANH Worker(24759): Creating background FlutterEngine instance.
I/AdrenoVK-0(24759): QUALCOMM build          : 436a040394, Ie3251bda9d
I/AdrenoVK-0(24759): Build Date              : 10/14/20
I/AdrenoVK-0(24759): Shader Compiler Version : EV<IP_ADDRESS>
I/AdrenoVK-0(24759): Local Branch            :
I/AdrenoVK-0(24759): Remote Branch           :
I/AdrenoVK-0(24759): Remote Branch           :
I/AdrenoVK-0(24759): Reconstruct Branch      :
I/AdrenoVK-0(24759): Build Config            : S P 10.0.7 AArch64
I/AdrenoVK-0(24759): Driver Path             : /vendor/lib64/hw/vulkan.adreno.so
I/flutter (24759): [IMPORTANT:flutter/shell/platform/android/android_context_vk_impeller.cc(60)] Using the Impeller rendering backend (Vulkan).
E/WM-WorkerWrapper(24759): Work [ id=412f6cf9-a489-4500-b6c1-eff035efd2ff, tags={ com.tangrainc.azure_notification_hub.AzRemoteMessageBackgroundWorker } ] failed because it threw an exception/error
E/WM-WorkerWrapper(24759): java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Expedited WorkRequests require a Worker to provide an implementation for
E/WM-WorkerWrapper(24759):  getForegroundInfo()
E/WM-WorkerWrapper(24759): 	at androidx.work.impl.utils.futures.AbstractFuture.getDoneValue(AbstractFuture.java:515)
E/WM-WorkerWrapper(24759): 	at androidx.work.impl.utils.futures.AbstractFuture.get(AbstractFuture.java:474)
E/WM-WorkerWrapper(24759): 	at androidx.work.impl.WorkerWrapper$2.run(WorkerWrapper.java:316)
E/WM-WorkerWrapper(24759): 	at androidx.work.impl.utils.SerialExecutorImpl$Task.run(SerialExecutorImpl.java:96)
E/WM-WorkerWrapper(24759): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
E/WM-WorkerWrapper(24759): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
E/WM-WorkerWrapper(24759): 	at java.lang.Thread.run(Thread.java:923)
E/WM-WorkerWrapper(24759): Caused by: java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Expedited WorkRequests require a Worker to provide an implementation for
E/WM-WorkerWrapper(24759):  getForegroundInfo()
E/WM-WorkerWrapper(24759): 	at androidx.work.impl.utils.futures.AbstractFuture.getDoneValue(AbstractFuture.java:515)
E/WM-WorkerWrapper(24759): 	at androidx.work.impl.utils.futures.AbstractFuture.get(AbstractFuture.java:474)
E/WM-WorkerWrapper(24759): 	at androidx.work.impl.WorkerWrapper$1.run(WorkerWrapper.java:298)
E/WM-WorkerWrapper(24759): 	at android.os.Handler.handleCallback(Handler.java:938)
E/WM-WorkerWrapper(24759): 	at android.os.Handler.dispatchMessage(Handler.java:99)
E/WM-WorkerWrapper(24759): 	at android.os.Looper.loop(Looper.java:250)
E/WM-WorkerWrapper(24759): 	at android.app.ActivityThread.main(ActivityThread.java:7806)
E/WM-WorkerWrapper(24759): 	at java.lang.reflect.Method.invoke(Native Method)
E/WM-WorkerWrapper(24759): 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
E/WM-WorkerWrapper(24759): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:958)
E/WM-WorkerWrapper(24759): Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Expedited WorkRequests require a Worker to provide an implementation for
E/WM-WorkerWrapper(24759):  getForegroundInfo()
E/WM-WorkerWrapper(24759): 	at androidx.work.impl.utils.futures.AbstractFuture.getDoneValue(AbstractFuture.java:515)
E/WM-WorkerWrapper(24759): 	at androidx.work.impl.utils.futures.AbstractFuture.get(AbstractFuture.java:474)
E/WM-WorkerWrapper(24759): 	at androidx.work.impl.utils.WorkForegroundRunnable$1.run(WorkForegroundRunnable.java:100)
E/WM-WorkerWrapper(24759): 	... 7 more
E/WM-WorkerWrapper(24759): Caused by: java.lang.IllegalStateException: Expedited WorkRequests require a Worker to provide an implementation for
E/WM-WorkerWrapper(24759):  getForegroundInfo()
E/WM-WorkerWrapper(24759): 	at androidx.work.Worker.getForegroundInfo(Worker.java:127)
E/WM-WorkerWrapper(24759): 	at androidx.work.Worker$2.run(Worker.java:100)
E/WM-WorkerWrapper(24759): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
E/WM-WorkerWrapper(24759): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
E/WM-WorkerWrapper(24759): 	at java.lang.Thread.run(Thread.java:923)
I/WM-WorkerWrapper(24759): Worker result FAILURE for Work [ id=412f6cf9-a489-4500-b6c1-eff035efd2ff, tags={ com.tangrainc.azure_notification_hub.AzRemoteMessageBackgroundWorker } ]

@deoscode to eliminate the possibility of a misconfig, can you try the the sameple app in this repo and just change the Azure Notification hub settings so you can test with your hub.
Also please provide what version of flutter are you using as well the version of android.

An update.
I cloned a fresh version of your repo.
Opened the example folder in android studio
updates using my google-services.json
update AndroidManifest.xml to use my azure hub settings.
changed the build.gradle to use my google services application id.
Build.gradle
defaultConfig {
applicationId = "com.deonic.sodium"
it still wouldnt build with compileSdk=35
Switched it down to 34 in build.gradle, as below
android {
namespace = "com.tangrainc.azure_notification_hub_example"
compileSdk = 34
ndkVersion = flutter.ndkVersion
it built and ran!
However, same symptoms as originally reported for background mesaages.
√ Built build\app\outputs\flutter-apk\app-debug.apk
Installing build\app\outputs\flutter-apk\app-debug.apk...
I/flutter (28254): [IMPORTANT:flutter/shell/platform/android/android_context_vk_impeller.cc(60)] Using the Impeller rendering backend (Vulkan).
Debug service listening on ws://<IP_ADDRESS>:52826/_kFd4yIBtSg=/ws
Syncing files to device moto g 10...
I/flutter (28254): main
D/ANH     (28254): Network 187 is available.
D/ANH     (28254): Network has been connected.
D/ANH     (28254): Network 188 is available.
I/Choreographer(28254): Skipped 174 frames!  The application may be doing too much work on its main thread.
I/flutter (28254): Opened App: {data: {}}
D/ProfileInstaller(28254): Installing profile for com.deonic.sodium
I/Choreographer(28254): Skipped 34 frames!  The application may be doing too much work on its main thread.
D/FANH    (28254): message received
I/flutter (28254): onMessage: {data: {}, id: 0:1735049656275762%db4081c0db4081c0, body: message body}
W/FirebaseMessaging(28254): Unable to log event: analytics library is missing
W/FirebaseMessaging(28254): Unable to log event: analytics library is missing
D/FANH    (28254): message received
W/FirebaseMessaging(28254): Unable to log event: analytics library is missing
W/FirebaseMessaging(28254): Missing Default Notification Channel metadata in AndroidManifest. Default value will be used.
I/FANH Worker(28254): Creating background FlutterEngine instance.
I/AdrenoVK-0(28254): QUALCOMM build          : 436a040394, Ie3251bda9d
I/AdrenoVK-0(28254): Build Date              : 10/14/20
I/AdrenoVK-0(28254): Shader Compiler Version : EV<IP_ADDRESS>
I/AdrenoVK-0(28254): Local Branch            :
I/AdrenoVK-0(28254): Remote Branch           :
I/AdrenoVK-0(28254): Remote Branch           :
I/AdrenoVK-0(28254): Reconstruct Branch      :
I/AdrenoVK-0(28254): Build Config            : S P 10.0.7 AArch64
I/AdrenoVK-0(28254): Driver Path             : /vendor/lib64/hw/vulkan.adreno.so
I/flutter (28254): [IMPORTANT:flutter/shell/platform/android/android_context_vk_impeller.cc(60)] Using the Impeller rendering backend (Vulkan).
E/WM-WorkerWrapper(28254): Work [ id=ca121068-d68c-41f4-bc6a-60b13a59f15c, tags={ com.tangrainc.azure_notification_hub.AzRemoteMessageBackgroundWorker } ] failed because it threw an exception/error
E/WM-WorkerWrapper(28254): java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Expedited WorkRequests require a Worker to provide an implementation for
E/WM-WorkerWrapper(28254):  getForegroundInfo()
E/WM-WorkerWrapper(28254): 	at androidx.work.impl.utils.futures.AbstractFuture.getDoneValue(AbstractFuture.java:515)
E/WM-WorkerWrapper(28254): 	at androidx.work.impl.utils.futures.AbstractFuture.get(AbstractFuture.java:474)
E/WM-WorkerWrapper(28254): 	at androidx.work.impl.WorkerWrapper$2.run(WorkerWrapper.java:316)
E/WM-WorkerWrapper(28254): 	at androidx.work.impl.utils.SerialExecutorImpl$Task.run(SerialExecutorImpl.java:96)
E/WM-WorkerWrapper(28254): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
E/WM-WorkerWrapper(28254): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
E/WM-WorkerWrapper(28254): 	at java.lang.Thread.run(Thread.java:923)
E/WM-WorkerWrapper(28254): Caused by: java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Expedited WorkRequests require a Worker to provide an implementation for
E/WM-WorkerWrapper(28254):  getForegroundInfo()
E/WM-WorkerWrapper(28254): 	at androidx.work.impl.utils.futures.AbstractFuture.getDoneValue(AbstractFuture.java:515)
E/WM-WorkerWrapper(28254): 	at androidx.work.impl.utils.futures.AbstractFuture.get(AbstractFuture.java:474)
E/WM-WorkerWrapper(28254): 	at androidx.work.impl.WorkerWrapper$1.run(WorkerWrapper.java:298)
E/WM-WorkerWrapper(28254): 	at android.os.Handler.handleCallback(Handler.java:938)
E/WM-WorkerWrapper(28254): 	at android.os.Handler.dispatchMessage(Handler.java:99)
E/WM-WorkerWrapper(28254): 	at android.os.Looper.loop(Looper.java:250)
E/WM-WorkerWrapper(28254): 	at android.app.ActivityThread.main(ActivityThread.java:7806)
E/WM-WorkerWrapper(28254): 	at java.lang.reflect.Method.invoke(Native Method)
E/WM-WorkerWrapper(28254): 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
E/WM-WorkerWrapper(28254): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:958)
E/WM-WorkerWrapper(28254): Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Expedited WorkRequests require a Worker to provide an implementation for
E/WM-WorkerWrapper(28254):  getForegroundInfo()
E/WM-WorkerWrapper(28254): 	at androidx.work.impl.utils.futures.AbstractFuture.getDoneValue(AbstractFuture.java:515)
E/WM-WorkerWrapper(28254): 	at androidx.work.impl.utils.futures.AbstractFuture.get(AbstractFuture.java:474)
E/WM-WorkerWrapper(28254): 	at androidx.work.impl.utils.WorkForegroundRunnable$1.run(WorkForegroundRunnable.java:100)
E/WM-WorkerWrapper(28254): 	... 7 more
E/WM-WorkerWrapper(28254): Caused by: java.lang.IllegalStateException: Expedited WorkRequests require a Worker to provide an implementation for
E/WM-WorkerWrapper(28254):  getForegroundInfo()
E/WM-WorkerWrapper(28254): 	at androidx.work.Worker.getForegroundInfo(Worker.java:127)
E/WM-WorkerWrapper(28254): 	at androidx.work.Worker$2.run(Worker.java:100)
E/WM-WorkerWrapper(28254): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
E/WM-WorkerWrapper(28254): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
E/WM-WorkerWrapper(28254): 	at java.lang.Thread.run(Thread.java:923)
I/WM-WorkerWrapper(28254): Worker result FAILURE for Work [ id=ca121068-d68c-41f4-bc6a-60b13a59f15c, tags={ com.tangrainc.azure_notification_hub.AzRemoteMessageBackgroundWorker } ]
Have you tried running your example in background and checking the debug logs?
Which version of compileSdk are you using?

Hey @deoscode I just tested this on the API 34 emulator and I do not see the problem you are experiencing. I was running Flutter 3.24 so the example app was working fine. Tried sending a push notification (both app in the background and closed) and the handler was triggered and the message was logged.
I then updated the example to use latest flutter SDK:
Flutter 3.27.1 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 17025dd882 (11 days ago) • 2024-12-17 03:23:09 +0900
Engine • revision cb4b5fff73
Tools • Dart 3.6.0 • DevTools 2.40.2

I had to adjust some build properties of the sample app in order for it to compile (those are pushed now to the repo). Then did a rebuild and tested again with app in background and closed. All is working fine:

I'm testing with the default Android FCM that is available in Azure portal when you try to make a test push.

Hi Peter,
I think its something to do with me changing the applicationId to deonic.sodium.com.
users will not be expecting to use your google settings json  and default channels. Im not sure if your code caters for this?
I will try defaulting to your appId and see if that works.
Thanks for your help, greatly appreciated.Wishing you a happy new year.
RegardsRavi
Yahoo Mail: Search, organise, conquer
On Fri, 27 Dec 2024 at 4:52 pm, Peter @.***> wrote:
Hey @deoscode I just tested this on the API 34 emulator and I do not see the problem you are experiencing. I was running Flutter 3.24 so the example app was working fine. Tried sending a push notification (both app in the background and closed) and the handler was triggered and the message was logged.
I then updated the example to use latest flutter SDK:
Flutter 3.27.1 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 17025dd882 (11 days ago) • 2024-12-17 03:23:09 +0900
Engine • revision cb4b5fff73
Tools • Dart 3.6.0 • DevTools 2.40.2
I had to adjust some build properties of the sample app in order for it to compile (those are pushed now to the repo). Then did a rebuild and tested again with app in background and closed. All is working fine:
image.png (view on web)
I'm testing with the default Android FCM that is available in Azure portal when you try to make a test push.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

For sure I do not expect users to use the sample app id :)
The only places where the example app id is present are in the android build gradle, iOS project and google-services.json. So I'm pretty sure that the problem is unrelated to changing the app id.

Please also try to run in in the emulators as it might be related to the phone and the Android version it is running. Searching for this error shows problems when using worker manager and expedited requests, but the background process that I use in the plugin is marked as non expedited, so not sure why you are getting the error.
https://github.com/PeterStaev/az_notification_hub/blob/be8c55a21f2817037e1a3ce702809c81050eb094/android/src/main/kotlin/com/tangrainc/azure_notification_hub/AzRemoteMessageBackgroundWorker.kt#L44-L47

I will try downloading the virtual "Medium Phone API 35" device, as I have always used my physical device for testing.
motorola moto g(10), Android 11.0 ("R")
arm64
api 30-ext15

Actually after re-reading the docs, I might have an idea what is going on. Seems on android 12 or less when setExpedited() is used it tries to create a foreground service and requires a notification to be shown to the user. I will see to refactor the code to account for this scenario. Will try to have a fix for the new year :)

@deoscode please try version 1.1.2. It should have the problem fixed.

Peter,
I can confirm its now working in v1.1.2
D/FANH    (31809): message received
I/flutter (31809): onMessage (foreground) : {data: {raised: 2024-12-23 22:05:01, source: Iodini, priority: 2, body: All text info, title: #99: Powered Up}, id: 0:1735567042284673%db4081c0f9fd7ecd}
I/flutter (31809): _save
I/flutter (31809): title:#99: Powered Up
I/flutter (31809): Status: Note Saved Successfully
I/flutter (31809): app state changed !!!!: AppLifecycleState.inactive
I/flutter (31809): app state changed !!!!: AppLifecycleState.hidden
I/flutter (31809): app state changed !!!!: AppLifecycleState.paused
D/FANH    (31809): message received
I/FA      (31809): Application backgrounded at: timestamp_millis:<PHONE_NUMBER>418
I/FANH Worker(31809): Creating background FlutterEngine instance.
I/AdrenoVK-0(31809): QUALCOMM build          : 436a040394, Ie3251bda9d
I/AdrenoVK-0(31809): Build Date              : 10/14/20
I/AdrenoVK-0(31809): Shader Compiler Version : EV<IP_ADDRESS>
I/AdrenoVK-0(31809): Local Branch            :
I/AdrenoVK-0(31809): Remote Branch           :
I/AdrenoVK-0(31809): Remote Branch           :
I/AdrenoVK-0(31809): Reconstruct Branch      :
I/AdrenoVK-0(31809): Build Config            : S P 10.0.7 AArch64
I/AdrenoVK-0(31809): Driver Path             : /vendor/lib64/hw/vulkan.adreno.so
I/flutter (31809): [IMPORTANT:flutter/shell/platform/android/android_context_vk_impeller.cc(60)] Using the Impeller rendering backend (Vulkan).
I/FANH Worker(31809): Worker not started, queueing message
I/WM-WorkerWrapper(31809): Worker result SUCCESS for Work [ id=080b9148-526b-47cf-b9ac-eb1ef1b0b3f5, tags={ com.tangrainc.azure_notification_hub.AzRemoteMessageBackgroundWorker } ]
I/flutter (31809): onBackgroundMessage: {data: {raised: 2024-12-23 22:05:01, source: Iodini, priority: 2, body: All text info, title: #99: Powered Up}, id: 0:1735567057942330%db4081c0f9fd7ecd}
Thank you so much.
Wishing you a happy New Year!


Toggle Input by code

Hi,
first of all, thank you for this great plug-in! It made my day.
I'm using it in UE4.27 and I was able to toggle the input using Project Properties (defining a Key combination to do so).
But now, I want to do the same, by code, but seems it's not working or I'm doing sth wrong.
I've used FImGuiModuleProperties, and then called SetInputEnabled(true). Like this:
this->GuiModuleProperties.SetInputEnabled(true);
It compiles and runs, but menu bar still only rendering and no accepting inputs. Any idea? In the README it's mentioned that also can be changed on a Properties file, but couldn't find it on the tree.
Thank so much!

I solved it. I upgraded the plug-in to add this option and to have it available on the Project's Settings.
Now it's working!


Resposne with WWW-Authenticate header when no token provided

According to RFC 6750, we need to respond with a WWW-Authenticate header when no token is presented to the gateway.

Should that be in the response for an invalid access token too?

I have to read the spec more carefully, but IIRC a an invalid token should
have a www header but with different values, error values. If so, I'll add
this at the same time.
On Jul 24, 2017 11:08 AM, "anestos"<EMAIL_ADDRESS>wrote:

Should that be in the response for an invalid access token too?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/curityio/nginx_introspect/issues/11#issuecomment-317363689,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACYio9M4cPxzdc0am84pocvsjESpa865ks5sRF8bgaJpZM4Og41o
.


CI: remove Azure sdist job

The GHA linux_meson workflow already does a couple of tests from an sdist, test_venv_install and  python_debug. We can therefore remove it from the Azure setup.

You're correct @tylerjereddy, I'll make amends.
The pypa-build docs say

python -m build
A simple, correct Python build frontend. By default, a source distribution (sdist) is built from {srcdir} and a binary distribution (wheel) is built from the sdist. This is recommended as it will ensure the sdist can be used to build wheels.

The python_debug job uses build, but I think I need to remove the --wheel flag. That will build the wheel from the sdist.
The windows.yml full_build_sdist_wheel is definitely building the wheel from an sdist.

Two different jobs going the vcs->sdist->wheel route seems reasonable to me. There is very little chance that the sdist creation is platform-dependent, but also not 100% impossible (e.g., a generated file containing the git hash of the commit being built somehow working differently on Windows).

@tylerjereddy the most recent commit should have it following the vcs->sdist->whl route for the linux_meson::python_debug job. I'd prefer not to remove sdist related cruft from the ci/azure-pipelines.yml template. It makes more sense to me to wait for when the files are removed completely, which shouldn't be too much longer.

Also, the Windows 64 bit/no pythran job is already in windows.yml:: full_build_sdist_wheel, so remove that as well. The windows.yml jobs examine 3.9/3.10/3.11 whilst all doing different types of build.

https://github.com/scipy/scipy/actions/runs/4791999712/jobs/8523033610?pr=18351#step:4:26 shows that the python_debug job is building from sdist.

I'd prefer not to remove sdist related cruft from the ci/azure-pipelines.yml template. It makes more sense to me to wait for when the files are removed completely, which shouldn't be too much longer.

Seems fine, and that'd be the way I would have gone as well.


Use voluptuous for Verisure

Description:
Migration of the configuration check to voluptuous. Also are now constants used.
Related issue (if applicable): fixes 127528299
Example entry for configuration.yaml (if applicable):
verisure:
  username: USERNAME
  password: PASSWORD
  alarm: 1
  hygrometers: 0
  smartplugs: 1
  thermometers: 0
  locks: 0
  mouse: 1
  code_digits: 4

@persandstrom , would be nice if you could take a look at the changes and run a quick test. Thanks.

🐬

Other than the missing config option this seems to work well :+1:


As a user I would like to run packageless in a container

packageless needs an official Docker image. This image should be built and published to DockerHub as part of the packageless release process using a GitHub Actions workflow.

Hey @everettraven can you assign me this? I can work on this

Hey @everettraven can you assign me this? I can work on this

@DipayanP007 sure thing!

hey @everettraven can you provide me with the name of the image to be built?

and as I can see there is no Dockerfile. it would be good if you can provide me with the commands to build the project so that I can write the dockerfile too.

hey @everettraven can you provide me with the name of the image to be built?

@DipayanP007 The image name should be packageless
One thing to note is that this app requires access to the Docker daemon/socket. I don't think this should have any effect on the Dockerfile though.

yeah it won't be a problem for Dockerfile. We will only need to explicitly mount the docker socket while running the container. So can you give the commands to run the project?

yeah it won't be a problem for Dockerfile. We will only need to explicitly mount the docker socket while running the container. So can you give the commands to run the project?

@DipayanP007 To build the project you can run go build.
That should produce a binary file named packageless (packageless.exe if on Windows).
You can run the program with ./packageless
I was thinking it would be best to have that as an ENTRYPOINT though as there are many sub commands that can be run.
Here is a link to the documentation that you can browse for a bit more information (specifically the CLI section for info on sub commands ): https://everettraven.github.io/packageless/

Hey @DipayanP007 I just wanted to check in and see if this is still in progress?

@DipayanP007 Are you still interested in working on this?
If not I will un-assign you on this issue so that someone else can pick it up.
Thanks!

Hey @everettraven Sorry I have been a bit busy. You can unassign this

@DipayanP007 No worries, thanks!


PSA for new adopters - g and b values are flipped

I realise this repo hasn't been updated in over 4 years, I'm mostly just putting this here in case any new users come along and have trouble with it.
There's a typo in the main file for setting up the returned object, resulting in the g and b values to be flipped.
In these lines of code:
https://github.com/bfred-it/get-canvas-pixel-color/blob/master/index.js#L19
the object is set up like so:

pixel.r = pixel[0];
pixel.b = pixel[1];
pixel.g = pixel[2];
pixel.a = pixel[3];

The b value is coming from index 1 and g is coming from index 2, meaning the returned object (as well as the concatenated string) are wrong. This can be easily gotten around if you know the issue is there. Just letting people know the issue is there.

Oh god, thank you for this :D
I'll fix it

No problem, happy to help out :) Thanks for the quick response

Thanks for opening an issue on an old repo :)
I published it as 2.0.0, let me know if it works correctly for you

Updated and it's working great now. Thanks for the quick turnaround 👍


No update data returned when query has both errors and data

When gql return query results with errors, empty object returned from update or result option.
How can I get the data by calling apollo query even query has some errors?
Results returned from GrahqiQL:
{
  "errors": [
    {
      "message": "'NoneType' object has no attribute 'value'",
      "locations": [
        {
          "line": 7,
          "column": 11
        }
      ],
      "path": [
...
      ]
    },
    {
      "message": "17 is not a valid shotgun server id.",
      "locations": [
        {
          "line": 7,
          "column": 11
        }
      ],
      "path": [
...
      ]
    }
  ],
  "data": {
    "ple_asset": {
      "entities": {
        "edges": [
          {
            "node": {
              "name": "TST",
              "shotgun_model": null
            }
          },
          {
            "node": {
              "name": "NIJ",
...

Results from apollo smart query:
Global error handler {error: Error: GraphQL error: 'NoneType' object has no attribute 'value'
GraphQL error: 17 is not a valid s…}
update: {}
We got some result! {}__proto__: Object false 7
We've got an error! Error: GraphQL error: 'NoneType' object has no attribute 'value'
GraphQL error: 17 is not a valid shotgun server id.
    at new ApolloError (bundle.esm.js?74ca:63)
    at eval (bundle.esm.js?74ca:1641)
    at Object.next (Observable.js?a7b2:308)
    at notifySubscription (Observable.js?a7b2:130)
    at onNotify (Observable.js?a7b2:165)
    at SubscriptionObserver.next (Observable.js?a7b2:219)
    at eval (bundle.esm.js?74ca:858)
    at Set.forEach (<anonymous>)
    at Object.next (bundle.esm.js?74ca:858)
    at notifySubscription (Observable.js?a7b2:130)

Have you set the errorPolicy? https://www.apollographql.com/docs/react/data/error-handling/

have same issue, but with $apollo.mutate, I can confirm { errorPolicy: 'all' } is passed into the client but e.graphQLErrors?.length === 0 is empty.
Trying to trace the rror seems impossible, as all the client function calls for mutate don't appear to be used. Somehow, whatever $apollo.mutate is using to perform the mutation is bypassing everything.
quite confusing.


Make slider more stylable, and dynamically stylable beased on current value

I had a use-case for making my slider themable based upon the current value of the slider (think changing the background color of the slider based on the input)
To that end, I created a "styler" function that gets passed in as an option, and returns an object of CSS rules. This is then compared against any styles that the slider code creates (allowing the styler to optionally override anything based on its class), and applies the combined style using element.css()
Here is an example styler function:
var styler = function (className, sliderValue) {
			/*jshint sub:true*/
			var style = { 'override': true };
			var handleDiameter = 60;
			var handleRadius = handleDiameter / 2;
			var leftMargin = ($scope.slider.width / 2) - (handleRadius);
			switch(className) {
				case 'l':
				case 'r':
				case 's':
					style['display']			= 'none';
					break;
				case 'pointer':
					style['width']	 			= handleDiameter +'px';
					style['height'] 			= handleDiameter +'px';
					style['margin-top'] 		= '-'+handleRadius+'px';
					style['border-radius'] 		= handleRadius+'px';
					style['background-image'] 	= 'none';
					style['background'] 		= '#aaa';
					style['border'] 			= '6px solid #000';
					style['margin-left'] 		= leftMargin+'px';
					style['left']				= '0';
					break;
				case 'value':
					style['background']			= 'none';
					style['z-index']			= '2';
					style['margin-left']		= leftMargin+'px';
					style['margin-top']			= '-7.5px';
					style['width']				= '3em';
					style['text-align']			= 'center';
					style['font-size']			= '1.5em';
					break;
				case 'bg':
					var negativeColor = [255,0,0];
					var positiveColor = [0,255,0];
					var grey = [127,127,127];
					var fromColor, toColor, finalColor;
					if (sliderValue > 0) {
						toColor = grey;
						fromColor = positiveColor;
					}
					else {
						toColor = grey;
						fromColor = negativeColor;
					}
					var ratio = Math.abs(sliderValue) / 100;
					finalColor = [
						Math.ceil(fromColor[0]*ratio + toColor[0]*(1-ratio)).toString(16),
						Math.ceil(fromColor[1]*ratio + toColor[1]*(1-ratio)).toString(16),
						Math.ceil(fromColor[2]*ratio + toColor[2]*(1-ratio)).toString(16)
					];
					finalColor = '#' + finalColor[0] + finalColor[1] + finalColor[2];
					style['width']				= $scope.slider.width+'px';
					style['height']				= $scope.slider.height+'px';
					style['background']			= finalColor;
					break;
			}
			return style;
		};

hi Nagey, it looks like a great PR and the first one for ng-slider, I will merge it when back home and give you a feedback. Great job, thx

hi, I have tried to merge it and fix some small issues, like giving noop() function in case styler function not set in options..
but in your first example, your were using reference to $scope.slider, how do you manage it ?
example:
var leftMargin = ($scope.slider.width / 2) - (handleRadius);
thx

For that $scope.slider, I was buiding that based off of $window, and my particular layout. It's something that gets managed with my controller's onresize handler.
if you're curious, I set it up thusly:
var baseWidth;
		if ($window.innerWidth > 1200) {
			baseWidth = 1140;
		}
		else if ($window.innerWidth > 992) {
			baseWidth = 940;
		}
		else if ($window.innerWidth > 768) {
			baseWidth = 710;
		}
		else {
			baseWidth = $window.innerHTML - 45;
		}

		$scope.video.width = baseWidth * 2 / 3;
		$scope.video.height = $scope.video.width * 1/1.7777777777777777778;

		$scope.slider = {};

		$scope.slider.width = baseWidth / 3 - 20;
		$scope.slider.height =  baseWidth * 2 / 3 * 1/1.7777777777777777778;

Also committed a fix to make sure scope.options.styler is defined.

I didn't make this change, but you might want to consider changing line 112 of the Gruntfile.js to read as follows:
  grunt.registerTask('test-continuous', ['default', 'jshint', 'bower', 'karma:unit']);

That way you can be sure that your CI is running off of the most recent version of the code itself, not the most recent built version.

ok, thx for providing these details, I was then checking for vertical and 2 pointers slider, so it is taking time ;)

anything else I can to do move this forward?

any update on this?

I started merge it and then quit because of another stuff on different project, really sorry I try to move back to it soon.


[SPARK-19461] Remove some unused imports.

What changes were proposed in this pull request?
Remove some unused imports in CoarseGrainedSchedulerBackend and YarnSchedulerBackend.
How was this patch tested?
No need to test.

Can one of the admins verify this patch?

This is too trivial for a JIRA, and we don't make PRs to remove a few imports. Please close this. http://spark.apache.org/contributing.html


Landing Page

Landing Page
User Story
AS AN employer looking for candidates with experience building single-page applications
I WANT to view a potential employee's deployed React portfolio of work samples
SO THAT I can assess whether they're a good candidate for an open position
##Acceptance Criteria
GIVEN a single-page application portfolio for a web developer
WHEN I load the portfolio
THEN I am presented with a page containing a header, a section for content, and a footer

This has been completed


refactor: rollback effort to make field12 operations generic ( PROOF-773 )

Rationale for this change
It was decided that effort to make field12 operations generic was not appropriate at this time. Work related to the effort is rolled back. The base/field/arithmetic_utility component is all that remains.
What changes are included in this PR?

subtract_p is moved back to field12/base package and once again made to support only six limb operation
The base/field/element concept is removed
The base/field/element_example is removed

Are these changes tested?
Yes, from previous tests.

:tada: This PR is included in version 1.18.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


CR 7.3.2

7.3.2. Add fields to collect the following information on a female patient if she is pregnant: date of last menstruation, expected delivery date, and actual delivery date

Coverage increased (+0.2%) to 54.975% when pulling d86ec27ca519c7dcf4300eeb6b85dca63b45f8e2 on valvijo:master into 567648fa66b02634c3a1f017e89163745d7dbd21 on esaude:master.

 7.3.2. Add fields to collect the following information on a female patient if she is pregnant: date of last menstruation, expected delivery date, and actual delivery date

 Transfer patient between POC applications is not working


Add 'NEOPIXEL' to LED Type Dropdown

Sure the 'WS281x' type works, but from a User Experience standpoint, seeing "NeoPixel' near the top of the list would help avoid confusion.

Added


feat(birdie): file tree view for asset explorer

minor visual bug, switching from file tree -> table asset explorer, first time opening directories will result in lock icons missing, but if you reopen the directory it will show up correctly


proposal: spec: break break to

Example 1:
for i := 0; i < 10; i++ { // the `for` label implicit declaration here
  switch i {
  case 3:
    break for // break
  }
  fmt.Println("i:", i)
}

Output:
0
1
2

Example 2:
for i := 0; i < 6; i++ { // the `for1` label implicit declaration here
  for j := 0; j < 2; j++ { // the `for2` label implicit declaration here
    switch i {
    case 3:
      break for // break to the label for2
    }
    fmt.Println("i:", i)
  }
}

Output:
0
0
1
1
2
2
4
4
5
5

We already a break statement to name a label to break out of a labelled loop (https://go.dev/ref/spec#Break_statements).  What is the advantage of having another mechanism for doing the same thing?

We already a break statement to name a label to break out of a labelled loop (https://go.dev/ref/spec#Break_statements). What is the advantage of having another mechanism for doing the same thing?

It's just a suggest, the only advantage is you needn't maintain them and care about their name

Based on the brief discussion above, and the emoji voting, this is a likely decline.  Leaving open for four weeks for final comments.

No further comments.


Control blur size on win tk

How I can control blur size with tk? I wanna make animation how it blurred from 0 to 1 (for example)

I'm sorry, but the mica texture does not support this leven of customization


Use a single tab field separator in keywords.txt

Each field of keywords.txt is separated by a single true tab. When you use multiple tabs it causes the field to be interpreted as empty. On Arduino IDE 1.6.5 and newer an empty KEYWORD_TOKENTYPE causes the default editor.function.style coloration to be used (as with KEYWORD2, KEYWORD3, LITERAL2). On Arduino IDE 1.6.4 and older it causes the keyword to not be recognized for any special coloration.
Reference:
https://github.com/arduino/Arduino/wiki/Arduino-IDE-1.5:-Library-specification#keywords

thx, but not really important, our minimum requirement is 1.6.10 and the keywords.txt contains almost nothing ;)

I guess you didn't read carefully. I explained that the wrong formatting of keywords.txt caused incorrect keyword highlighting on Arduino IDE 1.6.5 and newer.
As to containing almost nothing, in the event that the rest of the keywords are added one day, don't you think it's valuable to have a correctly formatted model in place?

To explain my confusing answer and thoughts:

On Arduino IDE 1.6.4 and older it causes the keyword to not be recognized for any special coloration.

our minimum requirement is 1.6.10 -> so this part of your information was not relevant

I explained that the wrong formatting of keywords.txt caused incorrect keyword highlighting on Arduino IDE 1.6.5 and newer.

I understood the bug. The effective difference you explain is a color change from green to orange. In my opinion that's not a huge impact...

[..]  don't you think it's valuable to have a correctly formatted model in place?

Of course I appreciate your work and pull request. It is already merged ;)

My general opinion about keywords.txt:

Only used for highlighting (low benefit), Not used for auto completion (that would be a real benefit)
It is a redundant information about public members/functions, which is already known by the source code.
-> A waste of work time if managed manually.
A bot/CI should manage the content of the file.

@per1234 Do you have some scripts to test keywords.txt? I think it would be cool if you can share them?
Adafruit did some travis ci Arduino stuff. I think it would be good to add your code to  https://github.com/adafruit/travis-ci-arduino/blob/master/library_check.sh

Yes I do. It's here:
https://github.com/per1234/arduino-ci-script/blob/development/arduino-ci-script.sh#L1972-L2219
This code is still under active development. I'm getting close to a production release and will try to get that moving forward faster. It's been a bit slow because I run the script on a list of >8000 Arduino libraries and so far every run I find some minor bugs and additional things I want to check for. The upside is it's a pretty thorough test. I'm going to stop adding new features until after the release but I still need to get a bug-free run before it's ready to release.
There are also functions to check for other common problems with Arduino projects, in addition to the standard compilation tests.
I'm aware of the Adafruit script but this code is part of my own Arduino CI script, which I feel is superior (of course I'm biased). So I'd rather spend my time working on my own script rather than theirs. Of course the code is all open source and I welcome anyone to use it in any way they like.

Thanks for sharing :+1:

@Rotzbua I finally got the keywords.txt test script finalized and in a stable release of arduino-ci-script.


Look into image ratios

in the ratios we have three_to_ten, which is then actually 3:10.
But we use it like 10:3, which should be written like ten_to_three.
Fix the that the images that should have three_to_ten(3:10) use the 3:10.
If some images should have 10:3, use ratio ten_to_three
Look into the images that should be 16:9/aspect-video to have sixteen_to_nine(16:9)
Look into which images should have 9:16(nine_to_sixteen)
Check that names and ratio matches

Consider the ratio three_to_ten which is 3:10 and the value will be 3/10 = 0.3. But if we consider "full width image" component, in the groq query it says 10:3 but in the component it is three_to_ten.  Even in sanity it says { title: '10:3', value: 0.3 }, here if we use the same logic ten_to_three will be 10:3 and the value will be 10/3 = 3.333 but in sanity for the ratio 10:3 the value is 0.3.

The ratios would have to be fixed in sanity as well then to reflect correct name to value, but it would require an migration script for production maybe, so we will put this back into the backlog for when we have more time on our hands


Helper methods( Filtering and Updating) for Notification model

This PR adds helper methods  that facilitate provide important operations to the Notification model. That is, we can now get and filter by receiver which would be very useful for the inbox. Also, we can filter by unread, read, deleted, and the type of the notification and mark multiple notifications as deleted, undeleted, read, unread.

Closing statment:  In this pull request, we introduced helpful methods that streamline essential operations for the Notification model. With these additions, we can now retrieve and filter notifications by receiver. Additionally, we enabled filtering by unread, read, deleted, and notification type the ability as well as marking multiple notifications as deleted, undeleted, read, or unread.
@24raniwalar worked on the mark_x() and is_x() methods
@omarelkashef  worked on the filter and get methods

Issue Score: Excellent
Comments:
Nice set of functions, and really clean code. Great job!


chore(oci): migrate to ORAS Golang library v2

What this PR does / why we need it:
I could not create a PR on Zoran's https://github.com/helm/helm/pull/12310 so this combines the two with:

rebased
fixed broken tests
diffs from Zoran's https://github.com/helm/helm/pull/13382/commits/e88e515453acf28916327a6bc409b29311c70e24

Updates from oras.land/oras-go to oras.land/oras-go/v2. The main user facing change is that the --plain-http parameter is now required even when accessing OCI registries running on localhost.
Fixes https://github.com/helm/helm/issues/11821
Special notes for your reviewer:
I'm new to this codebase and some tests needed to be adjusted to match the new dependency, please look over the test changes to see if there are any issues with those.
If applicable:

[ ] this PR contains user facing changes (the docs needed label should be applied if so)
[x] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

Tests failed in CI, but pass on the mac. I assume the problem is with the credential backend.

Two of the commits are Unverified.

Hmm, since I cant do a PR on Zoran's repo, I'll probably have to merge  main instead of rebase.

Two of the commits are Unverified.

Hmm, since I cant do a PR on Zoran's repo, I'll probably have to merge main instead of rebase.

Fixed

Hi. Any update in merging this pr?

Upgrading here is good for Helm 4. Backport to Helm 3 I think we should (continue to) think hard about https://github.com/helm/helm/pull/13382/files#r1836977600


Selecting the address in source and destination submits the form

Loading of page takes more time - geocoder failed due to zero_results
after searching once if the source/destination is updated, datatable gives error : cannot reinitialize DataTable

2nd issue is resolved

Fixed the issues


Requirements document for the dataframe interchange protocol

Continued from gh-30. Main changes:

added chunking
added memory layout description including need to support multiple representations of missing data
added some more detail on the Arrow C Data Interface
addressed open review comments from gh-30

Also added one important TBD about the connection with the array data interchange protocol, with a suggestion to add that if and only if the supported dtypes allow (i.e., only boolean, integer and floating-point dtypes, and missing data as separate boolean masks).
Up-to-date rendered version: https://github.com/data-apis/dataframe-api/blob/dataframe-interchange-protocol/protocol/dataframe_protocol_summary.md

Hmm good question. The main motivation (from requirement 12 - maybe easier to read in rendered form in https://data-apis.org/dataframe-protocol/latest/design_requirements.html) is: _Must support chunking, i.e. accessing the data in “batches” of rows. _
Given that columns are contiguous in memory and rows are not, I don't think having different chunks on different columns is a problem, but there are some constraints probably. The reason for that is that both the DataFrame and the Column objects have num_chunks; if they're both used then I'd say a "dataframe chunk" is the outer container, and within that each column can be chunked. In case the dataframe has num_chunks() == 1 then each column can in principle have an independent/arbitrary number of chunks.
Maybe a question to others - is there a reason to forbid this?

We had a discussion on this in a call 2 weeks ago, and the outcome was:

Internally, it is possible for a dataframe to have different chunk sizes for different columns.

One example given was that it could have performance advantages in some cases when using a string column (this happens in cuDF it looks like).

For interchange, uniform chunks are needed. The question is only if the re-chunking should be done on the producer or the consumer side.
Preference was for this to be on the consumer side.
Text and diagram here already show equal chunking, and at least the Modin implementation adhered to this (enforced on the producer side).
What's needed is a doc clarification stating that the producer must produce equal-size chunks.

I'll open a follow-up PR.


Fix the problem of rewriten null_flag of nullable column

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] others

Which issues of this PR fixes ：

Fixes #3252
Problem Summary(Required) ：

NullableColumn's null flag should not be rewritten

please add UT

run starrocks_clang-format

run starrocks_be_unittest


docs: Improve Features documentation structure

Pull Request description

How to test these changes

...

Pull Request checklists
This PR is a:

[ ] bug-fix
[ ] new feature
[ ] maintenance

About this PR:

[ ] it includes tests.
[ ] the tests are executed on CI.
[ ] the tests generate log file(s) (path).
[ ] pre-commit hooks were executed locally.
[ ] this PR requires a project documentation update.

Author's checklist:

[ ] I have reviewed the changes and it contains no misspelling.
[ ] The code is well commented, especially in the parts that contain more complexity.
[ ] New and old tests passed locally.

Additional information

Reviewer's checklist
Copy and paste this template for your review's note:
## Reviewer's Checklist

- [ ] I managed to reproduce the problem locally from the `main` branch
- [ ] I managed to test the new changes locally
- [ ] I confirm that the issues mentioned were fixed/resolved .

@abhijeetSaroha , in this PR I am just moving some texts and keeping the example a bit shorter


turn on travis

@joaoandremartins as discussed in yesterday's meeting

Thanks Elliotte.
This fixes half of #2.

What's the status of this? Should we merge it in?

No, we need to make it pass first.

I rebased so that there is a src directory in the branch, but now I don't see Travis being invoked at all.

https://travis-ci.org/GoogleCloudPlatform/app-tools-lib-for-java

I think if we merge this then travis will start running.
On Wed, Apr 20, 2016 at 1:17 PM, meltsufin<EMAIL_ADDRESS>wrote:

I rebased so that there is a src directory in the branch, but now I don't
see Travis being invoked at all.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/app-tools-lib-for-java/pull/6#issuecomment-212520386

--
Elliotte Rusty Harold
<EMAIL_ADDRESS>

Yes, I'm not sure why it's not kicking in for this branch. Let's trying merging it in.


chore: bdd-nh-1592933159 to 0.0.1

chore: Promote bdd-nh-1592933159 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


fix: fix eltype for generic logpdf distributions

This PR fixes eltype for generic logpdf distributions.

Codecov Report

Merging #109 (9ac69f3) into master (c44a56f) will increase coverage by 0.52%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #109      +/-   ##
==========================================
+ Coverage   75.19%   75.72%   +0.52%
==========================================
  Files         175      175
  Lines        5901     6038     +137
==========================================
+ Hits         4437     4572     +135
- Misses       1464     1466       +2

Impacted Files
Coverage Δ

src/distributions/function.jl
26.66% <0.00%> (+0.53%)
:arrow_up:

src/actors/score.jl
77.41% <0.00%> (-1.16%)
:arrow_down:

src/distributions/sample_list.jl
91.85% <0.00%> (-0.03%)
:arrow_down:

src/fixes.jl
100.00% <0.00%> (ø)

src/score/node.jl
100.00% <0.00%> (ø)

src/score/variable.jl
100.00% <0.00%> (ø)

src/algebra/permutation_matrix.jl
100.00% <0.00%> (ø)

src/approximations/optimizers/adam.jl
0.00% <0.00%> (ø)

src/nodes/equality.jl
97.53% <0.00%> (+0.06%)
:arrow_up:

src/distributions/normal_mean_variance.jl
97.14% <0.00%> (+0.08%)
:arrow_up:

... and 34 more

Continue to review full report at Codecov.

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


Snake Game chrome extension

Is your feature request related to a problem? Please describe.
This feature request is related to creating a simple snake game, which is a fun and entertaining activity for users.
Describe the solution you'd like
I would like to develop a basic snake game using HTML, CSS, and JavaScript. The game should have a grid-based layout where the snake moves around and eats food to grow longer. The user should control the snake's movement using arrow keys.
Additional context
This simple snake game aims to provide users with a nostalgic gaming experience similar to classic arcade games. It is a lightweight and straightforward project suitable for beginners to learn basic game development concepts.
What problem is this feature trying to solve?
This feature is not solving a specific problem but rather providing entertainment and recreational value to users through a classic and enjoyable game experience.
@Sulagna-Dutta-Roy please assign this to me under GSSOC24
Thank you.

assign to me

Not received any update on this. Closing this

@Sulagna-Dutta-Roy please don't close this ma'am I am in middle of exam I'll sure to upload the extension in 2 days.
Please reassign to me this.
Thank you

Not received any update on this. Closing this

Im busy in my exams and Intern ship preparation


Update dashboard.html.j2

Remove typo from notes in "Your sites" section on dashboard page.

What, you don't like the repetition repetition?

Thanks!


Best practices for formatting csv data for d3.js graph output

I'm looking for some advice on how to properly format my data for d3.js. I'm looking to show growth/reduction on a time line. I'm currently doing a API call to my storage systems which returns the following JSON:
{
  "data": [
    {
      "poolId": 0,
      "poolStatus": "POLN",
      "usedCapacityRate": 4,
      "poolName": "0",
      "availableVolumeCapacity": 67588185,
      "totalPoolCapacity": 82835665,
      "numOfLdevs": 21,
      "firstLdevId": 1451,
      "warningThreshold": 85,
      "depletionThreshold": 90,
      "virtualVolumeCapacityRate": -1,
      "isMainframe": false,
      "isShrinking": false,
      "locatedVolumeCount": 16,
      "totalLocatedCapacity": 47615041,
      "blockingMode": "NB",
      "totalReservedCapacity": 0,
      "reservedVolumeCount": 0,
      "poolType": "DT"
    },
    {
      "poolId": 1,
      "poolStatus": "POLN",
      "usedCapacityRate": 21,
      "poolName": "1",
      "availableVolumeCapacity": 21133817,
      "totalPoolCapacity": 35860177,
      "numOfLdevs": 5,
      "firstLdevId": 1481,
      "warningThreshold": 85,
      "depletionThreshold": 90,
      "virtualVolumeCapacityRate": -1,
      "isMainframe": false,
      "isShrinking": false,
      "locatedVolumeCount": 5,
      "totalLocatedCapacity": 17764771,
      "blockingMode": "NB",
      "totalReservedCapacity": 0,
      "reservedVolumeCount": 0,
      "poolType": "DT"
    }
  ]
}

I'm using the Python module pandas to export certain fields from the JSON output and putting it into a csv file. I have a cron job to do the collection daily and update my csv file for watching the growth/reduction of storage. The csv file formatting is as follows:
poolId,totalPoolCapacity,totalLocatedCapacity,availableVolumeCapacity,usedCapacityRate,storageSystem,date
0,85044361,82112507,35171335,40,system01,20170413
1,41943174,40819098,17263722,47,system01,20170413
0,41653599,50966017,15046668,60,system02,20170413
1,41653599,50335680,12486558,65,system02,20170413
2,26262699,25459800,12303396,56,system02,20170413
0,41653599,40336872,18031398,54,system03,20170413
1,41653599,40335680,15626268,69,system03,20170413
2,82835665,46141040,61256286,23,system03,20170413
3,139811153,54530320,119514990,4,system03,20170413
4,139811153,102768680,79238964,32,system03,20170413
0,82835665,58726152,88703076,4,system04,20170413
1,35860177,18875880,32275992,20,system04,20170413

I have my Python script add the columns "storageSystem" and "date" since it isn't included in the JSON output. Any advice would help immensely.

Please use Stack Overflow tag d3.js to ask for help. Although I make an effort to assist everyone that asks, I am not always available to provide help promptly or directly. Stack Overflow provides a better collaborative forum for self-help: tens of thousands of D3-related questions have already been asked there, and some answered questions may be relevant to you.
When asking for help, please include a link to a live example that demonstrates the issue, preferably on bl.ocks.org. It is often impossible to debug from code snippets alone. Isolate the issue and reduce your code as much as possible before asking for help. The less code you post, the easier it is for someone to debug, and the more likely you are to get a helpful response.
If you have a question about D3’s behavior and want to discuss it with other users, also consider the d3-js Google Group or joining the d3-js Slack.
Thank you! 🤗


Is is possible to get more data?

I have trained with my own network and it is working fine. The car is able to drive almost half the distance but after that it is not able to differentiate between the snow and the road due to the sunlight reflection on the map. Is it possible to get more data to train the network better?

Sure. You can use the python API to record more data from the front facing webcam to augment the training dataset. You'd need to add them to the data_raw folder, and modify the first notebook to pick up the new data.

Got it!! Thanks for the input!!


BUG: spatial.cKDTree: do not slide the median

Never slide the pivot when using median as pivot. Only slide the pivot when pivot is the midpoint. That’s what sliding midpoint means.
Sliding median is not a thing. A median is always the median.
Closes #20605

It seems when splitting on the median, we can get a situation where all points end up in the same branch. This will then trigger an infinite recursion, resulting in a stack overflow.

I also find this strange code in the kd-tree construction:
if (CKDTREE_UNLIKELY(p == start_idx || p == end_idx)) {
            // All children are equal in this dimension, try again with new bounds
            assert(!_compact);
            self->tree_buffer->pop_back();
            std::vector<double> tmp_bounds(2 * m);
            double* tmp_mins = &tmp_bounds[0];
            std::copy_n(mins, m, tmp_mins);
            double* tmp_maxes = &tmp_bounds[m];
            std::copy_n(maxes, m, tmp_maxes);

            const auto fixed_val = data[indices[start_idx]*m + d];
            tmp_mins[d] = fixed_val;
            tmp_maxes[d] = fixed_val;

            return build(self, start_idx, end_idx, tmp_maxes, tmp_mins, _median, _compact);
        }

It tries to solve the issue of empty branches by pretending the spread along a dimension is zero. However, it propagates a false max value into the kd-tree, which can result in bogus query results later on. It came in with d13a48c and is a logic error.

While looking for a regression test case, I seem to have found one that crashes on this PR branch and doesn't crash on main:
--- a/scipy/spatial/tests/test_kdtree.py
+++ b/scipy/spatial/tests/test_kdtree.py
@@ -1531,3 +1531,13 @@ def test_gh_18800(incantation):
     tree = incantation(points, 10)
     tree.query(arr_like, 1)
     tree.query_ball_point(arr_like, 200)
+
+
+def test_gh_20605():
+    # this currently crashes in gh-20606
+    # but not on main
+    data = np.full((100, 2), 4)
+    data[:50, :] = 5
+    data[52:60, 1] = 8
+    balanced_tree = KDTree(data=data,
+                           balanced_tree=True)

I suppose that makes me a little nervous.

Thanks for the test. It revealed two more bugs in the new C++ code.
There are also stability issues with using the median as pivot I have not seen before.
This makes me a bit nervous too.

@sturlamolden is this PR in a state where you think we should consider merging it before I branch for SciPy 1.14.0? It looks like you added my test and CI is green.

Using the median as a pivot has a fail mode when the median is the largest value in a node. When this happen, the larger child node is empty and the lesser is equal to the parent. The the recursion repeats itself ad infinitum and crashes when it runs out of stack. Sliding the pivot prevents this from happening. Logically we must therefore always apply the sliding midpoint rule, also when using the median. We should therefore rather change the documentation to reflect what the kd-tree actually does.

Note that the rationale here is different from the sliding midpoint rule: It exists to prevent slow queries when a node is streched along one dimension. In case of the median we want to avoid infinite recursion when building the kd-tree.

We should therefore rather change the documentation to reflect what the kd-tree actually does.

Hey @sturlamolden, just checking in as we are approaching the 1.15.0 release process - would you like to return to this?

I've closed this PR as it sounds like the code changes here aren't relevant to the desired solution to the linked issue any more - feel free to reopen if that is not the case!


chore: removing unused exports

I ran ts-prune on the repo and cleaned up most of the items which were identified as unused exports. A lot of them are leftover components/utilities from refactored code.
There will be an additional PR coming to remove index files from folders in favor of direct imports from files, and that will result in some additional unused exports being removed.

Codecov Report

Merging #140 (c5095c2) into cleanup (0b296cf) will increase coverage by 3.67%.
The diff coverage is 82.04%.

@@             Coverage Diff             @@
##           cleanup     #140      +/-   ##
===========================================
+ Coverage    73.16%   76.84%   +3.67%
===========================================
  Files          409      391      -18
  Lines         7159     7021     -138
  Branches      1119     1144      +25
===========================================
+ Hits          5238     5395     +157
+ Misses        1921     1626     -295

Impacted Files
Coverage Δ

src/client.tsx
0.00% <0.00%> (ø)

src/common/constants.ts
100.00% <ø> (ø)

src/common/promiseUtils.ts
0.00% <0.00%> (ø)

src/components/Entities/EntityDetails.tsx
44.11% <ø> (ø)

...nDetails/ExecutionNodeDetails/InputNodeDetails.tsx
0.00% <0.00%> (ø)

.../Executions/ExecutionDetails/NodeExecutionData.tsx
0.00% <0.00%> (ø)

...ponents/Executions/ExecutionInputsOutputsModal.tsx
39.13% <ø> (ø)

src/components/Executions/Tables/constants.ts
100.00% <ø> (ø)

src/components/Executions/Tables/utils.ts
100.00% <ø> (+70.58%)
:arrow_up:

...ions/TerminateExecution/TerminateExecutionForm.tsx
56.52% <0.00%> (ø)

... and 165 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #140 (c5095c2) into cleanup (0b296cf) will increase coverage by 3.67%.
The diff coverage is 82.04%.

@@             Coverage Diff             @@
##           cleanup     #140      +/-   ##
===========================================
+ Coverage    73.16%   76.84%   +3.67%
===========================================
  Files          409      391      -18
  Lines         7159     7021     -138
  Branches      1119     1144      +25
===========================================
+ Hits          5238     5395     +157
+ Misses        1921     1626     -295

Impacted Files
Coverage Δ

src/client.tsx
0.00% <0.00%> (ø)

src/common/constants.ts
100.00% <ø> (ø)

src/common/promiseUtils.ts
0.00% <0.00%> (ø)

src/components/Entities/EntityDetails.tsx
44.11% <ø> (ø)

...nDetails/ExecutionNodeDetails/InputNodeDetails.tsx
0.00% <0.00%> (ø)

.../Executions/ExecutionDetails/NodeExecutionData.tsx
0.00% <0.00%> (ø)

...ponents/Executions/ExecutionInputsOutputsModal.tsx
39.13% <ø> (ø)

src/components/Executions/Tables/constants.ts
100.00% <ø> (ø)

src/components/Executions/Tables/utils.ts
100.00% <ø> (+70.58%)
:arrow_up:

...ions/TerminateExecution/TerminateExecutionForm.tsx
56.52% <0.00%> (ø)

... and 165 more

Continue to review full report at Codecov.

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


[To Main] Upgrading the version of met-formio

Issue #: https://apps.itsm.gov.bc.ca/jira/browse/DESENG-596
Description of changes:

Upgrading the version of met-formio to add a default description for the form components.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the met-public license (Apache 2.0).

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

Project coverage is 75.69%. Comparing base (128b4b3) to head (105e395).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2489   +/-   ##
=======================================
  Coverage   75.69%   75.69%
=======================================
  Files         590      590
  Lines       21097    21097
  Branches     1530     1530
=======================================
  Hits        15969    15969
  Misses       4881     4881
  Partials      247      247

Flag
Coverage Δ

metweb
63.46% <ø> (ø)

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


No c lib

Changed some variable names and added some tests.

@vokal/systems @foresmac

LGTM. Can you get it set up so CVR is reporting to github?

LGTM

@foresmac sure, I'll put that on the list.


use EXIT_ON_ZERO_ACTIVE_CONNECTIONS，grpc service receiver NO_ERROR Received Goaway

We set EXIT_ON_ZERO_ACTIVE_CONNECTIONS true. When our service pod is terminating，service will receiver error, log as follow:
c.t.n.i.s.s.i.EventServiceImpl: Unexpected exception
io.grpc.StatusRuntimeException: UNAVAILABLE: HTTP/2 error code: NO_ERROR Received Goaway
Prestop in deployment of our service, we use our stop.sh and will sleep 30s before shutdown out service. sleep 30s is writtend in stop.sh.
The exception is receiver in the 30s of sleep.
We also find that there is no accesslog for error request and in the time before and after,there is success request for our service to request upstream service。
istio version is 1.16.4
k8s version is 1.24

Do you want your pod to stay up for 30s, even when there are no active connections?  If yes, you need to set MINIMUM_DRAIN_DURATION to 30s

@ramaraochavali Thank you for your reply. We encountered the same problem, I have two questions:

MINIMUM_DRAIN_DURATION will be executed first, so why not just set it to 0, and let EXIT_ON_ZERO_ACTIVE_CONNECTIONS to determine when to shutdown? Curious why do you need to set a static 30s before dynamic connection check? #https://github.com/istio/istio/issues/44690#issuecomment-1636339524
Prestop in deployment of our service, we use our stop.sh and will sleep 30s before shutdown out service. sleep 30s is writtend in stop.sh. There are no exceptions in the first five seconds(MINIMUM_DRAIN_DURATION default value is 5s), but intermittent exceptions(UNAVAILABLE: HTTP/2 error code: NO_ERROR Received Goaway) occurred in outgoing grpc calls within five seconds to 30 seconds. I am curious about the reason. Do you have any troubleshooting ideas?

We do not set it to 30s. The current default of MINIMUM_DRAIN_DURATION to 5s is because of historical reasons + some race condition involved (The PR should have have all the discussion). We can not change that now.
It is because Envoy goes in to draining mode after MINIMUM_DRAIN_DURATION and actively sends go aways I think

It is because Envoy goes in to draining mode after MINIMUM_DRAIN_DURATION and actively sends go aways I think

This("actively sends go aways") is detrimental to the service and doesn't sound like graceful downtime is achieved? Under what circumstances will goaway be sent? Because I see that most grpc requests are successful and only a few exceptions.
Does this mean that it is best to enter draining mode after the application container has completed a graceful shutdown?

are you seeing this behaviour for inbound/outbound?

With native sidecar support, can we use that to workaround it

are you seeing this behaviour for inbound/outbound?

outbound

oubound calls should not have any impact for sidecars. We drain inbound listeners only. But I guess, since the active connections becomes, the proxy might have shutdown. If you want proxy to be up till 30s, you should set MIN_DRAIN_DURATION

oubound calls should not have any impact for sidecars. We drain inbound listeners only. But I guess, since the active connections becomes, the proxy might have shutdown. If you want proxy to be up till 30s, you should set MIN_DRAIN_DURATION

From log of istio-proxy，we find the number of active connections is not 0 when an error is reported, which should not trigger proxy shutdown.

Can you share proxy log?

oubound calls should not have any impact for sidecars. We drain inbound listeners only. But I guess, since the active connections becomes, the proxy might have shutdown. If you want proxy to be up till 30s, you should set MIN_DRAIN_DURATION

From log of istio-proxy，we find the number of active connections is not 0 when an error is reported, which should not trigger proxy shutdown.

We set MIN_DRAIN_DURATION=30s, and It doesn't solve the problem. And in the accesslog，we find all request is receiver 200 in accesslog.
Log as follow.
2023-11-07T12:36:15.086402Z	info	Agent draining Proxy
2023-11-07T12:36:15.087454Z	info	Agent draining proxy for 30s, then waiting for active connections to terminate...
[2023-11-07T12:36:15.113Z] "POST /xxxxx HTTP/2" 200 - via_upstream - "-" 47 17 16 16 "-" "grpc-java-netty/1.25.0" "0fcafe45-824d-4166-a256-beb72343ba17" "xxxxx:8850" "<IP_ADDRESS>:8850" outbound|8850||xxxxx.xxxx.svc.cluster.local xxxxxx:41818 xxxx:8850 xxxxx:36076 - -
[2023-11-07T12:36:15.113Z] "POST /xxxxx HTTP/2" 200 - via_upstream - "-" 47 17 14 13 "-" "grpc-java-netty/1.25.0" "b61cfc32-22df-4592-99c5-78b941365424" "xxxx:8850" "xxxx:8850" outbound|8850||xxxx.xxxx.svc.cluster.local xxxx:41818 xxxx:8850 xxxx:36076 - -
……
[2023-11-07T12:36:17.541Z] "POST /xxxx HTTP/2" 200 - via_upstream - "-" 33 15 2 2 "-" "grpc-java-netty/1.25.0" "76ffec4c-06ce-41db-98bd-2919c806df97" "xxxx:8850" "<IP_ADDRESS>:8850" outbound|8850||xxxx.xxxx.svc.cluster.local xxxx:41818 xxxx:8850 xxxx:36928 - -
[2023-11-07T12:36:17.547Z] "POST /xxxx HTTP/2" 200 - via_upstream - "-" 47 242 23 23 "-" "grpc-java-netty/1.25.0" "5f84cf3a-f26f-40fa-8898-549f96be6363" "xxx:8850" "xxxx:8850" outbound|8850||xxx.xxxx.svc.cluster.local <IP_ADDRESS>:43068 xxx:8850 xxx:36940 - -
2023-11-07T12:36:45.088447Z	info	Checking for active connections...
2023-11-07T12:36:46.280820Z	info	There are still 466 active connections
2023-11-07T12:36:47.298137Z	info	There are still 419 active connections
……
2023-11-07T12:37:14.306157Z	info	There are still 440 active connections
And in 12:36:17 our service receiver a error, log as follow:
11-07-2023 12:36:17.547 ERROR [tapo-event-48-1] [TID: 2810340d8f4a4c3a9f9b380c10e6f8cc.3796.16993605401640205] c.t.n.i.s.s.i.EventServiceImpl: Unexpected exception
io.grpc.StatusRuntimeException: UNAVAILABLE: HTTP/2 error code: NO_ERROR Received Goaway
In 12:36:17, accesslog in isito-proxy show the request is receiver 200 but our service throw exception.


Proxy Authentication

Can you please modify redsocks-proxy to Handle Proxy Authentication:
Update the redsocks.conf.template to include PROXY_USER and PROXY_PASSWORD.
Adjust the entrypoint.sh to substitute these variables.

Here you go #8

Change are Released in the latest stable image

I only set it up to tunnel Port 80 and 443, but redsocks is limited to TCP traffic, I think the easiest way would be to run something like https://dnscrypt.info/ on the docker host and set the DNS Server to: dns: <IP_ADDRESS>:53

@CitizenDev played around with DNSCrypt:
https://github.com/mietzen/docker-redsocks-proxy/tree/dnscrypt
It's just an example, you can test it with:
git clone https://github.com/mietzen/docker-redsocks-proxy.git
cd docker-redsocks-proxy
git switch dnscrypt
docker compose up --build

It will tunnel all TCP traffic and catch all UDP DNS requests and redirect them to DNSCrypt / Quad9 DoH via the SOCKS5 Proxy.


167585681 class switcher

[167585681] class switcher
NP/DL -- implementation of the class switcher and, in the process, refactored the problem switcher to use a common "menu-pulldown-botton" react component. Some minimal tests were added and this PR does contain a couple of tests that have been commented out until all issues can be resolved.
In addition, some of the code in auth.ts was refactored and portal related api calls have been isolated in a new file portal-api.ts.

@kswenson -- @DALove1025 have finished our cleanup pass.
When you get a chance, we would like you to have another look. Thanks!


[FEATURE] PHP 7.2 support

@oliverklee Followed contributing guidelines, but I am unable to request a review.
There are a few warnings in 7.2 build - deprecation notice about each() which is caused by old version of PHPUnit and DOM warnings which are present in previous builds, so I let them be.

Thanks for the PR, @finwe! :heart:  Looks generally good!
Could you also please remove the obsolete "Requirements" section from the README (as it's all covered by the composer.json now)?

Merged. Thanks for contributing to Emogrifier, @finwe! :cookie: :heart:

And thanks to you for such a swift response!


Unable to compile sample project with Mac Catalyst

General information

IGListKit version: 4.0
iOS version(s): 14.2
CocoaPods/Carthage version: 1.10.0
Xcode version: 12.2
Devices/Simulators affected: Both
Reproducible in the demo project? (Yes/No): Yes
Related issues: N/A

Hey, I use IGListKit in my app for a few things, but have to comment it out to use it with a Catalyst version, there's a bunch of non-descript compiler complaints. I thought maybe something in my app was interacting with IGListKit weirdly, but if I create a sample project with a Podfile with only IGListKit defined, I still am unable to compile under Catalyst (though it compiles fine for iOS).
The specific issue I get is:

.../Pods/IGListKit/Source/IGListKit/Internal/IGListAdapterUpdater+DebugDescription.h:10:12: Cannot find interface declaration for 'IGListAdapterUpdater'

This seems sort of vague and I'm unsure why it would be unable to find the declaration for this only in Catalyst. Has anyone else run into this issue?

Also getting IGListKit build errors when building for Catalyst.
Same bullets as yours:
IGListKit version: 4.0
iOS version(s): 14.2
CocoaPods/Carthage version: 1.10.0
Xcode version: 12.2

me too


"Romanești" is listed in the drop-down menu

Description:
"Romanești" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Romanești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Romanești, GORJ (TÂRGU JIU)".


Can't send from Mac to a Samsung device after the Quick Share update

This is a known issue. Please don't write about it unless you have anything to add.
Unfortunately, there is currently no solution I can apply on my side because macOS doesn't allow apps to send Bluetooth broadcasts that Android listens for to become visible, and the Google Files workaround no longer works on Samsung devices.
The one remaining, atrocious workaround, is if you have a second Android device, you can open the "send" screen in Quick Share/Nearby Share on it, and then your Samsung device will become visible on the Mac as well.
Now, Google does recognize this limitation of Apple operating systems, and does provide a solution, but, unfortunately, it is currently disabled with a server-side flag. I don't know when or if they will enable it.
On non-Samsung devices, the Google Files workaround, as well as the intent shortcut, still work.

It looks like that the workaround still doesn't work.

Firstly, I thought the marriage of NearbyShare and QuickShare is a good thing, made things less redundant...
Any ideas how to research a new workaround?
On my S24 Ultra, i can confirm that none of the two workarounds to receive files from Mac are working...

i cant use it to send large/big size file. at avg it only can send aroung 5MB or 10MB at top. is there anything to fix this issue?

I just create hardcore shortcut which sets Nearby share to pairing mode. Set up new Requested link and type Nearby Share into search bar and simply create new shortcut. Using this app.
https://play.google.com/store/apps/details?id=rk.android.app.shortcutmaker&hl=en&gl=US&pli=1

I just create hardcore shortcut which sets Nearby share to pairing mode. Set up new Requested link and type Nearby Share into search bar and simply create new shortcut. Using this app. https://play.google.com/store/apps/details?id=rk.android.app.shortcutmaker&hl=en&gl=US&pli=1

I didn't understand what the activity is called, can you give more information?

I just create hardcore shortcut which sets Nearby share to pairing mode. Set up new Requested link and type Nearby Share into search bar and simply create new shortcut. Using this app. https://play.google.com/store/apps/details?id=rk.android.app.shortcutmaker&hl=en&gl=US&pli=1

Yes, could you please provide more details? I found in this application "Requested" section, but there no any items with "near" word. Do you use Samsung Galaxy?

it works fine for me on my galaxy s23 & m1 macbook air. when you share, you have to press the quick share icon, it won't just pop up like other devices do, it's available under the "share to devices nearby" section.

it works fine for me on my galaxy s23 & m1 macbook air. when you share, you have to press the quick share icon, it won't just pop up like other devices do, it's available under the "share to devices nearby" section.

This issue talks about sharing from Mac to Samsung. Sharing from Samsung to Mac works.

it works fine for me on my galaxy s23 & m1 macbook air. when you share, you have to press the quick share icon, it won't just pop up like other devices do, it's available under the "share to devices nearby" section.

This issue talks about sharing from Mac to Samsung. Sharing from Samsung to Mac works.

it works fine for me on my galaxy s23 & m1 macbook air. when you share, you have to press the quick share icon, it won't just pop up like other devices do, it's available under the "share to devices nearby" section.

This issue talks about sharing from Mac to Samsung. Sharing from Samsung to Mac works.

apologies, accidentally commented on the wrong thread

First of all, great job with this app.
I am using the Oneplus 11 and facing this issue when sending files from my Mac to Android. The share intent keeps loading. I also have the update on Android for the quick share.

is there any fix for this issue ?

is there any fix for this issue ?

Have you tried reading what you're commenting on?

As of today, with the latest version of NearDrop, receiving and sending files works for me in both directions.

As of today, with the latest version of NearDrop, receiving and sending files works for me in both directions.

Do you mean it works on your Samsung phone with Quick Share?

I have to correct my last statement: My S24 Ultra is only visible to share to when another regular quickshare device (in my case a windows laptop) is looking for receivers when sending a file via quickshare. When my device appears, the transfer works flawlessly.
The other way works without any hickups, i.e. sending from my S24 Ultra to my Macbook.

Not sure if I missed anything but both my Samsung phone (S23 Ultra) and tablet (Tab S9+) are now able to send AND recieve, even when no other device is there in the list (unlike what @ezBeanie said)

I'm unable to receive on my Google Pixel 6 (Android 14) from my MBP (Sonama 14.5)
The Google Files app no longer has a Nearby Share option. Apparently the new way to get there is via the 'Quick Share' quick setting in the status bar drawer but none of the toggles within (your devices/contacts/everyone) make the phone visible in my mac.
I've tried turning Quick Share off and on again, re-attempting the share after changing the nearby share 'who can share with you' toggle, no dice

Using the workaround does work but obviously not ideal:

install Activity Launcher
search for ReceiveSurfaceActivity and click the ... menu to create a shortcut to it
click that shortcut when you want the phone to be an available option using neardrop on pc

@nezorflame That's not it, look for com.google.android.gms.nearby.sharing.ReceiveSurfaceActivity

@nezorflame That's not it, look for com.google.android.gms.nearby.sharing.ReceiveSurfaceActivity

Yeah, seems that in my case it's missing

Can Confirm that this works like a charm with my Pixel 6 and M1 MacBook Air Edit: Both ways

Not working with Pixel 8 Pro and M1

macbook pro m3 pro, samsung s23 ultra, no dice. using kde connect for clipboard and stuff like that and localsend/macdroid for big files

macbook pro m3 pro, samsung s23 ultra, no dice. using kde connect for clipboard and stuff like that and localsend/macdroid for big files

It looks like the workaround activity does not exist on current GPS on OneUI 4.1

Google is re-adding the "receive" feature in Google Files
https://9to5google.com/2024/10/07/files-by-google-receive-fab/

Google is re-adding the "receive" feature in Google Files
https://9to5google.com/2024/10/07/files-by-google-receive-fab/

In Samsung, the Google Files application in the version specified in the article does not have a receive button.

Possibly A/B testing. This is present on Pixel phones. This might mean the activity that can be opened via shortcuts might have returned?

Yes, in GMS:
com.google.android.gms.nearby.sharing.ReceiveSurfaceActivity

no dice on Samsung S21 Ultra (SM-G998B)

Same here with S22 (SM-S901E)

From: Caio Wilson @.>
Sent: Monday, October 14, 2024 11:19:02 AM
To: grishka/NearDrop @.>
Cc: beatu2it @.>; Manual @.>
Subject: Re: [grishka/NearDrop] Can't send from Mac to a Samsung device after the Quick Share update (Issue #152)
no dice on Samsung S21 Ultra (SM-G998B)
—
Reply to this email directly, view it on GitHubhttps://github.com/grishka/NearDrop/issues/152#issuecomment-2410241498, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BENI27F27FIU3IEOFBTRD3DZ3NV6DAVCNFSM6AAAAABFASDIP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJQGI2DCNBZHA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Please stop saying "me too" and "same here". You're just flooding me with notifications without adding any information.

I discovered a workaround for the issue. Here's what you'll need:
An additional Android device (besides your Samsung device and Mac)
Steps:
1.Share a file from your Mac to your Samsung device. Even if your Mac doesn't immediately find your Samsung (Don't lose hope yet).
2.Share a file from the other Android device (not the Samsung (not sure if samsung will work)) using quick share. Keep the sharing window open where you see mac and your samsung phone.
3.Return to your Mac. Your Samsung device should now be visible and ready to receive files.
4.Select your Samsung device and VOILA Your file will be transferred from your Mac to your Samsung.
Looks like samsung quickshare is some quantum stuff so if some other android is observing it then its visible to mac too.

You are not adding anything new (see @ezBeanie's comment).
Please read the thread before posting, so everyone here who subscribed to the notifications don't get spammed.

Quick sum up

This is about SAMSUNG, not the other devices
This is only in the way Mac -> Samsung. Not the other way
The issue lies in the way the phone makes itself discoverable. This is why there are talks about the Google files / nearby shortcut to trigger this manually. none of these workarounds work on Samsung devices as of today.
as grishka said, please don't comment if you don't add anything new
Please don't comment if this is not about Samsung or the Mac->Samsung way

Now, Google does recognize this limitation of Apple operating systems, and does provide a solution, but, unfortunately, it is currently disabled with a server-side flag. I don't know when or if they will enable it.

Any news on this one? The last message in that issue was on August

It seems that Google is working on a native implementation for MacOS: https://9to5google.com/2024/11/01/google-quick-share-macos-ios-hint/

Could someone please make it clear on the read me if this is universal for Samsung.
I am not sure if:
a) if your samsung cannot be seen then it is experiencing this known issue, or if
b) all samsungs do not support mac -> android transfer.

No Samsungs can be seen. HOWEVER, if you have a non-Samsung Android device, then it can be seen and the transfer can be completed.

I'm unable to receive on my Google Pixel 6 (Android 14) from my MBP (Sonama 14.5)
The Google Files app no longer has a Nearby Share option. Apparently the new way to get there is via the 'Quick Share' quick setting in the status bar drawer but none of the toggles within (your devices/contacts/everyone) make the phone visible in my mac.
I've tried turning Quick Share off and on again, re-attempting the share after changing the nearby share 'who can share with you' toggle, no dice
Using the workaround does work but obviously not ideal:
1. install [Activity Launcher](https://play.google.com/store/apps/details?id=de.szalkowski.activitylauncher)

2. search for `ReceiveSurfaceActivity` and click the ... menu to create a shortcut to it

3. click that shortcut when you want the phone to be an available option using neardrop on pc

I tried to start the service as a user or as root and in both cases it gave me the same error
Samsung A54
Android 13
UI 5.1

Congrats @grishka for this piece of app, thanks

OMG READ THE WHOLE THREAD!

I'm unable to receive on my Google Pixel 6 (Android 14) from my MBP (Sonama 14.5)
The Google Files app no longer has a Nearby Share option. Apparently the new way to get there is via the 'Quick Share' quick setting in the status bar drawer but none of the toggles within (your devices/contacts/everyone) make the phone visible in my mac.
I've tried turning Quick Share off and on again, re-attempting the share after changing the nearby share 'who can share with you' toggle, no dice
Using the workaround does work but obviously not ideal:
1. install [Activity Launcher](https://play.google.com/store/apps/details?id=de.szalkowski.activitylauncher)

2. search for `ReceiveSurfaceActivity` and click the ... menu to create a shortcut to it

3. click that shortcut when you want the phone to be an available option using neardrop on pc

I tried to start the service as a user or as root and in both cases it gave me the same error
Samsung A54
Android 13
UI 5.1

Congrats @grishka for this piece of app, thanks

It literally isn't a method for Samsung. There's no workaround for Samsung yet 🤦♂

I discovered a workaround for the issue. Here's what you'll need:
An additional Android device (besides your Samsung device and Mac) Steps:
1.Share a file from your Mac to your Samsung device. Even if your Mac doesn't immediately find your Samsung (Don't lose hope yet). 2.Share a file from the other Android device (not the Samsung (not sure if samsung will work)) using quick share. Keep the sharing window open where you see mac and your samsung phone. 3.Return to your Mac. Your Samsung device should now be visible and ready to receive files. 4.Select your Samsung device and VOILA Your file will be transferred from your Mac to your Samsung.
Looks like samsung quickshare is some quantum stuff so if some other android is observing it then its visible to mac too.

Thanks a lot for this workaround, @Delocalized-electron! I followed the steps and used Samsung in step 2, and it worked perfectly. Really awesome!


Add Flameshot

Powerful Screenshot App
https://github.com/flameshot-org/flameshot
They have a deb available from their website.
https://github.com/flameshot-org/flameshot/releases/tag/v0.10.2

a nice trick: on github you can always get to the latest tag  by replace: /tag/vx.y with /latest
for example the latest release of flameshot is at https://github.com/flameshot-org/flameshot/releases/latest

Taking a look


chore(.github): Fix coverage run to separate unit test and coverage upload to codecov

Separate unit test coverage run to two separate steps: unit test and then make cover so that coverage report actually gets pushed.

Codecov Report

Merging #2249 (bc00586) into main (cd8d0b9) will decrease coverage by 5.47%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2249      +/-   ##
==========================================
- Coverage   55.87%   50.40%   -5.47%
==========================================
  Files         216      150      -66
  Lines       14218     9299    -4919
==========================================
- Hits         7944     4687    -3257
+ Misses       5484     4215    -1269
+ Partials      790      397     -393

Impacted Files
Coverage Δ

nodebuilder/share/config.go
0.00% <ø> (-51.62%)
:arrow_down:

nodebuilder/share/constructors.go
13.63% <ø> (-79.55%)
:arrow_down:

nodebuilder/share/module.go
0.00% <ø> (-89.52%)
:arrow_down:

nodebuilder/share/opts.go
0.00% <ø> (-66.67%)
:arrow_down:

share/availability/full/availability.go
45.94% <ø> (-37.84%)
:arrow_down:

share/availability/full/testing.go
100.00% <ø> (ø)

share/p2p/discovery/backoff.go
79.24% <ø> (ø)

share/p2p/discovery/discovery.go
66.39% <ø> (ø)

share/p2p/discovery/metrics.go
10.08% <ø> (ø)

share/p2p/discovery/options.go
60.86% <ø> (ø)

... and 2 more

... and 137 files with indirect coverage changes


chore(dependency) upgrade to bootstrap 4.0.0

This PR is intended to fulfill the request to upgrade the typescript-webpack-skeleton to Bootstrap 4.0.0 in issue #870.
As you can see, I had to change a bit of the markup to be aligned with new Bootstrap 4 components boilerplate.
This is the first step, I plan to upgrade the other skeletons after this PR is approved and merged. Let's say this one serve as a base for the other as the src folder is most-likely identical in all skeleton.
I'm open to comments, don't hesitate if you have any question!

@AshleyGrant Can you review?

@JoshuaVSherman Hey there. I don't think we need those imports. Those are already included in the bootstrap.css files WebPack picks up to bundle. I never had to add them individually doing this. That's possible I've been wrong all that time, but never had any issues, missing features doing it this way.
The bootstrap-grid.css file is there for people who only want to get the grid layout, without all the remaining fuzz of bootstrap, at least, that's what I always understood.

ok thanks
On Mon, Feb 26, 2018 at 8:55 AM, Marc-Andre Roy<EMAIL_ADDRESS>wrote:

@JoshuaVSherman https://github.com/joshuavsherman Hey there. I don't
think we need those imports. Those are already included in the
bootstrap.css files WebPack picks up to bundle. I never had to add them
individually doing this. That's possible I've been wrong all that time, but
never had any issues, missing features doing it this way.
The bootstrap-grid.css file is there for people who only want to get the
grid layout, without all the remaining fuzz of bootstrap, at least, that's
what I always understood.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aurelia/skeleton-navigation/pull/874#issuecomment-368510939,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMuN2FVh9N4LEzPWYz0uom3ZE9mAY_Uhks5tYrfhgaJpZM4SGTa-
.

--
Josh Sherman
https://web-jam.com
https://www.linkedin.com/in/joshuavsherman/
540-494-8035

Update to Bootstrap 4.1.0 done. I had to update some libraries because I'm on NodeJS 9.x branch and it cause me some issue. Anyway, minor updates, doesn't break anything.

@maroy1986 I've added a comment on the usage of the containerless attribute. I'd like to get rid of that if at all possible. Other than that I'm okay with the changes and I'll approve once the containerless attribute usage goes away, if at all possible.

@AshleyGrant Thanks for reviewing! About that @containerless thing, I've spent a lot of time either on my personal time as well as at work, trying to figure it out and never found any solution. The problem is, the fact we create a component for the header and declare the header inside it, seems to interfere with bootstrap javascript for the responsive menu. Removing the container of the component make it works. That's really strange and trust me, I spent a lot of time trying to get rid of that @containerless but never figure it out. But it's been a while, I will try to spend some time again on it, in case of I missed something back then that will jump in my face now.

I'll give it a quick look

@AshleyGrant Yes, just tested it on my side too and it's now working properly. That should be something that was "broken" in 4.0.0 but got fixed in 4.1.0. I'll commit this in the next minutes. Thanks!

@maroy1986 any chance you would be willing to do the same update for skeleton-esnext-webpack?

@AshleyGrant Sure! That was in my plans, I was just waiting for this one to be merged and then move to it.

If you've got nothing more going on I wouldn't stop you from updating the JSPM skeletons as well.

@AshleyGrant My goal was to do them all once I got one approved. Should be fairly trivial now that I get the markup figured it out. Ping me on Gitter if anything you wanna chat about it ;)


Maximum Size of the payload in the datachannel?

What is the maximum size of the payload which cant be sent over the datachannel. Is there an option to increase of decrease this limit?

Hi, thank you for your question. The SDK does not enforce any limits on the payload size for data channels as such because the specs don't mention anything about it. This limit is dictated by the browsers mainly. usrsctp is used by Chromium and its default limit is 256KB. Ideally, 16KB is a good data size. but this article will be useful in determining the limits.
Closing assuming answered. Feel free to reopen in case you have any other questions