Unable to start Minecraft Server in Docker

Describe the problem
The error is in this file:
2024-08-23-output.log.txt
Basically it errors out while trying to spin up for the first time.
Container definition
services:
  mc:
    image: itzg/minecraft-server
    ports:
      - "25566:25566"
    environment:
      EULA: "true"
      MOD_PLATFORM: AUTO_CURSEFORGE
      # allocate from https://console.curseforge.com/ and set in .env file
      CF_API_KEY: <<key goes here>>
      CF_PAGE_URL: https://www.curseforge.com/minecraft/modpacks/all-the-mods-9
      # Optional: select a specific version/file
      #CF_FILENAME_MATCHER: "0.2.34"
      MEMORY: 8G
    volumes:
      - mc-data:/data

volumes:
  mc-data: {}

Container logs
Log file is below

2024-08-23-output.log.txt

Is this the relevant problem?
Insufficient number of affixes to satisfy the loot rules

ATM9 used to work at least, but maybe there's new client mod exclusions needed with newest modpack. Speaking of which, be sure to re-pull the image to ensure latest global exclusions are used and temporarily set env var CF_FORCE_SYNCHRONIZE to "true".

I'm giving that a try with CF_FORCE_SYNCHRONIZE now

mc-1  | [21:12:23] [main/INFO] [Supplementaries/]: Loaded 27 flute songs
mc-1  | [21:12:23] [main/INFO] [Gateways to Eternity/]: Registered 7 gateways.
mc-1  | [21:12:23] [main/INFO] [Apotheosis : Enchantment/]: Registered 36 enchanting_stats.
mc-1  | [21:12:23] [main/INFO] [Apotheosis : Adventure/]: Registered 6 rarities.
mc-1  | [21:12:23] [main/INFO] [Apotheosis : Adventure/]: Registered 100 affixes.
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:uncommon for category wandRequired: 3; Provided: 1
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:rare for category wandRequired: 3; Provided: 1
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:rare for category wandRequired: 2; Provided: 1
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:rare for category curios:spellbookRequired: 2; Provided: 0
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:epic for category wandRequired: 4; Provided: 1
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:epic for category curios:spellbookRequired: 2; Provided: 0
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:mythic for category wandRequired: 4; Provided: 1
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:mythic for category helmetRequired: 3; Provided: 2
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:mythic for category bootsRequired: 3; Provided: 2
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:mythic for category wandRequired: 3; Provided: 2
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:mythic for category curios:spellbookRequired: 3; Provided: 0
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:common for category wandRequired: 2; Provided: 1
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category bowRequired: 5; Provided: 4
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category crossbowRequired: 5; Provided: 4
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category pickaxeRequired: 5; Provided: 4
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category shovelRequired: 5; Provided: 4
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category wandRequired: 5; Provided: 1
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category helmetRequired: 4; Provided: 2
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category bootsRequired: 4; Provided: 2
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category wandRequired: 4; Provided: 2
mc-1  | [21:12:23] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category curios:spellbookRequired: 4; Provided: 0
mc-1  | [21:12:23] [main/INFO] [Apotheosis : Adventure/]: Registered 34 gems.
mc-1  | [21:12:23] [main/INFO] [Apotheosis : Adventure/]: Registered 100 affix_loot_entries.
mc-1  | [21:12:23] [main/INFO] [Apotheosis : Adventure/]: Registered 39 bosses.
mc-1  | [21:12:23] [main/INFO] [Apotheosis : Adventure/]: Registered 8 rogue_spawners.
mc-1  | [21:12:23] [main/INFO] [Apotheosis : Adventure/]: Registered 5 minibosses.
mc-1  | [21:12:23] [main/INFO] [Apotheosis : Village/]: Registered 29 wanderer_trades.
mc-1  | [21:12:23] [main/INFO] [placebo/]: Registered 32 gear_sets.
mc-1  | [21:12:23] [main/INFO] [hostilenetworks/]: Registered 68 data_models.
mc-1  | [21:12:23] [main/INFO] [hostilenetworks/]: Registered 5 model_tiers.
mc-1  | [21:12:23] [main/WARN] [minecraft/MappedRegistry]: Not all defined tags for registry ResourceKey[minecraft:root / minecraft:worldgen/biome] are present in data pack: forge:none, totw_modded:has_structure/ratlantis_tower
mc-1  | [21:12:24] [main/INFO] [evilcraft/]: 19 Broom modifiers can be applied!
mc-1  | [21:12:27] [main/INFO] [zeta-internal/]: Dispatching ZTagsUpdated to 1 listener
mc-1  | [21:12:27] [main/INFO] [Moonlight/]: Applied 7 data villager trades
Gracefully stopping... (press Ctrl+C again to force)
request returned Bad Gateway for API route and version http://%2F%2F.%2Fpipe%2FdockerDesktopLinuxEngine/v1.46/containers/da46bf58f2d74323619ed34fc16a047f389bf0b3f8c784d6dd5b51bd9a3955c0/json, check if the server supports the requested API version

C:\Games\Docker>

Even after making sure all of the packages have updated, I'm having no luck. This is a brand new install. IDK what's going wrong here.
It just does the very long server load process and gives up at some point.

Yes, it's a modpack so it will have a fairly long startup time.  Durations have no impact on this type of recipe.
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_sword
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_sword
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_sword
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_sword
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_sword
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_sword
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_sword
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_sword
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_sword
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_sword
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_sword
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_sword
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_pick
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_pick
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_pick
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_pick
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_pick
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_pick
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_pick
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_pick
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_pick
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_pick
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_pick
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_pick
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_shovel
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_shovel
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_shovel
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_shovel
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_shovel
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_shovel
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_shovel
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_shovel
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_shovel
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_shovel
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_shovel
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_shovel
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_axe
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_axe
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_axe
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_axe
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_axe
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_axe
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_axe
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_axe
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_axe
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_axe
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_axe
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_axe
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_paxel
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_paxel
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_paxel
mc-1  | [22:14:47] [KubeJS Recipe Event Worker 0/WARN] [ars_nouveau/]: Use of deprecated recipe format in recipe ID: allthemods:allthemodium/alloy_paxel
mc-1  | /data/./run.sh: line 6:   195 Killed                  java @user_jvm_args.txt @libraries/net/minecraftforge/forge/1.20.1-47.2.20/unix_args.txt "$@"
mc-1  | 2024-08-24T22:15:01.911Z        WARN    mc-server-runner        Minecraft server failed. Inspect logs above for errors that indicate cause. DO NOT report this line as an error.        {"exitCode": 137}
mc-1  | 2024-08-24T22:15:01.926Z        INFO    mc-server-runner        Done
mc-1 exited with code 137

C:\Games\Docker> Desktop   o View Config   w Enable Watch

I think it got further that time.

Nothing was connected to the machine. No keyboard or anything like that.
mc-1  | [22:21:13] [main/INFO] [Caupona recipe generator/]: Building recipes...
mc-1  | /data/./run.sh: line 6:   193 Killed                  java @user_jvm_args.txt @libraries/net/minecraftforge/forge/1.20.1-47.2.20/unix_args.txt "$@"
mc-1  | 2024-08-24T22:21:38.460Z        WARN    mc-server-runner        Minecraft server failed. Inspect logs above for errors that indicate cause. DO NOT report this line as an error.        {"exitCode": 137}
mc-1  | 2024-08-24T22:21:38.481Z        INFO    mc-server-runner        Done
mc-1 exited with code 137

So weird.

"Killed" indication means something at operating system level killed it. Thats different than the manual stop I mentioned earlier.

You haven't mentioned any time frame for the startup so as a guess perhaps health check timeout needs to be adjusted
https://docker-minecraft-server.readthedocs.io/en/latest/misc/healthcheck/

Yeah that sounds promising. I'll look into it! Thanks!

Okay another failure... hmm... this time it was only a few minutes
mc-1  | [01:24:55] [main/INFO] [KubeJS Server/]: Scripts loaded
mc-1  | [01:24:55] [main/INFO] [KubeJS Server/]: Initializing recipe event...
mc-1  | [01:25:02] [main/INFO] [ne.mi.co.Co.apotheosis/COREMODLOG]: Replaced 2 calls to Enchantment#getMaxLevel() in net/minecraft/server/commands/EnchantCommand
mc-1  | [01:25:03] [main/INFO] [FTB Ranks/]: Loading command nodes...
mc-1  | [01:25:03] [main/INFO] [FTB Ranks/]: Loaded 4251 command nodes
mc-1  | [01:25:03] [main/INFO] [zeta-internal/]: Dispatching ForgeZAddReloadListener (as ZAddReloadListener) to 2 listeners
mc-1  | [01:25:03] [main/INFO] [quark-zeta/]: Dispatching ForgeZAddReloadListener (as ZAddReloadListener) to 2 listeners
mc-1  | [01:25:03] [main/INFO] [quark-zeta/]: Dispatching AdvancementModifierRegistry$1 (as ZGatherAdvancementModifiers) to 1 listener
mc-1  | [01:25:03] [Worker-Main-3/INFO] [KubeJS Server/]: [minecraft:worldgen/biome] Found 849 tags, added 8 objects, removed 0 objects
mc-1  | [01:25:03] [Worker-Main-3/ERROR] [minecraft/TagLoader]: Couldn't load tag alexsmobs:skreechers_can_spawn_wardens as it is missing following references: deeperdarker:otherside (from deeperdarker-forge-1.20.1-1.2.1.jar)
mc-1  | [01:25:03] [Worker-Main-3/ERROR] [minecraft/TagLoader]: Couldn't load tag totw_modded:has_structure/ratlantis_tower as it is missing following references: rats:ratlantis (from totw_modded-forge-1.20.1-1.0.5.jar)
mc-1  | [01:25:10] [Worker-Main-2/INFO] [KubeJS Server/]: [minecraft:entity_type] Found 231 tags, added 60 objects, removed 0 objects
mc-1  | [01:25:14] [Worker-Main-2/INFO] [KubeJS Server/]: [minecraft:fluid] Found 545 tags, added 2 objects, removed 4 objects
mc-1  | [01:25:14] [Worker-Main-3/WARN] [ar.Artifacts/]: Tag entries for curios:tags/items/magic_book.json cleared by tombstone-1.20.1-8.6.7.jar
mc-1  | [01:25:14] [Worker-Main-3/INFO] [KubeJS Server/]: tags.js#128: [minecraft:item] Found 8229 tags, added 197 objects, removed 6 objects
mc-1  | [01:25:14] [Worker-Main-3/ERROR] [minecraft/TagLoader]: Couldn't load tag ctov:wares/sealed_delivery_agreement as it is missing following references: wares:sealed_delivery_agreement (from [Forge]CTOV-v3.4.5.jar)
mc-1  | [01:25:14] [Worker-Main-1/INFO] [KubeJS Server/]: [minecraft:block] Found 2731 tags, added 745 objects, removed 0 objects
mc-1  | [01:25:14] [Worker-Main-3/ERROR] [minecraft/TagLoader]: Couldn't load tag ctov:wares/cardboard_box as it is missing following references: wares:cardboard_box (from [Forge]CTOV-v3.4.5.jar)
mc-1  | [01:25:14] [Worker-Main-1/WARN] [AlmostUnified/]: The following tags are invalid and will be ignored: [forge:ores/elementium, forge:ingots/apatite, forge:storage_blocks/raw_potassium_nitrate, forge:dusts/cloggrum, forge:nuggets/potassium_nitrate, forge:gems/amber, forge:wires/netherite, forge:nuggets/coal_coke, forge:gears/charcoal, forge:gears/coal, forge:gems/elementium, forge:wires/allthemodium, forge:ores/ender, forge:nuggets/charcoal, forge:rods/elementium, forge:wires/diamond, forge:wires/coal_coke, forge:ingots/chrome, forge:plates/cinnabar, forge:wires/cloggrum, forge:ingots/cinnabar, forge:storage_blocks/raw_invar, forge:nuggets/amber, forge:gems/steel, forge:dusts/aeternium, forge:wires/zinc, forge:dusts/elementium, forge:ores/calorite, forge:plates/bitumen, forge:ores/signalum, forge:wires/brass, forge:rods/aeternium, forge:gems/enderium, forge:rods/dragonsteel, forge:wires/horizonite, forge:raw_materials/charcoal, forge:storage_blocks/mithril, forge:gems/aeternium, forge:rods/crimson_iron, forge:plates/froststeel, forge:gems/electrum, forge:raw_materials/ender, forge:plates/azure_silver, forge:wires/falsite, forge:storage_blocks/raw_coal_coke, forge:nuggets/graphite, forge:gears/charoite, forge:gears/fluorite, forge:raw_materials/peridot, forge:dusts/bitumen, forge:raw_materials/twinite, forge:ores/steel, forge:gears/potassium_nitrate, forge:gems/cloggrum, forge:ores/bitumen, forge:ingots/coal_coke, forge:nuggets/apatite, forge:nuggets/charoite, forge:gears/graphite, forge:rods/desh, forge:gears/ender, forge:plates/coal, forge:rods/cloggrum, forge:nuggets/coal, forge:rods/ventium, forge:wires/ender, forge:dusts/aquite, forge:wires/aquite, forge:nuggets/fluorite, forge:nuggets/aquite, forge:raw_materials/steel, forge:dusts/mithril, forge:gears/amber, forge:gems/falsite, forge:gears/falsite, forge:gems/allthemodium, forge:ores/horizonite, forge:storage_blocks/raw_bitumen, forge:nuggets/sapphire, forge:gems/crimson_iron, forge:ingots/diamond, forge:gems/silver, forge:raw_materials/soul_infused, forge:gems/invar, forge:ingots/peridot, forge:wires/mithril, forge:ores/brass, forge:ores/aeternium, forge:wires/bronze, forge:wires/elementium, forge:gears/coal_coke, forge:gems/unobtainium, forge:gears/cloggrum, forge:dusts/froststeel, forge:gears/iesnium, forge:gems/ventium, forge:nuggets/ender, forge:nuggets/lapis, forge:dusts/ostrum, forge:plates/mithril, forge:gems/aquite, forge:plates/aeternium, forge:gears/froststeel, forge:rods/amber, forge:gems/cobalt, forge:wires/azure_silver, forge:ingots/lapis, forge:wires/iridium, forge:gems/horizonite, forge:gears/azure_silver, forge:gems/shellite, forge:ores/obsidian, forge:storage_blocks/raw_electrum, forge:rods/charcoal, forge:wires/silver, forge:ores/aquite, forge:gems/tin, forge:plates/crimson_iron, forge:raw_materials/tungsten, forge:wires/amber, forge:wires/tin, forge:gears/horizonite, forge:plates/cloggrum, forge:storage_blocks/raw_soul_infused, forge:nuggets/mithril, forge:raw_materials/shellite, forge:gems/tungsten, forge:gems/lead, forge:wires/rose_gold, forge:ingots/emerald, forge:rods/fluorite, forge:rods/azure_silver, forge:dusts/chrome, forge:raw_materials/coal_coke, forge:ores/mithril, forge:plates/aquite, forge:wires/sulfur, forge:gems/potassium_nitrate, forge:ores/charoite, forge:rods/potassium_nitrate, forge:gems/coal_coke, forge:storage_blocks/potassium_nitrate, forge:wires/cobalt, forge:ingots/ender, forge:gears/bitumen, forge:rods/soul_infused, forge:storage_blocks/amber, forge:ores/invar, forge:wires/bitumen, forge:raw_materials/lumium, forge:wires/aeternium, forge:gears/crimson_iron, forge:ores/desh, forge:nuggets/aeternium, forge:gems/dragonsteel, forge:raw_materials/bronze, forge:plates/falsite, forge:dusts/horizonite, forge:ores/electrum, forge:gems/aluminum, forge:wires/desh, forge:ores/rose_gold, forge:wires/graphite, forge:dusts/falsite, forge:gems/vibranium, forge:rods/falsite, forge:plates/sulfur, forge:gems/zinc, forge:ores/charcoal, forge:wires/dragonsteel, forge:wires/unobtainium, forge:wires/shellite, forge:raw_materials/chrome, forge:wires/lapis, forge:wires/tungsten, forge:gears/mithril, forge:ores/twinite, forge:plates/graphite, forge:wires/constantan, forge:storage_blocks/chrome, forge:raw_materials/brass, forge:rods/obsidian, forge:storage_blocks/raw_obsidian, forge:gears/cinnabar, forge:raw_materials/rose_gold, forge:wires/potassium_nitrate, forge:storage_blocks/raw_shellite, forge:gems/uranium, forge:plates/charcoal, forge:nuggets/cinnabar, forge:rods/ostrum, forge:ingots/amber, forge:wires/uranium, forge:dusts/amber, forge:raw_materials/potassium_nitrate, forge:gears/desh, forge:gems/chrome, forge:raw_materials/invar, forge:ores/bronze, forge:raw_materials/constantan, forge:wires/calorite, forge:gems/constantan, forge:storage_blocks/raw_bronze, forge:gears/ventium, forge:ingots/aeternium, forge:ores/soul_infused, forge:ores/enderium, forge:nuggets/chrome, forge:gems/iron, forge:ores/constantan, forge:dusts/ventium, forge:dusts/calorite, forge:gears/obsidian, forge:rods/coal_coke, forge:rods/chrome, forge:rods/graphite, forge:nuggets/obsidian, forge:wires/iesnium, forge:raw_materials/electrum, forge:wires/ostrum, forge:gems/ostrum, forge:storage_blocks/raw_charcoal, forge:storage_blocks/raw_rose_gold, forge:gems/netherite, forge:plates/charoite, forge:gems/nickel, forge:storage_blocks/ender, forge:ingots/bitumen, forge:ingots/fluorite, forge:gems/graphite, forge:plates/horizonite, forge:rods/netherite, forge:ingots/sapphire, forge:wires/chrome, forge:wires/invar, forge:plates/amber, forge:plates/apatite, forge:wires/froststeel, forge:gems/froststeel, forge:rods/ender, forge:plates/potassium_nitrate, forge:raw_materials/enderium, forge:nuggets/bitumen, forge:gems/bronze, forge:rods/froststeel, forge:storage_blocks/raw_ender, forge:gems/desh, forge:gems/brass, forge:wires/osmium, forge:gems/platinum, forge:wires/nickel, forge:storage_blocks/raw_brass, forge:storage_blocks/raw_dragonsteel, forge:ingots/charcoal, forge:gems/twinite, forge:rods/charoite, forge:wires/ruby, forge:ores/netherite, forge:plates/coal_coke, forge:gems/calorite, forge:rods/calorite, forge:storage_blocks/raw_chrome, forge:gears/peridot, forge:rods/coal, forge:gears/elementium, forge:plates/chrome, forge:wires/lumium, forge:wires/cinnabar, forge:dusts/desh, forge:nuggets/peridot, forge:gems/charoite, forge:raw_materials/obsidian, forge:gems/lumium, forge:rods/mithril, forge:gems/copper, forge:gems/iridium, forge:gears/aquite, forge:gears/calorite, forge:gems/iesnium, forge:rods/bitumen, forge:storage_blocks/raw_signalum, forge:gems/signalum, forge:wires/twinite, forge:rods/iesnium, forge:plates/peridot, forge:raw_materials/dragonsteel, forge:wires/platinum, forge:wires/soul_infused, forge:ores/shellite, forge:wires/vibranium, forge:storage_blocks/raw_peridot, forge:wires/obsidian, forge:storage_blocks/raw_aeternium, forge:storage_blocks/raw_lumium, forge:gems/soul_infused, forge:ingots/potassium_nitrate, forge:ingots/sulfur, forge:ingots/ruby, forge:ores/potassium_nitrate, forge:wires/charcoal, forge:storage_blocks/raw_enderium, forge:wires/ventium, forge:raw_materials/netherite, forge:storage_blocks/raw_mithril, forge:storage_blocks/raw_steel, forge:nuggets/sulfur, forge:plates/ender, forge:raw_materials/amber, forge:ores/ventium, forge:storage_blocks/raw_twinite, forge:gems/rose_gold, forge:storage_blocks/raw_constantan, forge:raw_materials/aeternium, forge:storage_blocks/aeternium, forge:ingots/charoite, forge:plates/ventium, forge:storage_blocks/raw_netherite, forge:rods/horizonite, forge:rods/sulfur, forge:rods/cinnabar, forge:wires/peridot, forge:nuggets/ruby, forge:ingots/mithril, forge:storage_blocks/raw_amber, forge:rods/shellite, forge:gears/chrome, forge:gems/gold, forge:storage_blocks/raw_tungsten, forge:ores/lumium, forge:gems/osmium, forge:ores/amber, forge:gems/bitumen, forge:ores/chrome, forge:gears/apatite, forge:rods/aquite, forge:rods/peridot, forge:gears/sulfur, forge:ingots/aquite, forge:gears/ostrum, forge:ores/falsite, forge:wires/signalum, forge:dusts/charoite, forge:ores/dragonsteel, forge:raw_materials/mithril, forge:ores/coal_coke, forge:ingots/coal, forge:wires/emerald, forge:plates/iesnium, forge:rods/twinite, forge:wires/charoite, forge:plates/fluorite, forge:raw_materials/bitumen, forge:raw_materials/signalum, forge:plates/elementium, forge:wires/crimson_iron, forge:ores/tungsten, forge:wires/apatite, forge:wires/coal, forge:gems/mithril, forge:gems/ender, forge:wires/fluorite, forge:gears/aeternium, forge:ores/ostrum, forge:gears/cobalt, forge:gems/obsidian, forge:gems/azure_silver, forge:wires/sapphire]
mc-1  | [01:25:14] [Worker-Main-1/INFO] [AlmostUnified/]: [TagOwnerships] Modified tag '#forge:gears/aluminum', added [gtceu:aluminium_gear]
mc-1  | [01:25:14] [Worker-Main-1/INFO] [AlmostUnified/]: [TagOwnerships] Modified tag '#forge:plastic', added [pneumaticcraft:plastic]
mc-1  | [01:25:14] [Worker-Main-1/INFO] [AlmostUnified/]: [TagOwnerships] Modified tag '#forge:dusts/aluminum', added [gtceu:aluminium_dust]
mc-1  | [01:25:14] [Worker-Main-1/INFO] [AlmostUnified/]: [TagOwnerships] Modified tag '#forge:plates/aluminum', added [gtceu:aluminium_plate]
mc-1  | [01:25:14] [Worker-Main-1/INFO] [AlmostUnified/]: [TagOwnerships] Modified tag '#forge:storage_blocks/raw_aluminum', added [gtceu:raw_aluminium_block]
mc-1  | [01:25:14] [Worker-Main-1/INFO] [AlmostUnified/]: [TagOwnerships] Modified tag '#forge:rods/aluminum', added [gtceu:aluminium_rod]
mc-1  | [01:25:14] [Worker-Main-1/INFO] [AlmostUnified/]: [TagOwnerships] Modified tag '#forge:raw_materials/aluminum', added [gtceu:raw_aluminium]
mc-1  | [01:25:14] [Worker-Main-1/INFO] [AlmostUnified/]: [TagOwnerships] Modified tag '#forge:storage_blocks/aluminum', added [gtceu:aluminium_block]
mc-1  | [01:25:14] [Worker-Main-1/INFO] [AlmostUnified/]: [TagOwnerships] Modified tag '#forge:ingots/aluminum', added [gtceu:aluminium_ingot]
mc-1  | [01:25:30] [Worker-Main-2/ERROR] [minecraft/SimpleJsonResourceReloadListener]: Couldn't parse data file productivebees:bee_conversion/neutronium_bee from productivebees:recipes/bee_conversion/neutronium_bee.json
mc-1  | com.google.gson.JsonParseException: java.io.EOFException: End of input at line 1 column 1 path $
mc-1  |         at net.minecraft.util.GsonHelper.m_13780_(GsonHelper.java:526) ~[server-1.20.1-20230612.114412-srg.jar%23887!/:?] {re:classloading,re:mixin}
mc-1  |         at net.minecraft.util.GsonHelper.m_263475_(GsonHelper.java:531) ~[server-1.20.1-20230612.114412-srg.jar%23887!/:?] {re:classloading,re:mixin}
mc-1  |         at net.minecraft.util.GsonHelper.m_13776_(GsonHelper.java:581) ~[server-1.20.1-20230612.114412-srg.jar%23887!/:?] {re:classloading,re:mixin}
mc-1  |         at net.minecraft.server.packs.resources.SimpleJsonResourceReloadListener.m_278771_(SimpleJsonResourceReloadListener.java:41) ~[server-1.20.1-20230612.114412-srg.jar%23887!/:?] {re:mixin,re:computing_frames,re:classloading,pl:mixin:APP:bookshelf.common.mixins.json:patches.packs.resources.MixinSimpleJsonResourceReloadListener,pl:mixin:A}
mc-1  |         at net.minecraft.server.packs.resources.SimpleJsonResourceReloadListener.m_5944_(SimpleJsonResourceReloadListener.java:29) ~[server-1.20.1-20230612.114412-srg.jar%23887!/:?] {re:mixin,re:computing_frames,re:classloading,pl:mixin:APP:bookshelf.common.mixins.json:patches.packs.resources.MixinSimpleJsonResourceReloadListener,pl:mixin:A}
mc-1  |         at net.minecraft.server.packs.resources.SimpleJsonResourceReloadListener.m_5944_(SimpleJsonResourceReloadListener.java:17) ~[server-1.20.1-20230612.114412-srg.jar%23887!/:?] {re:mixin,re:computing_frames,re:classloading,pl:mixin:APP:bookshelf.common.mixins.json:patches.packs.resources.MixinSimpleJsonResourceReloadListener,pl:mixin:A}
mc-1  |         at net.minecraft.server.packs.resources.SimplePreparableReloadListener.m_10786_(SimplePreparableReloadListener.java:11) ~[server-1.20.1-20230612.114412-srg.jar%23887!/:?] {re:mixin,re:computing_frames,re:classloading,pl:mixin:APP:moonlight.mixins.json:ConditionHackMixin,pl:mixin:A}
mc-1  |         at java.util.concurrent.CompletableFuture$AsyncSupply.run(Unknown Source) ~[?:?] {}
mc-1  |         at java.util.concurrent.CompletableFuture$AsyncSupply.exec(Unknown Source) ~[?:?] {}
mc-1  |         at java.util.concurrent.ForkJoinTask.doExec(Unknown Source) ~[?:?] {}
mc-1  |         at java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(Unknown Source) ~[?:?] {}
mc-1  |         at java.util.concurrent.ForkJoinPool.scan(Unknown Source) ~[?:?] {re:mixin,re:computing_frames}
mc-1  |         at java.util.concurrent.ForkJoinPool.runWorker(Unknown Source) ~[?:?] {re:mixin,re:computing_frames}
mc-1  |         at java.util.concurrent.ForkJoinWorkerThread.run(Unknown Source) ~[?:?] {re:mixin}
mc-1  | Caused by: java.io.EOFException: End of input at line 1 column 1 path $
mc-1  |         at com.google.gson.stream.JsonReader.nextNonWhitespace(JsonReader.java:1455) ~[gson-2.10.jar%2372!/:?] {}
mc-1  |         at com.google.gson.stream.JsonReader.doPeek(JsonReader.java:558) ~[gson-2.10.jar%2372!/:?] {}
mc-1  |         at com.google.gson.stream.JsonReader.peek(JsonReader.java:433) ~[gson-2.10.jar%2372!/:?] {}
mc-1  |         at com.google.gson.internal.bind.TypeAdapters$28.read(TypeAdapters.java:769) ~[gson-2.10.jar%2372!/:?] {}
mc-1  |         at com.google.gson.internal.bind.TypeAdapters$28.read(TypeAdapters.java:725) ~[gson-2.10.jar%2372!/:?] {}
mc-1  |         at com.google.gson.internal.bind.TypeAdapters$34$1.read(TypeAdapters.java:1007) ~[gson-2.10.jar%2372!/:?] {}
mc-1  |         at net.minecraft.util.GsonHelper.m_13780_(GsonHelper.java:524) ~[server-1.20.1-20230612.114412-srg.jar%23887!/:?] {re:classloading,re:mixin}
mc-1  |         ... 13 more
mc-1  | [01:25:30] [Worker-Main-2/ERROR] [minecraft/SimpleJsonResourceReloadListener]: Couldn't parse data file productivebees:bee_produce/neutronium_bee from productivebees:recipes/bee_produce/neutronium_bee.json
mc-1  | com.google.gson.JsonParseException: java.io.EOFException: End of input at line 1 column 1 path $
mc-1  |         at net.minecraft.util.GsonHelper.m_13780_(GsonHelper.java:526) ~[server-1.20.1-20230612.114412-srg.jar%23887!/:?] {re:classloading,re:mixin}
mc-1  |         at net.minecraft.util.GsonHelper.m_263475_(GsonHelper.java:531) ~[server-1.20.1-20230612.114412-srg.jar%23887!/:?] {re:classloading,re:mixin}
mc-1  |         at net.minecraft.util.GsonHelper.m_13776_(GsonHelper.java:581) ~[server-1.20.1-20230612.114412-srg.jar%23887!/:?] {re:classloading,re:mixin}
mc-1  |         at net.minecraft.server.packs.resources.SimpleJsonResourceReloadListener.m_278771_(SimpleJsonResourceReloadListener.java:41) ~[server-1.20.1-20230612.114412-srg.jar%23887!/:?] {re:mixin,re:computing_frames,re:classloading,pl:mixin:APP:bookshelf.common.mixins.json:patches.packs.resources.MixinSimpleJsonResourceReloadListener,pl:mixin:A}
mc-1  |         at net.minecraft.server.packs.resources.SimpleJsonResourceReloadListener.m_5944_(SimpleJsonResourceReloadListener.java:29) ~[server-1.20.1-20230612.114412-srg.jar%23887!/:?] {re:mixin,re:computing_frames,re:classloading,pl:mixin:APP:bookshelf.common.mixins.json:patches.packs.resources.MixinSimpleJsonResourceReloadListener,pl:mixin:A}
mc-1  |         at net.minecraft.server.packs.resources.SimpleJsonResourceReloadListener.m_5944_(SimpleJsonResourceReloadListener.java:17) ~[server-1.20.1-20230612.114412-srg.jar%23887!/:?] {re:mixin,re:computing_frames,re:classloading,pl:mixin:APP:bookshelf.common.mixins.json:patches.packs.resources.MixinSimpleJsonResourceReloadListener,pl:mixin:A}
mc-1  |         at net.minecraft.server.packs.resources.SimplePreparableReloadListener.m_10786_(SimplePreparableReloadListener.java:11) ~[server-1.20.1-20230612.114412-srg.jar%23887!/:?] {re:mixin,re:computing_frames,re:classloading,pl:mixin:APP:moonlight.mixins.json:ConditionHackMixin,pl:mixin:A}
mc-1  |         at java.util.concurrent.CompletableFuture$AsyncSupply.run(Unknown Source) ~[?:?] {}
mc-1  |         at java.util.concurrent.CompletableFuture$AsyncSupply.exec(Unknown Source) ~[?:?] {}
mc-1  |         at java.util.concurrent.ForkJoinTask.doExec(Unknown Source) ~[?:?] {}
mc-1  |         at java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(Unknown Source) ~[?:?] {}
mc-1  |         at java.util.concurrent.ForkJoinPool.scan(Unknown Source) ~[?:?] {re:mixin,re:computing_frames}
mc-1  |         at java.util.concurrent.ForkJoinPool.runWorker(Unknown Source) ~[?:?] {re:mixin,re:computing_frames}
mc-1  |         at java.util.concurrent.ForkJoinWorkerThread.run(Unknown Source) ~[?:?] {re:mixin}
mc-1  | Caused by: java.io.EOFException: End of input at line 1 column 1 path $
mc-1  |         at com.google.gson.stream.JsonReader.nextNonWhitespace(JsonReader.java:1455) ~[gson-2.10.jar%2372!/:?] {}
mc-1  |         at com.google.gson.stream.JsonReader.doPeek(JsonReader.java:558) ~[gson-2.10.jar%2372!/:?] {}
mc-1  |         at com.google.gson.stream.JsonReader.peek(JsonReader.java:433) ~[gson-2.10.jar%2372!/:?] {}
mc-1  |         at com.google.gson.internal.bind.TypeAdapters$28.read(TypeAdapters.java:769) ~[gson-2.10.jar%2372!/:?] {}
mc-1  |         at com.google.gson.internal.bind.TypeAdapters$28.read(TypeAdapters.java:725) ~[gson-2.10.jar%2372!/:?] {}
mc-1  |         at com.google.gson.internal.bind.TypeAdapters$34$1.read(TypeAdapters.java:1007) ~[gson-2.10.jar%2372!/:?] {}
mc-1  |         at net.minecraft.util.GsonHelper.m_13780_(GsonHelper.java:524) ~[server-1.20.1-20230612.114412-srg.jar%23887!/:?] {re:classloading,re:mixin}
mc-1  |         ... 13 more
mc-1  | /data/./run.sh: line 6:   188 Killed                  java @user_jvm_args.txt @libraries/net/minecraftforge/forge/1.20.1-47.2.20/unix_args.txt "$@"
mc-1  | 2024-08-25T01:25:46.312Z        WARN    mc-server-runner        Minecraft server failed. Inspect logs above for errors that indicate cause. DO NOT report this line as an error.        {"exitCode": 137}
mc-1  | 2024-08-25T01:25:46.340Z        INFO    mc-server-runner        Done
mc-1 exited with code 137

my docker-compose.yml
services:
  mc:
    image: itzg/minecraft-server
    ports:
      - "25566:25566"
    environment:
      EULA: "true"
      MOD_PLATFORM: AUTO_CURSEFORGE
      # allocate from https://console.curseforge.com/ and set in .env file
      CF_API_KEY: <valid key goes here>
      CF_PAGE_URL: https://www.curseforge.com/minecraft/modpacks/all-the-mods-9
      # Optional: select a specific version/file
      #CF_FILENAME_MATCHER: "0.2.34"
      #CF_FORCE_SYNCHRONIZE: true
      DISABLE_HEALTHCHECK: true
      MEMORY: 12G
    volumes:
      - mc-data:/data

volumes:
  mc-data: {}

Yeah it only gets through about [01:30:51] minutes worth of processing (1 minute and a half) before giving up.

Maybe it's this JSON file?
mc-1  | [01:30:51] [Worker-Main-1/ERROR] [minecraft/SimpleJsonResourceReloadListener]: Couldn't parse data file productivebees:bee_conversion/neutronium_bee from productivebees:recipes/bee_conversion/neutronium_bee.json

You might need to look at logs like this to see why system is killing the container process
https://docs.docker.com/engine/daemon/logs/
I'm running out of ideas 😬

time="2024-08-23T14:42:24.285075304Z" level=warning msg="Health check for container 4ab7b5f6caf73224d63bb114dc5e86f576c0d473123aa0c495129b60c80faa55 error: timed out starting health check for container 4ab7b5f6caf73224d63bb114dc5e86f576c0d473123aa0c495129b60c80faa55"
time="2024-08-23T14:42:24.529689315Z" level=error msg="stream copy error: reading from a closed fifo"
time="2024-08-23T14:42:24.531180215Z" level=error msg="stream copy error: reading from a closed fifo"
time="2024-08-23T14:42:25.009072436Z" level=info msg="ignoring event" container=4ab7b5f6caf73224d63bb114dc5e86f576c0d473123aa0c495129b60c80faa55 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
time="2024-08-24T19:14:50.298623575Z" level=info msg="ignoring event" container=2aedc2cbdc6f16e91818e0f94e4f0230fbf79d60fa359c0b7d91a80907eddfcc module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
time="2024-08-24T19:37:42.380001599Z" level=warning msg="Health check for container 21c430545dbc3d89a9649742dc62885ff3ff79cdabeab1733c8624994169ca76 error: timed out starting health check for container 21c430545dbc3d89a9649742dc62885ff3ff79cdabeab1733c8624994169ca76"
time="2024-08-24T19:37:43.003793197Z" level=info msg="ignoring event" container=21c430545dbc3d89a9649742dc62885ff3ff79cdabeab1733c8624994169ca76 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
time="2024-08-24T21:08:43.526681196Z" level=warning msg="Health check for container 21c430545dbc3d89a9649742dc62885ff3ff79cdabeab1733c8624994169ca76 error: timed out starting health check for container 21c430545dbc3d89a9649742dc62885ff3ff79cdabeab1733c8624994169ca76"
time="2024-08-24T21:08:43.922399022Z" level=info msg="ignoring event" container=21c430545dbc3d89a9649742dc62885ff3ff79cdabeab1733c8624994169ca76 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
time="2024-08-24T21:16:19.447147172Z" level=warning msg="Health check for container da46bf58f2d74323619ed34fc16a047f389bf0b3f8c784d6dd5b51bd9a3955c0 error: timed out starting health check for container da46bf58f2d74323619ed34fc16a047f389bf0b3f8c784d6dd5b51bd9a3955c0"
time="2024-08-24T21:16:19.457241679Z" level=error msg="attach failed with error: error attaching stdout stream: write unix /run/guest-services/docker.sock->@: write: broken pipe"
time="2024-08-24T21:16:19.573953260Z" level=error msg="stream copy error: reading from a closed fifo"
time="2024-08-24T21:16:19.574047660Z" level=error msg="stream copy error: reading from a closed fifo"
time="2024-08-24T21:16:20.014208763Z" level=info msg="ignoring event" container=da46bf58f2d74323619ed34fc16a047f389bf0b3f8c784d6dd5b51bd9a3955c0 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
time="2024-08-24T22:15:02.318938420Z" level=info msg="ignoring event" container=da46bf58f2d74323619ed34fc16a047f389bf0b3f8c784d6dd5b51bd9a3955c0 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
time="2024-08-24T22:21:38.877241232Z" level=info msg="ignoring event" container=da46bf58f2d74323619ed34fc16a047f389bf0b3f8c784d6dd5b51bd9a3955c0 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
time="2024-08-25T01:25:46.640077683Z" level=info msg="ignoring event" container=af3fc4d8c7766381499def403994d57e32bd9a10c29d6acd8342e540cd0b3330 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
time="2024-08-25T01:25:47.034133075Z" level=warning msg="Health check for container af3fc4d8c7766381499def403994d57e32bd9a10c29d6acd8342e540cd0b3330 error: container af3fc4d8c7766381499def403994d57e32bd9a10c29d6acd8342e540cd0b3330 is not running"
time="2024-08-25T01:30:59.738532328Z" level=warning msg="Health check for container 69b439e2cbdf42d187e8b76872a25f537062c85f0f54f9b885a936ffadc4c309 error: Canceled: context canceled"
time="2024-08-25T01:30:59.830307253Z" level=info msg="ignoring event" container=69b439e2cbdf42d187e8b76872a25f537062c85f0f54f9b885a936ffadc4c309 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"

Interesting. Maybe Docker for Windows 11 is having more issues than a linux host usually would.

I have the same starting issue with Linux server.

So I have the same "error message". However I am getting it later. Startup is fine but at some point whilst playing (usually between 5 to 30 minutes after startup) the above mentioned "Killed" message comes.
Used compose file:
version: "3.8"

services:
  mc:
    image: itzg/minecraft-server:java17
    tty: true
    stdin_open: true
    restart: unless-stopped
    ports:
      - "25565:25565"
    environment:
      EULA: "TRUE"
      TYPE: AUTO_CURSEFORGE
      # VERSION: 1.20.1
      CF_API_KEY: - redacted -
      CF_PAGE_URL: 'https://www.curseforge.com/minecraft/modpacks/all-the-mods-9-to-the-sky'
      MEMORY: 6G
    volumes:
      # attach the relative directory 'data' to the container's /data path
      - ./data:/data

I am running Docker on a linux machine however so I think this is not a Windows problem.

if you are using docker desktop it has a separate settings menu for memory if its below how much you told jvm that it can use it will exit with code 137

services:
  mc:
    environment:
      DISABLE_HEALTHCHECK: true

did the trick for me


get the sdk path to find the executable on linux

The method for running the PlaydateSimulator on Linux assumes that it's in your PATH. The desktop file that gets set up from the setup.sh script in the linux Playdate SDK just executes it from the SDK path, so I figure it's probably safe to do it the same way

Could we maybe have it try to execute PlaydateSimulator first and if that fails, then fallback to trying something based on the SDK path on all platforms?
This change would break running the simulator from crank on my system, but I admittedly have an uncommon setup so I can judt patch crank or work around this if generalizing this behavior is undesired by the maintainers

I think that's a good idea, I was considering making this change for all platforms, but noticed both Windows and Mac get some kind of installer, so I assumed there's less variability in the way the environments might be set up. I haven't tried the SDK on either Mac or Windows so I wasn't sure. I'll try a fallback for this cfg in the meantime

error: the feature lang_items is internal to the compiler or standard library

This is something new. Did I miss something? Is this feature was renamed or denied somehow? 🤔

LGTM, but what about error on CI? 🙄

Looks like it might be something new on nightly, I found this tracking issue for adding an internal_features lint, and based on the error message, it sounds like it's set to deny by default
https://github.com/rust-lang/compiler-team/issues/596

Looks like we're using stable toolchain instead of just installed nightly.

Seems to you're right 🙄

Updated on my machine, then tried adding an #![allow(internal_features)] to crankstart's lib.rs but that doesn't seem to have done it for me 😬

Looks like fixed:

job
PR

@lyonbeckers @lilyinstarlight important message


adding new resource types to the usage summary struct

We are splitting binary+tabular data outside of cloud storage and data_upload/egress into binary+tabular qualifiers. This is the change to show that new usage split on the usage panel on the billing admin.

@agreenb I added the new resource types for the data team too - can you just check that the types there are correct? Thanks!


getting errors about exported interfaces

Describe the bug
I have a typescript file (address.ts) that includes an exported interface (AddressProps). That interface is used elsewhere -- but the ladle app crashes on an uncaught syntax error when I try to start it, with an error message like
Uncaught SyntaxError: The requested module<EMAIL_ADDRESS>does not provide an export named 'AddressProps'

I suspect this has something to do with how ladle is processing typescript? I went in the browser and looked at the code in the dev app, and it is indeed true that the address.ts file in at<EMAIL_ADDRESS>has the declared export of the interface stripped out of it:

here's the start of the source file for reference:

Reproduction
I am unable to reproduce this in a a ladle sandbox, but this issue does not happen when I run storybook in the same codebase, and does not affect my published component library.
Environment

OS: macOS 12.6
Browser Chrome 106.0.5249.61 (Official Build) (x86_64)

Hey, can you create a github repo as a repro?


refactor: refactor storage module and add support for NumPy >= 2.0

Refactor the storage module to encapsulate the required functionality from array libraries to allocate memory buffers in a new concept, which simplifies the design at the same time by removing one layer.
Add:

New MemoryResourceHandler concept for low-level memory buffer handling, and two different implementations using NumPy and CuPy, which support newest changes in NumPy 2.0 interface
Basic unit tests for storage modules and a TODO note to migrate the old unit tests from cartesian

Change:

Rename type aliases for DeviceType literal values in _core.definitions
Unify the logic to deal with GPU allocation depending on CuPy being installed in the system  in storage.allocators instead of being duplicated in cartesian and next allocators

Delete:

The typing-only protocol ValidNumPyLikeAllocationNS from storage.allocators, which is not longer needed

Close in favor of #1563


How to set cell as text type?

In order to prevent DDE attack, how to set cell as text type?

I have same problem

but in my case I can't write percent like 2% it comes to 0,02. I dont know what is wrong with this

@905868332 need more detail (what export format? how are you reading data?).
@Juanryhn 2% is the cell { t: "n", v: 0.02, z: "0%" }.  If you are generating programmatically you can set the cell number format.

I solve it with option table_to_sheet raw = true
const ws = XLSX.utils.table_to_sheet(document.getElementById('tableBMForExcel'), { raw: true });

Import: For most formats, there is a distinct representation for string values.  The string =1+2 can be distinguished from the formula =1+2.  For CSV, by default =1+2 is stored as a numeric cell with a formula ({ t: "n", f: "1+2" }).  Passing the option raw: true treats all values as text:
> XLSX.read("=1+2,=3+4", {type: "string"}).Sheets.Sheet1
{
  A1: { t: 'n', f: '1+2' },
  B1: { t: 'n', f: '3+4' },
  '!ref': 'A1:B1'
}
> XLSX.read("=1+2,=3+4", {type: "string", raw: true}).Sheets.Sheet1
{
  A1: { t: 's', v: '=1+2' },
  B1: { t: 's', v: '=3+4' },
  '!ref': 'A1:B1'
}

Export: For most formats, passing a literal string value will generate text (e.g. { t: "s", v: "=1+2" } will be preserved)  For CSV, the behavior is identical to Excel by default (both the formula =1+2 and the text =1+2 will be mapped to the value =1+2).  Passing the option forceQuotes: true to sheet_to_csv will force quotes around each value:
> var ws = XLSX.read("=1+2,=3+4", {type: "string", raw: true}).Sheets.Sheet1
> XLSX.utils.sheet_to_csv(ws)
'=1+2,=3+4'
> XLSX.utils.sheet_to_csv(ws, {forceQuotes: true})
'"=1+2","=3+4"'


Fixes for ie 10 and 11 rendering of pdfs

When the fix is on staging, I can test it..
On Sun, Feb 15, 2015 at 9:49 PM, Chris Seto<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/CenterForOpenScience/osf.io/pull/1807
Commit Summary

Fixes for ie 10 and 11 rendering of pdfs

File Changes

M website/addons/base/views.py
https://github.com/CenterForOpenScience/osf.io/pull/1807/files#diff-0
(14)
M website/templates/project/view_file.mako
https://github.com/CenterForOpenScience/osf.io/pull/1807/files#diff-1
(10)

Patch Links:

https://github.com/CenterForOpenScience/osf.io/pull/1807.patch
https://github.com/CenterForOpenScience/osf.io/pull/1807.diff

—
Reply to this email directly or view it on GitHub
https://github.com/CenterForOpenScience/osf.io/pull/1807.


feat: add cheat_block_hash

Which component is your feature related to?
Forge
Feature Request
Add a cheatcode to cheat the block hash.

Is there even a syscall to get it though?

yes get_block_hash_syscall


Problem when one command calls another multiple times

Laravel Version
10.4.1
PHP Version
8.1.4
Database Driver & Version
No response
Description
When a command calls another command several times, with its signature, this is not reinitialized so the properties that are modified in the first call are found in the second
Steps To Reproduce
Run these commands
php artisan make:command Foo
php artisan make:command Bar
in Foo command put:
protected $signature = 'foo';

public function handle()
{
    $this->call('bar');
    $this->call('bar');
    $this->call('bar');
    return 0;
}

in Bar command put:
protected $signature = 'bar';

protected array $numbers = [];

public function handle()
{
    $this->numbers[] = rand(0, 100);
    dump($this->numbers);
}

Then run: php artisan foo

@driesvints then I don't particularly get why Illuminate\Console\Command@resolveCommand actually creates a new instance if you call the command via class name and not via signature. Is there a practical reason for that?


Webserver keeps freezing after plugged into Heating board

after an issue configureing the wifi, the board will freeze if plugged into the buderus heating board. The version is 0.0.8

Did you configure the GPIOs as mentioned in this discussion?
https://github.com/dewenni/ESP_Buderus_KM271/discussions/86

Setting the GPIO did the trick ;-) Sometimes I am blind :-D


Bring component integration test in line with ember-cli

This PR to ember-cli will likely be done soon and has a few differences from our implementation:

It generates a component integration test by default when generating a new component (and allows generating a unit test by specifying --unit)
It has a different argument (they use --test-type)

  availableOptions: [
    {
      name: 'test-type',
      type: ['integration', 'unit'],
      default: 'integration',
      aliases:[
        { 'i': 'integration'},
        { 'u': 'unit'},
        { 'integration': 'integration' },
        { 'unit': 'unit' }
      ]
    }
  ]

Once the ember-cli PR is merged I propose we bring this project back in sync. I will gladly submit a PR for this change.

Thanks for keeping track and working on this @blimmer!

:+1:
@blimmer Thanks, and sorry for any crossed wires!

No problem. Happy to see this taking priority!

The dependency branch was merged this morning. This can be worked whenever - I might be able to get to it this week(end)

@blimmer - Thank you!


HIVE-26445: Use tez.local.mode.without.network for qtests

What changes were proposed in this pull request?
This is to utilize the RPC free local DAGAppMaster introduced in TEZ-4236.
Why are the changes needed?
Because it makes unit tests stable by not starting a useless RPC in tez local mode.
Does this PR introduce any user-facing change?
No.
Is the change a dependency upgrade?
No.
How was this patch tested?
All tez based qtests.

I could not have reopened https://github.com/apache/hive/pull/3583, so this is the new PR


[BUG] A lot failed connections to full nodes on port 8444

Describe the bug
2021-06-16T23:27:40.000 full_node full_node_server        : INFO     Cannot connect to host <IP_ADDRESS>:8444 ssl:<ssl.SSLContext object at 0x7f19a1fb8ec0> [Connect call failed ('<IP_ADDRESS>', 8444)]
2021-06-16T23:27:43.181 full_node full_node_server        : INFO     -> handshake to peer <IP_ADDRESS> e981689bfb2da0184a2d5fefb23ec4c8598f0c9631dfaded860b7ca31dbba869
2021-06-16T23:27:43.237 full_node full_node_server        : INFO     Connected with full_node {'host': '<IP_ADDRESS>', 'port': 8444}
2021-06-16T23:27:43.238 full_node full_node_server        : INFO     -> new_peak to peer <IP_ADDRESS> e981689bfb2da0184a2d5fefb23ec4c8598f0c9631dfaded860b7ca31dbba869
2021-06-16T23:27:43.238 full_node full_node_server        : INFO     -> request_peers to peer <IP_ADDRESS> e981689bfb2da0184a2d5fefb23ec4c8598f0c9631dfaded860b7ca31dbba869
2021-06-16T23:27:43.239 full_node full_node_server        : INFO     Connection closed: <IP_ADDRESS>, node id: e981689bfb2da0184a2d5fefb23ec4c8598f0c9631dfaded860b7ca31dbba869
2021-06-16T23:27:43.239 full_node chaingreen.full_node.full_node: INFO     peer disconnected {'host': '<IP_ADDRESS>', 'port': 8444}
2021-06-16T23:27:47.066 full_node full_node_server        : INFO     -> handshake to peer <IP_ADDRESS> 027fd11177afddb767a65a27746d416df3a78d3b3ea833d6f5c84e9344bc3385
2021-06-16T23:27:47.268 full_node full_node_server        : INFO     Connected with full_node {'host': '<IP_ADDRESS>', 'port': 8444}
2021-06-16T23:27:47.268 full_node full_node_server        : INFO     -> new_peak to peer <IP_ADDRESS> 027fd11177afddb767a65a27746d416df3a78d3b3ea833d6f5c84e9344bc3385
2021-06-16T23:27:47.269 full_node full_node_server        : INFO     -> request_peers to peer <IP_ADDRESS> 027fd11177afddb767a65a27746d416df3a78d3b3ea833d6f5c84e9344bc3385
2021-06-16T23:27:47.270 full_node full_node_server        : INFO     Connection closed: <IP_ADDRESS>, node id: 027fd11177afddb767a65a27746d416df3a78d3b3ea833d6f5c84e9344bc3385
2021-06-16T23:27:47.270 full_node chaingreen.full_node.full_node: INFO     peer disconnected {'host': '<IP_ADDRESS>', 'port': 8444}

To Reproduce
Steps to reproduce the behavior:

Check the log: .chaingreen/mainnet/log/debug.log

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Linux
OS Version/Flavor: Ubuntu 20.04
CPU: Intel Xeon E3-1235L V3

Additional context
Add any other context about the problem here.

On Mac OS, syncronization constantly flies and the farm does not farm anything, blocks were won but the rewards never came.

Nodes are constantly falling off

Duplicate. Check here - https://github.com/ChainGreenOrg/chaingreen-blockchain/issues/17


Feature Request: Disable Desktop Notifications

It would be fantastic if you could disable all desktop notifications, forever. I don't want popups when running pb-for-desktop in Ubuntu - I simply want to SMS from my desktop with this.
Or ideally, have more options on which desktop notifications show up, and then I can choose SMS only.
Thanks!
🏡 Environmental Context
Operating System
Ubuntu

@clutchwave
This has just been shipped.
Looking forward to your feedback.


add check for healthy invoker to build-helm.sh

Use the controller's /invokers/healthy/count route to verify
that the controller has at least one healthy invoker before
attempting to proceed to the smoketest of invoking an action.

investigating travisci failure.  initial guess is that kube-deploy got out-of-synch with upstream repo while I was on vacation...

rebased to pick up fixes from #268


Alternate working directory configuration not respected (dbt_project.yml)

Is it possible to use this action template on dbt  when the dbt_project.yml file lives somewhere other than the root of the repository? If so, how to configure it? The below describes what I have attempted.
In a git action template, I am setting the working-directory for yu-iskw/action-sqlfluff@v3 as follows:
working-directory: ${{ github.workspace }}/dbt_transform_code

In the SQL Fluff configuration file, I've also experimented with setting the project_dir to '/home/runner/work/<repo-name>/<repo-name>/dbt_transform_code'
In either case, I see the following error from the git action run:
    File "/usr/local/bin/sqlfluff", line 8, in <module>
      sys.exit(cli())
    File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1130, in __call__
      return self.main(*args, **kwargs)
    File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1055, in main
      rv = self.invoke(ctx)
    File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1657, in invoke
      return _process_result(sub_ctx.command.invoke(sub_ctx))
    File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1404, in invoke
      return ctx.invoke(self.callback, **ctx.params)
    File "/usr/local/lib/python3.9/site-packages/click/core.py", line 760, in invoke
      return __callback(*args, **kwargs)
    File "/usr/local/lib/python3.9/site-packages/sqlfluff/cli/commands.py", line 830, in fix
      result = lnt.lint_paths(
    File "/usr/local/lib/python3.9/site-packages/sqlfluff/core/linter/linter.py", line 1164, in lint_paths
      for i, linted_file in enumerate(runner.run(expanded_paths, fix), start=1):
    File "/usr/local/lib/python3.9/site-packages/sqlfluff/core/linter/runner.py", line 142, in run
      for lint_result in self._map(
    File "/usr/local/lib/python3.9/multiprocessing/pool.py", line 870, in next
      raise value
  dbt.exceptions.DbtProjectError: Runtime Error
    no dbt_project.yml found at expected path /github/workspace/dbt_project.yml

Which appears to be telling me the process is looking for the dbt_project.yml file to exist at the root of the repository.

Is your dbt_project.yml located in somewhere other than the dbt project directory?
I test the actions with the workflow below. The working-directory input definitely works in my case.
https://github.com/yu-iskw/action-sqlfluff/blob/main/.github/workflows/test.yml#L36

Thanks for the response @yu-iskw . Yes, the dbt_project.yml is located in a directory called dbt_transform within the repo rather than at the root. Are you saying that the action template linked above works in this case, and can you please provide the name of the directory where the dbt_project.yml file lives?

https://github.com/yu-iskw/action-sqlfluff/blob/main/testdata/test_failed_dbt/dbt_project.yml

hey @yu-iskw , do you have a chance to test the same scenario with the dbt templater, instead of jinja?
INPUT_WORKING_DIRECTORY:
https://github.com/yu-iskw/action-sqlfluff/blob/2b313f10cc5db392bed833c57b7bac89775b2597/action.yml#L155
my hypothesis is, as we're CWD to INPUT_WORKING_DIRECTORY below, to install dbt deps;
https://github.com/yu-iskw/action-sqlfluff/blob/2b313f10cc5db392bed833c57b7bac89775b2597/entrypoint.sh#L55-L57
For the same reason, we may need to CWD to INPUT_WORKING_DIRECTORY before calling sqlfluff as well.
https://github.com/yu-iskw/action-sqlfluff/blob/2b313f10cc5db392bed833c57b7bac89775b2597/entrypoint.sh#L62-L80
could it be the reason?🤔


Added Greek Translation

Hi i hope i did follow the translation documentation steps correctly if an issue occured or i did a misstep please inform me
Best Regards
Nasos

Thank you!


Unable to install Qualys vulnerability solution on standard plan

Hi,
One of security centre recommendations we have is "Vulnerability assessment solution should be installed on your virtual machines".
According to the documentation we should be able to install a free licensed copy of Qualys, however when clicking through the recommendation we only appear to have an option to install Qualys or Rapid7 by providing our existing license key, which we obviously don't have.
The documentation implies I should be able to see a "Enable the built-in vulnerability assessment solution (powered by Qualys)" recommendation which is different to what I see. We're on the standard plan which is one of the prerequisites, though currently the free trial.
Am I missing something?
Thanks

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a9fbe6ca-1f70-657b-fc1a-c488335bdef6
Version Independent ID: 4962534a-ec5a-bc9a-f0ec-2074cf446807
Content: How to update to dynamic regulatory compliance monitoring in your Azure Security Center regulatory compliance dashboard
Content Source: articles/security-center/update-regulatory-compliance-packages.md
Service: security-center
GitHub Login: @memildin
Microsoft Alias: memildin

@akiller Thanks for your feedback! We will investigate and update as appropriate.

@akiller Sorry, closed by mistake. Thanks for your feedback! We will investigate and update as appropriate.

No problem!
I'm not sure if someone has fixed this but I just logged in and I can now see the "Enable the built-in vulnerability assessment solution on virtual machines (powered by Qualys) (Preview)" entry so it looks like it's now working.

@akiller ok. great.  thanks for letting us know.  We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Webpack does not include taGallery

I had to add ta-gallery in an existing project and the build process does not include the taGallery script for whatever reason.
I had to add the following lines to the main.js file to make the script work:
// Import taGallery
/* eslint-disable no-unused-vars */
import taGallery from '@markusantonwolf/ta-gallery/dist/js/ta-gallery-next';
/* eslint-enable no-unused-vars */

adding require('@markusantonwolf/ta-gallery') to the plugin section in tailwind.config.js was not enough.
Tailwind 3, Webpack 4

Thank you very much - I will add this to the documentation...


Use shorter prefixes in PSS tests to reduce test duration

PSS test duration depends on calculating the mined trojan chunk data. With the default settings it can take as much as 120 seconds. The idea is to use shorter prefixes to reduce the time it takes to run the PSS tests.

Bump.


how to use ignoreURLParametersMatching for run-time caching?

Library Affected:
workbox-sw, workbox-build, etc.
Hi @jeffposnick
I know it's possible to pass ignoreURLParametersMatching to precache so that it can ignore patterns in query string. I want to do the same thing, but for the run-time caching.
registerRoute(
    new RegExp('test'),
    new NetworkFirst({
        cacheName: config.app.cache_names.app_flags
    })
)

where do I put ignoreURLParametersMatching ? is it even possible ?

It's not possible to use ignoreURLParametersMatching directly as part of workbox-routing, but you can accomplish the same thing by using a matchCallback instead of a RegExp when defining your routes.
For example:
registerRoute(
  // This will match any request for /test?notIgnored=foo
  // with any other URL parameters effectively ignored.
  ({url, request}) => url.pathname === '/test' &&
                      url.searchParams.get('notIgnored') === 'foo',
  new NetworkFirst({cacheName: ...})
)

It's worth noting that we've recently updated our public documentation to prefer matchCallbacks instead of RegExps pretty much everywhere, as they're arguably simpler to think about. RegExps haven't been deprecated, though, so you're free to continue to use either.

So, my url looks like this.
https://example.com/insights?dateMin=484182831 . dateMin is gonna change for each time user refreshes the page. What happens now is everytime user refreshes the page, new entry gets added to the cache. If user goes offline, and refreshes the page, it won't find anything in cache since dateMin would be different timestamp each time..
With your proposed solution, I don't think it's gonna work..

In that case, don't check for dateMin in your matchCallback. The point of the example is that you can include a check for anything that you care about, and leave out a check for anything you don't care about.
You're also asking about something separate from routing, which is how to remove a URL parameter from a cache key before it's read/written to the cache.
Workbox has a cacheKeyWillBeUsed plugin callback that do that for you.
Taking both parts together, here's what you could go with:
async function cacheKeyWillBeUsed({request, mode}) {
  const url = new URL(request.url);
  return url.origin + url.pathname;
  // Any search params or hash will be left out.
}

registerRoute(
  // This will match any request for /test?notIgnored=foo
  // with any other URL parameters effectively ignored.
  ({url}) => url.origin === 'https://example.com' &&
             url.pathname === '/insights',
  new NetworkFirst({
    cacheName: 'my-cache-name,
    plugins: [{cacheKeyWillBeUsed}],
  }),
)

See https://github.com/GoogleChrome/workbox/issues/2316 and https://github.com/GoogleChrome/workbox/issues/2084 for similar discussions.

@jeffposnick  your example works like a charm.
One note BTW. I am using this for cross-origin request.
The line return url.origin + url.pathname; in cacheKeyWillBeUsed still results in only url.pathname.  Not the whole path with url.origin too. Any way I can achieve to make return url.origin + url.pathname; work too ?

Oh, hmm. I forgot that the request parameter passed to cacheKeyWillBeUsed might be a string, and isn't always a Request object, depending on how the underlying call to match() or put() ends up being made.
Try this:
async function cacheKeyWillBeUsed({request, mode}) {
  // Hardcode your cross-origin 'https://example.com' URL.
  const url = new URL(request.url || request, 'https://example.com');

  // Remove only paramToBeIgnored and keep other URL parameters.
  url.searchParams.delete('paramToBeIgnored');

  // Return the full remaining href.
  return url.href;
}


Update Trusty AI client to handle API changes (#1336)

Closes: #1336
Description

Update to the trusty client to handle the upcoming API changes described here: https://github.com/trustyai-explainability/trustyai-explainability/pull/186
How Has This Been Tested?

Run locally, made sure existing functionality was not broken.
Test Impact

Small, non visual change, no existing tests to update.
Request review criteria:

[X] The commits have meaningful messages (squashes happen on merge by the bot).
[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[X] The developer has manually tested the changes and verified that the changes work
[X] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

/approve

@alexcreasy I have removed your project and milestone -- we should track issues only in these things to avoid doubling down on items.


hybrid evasion/armour nodes not added to displayed increase

The hybrid evasion/armour nodes near Duelist do not increase the "inc armour" or "inc evasion" tallies in the tree statistics for increased armour and evasion.  Your evasion and armour goes up as it should, it's just not reported fully in the statistics.

The "%Inc X from Tree" stats in the sidebar are only intended to serve as a rough guide when building a tree; once gear and skills have been added you'll use the final computed Life/Evasion/etc values instead, so I haven't bothered making them count hybrid stats and such. I suppose I can fix that though, but I'll need to rework the code that sums those stats.

This is fixed in the next update.


Optimization of NSIndexSet.enumerate(batchSize: Int)

Problem:
We have to optimize the NSIndexSet.enumerate(batchSize: Int) because of too much complexity in it -> O(n)
Example:
If we try to fetch all emails we would do something like:
let range = NSRange(location: 1, length: Int.max - 1)
let indexSet = NSIndexSet(indexesInRange: range)

var results = [FetchResult]()
try imapSession.fetchMessages("INBOX", set: IMAPIndexes.indexes(indexSet), flags: [ .fullHeaders ]) { _ in }

Current result:
It takes too much time for a provider that have a batchSize == Int.max to create the only one indexset needed for the fetch.
Expected result:
Instant fetch
Possible solution:
We could try to use the Strideable protocol instead or simply optimize inside the method.

Is it really an issue ? because we have to generate a libetpan set afterwards. Having an infinite set is the base issue.

Agree but the problem still remains with the actual API.


Difference between alert(TB_WARNING, "..."); and tb_warning("...");

Both the alert(TB_WARNING,...) and procedure tb_warning("..."); seems to give identical log messages. When would you use one over the other? The only difference I see is that with alert you can control severity level, output to alert file, etc. But why do you have two different ways to output the same message?

Normally you would not use any of those procedures directly in your testbench, but rather checkers, awaits, etc. - where those procedures are included. There is no difference between the alert(tb_warning, ...) and tb_warning(...). The reason for having both are different historical needs.
-- Espen

TB_* is meant to be used when you know for sure that this alert is a pure testbench problem. For instance if you try to write a 16-bit value onto an 8-bit signal in a BFM. This could be useful information for the user. If you don't like this feature, you could just avoid using them in your own testbench.
-- Espen


[SPARK-15725][YARN] Ensure ApplicationMaster sleeps for the min interval.

What changes were proposed in this pull request?
Update ApplicationMaster to sleep for at least the minimum allocation interval before calling allocateResources. This prevents overloading the YarnAllocator that is happening because the thread is triggered when an executor is killed and its connections die. In YARN, this prevents the app from overloading the allocator and becoming unstable.
How was this patch tested?
Tested that this allows the an app to recover instead of hanging. It is still possible for the YarnAllocator to be overwhelmed by requests, but this prevents the issue for the most common cause.

Test build #59895 has started for PR 13482 at commit fde631b.

Test build #59895 has finished for PR 13482 at commit fde631b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59895/
Test PASSed.

@yhuai, @rxin, we should consider this work-around for 2.0 if it isn't too late. We see a lot of apps fail because the driver and AM lock up.

cc @vanzin @tgravescs

@rdblue could you follow the usual convention in the pr title ([SPARK-15725][yarn] Blah)? thx

Seems like an ok workaround to me; we really should spend some time looking at removing some of those locks and avoiding askWithRetry (which shouldn't ever be needed with a reliable RPC library like the one Spark uses).

@rdblue the reason for the hang is the GetExecutorLossReason right? AFAIK we send one to the AM every time an executor dies. What if we just keep a set of executor IDs we're waiting to kill on the driver (this might already exist) and query that before asking the AM? If a particular executor is in that set then we can just return ExecutorKilled.

I think this is important to fix for 2.0 but I personally found the changes in this patch rather confusing. If there's a simpler workaround we could do (such as the solution I suggested, if that works) then I would prefer that.

So why don't we just take out the notifyAll call when we get a GetExecutorLossReason?
We can add a parameter to resetAllocatorInterval() and resets the interval it but doesn't call the notify.  The most its going to sleep is the heartbeat interval (a few seconds), which doesn't seem bad to just get the lost reason. If they keep coming in the interval gets reset so it only sleep 200ms (default) on subsequent sleeps.
I guess you might end up with the same situation on the RequestExecutors,  but generally there I expect we request a bunch at a time and the allocation manager runs on a timer so those shouldn't be happens that frequently.
And we probably don't really need the notify on the requestExecutors call either but it its not hurting anything it could speed up requests a few seconds.

So why don't we just take out the notifyAll call when we get a GetExecutorLossReason?

If that helps it's ok too. It would probably increase a little bit the time for the driver to know why an executor failed, which can make some tasks take longer to be re-scheduled; but task failures because of executor loss aren't normal to start with, so it should be ok.

@andrewor14, I think we should consider two problems here: the fact that the thread will sleep for less than the min interval if something triggers it and whatever is currently triggering it. We should certainly fix the loss reason request that is currently triggering this behavior, but I still think that this patch is a good solution to the first problem in case there are other situations that cause it as well.
There's not a good reason to sleep for less than the min interval if it can cause the application to become unstable. We could look at a more complicated strategy -- like an exponentially increasing min interval up to the current min -- but the important thing right now is to ensure nothing can cause this instability.
To be clear, I don't consider this a complete fix for both of those problems. We should definitely avoid the askWithRetry, only signal the allocator thread when necessary, etc. But as a safety precaution, I think this patch is a good start.

We should probably decouple the task scheduling and the executor lost reason eventually, but that is a separate issue.
The only time I would see removing the notifyAll a problem is if they increase the heartbeat timeout to a very large number, but it would have to be close to the rpc timeout, which they just shouldn't do.   Otherwise a couple of extra seconds to reschedule the tasks in this failure case that is not the norm shouldn't be a problem and as soon as one happens, it goes down to the 200ms that this patch is suggesting anyway.
@rdblue  does removing the notifyAll call solve your problem as well?  That seems like a much cleaner approach then notifying but then sleeping some time again.

@tgravescs, removing notifyAll doesn't solve the problem entirely, it just removes one path that's causing the allocate call to be run too many times. (Also, I haven't tested delaying loss reasons in our Spark jobs at scale, other than for the 200ms introduced here.) Ensuring that allocate is not called too often addresses the problem no matter what the immediate cause is. That's why I think it's a good idea to fix the two separately: first ensure that allocate will not run too often and starve other operations on the YarnAllocator and, second, track down the cases that cause this.
Even if we were to fix the YarnAllocator so we don't have resource contention, ensuring a min interval between calls to allocate is a good idea so that Spark doesn't make too many useless calls to the resource manager. And, I don't want to track down this same bug in 3 months because of a different path trigger it.

Ok, I'm fine with this as a work around for now since you don't really know and this will ensure it, but please clean up the code so that its clear which sleep is which and add a nice comment stating why we are doing this.
Then I think we should file another jira to investigate a more proper fix for this.  We shouldn't have to wait for reason to schedule,

@rdblue can you address the comments? I would like to get this into the 2.0 rc1 if possible.

ping @rdblue do you have time to update this?

Test build #61117 has started for PR 13482 at commit e022408.

@tgravescs, I've updated it. Sorry about the delay, for some reason the notifications for this issue didn't make it to my inbox so I wasn't seeing updates.

Test build #61117 has finished for PR 13482 at commit e022408.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61117/
Test PASSed.

+1

@tgravescs, thanks for reviewing! Sorry about the delay!


Error with $path

I have only moved my site to a new server. I didn't touch anything.

Maybe it deals with php version?

I solve the problem by downgrading php from 7.2 to 5.6


WDL tasks in docker containers are missing DX environment variables

Hello,
I was creating a wdl that would access files directly from dnanexus something similar to:
task test{
   comand<<<
   python3 -c "import dxpy; list(dxpy.find_jobs())"
   >>>
    runtime{
        docker: "dockerimage"
        dx_access: object{
            Project: "CONTRIBUTE"
        }
    }
}

But the command fails with a permission error:
"Requires VIEW access to the project".
On further investigation adding source /home/dnanexus/environment to the command section  does seem to work.
I suspect adding this to the commandScript file or in containerRunScript would solve the problem.

At the moment, due to the security implications we do not recommend exposing your tokens to the container environment. I can not attest whether this will change soon to consider exposing application execution environment to the container and make it a default behavior. Maybe our product team may evaluate.


Marshal Class

Known Issues:

Forgot to add 	AddSpellTeleportPrepareStandard and AddSpellTeleportReconnectStandard to the auras
spell end needs review

Used Workarounds

As feats can't be marked as bonus feats only, I used args to handle new aura learning. Revisited once Class Features is availible
Spell Caster Level is discarded by the engine and set to 0. I assume because the Marshal can't cast spells and I just use the spell engine to handle the Auras and the Adrenaline Boost. Spell Level is now manually set in the "spells"

ToDo

Particle effects are not completed
Help file needs a revisit

Very nice!  I think you should update py00416standard_equipment_chest.py for the marshal.  Will look over it a bit more when I get a chance.

Very nice! I think you should update py00416standard_equipment_chest.py for the marshal. Will look over it a bit more when I get a chance.

Ty @doug1234
Will take a look at the standard equipment chest script, ty for pointing this out to me.


(#8062) Consider package epoch version when comparing yum package versions

By including the epoch version in the version returned as the "latest"
available, we can now properly consider package updates where only the
epoch version has changed.
Signed-off-by: Jude Nagurney<EMAIL_ADDRESS>Signed-off-by: Jacob Helwig<EMAIL_ADDRESS>

There's a comment in the install method "XXX: We don't actually deal with epochs here."
Is this wrong now (should be removed) or is it still the case for install and does that affect the functionality of this patch?

I'll take it out.  I don't think we actually need to do anything special since yum can understand packages with epochs in either name-epoch:ver-rel.arch or epoch:name-ver-rel.arch form, and the former should just work if people wish to specify the epoch as part of the ensure value instead of as part of the name.
package { 'foo':
  ensure => '1:1.2.3',
  provider => 'yum',
}

vs
package { '1:foo':
  ensure => '1.2.3',
  provider => 'yum',
}


changes to UI

@ldanzinger please take a look at the UI updates for this sample

Looks good. Nice work


added test for pywrap FastPathExecute using MatMul and tensors of dif…

tensors of different shapes (version 2 to fix CLA)
@saxenasaurabh

@amturati Can you please check @alextp's comments and keep us posted. Thanks!


Add CNCF case studies

Add 5 CNCF case studies

@marcduiker Does this need the grafana image added?

The Grafana image was already part of the repo, so it's good!


min/max interval size?

Hey,
can we set min/max interval size?
P.S. nice plugin :)

Currently not, but surely that'd be a nice addition.
Will work on it in near future, in the mean while if you implement that don't forget to send a PR. :)

Using a setTimeout() for waiting 2-3 seconds in onstatechange: function() will be better, because user needs time to move the ball to the value he wants.
ps. Thank your plugin, it is great, I'm using it in my project.

the setTimeout can ofcourse be used in your own onstateChanged listener ;). so you can implement it yourself without changing the code.


Drop formula step Averager

This is dropped because it is a relic from the very early days, and not used at all, and not even exposed to the public.

Sorry, I do not remember the discussion. :disappointed:
Maybe the commit description and the release can have more context about why this is being dropped?

Sorry, I do not remember the discussion. 😞

Sorry @tiyash-basu-frequenz. I meant @sahas-subramanian-frequenz. it was right next at my desk. But it doesn't matter too much. :)
IIRC, this is dropped because it is a relic from the very early days, and not used at all, and not even exposed to the public. And the latter is the reason why I did not add a release notes item, because it's not publically facing :)

@sahas-subramanian-frequenz can you give more context? Is it buggy? Are there other problems related to it? IMO it's a useful operation to have.

as discussed with @tiyash-basu-frequenz,

It would be nice to clarify what you discussed so other can know the reasoning behind this change, it is pretty mysterious then put like this :)

BTW, if that reason was not accurate (it has a IIRC), please update the body with the current/correct one. Also remember that PR bodies are used as merge commit messages, so try to write those as you would write a commit message.

I'm afraid I'd be getting the wording wrong. So without shooting myself into my foot, maybe @sahas-subramanian-frequenz knows the best :-)

The Averager step was a quick hack made to provide an average soc stream from the logical meter.  This was a temporary measure, until soc was available from the battery pool.  That requirement is now gone, and for the reasons listed below, it can't be made a part of the public API,  so it must be removed.
The Averager step has a number of issues that make it harder to integrate into our formula engine setup:

it takes only receivers
it can't be composed with other steps, and has to be the only step in a formula.
it doesn't decompose to a binary operation like max/min can, i.e avg(4, 5, 6) is not the same as avg(avg(4, 5), 6), so it can't be integrated into our postfix expression evaluator.

All the above can be changed, but not without sacrificing something.  But we should limit the proliferation of steps that don't fit together, and can be flaky if we try to force them to work with other operations,  and where every such operation needs special treatment from the developers.  Especially for steps for which we don't have a clear use-case.
What we really need is a new design concept based on a tree-walking evaluator, that would allow for the composition of arbitrary operations - binary or otherwise, seamlessly, without causing additional async cycles,  just from adding an implementation for the operation,  without having to touch implementation internals, like we're having to do operator priority in the current expression evaluator.

I would say put this in the PR description:

The Averager step was a quick hack made to provide an average soc stream from the logical meter.  This was a temporary measure, until soc was available from the battery pool.  That requirement is now gone, and for the reasons listed below, it can't be made a part of the public API,  so it must be removed.
The Averager step has a number of issues that make it harder to integrate into our formula engine setup:

it takes only receivers
it can't be composed with other steps, and has to be the only step in a formula.
it doesn't decompose to a binary operation like max/min can, i.e avg(4, 5, 6) is not the same as avg(avg(4, 5), 6), so it can't be integrated into our postfix expression evaluator.

All the above can be changed, but not without sacrificing something.  But we should limit the proliferation of steps that don't fit together, and can be flaky if we try to force them to work with other operations,  and where every such operation needs special treatment from the developers.  Especially for steps for which we don't have a clear use-case.

And maybe create a new issue with this?

What we really need is a new design concept based on a tree-walking evaluator, that would allow for the composition of arbitrary operations - binary or otherwise, seamlessly, without causing additional async cycles,  just from adding an implementation for the operation,  without having to touch implementation internals, like we're having to do operator priority in the current expression evaluator.

This still has release notes conflicts.


docs: change config.get() to object

Ref.: https://github.com/ipfs/js-ipfs-api/issues/822

@diasdavid @alanshaw what do you think? 😄


[RESOLVED] High ICMP ping response time

Problem started at 07:32:29 on 2023.04.19
Problem name: High ICMP ping response time
Host: HP_iLO
Severity: Warning
Operational data: Value: 652ms
Original problem ID: 19546
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23268&eventid=19546

Problem has been resolved in 1m 0s at 07:33:29 on 2023.04.19
Problem name: High ICMP ping response time
Host: HP_iLO
Severity: Warning
Original problem ID: 19546


fixconvert to s3 path when use aws endpoint

Proposed changes
Convert to s3 path when use aws endpoint
For compatibility， we can also use s3 client to access other cloud by setting s3 endpoint properties

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 47.92 seconds
stream load tsv:          512 seconds loaded<PHONE_NUMBER>9 Bytes, about 139 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.4 seconds inserted 10000000 Rows, about 340K ops/s
storage size:<PHONE_NUMBER>7 Bytes

run buildall

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 45.14 seconds
stream load tsv:          538 seconds loaded<PHONE_NUMBER>9 Bytes, about 132 MB/s
stream load json:         21 seconds loaded<PHONE_NUMBER> Bytes, about 107 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.3 seconds inserted 10000000 Rows, about 341K ops/s
storage size:<PHONE_NUMBER>0 Bytes

run p0

run buildall

run clickbench

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 44.77 seconds
stream load tsv:          536 seconds loaded<PHONE_NUMBER>9 Bytes, about 133 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          97.0 seconds inserted 10000000 Rows, about 103K ops/s
storage size:<PHONE_NUMBER>0 Bytes


feat: introduce InRegion pre-built Configurations

This commit introduces a first attempt at a pattern for providing the InRegion pre-built Configurations.  We needed a slightly different pattern here since these configurations are nested one level more deeply inside of the Configurations namespace.

had to rebase


Update to the latest pre-release version of xunit

This should improve testing performance a bit.

LGTM. I tested this yesterday and it works for me. But I couldn't really notice big performance boost unfortunately.

I'm seeing ~30% faster to discover tests after I rebuild.


[FEATURE REQUEST]: Sphinx Documentation for Packager, Geoprocess

@adamscarberry , can you please take a look at the Sphinx docs (review)?

Sphinx documentation moved to Mkdocs.  Sphinx and jekyll not playing well together with the current docs setup for components of cumulus-api.  YAML and Markdown bases for documentation configuration.  Geoprocess and Packager documentation pages updated with Mkdocs.


Use dedicated path for WebDAV deployment.

Fixes "Failed getting intermediate path at http://localhost:4502/apps/.
Reason: Forbidden"
This closes #1726

Thanks


(AzureCXP) fixes MicrosoftDocs/azure-docs#100646

Performed changes line no 66
changed from
override
changed to
overridden

Learn Build status updates of commit 5af5dcb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/active-directory/authentication/howto-authentication-temporary-access-pass.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Add support for voting on polls

As far as I can see, the docs outline methods for creating polls but not voting on already-created polls and observing their states.
Is this something which could be implemented?

As this can be done in the web ui by regular facebook users, there's no reason this couldn't be implemented.
As usual, implementing a feature like this involves performing the action in the browser while observing the requests being sent using browser devtools, then replicating the requests in the api code. I would imagine that voting would be similar to the createPoll code.
We're happy to support anyone who is trying to investigate this 😄

First a foremost, does the poll creation return some form of ID?

Our api currently doesn't return a poll id afaik. If there is something we should be returning, we can definitely accept a change to do that 😄


Add Confio to the cosmos-rust governing team

This is our first governance vote for expanding the maintaining team. I would like to invite Confio to the governance process of this repo.
This includes having one member on the Crates.io maintainer list of cosmos-sdk-proto (and future crates published from this repo) as well
as being added to this list of teams capable of seconding a change before merge (as outlined in the readme) and given push access to make
branches.

https://github.com/orgs/cosmos/teams/confio_cosmos-rust-write/members


Add create_task function

Fixes #69
This PR adds the ability to create new tasks and save them to the DB.
Changes you made

Add a function "create_task" to add task to DB
Add tests for the above function
Remove dummy test

I know, I'm on it.

Sorry for the force push, had some issues with update from main ..

Please change the PR description to be meaningful. For example: "this PR adds the ability to ..." or "this PR fixes a bug where ..." or "this PR changes the way we do ... because ..."

Done

Resolved everything.
Note that there will be conflicts when merging #74 and #83, so please after merging one of them, wait so I will resolve the conflicts (the conflicts are only because I worked on the same model file)

@orzionpour Let us know which one you want to merge first. #74 or #83

@natifridman doesn’t matter which one, after merging one of them i’ll let you know when the second is ready. Thanks


App provider: public link user is displayed as the sharing user in the office app

Describe the bug
The public link user is displayed as the original sharing user in the office app.
Steps to reproduce
Steps to reproduce the behavior:

einstein creates a public share of documents
open office files on the public link

Expected behavior
the user is called "anonymous"
Actual behavior
the user is called "einstein"
https://user-images.githubusercontent.com/34452982/139468892-aeecf955-278b-4835-b2c4-14ec6a0d483c.mp4

@wkloucek @C0rby  can we change the displayname in the token?

probably fixed by https://github.com/cs3org/reva/blob/32b439e51b946d0d1089f5bcb21135fad59b0574/pkg/app/provider/wopi/wopi.go#L141-L158, will need to check

Yeah, good question how.
The problem is that for shares the share creator/owner gets impersonated, that is why the applications show their name.

No longer the case


How to make logs optional on/off ?

In this case I want to NOT show logs on PRODUCTION and have the ability to turn logging on or OFF?
Any suggestion ?

Hi James, I've done some changes on my PR.
Kind Regards,
Renato Cardoso
On 26 April 2018 at 10:53, Justin Kames<EMAIL_ADDRESS>wrote:

Closed #9 https://github.com/justinkames/vuejs-logger/issues/9.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/justinkames/vuejs-logger/issues/9#event-1595953272,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACyPpVHav3fOGx3V0hDeySnhyryFsFOqks5tsYsMgaJpZM4TjXeG
.


Add local database support so that the feature for observing the real time database change without using fetch query

ATTENTION: DO NOT USE THIS FIELD TO ASK SUPPORT QUESTIONS. USE THE PLATFORM CHANNELS FOR THIS. THIS SPACE IS DEDICATED ONLY FOR FEATURE REQUESTS
Is your feature request related to a problem? Please describe.
I want to fetch the data from database but by the time query run and get the data from database, the data is not filled in database and the query will return 0 records. So there should be a mechanism where i can observe the database changes and reflect on ui without fetching query till the data records return greater than 0.
Describe the solution you'd like
On App launch I want to get the list of users from server and insert it to database. By the time user reaches to home screen of app and if the data is not inserted in database the fetch query on home screen return 0 records and I need to query again to fetch the data from database. So in order to avoid using the fetch query again and again till the records count is greater than 0. There should be a live data observer which observe changes in database and update Ui accordingly.
Describe alternatives you've considered
using stream
fetching data again

I don't think this is a getx problem. You may have to change your db client (hive ro sqflite) to sqlbrite or any other db that supports reactive stream.

How to use the reactive stream via floor database in order to fetch the data with Getx widegt?


shorten-links should apply also after you edit your comment

Edit one of your comments containing a URL
Save it
Notice that the links are no longer shortened by the shorten-links feature.

How to fix this

My other extension https://github.com/bfred-it/github-issue-link-status correctly re-applies the changes when you edit your comment, so the code can probably be copied from there
This should probably be part of on-new-comments.ts so all related features benefit from it.

I have no freakin clue what im supposed to say! But I'll say sorry. I can do better. But ive got truck broke down and start job tomm. Have to ride bike to get part. I make mistakes. I'm human.

Duplicate of https://github.com/sindresorhus/refined-github/issues/2572

This should follow https://github.com/sindresorhus/refined-github/pull/2992

This issue seems very interesting!
I did a little bit of digging, and it looks like the shorten-links feature is not being applied to the newly added comments as well. Based on the description of this issue, it sounds like it should, right?
And should shorten-links feature include onNewComments listener or indicate that the page has comments?
Adding this to the shorten-links seems to "fix" the issue for links in the comments. However, it may not work for links outside of the comment/discussion box.
include: [
 pageDetect.hasComments
]

I am pretty new to repo so I might not be heading in the right direction, right away, haha.

If include is missing, it will be applied to every page. Adding it might fix it because explicitly specifying that automatically includes onNewComments.
You can try just adding onNewComments like in: https://github.com/sindresorhus/refined-github/blob/0fa514dbeeab6395ef095cff80beac41443a6574/source/features/hide-inactive-deployments.tsx#L28