[InAppMessaging] Not receiving test message on one device (while another device working)

Step 0: Are you in the right place?

For issues or feature requests related to the code in this repository
file a Github issue.

If this is a feature request please use the Feature Request template.

For general technical questions, post a question on StackOverflow
with the firebase tag.
For general (non-iOS) Firebase discussion, use the firebase-talk
google group.
For backend issues, console issues, and other non-SDK help that does not fall under one
of the above categories, reach out to
Firebase Support.
Once you've read this section and determined that your issue is appropriate for
this repository, please delete this section.

[REQUIRED] Step 1: Describe your environment

Xcode version: 14.0.1 (12A7300)
Firebase SDK version: 6.24.0
Firebase Component: Core, Analytics, Crashlytics, InAppMessaging
Component version:

  - Firebase (6.24.0):
    - Firebase/Core (= 6.24.0)
  - Firebase/Analytics (6.24.0):
    - Firebase/Core
  - Firebase/Core (6.24.0):
    - Firebase/CoreOnly
    - FirebaseAnalytics (= 6.5.0)
  - Firebase/CoreOnly (6.24.0):
    - FirebaseCore (= 6.7.0)
  - Firebase/Crashlytics (6.24.0):
    - Firebase/CoreOnly
    - FirebaseCrashlytics (~> 4.1.0)
  - Firebase/InAppMessaging (6.24.0):
    - Firebase/CoreOnly
    - FirebaseInAppMessaging (~> 0.20.0)

Installation method: CocoaPods

[REQUIRED] Step 2: Describe the problem
Steps to reproduce:

I have two iOS physical devices, one is iPhone 8 Plus and another one is iPhone 11.
I was able to get the two installation IDs of the two devices, and iPhone 8 Plus could receive the test messages from Firebase In-app Message Web Console.
However, when I tested on another device (iPhone 11), it couldn't receive any test messages with exact the same settings and code.

Logs on the non-working device:
2020-10-19 21:59:22.496580+0200 [APP_NAME][10533:8512235] 6.24.0 - [Firebase/Core][I-COR000001] Configuring the default app.
2020-10-19 21:59:22.532262+0200 [APP_NAME][10533:8512233] 6.24.0 - [Firebase/Installations][I-FIS002001] -[FIRInstallationsIDController installationWithValidAuthTokenForcingRefresh:0], appName: __FIRAPP_DEFAULT
2020-10-19 21:59:22.532328+0200 [APP_NAME][10533:8512233] 6.24.0 - [Firebase/Installations][I-FIS002000] -[FIRInstallationsIDController createGetInstallationItemPromise], appName: __FIRAPP_DEFAULT
2020-10-19 21:59:22.532743+0200 [APP_NAME][10533:8512202] [Firebase/Crashlytics] Version 4.1.1
2020-10-19 21:59:22.533091+0200 [APP_NAME][10533:8512240] 6.24.0 - [Firebase/Crashlytics][I-CLS000000] [Crashlytics] Running on iPhone12,1, 14.0.1 (18A393)
2020-10-19 21:59:22.533996+0200 [APP_NAME][10533:8512234] 6.24.0 - [Firebase/Analytics][I-ACS024000] Debug mode is on
2020-10-19 21:59:22.534069+0200 [APP_NAME][10533:8512234] 6.24.0 - [Firebase/Analytics][I-ACS025028] AdMob and Firebase are in use in this app, but are not linked. For analytics data consistency and integrity, it is highly recommended that you link your AdMob app to the corresponding Firebase app and re-download the GoogleServices-Info.plist file. See https://support.google.com/admob/answer/6383165 for more information.
2020-10-19 21:59:22.545107+0200 [APP_NAME][10533:8512233] 6.24.0 - [Firebase/Crashlytics][I-CLS000000] [Crashlytics:Crash:Reports:Event] Registered Firebase Analytics event listener
2020-10-19 21:59:22.545208+0200 [APP_NAME][10533:8512233] 6.24.0 - [Firebase/Crashlytics][I-CLS000000] Automatic data collection is enabled.
2020-10-19 21:59:22.545349+0200 [APP_NAME][10533:8512233] 6.24.0 - [Firebase/Crashlytics][I-CLS000000] Unsent reports will be uploaded at startup
2020-10-19 21:59:22.547340+0200 [APP_NAME][10533:8512240] 6.24.0 - [Firebase/InAppMessagingDisplay][I-FID100010] Got notification for kFIRAppReadyToConfigureSDKNotification. Setting display component on headless SDK.
2020-10-19 21:59:22.547615+0200 [APP_NAME][10533:8512240] 6.24.0 - [Firebase/InAppMessaging][I-IAM290001] Setting a non-nil message display component
2020-10-19 21:59:22.547667+0200 [APP_NAME][10533:8512240] 6.24.0 - [Firebase/InAppMessaging][I-IAM170001] Got notification for kFIRAppReadyToConfigureSDKNotification
2020-10-19 21:59:22.547723+0200 [APP_NAME][10533:8512240] 6.24.0 - [Firebase/InAppMessaging][I-IAM170002] Auto bootstrap Firebase in-app messaging SDK
2020-10-19 21:59:22.547842+0200 [APP_NAME][10533:8512240] 6.24.0 - [Firebase/InAppMessaging][I-IAM170005] Not running in simulator. Use regular clearcut uploading strategy.
2020-10-19 21:59:22.548620+0200 [APP_NAME][10533:8512240] 6.24.0 - [Firebase/InAppMessaging][I-IAM310001] Persistent file path for activity log data is /var/mobile/Containers/Data/Application/5234DEA7-0818-476E-820F-19922794F67E/Library/Caches/firebase-iam-activity-log-cache
2020-10-19 21:59:22.549138+0200 [APP_NAME][10533:8512240] 6.24.0 - [Firebase/InAppMessaging][I-IAM230001] Persistent file path for clearcut log records is /var/mobile/Containers/Data/Application/5234DEA7-0818-476E-820F-19922794F67E/Library/Caches/firebase-iam-clearcut-retry-records
2020-10-19 21:59:22.550941+0200 [APP_NAME][10533:8512240] 6.24.0 - [Firebase/InAppMessaging][I-IAM230002] Loaded 0 clearcut log records from file in 0.000178 seconds
2020-10-19 21:59:22.551827+0200 [APP_NAME][10533:8512240] 6.24.0 - [Firebase/InAppMessaging][I-IAM230005] Returning 0 clearcut retry records from popStillValidRecords
2020-10-19 21:59:22.552331+0200 [APP_NAME][10533:8512240] 6.24.0 - [Firebase/InAppMessaging][I-IAM260001] FIRIAMClearcutUploader created with strategy as min wait time in seconds:300;max wait time in seconds:43200;failure backoff time in seconds:3600;batch send size:50
2020-10-19 21:59:22.552851+0200 [APP_NAME][10533:8512240] 6.24.0 - [Firebase/InAppMessaging][I-IAM290001] SDK is in mode of Regular and has seen 4 fetches.
2020-10-19 21:59:22.557684+0200 [APP_NAME][10533:8512240] 6.24.0 - [Firebase/InAppMessaging][I-IAM300010] Detected 0 custom URL schemes from environment
2020-10-19 21:59:22.564503+0200 [APP_NAME][10533:8512235] 6.24.0 - [Firebase/Analytics][I-ACS031025] Analytics screen reporting is enabled. Call +[FIRAnalytics setScreenName:setScreenClass:] to set the screen name or override the default screen class name. To disable screen reporting, set the flag FirebaseScreenReportingEnabled to NO (boolean) in the Info.plist
2020-10-19 21:59:22.607049+0200 [APP_NAME][10533:8512240] 6.24.0 - [GULReachability][I-REA902003] Monitoring the network status
2020-10-19 21:59:22.608370+0200 [APP_NAME][10533:8512242] 6.24.0 - [Firebase/Analytics][I-ACS023007] Analytics v.60500000 started
2020-10-19 21:59:22.608962+0200 [APP_NAME][10533:8512242] 6.24.0 - [Firebase/Analytics][I-ACS023008] To disable debug logging set the following application argument: -noFIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)
2020-10-19 21:59:22.609273+0200 [APP_NAME][10533:8512242] 6.24.0 - [Firebase/Analytics][I-ACS023009] Debug logging enabled
2020-10-19 21:59:22.609329+0200 [APP_NAME][10533:8512242] 6.24.0 - [Firebase/Analytics][I-ACS023207] To enable verbose logging set the following application argument: -FIRAnalyticsVerboseLoggingEnabled (see http://goo.gl/RfcP7r)
2020-10-19 21:59:22.639384+0200 [APP_NAME][10533:8512235] 6.24.0 - [GULReachability][I-REA902003] Monitoring the network status
2020-10-19 21:59:22.642891+0200 [APP_NAME][10533:8512202] <Google> To get test ads on this device, set: GADMobileAds.sharedInstance.requestConfiguration.testDeviceIdentifiers = @[ @"b492485b3b9a90aa60cdfe60352af332" ];
2020-10-19 21:59:22.643476+0200 [APP_NAME][10533:8512202] <Google> Note that test device identifiers may be reset when uninstalling and reinstalling the application.
2020-10-19 21:59:22.728093+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM260010] App foregrounded, FIRIAMClearcutUploader will seed next send
2020-10-19 21:59:22.728275+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM260006] Next upload attempt scheduled in 0 seconds
2020-10-19 21:59:22.728424+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM230005] Returning 0 clearcut retry records from popStillValidRecords
2020-10-19 21:59:22.728661+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM260007] No clearcut records to be uploaded
2020-10-19 21:59:22.728805+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM260010] App foregrounded, FIRIAMClearcutUploader will seed next send
2020-10-19 21:59:22.728873+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM260006] Next upload attempt scheduled in 0 seconds
2020-10-19 21:59:22.729085+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM230005] Returning 0 clearcut retry records from popStillValidRecords
2020-10-19 21:59:22.729139+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM260007] No clearcut records to be uploaded
2020-10-19 21:59:22.729179+0200 [APP_NAME][10533:8512246] 6.24.0 - [GULReachability][I-REA902004] Network status has changed. Code:1, status:Disconnected
2020-10-19 21:59:22.729340+0200 [APP_NAME][10533:8512246] 6.24.0 - [GULReachability][I-REA902004] Network status has changed. Code:2, status:Connected
2020-10-19 21:59:22.729386+0200 [APP_NAME][10533:8512246] 6.24.0 - [GoogleUtilities/AppDelegateSwizzler][I-SWZ001008] Successfully created App Delegate Proxy automatically. To disable the proxy, set the flag GoogleUtilitiesAppDelegateProxyEnabled to NO (Boolean) in the Info.plist
2020-10-19 21:59:22.729540+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM180002] Firebase In-App Messaging SDK version 0.20.2 finished startup in 0.116005 seconds with these settings: APIServer:firebaseinappmessaging.googleapis.com;ProjectNumber:811824953249; API_Key:AIzaSyBJxbY2AtUMt98gRq2GcdhPB0GVbkXz1ek;Clearcut Server:play.googleapis.com; Fetch Minimal Interval:86400 seconds; Activity Logger Max:100; Foreground Display Trigger Minimal Interval:86400 seconds;
Clearcut strategy:min wait time in seconds:300;max wait time in seconds:43200;failure backoff time in seconds:3600;batch send size:50;Global Firebase auto data collection enabled
2020-10-19 21:59:22.729574+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM150004] Persistent file path for fetch response data is /var/mobile/Containers/Data/Application/5234DEA7-0818-476E-820F-19922794F67E/Library/Caches/firebase-iam-messages-cache
2020-10-19 21:59:22.729611+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM150004] Persistent file path for fetch response data is /var/mobile/Containers/Data/Application/5234DEA7-0818-476E-820F-19922794F67E/Library/Caches/firebase-iam-messages-cache
2020-10-19 21:59:22.729652+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM150001] Loaded response from fetch storage successfully.
2020-10-19 21:59:22.729769+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM900014] No fetch epoch time detected in API response.
2020-10-19 21:59:22.729817+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM900002] 0 message definitions were parsed out successfully and 0 messages are discarded
2020-10-19 21:59:22.729952+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM160011] No analytics event trigger based messages, disable listening
2020-10-19 21:59:22.730006+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM140003] Stop observing Firebase Analytics events for display check.
2020-10-19 21:59:22.730100+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM160001] There are 0 test messages and 0 regular messages and 0 Firebase Analytics events to watch after resetting the message cache
2020-10-19 21:59:22.730399+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM180001] Message loading from fetch storage was done.
2020-10-19 21:59:22.731293+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM180014] No auto data collection enable setting entry detected.So no FIAM programmatic setting from the app.
2020-10-19 21:59:22.731365+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM180018] No programmatic or plist setting at FIAM level. Fallback to global Firebase level setting.
2020-10-19 21:59:22.731405+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM180008] Start SDK runtime components.
2020-10-19 21:59:22.731585+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM600002] Start observing app foreground notifications for message fetching.
2020-10-19 21:59:22.731748+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM140002] Start observing Firebase Analytics events for rendering messages.
2020-10-19 21:59:22.731859+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM180020] Start regular display flow for non-testing instance mode
2020-10-19 21:59:22.732348+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM500002] Start observing app foreground notifications for rendering messages.
2020-10-19 21:59:22.732615+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM400005] Interval time from last display is<PHONE_NUMBER>.663377 seconds
2020-10-19 21:59:22.732666+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM400001] No appropriate in-app message detected for display.
2020-10-19 21:59:22.732907+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM700005] Interval from last time fetch is 696.019727 seconds
2020-10-19 21:59:22.732959+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM700008] Interval from last time fetch is 696.019727 seconds, smaller than fetch wait time 86400.000000
2020-10-19 21:59:22.733060+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/InAppMessaging][I-IAM700003] Only 696.019727 seconds from last fetch time. No action.
2020-10-19 21:59:22.733102+0200 [APP_NAME][10533:8512246] 6.24.0 - [Firebase/Analytics][I-ACS025026] Deferring to Firebase for event data collection
2020-10-19 21:59:22.918658+0200 [APP_NAME][10533:8512202] WF: === Starting WebFilter logging for process [APP_NAME]
2020-10-19 21:59:22.918694+0200 [APP_NAME][10533:8512202] WF: _userSettingsForUser mobile: {
    filterBlacklist =     (
    );
    filterWhitelist =     (
    );
    restrictWeb = 1;
    useContentFilter = 0;
    useContentFilterOverrides = 0;
    whitelistEnabled = 0;
}
2020-10-19 21:59:22.918724+0200 [APP_NAME][10533:8512202] WF: _WebFilterIsActive returning: NO
2020-10-19 21:59:22.978317+0200 [APP_NAME][10533:8512253] 6.24.0 - [Firebase/Analytics][I-ACS800023] No pending snapshot to activate. SDK name: app_measurement
2020-10-19 21:59:23.013472+0200 [APP_NAME][10533:8512233] 6.24.0 - [Firebase/Analytics][I-ACS002002] APMExperimentAlarm scheduled to fire in approx. (s): 13179.73830699921
2020-10-19 21:59:23.030794+0200 [APP_NAME][10533:8512251] 6.24.0 - [Firebase/InAppMessaging][I-IAM190007] Successfully generated FIS token
2020-10-19 21:59:23.030883+0200 [APP_NAME][10533:8512251] 6.24.0 - [Firebase/Installations][I-FIS002000] -[FIRInstallationsIDController createGetInstallationItemPromise], appName: __FIRAPP_DEFAULT
2020-10-19 21:59:23.031257+0200 [APP_NAME][10533:8512251] 6.24.0 - [Firebase/Installations][I-FIS002001] -[FIRInstallationsIDController installationWithValidAuthTokenForcingRefresh:0], appName: __FIRAPP_DEFAULT
2020-10-19 21:59:23.031399+0200 [APP_NAME][10533:8512251] 6.24.0 - [Firebase/InAppMessaging][I-IAM190009] Successfully in fetching both FID as eOh5cJBkvEDUru1XQeXkci and FIS token as eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJmaWQiOiJlT2g1Y0pCa3ZFRFVydTFYUWVYa2NpIiwicHJvamVjdE51bWJlciI6ODExODI0OTUzMjQ5LCJleHAiOjE2MDM3NDExMzMsImFwcElkIjoiMTo4MTE4MjQ5NTMyNDk6aW9zOjA5ODAwMmRlOThiZjZlYTY0ZmJkZTAifQ.AB2LPV8wRQIgB-8bC9_Hezn0ZqKm1Yqlrdi9s_MkeZT34tlc_KM21BYCIQC3U9Awkl2w_bil7vGQNn0tWQnBLhnXBUnPKz-hlsL3tg
2020-10-19 21:59:23.032148+0200 [APP_NAME][10533:8512251] 6.24.0 - [Firebase/InAppMessaging][I-IAM180017] Starting InAppMessaging runtime with Firebase Installation ID eOh5cJBkvEDUru1XQeXkci
2020-10-19 21:59:23.032527+0200 [APP_NAME][10533:8512251] 6.24.0 - [Firebase/Analytics][I-ACS031010] Tracking view controller. Class, ID: ViewController,<PHONE_NUMBER>745714558
2020-10-19 21:59:23.145877+0200 [APP_NAME][10533:8512240] 6.24.0 - [Firebase/Analytics][I-ACS800023] No pending snapshot to activate. SDK name: app_measurement
2020-10-19 21:59:23.146350+0200 [APP_NAME][10533:8512240] 6.24.0 - [Firebase/Analytics][I-ACS029017] Configuration was not found in database. The configuration will be fetched from the network when necessary
2020-10-19 21:59:23.233327+0200 [APP_NAME][10533:8512240] 6.24.0 - [Firebase/Analytics][I-ACS023016] Analytics is ready to receive events
2020-10-19 21:59:23.458952+0200 [APP_NAME][10533:8512243] 6.24.0 - [Firebase/Analytics][I-ACS032003] iAd framework is not linked. Search Ad Attribution Reporter is disabled.
2020-10-19 21:59:23.460519+0200 [APP_NAME][10533:8512243] 6.24.0 - [Firebase/Analytics][I-ACS002002] Engagement timer scheduled to fire in approx. (s): 3600
2020-10-19 21:59:23.460560+0200 [APP_NAME][10533:8512243] 6.24.0 - [Firebase/Analytics][I-ACS023012] Analytics collection enabled
2020-10-19 21:59:23.462177+0200 [APP_NAME][10533:8512243] 6.24.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: auto, screen_view (_vs), {
    ga_event_origin (_o) = auto;
    ga_screen_class (_sc) = ViewController;
    ga_screen_id (_si) =<PHONE_NUMBER>745714558;
}
2020-10-19 21:59:23.462754+0200 [APP_NAME][10533:8512239] 6.24.0 - [Firebase/Analytics][I-ACS023073] Debug mode is enabled. Marking event as debug and real-time. Event name, parameters: screen_view (_vs), {
    ga_debug (_dbg) = 1;
    ga_event_origin (_o) = auto;
    ga_realtime (_r) = 1;
    ga_screen_class (_sc) = ViewController;
    ga_screen_id (_si) =<PHONE_NUMBER>745714558;
}
2020-10-19 21:59:23.716809+0200 [APP_NAME][10533:8512253] 6.24.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: screen_view (_vs), {
    ga_debug (_dbg) = 1;
    ga_event_origin (_o) = auto;
    ga_realtime (_r) = 1;
    ga_screen_class (_sc) = ViewController;
    ga_screen_id (_si) =<PHONE_NUMBER>745714558;
}
2020-10-19 21:59:23.747914+0200 [APP_NAME][10533:8512202] WF: _userSettingsForUser mobile: {
    filterBlacklist =     (
    );
    filterWhitelist =     (
    );
    restrictWeb = 1;
    useContentFilter = 0;
    useContentFilterOverrides = 0;
    whitelistEnabled = 0;
}
2020-10-19 21:59:23.747954+0200 [APP_NAME][10533:8512202] WF: _WebFilterIsActive returning: NO
2020-10-19 21:59:23.875003+0200 [APP_NAME][10533:8512253] 6.24.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 0.1528949737548828
2020-10-19 21:59:23.875697+0200 [APP_NAME][10533:8512253] 6.24.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: am, ad_query (_aq), {
    ad_event_id (_aeid) = -4179783338795622666;
    ga_event_origin (_o) = am;
    ga_screen_class (_sc) = ViewController;
    ga_screen_id (_si) =<PHONE_NUMBER>745714558;
}
2020-10-19 21:59:23.876436+0200 [APP_NAME][10533:8512253] 6.24.0 - [Firebase/Analytics][I-ACS023073] Debug mode is enabled. Marking event as debug and real-time. Event name, parameters: ad_query (_aq), {
    ad_event_id (_aeid) = -4179783338795622666;
    ga_debug (_dbg) = 1;
    ga_event_origin (_o) = am;
    ga_realtime (_r) = 1;
    ga_screen_class (_sc) = ViewController;
    ga_screen_id (_si) =<PHONE_NUMBER>745714558;
}
2020-10-19 21:59:24.049429+0200 [APP_NAME][10533:8512241] 6.24.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: ad_query (_aq), {
    ad_event_id (_aeid) = -4179783338795622666;
    ga_debug (_dbg) = 1;
    ga_event_origin (_o) = am;
    ga_realtime (_r) = 1;
    ga_screen_class (_sc) = ViewController;
    ga_screen_id (_si) =<PHONE_NUMBER>745714558;
}
2020-10-19 21:59:24.227050+0200 [APP_NAME][10533:8512245] 6.24.0 - [Firebase/Analytics][I-ACS002001] Measurement timer fired
2020-10-19 21:59:24.227102+0200 [APP_NAME][10533:8512245] 6.24.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-10-19 21:59:24.281242+0200 [APP_NAME][10533:8512241] 6.24.0 - [Firebase/Analytics][I-ACS023105] Event is not subject to real-time event count daily limit. Marking an event as real-time. Event name, parameters: screen_view (_vs), {
    ga_debug (_dbg) = 1;
    ga_event_origin (_o) = auto;
    ga_realtime (_r) = 1;
    ga_screen_class (_sc) = ViewController;
    ga_screen_id (_si) =<PHONE_NUMBER>745714558;
}
2020-10-19 21:59:24.285269+0200 [APP_NAME][10533:8512241] 6.24.0 - [Firebase/Analytics][I-ACS023105] Event is not subject to real-time event count daily limit. Marking an event as real-time. Event name, parameters: ad_query (_aq), {
    ad_event_id (_aeid) = -4179783338795622666;
    ga_debug (_dbg) = 1;
    ga_event_origin (_o) = am;
    ga_realtime (_r) = 1;
    ga_screen_class (_sc) = ViewController;
    ga_screen_id (_si) =<PHONE_NUMBER>745714558;
}
2020-10-19 21:59:24.286700+0200 [APP_NAME][10533:8512245] 6.24.0 - [Firebase/Analytics][I-ACS012018] Saving bundle. size (bytes): 488
2020-10-19 21:59:24.286771+0200 [APP_NAME][10533:8512245] 6.24.0 - [Firebase/Analytics][I-ACS023116] Bundle added to the upload queue. BundleID, timestamp (ms): 20,<PHONE_NUMBER>813
2020-10-19 21:59:24.475615+0200 [APP_NAME][10533:8512241] 6.24.0 - [Firebase/Analytics][I-ACS023039] Measurement data sent to network. Timestamp (ms), data:<PHONE_NUMBER>475, <APMPBMeasurementBatch: 0x281a2c7a0>
2020-10-19 21:59:24.478481+0200 [APP_NAME][10533:8512245] 6.24.0 - [Firebase/Analytics][I-ACS900000] Uploading data. Host: https://app-measurement.com/a
2020-10-19 21:59:24.530551+0200 [APP_NAME][10533:8512241] 6.24.0 - [Firebase/Analytics][I-ACS901006] Received SSL challenge for host. Host: https://app-measurement.com/a
2020-10-19 21:59:24.569468+0200 [APP_NAME][10533:8512245] 6.24.0 - [Firebase/Analytics][I-ACS023044] Successful upload. Got network response. Code, size: 204, -1
2020-10-19 21:59:24.574864+0200 [APP_NAME][10533:8512241] 6.24.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 0.2385399341583252
2020-10-19 21:59:24.768782+0200 [APP_NAME][10533:8512253] 6.24.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-10-19 21:59:41.654310+0200 [APP_NAME][10533:8512239] 6.24.0 - [Firebase/InAppMessaging][I-IAM310004] App will become inactive, save activity logs
2020-10-19 21:59:41.654355+0200 [APP_NAME][10533:8512239] 6.24.0 - [Firebase/InAppMessaging][I-IAM310004] App will become inactive, save activity logs
2020-10-19 21:59:41.661617+0200 [APP_NAME][10533:8512239] 6.24.0 - [Firebase/InAppMessaging][I-IAM230003] Saving 0 clearcut log records into file is successful
2020-10-19 21:59:41.661818+0200 [APP_NAME][10533:8512239] 6.24.0 - [Firebase/InAppMessaging][I-IAM230003] Saving 0 clearcut log records into file is successful
2020-10-19 21:59:41.662053+0200 [APP_NAME][10533:8512239] 6.24.0 - [Firebase/Analytics][I-ACS002003] Engagement timer canceled
2020-10-19 21:59:41.662303+0200 [APP_NAME][10533:8512239] 6.24.0 - [Firebase/Analytics][I-ACS002002] Engagement timer scheduled to fire in approx. (s): 3600
2020-10-19 21:59:41.662337+0200 [APP_NAME][10533:8512239] 6.24.0 - [Firebase/Analytics][I-ACS002003] Engagement timer canceled
2020-10-19 21:59:41.730872+0200 [APP_NAME][10533:8512253] 6.24.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: auto, user_engagement (_e), {
    engagement_time_msec (_et) = 18363;
    ga_event_origin (_o) = auto;
    ga_screen_class (_sc) = ViewController;
    ga_screen_id (_si) =<PHONE_NUMBER>745714558;
}
2020-10-19 21:59:41.730959+0200 [APP_NAME][10533:8512253] 6.24.0 - [Firebase/Analytics][I-ACS023073] Debug mode is enabled. Marking event as debug and real-time. Event name, parameters: user_engagement (_e), {
    engagement_time_msec (_et) = 18363;
    ga_debug (_dbg) = 1;
    ga_event_origin (_o) = auto;
    ga_realtime (_r) = 1;
    ga_screen_class (_sc) = ViewController;
    ga_screen_id (_si) =<PHONE_NUMBER>745714558;
}
2020-10-19 21:59:41.843313+0200 [APP_NAME][10533:8512239] 6.24.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: user_engagement (_e), {
    engagement_time_msec (_et) = 18363;
    ga_debug (_dbg) = 1;
    ga_event_origin (_o) = auto;
    ga_realtime (_r) = 1;
    ga_screen_class (_sc) = ViewController;
    ga_screen_id (_si) =<PHONE_NUMBER>745714558;
}
2020-10-19 21:59:41.845702+0200 [APP_NAME][10533:8512253] 6.24.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 0.7523399591445923
2020-10-19 21:59:41.846345+0200 [APP_NAME][10533:8512239] 6.24.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: auto, app_background (_ab), {
    ga_event_origin (_o) = auto;
    ga_screen_class (_sc) = ViewController;
    ga_screen_id (_si) =<PHONE_NUMBER>745714558;
}
2020-10-19 21:59:41.847057+0200 [APP_NAME][10533:8512239] 6.24.0 - [Firebase/Analytics][I-ACS023073] Debug mode is enabled. Marking event as debug and real-time. Event name, parameters: app_background (_ab), {
    ga_debug (_dbg) = 1;
    ga_event_origin (_o) = auto;
    ga_realtime (_r) = 1;
    ga_screen_class (_sc) = ViewController;
    ga_screen_id (_si) =<PHONE_NUMBER>745714558;
}
2020-10-19 21:59:41.873454+0200 [APP_NAME][10533:8512253] 6.24.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: app_background (_ab), {
    ga_debug (_dbg) = 1;
    ga_event_origin (_o) = auto;
    ga_realtime (_r) = 1;
    ga_screen_class (_sc) = ViewController;
    ga_screen_id (_si) =<PHONE_NUMBER>745714558;
}
2020-10-19 21:59:41.894994+0200 [APP_NAME][10533:8512253] 6.24.0 - [Firebase/Analytics][I-ACS023105] Event is not subject to real-time event count daily limit. Marking an event as real-time. Event name, parameters: user_engagement (_e), {
    engagement_time_msec (_et) = 18363;
    ga_debug (_dbg) = 1;
    ga_event_origin (_o) = auto;
    ga_realtime (_r) = 1;
    ga_screen_class (_sc) = ViewController;
    ga_screen_id (_si) =<PHONE_NUMBER>745714558;
}
2020-10-19 21:59:41.896963+0200 [APP_NAME][10533:8512253] 6.24.0 - [Firebase/Analytics][I-ACS023105] Event is not subject to real-time event count daily limit. Marking an event as real-time. Event name, parameters: app_background (_ab), {
    ga_debug (_dbg) = 1;
    ga_event_origin (_o) = auto;
    ga_realtime (_r) = 1;
    ga_screen_class (_sc) = ViewController;
    ga_screen_id (_si) =<PHONE_NUMBER>745714558;
}
2020-10-19 21:59:41.898184+0200 [APP_NAME][10533:8512253] 6.24.0 - [Firebase/Analytics][I-ACS023087] User property set. Name, value: lifetime_user_engagement (_lte), 108061
2020-10-19 21:59:41.898359+0200 [APP_NAME][10533:8512253] 6.24.0 - [Firebase/Analytics][I-ACS023087] User property set. Name, value: session_user_engagement (_se), 108061
2020-10-19 21:59:41.899798+0200 [APP_NAME][10533:8512239] 6.24.0 - [Firebase/Analytics][I-ACS012018] Saving bundle. size (bytes): 478
2020-10-19 21:59:41.899888+0200 [APP_NAME][10533:8512239] 6.24.0 - [Firebase/Analytics][I-ACS023116] Bundle added to the upload queue. BundleID, timestamp (ms): 21,<PHONE_NUMBER>598
2020-10-19 21:59:41.902337+0200 [APP_NAME][10533:8512239] 6.24.0 - [Firebase/Analytics][I-ACS023039] Measurement data sent to network. Timestamp (ms), data:<PHONE_NUMBER>902, <APMPBMeasurementBatch: 0x281a247c0>
2020-10-19 21:59:41.905441+0200 [APP_NAME][10533:8512253] 6.24.0 - [Firebase/Analytics][I-ACS900000] Uploading data. Host: https://app-measurement.com/a
2020-10-19 21:59:41.964515+0200 [APP_NAME][10533:8512522] 6.24.0 - [Firebase/Analytics][I-ACS901006] Received SSL challenge for host. Host: https://app-measurement.com/a
2020-10-19 21:59:42.032043+0200 [APP_NAME][10533:8512239] 6.24.0 - [Firebase/Analytics][I-ACS023044] Successful upload. Got network response. Code, size: 204, -1
2020-10-19 21:59:42.039661+0200 [APP_NAME][10533:8512253] 6.24.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-10-19 21:59:42.039966+0200 [APP_NAME][10533:8512253] 6.24.0 - [Firebase/Analytics][I-ACS023142] Cancelling background upload task. Task ID : 9

Looking into this now.

Just tested this on an iPhone 11 and it's working as expected.
From the logs, it looks like the test message was never fetched. Can you try relaunching the app after setting up the message for testing and getting the "Campaign ready for testing" toast on the Firebase console?

Yes I could see the "Campaign ready for testing" message. I sent the test message from the console to both devices, as shown below:

But only got the test message on one device, and got this log on my iPhone 11, which was the weird part:
 There are 0 test messages and 0 regular messages and 0 Firebase Analytics events to watch after resetting the message cache

I've had this problem as well.
I needed to remove and reinstall the app for the test message to appear.

@antonjn Thanks for your reply. I've tried the uninstall-and-install trick but it doesn't work for me.

Perhaps the issue is testing on multiple devices at a time... will try to duplicate.

You know what. This issue might be related to mine. If it's an iOS 13+ device the window might have been shown but gotten a zero frame, hence blocking all other messages to show until the app is restarted, as you can't interact to dismiss that window. Easy to check in the view debugger of an attached device. If you find a zero size window showing the FIRIAM message view that might be the problem. It's not that likely that this is your problem as it's related to the app's foreground/background state during the message window presentation eg. if you get a message during a drag to show home/app switcher gesture (drag up from bottom a little, hold the gesture and wait for message to "appear").

When I try this myself with a custom window it does not happen on iOS 12, 13 nor 14. So the problem seems to be with firebase!?, but I don't know what's going wrong.
I created a custom view controller and presented it in a window with
func presentInWindow() -> UIWindow {         let window = UIWindow(frame: UIScreen.main.bounds)         window.rootViewController = self         window.windowLevel = .normal         window.isHidden = false         return window     }
I do keep a strong reference to the window while it's presented but firebase seems to do that as well (in a static property in FIRIAMRenderingWindowHelper.m)
My window is triggered from the same place as the firebaseAnalytics.logEvent("trigger", parameters: nil) event is triggered, but my window don't get the zero frame problem at all.

Yeah, I can't seem to reproduce this. Tried testing with multiple devices at once and it still worked. Was using this flow:

Trigger test on device via console.
Kill and relaunch app.

@iflyingboots (nice GitHub handle!) are you still running into this?

@christibbs Hi, I just performed another test, same build, same devices, and, it worked! No idea what happened, but it's indeed working now.
Thank for your help!

Great to hear.


show a modal warning if no reward scores would be earned

the backend doesn't return the correct data right now, for testing add true ||

Please provide a short description of the change or if the change is sufficiently described in the GitHub issue, provide a link to the issue.
How has this been tested?
Please describe the test strategy you followed.

[ ] automated unit test
[ ] automated integration test
[ ] automated acceptance test
[ ] manual, exploratory test

In case of manual test, please document the test well including a set of user instructions and prerequisites. Each including an action, it's result, and where appropriate a screenshot.
Checklist before requesting a review

[ ] My code follows the coding guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] My code fulfilles all acceptance criteria
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have made corresponding changes to the documentation
[ ] I have added explanation of architectural decision and rationales to wiki/adr
[ ] I have updated the changes in the ticket description

Checklist for reviewer

[ ] The code works and does not throw errors
[ ] The code is easy to understand and there are no confusing parts
[ ] The code follows the coding guidelines of this project
[ ] The code change accomplishes what it is supposed to do
[ ] I cannot think of any use case in which the code does not behave as intended
[ ] The added and existing tests reasonably cover the code change
[ ] I cannot think of any test cases, input or edge cases that should be tested in addition
[ ] Description of the change is included in the documentation

Hast recht ich hab den check ergänzt, das hat gefehlt. Gerne mergen wenns dann so passt :)

Ich sehe jetzt gerade auch erst, bräuchten wird das nicht auf für das Quiz?

Außerdem, wir sind uns sicher, dass der NaN Fehler im Bild vom Anfang ein Backup Problem ist oder?  Und falls wir nicht wissen, wie lange es bei denen braucht, bis es gefixt ist, sollten wir nicht einen anderen Text anzeigen, wie: "You just learned a few days ago. You will not earn any reward point by doing this now."

ist doch auch fürs quiz oder nicht?

und ich würd da jetzt kein workaround machen für den backend bug

Ich sehe was du meinst mit dem Quiz, hab es vermutlich überflogen. Es scheint mir das mit dem Flashcard API changes hat die Funktion gekillt. Probiere es gerade aus, nachdem ich main in diesen branch lokal gemerged habe.
Es reagiert nicht :(


IP Connection trouble

I have been using the AHM 32 module for several months without issue, now it will not connect over IP.  It keeps trying to connect but returns an error.  I connected my AHM 16 to test connection to Companion and it was fine.  The unit returns a "ping" and there is normal control by "AHM System Manager" so the unit is likely o.k.  I deleted/re-installed the module but that did not help.

@joejoe100 Are you still experiencing this issue with the latest version of Companion? If so, what is the error being returned in the Companion log?


runtime: update govmm and move to virtio 1.0 for hotplugs

/test

@ganeshmaharaj CI looks good. Looks like we can get rid of the disable-modern switch.

/test

@grahamwhaley this change good to land?

@ganeshmaharaj - I think you need some formal acks from some virtio aware folks first :-) /cc @devimc @amshinde
Also, I think @jodh-intel will ask you to format the vendor update commits with the short logs of what has changed...

Yes please! ;)

https://github.com/kata-containers/community/blob/master/CONTRIBUTING.md#re-vendor-prs

@grahamwhaley @jodh-intel done and done. :)

/test

/test

@amshinde @devimc disabling the check is causing centos & RHEL to fail even the simplest of commands kata-runtime list --quiet. Not sure what is happening there. @chavafg @jcvenegas would you have any clues? Let me try and re-create this locally.

@amshinde @devimc @jodh-intel @grahamwhaley  if we want to go down the path of completely removing the virtio 0.9 version support, can we allow this PR to land in it's previous form (https://github.com/kata-containers/runtime/commit/ea40d17fbf5522b3f2c4d0d3a411ca2329d3a59b) and unblock virtiofs memory hotplug. Following that, I can work on clearing out the rest of the code?

i tried to re-create the centos issue locally and that seems to work just fine.
Running command '/usr/local/bin/kata-runtime [kata-runtime --log=/tmp/bundle489176700/log run --bundle=/tmp/bundle489176700 --console= --pid-file=/tmp/bundle489176700/pid --detach YmYSQ2ICQcri129TJPgN]'
[kata-runtime --log=/tmp/bundle489176700/log run --bundle=/tmp/bundle489176700 --console= --pid-file=/tmp/bundle489176700/pid --detach YmYSQ2ICQcri129TJPgN]
Timeout: 120 seconds
Exit Code: 0
Stdout:
Stderr:
Running command '/usr/local/bin/kata-runtime [kata-runtime state YmYSQ2ICQcri129TJPgN]'
[kata-runtime state YmYSQ2ICQcri129TJPgN]
Timeout: 120 seconds
Exit Code: 0
Stdout: {
  "ociVersion": "1.0.1-dev",
  "id": "YmYSQ2ICQcri129TJPgN",
  "status": "stopped",
  "pid": 4996,
  "bundle": "/tmp/bundle489176700",
  "annotations": {
    "com.github.containers.virtcontainers.pkg.oci.bundle_path": "/tmp/bundle489176700",
    "com.github.containers.virtcontainers.pkg.oci.config": "{\"ociVersion\":\"1.0.0-rc2-dev\",\"root\":{\"path\":\"rootfs\",\"readonly\":true},\"hostname\":\"runc\",\"mounts\":[{\"destination\":\"/proc\",\"type\":\"proc\",\"source\":\"proc\"},{\"destination\":\"/dev\",\"type\":\"tmpfs\",\"source\":\"tmpfs\",\"options\":[\"nosuid\",\"strictatime\",\"mode=755\",\"size=65536k\"]},{\"destination\":\"/dev/pts\",\"type\":\"devpts\",\"source\":\"devpts\",\"options\":[\"nosuid\",\"noexec\",\"newinstance\",\"ptmxmode=0666\",\"mode=0620\",\"gid=5\"]},{\"destination\":\"/dev/shm\",\"type\":\"tmpfs\",\"source\":\"shm\",\"options\":[\"nosuid\",\"noexec\",\"nodev\",\"mode=1777\",\"size=65536k\"]},{\"destination\":\"/dev/mqueue\",\"type\":\"mqueue\",\"source\":\"mqueue\",\"options\":[\"nosuid\",\"noexec\",\"nodev\"]},{\"destination\":\"/sys\",\"type\":\"sysfs\",\"source\":\"sysfs\",\"options\":[\"nosuid\",\"noexec\",\"nodev\",\"ro\"]},{\"destination\":\"/sys/fs/cgroup\",\"type\":\"cgroup\",\"source\":\"cgroup\",\"options\":[\"nosuid\",\"noexec\",\"nodev\",\"relatime\",\"ro\"]}],\"hooks\":{},\"linux\":{\"resources\":{\"devices\":[{\"allow\":false,\"access\":\"rwm\"}]},\"cgroupsPath\":\"kata\",\"namespaces\":[{\"type\":\"pid\"},{\"type\":\"network\"},{\"type\":\"ipc\"},{\"type\":\"uts\"},{\"type\":\"mount\"}],\"maskedPaths\":[\"/proc/kcore\",\"/proc/latency_stats\",\"/proc/timer_list\",\"/proc/timer_stats\",\"/proc/sched_debug\",\"/sys/firmware\"],\"readonlyPaths\":[\"/proc/asound\",\"/proc/bus\",\"/proc/fs\",\"/proc/irq\",\"/proc/sys\",\"/proc/sysrq-trigger\"]},\"process\":{\"consoleSize\":{\"height\":0,\"width\":0},\"user\":{\"uid\":0,\"gid\":0},\"args\":[\"true\"],\"env\":[\"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin\",\"TERM=xterm\"],\"cwd\":\"/\",\"rlimits\":[{\"type\":\"RLIMIT_NOFILE\",\"hard\":1024,\"soft\":1024}],\"noNewPrivileges\":true,\"capabilities\":{\"Bounding\":null,\"Effective\":null,\"Inheritable\":null,\"Permitted\":null,\"Ambient\":null}}}",
    "com.github.containers.virtcontainers.pkg.oci.container_type": "pod_sandbox"
  }
}
Stderr:
Running command '/usr/local/bin/kata-runtime [kata-runtime list --quiet]'
[kata-runtime list --quiet]
Timeout: 120 seconds
Exit Code: 0
Stdout: YmYSQ2ICQcri129TJPgN

Stderr:
Running command '/usr/local/bin/kata-runtime [kata-runtime delete --force YmYSQ2ICQcri129TJPgN]'
[kata-runtime delete --force YmYSQ2ICQcri129TJPgN]
Timeout: 120 seconds
Exit Code: 0
Stdout:
Stderr:
Running command '/usr/local/bin/kata-runtime [kata-runtime list --quiet]'
[kata-runtime list --quiet]
Timeout: 120 seconds
Exit Code: 0
Stdout:
Stderr:

• [SLOW TEST:8.890 seconds]
state
/home/ganeshma/go/src/github.com/kata-containers/tests/functional/state_test.go:26
  container
  /home/ganeshma/go/src/github.com/kata-containers/tests/vendor/github.com/onsi/ginkgo/extensions/table/table.go:92
    with workload [true], timeWait 5
    /home/ganeshma/go/src/github.com/kata-containers/tests/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46
------------------------------

Ran 8 of 8 Specs in 10.586 seconds
SUCCESS! -- 8 Passed | 0 Failed | 0 Pending | 0 Skipped PASS

Ginkgo ran 1 suite in 11.716992429s
Test Suite Passed
bash sanity/check_sanity.sh

I am going to say this might be azure vs local VM that i am hitting. i think it would be good to take this change in steps. Get the hotplug unblocked and then sort this out completely.

@ganeshmaharaj may be the problem is the host's kernel. CentOS and RHEL use old kernels.

/test

/test

Again, /cc @mcastelino for input on https://github.com/kata-containers/runtime/pull/1868#issuecomment-510327822.

LGTM
The fact that this works on Azure means the kvm issue has been addresses. The issue may crop up on older kernels in which case the user can opt to disable modern

FYI this seems to be the kvm fix for the original issue
https://patchwork.kernel.org/patch/10184241/

The landed fix
https://github.com/torvalds/linux/commit/d391f1207067268261add0485f0f34503539c5b0


How can I benchmark the gradients compression method in Deep500?

I need to test my gradients compression algorithm, but the tutorial does not include level3, would you give me some instruction, thank you!

I would start with the distributed training sample: https://github.com/deep500/deep500/blob/master/samples/distributed_training.py
and extending the DistributedOptimizer class with your logic, wrapping around an existing optimizer (as in the sample).

Do you mean that I can not test my gradients compression method in this version? If I implement the compression algorithm in communication.py, in which I change the tensor communicated with MPI, is it a solution?

For example, How can I test SparCML in Deep500? Thank you!


Research UI testing

References #117

Found these resources:

https://github.com/jupyter-widgets/ipywidgets/issues/2934
https://github.com/widgetti/solara
https://solara.dev/docs/howto/testing

Using Solara will cause us to switch from ipyvolume/ipywidgets to it. Doesn't seem viable at this stage of our development.
Galata  is the visual regression tester for ipywidgets which will require us to incorporate Javascript/Typescript.
{t:16}

Hi,

Using Solara will cause us to switch from ipyvolume/ipywidgets to it

This is not the case, solara works with all widget libraries, like classic ipywidgets and ipyvolume.
Since then we split off the package from solara and it is now called pytest-ipywidgets, which allows you to test with or without a browser (playwright).
A basic example is:
import ipywidgets as widgets
import playwright.sync_api
from IPython.display import display

def test_widget_button_solara(solara_test, page_session: playwright.sync_api.Page):
    # The test code runs in the same process as solara-server (which runs in a separate thread)
    # Note: this test uses ipywidgets directly, not solara components.
    button = widgets.Button(description="Click Me!")

    def change_description(obj):
        button.description = "Tested event"

    button.on_click(change_description)
    display(button)
    page_session.locator("text=Click Me!").click()
    page_session.locator("text=Tested event").wait_for()


Curl mime

Add. Support new mime API available since libcurl 7.56.0
Change. Use local HTTP server to run tests instead of using public web services.
Few changes to handle libcurl 7.56.0

Coverage decreased (-1.5%) to 59.441% when pulling a8288a6217f17207bb101e1d71ec68ec3ffc356b on moteus:curl_mime into 14a9246abe3b50309759e1b9f50426ef1f265680 on Lua-cURL:master.

Coverage decreased (-1.5%) to 59.441% when pulling a8288a6217f17207bb101e1d71ec68ec3ffc356b on moteus:curl_mime into 14a9246abe3b50309759e1b9f50426ef1f265680 on Lua-cURL:master.


I'm unable to see the docs folder mentioned in description. What am i missing?

You have to improve

no worries I found out you have to create one. Thanks

yes, for anyone wondering, you need to create a new /docs folder in the root of the project.


Removing Saved Stream in Rhino is not working properly

Happening on an M1 Mac 👇🏼

Hitting Remove icon
Click in Remove button in the modal
Result: Modal keeps and saved stream is not removed until Cancel button is hit or modal is closed (not sure about the exact pattern)

Works on an Intel mac with 2.11.1 installed

I think @clairekuang can have more info here


Binding doesn't work on value attribute of  element in IE11

Here is a sample that illustrates it. As you can see the progress element stays at value=0.
seen on IE11 with angular 1.4

That's a dupe of #7218 (see workaround in the issue)


Develop

Codecov Report

Merging #6 (e1e1d36) into main (e125ef4) will decrease coverage by 0.68%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main       #6      +/-   ##
==========================================
- Coverage   70.14%   69.46%   -0.69%
==========================================
  Files           3        3
  Lines         134      131       -3
==========================================
- Hits           94       91       -3
  Misses         23       23
  Partials       17       17

Impacted Files
Coverage Δ

ghdeps/print.go
100.00% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Update README.md to Resolve Errors

Adding an additional scheduler option as the previous example was failing to build the backend. #49
Also, the spec was missing in the groupTransformer which caused all insertions of new groups to fail with an error such that:
[1] 2024-03-21T21:53:32.085Z catalog warn Policy check failed for group:default/xxxxxxxx; caused by Error: Malformed envelope, <root> must NOT have additional properties type=plugin entity=group:default/xxxxx

thanks for all of these fixes @billabongrob


Missing dapr Python version 1.12.0 packages in PIP

It appears that no dapr python api packages were deployed to PIP as part of the version 1.12.0 release.  Would it be possible to publish new package versions for the following dapr libraries?
https://pypi.org/project/dapr/
https://pypi.org/project/dapr-ext-grpc/
https://pypi.org/project/flask-dapr/
https://pypi.org/project/dapr-ext-fastapi/

Yes this is as expected, please see https://github.com/dapr/python-sdk/issues/608
There were missing dependency builds for Python 3.12 at release time.

Closing as duplicate of tracking issue.


Connecting Cassandra to JNDI in WildFly: A Guide for Integration with cassandra-jdbc-wrapper-4.11.0.jar

Hi team,
I've developed this project and obtained the cassandra-jdbc-wrapper-4.11.0.jar. With this JAR, I've successfully executed a Java JDBC program. Currently, I'm attempting to establish a connection between Cassandra and JNDI (using WildFly). Could you provide guidance on achieving this use case if it's possible?

Hello @Arjunguptha98,
I´m not sure to understand your question.
If you want to configure a JDBC datasource identified by a JNDI name in WildFly, there is nothing specific to do for this driver and you can configure the datasource as any JDBC datasource in Wildfly as explained in the reference documentation.
And you can refer to this page for driver and connection URL settings.

Hi @maximevw
Thank you for your reply. I've obtained the JDBC URL for Cassandra. However, I'm uncertain about how to configure the Cassandra driver in standalone.xml and module.xml.

Hello @Arjunguptha98
First of all, I will convert this to a discussion as your question is not an issue related to the JDBC driver. :)
I have no expertise with Wildfly, but based on the following sources (here and there), I think you should do something like this:

Download the driver JAR.
Put the JAR in the folder {WildFlyDirectory}/modules/system/layers/base/com/ing/data and create a module.xml file in the same folder:

<module xmlns="urn:jboss:module:1.9" name="com.ing.data">
  <resources>
    <resource-root path=" cassandra-jdbc-wrapper-4.11.0-bundle.jar"/>
  </resources>
  <dependencies>
    <module name="javax.api"/>
    <module name="javax.transaction.api"/>
  </dependencies>
</module>

In the standalone.xml file, locate the <subsystem>/<datasources> part and include the following datasource :

<datasource jndi-name="java:jboss/datasources/cassandraDS" pool-name="cassandraDS" enabled="true">
  <connection-url>{JDBC URL}</connection-url>
  <driver>cassandra</driver>
  <security>
    <user-name>{username}</user-name>
    <password>{password}</password>
  </security>
</datasource>

Then, also in standalone.xml, locate the tag <drivers> and put this inside:

<driver name="cassandra" module="com.ing.data">
  <driver-class>com.ing.data.cassandra.jdbc.CassandraDriver</driver-class>
</driver>

Reboot the Wildfly server.

There is no guarantee it works exactly like this, I just deduced that from various documentation found on the Internet and I never tested this.
I really encourage you to consult the WildFly Admin guide for further details on JDBC datasource configuration.


[fuzz] Create ext authz http fuzzer with dynamic metadata

Signed-off-by: Asra Ali<EMAIL_ADDRESS>Commit Message: Added dedicated fuzzer for ext_authz filter.
Additional Description:

Speed: ~400-500 exec/sec locally over the course of 5ish minutes.
Coverage: Covers 70.5% of http/ext_authz/ directory code. Gaps are:

Configuration code (merge context extensions)
Encode pathway
response features like headers to add (only status is fuzzed)

Risk Level: Low
Testing: Added corpus entries mirroring unit test cases, including metadata.

This is ready for review!
@fcfort

This looks reasonable though I admit that I need to learn more about how fuzz tests work in Envoy.

@fcfort would you be able to review (or find a review)?
(@chaoqin-li1123 I'm adding a new fuzzer here)

@asraa I am closing so we keep active assignment on PRs. Please re-open if you want to continue this workstream.

/wait

cc @adisuissa


Slow/laggy loading of channel list

Upon refreshing or navigating to Zulip, it takes ~10 seconds for the channel list to stabilize. For example on the Rust Zulip, where I am subscribed to about 50 channels:

I see this behavior on Firefox, Windows and MacOs. Originally reported on the Rust Zulip, and confirmed by another user https://rust-lang.zulipchat.com/#narrow/stream/122653-zulip/topic/Slow.20loading.20of.20channel.20list.
Zulip Server and web app version:

[x] Zulip Cloud (*.zulipchat.com)
[ ] Zulip Server 8.0+
[ ] Zulip Server 7.0+
[ ] Zulip Server 6.0+
[ ] Zulip Server 5.0 or older
[ ] Other or not sure

Some more research was done at that linked Zulip thread - looks like it is loading 2000 messages per channel for 15 channels, each channel about 2.5M, means about 40 MB to fetch before it can show the channel list. It should definitely fetch the channel list first and use that to populate the display, before starting to load all the messages.
Also as @apiraino  pointed out, 2000 messages per channel is a lot to fetch preemptively, could probably get by with significantly fewer until the user scrolls back.

This is because the definition of https://zulip.com/help/manage-inactive-channels is not checkable without fetching deeper message history. #27009 will address this, but in the meantime, if you turn off that setting, the channel list should be stable immediately before any messages are fetched.
(This symptom is important to address via #27009, since it seems annoying and that setting is enabled by default.)

Let me see if we can get #30629 finished, as that's the key piece of engineering required to fix this.

Closing as fixed by #30629.


"make install" fails on Mac OS X

Mac OS X install command does not accept -D (capital D)
$ install
usage: install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
[-o owner] file1 file2
install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
[-o owner] file1 ... fileN directory
install -d [-v] [-g group] [-m mode] [-o owner] directory ...

From man install: -D create all leading components of DEST except the last, then copy SOURCE to DEST
Looks like we could add an extra step to the recipe to just do mkdir -p on dirname of the target.

Closed by https://github.com/google/grumpy/pull/213


Adding nep5 token to neoscan

Hi,
I know this is not the place for questions but I have tried on discord and did not get any answer so I am hoping to find help here.
I have neoscan docker running with private net. After creating and deploying new token I am able to see it in my wallet but I am not able to see that token on neoscan. When trying to getBalance with neonjs using neoscan my token balance is not visible, it is visible only if I ping directly privnet.
My question is how can I add/register/issue token on neoscan so I can query token balance with neoscan api?

if it is the last version of neo-local priv-net docker(that includes the neo-python notifications DB) it should pick nep5 tokens automatically. There's no support for nep5 in the older version.


Moved persist out of the PreparationsManager

flatMap for the win. This sequences the effect of planning the query with the effect of running the query. I should write tests for this… Probably don't merge yet.
[ch2223]

@djspiewak interesting, the cancel preparation when pending test failed in appveyor but not on travis. Is that test ib a nondeterministic state?

Okay, unit tests are now in place verifying this works in a vacuum. I'd like to try an end-to-end test to ensure that it resolves the originating bug, but that doesn't have to hold up the merge. This has been published as 74.0.0-d5c16aa; @jsantos17, when you get a chance, can you check to see if the original issue is still reproducible with that snapshot?

@djspiewak I have tested this and aside from OOME also present in master, I discovered the /table/<uuid>/preparation endpoint no longer checks for errors in the preparation's query. Preparations with errors in the query are accepted but the preparation never starts. The preparation status isn't updated to reflect the failure either.
Will open a CH ticket to report the OOME in master; but in short, joins with sources larger than 2 megabytes makes quasar crash. Even when the result set is ~50 megabytes.

@jsantos17 @alissapajer Something is wrong elsewhere then. I just added a unit test which verifies that errors in evaluation are correctly reported by PreparationsManager.

@djspiewak just tested again with a clean database and your latest changes up to 0b4bb4e and I'm still seeing the same problem.  I can try that too.

I think you'll probably get an email. Effectively what this does is shift errors in compilation and planning from the initial POST to the async response, which is currently just emails.

@djspiewak just tried that and the server died with a template-related exception. Tried again in master and it worked fine.

Effectively what this does is shift errors in compilation and planning from the initial POST to the async response, which is currently just emails.

We still need to show the correct status in /table/<uuid>, right? I understand the UI polls that endpoint to show the status of preparations.

@jsantos17 Ticketed:

https://app.clubhouse.io/data/story/2494/preparation-errors-cause-email-template-explosion
https://app.clubhouse.io/data/story/2495/defaulttables-needs-to-maintain-error-state-on-async-preparation-failure

I think we should land this PR anyway, despite the fact that there are these other issues. These issues are technically pre-existing.
The real question is: does this PR fix the freezing on the POST on large joins? Not the OOM, but just the hang.

The real question is: does this PR fix the freezing on the POST on large joins? Not the OOM, but just the hang.

@djspiewak yes, it won't hang anymore. Let's land this and address the two tickets separately.


Breaks with jQuery in noconflict mode

Hello,
The plug-in does not seem to works when jQuery is in no conflict mode and that prototype is used.
After loading jquery and prototype on the same page, and setting jquery up in no-conflict mode, I observed a strange behaviour from hover-dropdown. The elements I hovered on appeared as expected, but the whole thing disappeared when I hovered off. Not just the menu, the button too. A "display: none" was added to the element's style.
This behaviour was observed for my custom elements, but I also checked with copy pasted elements from your demo site to confirm the issue. It still disappeared completely.
The workaround is to replace '$' by 'jQuery' in the code. I'm not sure this is worth changing, as very few people would have to work with prototype. I just wanted to signal the problem.
EDIT : It does not seems that simple after all. Even with 'jQuery' instead of '$' in the code, my elements still disappear when I setup jQuery in no-conflict mode.
Regards,
Manfred

Yeah, not sure what's going on, but if you look at the last line of the code, it's passing jQuery into the closure wrapping all the code and only using $ locally, so it doesn't have anything to do with a conflict, since it's properly using the jQuery variable.
So it definitely works if you don't use no conflict mode? Or do you have something else going on? Does it work normally without this plugin installed (i.e. by using Bootstrap's default behavior to click to activate the menu and then if you click off, it does what you expect, etc?).

I made a matrix with all the possibilities :

By webapp I mean widget that requires prototype.js to work.
Obviously, the webapp does not work as long as prototype is not loaded or jQuery is not in no-conflict mode. But when they are both enabled, the dropdown does not work anymore, be it your dropdown-hover or bootstrap's dropdown.
Seeing this last result, it seems to be an issue for bootstrap itself, and not the hover plugin. I am not really familiar with github, do you know if we can/must/should move the subject ?

Where are you calling jQuery.noConflict()?

I have a Durandal application, so before app.start(), but after jQuery is loaded (if that was your hidden question ?).


Specify license

Would love to know what license you have in mind for this project!
Richard

Added the MIT License! Feel free to do whatever you want with this project! :)

Great,  thanks! Looking forward to looking closer at it! 😀
Den fre. 23. des. 2016, 16:28 skrev Elliot Forbes<EMAIL_ADDRESS>
:

Closed #2 https://github.com/elliotforbes/angular-2-admin/issues/2.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/elliotforbes/angular-2-admin/issues/2#event-904154647,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFe70-VSVwKzQcg4V8R71JvnmCNOtod-ks5rK-iFgaJpZM4LUyuE
.


[BRD-56] - Tests e2e

E2E tests
E2E pipeline

Pull Request Test Coverage Report for Build 763208888

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 763149716:
0.0%

Covered Lines:
77

Relevant Lines:
77

💛  - Coveralls


FrontEnd: Make the copy button intuitive!

Check out the live website.
http://awesome-react-links.surge.sh
The website is in react.
It has a copy button next to the code snippet. make it more intuitive and beautiful.

@drex44 Can't seem to find that copy button on the production site. Am I just blind or is it gone?

sorry, please check again!

Now I can see it. 👍 Will check what I can do here.

Thanks @jrdevforlife

@RekkyRek Sure, go ahead. Make sure to post some screenshots.

I came up with a simple solution, nothing fancy. I went with your current "color scheme". It's easy to change later on tho.

Great Job man!. PR merged! :+1:


Jsonapi V3 Support for repeater fields

The Jsonapi is a great Bolt extension, I like it a lot in bolt v2. My compliments for the work done sofar.
I created a bolt site for managing my test cases using repeater fields.
Are there any plans to support the repeater fields as well in the nearby future?
At the moment it will return something like this:
"data": {
    "id": "19",
    "type": "testcases",
    "attributes": {
        "title": "Title",
        "steps": "Doctrine\\Common\\Collections\\ArrayCollection@0000000043727ab300000000657c01b3"
    },

Please try 3.0.1, and see if that works for you.

@Raistlfiren thanks for the update. Its better than the above, heres the output of one of mine:
{
  "specifications": [
    {
      "text": "EAN123",
      "float": "100",
      "image": {
        "file": "2016-07\/marlborough-oak.jpg",
        "url": "http:\/\/localhost\/files\/2016-07\/marlborough-oak.jpg",
        "thumbnail": "http:\/\/localhost\/thumbs\/400x300\/2016-07\/marlborough-oak.jpg"
      },
      "file": {
        "file": "2016-07\/704-document-1.pdf",
        "url": "http:\/\/localhost\/files\/2016-07\/704-document-1.pdf"
      },
      "integer": "2"
    },
    {
      "text": "fafas",
      "float": "244",
      "image": {
        "file": "",
        "url": "http:\/\/localhost\/files\/",
        "thumbnail": "http:\/\/localhost\/thumbs\/400x300\/"
      },
      "file": {
        "file": "",
        "url": "http:\/\/localhost\/files\/"
      },
      "integer": "4"
    }
  ]
}

It seems theres something a little weird with the naming of the fields :(


Feature/lol/cluster heartbeat task

Connects #219
Adds a cluster health check step to the worker pipeline. The EMR kickoff returns a job/cluster id. This is used to create an SQS message with the layer id and job id. When this is picked up in the queue, boto uses the data to check on the status of the instances and steps in the EMR job. If the instances or the steps are not in a running state, the job is marked as failed. Otherwise the job is added to the queue again and the original one is deleted.
To test:

Start off a job by uploading an image.
When UI indicates that the job is now processing, log in to AWS and take a look at your EMR job.
When it has started to spin up, stop the worker.
Use the SQS queue UI to view messages in the queue (there is a 5 minute delay on these messages, you might want to reduce that wait with the constants in process.py.
Look to see that a heartbeat message was added to the queue.
Restart the worker.
Terminate the EMR cluster before it finishes processing.
Note the UI updates and marks the job as failed.

Looks good, testing now.

+1 Tested

Consider adding some logging messages. Here's a few I created just for testing purposes:
diff --git a/src/rf/apps/workers/process.py b/src/rf/apps/workers/process.py
index ad8de70..3b20970 100644
--- a/src/rf/apps/workers/process.py
+++ b/src/rf/apps/workers/process.py
@@ -262,7 +262,10 @@ class QueueProcessor(object):
         except Layer.DoesNotExist:
             return False

+        log.info('Heartbeat for layer %d', layer_id)
+
         if not check_status(job_id):
+            log.info('EMR job for layer %d has failed!', layer_id)
             return status_updates.update_layer_status(layer_id,
                                                       enums.STATUS_FAILED,
                                                       ERROR_MESSAGE_EMR_DEAD)

:+1:


Option to save analysis launch json for reproducibility

UI and API are not of much assistance when it comes to collecting a workflow inputs in order to rerun

This should be available for the following subcommands

icav2-launch-pipeline-analysis


🐛 Quickstart throws an error in Deno deploy

Environment information
Supabase functions (Deno deploy edge functions) with supabase cli v1.77.9

What happened?
Importing autometrics via import { autometrics } from<EMAIL_ADDRESS>and wrapping a simple function gave me the following error:
[Info] Autometrics: Initiating a Prometheus Exporter on port: 9464, endpoint: /metrics

[Error] TypeError: (0 , re.createServer) is not a function
    at new r (https://esm.sh/v128/@opentelemetry/exporter-prometheus@0.41.0/esnext/exporter-prometheus.mjs:18:1309)
    at getMetricsProvider (https://esm.sh/v128/@autometrics/autometrics@0.5.0/esnext/autometrics.mjs:4:2276)
    at getMeter (https://esm.sh/v128/@autometrics/autometrics@0.5.0/esnext/autometrics.mjs:4:2387)
    at https://esm.sh/v128/@autometrics/autometrics@0.5.0/esnext/autometrics.mjs:4:3459
    at Server.<anonymous> (file:///home/deno/functions/rabbit/index.ts:15:26)

Expected result
I would expect a friendlier error message instead of a runtime Type error

Thanks for reporting this @brettimus! I need to update the quickstart for Deno-specific instructions. Just to validate that this works can you try importing autometrics with an npm specifier and let me know if that works?
So:
import { autometrics } from "npm:autometrics"

so yeah the issue here is npm specifiers still don't work with Deno deploy (support should be coming this year)
a deno script run with an npm:autometrics import does indeed work

This might be more of a hackday-type kind of suggestion, but we could consider using https://github.com/denoland/dnt instead. Then we'd build the library to be Deno-first, and let them generate the NPM packages for us. It's actually an easier setup altogether, assuming the NPM compatibility doesn't fail us...

oh Deno's dnt looks interesting - I'm tempted 🙂. We use some Node-specific APIs in the libraries that get polyfilled in Deno - I wonder how that will play along with it

If I understand correctly, dnt will polyfill it the other way around, so if you use Deno-specific APIs instead of the Node-specific APIs, it will still make sure it works well as an NPM package too. It might even work out-of-the-box with Node-specific APIs if you use npm: and node: prefixes internally, but then you probably will still run into the same issues with Deno deploy as you have now. But yeah, it might warrant some experimentation :)


Stroud-Eklund Shipyard moved 6000Km away

When i travel to Stroud-Eklund Shipyard, it's not where it should be, but 6000Km away.

Game Version
<IP_ADDRESS>
Language
日本語（JA）
New Game
Yes
Reproduction Steps
When i travel to Stroud-Eklund Shipyard.

I had this error too, and as a workaround, I was able to get into the shipyard by typing the command: player.moveto 167869
Note, I found that I needed to use the command after I got out of my ship on a planet somewhere, otherwise I was floating in space.


Change repo URLs for components of DiffinDiffs

I wish to move two packages to subfolders of another repo.
I have made the following check following other developers:

Clone the new repo and cd to that.
In Julia, I do:

julia> using TOML

julia> packages = ["DiffinDiffsBase", "InteractionWeightedDIDs"]
2-element Vector{String}:
 "DiffinDiffsBase"
 "InteractionWeightedDIDs"

julia> for pkg in packages
           versions = TOML.parsefile(joinpath(first(DEPOT_PATH), "registries",
                                     "General", pkg[1:1], pkg, "Versions.toml"))

           found = all(sort(collect(keys(versions)))) do version
               tree_sha = versions[version]["git-tree-sha1"]
               try
                   readchomp(`git rev-parse -q --verify "$(tree_sha)^{tree}"`)
                   return true
               catch
                   false
               end
           end
           println(pkg, ": ", found ? "all versions found!" : "ney")
       end
DiffinDiffsBase: all versions found!
InteractionWeightedDIDs: all versions found!

@DilumAluthge Hi! I am not sure whether manual PR like this is watched. So, I just wish to let you know so that the PR is not ignored. Thank you!


Save exact mongodb version as a temporary fix

https://github.com/joeframbach/agendash/issues/28

The mongodb dependency will be removed entirely in the upcoming release.


Addon opentelemetry-operator

Description of your changes
Adds a new Addon opentelemetry-operator

Fixes #5774
How has this code been tested?

Checklist

I have:

[x] Title of the PR starts with type (e.g. [Addon] , [example] or [Doc]).
[x] Updated/Added any relevant documentation and examples.
[x] New addon should be put in experimental.
[x] Update addon should modify the version in metadata.yaml to generate a new version.

Verified Addon promotion rules
If this pr wants to promote an experimental addon to verified, you must check whether meet these conditions too:

[x] This addon must be tested by addon's e2e-test to guarantee this addon can be enabled successfully.
This addon must have some basic but necessary information.

[x] An accessible icon url and source url defined in addon's metadata.yaml.
[x] A detail introduction include a basic example about how to use and what's the benefit of this addon in README.md.
[x] Also provide an introduction in KubeVela documentation.
[x] It's more likely to be accepted if useful examples provided in example dir.

@wonderflow @wangyikewxgm  This addon is done, Please review it :)

Thanks for review @wonderflow, Okay! I'll simplify this addon so that users can use it easily :)

@wonderflow How about below structure:
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
  name: otel-pod-sample-1
spec:
  components:
    - type: "k8s-objects"
      name: "otel-pod-1"
      properties:
        objects:
          - apiVersion: v1
            kind: Pod
            metadata:
              name: myapp-1
              annotations:
                sidecar.opentelemetry.io/inject: "true"
            spec:
              containers:
                - name: myapp
                  image: jaegertracing/vertx-create-span:operator-e2e-tests
                  ports:
                    - containerPort: 8080
                      protocol: TCP
      traits:
        - type: opentelemetry-collector
          name: otel-container
          properties:
            mode: sidecar
            config: |
              receivers:
                jaeger:
                  protocols:
                    thrift_compact:
              processors:

              exporters:
                logging:

              service:
                pipelines:
                  traces:
                    receivers: [jaeger]
                    processors: []
                    exporters: [logging]

Yes, this becomes better.

@wonderflow Please review it again, I've added component definitions as traits & Updated the Readme.