Black screen, then game closes. no crash

Describe the bug/error
On Arch Linux,
When i try to launch the game using min-ed-launcher it opens a fairly small window compared to my native 1080p that closes on its own a few seconds.
the game as a whole never actually starts unless i use the one from the actual game
the window is completely black and is named Elite - Dangerous (Client)
Steam Version of Odyssey
Proton Version: (GE-Proton7-49)
Launch Options:
gamemoderun alacritty -e ./MinEdLauncher %COMMAND% /edo /autorun /autoquit

Also tried with Konsole to the same effect
Debug log
2023-02-20 18:39:11.392 -05:00 [INF] Elite Dangerous: Minimal Launcher - v0.8.1+6145fdf5
2023-02-20 18:39:11.519 -05:00 [DBG]
    Args: [|"/home/<snip user>/.local/share/Steam/ubuntu12_32/reaper"; "SteamLaunch";
  "AppId=359320"; "--";
  "/home/<snip user>/.local/share/Steam/ubuntu12_32/steam-launch-wrapper"; "--";
  "/usr/share/steam/compatibilitytools.d/proton-ge-custom/proton";
  "waitforexitandrun";
  "/media/data/Steam/steamapps/common/Elite Dangerous/EDLaunch.exe"; "/Steam";
  "/novr"; "/edo"; "/autorun"; "/autoquit"|]
    OS: Linux64
    Env: STEAM_COMPAT_DATA_PATH=/media/data/Steam/steamapps/compatdata/359320

2023-02-20 18:39:11.523 -05:00 [DBG] Reading settings from '/home/<snip user>/.config/min-ed-launcher/settings.json'
2023-02-20 18:39:11.723 -05:00 [DBG] Settings: { }
2023-02-20 18:39:11.733 -05:00 [DBG] Unset LC_ALL. Using $LANG to determine correct UI culture
2023-02-20 18:39:11.792 -05:00 [INF] Elite Runtime
    Platform: Steam
    CobraBay Version: 0.4.6779.0
    Products Dir: /media/data/Steam/steamapps/common/Elite Dangerous/Products
2023-02-20 18:39:11.812 -05:00 [DBG] Getting machine id
2023-02-20 18:39:11.872 -05:00 [INF] Logging in
2023-02-20 18:39:11.873 -05:00 [DBG] Getting remote time
2023-02-20 18:39:13.241 -05:00 [DBG] Got steam client
2023-02-20 18:39:13.241 -05:00 [DBG] Got steam pipe
2023-02-20 18:39:13.282 -05:00 [DBG] Got steam global user
2023-02-20 18:39:13.284 -05:00 [DBG] Got steam user
2023-02-20 18:39:13.285 -05:00 [DBG] Requesting steam auth ticket
2023-02-20 18:39:13.286 -05:00 [DBG] Got steam auth ticket
2023-02-20 18:39:13.293 -05:00 [DBG] Authenticating via Steam
2023-02-20 18:39:13.977 -05:00 [DBG] Successfully authenticated
2023-02-20 18:39:13.978 -05:00 [DBG] Disposing Steam resources
2023-02-20 18:39:13.978 -05:00 [DBG] Cancelling auth ticket
2023-02-20 18:39:13.978 -05:00 [DBG] closing steam
2023-02-20 18:39:13.981 -05:00 [INF] Logged in via Steam as: <snip name>
2023-02-20 18:39:13.981 -05:00 [DBG] Getting authorized products
2023-02-20 18:39:15.719 -05:00 [DBG] Purchases Response:
{"purchases":[{"colour":"#f07b05","filter":"ed","directory":"elite-dangerous-64","serverargs":"","gameargs":"SeasonOne","sortkey":"06","product_name":"Legacy Elite Dangerous","imageset":{"box":"http://hosting.zaonce.net/launcher_new/images/box_ed.jpg","hero":"http://hosting.zaonce.net/launcher_new/images/Elite_Dangerous_LauncherHero.png","logo":"http://hosting.zaonce.net/launcher_new/logos/ED_Refresh_Logo_Full_White.png"},"ratings":{"esrb":"teen","pegi":"7"},"game_api":"https://api3x.orerve.net","game_branch":38,"patch_notes_game_code":13,"product_sku":"FORC-FDEV-D-1010","template":"http://hosting.zaonce.net/launcher-steam/elite/en.html"},{"colour":"#f07b05","filter":"eda","directory":"elite-dangerous-64","serverargs":"","gameargs":"CQCArena","sortkey":"20","product_name":"Elite Dangerous: Arena","imageset":{"box":"http://hosting.zaonce.net/launcher_new/images/box_arena.jpg","hero":"http://hosting.zaonce.net/launcher_new/images/Elite_Dangerous_Arena_LauncherHero.png","logo":"http://hosting.zaonce.net/launcher_new/logos/ED_Refresh_Logo_Full_White.png"},"ratings":{"esrb":"teen","pegi":"7"},"game_api":"https://api3x.orerve.net","game_branch":38,"patch_notes_game_code":13,"product_sku":"FORC-FDEV-D-1012","template":"http://hosting.zaonce.net/launcher-steam/elite-dangerous-arena/en.html"},{"colour":"#f07b05","filter":"ed","directory":"COMBAT_TUTORIAL_DEMO","serverargs":"","gameargs":"","sortkey":"30","product_name":"Single Player Combat Training","imageset":{"box":"http://hosting.zaonce.net/launcher_new/images/box_ed.jpg","hero":"http://hosting.zaonce.net/launcher_new/images/Elite_Dangerous_LauncherHero.png","logo":"http://hosting.zaonce.net/launcher_new/logos/ED_Refresh_Logo_Full_White.png"},"ratings":{"esrb":"teen","pegi":"7"},"game_api":"https://api3x.orerve.net","game_branch":38,"patch_notes_game_code":13,"product_sku":"COMBAT_TUTORIAL_DEMO","template":"http://hosting.zaonce.net/launcher-steam/elite/en.html"},{"colour":"#0a8bd6","filter":"edh","directory":"elite-dangerous-64","serverargs":"","gameargs":"","sortkey":"05","product_name":"Legacy Horizons","imageset":{"box":"http://hosting.zaonce.net/launcher_new/images/box_edh.png","hero":"http://hosting.zaonce.net/launcher_new/images/Elite_Dangerous_Horizons_LauncherHero.png","logo":"http://hosting.zaonce.net/launcher_new/logos/ED_Refresh_Logo_Full_White.png"},"ratings":{"esrb":"teen","pegi":"7"},"game_api":"https://api3x.orerve.net","game_branch":38,"patch_notes_game_code":13,"product_sku":"FORC-FDEV-D-1013","template":"http://hosting.zaonce.net/launcher-steam/elite-dangerous-horizons-38/en.html"},{"colour":"#f07b05","filter":"ed","directory":"elite-dangerous-odyssey-64","serverargs":"","gameargs":"SeasonTwo","sortkey":"04","product_name":"Elite Dangerous: Horizons","imageset":{"box":"http://hosting.zaonce.net/launcher_new/images/box_edh.png","hero":"http://hosting.zaonce.net/launcher_new/images/Elite_Dangerous_Horizons_LauncherHero.png","logo":"http://hosting.zaonce.net/launcher_new/logos/ED_Refresh_Logo_Full_White.png"},"ratings":{"esrb":"teen","pegi":"7"},"game_api":"https://api.orerve.net","game_branch":40,"patch_notes_game_code":943,"product_sku":"FORC-FDEV-DO-38-IN-40","template":"http://hosting.zaonce.net/launcher-steam/elite-dangerous-horizons/en.html"},{"colour":"#0a8bd6","filter":"edh","directory":"elite-dangerous-odyssey-64","serverargs":"","gameargs":"","sortkey":"00","product_name":"Elite Dangerous: Odyssey","imageset":{"box":"http://hosting.zaonce.net/launcher_new/images/box_edo.jpg","hero":"http://hosting.zaonce.net/launcher_new/images/Elite_Dangerous_Odyssey_LauncherHero.png","logo":"http://hosting.zaonce.net/launcher_new/logos/ED_Watson_Logo_Full_White.png"},"ratings":{"esrb":"teen","pegi":"16"},"game_api":"https://api.orerve.net","game_branch":40,"patch_notes_game_code":943,"product_sku":"FORC-FDEV-DO-1000","template":"http://hosting.zaonce.net/launcher-steam/odyssey/en.html"}]}
2023-02-20 18:39:15.738 -05:00 [DBG] Authorized Products: Elite Dangerous: Odyssey,Elite Dangerous: Horizons,Legacy Horizons,Legacy Elite Dangerous,Elite Dangerous: Arena,Single Player Combat Training
2023-02-20 18:39:15.738 -05:00 [INF] Checking for updates
2023-02-20 18:39:16.558 -05:00 [DBG] Launcher is latest release 0.8.1
2023-02-20 18:39:16.565 -05:00 [DBG] Disabling 'Single Player Combat Training'. Unable to find product at '/media/data/Steam/steamapps/common/Elite Dangerous/Products/COMBAT_TUTORIAL_DEMO/VersionInfo.txt'
2023-02-20 18:39:18.888 -05:00 [INF] Available Products:
	Elite Dangerous: Odyssey  FORC-FDEV-DO-1000     Up to Date
	Elite Dangerous: Horizons FORC-FDEV-DO-38-IN-40 Up to Date
	Legacy Horizons           FORC-FDEV-D-1013      Up to Date
	Legacy Elite Dangerous    FORC-FDEV-D-1010      Up to Date5
	Elite Dangerous: Arena    FORC-FDEV-D-1012      Up to Date
2023-02-20 18:39:19.004 -05:00 [INF] Launching Elite Dangerous: Odyssey
2023-02-20 18:39:19.264 -05:00 [DBG] Process: /media/data/Steam/steamapps/common/Elite Dangerous/Products/elite-dangerous-odyssey-64/EliteDangerous64.exe "ServerToken 7ec...d4c[100] 3bc...f3a[1828] " /language English\\UK /steam /novr
2023-02-20 18:39:51.160 -05:00 [INF] Shutdown Elite Dangerous: Odyssey

settings.json
{
    "apiUri": "https://api.zaonce.net",
    "watchForCrashes": false,
    "language": "en",
    "autoUpdate": true,
    "checkForLauncherUpdates": true,
    "maxConcurrentDownloads": 4,
    "forceUpdate": "",
    "processes": [
    ],
    "shutdownProcesses": [
    ],
    "filterOverrides": [
        { "sku": "FORC-FDEV-DO-1000", "filter": "edo" },
        { "sku": "FORC-FDEV-DO-38-IN-40", "filter": "edh4" }
    ],
    "additionalProducts": [
    ]
}

Log journal from black screen indecent
{ "timestamp":"2023-01-26T19:07:25Z", "event":"Fileheader", "part":1, "language":"English/UK", "Odyssey":true, "gameversion":"<IP_ADDRESS>6", "build":"r289925/r0 " }
{ "timestamp":"2023-01-26T19:08:42Z", "event":"Shutdown" }

Log journal from vanilla launcher
went to main menu then exited manually
{ "timestamp":"2023-01-26T19:36:19Z", "event":"Fileheader", "part":1, "language":"English/UK", "Odyssey":true, "gameversion":"<IP_ADDRESS>6", "build":"r289925/r0 " }
{ "timestamp":"2023-01-26T19:37:30Z", "event":"Commander", "FID":"F2687763", "Name":"Jimmon" }
{ "timestamp":"2023-01-26T19:37:30Z", "event":"Materials", "Raw":[ { "Name":"phosphorus", "Count":3 }, { "Name":"sulphur", "Count":9 }, { "Name":"vanadium", "Count":15 }, { "Name":"chromium", "Count":9 }, { "Name":"zinc", "Count":15 }, { "Name":"manganese", "Count":3 }, { "Name":"tungsten", "Count":3 }, { "Name":"germanium", "Count":3 } ], "Manufactured":[ { "Name":"biotechconductors", "Name_Localised":"Biotech Conductors", "Count":1 } ], "Encoded":[ { "Name":"encryptionarchives", "Name_Localised":"Atypical Encryption Archives", "Count":3 }, { "Name":"consumerfirmware", "Name_Localised":"Modified Consumer Firmware", "Count":3 } ] }
{ "timestamp":"2023-01-26T19:37:30Z", "event":"Rank", "Combat":0, "Trade":2, "Explore":2, "Soldier":0, "Exobiologist":0, "Empire":0, "Federation":0, "CQC":0 }
{ "timestamp":"2023-01-26T19:37:30Z", "event":"Progress", "Combat":44, "Trade":47, "Explore":91, "Soldier":55, "Exobiologist":0, "Empire":13, "Federation":100, "CQC":0 }
{ "timestamp":"2023-01-26T19:37:30Z", "event":"Reputation", "Empire":0.792000, "Federation":3.549870 }
{ "timestamp":"2023-01-26T19:37:30Z", "event":"EngineerProgress", "Engineers":[ { "Engineer":"Felicity Farseer", "EngineerID":300100, "Progress":"Invited" }, { "Engineer":"Eleanor Bresa", "EngineerID":400011, "Progress":"Known" }, { "Engineer":"Hero Ferrari", "EngineerID":400003, "Progress":"Known" }, { "Engineer":"Jude Navarro", "EngineerID":400001, "Progress":"Known" }, { "Engineer":"Liz Ryder", "EngineerID":300080, "Progress":"Known" }, { "Engineer":"Rosa Dayette", "EngineerID":400012, "Progress":"Known" }, { "Engineer":"Baltanos", "EngineerID":400010, "Progress":"Known" }, { "Engineer":"The Dweller", "EngineerID":300180, "Progress":"Unlocked", "RankProgress":0, "Rank":1 }, { "Engineer":"Elvira Martuuk", "EngineerID":300160, "Progress":"Unlocked", "RankProgress":0, "Rank":1 }, { "Engineer":"Tod 'The Blaster' McQuinn", "EngineerID":300260, "Progress":"Invited" }, { "Engineer":"Domino Green", "EngineerID":400002, "Progress":"Known" } ] }
{ "timestamp":"2023-01-26T19:37:30Z", "event":"LoadGame", "FID":"F2687763", "Commander":"Jimmon", "Horizons":true, "Odyssey":true, "Ship":"UtilitySuit_Class1", "Ship_Localised":"Maverick Suit", "ShipID":4293000003, "ShipName":"", "ShipIdent":"", "FuelLevel":1.000000, "FuelCapacity":1.000000, "GameMode":"Solo", "Credits":25736, "Loan":0, "language":"English/UK", "gameversion":"<IP_ADDRESS>6", "build":"r289925/r0 " }
{ "timestamp":"2023-01-26T19:37:49Z", "event":"Statistics", "Bank_Account":{ "Current_Wealth":7913811, "Spent_On_Ships":1698082, "Spent_On_Outfitting":11377533, "Spent_On_Repairs":5717, "Spent_On_Fuel":4223, "Spent_On_Ammo_Consumables":6768, "Insurance_Claims":1, "Spent_On_Insurance":18887, "Owned_Ship_Count":2, "Spent_On_Suits":450000, "Spent_On_Weapons":600000, "Spent_On_Suit_Consumables":629000, "Suits_Owned":4, "Weapons_Owned":7, "Spent_On_Premium_Stock":0, "Premium_Stock_Bought":0 }, "Combat":{ "Bounties_Claimed":29, "Bounty_Hunting_Profit":54040, "Combat_Bonds":0, "Combat_Bond_Profits":0, "Assassinations":7, "Assassination_Profits":837937, "Highest_Single_Reward":18600, "Skimmers_Killed":0, "OnFoot_Combat_Bonds":0, "OnFoot_Combat_Bonds_Profits":0, "OnFoot_Vehicles_Destroyed":0, "OnFoot_Ships_Destroyed":0, "Dropships_Taken":0, "Dropships_Booked":0, "Dropships_Cancelled":0, "ConflictZone_High":0, "ConflictZone_Medium":0, "ConflictZone_Low":0, "ConflictZone_Total":0, "ConflictZone_High_Wins":0, "ConflictZone_Medium_Wins":0, "ConflictZone_Low_Wins":0, "ConflictZone_Total_Wins":0, "Settlement_Defended":0, "Settlement_Conquered":0, "OnFoot_Skimmers_Killed":0, "OnFoot_Scavs_Killed":0 }, "Crime":{ "Notoriety":0, "Fines":1, "Total_Fines":500, "Bounties_Received":5, "Total_Bounties":5000, "Highest_Bounty":1000, "Malware_Uploaded":0, "Settlements_State_Shutdown":0, "Production_Sabotage":0, "Production_Theft":17, "Total_Murders":11, "Citizens_Murdered":6, "Omnipol_Murdered":0, "Guards_Murdered":5, "Data_Stolen":0, "Goods_Stolen":6, "Sample_Stolen":0, "Total_Stolen":6, "Turrets_Destroyed":0, "Turrets_Overloaded":0, "Turrets_Total":0, "Value_Stolen_StateChange":0, "Profiles_Cloned":3 }, "Smuggling":{ "Black_Markets_Traded_With":0, "Black_Markets_Profits":0, "Resources_Smuggled":0, "Average_Profit":0, "Highest_Single_Transaction":0 }, "Trading":{ "Markets_Traded_With":2, "Market_Profits":75674, "Resources_Traded":21, "Average_Profit":9459.25, "Highest_Single_Transaction":22392, "Data_Sold":39, "Goods_Sold":92, "Assets_Sold":0 }, "Mining":{ "Mining_Profits":75682, "Quantity_Mined":13, "Materials_Collected":66 }, "Exploration":{ "Systems_Visited":170, "Exploration_Profits":434842, "Planets_Scanned_To_Level_2":132, "Planets_Scanned_To_Level_3":132, "Efficient_Scans":2, "Highest_Payout":112039, "Total_Hyperspace_Distance":2086, "Total_Hyperspace_Jumps":205, "Greatest_Distance_From_Start":256.14143268799, "Time_Played":146640, "OnFoot_Distance_Travelled":19303, "Shuttle_Journeys":0, "Shuttle_Distance_Travelled":0, "Spent_On_Shuttles":0, "First_Footfalls":0, "Planet_Footfalls":19, "Settlements_Visited":4 }, "Passengers":{ "Passengers_Missions_Accepted":1, "Passengers_Missions_Bulk":0, "Passengers_Missions_VIP":8, "Passengers_Missions_Delivered":8, "Passengers_Missions_Ejected":0 }, "Search_And_Rescue":{ "SearchRescue_Traded":0, "SearchRescue_Profit":0, "SearchRescue_Count":0, "Salvage_Legal_POI":1815500, "Salvage_Legal_Settlements":0, "Salvage_Illegal_POI":500000, "Salvage_Illegal_Settlements":0, "Maglocks_Opened":23, "Panels_Opened":10, "Settlements_State_FireOut":0, "Settlements_State_Reboot":0 }, "Crafting":{ "Count_Of_Used_Engineers":0, "Recipes_Generated":0, "Recipes_Generated_Rank_1":0, "Recipes_Generated_Rank_2":0, "Recipes_Generated_Rank_3":0, "Recipes_Generated_Rank_4":0, "Recipes_Generated_Rank_5":0, "Suit_Mods_Applied":0, "Weapon_Mods_Applied":0, "Suits_Upgraded":0, "Weapons_Upgraded":0, "Suits_Upgraded_Full":0, "Weapons_Upgraded_Full":0, "Suit_Mods_Applied_Full":0, "Weapon_Mods_Applied_Full":0 }, "Crew":{ "NpcCrew_TotalWages":0, "NpcCrew_Hired":0, "NpcCrew_Fired":0, "NpcCrew_Died":0 }, "Multicrew":{ "Multicrew_Time_Total":0, "Multicrew_Gunner_Time_Total":0, "Multicrew_Fighter_Time_Total":0, "Multicrew_Credits_Total":0, "Multicrew_Fines_Total":0 }, "Material_Trader_Stats":{ "Trades_Completed":0, "Materials_Traded":0, "Assets_Traded_In":0, "Assets_Traded_Out":0 }, "Exobiology":{ "Organic_Genus_Encountered":0, "Organic_Species_Encountered":0, "Organic_Variant_Encountered":0, "Organic_Data_Profits":0, "Organic_Data":0, "First_Logged_Profits":0, "First_Logged":0, "Organic_Systems":0, "Organic_Planets":0, "Organic_Genus":0, "Organic_Species":0 } }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"ReceiveText", "From":"", "Message":"$COMMS_entered:#name=Arro Naga;", "Message_Localised":"Entered Channel: Arro Naga", "Channel":"npc" }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"HESPEROS [G-CLAN] FFK-W4Z", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"[AXI] RESILIENT KNIGHT X8Q-T8K", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"Midwinter Point" }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"Trapaconda HBV-37X", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"Transparent Mathematic Laboratories" }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"THE FALL OF HYPERION K8F-64K", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"OBUX VHF-BVJ", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"F.E.S. FANG K4M-W3N", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"tenryu VBZ-TXN", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"Gillekens Gateway", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"HILDA GARDE TBX-GXK", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"THOR XHX-9KY", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"Solemn Goose" }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"THE DARK WHEEL WFW-G6Z", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"AVERTED VISION V5Y-B7V", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"$MULTIPLAYER_SCENARIO14_TITLE;", "SignalName_Localised":"Resource Extraction Site" }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"$MULTIPLAYER_SCENARIO79_TITLE;", "SignalName_Localised":"Resource Extraction Site [Hazardous]" }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"$MULTIPLAYER_SCENARIO77_TITLE;", "SignalName_Localised":"Resource Extraction Site [Low]" }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"DONGUN'S CARRIER Q0W-53Q", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"FENIX KLB-45T", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"XANDER CORP Q9F-58G", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"JORMUNGAND V6M-7VF", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"DVFC BONFIRE BEACON X7N-64T", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"Sakura Spaceflower J9J-2KL", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"NAG-950 Dionysus-class Cropper" }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"SALTPILLAR JHK-4KT", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"Abyss V6G-N9B", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"OSIRIS QFW-B4V", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"SARATOGA XFW-39F", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"THE BLACK HEART WENCH H2F-LVV", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"FNS STARFALL J3B-7QG", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"SMILING PYTHON X3H-73L", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"fns ETERNAL CRUSADER T9Z-2XZ", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"SYSNSTER CARRIER KLX-G2M", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"-STORAGE- WAWA BNJ-6XZ", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"$MULTIPLAYER_SCENARIO42_TITLE;", "SignalName_Localised":"Nav Beacon" }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"BRIGHT FALLS XNZ-24N", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"ECOBEE LONGHAUL XHF-5VW", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"Schwabenstolz QHK-L9Z", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"FRANCESCA T8Z-LVZ", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"[CODE]TON'S OF FUN! Q3W-5DZ", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"STAR DESTROYER K5T-3TK", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"FSSSignalDiscovered", "SystemAddress":8880012661466, "SignalName":"INCUBATOR JZQ-5VN", "IsStation":true }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"Location", "DistFromStarLS":36256.879241, "Docked":false, "OnFoot":true, "StarSystem":"Arro Naga", "SystemAddress":8880012661466, "StarPos":[49.37500,6.18750,33.09375], "SystemAllegiance":"Federation", "SystemEconomy":"$economy_Industrial;", "SystemEconomy_Localised":"Industrial", "SystemSecondEconomy":"$economy_Refinery;", "SystemSecondEconomy_Localised":"Refinery", "SystemGovernment":"$government_Democracy;", "SystemGovernment_Localised":"Democracy", "SystemSecurity":"$SYSTEM_SECURITY_high;", "SystemSecurity_Localised":"High Security", "Population":37926470, "Body":"Gillekens Gateway", "BodyID":46, "BodyType":"Station", "Factions":[ { "Name":"Future of Arro Naga", "FactionState":"None", "Government":"Democracy", "Influence":0.482482, "Allegiance":"Federation", "Happiness":"$Faction_HappinessBand2;", "Happiness_Localised":"Happy", "MyReputation":0.036247 }, { "Name":"Bureau of Arro Naga League", "FactionState":"None", "Government":"Dictatorship", "Influence":0.072072, "Allegiance":"Independent", "Happiness":"$Faction_HappinessBand2;", "Happiness_Localised":"Happy", "MyReputation":0.000000 }, { "Name":"Fong Wang Limited", "FactionState":"None", "Government":"Corporate", "Influence":0.185185, "Allegiance":"Federation", "Happiness":"$Faction_HappinessBand2;", "Happiness_Localised":"Happy", "MyReputation":9.906850 }, { "Name":"Arro Naga Ltd", "FactionState":"None", "Government":"Corporate", "Influence":0.078078, "Allegiance":"Federation", "Happiness":"$Faction_HappinessBand2;", "Happiness_Localised":"Happy", "MyReputation":0.000000, "PendingStates":[ { "State":"CivilWar", "Trend":0 } ] }, { "Name":"Arro Naga Gold Society", "FactionState":"PublicHoliday", "Government":"Anarchy", "Influence":0.026026, "Allegiance":"Independent", "Happiness":"$Faction_HappinessBand1;", "Happiness_Localised":"Elated", "MyReputation":0.000000, "ActiveStates":[ { "State":"PublicHoliday" } ] }, { "Name":"Constitution Party of Arro Naga", "FactionState":"None", "Government":"Dictatorship", "Influence":0.078078, "Allegiance":"Independent", "Happiness":"$Faction_HappinessBand2;", "Happiness_Localised":"Happy", "MyReputation":0.000000 }, { "Name":"Celestial Horizon Corp", "FactionState":"None", "Government":"Dictatorship", "Influence":0.078078, "Allegiance":"Independent", "Happiness":"$Faction_HappinessBand2;", "Happiness_Localised":"Happy", "MyReputation":0.000000, "PendingStates":[ { "State":"CivilWar", "Trend":0 } ] } ], "SystemFaction":{ "Name":"Future of Arro Naga" }, "Conflicts":[ { "WarType":"civilwar", "Status":"pending", "Faction1":{ "Name":"Arro Naga Ltd", "Stake":"Chevalier's Command", "WonDays":0 }, "Faction2":{ "Name":"Celestial Horizon Corp", "Stake":"", "WonDays":0 } } ] }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"Music", "MusicTrack":"NoTrack" }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"SuitLoadout", "SuitID":1755763601140710, "SuitName":"utilitysuit_class1", "SuitName_Localised":"Maverick Suit", "SuitMods":[  ], "LoadoutID":4293000003, "LoadoutName":"Maverick", "Modules":[ { "SlotName":"PrimaryWeapon1", "SuitModuleID":1755919414947628, "ModuleName":"wpn_m_assaultrifle_plasma_fauto", "ModuleName_Localised":"Manticore Oppressor", "Class":1, "WeaponMods":[  ] }, { "SlotName":"SecondaryWeapon", "SuitModuleID":1755859476324330, "ModuleName":"wpn_s_pistol_plasma_charged", "ModuleName_Localised":"Manticore Tormentor", "Class":1, "WeaponMods":[  ] } ] }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"Backpack", "Items":[  ], "Components":[  ], "Consumables":[  ], "Data":[  ] }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"ShipLocker", "Items":[ { "Name":"gmeds", "Name_Localised":"G-Meds", "OwnerID":0, "Count":4 }, { "Name":"healthmonitor", "Name_Localised":"Health Monitor", "OwnerID":0, "Count":11 }, { "Name":"insightentertainmentsuite", "Name_Localised":"Insight Entertainment Suite", "OwnerID":0, "Count":9 }, { "Name":"lazarus", "OwnerID":0, "Count":1 }, { "Name":"largecapacitypowerregulator", "Name_Localised":"Power Regulator", "OwnerID":0, "Count":1 } ], "Components":[ { "Name":"circuitboard", "Name_Localised":"Circuit Board", "OwnerID":0, "Count":6 }, { "Name":"circuitswitch", "Name_Localised":"Circuit Switch", "OwnerID":0, "Count":5 }, { "Name":"electricalfuse", "Name_Localised":"Electrical Fuse", "OwnerID":0, "Count":6 }, { "Name":"electricalwiring", "Name_Localised":"Electrical Wiring", "OwnerID":0, "Count":9 }, { "Name":"metalcoil", "Name_Localised":"Metal Coil", "OwnerID":0, "Count":4 }, { "Name":"microsupercapacitor", "Name_Localised":"Micro Supercapacitor", "OwnerID":0, "Count":5 }, { "Name":"microtransformer", "Name_Localised":"Micro Transformer", "OwnerID":0, "Count":6 }, { "Name":"motor", "OwnerID":0, "Count":9 }, { "Name":"opticalfibre", "Name_Localised":"Optical Fibre", "OwnerID":0, "Count":17 }, { "Name":"electromagnet", "OwnerID":0, "Count":7 }, { "Name":"microelectrode", "OwnerID":0, "Count":22 } ], "Consumables":[ { "Name":"healthpack", "Name_Localised":"Medkit", "OwnerID":0, "Count":20 }, { "Name":"energycell", "Name_Localised":"Energy Cell", "OwnerID":0, "Count":19 }, { "Name":"amm_grenade_emp", "Name_Localised":"Shield Disruptor", "OwnerID":0, "Count":20 }, { "Name":"amm_grenade_frag", "Name_Localised":"Frag Grenade", "OwnerID":0, "Count":20 }, { "Name":"amm_grenade_shield", "Name_Localised":"Shield Projector", "OwnerID":0, "Count":20 }, { "Name":"bypass", "Name_Localised":"E-Breach", "OwnerID":0, "Count":15 } ], "Data":[ { "Name":"chemicalinventory", "Name_Localised":"Chemical Inventory", "OwnerID":0, "Count":2 }, { "Name":"maintenancelogs", "Name_Localised":"Maintenance Logs", "OwnerID":0, "Count":10 }, { "Name":"mininganalytics", "Name_Localised":"Mining Analytics", "OwnerID":0, "Count":5 } ] }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"Missions", "Active":[  ], "Failed":[  ], "Complete":[  ] }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"Music", "MusicTrack":"Exploration" }
{ "timestamp":"2023-01-26T19:38:13Z", "event":"Music", "MusicTrack":"NoTrack" }
{ "timestamp":"2023-01-26T19:38:14Z", "event":"ReceiveText", "From":"Gillekens Gateway", "Message":"$STATION_NoFireZone_entered;", "Message_Localised":"No fire zone entered.", "Channel":"npc" }
{ "timestamp":"2023-01-26T19:48:41Z", "event":"Music", "MusicTrack":"Exploration" }
{ "timestamp":"2023-01-26T19:48:44Z", "event":"Music", "MusicTrack":"MainMenu" }
{ "timestamp":"2023-01-26T19:48:50Z", "event":"Shutdown" }

It looks like the game isn't being launched via proton. The launcher parses the args that steam provides in order to determine how to launch proton.
I noticed a couple things about your config:

There's no soldier path in your arguments which is the container steam uses for proton starting at version 5.13. Have you disabled that? Normally, there'd be a few extra args, one of which being /home/<user>/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier/_v2-entry-point
You're using a non-standard path name for proton /usr/share/steam/compatibilitytools.d/proton-ge-custom/proton. The launcher is currently case-sensitive when it checks for not running via soldier. I think it would work if your path were /usr/share/Steam/compatibilitytools.d/Proton-ge-custom/proton instead. I'll add case-insensitivity to my todo list.

It looks like the game isn't being launched via proton. The launcher parses the args that steam provides in order to determine how to launch proton.
I noticed a couple things about your config:

There's no soldier path in your arguments which is the container steam uses for proton starting at version 5.13. Have you disabled that? Normally, there'd be a few extra args, one of which being /home/<user>/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier/_v2-entry-point
You're using a non-standard path name for proton /usr/share/steam/compatibilitytools.d/proton-ge-custom/proton. The launcher is currently case-sensitive when it checks for not running via soldier. I think it would work if your path were /usr/share/Steam/compatibilitytools.d/Proton-ge-custom/proton instead. I'll add case-insensitivity to my todo list.

To test, i renamed /usr/share/steam/compatibilitytools.d/proton-ge-custom/ to /usr/share/Steam/compatibilitytools.d/Proton-ge-custom/
as you suggested, but nothing changed.
so i manually downloaded the non-AUR archive from glorious eggrolls github and extracted it to /home/<snip user>/.local/share/Steam/compatibilitytools.d
and it worked, complete with loading SteamLinuxRuntime_soldier as you mentioned
i tried copying /usr/share/Steam/compatibilitytools.d/Proton-ge-custom/ to  /home/<snip user>/.local/share/Steam/compatibilitytools.d/Proton-ge-custom/
and when i copied the AUR package to my user directories compatibilitytools.d folder it had the same issue as it did in the /usr/share/ compatibilitytools.d directory
so i downloaded the actual AUR proton-ge-custom-bin package instead of the Chaotic-AUR package to see if there is a difference
and the actual AUR package works, meaning the problem is with the chaotic-aur package
Source of the bug
It was caused by the chaotic-aur version of proton-ge-custom-bin
Use the actual AUR version, it works as expected.
it's not an issue with min-ed-launcher


Align colors in SDL package to Go specification

Closes https://github.com/veandco/go-sdl2/issues/580
This PR does the following changes:

It ensures that Surface.Set does not panic by handling colors correctly.
It changes Surface.At to return color.NRGBA instead of color.RGBA which is the correct type for what is being returned (non-alpha-premultiplied color). This can be a breaking change if anyone ever expected a specific color from the method, despite the interface abstraction.
It changes the sdl.Color type to color.NRGBA which is the correct representation of what is held in sdl.Color (non-alpha-premultiplied color). This is a breaking change. Preserving the color.RGBA type mapping would require more code rework.
It fixes all of the color models to properly return 16bit-component alpha-premultiplied colors.
It fixes a broken type reference in the sdl package

Things to note:

The color.RGBA type in Go represents an alpha-premultiplied color and SDL2 appears to use standard non-alpha premultiplied colors everywhere. This is why color.NRGBA is the correct pick.
The Color.RGBA method is expected to return 16bit (i.e. from 0x0000 to 0xFFFF) alpha-premultiplied color components.
The PR makes heavy use of color.NRGBA and color.NRGBAModel, since these are the official ones and they have stable and optimized implementations for color conversions between alpha-premultiplied and non-alpha-premultiplied variants and from 8bit-component to 16bit-component colors.

Side notes:

In the past I had written a blog post about Go's colors which can shed some light on the above considerations. Feel free to remove this section if such type of links are unacceptable here.
While downscaling of bytes is trivial, upscaling is not so if you want to fill the whole scale. I have tried to come up with the proper bit-wise operation expressions but to double-check I have used the following Go program to empirically measure it: https://play.golang.com/p/fYrvt4TXFv2

This PR should be ready for a more general public verification. The more people that have color scenarios in their apps to verify the better.

Thank you very much @mokiat! I will merge this into the v0.4.x branch and create a new patch release as well so more people can test it.

Yes, master is preferred in most cases. I usually cherry-pick the commit into v.4.x branch afterwards. (Speaking of, I really should get v0.5.x out already 😓, just stuck on the static libraries currently).


fix the mqtt queue multi level topic with special characters and delete the unused yaml travis

in the main branch
mqtt queue multi level topic has charactor "/" ,
When the broker diapatch, it will create a multi-level file directory, causing problems such as recovery...

link #12 PR has merge and fixed


OCPNODE-2734: Replace gcr.io/kubebuilder/kube-rbac-proxy image

Fixes https://github.com/openshift/instaslice-operator/issues/291
Add the WithAuthenticationAndAuthorization filter to support deprecation of kube-rbac-proxy image from the kubebuilder repository
make lint, make test, make test-e2e-kind-emulated pass locally
There is no e2e test as of now to test this metrics endpoint, I would like to add the same and holding this PR until then
/hold
/cc @rphillips @kannon92 @mamy-CS

I think you are missing a few services/role binding for this to work.
ex: https://github.com/kubernetes-sigs/jobset/pull/722
I tested this by creating a metrics pod and using curl to verify that I could view the metrics if I use the right certs.

We don't have any metrics yet so not sure what we would test. I guess you can try grabbing the metrics from controller-runtime?

Having the vendor update in a separate commit would be helpful for the review.


Error when running docker container

Describe the bug
When using the docker container interactively it returns
[15:01:14] ❌ Completion script generation failed: ['ns-train', '--tyro-print-completion', 'bash']        install.py:107
Traceback (most recent call last):                                                             install.py:111
File "/home/user/.local/bin/ns-train", line 5, in
from scripts.train import entrypoint
File "/home/user/nerfstudio/scripts/train.py", line 49, in
from nerfstudio.configs.method_configs import AnnotatedBaseConfigUnion
File "/home/user/nerfstudio/nerfstudio/configs/method_configs.py", line 47, in
from nerfstudio.field_components.temporal_distortions import TemporalDistortionKind
File "/home/user/nerfstudio/nerfstudio/field_components/init.py", line 17, in
from .encodings import Encoding, ScalingAndOffset
File "/home/user/nerfstudio/nerfstudio/field_components/encodings.py", line 34, in
import tinycudann as tcnn
File "/home/user/.local/lib/python3.10/site-packages/tinycudann/init.py", line 9, in

from tinycudann.modules import free_temporary_memory, NetworkWithInputEncoding, Network,
Encoding
File "/home/user/.local/lib/python3.10/site-packages/tinycudann/modules.py", line 35, in

raise EnvironmentError(f"Could not find compatible tinycudann extension for compute
capability {system_compute_capability}.")
OSError: Could not find compatible tinycudann extension for compute capability 75.
To Reproduce
Steps to reproduce the behavior:
$ docker run --gpus all -v ~/workspace:/workspace/ -v /srv/nerfstudio/.cache/:/home/user/.cache/ -p 7007:7007 --rm -it dromni/nerfstudio:0.1.16
Expected behavior
Screenshots

Additional context
Running on
Headless Ubuntu 22.04
Nvidia Driver Version: 525.78.01
CUDA Version: 12.0
Quadro RTX 5000

same issue , either run or build from repo.

Please try again with dromni/nerfstudio:0.1.16 which was rebuilt. Also, please use global paths, no realtives!


Add python-validity support

Describe the package
I was hoping to get the python-validity (https://github.com/uunicorn/python-validity) package out of the box in this image.
Thus, fingerprints can be used on most types of laptops.
Information on the package
https://github.com/uunicorn/python-validity
Validity fingerprint sensor driver.
Image
All Images

Considering this is hardware enablement, maybe this issue would better fit the config layer

Interesting.
I would like to know some personal experiences with specific laptop models, which got working fingerprint after installing this package. So far, I could not find any anecdotal experiences on this.
Just a note that those dependencies should be installed as well, as listed in main page:
open-fprintd
fprintd-clients
fprintd-clients-pam

As an anecdote: python-validity is required to get the fingerprint readers working on both of my ThinkPads (T480s and X1 Nano). I would love to see an option for this.
I suppose it makes sense here given that ublue has a strong foundation of hardware enablement.
Bus 001 Device 004: ID 06cb:009a Synaptics, Inc. Metallica MIS Touch Fingerprint Reader

Alright so this isn't in any repo and no one seems to be working on it, if someone wants to work on this please reopen.


Ignore all Python 3 virtual environments

jenkins: test this please

test this please

Jenkins, test this please

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences


Update to Symfony 5.2 RC1

have you checked where the new deprecation comes from ?

@stof yes ... it's from Symfony's Twig Loader pass ... but I was going to fix it and couldn't, because apparently it's been fixed since the beta release:

this might indicate missing tests in Symfony, as the testsuite should forbid deprecations...

@stof @nicolas-grekas after upgrading to Symfony 5.2 beta3 I can still see that deprecation. Is this something to be fixed upstream in Symfony? Thanks! Details:

I've just updated to 5.2 RC1. I don't see any issues or deprecations ... and the application feels super lightweight and responsive.

I've updated to 5.2 RC2. These are the reported deprecations:
Remaining indirect deprecation notices (7)

  6x: The "Doctrine\Common\Inflector\Inflector::classify" method is deprecated and will be dropped in doctrine/inflector 2.0. Please update to the new Inflector API.
    2x in AddUserCommandTest::testCreateUserNonInteractive from App\Tests\Command
    2x in AddUserCommandTest::testCreateUserInteractive from App\Tests\Command
    1x in BlogControllerTest::testAdminNewPost from App\Tests\Controller\Admin
    1x in UserControllerTest::testEditUser from App\Tests\Controller

  1x: Since symfony/dependency-injection 5.2: The "Symfony\Component\DependencyInjection\Alias::setPrivate()" method is deprecated, use "setPublic()" instead.
    1x in AddUserCommandTest::testCreateUserNonInteractive from App\Tests\Command


Make error message for rmdir better

https://github.com/yruen/Texture-Filterer/blob/d1ef041b52d2bebd568c917a1abe1d7dff5af6b6/other_scripts/otherUtils.py#L38

Hi @yruen , Are you looking for something like this?
try:
error = os.rmdir(dir)
except:
print("An exception has occurred while trying to delete the directory : " ,dir)
print("Exception class : ", sys.exc_info()[0])
print("Exception message : ", sys.exc_info()[1])

@nikhilnarla thank you for your suggestion,
I was thinking more of it catching the error if it detects there are still files in the folder that way it'd print out something like "Could not delete: folder is not empty" but thank you

@nikhilnarla that's a very valid point. I did not consider that. Thank you for your comment, I'll use this as a base


fix cost tensor device

fix #576

Codecov Report

Merging #577 (9de7195) into main (a5ba9d0) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #577   +/-   ##
=======================================
  Coverage   97.17%   97.17%
=======================================
  Files          56       56
  Lines        2333     2333
=======================================
  Hits         2267     2267
  Misses         66       66

Impacted Files
Coverage Δ

pfhedge/nn/functional.py
91.40% <100.00%> (ø)

Continue to review full report at Codecov.

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


Mapping of texture filtering modes for NativeEngine contains mismatches

The affected tech may also be called sampling modes. Constants.TEXTURE_LINEAR_LINEAR_MIPNEAREST is currently mapped to trilinear sampling, which is incorrect. This should either be amended or called out explicitly, and the other mappings should also be reviewed to ensure they are correctly matched.

Addressing with https://github.com/BabylonJS/BabylonNative/pull/419.

#419 now merged.


Update  base image version for apptainer cluster examle

Fix: #70
from  slurm-gcp-5-9-hpc-rocky-linux-8-1707957597
to slurm-gcp-5-10-hpc-rocky-linux-8-1707957597
Signed-off-by: Yoshiaki Senda<EMAIL_ADDRESS>

The following error is what I got during deployment
Writing outputs for deployment group cluster to file hpctainer/cluster/cluster_inputs.auto.tfvars
Initializing deployment group hpctainer/cluster
Testing if deployment group hpctainer/cluster requires adding or changing cloud infrastructure
Error: terraform plan for deployment group hpctainer/cluster failed
exit status 1

Error: Resource postcondition failed

  on modules/embedded/community/modules/scheduler/schedmd-slurm-gcp-v5-controller/source_image_logic.tf line 62, in data "google_compute_image" "slurm":
  62:       condition     = !contains(keys(local.known_project_families), self.project) || try(contains(local.known_project_families[self.project], self.family), false)
    ├────────────────
    │ local.known_project_families is object with 1 attribute "schedmd-slurm-public"
    │ self.family is "slurm-gcp-5-9-hpc-rocky-linux-8"
    │ self.project is "schedmd-slurm-public"

Image family slurm-gcp-5-9-hpc-rocky-linux-8 published by SchedMD in project
schedmd-slurm-public is not compatible with this release of the Terraform
Slurm modules. Select from known compatible releases:
	"slurm-gcp-5-10-debian-11"
	"slurm-gcp-5-10-hpc-rocky-linux-8"
	"slurm-gcp-5-10-ubuntu-2004-lts"
	"slurm-gcp-5-10-ubuntu-2204-lts-arm64"
	"slurm-gcp-5-10-hpc-centos-7-k80"
	"slurm-gcp-5-10-hpc-centos-7"

Error: Resource postcondition failed

  on modules/embedded/community/modules/scheduler/schedmd-slurm-gcp-v5-login/source_image_logic.tf line 62, in data "google_compute_image" "slurm":
  62:       condition     = !contains(keys(local.known_project_families), self.project) || try(contains(local.known_project_families[self.project], self.family), false)
    ├────────────────
    │ local.known_project_families is object with 1 attribute "schedmd-slurm-public"
    │ self.family is "slurm-gcp-5-9-hpc-rocky-linux-8"
    │ self.project is "schedmd-slurm-public"

Image family slurm-gcp-5-9-hpc-rocky-linux-8 published by SchedMD in project
schedmd-slurm-public is not compatible with this release of the Terraform
Slurm modules. Select from known compatible releases:
	"slurm-gcp-5-10-debian-11"
	"slurm-gcp-5-10-hpc-rocky-linux-8"
	"slurm-gcp-5-10-ubuntu-2004-lts"
	"slurm-gcp-5-10-ubuntu-2204-lts-arm64"
	"slurm-gcp-5-10-hpc-centos-7-k80"
	"slurm-gcp-5-10-hpc-centos-7"


Incompatibility with Monk's Enhanced Journals

Clicking on the Linked Links doesn't do anything.
System used: World of Darkness 20th edition v. 4.1.3
Foundry 12.331.
Thanks.

Monk's Enhanced journal makes extensive changes to journal links, so currently the modules are not compatible. Maybe i can add compatibility as a feature in the next version

Sadly it's a pretty extensive project to add Compatibility to Monk's enhanced Journal.
Might happen in the future, but most not too soon as i neither use MEJ nor am i familiar with its function.

Monk's is pretty active on their discord, when you can, you could talk to them to enable compatibility.

I'll try, but the problem with MEJ ist, that it (almost) completely changes the way journals work. So its probably easier for them to integrate a similar backlink-funcitionality directly into their module instead of interfacing with this one.
I'll talk to them as soon as i had time to find ouf the exact nature of the issue.


Scenes created in Tuya are loaded into Hubitat but don't run

Hi, this is a follow up to my post in the Hubitat community forum. Thank you for this amazing driver! I noticed that it correctly pulled down my Tuya devices and even a scene (which I use for turning a socket off and back on to ring a doorbell). However, the On button didn't actually run the scene. I believe it's because my Home ID is too large - 9 digits long - which does not fit in an Int. But, Int shouldn't be needed since it's only used for appending to the URL in the API call anyway.
I got it to work by changing every "Int homeId" to "String homeId", including in the triggerTuyaScene() function definition.
The only thing is that for scenes, it doesn't make a lot of sense to have a "switch" as the default component since they wouldn't have an Off function. Perhaps your code could add Tuya scenes as a push button or similar?
Regards,
Gabriel Mongefranco
Mobile Data Architect
https://gabriel.mongefranco.com

I'll change the Integer homeId to String homeId as you are right, there is no reason for it to be an Integer as its just a key.


fix(react): fix GA4 integration not firing PRODUCT_UPDATED.CHANGE_QUANTITY when quantity is 0

Description
While implementing GA4 integration we received feedback that we should fire event change_quantity "when a user removes the last item from a product from the cart". Meaning firing eventTypes.PRODUCT_UPDATED with oldQuantity as previous added quantity and quantity as 0.
Since 0 is falsy, it will never fire this event because of the verification. So instead I think using lodash's isFinite is a better verification than just falsy check, as this makes it possible to fire change_quantity with quantity 0.
Dependencies
None
Checklist

[x] The commit message follows our guidelines
[ ] Tests for the respective changes have been added
[ ] The code is commented, particularly in hard-to-understand areas
[x] The labels and/or milestones were added

Disclaimer
By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement

hello @AceBunny!
first of all, thank you for your contribution :)
could you please add a unit test to cover this specific case, so we can proceed with the PR?
thank you!

Hi @ruifcnunes
Just added a new united test for this case, can you check if it is ok? Thanks 😄


Set minimum and maximum width and height box area resizing

can I Set minimum and maximum width and height box area resizing? thx

@mramdhani Which version is was used?

version 4.1.0

Cropbox::widget([
    ...
    'pluginOptions' => [
        'variants' => [
            [
                'width' => 200,
                'height' => 200,
                'minWidth' => 180,
                'minHeight' => 200,
                'maxWidth' => 350,
                'maxHeight' => 350
            ]
        ]
    ],
    ...
]);

https://github.com/bupy7/jquery-cropbox/blob/master/README.md#variants-required

The reason for closing: No answer.


Beacon check fixes

Problems that had to be overcome:

Added spacing for clarity of code
The old if statement to check if the contract was a beacon and add never considered the second part of the if statement thus failing and always passing into the code.
Old beacon contracts contained 3 elements not 4 thus why the beacon elements sent back nothing for the required strings. In turn causing a bad beacon contract tx.

Solutions:

Split the if statements and they are working correctly now
Added required mandatory block of 378000 for testnet and 1070000 for production (~14 days from now)
Added Debug messages for the tx checks in memory pool and checkblock
Added Debug messages for the memory pool/Checkblock failed information used as well
Added a forgotten check to see if beacon is not in cache.

why? if it gets past in block then it's in chain.
On Oct 22, 2017 4:00 AM, "Tomáš"<EMAIL_ADDRESS>wrote:

@tomasbrod commented on this pull request.
In src/main.cpp
https://github.com/gridcoin/Gridcoin-Research/pull/701#discussion_r146128185
:

@@ -3977,7 +3977,7 @@ bool CBlock::CheckBlock(std::string sCaller, int height1, int64_t Mint, bool fCh

     // Verify beacon contract if a transaction contains a beacon contract
     if (!VerifyBeaconContractTx(tx.hashBoinc) && !fLoadingIndex)

       return DoS(25, error("CheckBlock[] : bad beacon contract found in tx contained within block; rejected"));

       return DoS(25, error("CheckBlock[] : bad beacon contract found in tx %s contained within block; rejected", tx.GetHash().ToString().c_str()));

You can skip your beaconchecks here.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gridcoin/Gridcoin-Research/pull/701#pullrequestreview-71029842,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMrVQC5XqNfVXLpDz7kfcCgAOW9oUhFXks5suyBVgaJpZM4QBwB1
.


Kudos resource

Fixes #4431
This PR adds a new Kudos module and also creates a new Kudos API Resource. The module sets up a dosomething_kudos database table which will contain all kudos records that are attached to specific reportback items.
There is more work to be done, but this PR sets up a lot of the groundwork. The /api/v1/kudos basic endpoints work and can successfully create a kudos record (or multiple records at once) and delete individual records.
Just to note, the newly added abstract Transformer class residing in the dosomething_api module will set up universal transformer methods that the resource classes can extend. This abstract class will be fleshed out in following PRs.
@jonuy @angaither

The module should also be added to dosomething.info as well

@weerd Did you check out RESTful at all? It provides a lot of these CRUD endpoints out of the box...

Ooh, one thing that's missing. You can automatically enable the Services endpoints by exporting them into the dosomething_api via Features.  If they are enabled in your local DB, run drush fu dosomething_api to update the feature -- you'll see the new endpoints added to the file.
Once all is said and done, pull down the staging db and run a ds build to do a full test of enabling the module and the endpoints.

Oh yeah. I was gonna do the Features stuff in a separate PR once I had the Kudos stuff at full functionality, but I can do that in this PR if it makes more sense?

Oh, ok. It's think it's fine to keep it in a separate PR -- didn't know it was on the way.

@aaronschachter went ahead and just removed that unused targeted action for kudos in reportback-items resource :)

@angaither @aaronschachter also made the updates to the dosomething.info and dosomething.make files. Check those out to make sure they look correct :grimacing:

Looks good to me, did you test with a clean stage db and ds build ?

Oh, I didn't do that since I didn't set up the Feature in this PR. Should I do that test anyhoo and then turn the stuff on manually?

Yeah, it's worth sanity testing that the module is enabled and the table shows up.

The module doesn't seem to be turned on during the rebuild but it doesn't break the build :)

That's weird, @weerd. If you enable the module manually, does it work properly? e.g. Table appears, etc

Yep. It's all good if done manually.

Hmm, then something is up.. .either with this module or possibly with the ds build function that checks to auto-enable modules...
It's not the end of the world if we have to enable manually but it's def a new issue..

I ran this locally and it enabled ok. Did it work on staging?

Haven't deployed to stage yet, but I can now to try it :)

Looks good on Staging; was properly enabled. Might just be a "my local is slightly borked" kinda thing. :grimacing:


Initiate Urdu Localization Team

This issue is to initiate a new l10n Team
Please only use this template for submitting a new l10n team initiation requests.
See https://github.com/cncf/glossary/blob/main/LOCALIZATION.md for basic requirements for a new l10n team.

(1) The language and language code for l10n
Find localization's two-letter language code from ISO 639-1 standard.
For example, the two-letter code for Korean is kr.

Language name (ex: Urdu):
Language two-letter code (ex: ur):

(2) List of volunteers
Name and GitHub Username for each l10n volunteer. Add [A] to make them approvers.
Ex: - [A] Seokho Son (@seokho-son)

[A] Saim Safdar (@Saim-Safdar)
[A] Waleed Ahmed (@waleed318)
Ali Raza (@Ali15700)
Fateh Muhammad (@FatehMuhammad)
Haseeb Shaukat (@mhaseebshaukat)

(Note) Next actions from maintainers

Create a new development branch for the l10n. (ex: dev-kr)
Update codeowners to add l10n contents approvers.
Add a new label for the language.

Thank you, Waleed, now we just need to create the dev branch but wouldn't be able to do so because we don't have permission, can you please help us with that @CathPag

Awesome, @seokho-son and @jihoon-seo will walk you through the process :)

Hi @seokho-son and @jihoon-seo, Need to create local branch for Urdu (dev-ur) as soon as possible. Guide us through the process, so we can start working.

Hi @waleed318

label for ur: https://github.com/cncf/glossary/labels/lang%2Fur
#glossary-localization-urdu channel in CNCF Slack (please invite all ur team members to the channel)

By the way, I think one approver is not enough considering an approver cannot approve his/her PR by self.
Also, in order to merge a PR to dev-ur, the PR requires at least two approvals (from two approvers except author of the PR).

[A] Saim Safdar (@Saim-Safdar)
Waleed Ahmed (@waleed318)
Ali Raza (@Ali15700)
Fateh Muhammad (@FatehMuhammad)

Please discuss with your team members who can participate as additional approver.
Candidates may need to check #723 in advance. (If there is no eligible approver, please consult with maintainers)
In the meantime I will create dev-ur for Urdu team ! Thanks~!

/assign

Team

[A] Saim Safdar (@Saim-Safdar)
[A] Waleed Ahmed (@waleed318)
Ali Raza (@Ali15700)
Fateh Muhammad (@FatehMuhammad)
Haseeb Shaukat (@mhaseebshaukat)

Ok, I assume your comment suggests that Urdu team will initiate with two approvers. :)

https://github.com/cncf/glossary/tree/dev-ur 🎊

I guess that we should update dev-ur branch with the latest main branch, to make #1324 effective in dev-ur branch too. 😊

Yes @jihoon-seo
Cloud you open ?

I think tasks to initiate Urdu team are complete !


CVE-2022-3172 1-20 patch backport

Issue #, if available:
Description of changes:
Cherry-picked the solution for fix for 1.22 and attempted 1.20 backport, and this additional fix
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

lgtm


[RFC] Improve Developer Experience of LDAP Plugin

Status: Open for comments

Need
Currently, the LDAP plugin is quite opaque: when using it to read and ingest users from an LDAP service, we have nearly no output other than one line in the logs:
2021-07-26T08:35:21.071Z catalog info Reading LDAP users and groups type=plugin

When LOG_LEVEL=debug is used, we get a little bit more, but not nearly enough to facilitate efficient development. Specifically, we do not know when:

the plugin boots up,
the plugin connects to an LDAP service,
the plugin successfully reads users and groups or fails,
ingestion starts,
ingestion is in progress over time, with ideally an estimated time of completion because some orgs have upwards of 10K records and predictability would help a lot here, and finally when
ingestion ends and all users/groups have been imported.

Proposal
I propose we add more detail to the logging that exposes this information in order to allow for a lot more transparency to developers using this plugin. I believe this will improve its developer experience.
Reasonable Defaults
To further improve the developer experience, I also propose adding reasonable defaults to the LDAP reader's configuration, specifically
scope: sub
paged: true

Let's talk about these.

scope: sub: This directive indicates to the LDAP reader to search for all descendants of the search base, instead of the first level down, or just the base object. This is useful because it fits a more generic user/group data model and accommodates varying organizational structures of LDAP directories. I feel this would be the easiest for most consumers to adopt for these reasons. Other alternatives include reading users and groups from levels that are either too shallow or too deep.

paged: true: At scale, without paging, this plugin will receive more data than it can handle and either crash or timeout, as we've experienced using this at Spotify. To remedy this, I propose adding paging as a reasonable default.

We would of course add documentation to make these defaults explicit, as well as instruct users on how to customize them to best suit their organization.

Alternatives
We leave it the way it is? 🤔

Risks

The sub search might get quite deep in an organization's LDAP tree and take a very long time to yield results, however our use of paging remedies this.

I vote yes for all of these! Path of least surprise and most visibility.

I wonder if it makes sense to also move over to using https://github.com/ldapts/ldapts instead of ldapjs. Maybe a nicer query API and looks to be maintained. Wondering if ldapjs is kind of no longer maintained?

This is a lovely idea! TypeScript for life!


A way to make sounds only apply to (certain) weapons?

Is your feature request related to a problem? Please describe.
So I'm currently trying to port BVSSICs Chunked Up Weapons to USTManager, but I've noticed that a lot of sounds are shared between other weapons and enemies, causing stuff to sound pretty weird in some places.
Describe the solution you'd like
maybe some sort of additional syntax that you can add as a sort of suffix/prefix so a certain sound replacement only applies to a specific weapon? (or maybe enemies too?)
example uhhh
"AltRevolverShoot1D": "RevolverSounds/Alt/AltRevPrimaryFire.wav": "weapon.AltPiercer",
that way the sound is only changed for AltPiercer, and anything else that uses AltRevolverShoot1D doesn't have their sound changed
Describe alternatives you've considered
yeah i got nothig </3

This is outside the scope of USTManager but I think I can make an extension/plugin for USTManager to support it but it'll take a few days, worst case 1 or 2 weeks if I don't have the time to get something together. Anyway I just need to restructure some small things in USTManager first but that should be fast

Take your time chief, I can wait
Thanks for taking this into consideration though you the goat 🐟


Add V3 migration message to 'How Bot Works' page

Add V3 migration page to 'How Bot Service Works' Page V3
Some other services such as Cortana point to the V3 page:
How Bot Service works V3
Consider adding same message as in the below page to the page referenced above:
https://docs.microsoft.com/en-us/azure/bot-service/bot-service-quickstart?view=azure-bot-service-3.0
See for example referencing  page from Cortana:
https://docs.microsoft.com/en-us/cortana/skills/get-started

Thanks for your feedback. A migration document is currently being worked on that will do this.


License?

Hi:
I could not find any license for this repo. What would it be?
Thanks!

Sorry, we already included a license in the project.

Thank you ++


Added ProjectType in projecttypes.json for Windows.Devices.GPIO and WinUI3

@madskristensen; Updated the projecttypes.json to support projects I work on which include Windows.Devices.GPIO for WinUI3. Note: This will only show if the User's Project file contains:
	<ItemGroup>
		<ProjectCapability Include="Windows.Devices.Gpio" />
	</ItemGroup>

And it is a WinUI 3 Project that contains Windows.App.SDK.
This also validates what I stated in the Tutorial that Template developers can add project types to their template project file and update the HelpExplorer projecttypes.json to get it available to the user.

@madskristensen; Updated the projecttypes.json file for Android App/lib for .NET 6 built-in VS template. As usual the URL links may not be the ones the MS VS PM wants.

@madskristensen; Updated projecttypes.json to support DotNetCoreRazor built-in VS Templates.

@madskristensen; Updated projecttypes.json to support MS Teams App .NET Core

@madskristensen This seems to be the most I can do with built-in templates since many do not have any different capabilities between them. So, unless the Project Template older decides to add custom project capabilities to the template it would be hard to provide a more precise URL links.

Fantastic. Thank you so much


New version: AutoGP v0.1.7

Registering package: AutoGP
Repository: https://github.com/probsys/AutoGP.jl
Created by: @fsaad
Version: v0.1.7
Commit: dd007588f3fb0e0cc77dc345c81cc4149ddaee0d
Reviewed by: @fsaad
Reference: https://github.com/probsys/AutoGP.jl/commit/dd007588f3fb0e0cc77dc345c81cc4149ddaee0d#commitcomment-149514211
Description: Automated Bayesian model discovery for time series data

[merge approved]


Multiple species entry > Create multiple observations on same point

Is your feature request related to a problem? Please describe.
Feature.
Describe the solution you'd like
There are times where multiple species are found on the exact same point.  While the recently developed copy form function could be used here, the workflow to recreate the exact same point would be very clunky.  Where the copy function is more likely to be used is with similar observations in a nearby area.
Ideally they could select multiple species on the form, and the app will create multiple records (1 per species) each with a geometry of the same point.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Subsequent ticket from #157

This type of workflow will be required for the aquatic observation.
Workflow:
Capture a location on a lake and assign it a nominal area/geometry (specifically a circle).
Record a set of common variables/ attributes that will get assigned to all subsequent species selects.
The user adds 1 or more specifies records (much like the chem treatment form)
In the back end individual observations are created. The copy function autofills the common values.

Using the clone activity functionality, currently the user will be able to specify a geometry and all the form fields they wish to (including a species) and then press clone. The original activity will be stored as it was but will also be cloned identically with the same geometry and form fields. Now, all they have to do is select a different species and continue cloning and repeating this process for as many species as there are
Is this an acceptable workflow? @mikeshasko

Using the clone activity functionality, currently the user will be able to specify a geometry and all the form fields they wish to (including a species) and then press clone. The original activity will be stored as it was but will also be cloned identically with the same geometry and form fields. Now, all they have to do is select a different species and continue cloning and repeating this process for as many species as there are
Is this an acceptable workflow? @mikeshasko

Yes for the aquatic plant and aquatic animal workflow...
1 location of the water is selected
A set of "water" related variables are collected.
1 or more species (with some species variables) are then collected.
So in the end each x,y point could be its own "observation" or we could have the one observation with multiple species.

Yes for the aquatic plant and aquatic animal workflow...
1 location of the water is selected
A set of "water" related variables are collected.
1 or more species (with some species variables) are then collected.
So in the end each x,y point could be its own "observation" or we could have the one observation with multiple species.


Terminal not "visible"

Issue Type: Bug
After screen saver, sleep mode and maby other cases. All the terminals doesn't display the text. You can type, but you don't see the inputed text. You can only see a square.
VS Code version: Code 1.68.0 (4af164ea3a06f701fe3e89a2bcbb421d2026b68f, 2022-06-08T11:44:16.822Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz (4 x 2594)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: unavailable_offopengl: enabled_onrasterization: unavailable_offraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: unavailable_off

Load (avg)
undefined

Memory (System)
7.91GB (1.05GB free)

Process Argv
--crash-reporter-id 5e8b672d-750c-48e1-a055-193ab05c3f9e

Screen Reader
no

VM
0%

Extensions (26)

Extension
Author (truncated)
Version

project-manager
ale
12.6.0

gitignore
cod
0.7.0

doxdocgen
csc
1.4.0

git-extension-pack
don
0.1.3

githistory
don
0.6.19

gitlens
eam
12.1.1

vscode-pull-request-github
Git
0.44.0

githd
hui
2.2.4

better-cpp-syntax
jef
1.15.19

cmake-language-support-vscode
jos
0.0.4

vscode-dotnet-runtime
ms-
1.5.0

python
ms-
2022.8.1

vscode-pylance
ms-
2022.6.30

jupyter
ms-
2022.5.1001601848

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.8

remote-containers
ms-
0.238.3

remote-ssh
ms-
0.82.1

remote-ssh-edit
ms-
0.80.0

remote-wsl
ms-
0.66.3

cmake-tools
ms-
1.11.26

cpptools
ms-
1.10.7

cpptools-extension-pack
ms-
1.2.0

svg-preview
Sim
2.8.3

cmake
twx
0.0.17

vscode-open-in-github
ziy
1.3.6

(1 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonvspyt551:30345470
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vscscmwlcmt:30465135
cppdebug:30492333
vsclangdf:30486550

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.68.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

does changing terminal.integrated.gpuAcceleration help?

Thanks, that solved the issue :). The gpuAcceleration setting had several options. Setting the Acceleration to OFF was a success. I have only observed the issue on an elderly lab computer.


Add command for cart pruning

This PR adds a command lunar:prune:carts and some new config params under lunar.cart.prune_tables to determine how pruning should be carried out.
I opted for using a pipeline for amending the query, as we ultimately always seem to end up there.
I've tried to default to some sensible settings (90 days, dont prune carts with orders associated).
If pruning is enabled we automatically add a daily task rather then needing the developer to do it.

@ryanmitchell thanks for this. I think we need some documentation somewhere for this and also a test, as we don't want to make any mistakes with deleting carts.

Yep sorry I meant to ask where you'd want the docs to go - I wasnt sure where it best fitted.

Yep sorry I meant to ask where you'd want the docs to go - I wasnt sure where it best fitted.

It's a good point. I had started updated docs for this config area, I could do with merging what I've done so far. I'll review and get back to you.

Do you think create 2 commands and a documentation to add the command into app console kernal gives more flexibility to control how frequent it should be called.
The pipelines can be use to customize (eg: query cart older than X days) and sensible defaults being provided by lunar
also the query should be optimized with cursor fetch or paginated, and wrapped in DB::transaction

Any thoughts on this one? Im happy to add to the docs if you point me in the right direction.

Any thoughts on this one? Im happy to add to the docs if you point me in the right direction.

I would probably suggest adding something to https://docs.lunarphp.io/core/reference/carts.html

Thanks @glennjacobs. I've added some docs now.


Adding Fibaro Walli Outlet using S2 always gets down to S0 even using the correct DSK

Checklist

[X]  I am not using Home Assistant. Or: a developer has told me to come here.
[X] I have checked the troubleshooting section and my problem is not described there.
[X] I have read the changelog and my problem is not mentioned there.

Deploy method
Docker
Z-Wave JS UI version
8.5.0
ZwaveJS version
10.3.1
Describe the bug
Using a SiliconLabs Z-700 chip (Aeotec Z Pi 7)
Adding Fibaro Walli Outlet (FGWOE-011) only uses S0 though S2 is offered and the korrekt DKS key is entered.
This is somehow strange, because when using SimplicityStudio from Silicon labs, adding the Fibaro node works using S2 flawless. Note that you cant just use the inclusion from SS, you must use zwave2mqtt, else the node is not properly recognized by zwave2mqtt.

In September, I added the node the first time and made it to have a S2 security instant, but afterwards, as I removed the node for testing purposes, it never added with S2 again. Fully resetting the node does not change the behaviour. Interestingly it always shows all S2 capabilities and I can enter the DSK, but it never uses S2 but S0 only. Removing the checkmark to use S0, it does not include the node. But as SimplicityStudio CAN use S2, the issue is imho in zwave2mqtt and therefore I believe it is a bug.
I have an other node, Qubino 3 Phase Smart Meter where S2 is used on both SS and zwave2mqtt, also after removing and readding the node. Seems that there is something special going on in the communication with the Fibaro.
To Reproduce
Add, the node using S2. Remove the node and re-add it again should always use S2 when offered and the correct DSK has been entered. Checked with Simplicity Studio from Silicon Labs using the same controller where it works.
Expected behavior
Adding a node offering S2 should add it correctly when the right DSK has been entered independent if it was removed before.
Additional context
No response

Please attach zwave-js driver logs


include dwForceJump

            // force jump
            constexpr std::ptrdiff_t dwForceJump = 0x172F570;

Oh, thanks for letting me know. I didn't know it moved, and I ended up looking for it myself.


Add configuration to avoid generating pages for redirects

Right now, it basically copies the files, which is a bit excessive.

As I commented in #59, if we don't want to add an HTML meta refresh to simulate a redirect, then it might be nice to add a configuration that throws an error on redirects / doesn't follow redirects. Would you be open to a PR that adds a config to not follow redirects (and thus throw an error / warning for unexpected status codes)?
With such a config I can be sure to remove all flask.redirect calls from my site and manually create an HTML meta refresh template instead, preventing duplicate content from appearing on the site.


尝试在Cloudflare Workers上部署失败

首先在Cloudflare Workers上创建了新的Worker，然后用Cloudflare的Wrangler工具拉取到本地，然后克隆本仓库代码、安装依赖、构建：

git clone https://github.com/totravel/shadowsocks-ws.git
cd shadowsocks-ws
npm i
npm run build

在wrangler.toml中添加Cloudflare对Node.js的支持，参见：Node.js compatibility。

compatibility_flags = [ "nodejs_compat" ]
compatibility_date = "2024-09-23"

修改入口为构建的server.min.mjs。
执行npx wrangler deploy部署。

PS C:\Users\14485\Desktop\patient-block-457d> npx wrangler deploy

 ⛅ wrangler 3.95.0
-------------------

▲ [WARNING] "import.meta" is not available with the "iife" output format and will be empty [empty-import-meta]

    src/server.min.mjs:319:117686:
      319 │ ...R".red,...e);const Px=n(o(import.meta.url)),Bx="closed",Nx="op...
          ╵                              ~~~~~~~~~~~

  You need to set the output format to "esm" for "import.meta" to work correctly.

X [ERROR] Build failed with 3 errors:

  X [ERROR] Top-level await is currently not supported with the
  "iife" output format

      src/server.min.mjs:319:118657:
        319 │ ...));const{createServer:Qx}=Gx?await import("node:https"):await ...
            ╵                                 ~~~~~

  X [ERROR] Top-level await is currently not supported with the
  "iife" output format

      src/server.min.mjs:319:118684:
        319 │ ...x?await import("node:https"):await import("node:http"),Jx=Gx?Q...
            ╵                                 ~~~~~

  X [ERROR] Unexpected external import of "assert",
  "async_hooks", "buffer", "crypto", "events", "fs", "http", "https", "net", "node:console",
  "node:crypto", "node:events", "node:fs", "node:http", "node:https", "node:net", "node:path",
  "node:process", "node:stream", "node:timers/promises", "node:url", "os", "path", "querystring",
  "stream", "string_decoder", "tls", "tty", "url", "util", and "zlib".
  Your worker has no default export, which means it is assumed to be a Service Worker format Worker.
  Did you mean to create a ES Module format Worker?
  If so, try adding `export default { ... }` in your entry-point.
  See https://developers.cloudflare.com/workers/reference/migrate-to-module-workers/.
  [plugin hybrid-nodejs_compat]

▲ [WARNING] "import.meta" is not available with the "iife" output format and will be empty [empty-import-meta]

    src/server.min.mjs:319:117686:
      319 │ ...R".red,...e);const Px=n(o(import.meta.url)),Bx="closed",Nx="op...
          ╵                              ~~~~~~~~~~~

  You need to set the output format to "esm" for "import.meta" to work correctly.

🪵  Logs were written to "C:\Users\14485\.wrangler\logs\wrangler-2024-12-11_14-14-21_223.log"

--- 2024-12-11T14:14:21.349Z debug
🪵  Writing logs to "C:\Users\14485\.wrangler\logs\wrangler-2024-12-11_14-14-21_223.log"
---

--- 2024-12-11T14:14:21.348Z debug
Metrics dispatcher: Posting data {"deviceId":"5e262cf4-f15c-4b2b-92c3-ff4a2c9756f8","event":"wrangler command started","timestamp":1733926461348,"properties":{"amplitude_session_id":1733926461347,"amplitude_event_id":0,"wranglerVersion":"3.95.0","osPlatform":"Windows","osVersion":"Windows 11 Pro","nodeVersion":22,"packageManager":"npm","isFirstUsage":false,"configFileType":"toml","isCI":false,"isInteractive":true,"argsUsed":["j","xGradualRollouts","xJsonConfig","xVersions"],"argsCombination":"j, xGradualRollouts, xJsonConfig, xVersions","command":"wrangler deploy","args":{"xJsonConfig":true,"j":true,"xVersions":true,"xGradualRollouts":true,"noBundle":false,"latest":false,"keepVars":false}}}
---

--- 2024-12-11T14:14:21.356Z debug
.env file not found at ".env". Continuing... For more details, refer to https://developers.cloudflare.com/workers/wrangler/system-environment-variables/
---

--- 2024-12-11T14:14:21.401Z log

 ⛅ wrangler 3.95.0
-------------------

---

--- 2024-12-11T14:14:21.496Z debug
Retrieving cached values for account from node_modules\.cache\wrangler
---

--- 2024-12-11T14:14:21.496Z debug
Starting verifyWorkerMatchesCITag() with tag: undefined, name: patient-block-457d
---

--- 2024-12-11T14:14:21.496Z debug
No WRANGLER_CI_MATCH_TAG variable provided, aborting verifyWorkerMatchesCITag()
---

--- 2024-12-11T14:14:21.497Z debug
-- START CF API REQUEST: GET https://api.cloudflare.com/client/v4/accounts/78c3bb454d6f7b59a347ed40a1d9fde2/workers/services/patient-block-457d
---

--- 2024-12-11T14:14:21.497Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2024-12-11T14:14:21.497Z debug
INIT: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2024-12-11T14:14:21.497Z debug
-- END CF API REQUEST
---

--- 2024-12-11T14:14:22.774Z debug
-- START CF API RESPONSE: OK 200
---

--- 2024-12-11T14:14:22.774Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2024-12-11T14:14:22.774Z debug
RESPONSE: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2024-12-11T14:14:22.774Z debug
-- END CF API RESPONSE
---

--- 2024-12-11T14:14:22.775Z debug
-- START CF API REQUEST: GET https://api.cloudflare.com/client/v4/accounts/78c3bb454d6f7b59a347ed40a1d9fde2/workers/scripts/patient-block-457d/deployments
---

--- 2024-12-11T14:14:22.775Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2024-12-11T14:14:22.775Z debug
INIT: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2024-12-11T14:14:22.775Z debug
-- END CF API REQUEST
---

--- 2024-12-11T14:14:23.175Z debug
-- START CF API RESPONSE: OK 200
---

--- 2024-12-11T14:14:23.175Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2024-12-11T14:14:23.175Z debug
RESPONSE: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2024-12-11T14:14:23.175Z debug
-- END CF API RESPONSE
---

--- 2024-12-11T14:14:23.320Z log

---

--- 2024-12-11T14:14:23.323Z error
X [ERROR] Build failed with 3 errors:

  X [ERROR] Top-level await is currently not supported with the
  "iife" output format

      src/server.min.mjs:319:118657:
        319 │ ...));const{createServer:Qx}=Gx?await import("node:https"):await ...
            ╵                                 ~~~~~

  X [ERROR] Top-level await is currently not supported with the
  "iife" output format

      src/server.min.mjs:319:118684:
        319 │ ...x?await import("node:https"):await import("node:http"),Jx=Gx?Q...
            ╵                                 ~~~~~

  X [ERROR] Unexpected external import of "assert",
  "async_hooks", "buffer", "crypto", "events", "fs", "http", "https", "net", "node:console",
  "node:crypto", "node:events", "node:fs", "node:http", "node:https", "node:net", "node:path",
  "node:process", "node:stream", "node:timers/promises", "node:url", "os", "path", "querystring",
  "stream", "string_decoder", "tls", "tty", "url", "util", and "zlib".
  Your worker has no default export, which means it is assumed to be a Service Worker format Worker.
  Did you mean to create a ES Module format Worker?
  If so, try adding `export default { ... }` in your entry-point.
  See https://developers.cloudflare.com/workers/reference/migrate-to-module-workers/.
  [plugin hybrid-nodejs_compat]

---

--- 2024-12-11T14:14:23.327Z debug
Metrics dispatcher: Posting data {"deviceId":"5e262cf4-f15c-4b2b-92c3-ff4a2c9756f8","event":"wrangler command errored","timestamp":1733926463327,"properties":{"amplitude_session_id":1733926461347,"amplitude_event_id":1,"wranglerVersion":"3.95.0","osPlatform":"Windows","osVersion":"Windows 11 Pro","nodeVersion":22,"packageManager":"npm","isFirstUsage":false,"configFileType":"toml","isCI":false,"isInteractive":true,"argsUsed":["j","xGradualRollouts","xJsonConfig","xVersions"],"argsCombination":"j, xGradualRollouts, xJsonConfig, xVersions","command":"wrangler deploy","args":{"xJsonConfig":true,"j":true,"xVersions":true,"xGradualRollouts":true,"noBundle":false,"latest":false,"keepVars":false},"durationMs":1996,"durationSeconds":1.996,"durationMinutes":0.03326666666666667,"errorType":"BuildFailure"}}
---

换一种做法，直接把构建好的server.min.mjs文件替换默认Worker的worker.js文件，并且设置好兼容性标志nodejs_compat并设置环境变量，结果部署时报错：
Uncaught SyntaxError: Cannot use import statement outside a module at worker.js:1

shadowsocks-ws 还不能部署在 Cloudflare Workers。
之前，想要部署在 Cloudflare Workers 上的 Node.js 应用只能调用 Cloudflare Workers 特定的 APIs，不能使用 Node.js 内置模块，所以，作为传统的 Node.js 应用，shadowsocks-ws 无法适配到 Cloudflare Workers。
我没有注意到 Cloudflare Workers 现在已经开始为传统 Node.js 应用运行时提供支持。过些天我会抽空看看能不能适配。

edgetunnel和epeius都没有实现UDP支持，并且目前已经被Cloudflare识别，无法部署。我是因为这个才注意到shadowsocks-ws。

Cloudflare更新条款明确说明不得将其作为代理使用 也不得优选IP

近两年，多个 PaaS 平台先后取消免费额度、提高使用门槛或禁止代理服务。PaaS 平台通常都不支持 UDP。长期来看，个人部署终究还是得选择常规 VPS。现在 shadowsocks-ws 主要是供轻度用户部署在配有域名和证书的主机上，跟其他项目相比，或许已经没有什么优势了。

近两年，多个 PaaS 平台先后取消免费额度、提高使用门槛或禁止代理服务。PaaS 平台通常都不支持 UDP。长期来看，个人部署终究还是得选择常规 VPS。现在 shadowsocks-ws 主要是供轻度用户部署在配有域名和证书的主机上，跟其他项目相比，或许已经没有什么优势了。

羊毛薅秃了。VPS部署的话通常可以用v2ray-core这种功能更丰富的代理软件。


add time and size bounds

@DanielJMaher @oceanzus

@birdage Biride, it looks like you aren't using the streaming and chunking.

Merging and i'll fix myself

@DanielJMaher did you fix this then?

Fixing it in my next commit


Fix compat Error conversion

Latest failure(0.1.4) breaks failure Error to std Error (without send and sync) conversion. The changes are related to https://github.com/rust-lang-nursery/failure/pull/283
This PR adds:

2 smoke test cases for error conversion: Error to Box<StdError + Send + Sync> and Error to Box
add conversion from Error to Box back

Drat, sorry about that breakage. Thanks for the fix.

@davidbarsky @mitsuhiko if 0.1.4 breaks semver compatibility, perhaps it should be yanked (and the other changes published as 0.1.5)?

@lucab going to publish 0.1.5 now. Not sure if yanking is a good idea.

Yanking is definitely a good idea. It's a clear signal that it's broken. Yanking doesn't remove the package, it just hides it from public view. If someone has a dependency on 0.1.4 (in cargo.lock or whatever), it will still work properly.


Extend caching pre-condition to pre-cache too

Description
The intended change, motivation and consequences.
Notes
Optional observations, comments or explanations.
Tests

Server-side code should have automated tests
Client-side code and scripts should have at least a manual test plan
See also IDseq PR Guidelines

@gregdingle you requested explanation of the check that was missing -- see comment in ready_for_cache? method. Super exotic edge case

thanks for the follow up!

Actually I just realized this might mean pre-cache never happens. The last output_state may be loaded before the last Batch job completes. That will be the last incarnation of the result monitor for that sample, so it never gets a chance to do the pre-caching. I will need to think about this PR some more

Ah, I wasn't ready to merge yet!


Network can add multiple management

Describe the bug
Network can add multiple management,
expect
only one should be created

Validated


Web interface crashes on view

A second or two after viewing the glass interface the http process will crash and start over a few seconds later. When this happens this log entry is created.
Error: write EPIPE
    at WriteWrap.afterWrite [as oncomplete] (net.js:868:14)
events.js:183
      throw er; // Unhandled 'error' event
      ^

Error: write EPIPE
    at WriteWrap.afterWrite [as oncomplete] (net.js:868:14)

On Centos 7 with Node 8.15

Issue ended up being an IPS that was triggering a rule due to port 8080. I added an exception that resolved the issue. Closing issue.


Definition preview

Some participants in our usability study frequently used the functionality of the symbol search prototype to go find the green-highlighted sentence. These users participants thought it would be easier for them to use the tool if there was some visual aid (e.g., a tooltip) that showed them the highlighted sentence as soon as they clicked on a symbol.
This issue includes two steps:

[ ] Come up with a compelling design to satisfy this need. It might be a tooltip. It might just be a preview of the sentence that appears out-of-the-way, in the corner of the screen, which is easy to dismiss.
[ ] Implement that design.

Notes after playing around with prototypes of both designs:

I feel strongly that a tool tip is not the right direction it really does feel like it disrupts the flow of reading an equation that is even remotely long.
An out of the way tooltip does feel like a much better interaction however there is a caveat: it doesn't make much sense to display it when the green sentence is already visible on the page, however it also feels like it would be a bit strange if it didn't have the same interaction for every  symbol.

 Maybe something where we make the green sentence itself 'sticky' in that if a symbol is highlighted and the green sentence is out of view or scrolls out of view, the sentence turns into a floating tooltip. I also imagine this would be much harder to implement tho

Integrated in https://github.com/allenai/scholar-reader/commit/9b5c8aed2b672ef39a0de526106a59e46d854a2a.
One issue is that, in this commit, rendering gets pretty gummy when one clicks on the page. I'm not sure why.


[stable/k8s-event-logger] - latest chart not avaiable

There was an update to the stable chart for k8s-event-logger yesterday, but when accessing https://chart.deliveryhero.io/index.yaml the latest version still shows 1.1.7 instead of 1.1.8. Is there a delay in chartmuseum before the chart is available publically?

Yes, there's a temporary cache in place, see https://github.com/deliveryhero/helm-charts/issues/607, I'll hopefully have a fix today 🙏

@jaimin-shah-fs can you please check with the new OCI hosted chart: https://github.com/deliveryhero/helm-charts/tree/master/stable/k8s-event-logger#how-to-install-this-chart


Various panics fixes

Closes #67 and #56.

refactored message parsing
introduced custom message, request and response
fixed both panics
fixed response body processing

Could you please add some unit tests to functions?

Awesome work!


Container improvements

Hey guys, thanks for sharing your work! Just a couple of notes on how the container image can be improved. Unfortunately, currently the Wordpress installation is barely usable.
I made some improvements here: https://github.com/imankulov/docker-wordpress-ssh/blob/master/Dockerfile . I don't make a pull request, because I feel that probably some changes should be put there, whereas for some others tutum-docker-lamp is a better place.
In particular, what would cool to fix:

Update apache2 default config to make Wordpress .htaccess work (support of SEF urls, see https://github.com/imankulov/docker-wordpress-ssh/blob/master/apache-default).
Enable mod_rewrite (support of SEF urls)
change the ownership for the /app directory (unlock automatic updates, plugins, themes installation, etc)
Optionally install more php extensions, like curl and imagick.

Thanks.

@fermayo ssh access would be a nice addition indeed :+1:
I just sign-up to your platform, that looks amazing ! :)

Well, now we already have ssh... But no instructions on how to set it up! :(
I'm going with sudo docker exec -i -t loving_heisenberg bash for now.


gadgets/run: Add JSON output

gadgets/run: Add JSON output
This PR adds a new formatter which outputs json "through" the columns library.
This has the advantage that the columns and json output will always be aligned and the same. Additionally we won't need duplicate logic for the different output modes in the run gadget

I see this flattens the results! Great!

I rebased it to test it with https://github.com/inspektor-gadget/inspektor-gadget/pull/1702 and this is the output:
$ sudo IG_EXPERIMENTAL=true ./ig run --prog @./gadgets/trace_tcpconnect_x86.bpf.o --definition @./gadgets/trace_tcpconnect.yaml -o json
INFO[0000] Experimental features enabled
{
  "runtime": {
    "runtimeName": "docker", "containerId": "c00c1df110fa46c87deb793ae9de5321c0a2b0f6931dea6088829f5ac96fed3a", "containerName": "test-container"}, "node": "", "namespace": "", "pod": "", "container": "", "hostnetwork": false, "timestamp": "1970-01-01T00:00:00.000000000Z", "mntns":<PHONE_NUMBER>, "pid": 87921, "task": "wget", "uid": 0, "gid": 0, "version": 4, "src": "<IP_ADDRESS>", "dst": "<IP_ADDRESS>", "sport": 60550}
{
  "runtime": {
    "runtimeName": "docker", "containerId": "c00c1df110fa46c87deb793ae9de5321c0a2b0f6931dea6088829f5ac96fed3a", "containerName": "test-container"}, "node": "", "namespace": "", "pod": "", "container": "", "hostnetwork": false, "timestamp": "1970-01-01T00:00:00.000000000Z", "mntns":<PHONE_NUMBER>, "pid": 87921, "task": "wget", "uid": 0, "gid": 0, "version": 4, "src": "<IP_ADDRESS>", "dst": "<IP_ADDRESS>", "sport": 56216}

The format is strange and it doesn't have the k8s sub-struct 🤔

and it doesn't have the k8s sub-struct thinking

Since the K8sMetadata field in CommonData doesn't have a column name it will not show it as a substruct. This PR "retrieves" the JSON fields from the columns library. So the column name is important for this.

The problem with adding the column name to the K8sMetadata field in CommonData is that it implies adding K8S. prefix to all its columns: K8S.NODE, K8S.PODNAME, etc. It's okay for ig but not sure if it is what we want for kubeclt-gadget. I'm not sure how we want to manage this.
cc @mauriciovasquezbernal

WIP and proposal. Ideas really welcome :)
I just added another commit which adds some integration test helpers and modifies the test for TestRunTraceOpen.
We can't use the traditional functions for the containerized gadgets.
They were directly unmarshaling into the Event object which we don't have with containerized gadgets.
Most of the columns are dynamically created and therefore the output json is also mostly dynamic and depends solely on the BTF and config from the input.
So with this commit the expected entry is now a map[string]interface{} which gets constructed through RunEventToJsonObj(...) and MergeJsonObjs(...) where the actual payload of the eBPF program is merged into the json object returned by RunEventToJsonObj(...)
The rational behind creating helper functions such as SetEventTimestamp is that we can control the json path in a single location. So when the field changes in the future we don't have to change every test, only that function.

and it doesn't have the k8s sub-struct thinking

Since the K8sMetadata field in CommonData doesn't have a column name it will not show it as a substruct. This PR "retrieves" the JSON fields from the columns library. So the column name is important for this.

The problem with adding the column name to the K8sMetadata field in CommonData is that it implies adding K8S. prefix to all its columns: K8S.NODE, K8S.PODNAME, etc. It's okay for ig but not sure if it is what we want for kubeclt-gadget. I'm not sure how we want to manage this.
cc @mauriciovasquezbernal

IMHO it's okay to have the k8s substruct in JSON also for kubectl-gadget - in that environment it's maybe a bit too specific, but at least the 3rd party tools digesting that JSON can rely on the same data structure for both environments.

and it doesn't have the k8s sub-struct thinking

Since the K8sMetadata field in CommonData doesn't have a column name it will not show it as a substruct. This PR "retrieves" the JSON fields from the columns library. So the column name is important for this.

The problem with adding the column name to the K8sMetadata field in CommonData is that it implies adding K8S. prefix to all its columns: K8S.NODE, K8S.PODNAME, etc. It's okay for ig but not sure if it is what we want for kubeclt-gadget. I'm not sure how we want to manage this.
cc @mauriciovasquezbernal

IMHO it's okay to have the k8s substruct in JSON also for kubectl-gadget - in that environment it's maybe a bit too specific, but at least the 3rd party tools digesting that JSON can rely on the same data structure for both environments.

Yeah, it is already like that. The runtime and k8s substructs in JSON are already present for kubectl-gadget. The question is to add the K8S. prefix to the columns name in kubeclt-gadget.

and it doesn't have the k8s sub-struct thinking

Since the K8sMetadata field in CommonData doesn't have a column name it will not show it as a substruct. This PR "retrieves" the JSON fields from the columns library. So the column name is important for this.

The problem with adding the column name to the K8sMetadata field in CommonData is that it implies adding K8S. prefix to all its columns: K8S.NODE, K8S.PODNAME, etc. It's okay for ig but not sure if it is what we want for kubeclt-gadget. I'm not sure how we want to manage this.
cc @mauriciovasquezbernal

IMHO it's okay to have the k8s substruct in JSON also for kubectl-gadget - in that environment it's maybe a bit too specific, but at least the 3rd party tools digesting that JSON can rely on the same data structure for both environments.

Yeah, it is already like that. The runtime and k8s substructs in JSON are already present for kubectl-gadget. The question is to add the K8S. prefix to the columns name in kubeclt-gadget.

Ah, I see. We could add something like WithStripPrefixes("k8s") for the columns output (columnsformatter), if we want to get rid of it.

It's okay for ig but not sure if it is what we want for kubeclt-gadget. I'm not sure how we want to manage this.

It'd be better not to have it IMO. But if that's needed for this PR to work and removing it is difficult I'll just add.

What's the plan for the YAML support? If possible I'd like to remove the genericConverter (as it uses a different layout for the data, takes a bumblebee dependency, etc.). I think we can translate JSON to YAML. I see there are different options to do that ->https://pkg.go.dev/github.com/ghodss/yaml#JSONToYAML, https://github.com/itchyny/json2yaml. WDYT?
(For sure native YAML support would be better, but IMO that's too much work at this point)
WDYT @flyth ?

I also think we should opt for a generic converter for now - IMHO speed is much more important for JSON than for yaml.
https://pkg.go.dev/github.com/ghodss/yaml#JSONToYAML == https://github.com/kubernetes-sigs/yaml which we already import (it says "kubernetes-sigs/yaml is a permanent fork of ghodss/yaml."), so we could use just that.

What's the plan for the YAML support?

It turns out that using JSONToYAML is easier than I anticipated. Feel free to cherry-pick https://github.com/inspektor-gadget/inspektor-gadget/commit/a3c384f6652237721360f46035ababb6d87ebf71 so we implement that right away on this PR.

There is only one question left, (for later on)

Also, for the future, do we want to support omitempty?


Cuda array interface

Adding export code to #42

This is a detail but fc4cfa8addc10b82329c1b299f7b1abd7d1aba4a and 792d00e4bf4860367f69e5efede1698b121fcd05 could be squashed into a single commit. This PR will be merged for CudaCommon v2, after a first release of CudaCommon v1.2, based on ITK v5.4.1 and/or v5.4.2.


fix(linter): fix false positives in no-confusing-non-null-assertion

This lint did not check which operator was used, so it would warn you that a! + b looks too much like a !+ b, which doesn't make much sense.
  ! typescript-eslint(no-confusing-non-null-assertion): Confusing combinations of non-null assertion and equal test like "a! + b", which looks very similar to not equal "a !+ b".
     ,-[util.ts:115:19]
 114 |     coordEach(wrapped, (coord) => {
 115 |       coord[0] = (coord[0]! + 360) % 360
     :                   ^^^^^^^^^^^^^^^
 116 |     })
     `----
  help: Remove the "!", or prefix the "=" with it.

This patch adds tests for various binary operators and restricts the lint to only those that actually look like !=.

I recognize your OG name! Thank you for contributing!