flutter google maps suddenly not working anymore

Steps to reproduce
cannot provide mre
Expected results
working google maps
Actual results
map not loading
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
D/CompatibilityChangeReporter( 8107): Compat change id reported: 183155436; UID 10420; state: ENABLED
I/FirebaseApp( 8107): Device unlocked: initializing all Firebase APIs for app [DEFAULT]
D/CompatibilityChangeReporter( 8107): Compat change id reported: 3400644; UID 10420; state: ENABLED
D/VRI[MainActivity]( 8107): Draw frame after cancel
D/ProfileInstaller( 8107): Installing profile for com.bytesmoke.saleswipe
D/MapsInitializer( 8107): preferredRenderer: null
D/zzcc    ( 8107): preferredRenderer: null
I/zzcc    ( 8107): Making Creator dynamically
W/ziparchive( 8107): Unable to open '/data/user_de/0/com.google.android.gms/app_chimera/m/00000002/DynamiteLoader.uncompressed.dm': No such file or directory
W/ziparchive( 8107): Unable to open '/data/user_de/0/com.google.android.gms/app_chimera/m/00000002/DynamiteLoader.uncompressed.dm': No such file or directory
I/DynamiteModule( 8107): Considering local module com.google.android.gms.maps_core_dynamite:0 and remote module com.google.android.gms.maps_core_dynamite:241610202
I/DynamiteModule( 8107): Selected remote version of com.google.android.gms.maps_core_dynamite, version >= 241610202
V/DynamiteModule( 8107): Dynamite loader version >= 2, using loadModule2NoCrashUtils
W/System  ( 8107): ClassLoader referenced unknown path:
D/nativeloader( 8107): Configuring clns-6 for other apk . target_sdk_version=34, uses_libraries=, library_path=/data/app/~~N6_kwJCGByb_Q8dss9-IwA==/com.google.android.gms-FAC3YavHcLO7pDWU5ozxrQ==/lib/arm64:/data/app/~~N6_kwJCGByb_Q8dss9-IwA==/com.google.android.gms-FAC3YavHcLO7pDWU5ozxrQ==/base.apk!/lib/arm64-v8a, permitted_path=/data:/mnt/expand:/data/user/0/com.google.android.gms
W/ziparchive( 8107): Unable to open '/data/user_de/0/com.google.android.gms/app_chimera/m/0000000d/dl-MapsCoreDynamite.integ_241610202100400.dm': No such file or directory
W/ziparchive( 8107): Unable to open '/data/user_de/0/com.google.android.gms/app_chimera/m/0000000d/dl-MapsCoreDynamite.integ_241610202100400.dm': No such file or directory
W/smoke.saleswipe( 8107): Accessing hidden method Ldalvik/system/VMStack;->getStackClass2()Ljava/lang/Class; (unsupported, reflection, allowed)
D/nativeloader( 8107): Configuring clns-7 for other apk . target_sdk_version=34, uses_libraries=ALL, library_path=/data/user_de/0/com.google.android.gms/app_chimera/m/0000000d/dl-MapsCoreDynamite.integ_241610202100400.apk!/lib/arm64-v8a, permitted_path=/data:/mnt/expand
D/nativeloader( 8107): Extending system_exposed_libraries: libedgetpu_dba.google.so
I/native  ( 8107): I0000 00:00:1718909660.203198    8107 jni_init.cc:8] Initializing JNI...
I/Google Android Maps SDK( 8107): Google Play services client version: 18020000
I/Google Android Maps SDK( 8107): Google Play services package version: 242213038
I/Google Android Maps SDK( 8107): Google Play services maps renderer version(maps_core): 241610202
D/MapsInitializer( 8107): loadedRenderer: LATEST
D/zzcc    ( 8107): preferredRenderer: null
I/Google Android Maps SDK( 8107): Google Play services package version: 242213038
I/Google Android Maps SDK( 8107): Google Play services maps renderer version(maps_core): 241610202
D/CompatibilityChangeReporter( 8107): Compat change id reported: 210923482; UID 10420; state: ENABLED
D/CompatibilityChangeReporter( 8107): Compat change id reported: 63938206; UID 10420; state: DISABLED
D/CompatibilityChangeReporter( 8107): Compat change id reported: 171228096; UID 10420; state: ENABLED
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
I/PlatformViewsController( 8107): Hosting view in view hierarchy for platform view: 0
I/PlatformViewsController( 8107): PlatformView is using SurfaceProducer backend
D/CompatibilityChangeReporter( 8107): Compat change id reported: 236825255; UID 10420; state: ENABLED
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
I/GoogleMapController( 8107): Installing custom TextureView driven invalidator.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
D/TrafficStats( 8107): tagSocket(242) with statsTag=0x99e6744e, statsUid=-1
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
I/smoke.saleswipe( 8107): Compiler allocated 4617KB to compile void m.edh.b(m.dls, m.eca, m.eec, m.elq, boolean)
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
I/smoke.saleswipe( 8107): Compiler allocated 7550KB to compile void m.eiq.V(m.enc, m.fdq, android.content.res.Resources, m.ele, m.evm, boolean, m.dld, java.util.Map, boolean, boolean)
I/smoke.saleswipe( 8107): Compiler allocated 7521KB to compile void m.eiq.V(m.enc, m.fdq, android.content.res.Resources, m.ele, m.evm, boolean, m.dld, java.util.Map, boolean, boolean)
I/smoke.saleswipe( 8107): Compiler allocated 8406KB to compile void m.eiq.V(m.enc, m.fdq, android.content.res.Resources, m.ele, m.evm, boolean, m.dld, java.util.Map, boolean, boolean)
I/smoke.saleswipe( 8107): Compiler allocated 5172KB to compile void m.ezm.e()
I/smoke.saleswipe( 8107): Compiler allocated 4617KB to compile void m.edh.b(m.dls, m.eca, m.eec, m.elq, boolean)
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
W/ProxyAndroidLoggerBackend( 8107): Too many Flogger logs received before configuration. Dropping old logs.
I/smoke.saleswipe( 8107): Background concurrent mark compact GC freed 358207(25MB) AllocSpace objects, 125(9428KB) LOS objects, 75% free, 17MB/69MB, paused 348us,6.508ms total 97.177ms
W/smoke.saleswipe( 8107): ApkAssets: Deleting an ApkAssets object '<empty> and /data/app/~~iN-zcRNG4bVAjA4YvBojPg==/com.google.android.marvin.talkback-NfXiUhkfBtJLB7XZy3grpA==/base.apk' with 1 weak references
W/smoke.saleswipe( 8107): ApkAssets: Deleting an ApkAssets object '<empty> and /data/app/~~iN-zcRNG4bVAjA4YvBojPg==/com.google.android.marvin.talkback-NfXiUhkfBtJLB7XZy3grpA==/split_config.arm64_v8a.apk' with 1 weak references
W/DynamiteModule( 8107): Local module descriptor class for com.google.android.gms.googlecertificates not found.
I/DynamiteModule( 8107): Considering local module com.google.android.gms.googlecertificates:0 and remote module com.google.android.gms.googlecertificates:7
I/DynamiteModule( 8107): Selected remote version of com.google.android.gms.googlecertificates, version >= 7
W/smoke.saleswipe( 8107): ClassLoaderContext classpath size mismatch. expected=12, found=7 (DLC[];PCL[base.apk*1841315031:base.apk!classes2.dex*1936044014:base.apk!classes3.dex*4028701199:base.apk!classes4.dex*2147827830:base.apk!classes5.dex*1440606754:base.apk!classes6.dex*732157406:base.apk!classes7.dex*3342168216:base.apk!classes8.dex*2496763741:base.apk!classes9.dex*2929669126:base.apk!classes10.dex*3072727027:base.apk!classes11.dex*3450565915:base.apk!classes12.dex*830974882]{PCL[/system/framework/org.apache.http.legacy.jar*2132279816]#PCL[/system/framework/com.android.media.remotedisplay.jar*521634980]#PCL[/system/framework/com.android.location.provider.jar*2604345736]#PCL[/system_ext/framework/org.carconnectivity.android.digitalkey.timesync.jar*418335382]} | DLC[];PCL[/data/app/~~K0e5FjzphumHghhoXWsJbg==/com.bytesmoke.saleswipe-O08Eek2eQ3HpXOt9Hrj11A==/base.apk*1582518668:/data/app/~~K0e5FjzphumHghhoXWsJbg==/com.bytesmoke.saleswipe-O08Eek2eQ3HpXOt9Hrj11A==/base.apk!classes2.dex*101465414:/data/app/~~K0e5FjzphumHghhoXWsJbg==/com.bytesmoke.saleswipe-O08Eek2eQ3HpXOt9Hrj11A==/base.apk!classes3.dex*2345837250:/data/app/~~K0e5FjzphumHghhoXWsJbg==/com.bytesmoke.saleswipe-O08Eek2eQ3HpXOt9Hrj11A==/base.apk!classes4.dex*3397723637:/data/app/~~K0e5FjzphumHghhoXWsJbg==/com.bytesmoke.saleswipe-O08Eek2eQ3HpXOt9Hrj11A==/base.apk!classes5.dex*2804164671:/data/app/~~K0e5FjzphumHghhoXWsJbg==/com.bytesmoke.saleswipe-O08Eek2eQ3HpXOt9Hrj11A==/base.apk!classes6.dex*1643957337:/data/app/~~K0e5FjzphumHghhoXWsJbg==/com.bytesmoke.saleswipe-O08Eek2eQ3HpXOt9Hrj11A==/base.apk!classes7.dex*1877423313]{PCL[/system/framework/org.apache.http.legacy.jar*2132279816]})

Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.22.2, on Microsoft Windows [Version 10.0.22631.3737], locale en-DE)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.5.4)
[√] Android Studio (version 2022.1)
[√] IntelliJ IDEA Ultimate Edition (version 2023.1)
[√] Connected device (5 available)
[√] Network resources

• No issues found!

Hi @leeflix, what version of google_maps_flutter & google_maps_flutter_android are you using?
Is your google maps api key properly setting? Was it working before? Did you change anything before it failed?


[FIX] Fix missing week in January

Fix missing week in January for leap years.

Could you elaborate how this fixes the problem?

We will have fixed amount of weeks in month. Previously calculating amount was incorrect for leap years, I tried to fixed it but when I fixed January a December has been broken. There is no need for using any algorithms for that, it's known soulution used for example on os x calendar (and probably many others) also now calendar with have fixed height.


isKeyframe is returning undefined

Hi, I've found that the isKeyframe property is returning undefined for most of the webm videos I've tried, this causes an error with the VideoDecoder because it needs to start decoding on a keyframe. Can you look into it?

Here's a example video if you need one.
https://drive.google.com/file/d/1d3P2nzexyQA8yKTgticgLddqbPn_zIKP/view?usp=sharing

Hi @Tenpi, this issue was fixed in this PR -> https://github.com/jscodec/jswebm/pull/25
However, you are still getting this issue because the npm package is not updated. So you are still using an older version of jswebm, where the undefined issue isn't solved. I think @brianxautumn owns this repo and he has the access to publish it to npm. In the meanwhile, if you want to use this repo, you can fork it, and use the github url in the package.json to install this package.

Ok, I apologize for missing that this was already fixed. I can see that the npm package hasn't been updated in 2 years.
@brianxautumn, if you are no longer interested in maintaining this project, you should add someone else with write access to the npm package. Thanks.
For now I am going to use my fork of this project.

HI, I'll try to get a new revision published soon! and yes need help maintaining

Ok, I apologize for missing that this was already fixed. I can see that the npm package hasn't been updated in 2 years.
@brianxautumn, if you are no longer interested in maintaining this project, you should add someone else with write access to the npm package. Thanks.
For now I am going to use my fork of this project.

Your fork makes the lib being able to work with Nuxt, thanks! Nice fix


GEOMESA-917 Reducing deduplication

OR queries are split into disjoint form, so that we don't have to deduplicate them
Filter manipulation (handling dwithin units, IDL bounds, etc) is done up front instead of inside the different strategies

Can you add a test for a query that is
bbox(whole world) AND dtg during AND (attr = 'foo' OR attr = 'bar' OR attr = 'baz')
where you have an attribute index on 'attr' of high cardinality and ensure that we are not trying to dedupe it?

Merged.  9b9a290..dd5dcc9


Flutter App Crashes on IOS with Memory Leak Error While Connecting to Firestore

I have a flutter app that is working perfectly on Android, now trying to test it on IOS.
Device: Real Iphone 7 - IOS: 15.7.3
problem:
App crashes and shutsdown once it try to connect to the first firestore stream builder in the app and it generates a memory leak error like the below. what is causing the problem?
Error:
 thread #10, name = 'io.flutter.1.ui', stop reason = EXC_RESOURCE RESOURCE_TYPE_MEMORY (limit=1450 MB, unused=0x0)
code:
class _AppConfigPageState extends State<AppConfigPage> {
@override
 Widget build(BuildContext context) {
    debugPrint("AppConfig"); --> this is printed successfully
    // it crashes here exactly.
    return StreamBuilder<QuerySnapshot>(
     stream: FirebaseFirestore.instance
        .collection('AppConfigsCollection')
        .snapshots(),
     builder: (context, snapshot) {
      if (!snapshot.hasData) {
        //it never reaches here.
        return Container();
      } else {
        if (snapshot.data!.docs.isEmpty) {
          //it never reaches here.
          return CheckYourConnectionPage();
        } else {
        //it nevers reaches here.
        rest of code.
        }}});}}

full output of the run:
Launching lib/main.dart on iPhone in debug mode...
Automatically signing iOS for device deployment using specified development team in Xcode project: Z89FAWAJDM
Running Xcode build...
Xcode build done.                                           308.0s
Installing and launching...
10.3.0 - [FirebaseMessaging][I-FCM001000] FIRMessaging Remote Notifications proxy enabled, will swizzle remote notification receiver handlers. If you'd prefer to manually integrate Firebase Messaging, add "FirebaseAppDelegateProxyEnabled" to your Info.plist, and set it to NO. Follow the instructions at:
https://firebase.google.com/docs/cloud-messaging/ios/client#method_swizzling_in_firebase_messaging
to ensure proper integration.
10.3.0 - [FirebaseAnalytics][I-ACS023007] Analytics v.10.3.0 started
10.3.0 - [FirebaseAnalytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)
no valid “aps-environment” entitlement string found for application
10.3.0 - [FirebaseMessaging][I-FCM012002] Error in application:didFailToRegisterForRemoteNotificationsWithError: no valid “aps-environment” entitlement string found for application
10.3.0 - [FirebaseAnalytics][I-ACS800023] No pending snapshot to activate. SDK name: app_measurement
10.3.0 - [FirebaseAnalytics][I-ACS023012] Analytics collection enabled
10.3.0 - [FirebaseAnalytics][I-ACS023220] Analytics screen reporting is enabled. Call Analytics.logEvent(AnalyticsEventScreenView, parameters: [...]) to log a screen view event. To disable automatic screen reporting, set the flag FirebaseAutomaticScreenReportingEnabled to NO (boolean) in the Info.plist
Debug service listening on ws://<IP_ADDRESS>:60988/AWnfx2cL1rU=/ws
Syncing files to device iPhone...
flutter: LangInit
flutter: en
flutter: AppConfig
[GETX] Instance "MyLocaleController" has been created
[GETX] Instance "MyLocaleController" has been initialized
[GETX] Instance "GetMaterialController" has been created
[GETX] Instance "GetMaterialController" has been initialized
* thread #10, name = 'io.flutter.1.ui', stop reason = EXC_RESOURCE RESOURCE_TYPE_MEMORY (limit=1450 MB, unused=0x0)
    frame #0: 0x000000010886924c Flutter`dart::Object::HandleImpl(dart::Zone*, dart::ObjectPtr, long) + 116
Flutter`dart::Object::HandleImpl:
->  0x10886924c <+116>: str    x20, [x9, #0x18]
    0x108869250 <+120>: tbnz   w20, #0x0, 0x10886925c    ; <+132>
    0x108869254 <+124>: mov    w8, #0x3a
    0x108869258 <+128>: b      0x108869278               ; <+160>
Target 0: (Runner) stopped.
Lost connection to device

Flutter doctor:
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.3.4, on macOS 12.6 21G115 darwin-x64, locale en-US)                                                                                Checking Android licenses is taking an unexpectedly long time...[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.0.1)
[✗] Chrome - develop for the web (Cannot find Chrome executable at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
    ! Cannot find Chrome.  Doctor found issues in 1 category.

Hello @SherifSaidElahl. This issue seems specific to cloud_firestore. Therefore, Flutter is not the correct place to raise this issue. I suggest you raise an issue on the FlutterFire repository (https://github.com/firebase/flutterfire/issues). Since this is not an issue with Flutter itself, I'll close this issue. Thank you


Feat: plugin rax store

Codecov Report

Merging #554 (575a128) into release-next (6546dd9) will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff              @@
##           release-next     #554   +/-   ##
=============================================
  Coverage         87.80%   87.80%
=============================================
  Files                21       21
  Lines               779      779
  Branches            196      196
=============================================
  Hits                684      684
  Misses               86       86
  Partials              9        9

Version
rax-app

build-plugin-rax-app 6.1.4-0
build-plugin-rax-kraken 1.0.10-0
plugin-rax-store 1.0.0
build-plugin-rax-web 1.1.6-0
build-plugin-rax-weex  1.0.9-0
rax-app-renderer 1.1.1-0
rax-app 3.3.0-0

Version
rax-app

build-plugin-rax-app 6.1.4-0
build-plugin-rax-kraken 1.0.10-0
plugin-rax-store 1.0.0
build-plugin-rax-web 1.1.6-0
build-plugin-rax-weex  1.0.9-0
rax-app-renderer 1.1.1-0
rax-app 3.3.0-0


Bottom Right and Bottom Left Position

A feature to support bottom right and bottom left position.

Added feature!


GEODE-8221: Commits session data prior to sending output to browser

Refactors abstraction of CommitSessionValve.


tutorial.ipynb

based on a previous reply, I edited my node.csv and link.csv so that the ids are floats in both and I also used path4gmns==0.9.4. This got me through the first issue and i get the following warning output from 3.1

Next I tried two things:

Since I already have a demand.csv and zone.csv from running grid2demand, I ran 3.2 directly from 3.0 with these demand.csv and zone.csv
zone.csv
demand.csv
and I got this error:

To see if my issue was stemming from files with grid2demand, I deleted my demand.csv and zone.csv files and ran section 3.2 to create them.
That created these demand.csv and zone.csv
zone_from tutorial.csv
demand_from tutorial.csv
and yielded this error in the next block of code:

I am not sure if these issues stem from downgrading to 0.9.4 or if there is another problem with my data. thanks for your help!

Those warnings and exceptions are not errors of Path4GMNS. They are part of the internal validation which indicate what went wrong with the input data and what the possible fixes are.
Take the first two warnings for example, Path4GMNS warns you that settings.yml is missing, and it will set up the run using the default values for demand period and agent type. You can find details on settings.yml in the tutorial under session 4.1 and in the Use Cases.
Then the next one (i.e., KeyError: 'zone_id') informs you that the column of zone_id is missing from zone.csv. There is a column with header activity_zone_id rather than zone_id in your zone file.
The last one is related to the length unit of links. As mentioned in the tutorial, Path4GMNS uses mile and mile per hour (mph) as the default units for length and speed in its internal calculation and all outputs. Links presented in your link.csv have large values in length, which do not make sense if mile is the unit.
As the demand synthesis is subjected to a time budget (the default value is 120 min), no OD pairs are connected / reachable given this time budget and no demand is synthesized (see Synthesize Zones and OD Demand for details). Therefore, you got the last warning from Path4GMNS (i.e., "NO VALID OD VOLUME!! Double check your demand.csv and make sure there is zone info in node.csv'") as your demand_from tutorial.csv is empty.
You can get around this issue by specifying the length unit as meter (or bump up the time budget to a very large number).


Split item store functionality out from PostgresDriver

Similar to #127 (merged in d6507f0)
This extracts the ItemStore functionality out from BackingStoreDriver
and its subclasses, in a similar way to that which was already done
for EntryLog.  That is, ItemStore has been converted to an interface,
with separate implementations for on-demand and transactional work.
Extra things done:

the InMemory*DAOs have been simplified - it makes sense to have one
class that implements both the query and command interfaces.
the InMemoryEntryLog was so similar to the OnDemandEntryLog that
they could actually share most of their code.
there's no need for an InMemoryItemStore -- it's just an
OnDemandItemStore with InMemoryItemDAO backing it
there's some gnarly bits in ItemStore where the getIterator()
methods need to know those items which are referenced by particular
entries; so the ItemStore needs access to the entry storage as well
as the item storage.  This is reflected in how we end up
constructing the various ItemStore implementations
the previously @Ignored test in PostgresDriverTransactionalTest has
been reinstated in PostgresDriverTransactionalFunctionalTest, in
terms of a transaction on a PostgresRegister.

@karlbaker02 I pushed fixes for the things you mentioned today

👍


Extend state manager (VM)

Is there a way we could extend the class, either by require('inherit') or ES6 classes?


Add Datatypes/Data structures to stdlib

We need to provide a set of Type's that can be used in constructing computation descriptions in the StdLib.
As an initial list might be:

Int
Long
Double
String
Boolean
Byte
Decimal
Char
Float
Null
Short
Timestamp
Date

Data Structures (we need to define the semantics of these since they are not concrete collections at this point)

Array
Map
Set
Tuple

Can I take this up?

Sure @afsalthaj!

@afsalthaj - let me know if you'd like to pair on this.

@jdegoes
What implementations of Data Structures should we support? Ideally it could be abstract but because the AnalyticsModule currently defines the types, the implementing modules don't really have a choice in the matter.
e.g. Should we use java collections for speed or Scala collections for more seamless interop? Scala collections are quite slow, and Java collections have their own problems.
IMO It would be ideal if this could be abstracted away entirely so that we could use efficient structures to represent the operations as an interpreter concern (e.g. perhaps we want to use apache arrow for our arrays rather than scala.Array) etc
This would mean describing an Array like thing for example and having the interpreter make this concrete. Thoughts?

@camjo
For Type, we only need to describe the type the user will receive after running the flow. So simple data structures like Scala's Map probably suffice.
Internally, inside LocalAnalyticsModule, we will use Array for virtually everything (in fact, mostly arrays of unboxed primitives), because it's about the fastest we can do.

Btw, the Type stuff doesn't constrain our implementation at all. That's just for end-stage conversion.

@dandxy89 Sure. Please let me know a good time to discuss. (Will be away the next 3 days). Meanwhile we having some direct discussion with @camjo .

@dandxy89 @camjo
I have just raised a PR for the data-types.
You could take a look at this:
https://github.com/scalaz/scalaz-analytics/pull/12
I have got a few doubts on whether users will be representing the date and timestamp using java.sql types. Also we could discuss on data structures (array, map etc)

I will be adding Array (it could be a list since it forms only a description at this point ?),
Map and set today.

How do you see the syntax for custom data structures (cases classes at least)?


Allow more than one instance of the Ebay API connection

Use cases:

Running a test with two different Ebay users (e.g. buyer and seller)
Connecting to sandbox and production system simultaneously. That is necessary when in a test/dev system you want to work with category suggestions: Category suggestions work only in production system, not in the sandbox. So, this call may just as well always connect to the production system, no matter whether it is test, dev or production.

The new usage pattern may then look like this:
ebay1 = Ebayr::API.new(configuration_hash_from_file)
ebay.call(:GetSuggestedCategories, options_1)

ebay2 = Ebayr::API.new(another_configuration_hash_from_file)
ebay.call(:GetItem, options_2)

allthewhile maintaining backward compatibility…

I am going to implement this feature now and use it for my client. I will consider your comments/suggestions before making a PR.

Just found out that this works:
2.2.2 :014 > class BB; include Ebayr.dup;end
 => BB
2.2.2 :015 > class AA; include Ebayr.dup;end
 => AA
2.2.2 :016 > bb = BB.new
 => #<BB:0x007fae9d195890>
2.2.2 :017 > bb.ru_name = 1
 => 1
2.2.2 :018 > aa = AA.new
 => #<AA:0x007fae9c9da178>
2.2.2 :020 > aa.ru_name = 3
 => 3
2.2.2 :021 > aa.ru_name
 => 3
2.2.2 :022 > bb.ru_name
 => 1

So, instances of AA and BB can be used for different connections. Not sure if I like this solution. I am bothered by the dup in the include.

I have decided for now to go with this:
class EbayConnector
  def initialize(force_environment: :sandbox)
    @ebayr = Ebayr.dup
    if production? || force_environment.to_sym == :production
      load_configuration 'config/ebay.conf.yml'
    else
      load_configuration 'config/ebay.conf.sandbox.yml'
    end
  end

  def load_configuration(file)
    config = Psych.load_file(file)
    config.each do |key, value|
      @ebayr.send "#{key}=", value
    end
  end

  def method_missing(method, *args)
    handle_call method, *args
end

  def handle_call(request_type, options = {})
    @ebayr.call request_type, options
  end
end

It is not totally elegant, but it works. Any objections to close this issue?

@meismann You still working on this? I guess having an instantiable EBayr::Client class with the same API as the module makes sense. Not sure why including the module as-is in the class wouldn't work...

Actually, it is done (https://github.com/meismann/ebayr/tree/multiple-instances) and I have been using it for my client since a few days. I need my current PR merged before I can open another one. AFAIK, if I merge the my multiple-instances branch in my master, it would be in the current PR automatically.

Oh, and I need to update the README. So, it is not completely done, admittedly ;-)

Cool. How about we merge it into the v0.1 branch, and release a gem in the next week or so?

All right, agreed!

@meismann I'd like this feature, but it can't be merged standalone into master as-is. Did you base it on your local fork? Could you to re-implement it against @GCorbel 's changes?


DefaultPropsProvider breaks microfrontend setups - please move to @mui/styles

Summary
The newly introduced DefaultPropsProvider (https://github.com/mui/material-ui/pull/42820) causes problems in micro-frontend setups, since it is located in the main @mui/material package which is usually too big to be shared between modules in a micro-frontend environment.
The root of the problem is that each module in the environment will get its own instance of DefaultPropsProvider, meaning that custom properties injected in an orchestrator (e.g. an App Shell) are erased on the module-level.
The common way to solve this issue would be to instead move this provider to a smaller, shareable package which can be shared. The best place is probably @mui/styles, which also houses the ThemeProvider (which also needs to be shared across modules).
Examples
No response
Motivation
Better support for micro-frontends.
Search keywords: DefaultPropsProvider

The DefaultPropsProvider in @mui/material is a reexport of @mui/system so the context is already created from a shareable package: https://github.com/mui/material-ui/blob/next/packages/mui-system/src/DefaultPropsProvider/DefaultPropsProvider.tsx#L6.

@siriwatknp thanks for the reply! We already share @mui/system, and unfortunately the problem is still happening.
I will look into a reproducible example, but unfortunately our setup is proprietary and quite complex.

We already share @mui/system, and unfortunately the problem is still happening.

The behavior should already be the same for the ThemeProvider and the DefaultPropsProvider from @mui/system. You mentioned @mui/styles - this package is related to the v4 styling (makeStyles, etc).
One thing to make sure is to check that you have the same versions everywhere - this is most often the issue for ending up with different contexts.

Close this issue as I think it's related to the setup, not Material UI. Feel free to reopen with reproducible sandbox/repo, I'm happy to take a look.


Use makedirs instead of mkdir

No reason not to, and it has fewer assumptions about the directory structure.

Thank you for this simple but important improvement.


Error with external-secrets, ArgoCD, kustomize, and custom Namespace

Describe the solution you'd like
To be able to use external-secrets with ArgoCD and kustomize without encountering the stat /tmp/certs/tls.crt: no such file or directory error, while using a custom Namespace and deploying SecretStore in the same Application as external-secrets.
What is the added value?
By solving this issue, users will be able to manage external-secrets using ArgoCD and GitHub with a code-based approach and deploy it more flexibly with kustomize.
Give us examples of the outcome
The ideal outcome would be the following configuration working without any errors:
ArgoCD refers to user-defined manifests instead of Helm
kustomization.yaml in the referenced directory specifies helmCharts
SecretStore is deployed in the same Application as external-secrets
A custom Namespace is used
You can refer to the following manifests as examples:
external-secrets
application
Observations (Constraints, Context, etc):
The full error message is as follows. This occurred in external-secrets-webhook:
{"level":"info","ts":1682764719.5310128,"logger":"setup","msg":"validating certs"}
{"level":"error","ts":1682764719.5310957,"logger":"setup","msg":"invalid certs. retrying...","error":"stat /tmp/certs/tls.crt: no such file or directory","stacktrace":"github.com/external-secrets/external-secrets/cmd.waitForCerts\n\t/home/runner/work/external-secrets/external-secrets/cmd/webhook.go:188\ngithub.com/external-secrets/external-secrets/cmd.glob..func3\n\t/home/runner/work/external-secrets/external-secrets/cmd/webhook.go:82\ngithub.com/spf13/cobra.(*Command).execute\n\t/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:920\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\t/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:1044\ngithub.com/spf13/cobra.(*Command).Execute\n\t/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:968\ngithub.com/external-secrets/external-secrets/cmd.Execute\n\t/home/runner/work/external-secrets/external-secrets/cmd/root.go:221\nmain.main\n\t/home/runner/work/external-secrets/external-secrets/main.go:21\nruntime.main\n\t/opt/hostedtoolcache/go/1.19.7/x64/src/runtime/proc.go:250"}

The versions of the tools and applications are as follows:
Argo CD v2.6.7
Go Version go1.18.10
kustomize v4.5.7
Helm v3.10.3
kubectl v0.24.2
K8s Rev: v1.21.5+k3s2
Additionally, this issue may be related to the following issues:
https://github.com/external-secrets/external-secrets/issues/997
https://github.com/external-secrets/external-secrets/issues/1026
Other information:
I have found two methods to address this issue:

Change the Namespace to default
external-secrets

Use Helm directly in ArgoCD instead of Kustomization

Relevant part in application.yaml
https://github.com/honahuku/manifest/blob/519a7edac82545248f86d6e1f06e2bad70753a3d/root/application.yaml#L163-L203
However, with the second method, there is an issue where the SecretStore cannot be deployed in the same Application as external-secrets. To address this, I created a new Application called config and deployed the SecretStore there. But I feel this is not the best solution.
On the other hand, the first method has the problem of not being able to use a custom Namespace. Is there any better solution available?

Hi @honahuku ! your kustomization that you posted is also using helmCharts. Is this intended?
I do not see why this issue would be happening. You should be possible to just have a kustomization layer on top of our manifests to change the namespaces appropriately.

However, with the second method, there is an issue where the SecretStore cannot be deployed in the same Application as external-secrets. To address this, I created a new Application called config and deployed the SecretStore there. But I feel this is not the best solution.

This issue is inherent with helm charts, since we template our CRDs to inject the webhook configuration. If you're not running on v1alpha1 resources, what you can do simply is add these flags:
--set webhook.create=false
--set certController.create=false
--set crd.conversion.enabled=false

Thanks for the suggested solution!
I'm currently working on it, so please bear with me for a bit.

Hello, @gusfcarvalho!
I understand that you intentionally included helmCharts in your kustomize.
To make the situation clearer, please take a look at the diff between these two commits:
before-applying-webhook-disabling...after-applying-webhook-disabling
The only change I made here is adding the values to disable the creation of the webhook, as you suggested.
In the commit tagged before-applying-webhook-disabling, an error occurs in external-secrets-webhook, and external-secrets cannot be used, as I mentioned before.
In the commit tagged after-applying-webhook-disabling, external-secrets-webhook is disabled, so no error occurs and it can be used.
I was able to resolve the issue using your suggested method. However, I'm still curious why disabling the external-secrets-webhook makes it work, and whether the external-secrets-webhook itself doesn't cause any problems with the functioning of external-secrets.
Additionally, if it's okay with you, I'd like to add documentation on how to use external-secrets with a combination of ArgoCD and kustomize. May I send a pull request?

I'm having exactly the same issue.
Isn't disabling ValidatingWebhookConfiguration an undesirable thing? Can this compromise be addressed somehow in a helm template?

Just setting the namespace on all resources is not enough, you'll also need to set some cli args like here:
https://github.com/external-secrets/external-secrets/blob/main/deploy/charts/external-secrets/templates/cert-controller-deployment.yaml#L54
There's probably more, just as a hint

I have the same issue, super frustrating. Any luck?

hi @yehoshuadimarsky. Did the workarounds stated above not work for your use case?

@gusfcarvalho, which complete set of workarounds would you currently recommend based on the complete history of this discussion?
Still https://github.com/external-secrets/external-secrets/issues/2273#issuecomment-1529141991 alone, or something else?

you need to specify the namespace for the helm generator as well because the non-kubernetes settings:
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: custom-ns
helmCharts:
  - name: external-secrets
    repo: https://charts.external-secrets.io/
    version: 0.9.13
    releaseName: external-secrets-operator
    namespace: custom-ns
    includeCRDs: true

the above deployed ok for me


Add GitHub actions to run tests on multiple lisp implementations

Using the clfoundation lisp Docker images, add GitHub actions scripts to run the FiveAM tests. Hoping this will lead to better development.

The history of this pull request is a hot mess because of my need to debug on GitHub itself. So I argue that this should definitely be merged but it must be squash-merged.

Couldn't you squash it from your side?

Couldn't you squash it from your side?

I could, but GitHub would do it for us. And since I can't actually merge it, it doesn't seem worth the trouble.

Not much trouble here, just use git rebase -i e11dee752a8f59065033ef9d60641d4a2f1e8379 from branch github-actions, then replace the first pick with reword and all other pick with fixup, then enter your new commit message, then git commit --amend -C HEAD --reset-author to reset the commit to the current date, then force push to github. :)

@rpgoldman I don't care what Github can do. I want to see a single clean commit.

Ok, I’ll do the rebase then. I’ll get it done in the next hour
--
Robert P. Goldman
On August 5, 2023 at 20:46:45, Stelian Ionescu @.@.)) wrote:

@rpgoldman(https://github.com/rpgoldman) I don't care what Github can do. I want to see a single clean commit.
—
Reply to this email directly, view it on GitHub(https://github.com/lispci/fiveam/pull/93#issuecomment-1666672772), or unsubscribe(https://github.com/notifications/unsubscribe-auth/AAAAZSW5EXTPGYRUAM54U23XT3ZQLANCNFSM6AAAAAATCGMSV4).
You are receiving this because you were mentioned.Message ID: @.***>

OK, it's done.

Testing a merge on my fork, I get this odd error testing on Allegro. This seems to be some weird runner issue, not an issue with anything CL.  Anyone seen this before? Any idea what it means?
A little poking around suggests that maybe this is an issue with the Docker image, but I can't say for sure.

On second thought, git reset --soft e11dee752a8f59065033ef9d60641d4a2f1e8379 then git commit -a would have been much simpler. 😅

OK, this seems to have fixed things. No idea why this went wrong, but this should be good to merge now.

Now that this is squashed, could it be merged, please?

I think this is ready to go now.  Thanks for the improvements.

Looks good. I'll merge it as-is to see how it goes.
One major improvement would be to open an issue with the maintainer of the Docker image and ask to include a QL setup, that would allow users to avoid the boilerplate of build.lisp and test.lisp.


0.0.18-alpha.4 can't add components anymore

I updated to VideoKit 0.0.18-alpha.4 and for some reason after restarting the editor, my scripts were not attached to a gameobject anymore. I also was not able to find them again when adding a new component. Even though, I can use the components as usual via script.

I re-added the videokit package some times. Now I'm able to add the component again from the Unity editor! 💯


[BUG] Azure.Storage.Queues SDK fails with custom hostname in the connection string

Describe the bug
The Url used by the library ends up being http://azurite:10001/queuename instead of http://azurite:10001/devstoreaccount1/queuename
It's a problem analogous to the one described here https://github.com/Azure/azure-sdk-for-net/issues/9404. It was already fixed for the blobs but not for the queues.
Expected behavior
Correctly interpret connection string when using custom host name.
Actual behavior (include Exception or Stack Trace)
{System.Xml.XmlException: Root element is missing.
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   at System.Xml.XmlTextReaderImpl.Read()
   at System.Xml.Linq.XDocument.Load(XmlReader reader, LoadOptions options)
   at System.Xml.Linq.XDocument.Load(Stream stream, LoadOptions options)
   at Azure.Storage.Queues.QueueRestClient.Messages.DequeueAsync_CreateResponse(ClientDiagnostics clientDiagnostics, Response response)
   at Azure.Storage.Queues.QueueRestClient.Messages.DequeueAsync(ClientDiagnostics clientDiagnostics, HttpPipeline pipeline, Uri resourceUri, String version, Nullable`1 numberOfMessages, Nullable`1 visibilitytimeout, Nullable`1 timeout, String requestId, Boolean async, String operationName, CancellationToken cancellationToken)
   at Azure.Storage.Queues.QueueClient.ReceiveMessagesInternal(Nullable`1 maxMessages, Nullable`1 visibilityTimeout, Boolean async, CancellationToken cancellationToken)
   at Azure.Storage.Queues.QueueClient.ReceiveMessagesAsync(Nullable`1 maxMessages, Nullable`1 visibilityTimeout, CancellationToken cancellationToken)

To Reproduce
var connectionString = "UseDevelopmentStorage=true;DevelopmentStorageProxyUri=http://azurite/;"
var queueClient = new QueueClient(connectionString, queueName);
queueClient.CreateIfNotExists();

Environment:
Azure.Storage.Queues 12.4.2
.NET Core 3.1

Thank you for your feedback.  Tagging and routing to the team best able to assist.

Hi,
Thanks for bringing up this issue. You're correct looks like the PR fixed it for blobs, but not for queues or files.
We will look to reference this PR https://github.com/Azure/azure-sdk-for-net/pull/13124 for the fix.
I will label this issue as a bug and we will look to getting this in when we can.

Just got here because of that PR #13124 as well, we're running Azurite inside a Kubernetes cluster on our dev machines on a different port (9100), which causes the same problem, not finding container references for blobs as the BlobUriBuilder is not able to find the AccountName in the uri.
Of course, we can fix our local situation by using one of the ports listed in the range mentioned at https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/storage/Azure.Storage.Blobs/src/BlobUriBuilder.cs#L41 , but perhaps another solution could be found as well, for example if the AccountName was set before, to attempt to find the AccountName in the Uri during parsing?

@wcabus will look into including ports that are different from the currently listed port. Could you create a new issue about this port issue as this is separate bug from this bug? Thanks.


Integration with Github Codespaces

The Problem
Setting up local dev env is time consuming and not everyone's pc meet minimum system requirements for setup.
The Solution
That's where Github Codespaces comes into picture and helps us in configuring project on cloud without need of installing anything on local pc.
It would be helpful for users of Swirl to easily setup dev env without any hustle(Without even entering single command to run).

This has been merged...closing the Issue.  Thanks @s-vamshi !


version: 1.13  When the window is maximized, click Restore cannot display the correct size

Environment

OS: win10 64
scrcpy version: 1.13
installation method: [e.g. manual build, apt, snap, brew, Windows release...]
device model:
Android version: 7.0

Describe the bug
When the window is maximized, click Restore cannot display the correct size

What is your expected correct size? What is the size you get?
You specified version 1.13 in the title: is the behavior different from v1.12?

Same issue
My original size 1280x720 then change the size to 800x600. If I did maximize then restore down or fullscreen then unfullscreen its back to original size 1280x720.
1.12 doent have this issue, while 1.13 does.

Thank you for your report.
Fixed by ead7ee4a03c9533ea7bb992a9c2df6ec757fd1f0.
Here is a build for Windows so that you can test (replace in your scrcpy v1.13 directory):

scrcpy.exe
SHA256: 3e64189d03fa26f920d31e002d3d6b751ed495ef46319dce45be3e3b2d46f28a
scrcpy-server
SHA256: 84707914eab0a0e47f1532ee585a95ac29b5368951e7b0362610f9949bf3e685

@rom1v When replacing those files, Windows warns about opening scrcpy.exe, and when trying to run  scrcpy-noconsole.exe , it doesn't do anything.
Any way to call scrcpy.exe without console, instead of using scrcpy-noconsole.exe?
:(

When replacing those files, Windows warns about opening scrcpy.exe

Which warnings?

Any way to call scrcpy.exe without console, instead of using scrcpy-noconsole.exe?

The "no console" thing is Windows specific, and changes the way the binary is linked:
https://github.com/Genymobile/scrcpy/blob/82446b6b0db284e9f9a125cd3e4785586f6845f3/app/meson.build#L135-L139
So it cannot be switched by a command-line argument.

I closed the warning. It's the normal warning of running an EXE file. Here, I replaced and launched it again:

I don't remember it appeared last time I extracted and launched the tool. Odd.
As for no-console, too bad. No workaround then?

 Just click "Run anyway".

Sure. No reason to stop trusting the same one that I used before :)

scrcpy.exe
SHA256: 3e64189d03fa26f920d31e002d3d6b751ed495ef46319dce45be3e3b2d46f28a
scrcpy-server
SHA256: 84707914eab0a0e47f1532ee585a95ac29b5368951e7b0362610f9949bf3e685
I couldn't reproduce the error. Thank you!


Prefix cache is not evicted before OOM

I found it while working on mistralrs-bench.
I could only run concurrency=5, n=128 after disabling prefix cache fully in commit https://github.com/EricLBuehler/mistral.rs/pull/166/commits/c1efae080ccdac6bd7c0cc83a00f38ac50995a23

This problem may have been linked to the now-nonexistant bug in #165 because the prefix cache is only updated after the sequence is finished.


Don't fail due to missing versions in check mode.

Description
In check mode, the following failures would occur:
Set RKE2 version:
{{ versions_check.stdout | from_json }}'. Error was a <class 'json.decoder.JSONDecodeError'>, original message: Expecting value: line 1 column 1 (char 0)"}
Run AirGap RKE2 script:
The conditional check 'rke2_version != installed_version and rke2_airgap_mode' failed.
Run RKE2 script:
error while evaluating conditional (rke2_version != installed_version and not rke2_airgap_mode): 'installed_version' is undefined.
Skip those tasks in check mode.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Small minor change not affecting the Ansible Role code (GitHub Actions Workflow, Documentation etc.)

How Has This Been Tested?
Applied the role locally again with --check and no failures this time.

I'm hitting this error when running in check mode:
fatal: [node-01]: FAILED! => {"msg": "An unhandled exception occurred while templating '{{ versions_check.stdout | from_json }}'. Error was a <class 'json.decoder.JSONDecodeError'>, original message: Expecting value: line 1 column 1 (char 0)"}

Could you please merge this?


Cannot read property 'params' of undefined

<template>

            <LeftSide/>

Товары

{{good.brend}}

{{good.description}}

                <GoodsGrid/>

</template>

I try to get element of array goods, And substitute its values depending on the id (dynamically)

Hi @Jussiadev,

params is not available in data, you should use this.$route.params.id.
you should use find instead of filter for goods.

@alexchopin
return {                 good: goods.find((good) => String(good.id) === this.$route.params.id)             }
It still does not work

Can you provide us a repo to help you?

@alexchopin Everything worked here. But the issue #1463  still does not work. I tried the proposed changes, but it did not help.

Same issue here. Using the this.$route.params.id in created and works if the developer toolbar is open with disable cache. When i don't disable cache, the error consists: Cannot read property 'value' of undefined


🪡 Fix example hook

The useTokenBalance() hook in the website's example code references a deprecated hook, useContractCall():
function useTokenBalance(
	tokenAddress: string|Falsy,
	address: string|Falsy): BigNumber|undefined
{
	const [tokenBalance] = useContractCall (
		address && tokenAddress && {
			abi: ERC20Interface, // ABI interface of the called contract
			address: tokenAddress, // On-chain address of the deployed contract
			method: "balanceOf", // Method to be called
			args: [address], // Method arguments - address to be checked for balance
			}
		) ?? [ ];

	return tokenBalance;

}

https://github.com/TrueFiEng/useDApp/blob/master/packages/website/src/index.html#L336
This call yields a deprecation warning in editors like VS Code:

This PR updates the useTokenBalance() implementation to instead call useCall(), following the hook's @example code as closely as possible:
function useTokenBalance(
	tokenAddress: string|Falsy,
	address: string|Falsy): BigNumber|undefined
{
	const { value, error } = useCall(
		address && tokenAddress && {
			contract: new Contract(tokenAddress, ERC20Interface), // Contract instance
			method: "balanceOf", // Method to be called
			args: [address], // Method arguments - address to be checked for balance
			}
		) ?? {};

	if(error) {
		console.error(error.message)
		return undefined
	}

	const { balance } = value || {}

	return balance

}

Screenshot of the updated page example running on localhost:

@MichaelZalla Thanks! I simplified the example code a little bit.


Drop 0.10 environment from .travis.yml

https://github.com/moment/moment/pull/3545#issuecomment-258198233
Node 0.10 is dead. Long live Node!

Merged in 78737433d64c912117649ef101f5792f425ee46f


Congressional districts sourcing from local file

Inline comment explains
      # For some reason the zip file for 21b is not working right, so we are doing a local archive this time
But 21d from online open data works, so implement the normal process of downloading from the web

This was resolved in pull request #195


Small icon is not visible in status bar on API 30+ when MediaStyle is set in notification

Media3 Version
Media3 1.0.1
Devices that reproduce the issue
Pixel 5 v12.0 no icon
Galaxy S22 v12.0 no icon
Galaxy S21 v11.0 no icon
Moto G71 5G v11.0 no icon
Galaxy S20 v10.0 icon visible
Moto G9 Play v10.0 icon visible
Devices that do not reproduce the issue
No response
Reproducible in the demo app?
Yes
Reproduction steps
The issue can be reproduced in UAMP: Android Media Player (branch media3 and main)
I found the reason during a long time of debugging.
Let's reproduce with UAMP media3 branch. For displaying notifications is used DefaultMediaNotificationProvider
If I comment this line DefaultMediaNotificationProvider.java#L370 icon will be visible in status bar.
Note: the issue is old. Before migrating to media3 the same was in PlayerNotificationManager  when mediaSession is set to MediaStyle PlayerNotificationManager.java#L1246 If comment this line icon becomes visible.
Expected result
Icon should be visible

Actual result
Icon is not visible in API 30+

Media
N/A
Bug Report

[ ] You will email the zip file produced by adb bugreport to<EMAIL_ADDRESS>after filing this issue.

Starting with Android 11/API 11 a mini player with media controls is created for each media style notification and the icon isn't displayed in the status bar for such notification. Instead media notifications are placed in a carousel. Please find the blog post that announced that change that says: The small icon and app name are shown in the upper left of the media controls.
https://android-developers.googleblog.com/2020/08/playing-nicely-with-media-controls.html

Closing as this is answered and there was no further activity.


Zoom is not working anymore

Example code
import numpy as np
from bqplot import pyplot as plt

plt.figure(1, title='Line Chart')
np.random.seed(0)
n = 200
x = np.linspace(0.0, 10.0, n)
y = np.cumsum(np.random.randn(n))
plt.plot(x, y)
plt.show()

Now clicking the panzoom button, we don't have a working zoom anymore.
This was originally reported downstream at https://github.com/spacetelescope/jdaviz/issues/486 and the upstream issue
at https://github.com/d3/d3-zoom/issues/231
This affects Chrome 89.0.4389.90 (OSX), and is demonstrated by zoom not working at: https://observablehq.com/@philjones/zoom-svg-chrome-89-0-4389-90-bug

Weirdly, after upgrading Chrome (still reporting the same version!) https://observablehq.com/@philjones/zoom-svg-chrome-89-0-4389-90-bug works 🤷

@sntgluca does https://observablehq.com/@philjones/zoom-svg-chrome-89-0-4389-90-bug work for you?

@maartenbreddels ,
interesting.
With the link above I can zoom correctly with

Chrome Version 90.0.4430.93 (Official Build) (x86_64)
Edge Version 90.0.818.42 (Official build) (64-bit)
while it doesn't work with Safari Version 14.1 (156<IP_ADDRESS>.5, 15611)

With a Jupyter notebook I can zoom correctly with Edge and it doesn't work with either Chrome or Safari.

The link works for me on Firefox 88 (64 bit)

Hmm. Maybe this is also why I cannot zoom over at spacetelescope/jdaviz#564 ?

@pllim yes, I linked to https://github.com/spacetelescope/jdaviz/issues/486 so i guess those are duplicates.


prepare release v1.14.1

What type of PR is this?
prepared release for v1.14.1

We do not support manual releases anymore.
/close


Improve the document cache miss error message

Helps folks get a bit more insight into what's going on when this error is thrown:

Thanks for this! Added to the pinned roadmap
In most cases this log message doesn't need to be reported at all.
For example, this error is shown when files are parsed but no documents are found, for example on save.  this is very common for .js/ts/etc files without graphql`` tags.
However, a more relevant message is clipped at the top, which indicates an error from graphql-config. This and other graphql-config error messages we should show in debug output, so that users can debug with graphql-config maintainers more easily.
The frequency of the message is a symptom of other issues with over-parsing that we need to ameliorate.
Again, thanks a bunch for this! This is a good step in the right direction for error logging in the LSP server

@orta can you add a changeset?

So these messages are a great improvement to be sure, but instead of throwing an error, we can do this:
if (!cachedDocument) {
 	this.logger.debug(this._errorMessageForMissingDocument(textDocument.uri));
 	return
}

Yeah, agree, we should remove the error messages realistically because they're just not that useful

This was another one of those situations where I couldn’t understand why it was there in the first place. Previously almost nothing went to the output panel and all logging went to file, but I exposed some to output panel, and the logging to file is yet another thing to question, another artefact of the pre-LSP era of this server

@orta beautiful, thank you!


Move data type checking against paramtype of ParamSpec into DataSet

It seems more logical that DataSet's register_parameter method takes care of type validation of the data against its ParamSpec, because ParamSpec is on the same level as DataSet. Currently, the logic is in DataSaver, hence its scope is now to large. DataSaver should only know how to interface between qcodes parameters (there are many different classes) and DataSet, but not go deep into type checking, etc.

While I agree that there is too much going on in the DataSaver (we are working on refactoring some of that into InterDependencies in #1227), I can't really see any alternative when it comes to validating the type of the data as it is being saved. Am I missing your point?

You're right, but the data is actually saved in DataSet, not in DataSaver. DataSaver's role is to interface between qcodes parameters world and DataSet, right? Hence DataSaver just unwraps Parameters, ArrayParameters, etc. and passes values to DataSet. And since only DataSet knows about ParamSpecs of the parameters, the type checking of values against types in ParamSpec belongs to DataSet. This is my point.

Thanks for clarifying. So although the datasaver must command when the validation is done, the code that knows how to validate (and thus actually performs the validation) belongs somewhere else. Is that it? If so, wouldn't it then seem appropriate to make the ParamSpecs have associated validators? (I'm not saying that the ParamSpecs are parameters, but they are parameters)

closing as outdated, and not really relevant anymore.


Crash

XCGLogger.BaseDestination.process(logDetails: XCGLogger.LogDetails) -> () :0
XCGLogger
protocol witness for XCGLogger.DestinationProtocol.process(logDetails: XCGLogger.LogDetails) -> () in conformance XCGLogger.BaseDestination : XCGLogger.DestinationProtocol in XCGLogger :0
XCGLogger
XCGLogger.XCGLogger.logln(: XCGLogger.XCGLogger.Level, functionName: Swift.String, fileName: Swift.String, lineNumber: Swift.Int, userInfo: [Swift.String : Any], closure: () -> Any?) -> () XCGLogger.swift:347
XCGLogger
XCGLogger.XCGLogger.logln(: XCGLogger.XCGLogger.Level, functionName: Swift.StaticString, fileName: Swift.StaticString, lineNumber: Swift.Int, userInfo: [Swift.String : Any], closure: () -> Any?) -> () XCGLogger.swift:325
XCGLogger
merged XCGLogger.XCGLogger.verbose(: @autoclosure () -> Any?, functionName: Swift.StaticString, fileName: Swift.StaticString, lineNumber: Swift.Int, userInfo: [Swift.String : Any]) -> ()
XCGLogger
XCGLogger.XCGLogger.info(: @autoclosure () -> Any?, functionName: Swift.StaticString, fileName: Swift.StaticString, lineNumber: Swift.Int, userInfo: [Swift.String : Any]) -> ()
XCGLogger version: 6.1.0

Hello,
recently facing this crash, please have a look on this:
XCGLogger version: 6.1.0

Do we haver any update on this ? Is it still to be triaged ?


#ref in additional properties

Hi. I try to make a template for asciidoc (asciidoctor, in fact). With test examples everythin is great. But I faced the following problem.
Here is the part of specification:
    ModelMetaData:
      required:
        - members
        - attributes
      properties:
        members:
          description:
            Meta data for members
          additionalProperties: # key - memberId
            $ref: '#/components/schemas/MemberMetaData'
        attributes:
          description:
            Meta data for attributes
          additionalProperties: # key - attributeId
            $ref: '#/components/schemas/AttributeMetaData'

    MemberMetaData:
      required:
        - text
      properties:
        text:
          description:
            id of the member as a text
          type: string
        aggregateText:
          description:
            aggregate of the member as a text
          type: string
        formulaeText:
          description:
            formulae of the member as a text
          type: string

    AttributeMetaData:
      required:
        - text
      properties:
        text:
          description:
            id of the attribute as a text
          type: string

In the resulting table I get summaryAsHTML, descriptionAsHTML and generatedExample as extra rows and get empty descriptions.

The same problem is with Markdown template.
Here is the template code, that iterates through properties:
{{#each prop.additionalProperties.properties}}
{{> schemaProp prop=. propName=@key required=(isRequired ../prop.additionalProperties @key) path=(buildPath ../propName ../path @key)}}
{{/each}}

If the problem can be fixed in a template, just give a hint, I'll make PR for Markdown and if you don't mind I can make PR for asciidoc template.

Probably, solved this in #28

Fixed in #28.


Refactoring command into main block

I decide to put the command line argument part into the main block. This will allow other module to "import linkfinder" for further use.
I remove these lines because I notice that jsbeautifier is required for this module anyway.
# Newlines in regex? Important for CLI output without jsbeautifier
if args.output != 'cli':
    addition = ("[^\n]*","[^\n]*")
else:
    addition = ("","")

Also I don't really understand this part but I don't think output argument should alter input content so I remove this if args.output != 'cli':. If it is necessary by any mean, I will add it back.
def parser_file(content, regex, more_regex=None):
...
    # Beautify
    if args.output != 'cli': # <-- I don't know what this line does
        if len(content) > 1000000:
            content = content.replace(";",";\r\n").replace(",",",\r\n")
        else:
            content = jsbeautifier.beautify(content)

Also I try to remove global argument dependency. Accepting as function parameter will make the project easier to maintain and allow other code to import. I haven't done fixing this yet. I rush to fix parser_file function first so I could add unit-test into this project.
Any suggestion/change/opinion is appreciated.
Also since I did change a lot of lines, (even I have tested on my part, it's might not be covered), further test is also appreciated.

This is very useful. I'll look at this in more detail tomorrow, but for now a big THANK YOU 😄

The reason I set up CLI like that with the addition = ("[^\n]*","[^\n]*") is because if CLI output is enabled we don't use jsbeautifier.beautify(content) and thus the newlines have to be added in order to make sure that the regular expression is evaluated over every new line. Else it would just find 1 URL in a very big line.

Rest LGTM. I you could add that support back or refactor it a little bit that would be perfect and I'd happily merge the pull

The reason why
if args.output != 'cli':
    addition = ("[^\n]*","[^\n]*")

Is there is because if we use CLI we don't care about the context of where the URL is in. Meaning we just want the URL without surrounding code. Because of this we dont need to beautify the code or explode based on ,;. This also makes LinkFinder a lot quicker and is why we can't remove these if statements. Yes if we remove them it would still work. But the program would be a lot slower in CLI mode.
Rest LGTM.

I think I understand that now.
Will see how can I refactor it tmr.
Thank for a review.

@GerbenJavado Could you take a look again ?

I have wrapped the "surrounding code" regex into function mode "with context" and "without context".
I still leave output to cli default to "without context" and html default to "with context" as it is. We could add the option to switch mode later.

I haven't refactor'ed the whole module, only focus on regex parser right now so anyone else could easily run the test and improve the regex and able to call the function externally. Tell me if there is any function/code that need to be focused. I will look more into it.

For some reason:
python linkfinder.py -i https://www.nu.nl/ -o cli -d

is broken. I'll look into this soon.

Hmm a very "hacky" test shows this fixes it. Do you know a better solution?
if mode == 0:
                    endpoint = cgi.escape(endpoint[0]).encode('ascii', 'ignore').decode('utf8')
                else:
                    endpoint = cgi.escape(endpoint[1]).encode('ascii', 'ignore').decode('utf8')

No @Bankde looks quite solid already. Also modifying someone else's code is never easy. Im already very happy with these changes.

Should work now.
The computing time is pretty much same as previous regex.
By the way, I have removed this line
189    group = list(filter(None, item))
I guess that it's to copy the list. However, I see that the list is not shared with any other function so copying might not be needed. I might have missed something tho.

As far as I know I implemented list(filter(None, item)) to prevent exact duplicates. Would removing this remove this feature?

I think the line that remove duplicate was this one
items = list(set(items))
which I have replaced with this one
items = {item['link']:item for item in items}.values()
I also add test to check that no duplicate value is returned.
Note that I could only test cli. Testing html result will be bigger work here.

Thanks for your awesome work!


Unified fields and attributes; simplified DB nullability

Attributes are now fields with a hidden attribute.
There is no longer an attribute specific notion of path and all the logic which handled attribute vs. field paths has been eliminated.
Moved all DB nullability info onto the per-column Codecs which are now the sole source of field-mapping level nullability via ColumnRef.
Moved TableDef into the API, as part of DoobieMapping/SkunkMapping. Tests updated to use this style.

Moved TableDef into the API, as part of DoobieMapping/SkunkMapping.

I see this in DoobieMapping but not in SkunkMapping. Lost commit maybe?


Security scan of cypress/included:latest have significant vulnerability findings

Hey,
I'm using the builded image of cypress/included:latest to run our tests in CI/CD pipelines. To save traffic, we are having our own container registry and moving multiple images from dockerhub to our own registry. In this process we are also scanning these images for known security vulnerabilities with trivy.
This process is finding a lot of outdated versions and security issues in that image.
To reconstruct the security scanning, here are the commands:
# create a local copy of the image
docker pull cypress/included:latest

# start the scanner
trivy image cypress/included:latest

Output:
cypress/included:latest (debian 12.5)

Total: 287 (UNKNOWN: 0, LOW: 176, MEDIUM: 67, HIGH: 41, CRITICAL: 3)

[...] <long table with all found vulnerabilities/>

Node.js (node-pkg)

Total: 45 (UNKNOWN: 0, LOW: 3, MEDIUM: 19, HIGH: 19, CRITICAL: 4)

[...] <another long table with all found vulnerabilities/>

Suggestion

update the base image before hand with the debian package manager
update the dependencies of package.json during the building process
add trivy in the building process pipeline as a github action

@sebb-m0
Could you run your trivy scan again with the --ignore-unfixed option? Cypress Docker images depend on upstream Debian and Cypress for their contents. It's not possible to fix security vulnerabilities which have not been fixed upstream.

Hey Mike,
you're right. This makes this a bit more organized:
trivy image cypress/included:latest --ignore-unfixed

cypress/included:latest (debian 12.5)
Total: 0 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 0)

Node.js (node-pkg)
Total: 45 (UNKNOWN: 0, LOW: 3, MEDIUM: 19, HIGH: 19, CRITICAL: 4)

then only the package.json dependencies needs to be updated.

@sebb-m0
Thank you for confirming that you don't see any fixable issues in Debian! The latest cypress/factory:4.0.2 image was built just a few days ago and since the build process pulls up-to-date Debian packages, this means that all possible fixes are already included. cypress/included uses cypress/factory when it itself is built.
Regarding the remaining issues, running the following:
trivy image --ignore-unfixed cypress/included:13.11.0 --format json | grep PkgPath

shows that each of the reported vulnerabilities comes from a package.json which is bundled with the Cypress binary in root/.cache/Cypress/13.11.0/Cypress/resources/app/node_modules/
These are not vulnerabilities which can be fixed directly by cypress/included Docker images. Any fixes would need to come from the upstream repo https://github.com/cypress-io/cypress. The Cypress binary is installed as-provided and it is not manipulated by the Cypress Docker image process.

Thanks for pointing this out. Then I'll go to the cypress-io/cypress project with that issue. I already checked out the current develop branch and start trivy locally and see a similar behavior.
yarn.lock (yarn)
Total: 35 (UNKNOWN: 0, LOW: 2, MEDIUM: 14, HIGH: 15, CRITICAL: 4)

@sebb-m0
I have added comments into the Cypress repo for the 4 critical vulnerabilities.
The following will filter these for a report:
trivy image --ignore-unfixed --vuln-type library --severity CRITICAL cypress/included:13.11.0


dat -> hyperdrive converter fails on Windows with Error: /C: could not be found

Describe the bug
When using the dat -> hyperdrive converter in Beaker on Windows (doesn't happen on Linux with the same Dat archives), the files listing is shown as empty and after clicking the "convert" button, it creates a new hyperdrive but the only file is a index.json with empty curly brackets inside, no other files are created. When starting Beaker from PowerShell, it shows the error Error: /C: could not be found after clicking on the "convert" button.
To Reproduce
Steps to reproduce the behavior:

Open Beaker
Scroll down to the legacy Dat to hyperdrive converter section on the New Tab page
Click on any of the archives
Click on convert button
Mostly empty hyperdrive opens, error in console: Error: /C: could not be found

Expected behavior
A new hyperdive is created with all the files from the old Dat archive inside.
Desktop (please complete the following information):

OS: Windows 10
Beaker Browser 1.0 pre-release

Additional context
The full error shown in the console after clicking the "convert" button on a legacy Dat archive:
(node:19660) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(node:19660) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
Sparse-file support not detected. Falling back to indexed data files.
(node:19660) UnhandledPromiseRejectionWarning: Error: /C: could not be found
    at notFound (C:\Users\serio\AppData\Local\Programs\beaker-browser\resources\app\bg\dat\converter\node_modules\append-tree\index.js:683:13)
    at onnodes (C:\Users\serio\AppData\Local\Programs\beaker-browser\resources\app\bg\dat\converter\node_modules\append-tree\index.js:116:36)
    at onget (C:\Users\serio\AppData\Local\Programs\beaker-browser\resources\app\bg\dat\converter\node_modules\append-tree\index.js:358:21)
    at processTicksAndRejections (internal/process/task_queues.js:82:21)
(node:19660) UnhandledPromiseRejectionWarning: Error: /C: could not be found
    at notFound (C:\Users\serio\AppData\Local\Programs\beaker-browser\resources\app\bg\dat\converter\node_modules\append-tree\index.js:683:13)
    at onnodes (C:\Users\serio\AppData\Local\Programs\beaker-browser\resources\app\bg\dat\converter\node_modules\append-tree\index.js:116:36)
    at onget (C:\Users\serio\AppData\Local\Programs\beaker-browser\resources\app\bg\dat\converter\node_modules\append-tree\index.js:358:21)
    at processTicksAndRejections (internal/process/task_queues.js:82:21)
(node:19660) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:19660) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:19660) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:19660) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Interesting! Thanks for filing, I'll check into this.

@pfrazee I'm afraid in 1.0.0-prerelease.2 the issue is still there, but the error message changed to a missing module, maybe it didn't get packaged with the installer or the path is wrong:
internal/modules/cjs/loader.js:800
    throw err;
    ^

Error: Cannot find module<EMAIL_ADDRESS>Require stack:
- C:\Users\serio\AppData\Local\Programs\beaker-browser\resources\app\bg\dat\converter\index.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:797:17)
    at Module._load (internal/modules/cjs/loader.js:690:27)
    at Module._load (electron/js2c/asar.js:738:28)
    at Function.Module._load (electron/js2c/asar.js:738:28)
    at Module.require (internal/modules/cjs/loader.js:852:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (C:\Users\serio\AppData\Local\Programs\beaker-browser\resources\app\bg\dat\converter\index.js:1:1)
    at Module._compile (internal/modules/cjs/loader.js:967:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1004:10)
    at Module.load (internal/modules/cjs/loader.js:815:32) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    'C:\\Users\\serio\\AppData\\Local\\Programs\\beaker-browser\\resources\\app\\bg\\dat\\converter\\index.js'
  ]
}

Ohhh what a bummer. I must have biffed the packaging on Windows, and I only tested the dat converter on mac. So sorry. On my TODOs.


Postgres - the operator ? is installed as ??

Environment
Liquibase Version:   4.2.2 #36
Liquibase Integration & Version:  CLI
Liquibase Extension(s) & Version:   n/a
Database Vendor & Version:    postgres 13  (docker postgres-13-alpine)
Operating System Type & Version:   windows 10 64-bit
Description
We deploy our postgres databases using the sqlfile tag in the changeset, and the update operation.   I recently wrote a function which tested some jsonb data using the ? operator.
.... WHERE f.filter_object::JSONB ? 'patient_status';
After using liquibase to update the database with this new function, the function failed to work, and when I examined the function source using pgAdmin (or any tool), the ? operator had become ?? , e.g.
    WHERE f.filter_object::JSONB ?? 'patient_status';
which is not valid.
Steps To Reproduce
List the steps to reproduce the behavior.

create a folder called functions and a file called this_key_exists.sql with the following content:

create or replace function this_key_exists ( doc jsonb, keyname text  )
   returns boolean
   language plpgsql
as
$$
begin
   return ( doc ? keyname  );
end;
$$;

/*
select this_key_exists ('{"id":1, "this_value":2}', 'id');
*/

create a folder called deployment, with a single file, masterchangelog.xml, with these contents:

<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
  xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog
                      http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.8.xsd">
    <includeAll path="changelogs" relativeToChangelogFile="true"/>
</databaseChangeLog>

create a folder under that called changelogs
in the changelogs, folder create a file, changelog_functions.xml, with these contents:

<?xml version="1.0" encoding="utf-8"?>
<databaseChangeLog xmlns="http://www.liquibase.org/xml/ns/dbchangelog" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.8.xsd">
  <changeSet author="cameron" id="public.this_key_exists" runOnChange="true">
    <sqlFile dbms="postgresql" endDelimiter=";" path="../../functions/this_key_exists.sql" relativeToChangelogFile="true" splitStatements="false" stripComments="false" />
  </changeSet>
</databaseChangeLog>

For simplicty, we'll install this function in the default postgres database.

  liquibase --changeLogFile=./deployment/masterchangelog.xml  --username=postgres --password=_admin password_  --driver=org.postgresql.Driver --classpath=_path_to_jar_\postgresql-42.2.18.jar --url="jdbc:postgresql://localhost:5432/postgres"  update

Actual Behavior
The function is installed, but an attempt to invoke it in pgAdmin will result in an error.
Example query:
select this_key_exists ('{"id":1, "this_value":2}', 'id');

ERROR:  operator does not exist: jsonb ?? text
LINE 1: SELECT ( doc ?? keyname  )
^
HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
QUERY:  SELECT ( doc ?? keyname  )
CONTEXT:  PL/pgSQL function this_key_exists(jsonb,text) line 3 at RETURN
SQL state: 42883

Expected/Desired Behavior
No error.  Returns "true" in that example.
Screenshots (if appropriate)
If applicable, add screenshots to help explain your problem.
Additional Context
Someone suggested that the jdbc driver escapes the ? character, making it appear as ??.    This may be related to the problem.

Thanks @RSchoedel for creating this issue.  We will add it to the list of issues to process.

I was interested in this fix and just found that it is fixed with 4.4.3. Tks.

That's great.   Thank you for letting me know.
On Mon, Jul 4, 2022 at 1:58 AM xamuelih @.***> wrote:

I was interested in this fix and just found that it is fixed with 4.4.3.
Tks.
—
Reply to this email directly, view it on GitHub
https://github.com/liquibase/liquibase/issues/1759#issuecomment-1173546732,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHAZOI44FEAJX4KY7AZXWTDVSKRRRANCNFSM4Y7DJN3Q
.
You are receiving this because you were mentioned.Message ID:
@.***>


Reduce the Space between different types of icon section

Empty space between different Icon sections is alot.

Sure @shagunchandra

The space above Action.js is too less on mobile view.

@Abhirup-99 I have fixed this, can you review my PR?


FIXES: tests on 14.1.1 (Sonoma) Apple M1 Max

FIXES: tests on 14.1.1 (Sonoma) Apple M1 Max (Issue #22) by generally introducing a time.sleep(5) for click_menu_item.

Thank you!

My pleasure!


LeaderF starts with Error

vim or neovim?

[x] vim
[ ] neovim

Output of vim --version or nvim --version: VIM - Vi IMproved 9.0
Output of :echo has("python"): 1
Output of :echo has("python3"): 1
Output of :echo &pythondll(only vim, not neovim): libpython2.7.so.1.0
Output of :echo &pythonthreedll(only vim, not neovim): libpython3.6m.so.1.0
Output of :py print(sys.version): 2.7.18 (default, Mar 04 2021, 23:25:57) [GCC]
Output of :py3 print(sys.version): 3.6.15 (default, Sep 23 2021, 15:41:43) [GCC]
Output of :echo g:Lf_Debug_Cmd: pt --nocolor   -g="" "."
Output of :echo g:Lf_FilesFromCache: 1

Operating system:

[x] Linux
[ ] Mac OS X
[ ] Windows
[ ] Etc.

Configurations related to LeaderF in vimrc:
nothing, only install with vim-plug:

Plug 'Yggdroot/LeaderF'
Describe your question, feature request, or bug.
Steps to reproduce

Install Leader F with vim-plug
reload vim and open LeaderF with shortcut
-> Error Loger comes out

Actual behaviour
Expected behaviour

Does pt --nocolor -g="" "." work in your command line?
There is something wrong with your pt command.
Or you can set let g:Lf_DefaultExternalTool = "find".

Thanks for your Tipp and your quick Support!
The command works in my command line.
After setting the Parameter in .vimrc, LeaderF seems to work again
So Thank you :)
Yggdroot @.***> schrieb am Fr. 17. Feb. 2023 um 02:35:

Does pt --nocolor -g="" "." work in your command line?
There is something wrong with your pt command.
Or you can set let g:Lf_DefaultExternalTool = "find".
—
Reply to this email directly, view it on GitHub
https://github.com/Yggdroot/LeaderF/issues/986#issuecomment-1433973471,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI7LPJS3TWNQ6BV5LFGTJJTWX3IVHANCNFSM6AAAAAAU6XDCKQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Does helm operator implement controller

Type of question

General operator-related help

Question
I have upgraded to operator-sdk 1.5.0 from 1.3.0, and I read there was a breaking change in the release notes

Breaking change: PROJECT config version 3-alpha has been upgraded to version 3. (#4613)

After running operator-sdk alpha config-3alpha-to-3, my PROJECT file has this TODO item
 # TODO(user): Uncomment the below line if this resource implements a controller, else delete it.

My operator is a helm based one, so would it be considered as implementing a controller?
What did you do?

What did you expect to see?

What did you see instead? Under which circumstances?

Environment
Operator type:

/language helm
Kubernetes cluster type:

$ operator-sdk version
operator-sdk version: "v1.5.0", commit: "98f30d59ade2d911a7a8c76f0169a7de0dec37a0", kubernetes version: "1.19.4", go version: "go1.15.5", GOOS: "linux", GOARCH: "amd64"
$ go version (if language is Go)

$ kubectl version

Additional context

Just looking for a "yes/no" answer to this, so I can test if my operator upgrades run smoothly

Hi @bitscuit,
You have no controllers. The issue is in the migration tool. You can see in the testdata/helm/memcached-operator/PROJECT an example how it should be.

The bug here is that the alpha config-3alpha-to-3 puts a TODO that is confusing to helm and ansible developers since there is no action for them. The fix for this will be to remove this TODO comment from helm and ansible based configs to avoid the confusion in the future.

Thank you for the explanations!

Closed by #4742


Typo in image filename

The file blunt_end_restriction_enzyme_clevage_site.svg is misspelt and therefore shows a user_defined.svg symbol instead.
File is at knox/src/main/resources/static/img/sbol/blunt_end_restriction_enzyme_clevage_site.svg

Whoops, this might have been my fault, when I was doing the UI I downloaded the svg files from sbolstandard.org, but @nroehner pointed out to me that the internal name used by knox to represent blunt end restriction sites was called blunt_end_restriction_enzyme_clevage_site (the proper full name) and would not match the abbreviated filename used by sbolstandard (blunt_restriction_site.svg), so I renamed the file, incorrectly


Ensure unit and doc tests compile and run.

Previously, running $ cargo test --all would fail with doctest
compilation issues as well as unit test failures. This change ensures
that the doctests compile and the unit test is updated.
The unit test in question (test_table_insertion_with_list) was
failing due to the generated SQL having CAST statements in it - the
assert_eq has been updated.
This change also adds a test make target that will run the rust
tests and ensures that this is run as a part of the PR GHA.

The E2E tests are failing because they relied on some secrets that only get passed to workflows for members of the repo. You've found a bug in our process by being the first external contributor! We'll get this fixed, and I'll go ahead and merge this PR now.


632-devfile annotation support in generators

What does this PR do?:

This PR is for devfile annotation support.
Which issue(s) this PR fixes:
Fixes https://github.com/devfile/api/issues/632
Fixes https://github.com/devfile/api/issues/675
PR acceptance criteria:
Testing and documentation do not need to be complete in order for this PR to be approved. We just need to ensure tracking issues are opened.

Open new test/doc issues under the devfile/api repo
Check each criteria if:
There is a separate tracking issue. Add the issue link under the criteria
or
test/doc updates are made as part of this PR
If unchecked, explain why it's not needed

[x] Unit/Functional tests

[ ] QE Integration test

[ ] Documentation

[ ] Client Impact

How to test changes / Special notes to the reviewer:

We should include some coverage for parent/plugin Annotation overrides in the parse_test.go

@kim-tsao I've pushed a new commit to add annotation field in plugin & parent override tests.

@kadel Can you also help review if this PR addresses Odo's request.

@kadel Can you also help review if this PR addresses Odo's request.

@yangcao77 Testing with odo, I can see that the annotation field is added to v2.0.0 and v2.1.0 devfiles also, for example:
components:
- container:
    annotation: {}
    endpoints:
    - name: http-3000
      targetPort: 3000
    image: registry.access.redhat.com/ubi8/nodejs-14:latest
    memoryLimit: 1024Mi
    mountSources: true
    sourceMapping: /project
  name: runtime
[...]
schemaVersion: 2.0.0

@kadel Can you also help review if this PR addresses Odo's request.

@yangcao77 Testing with odo, I can see that the annotation field is added to v2.0.0 and v2.1.0 devfiles also, for example:
components:
- container:
    annotation: {}
    endpoints:
    - name: http-3000
      targetPort: 3000
    image: registry.access.redhat.com/ubi8/nodejs-14:latest
    memoryLimit: 1024Mi
    mountSources: true
    sourceMapping: /project
  name: runtime
[...]
schemaVersion: 2.0.0

@feloy How did you get this content? you are using devfile writer ? Then this should be a bug.
annotations are not added to devfile v2.0.0 or v2.1.0, and we are not planning to do that.
https://github.com/devfile/api/blob/2.0.x/schemas/latest/devfile.json
https://github.com/devfile/api/blob/2.1.x/schemas/latest/devfile.json

@feloy The annotation problem with writer should be fixed, can you help test again? Thanks.

@feloy The annotation problem with writer should be fixed by the new commit in this PR, can you help test again? Thanks.

@yangcao77 yes, the problem is fixed with this commit, thanks


Cache breaker for spritesheets loaded via JSON

We are having caching issues with updating assets spritesheet. The spritsheet loading is done by adding spritesheet.json to the PIXI loader, which in turn will load the referenced spritesheet.png file. We added cache breaker to all the assets, like spritesheet.json?version=1.2, but there is now way to forward this cache breaker to pixi.
Chrome is aggresively caching the spritesheet.png file because it has the same name. Is there any way we can force the PIXI loader to add a cache breaker for the images loaded as spritesheets?
Currently, the files are loaded in the browser like:
spritesheet.json?version=1.2
spritesheet.png

What it should look like:
spritesheet.json?version=1.2
spritesheet.png?version=1.2

The loader lets you specify
defaultQueryString which automatically lets you perform cache busting for each item it loads. Might be what you need?
https://github.com/englercj/resource-loader

I tried setting PIXI.loader.defaultQueryString but it doesn't seem to do anything.

You probably won't need your own cache busting URLs and the loader doing to too?

Seems to be working now, the only issues is that the cache breaker is not added for sound (.mp3) files.


Staging comms v1 (#301)

This PR introduces the DeepSpeed Comm. Backend (v1).
Co-authored-by: Quentin Anthony<EMAIL_ADDRESS>Co-authored-by: Ammar Ahmad Awan<EMAIL_ADDRESS>Co-authored-by: Jeff Rasley<EMAIL_ADDRESS>

@SeanNaren can you take a look at the lightning test failure? We're seeing this on other PRs and in master right now as well. It appears to be a protobuf issue, have you seen this on your side before?

@jeffra -- This has been tested with HelloDeepSpeed, cifar (ZeRO 1,2,3 and MoE), and a modified Megatron-Deepspeed (changed to use the new DeepSpeed comms API) with the following configurations and results:
https://gist.github.com/Quentin-Anthony/ed2082202b79451a15e946db174b4dbc

@jeffra and @tjruwase -- Any further comments?

Can one of the admins verify this patch?


Newest version size too small

Hello:
I have a simple question, Under ftp site, the file size for ExAC.r0.3.1.sites.vep.vcf.gz only have 45.4MB?, while, it should be at least few GB. but i found file size for ExAC.r0.3.sites.vep.vcf.gz about 3.18 GB. So, something wrong with ExAC.r0.3.1.sites.vep.vcf.gz?
Thanks.

This shows as 4.0GB to me, accessing the FTP site through Chrome. See screenshot:

Note, this was at the following URL:
ftp://ftp.broadinstitute.org/pub/ExAC_release/release0.3.1/


Fix podified-multinode-edpm-e2e-nobuild-tagged-crc

podified-multinode-edpm-e2e-nobuild-tagged-crc fails with Could not find or access
'/home/zuul/ci-framework-data/artifacts/pre_deploy_ceph_deploy.yml'
Testing the job with hci_ceph_backends.yml
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

recheck


chore: Repo limit check visibility status not updated in DB in commit flow

Description
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Manual
Jest
Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] 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
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/ok-to-test

/build-deploy-preview

[ ] Getting following error, on connecting an app to git, there are no previously git connected app in this workspace. @AnaghHegde

/ok-to-test

/build-deploy-preview

/build-deploy-preview

/ok-to-test

@AnaghHegde I added 4 public repos then made all of them private, on committing in one of the app it first shows the repo limit modal but on hard refresh and on trying to commit again, commit goes through. Refer:
https://user-images.githubusercontent.com/80334441/237013632-b7ddbca4-58fd-4fb4-8fbd-9b51f5631554.mov

/build-deploy-preview

/build-deploy-preview

/ok-to-test


WIP: Report lint warnings from file

Similar to reporting custom comments, but with much tighter integration to Phabricator's APIs so the lint warnings show up inline in reviews.
TODOs:

[ ] Actually parse the remote file
[ ] Support line-by-line JSON as well as properly-formed JSON to allow tools to easily tee into the file
[ ] Manually test on private phab/jenkins

Fixes #162

Coverage decreased (-2.1%) to 90.025% when pulling e6818bda6d9c3076ab6c7e97ede2727f12c41086 on report-lint-warnings into 75e19ad2500109146be44b00e0583f40c7caf3bc on master.

Changes Unknown when pulling 3d69e7df931ffb12c5955574ca279c90762c07a2 on report-lint-warnings into ** on master**.

Coverage decreased (-2.5%) to 89.674% when pulling 3d69e7df931ffb12c5955574ca279c90762c07a2 on report-lint-warnings into 132df63c5ab2039f1854996471e18ff511925b83 on master.

This seems very useful!

Glad to see!

@anuptalwalkar take a look at #162 to see what this PR is supposed to accomplish (lint versus comments)

Seems like there are merge conflicts to resolve as well.

Coverage decreased (-3.7%) to 88.487% when pulling 9686b256d583c68c53d88550d41181bf2f792a61 on report-lint-warnings into 5c6a87406a2e61db0b09b26c47427a224d3d7d7b on master.

Coverage decreased (-0.2%) to 91.973% when pulling 55724e02c1d2c07b3456d72e1239bfdd78f65cd9 on report-lint-warnings into 5c6a87406a2e61db0b09b26c47427a224d3d7d7b on master.

This looks great @anuptalwalkar, thanks for finishing it (or more accurately, doing all the real work).
I'd like to do a bit of manual testing and then will merge and release a new version of the plugin.

Coverage increased (+0.2%) to 92.451% when pulling dccaec3eeeb2c29eb15cbb6c1f85e20b8f8e4587 on report-lint-warnings into 5c6a87406a2e61db0b09b26c47427a224d3d7d7b on master.

BTW @jjx will we need any changes to DSL stuff to enable this once landed? There's a new option (default on) that we should apply to all of our jobs

Coverage increased (+0.2%) to 92.457% when pulling 8e0990c6dd14314355ae4e7d1ff250608d199a1e on report-lint-warnings into 5c6a87406a2e61db0b09b26c47427a224d3d7d7b on master.


Release v0.16.0

[x] #737
[x] #749
[x] #526
[ ] #1006

Brief feedback - we are running 0.16.0-rc3 in 8 environments now.
The pods get their additional properties.
There was an issue applying updated Terraform objects with spec.RunnerPodTemplate.spec where Flux complained that this was not valid. Editing the kind:Terraform manually was fine. This happened not on all Terraform objects in the same cluster though 🤷


Add labeldrop and labelkeep actions.

Introduce two new relabel actions. labeldrop, and labelkeep.
These can be used to filter the set of labels by matching regex

labeldrop: drops all labels that match the regex
labelkeep: drops all labels that do not match the regex

implementation lgtm 👍
On a higher level we should have a general consensus as to whether this should be a feature, but personally I think it's worth it, especially for being able to protect ourselves from applications that would otherwise break Prometheus.

See the reference ticket for discussion. This doesn't help with high
cardinality metrics. It's more to do with bulk label removal to help remove
unwanted labels where they cannot easily be removed at source.
On Tue, 13 Dec 2016, 21:53 Frederic Branczyk<EMAIL_ADDRESS>wrote:

implementation lgtm 👍
On a higher level we should have a general consensus as to whether this
should be a feature, but personally I think it's worth it, especially for
being able to protect ourselves from applications that would otherwise
break Prometheus.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/prometheus/pull/2279#issuecomment-266873878,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEo8woKen27nCC_xWL9Paqi-FN2BqNOks5rHxPrgaJpZM4LMNuv
.

Thanks!


can not implement single selection

yeah i can't
code samples in docs are not working for me.

What exactly does not work for you?


Share and collect validator signatures over UCCB events

When validators sign a Relayed event, they shall broadcast their signatures using libp2p, and they shall collect and store the signatures broadcast by other validators.
On every new signature received, validators shall check if the signatures collected have reached the supermajority and mark the respective UCCB nonce as ready, meaning that a UCCB transaction can be submitted to the target chain,

Implemented in https://github.com/Zilliqa/zq2/pull/1354