EULA Environment variable not taken into account during startup of CurseForge modpack

Describe the problem
Server does not start and is stuck at the "eula not accepted" message.
atm7.zip is the ATM7 server files renamed.
The startup goes well until that moment:
mc_1  | [11:52:40] [main/INFO]: You need to agree to the EULA in order to run the server. Go to eula.txt for more info.
I also have checked every eula.txt found in the data folder and they all have the eula=TRUE line.
Container definition
version: "3"

services:
  mc:
    image: itzg/minecraft-server
    ports:
      - 25565:25565
    environment:
      EULA: "TRUE"
      TYPE: "CURSEFORGE"
      CF_SERVER_MOD: "atm7.zip"
    tty: true
    stdin_open: true
    restart: unless-stopped
    volumes:
      # attach a directory relative to the directory containing this compose file
      - ./minecraft-data:/data

Container logs
mc_1  | [11:51:52] [INFO] Starting Loader, output incoming
mc_1  | [11:51:58] [main/INFO]: ModLauncher running: args [--launchTarget, forgeserver, --fml.forgeVersion, 39.0.43, --fml.mcVersion, 1.18.1, --fml.forgeGroup, net.minecraftforge, --fml.mcpVersion, 20211210.034407, nogui]
mc_1  | [11:51:58] [main/INFO]: ModLauncher 9.0.7+91+master.8569cdf starting: java version 17.0.1 by Eclipse Adoptium
mc_1  | [11:52:00] [main/INFO]: SpongePowered MIXIN Subsystem Version=0.8.5 Source=union:/data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/libraries/org/spongepowered/mixin/0.8.5/mixin-0.8.5.jar%2319! Service=ModLauncher Env=SERVER
mc_1  | [11:52:06] [main/INFO]: Found mod file [1.18.1] SecurityCraft v<IP_ADDRESS>-beta1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file absentbydesign-1.18-1.6.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file AdditionalEnchantedMiner-1.18.1-18.5.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file additionallanterns-1.0.0-mc1.18.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file advancedperipherals-1.18.1-<IP_ADDRESS>r.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file AEInfinityBooster-1.18.1-1.0.0+3.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file AI-Improvements-1.18-0.4.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file alexsmobs-1.16.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file AllTheCompressed-1.0.2-1.18.1-39.0.59.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file allthemodium-1.7.0-pre22-1.18.1-39.0.10.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file alltheores-1.7.9-1.18.1-39.0.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file allthetweaks-1.8.3-1.18.1-39.0.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file angelring-1.18.1-2.0.0.alpha.2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file Apotheosis-1.18.1-5.0.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file appleskin-forge-mc1.18-2.2.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file appliedenergistics2-10.0.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file Aquaculture-1.18.1-2.3.2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file architectury-3.4.9.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file ars_nouveau-1.18.1-2.1.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file artifacts-1.18.1-4.0.2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file balm-2.4.1+0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file baubley-heart-canisters-1.18-1.0.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file Beyond-Earth-1.18.1-6.0b.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file Beyond-Earth-Giselle-Addon-1.18.1-1.5.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file biggerreactors-1.18.1-0.6.0-beta.0.2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file BiomesOPlenty-1.18.1-<IP_ADDRESS>-universal.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file blockui-1.18-0.0.40-ALPHA.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file blockydoors-1.18-1.0.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file blue_skies-1.18.1-1.3.2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file buildinggadgets-3.10.1-build.3+mc1.18.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file caelus-forge-1.18-<IP_ADDRESS>.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file catalogue-1.6.0-1.18.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file cc-tweaked-1.18.1-1.100.2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file charginggadgets-1.5.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file chipped-1.18.1-1.2.1-forge.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file citadel-1.10.8-1.18.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file cleancut-mc1.18-3.0-forge.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file clickadv-1.18-2.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file ClickMachine-1.18.1-6.0.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file clienttweaks-forge-1.18-7.0.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file cloth-config-6.1.50-forge.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file Clumps-forge-1.18.1-8.0.0+5.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file collective-1.18.1-3.8.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file comforts-forge-1.18-<IP_ADDRESS>.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file CommonCapabilities-1.18.1-2.8.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file compactmachines-4.0.0-beta.4.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file configured-1.5.1-1.18.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file connectedglass-1.1.1-mc1.18.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file constructionwand-1.18.1-2.6.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file cookingforblockheads-forge-1.18.1-11.1.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file corail_woodcutter-1.18-2.2.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file CosmeticArmorReworked-1.18.1-v1a.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file craftingtweaks-forge-1.18.1-14.0.2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file crashutilities-4.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file create-mc1.18.1_v0.4c.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file createaddition-1.18.1-20220111b.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file creeperoverhaul-1.18.1-0.2.0-forge.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file Croptopia-1.18-FORGE-1.8.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file CTM-1.18-1.1.3+1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file Cucumber-1.18.1-5.0.2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file curioofundying-forge-1.18-<IP_ADDRESS>.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file curios-forge-1.18.1-<IP_ADDRESS>.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file curiouselytra-forge-1.18.1-<IP_ADDRESS>.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file curiousshulkerboxes-forge-1.18.1-<IP_ADDRESS>.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file CyclopsCore-1.18.1-1.13.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file DimStorage-1.18.1-6.0.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file domum_ornamentum-1.18.1-1.0.39-ALPHA-universal.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file DungeonCrawl-1.18.1-2.3.6.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file DungeonsArise-1.18.1-2.1.49c-beta.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file elevatorid-1.18-1.8.3.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file enderchests-1.18-1.9.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file endertanks-1.18-1.11.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file engineersdecor-1.18.1-1.1.19-b3.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file enhancedcelestials-2.0.9-1.18.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file entangled-1.3.10-mc1.18.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file expandability-5.0.0-forge.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file ExplorersCompass-1.18.1-1.1.2-forge.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file ExtraDisks-1.18.1-2.0.2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file ExtraStorage-1.18.1-2.0.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file farmingforblockheads-forge-1.18.1-9.0.3.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file FastFurnace-1.18.1-6.0.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file FastLeafDecay-27.2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file FastSuite-1.18.1-3.0.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file FastWorkbench-1.18.1-6.0.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file feature_nbt_deadlock_be_gone_forge-1.0.0+1.18.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file ferritecore-4.0.0-forge.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file flywheel-forge-1.18-0.5.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file FpsReducer-forge-1.25-mc1.18.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file FramedBlocks-4.1.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file ftb-chunks-forge-1801.3.4-build.121.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file ftb-library-forge-1801.3.5-build.109.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file ftb-teams-forge-1801.2.4-build.46.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file furniture-7.0.0-pre27-1.18.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file geckolib-1.18-forge-3.0.9.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file glassential-forge-1.18-1.2.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file hexerei-0.1.13.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file HostileNeuralNetworks-1.18.1-3.0.5.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file Iceberg-1.18.1-1.0.33.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file ImmersiveEngineering-1.18.1-7.1.0-145.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file IntegratedCrafting-1.18.1-1.0.20.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file IntegratedDynamics-1.18.1-1.10.6.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file IntegratedTerminals-1.18.1-1.2.11.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file IntegratedTunnels-1.18.1-1.8.9.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file inventoryessentials-forge-1.18-4.0.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file inventorysorter-1.18-19.0.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file ironchest-1.18-13.0.7.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file ironfurnaces-1.18.1-3.1.3.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file IronJetpacks-1.18.1-5.0.2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file itemcollectors-1.1.4-mc1.18.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file jeed-1.18-1.6.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file jei-1.18.1-<IP_ADDRESS>.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file jmi-1.18.1-0.7-36.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file journeymap-1.18.1-5.8.0beta11.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file JustEnoughProfessions-1.18-1.2.2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file JustEnoughResources-1.18.1-<IP_ADDRESS>.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file Kiwi-1.18-forge-5.2.3.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file kubejs-create-1801.2.0-build.14.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file kubejs-forge-1801.4.1-build.271.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file kubejs-immersive-engineering-1801.2.0-build.29.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file lazydfu-1.0-1.18+.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file LibX-1.18.1-3.1.8.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file LightingWand-1.18-forge-3.0.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file logprot-1.18-1.4.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file lootr-1.18-<IP_ADDRESS>.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file mahoutsukai-1.18.1-v1.34.2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file mcjtylib-1.18-6.0.7.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file mcw-bridges-2.0.1-mc1.18.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file mcw-doors-1.0.5-mc1.18.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file mcw-fences-1.0.2-mc1.18.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file mcw-lights-1.0.2-mc1.18.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file mcw-paintings-1.0.2-mc1.18.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file mcw-roofs-2.1.0-mc1.18.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file mcw-trapdoors-1.0.4-mc1.18.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file mcw-windows-2.0.2-mc1.18.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file minecolonies-1.18.1-1.0.368-ALPHA.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file mininggadgets-1.10.2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file mna-<IP_ADDRESS>.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file mob_grinding_utils-1.18.1-0.4.33.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file modnametooltip-1.18.1-1.18.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file modular-routers-1.18.1-9.0.1-79.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file moredragoneggs-3.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file MouseTweaks-forge-mc1.18-2.21.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file multi-piston-1.18-1.2.2-ALPHA.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file MyServerIsCompatible-1.18-1.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file MysticalAgradditions-1.18.1-5.0.2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file MysticalAgriculture-1.18.1-5.0.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file MysticalCustomization-1.18.1-3.0.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file NaturesAura-35.4.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file NaturesCompass-1.18.1-1.9.4-forge.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file netherportalfix-forge-1.18-9.0.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file no_null_processors_forge-2.0.2+1.18.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file nomowanderer-1.18.1_1.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file norecipeadvancements-2.0.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file occultism-1.18.1-1.25.5.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file OreExcavation-1.10.159.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file PassthroughSigns-1.18-2.5.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file Patchouli-1.18.1-64.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file PatinaPipeworks-1.18.1-1.0.6-universal.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file phosphophyllite-1.18.1-0.6.0-beta.0.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file pipez-1.18.1-1.0.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file Placebo-1.18.1-6.0.4.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file platforms-1.18-1.9.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file polymorph-forge-1.18.1-0.36.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file potionsmaster-0.5.2-1.18.1-39.0.19.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file productivebees-1.18.1-<IP_ADDRESS>.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file PuzzlesLib-v3.1.3-1.18.1-Forge.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file pylons-2.0.6.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file quartz-1.18.1-0.0.0-beta.0.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file rangedpumps-0.9.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file reap-1.18.1-1.0.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file refinedstorage-1.10.0-beta.4.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file refinedstorageaddons-0.8.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file repurposed_structures_forge-4.2.5+1.18.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file rftoolsbase-1.18-3.0.3.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file rftoolsbuilder-1.18-4.0.5.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file rftoolscontrol-1.18-5.0.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file rftoolspower-1.18-4.0.3.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file rftoolsstorage-1.18-3.0.5.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file rftoolsutility-1.18-4.0.6.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file rhino-forge-1800.1.7-build.94.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file RootsClassic-1.18.1-1.1.17.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file rsgauges-1.18.1-1.2.13.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file SaveYourPets-1.18-<IP_ADDRESS>.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file ScalableCatsForce-2.13.7-build-2-with-library.jar of type LANGPROVIDER with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file selene-1.18-1.12.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file shetiphiancore-1.18-3.10.2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file Shrink-1.18.1-1.3.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file silent-gear-1.18.1-2.8.6.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file silent-lib-1.18-6.0.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file simplemagnets-1.1.4-mc1.18.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file SimpleStorageNetwork-1.18.1-1.5.2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file simplylight-1.18.1-1.4.0-build.26.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file SoL-Carrot-1.18.1-1.12.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file sophisticatedbackpacks-1.18.1-<IP_ADDRESS>5.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file spark-forge.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file StorageDrawers-1.18.1-10.1.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file structure_gel-1.18.1-2.1.2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file structurize-1.18.1-1.0.335-ALPHA.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file supermartijn642configlib-1.0.9-mc1.18.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file supermartijn642corelib-1.0.16a-mc1.18.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file supplementaries-1.18.1-1.1.11.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file TerraBlender-forge-1.18.1-<IP_ADDRESS>.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file TerraForged-1.18.1-0.3.0-alpha-2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file tesseract-1.0.24-mc1.18.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file theoneprobe-1.18-5.0.3.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file tinygates-2.0.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file tinyredstone-1.18-3.1.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file tombstone-7.3.6-1.18.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file toms_storage-1.18-1.2.23.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file torchmaster-18.0.3-beta.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file TradingPost-v3.1.2-1.18.1-Forge.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file trashcans-1.0.12-mc1.18.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file trashslot-forge-1.18-11.0.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file treeharvester_1.18.1-4.2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file UtilitiX-1.18.1-0.3.7.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file villagertools-1.18-1.0.2.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file voidtotem-forge-1.18.1-1.1.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file WaterStrainer-1.18-12.1.0.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file waystones-forge-1.18.1-9.0.3.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file windowlogging-mc1.18.1_v0.0.8.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file wirelesschargers-1.0.3a-mc1.18.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file WitherSkeletonTweaks-1.18.1-7.0.1.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file xnet-1.18-4.0.3.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:06] [main/INFO]: Found mod file xptome-1.18-2.1.3.jar of type MOD with locator {mods folder locator at /data/FeedTheBeast/SIMPLE-SERVER-FILES-0.2.35/setup/mods}
mc_1  | [11:52:07] [main/INFO]: Found mod file fmlcore-1.18.1-39.0.43.jar of type LIBRARY with locator net.minecraftforge.fml.loading.moddiscovery.MinecraftLocator@2313052e
mc_1  | [11:52:07] [main/INFO]: Found mod file javafmllanguage-1.18.1-39.0.43.jar of type LANGPROVIDER with locator net.minecraftforge.fml.loading.moddiscovery.MinecraftLocator@2313052e
mc_1  | [11:52:07] [main/INFO]: Found mod file mclanguage-1.18.1-39.0.43.jar of type LANGPROVIDER with locator net.minecraftforge.fml.loading.moddiscovery.MinecraftLocator@2313052e
mc_1  | [11:52:07] [main/INFO]: Found mod file server-1.18.1-20211210.034407-srg.jar of type MOD with locator net.minecraftforge.fml.loading.moddiscovery.MinecraftLocator@2313052e
mc_1  | [11:52:07] [main/INFO]: Found mod file forge-1.18.1-39.0.43-universal.jar of type MOD with locator net.minecraftforge.fml.loading.moddiscovery.MinecraftLocator@2313052e
mc_1  | [11:52:32] [main/INFO]: Compatibility level set to JAVA_17
mc_1  | [11:52:33] [main/INFO]: Successfully loaded Mixin Connector [com.thevortex.allthetweaks.mixin.MixinConnector]
mc_1  | [11:52:33] [main/INFO]: Successfully loaded Mixin Connector [shetiphian.endertanks.mixins.MixinConnector]
mc_1  | [11:52:33] [main/INFO]: Successfully loaded Mixin Connector [shetiphian.core.mixins.MixinConnector]
mc_1  | [11:52:33] [main/INFO]: Launching target 'forgeserver' with arguments [nogui]
mc_1  | [11:52:33] [main/WARN]: Reference map 'croptopia.refmap.json' for croptopia.mixins.json could not be read. If this is a development environment you can ignore this message
mc_1  | [11:52:35] [main/WARN]: Reference map 'rhino-forge-refmap.json' for rhino.mixins.json could not be read. If this is a development environment you can ignore this message
mc_1  | [11:52:35] [main/WARN]: Reference map 'trashslot.refmap.json' for trashslot.mixins.json could not be read. If this is a development environment you can ignore this message
mc_1  | [11:52:36] [main/FATAL]: Attempted to load class net/minecraft/client/player/LocalPlayer for invalid dist DEDICATED_SERVER
mc_1  | [11:52:36] [main/WARN]: Error loading class: net/minecraft/client/player/LocalPlayer (java.lang.RuntimeException: Attempted to load class net/minecraft/client/player/LocalPlayer for invalid dist DEDICATED_SERVER)
mc_1  | [11:52:36] [main/WARN]: @Mixin target net.minecraft.client.player.LocalPlayer was not found ars_nouveau.mixins.json:ClientElytraMixin
mc_1  | [11:52:37] [main/INFO]: Patching ServerResources#<init>
mc_1  | [11:52:38] [main/WARN]: Error loading class: de/maxhenkel/gravestone/events/DeathEvents (java.lang.ClassNotFoundException: de.maxhenkel.gravestone.events.DeathEvents)
mc_1  | [11:52:38] [main/WARN]: Error loading class: de/maxhenkel/corpse/events/DeathEvents (java.lang.ClassNotFoundException: de.maxhenkel.corpse.events.DeathEvents)
mc_1  | SLF4J: No SLF4J providers were found.
mc_1  | SLF4J: Defaulting to no-operation (NOP) logger implementation
mc_1  | SLF4J: See http://www.slf4j.org/codes.html#noProviders for further details.
mc_1  | [11:52:40] [main/INFO]: You need to agree to the EULA in order to run the server. Go to eula.txt for more info.
mc_1  | [11:52:40] [INFO] Server has been stopped, it has started 3 times in 60min
mc_1  | [11:52:40] [INFO] Restarting server in 10 seconds, press ctrl+c to stop```

The container startup positions the Eula file in at least two locations for mod packs, so I need to investigate why that modpack defeats that logic.

@itzg  can we add help wanted to .github/workflows/issue-label.yml to increase visibility?

@itzg can we add help wanted, priority/high, question, and status/waiting on upstream to .github/workflows/issue-label.yml to increase visibility?

Done!

I have the same Problem. This Modpack has a subfolder called 'setup' where all the server files are.
My workaround was to edit the modpack zip.
in SIMPLE-SERVER-FILES-x.x.xx.zip edit the file server-setup-config.yaml
baseInstallPath: /setup
to
baseInstallPath: ~
and repack the zip

@incur thanks for the info. Is that also with ATM7? What I really need to do is detect and rearrange the modpack on the fly like you're doing manually.

@incur thanks for the info. Is that also with ATM7? What I really need to do is detect and rearrange the modpack on the fly like you're doing manually.

yes, also ATM7 with the not so simple server files

with the not so simple server files

😁

@lotrez Workaround which works great for me is setting CF_BASE_DIR=/data

Was it intended to go to Done?

Yeah, it would be nice if the stake check was project-state aware

I think this issue is more generalized than just the EULA not being properly taken into account. For example, I recently setup Rebirth of the Night with a docker-compose script and its whitelist and op environment variables were not properly implemented. Likely for the same reason as here. When I execed a bash shell into the container, I could see whitelist.json and ops.json files in the /data directory, but not in the directory where the server files were located. This seems to also be a problem for those files.

This seems to be caused by start-setupRbac and writeEula() in start-utils not caring about the install location as set in FTB_BASE_DIR & CF_BASE_DIR.


Remove unused "templates" directory

The "templates" directory in the root is unused and should not be created anymore:
https://github.com/Dytanic/CloudNet/blob/master/cloudnet-core/src/main/java/de/dytanic/cloudnetcore/CloudConfig.java#L81

#close


MimeType detection now work on Streams

Why was that is_string even there?
Tested in most situations with Laravel 5.3

@annejan iirc that was because the main package couldn't determine it nices. I'll up the requirement from this to the main package to 1.0.27 where it was fixed.


Using Terragrunt for modules with multiple providers

How does Terragrunt call into modules with multiple providers? I'm going with the approach of keeping the code DRY and keeping only terragrunt.hcl files in my directories, which is partitioned by environment and component.
For example, AWS VPC peering is a common component that requires 2 providers as there's both a requester and a provider. In regular Terraform, I'd do something like
module "vpc_peering" {
  source = "../path/vpc-peer"
  ... (arguments)

  providers = {
    aws.requester = aws.default
    aws.accepter = aws.peer
  }
}

However, if I'm using a root level terragrunt.hcl and then a directory level terragrunt.hcl that includes the root level one and has terraform and input blocks, I'd have something like:
# root level terragrunt.hcl
remote_state {
  backend "s3"
  (some config)
}

generate "provider" {
  (provider config for both aws.default and aws.peer)
}

# directory level terragrunt.hcl
terraform {
  source = "../path/vpc-peer"
}

include {
  path = find_in_parent_folders()
}

inputs = {
  (arguments)
}

How would one pass multiple providers to the module?

Terragrunt currently doesn't support passing in multiple provider aliases to a module directly. I'm not sure terraform supports setting that on the CLI either so this might not be possible to implement.
That said, there are two possible workarounds for this:

Create a wrapper terraform module that manually configures the providers and sets the setting on the module.

In theory, you should be able to override the providers for the module directly using the generate block. So instead of calling the, default and peer, you call the providers requester and accepter, which would then be injected directly into the module.

@yorinasub17 - I know this got closed, but I would love to see this get added as an enhancement. Wasn't sure if I should open a "duplicate" issue or try to get this re-opened.
As to the first option - I'd have to map all the input vars and output vars and do it for every module that is looking for multiple providers.  It would also mean not being able to leverage all the provider blocks generated previously, which would add to duplicated code and potentially confusion since resource creation would be decoupled from those provider blocks. Unless I'm just missing a way easier implementation here.
The second of the approaches you mentioned just errors with:
Error: Duplicate provider configuration

You could remove the two provider blocks in the vpc-peering module, but then everytime you this happens in a community module you're forking and maintaining your own code base and/or you're changing your providers to match what each module might call them, default peer accepter etc..
Apologies on any ignorance towards terraform/terragrunt here. Been thrown in the deep end here.

Unfortunately, this is not something terragrunt can handle in the current design (because terraform doesn't provide us the options to update providers on the CLI), so even if we open a ticket, we would most likely close it out as something we won't implement, or will be ignored for years. The only way I see terragrunt supporting this is if we implement https://github.com/gruntwork-io/terragrunt/issues/759, but that won't happen for a while.
The workarounds I mentioned above, however painful it is, is the only options you have right now if you want to customize a provider defined in a module with terragrunt.

module "sns_shared" {
source = "../../modules_prod/services/sns"
providers = {
aws.default = aws.default
aws.test = aws.test
}
}
generate "provider" {
path      = "provider.tf"
if_exists = "overwrite_terragrunt" # Allow modules to override provider settings
contents = <<EOF
provider "aws" {
alias = "default"
region = "eu-central-1"
}
provider "aws" {
alias = "test"
region = "us-east-1"
}
EOF
}


[Event Request] Codeunit 6620 - OnCheckItemAvailabilityOnBeforeValidateShipmentDate

In codeunit 6620 Copy Document Mgt., function CheckItemAvailability, please add the following event:
[…]
ToSalesLine."Drop Shipment" :=
  NOT RecalculateLines AND ToSalesLine."Drop Shipment" AND
  (ToSalesHeader."Document Type" = ToSalesHeader."Document Type"::Order);

// >> ---------- NEW
OnCheckItemAvailabilityOnBeforeValidateShipmentDate(ToSalesHeader,ToSalesLine);
// << ---------- NEW
IF ToSalesLine."Shipment Date" = 0D THEN BEGIN
  IF ToSalesHeader."Shipment Date" <> 0D THEN
    ToSalesLine.VALIDATE("Shipment Date",ToSalesHeader."Shipment Date")
  ELSE
    ToSalesLine.VALIDATE("Shipment Date",WORKDATE);
END;
[…]

As the name indicates, it is essential for us having the event executed before any Shipment Date is validated.

Note: implemented with publisher OnBeforeSetShipmentDateInLine
LOCAL [IntegrationEvent] OnBeforeSetShipmentDateInLine(SalesHeader : Record "Sales Header";VAR SalesLine : Record "Sales Line")


XDebug error

When trying to setup remote debugging i receive this error in xdebug.log:
Log opened at 2017-06-07 07:57:26
I: Connecting to configured address/port: <IP_ADDRESS>:9000.
W: Creating socket for '<IP_ADDRESS>:9000', poll success, but error: Operation now in progress (29).
E: Could not connect to client. :-(
Log closed at 2017-06-07 07:57:26

Is there any relation with Devilbox itself?
For now, i use PHPStorm and internal IDE validation is working fine, but no remote debugging is happening.

I will try to reproduce this. Can you let me know a bit more about your setup:

Windows, Linux or OSX
In Case of Windows: Are you using Docker Toolbox or Docker for Windows
Docker and Docker-compose versions
XDEBUG setup in .env

Ubuntu 16.04
Docker 17.03.1-ce
Docker-compose 1.13.0

.env
PHP_SERVER=php-fpm-7.1

#############

PHP_XDEBUG_ENABLE=1
PHP_XDEBUG_REMOTE_PORT=9000
PHP_XDEBUG_REMOTE_HOST=<IP_ADDRESS>

PHPStorm configured through Docker php executable, with server mapped properly on container folders.

That was entirely my mistake. Have not read the comment above PHP_XDEBUG_REMOTE_HOST parameter. I forget to change IP to my host address, so xdebug was unable to connect. Sorry.

Good to hear. I will have to add this to the FAQ section.

How can I setup VS Code with Xdebug?
I think Xdebug was started but VS Code cannot "listen" it.
Here is my xdebug.log
Log opened at 2017-11-16 17:07:24
I: Connecting to configured address/port: <IP_ADDRESS>:9000.
E: Time-out connecting to client. :-(
Log closed at 2017-11-16 17:07:24

PHP Debug for VS Code: https://marketplace.visualstudio.com/items?itemName=felixfbecker.php-debug
Thanks a lot!

@lbngoc Unfortunately I have never used VS Code, so I will not be able to help you on the client side.
On the devilbox side however, you should simply apply those settings:
PHP_XDEBUG_ENABLE=1
PHP_XDEBUG_REMOTE_PORT=9000
PHP_XDEBUG_REMOTE_HOST=<IP_ADDRESS>

Change <IP_ADDRESS> to whatever IP address you local computer (where VC Code runs on) is using.

@cytopia
Can we expose port 9000 to localhost of local computer?
I see that my local IP changed every I power on my laptop.
@ilsenem
Could you please share your debug config with PHPStorm ?

@lbngoc There is no config, really. I just replace default IP provided in devilbox configuration with my machine IP and all worked. The only thing i changed is path mappings, but PhpStorm will ask for it on first debug session.

@ilsenem Thanks you. I also think my issue maybe come from the path mapping, I will find another way.

@lbngoc did you find a solution. I have the same issue
Log opened at 2017-12-14 06:21:58
I: Connecting to configured address/port: <IP_ADDRESS>:9000.
E: Time-out connecting to client. :-(
Log closed at 2017-12-14 06:21:58
PHP_XDEBUG_REMOTE_HOST=<IP_ADDRESS>
If it needs to be different what would the ip be, the ip on the local network 10.0.1.XX?
Thank you

I see a similar problem. I used
ip route get <IP_ADDRESS> | awk '{print $NF; exit}'
and put this in .env at PHP_XDEBUG_REMOTE_HOST
The xdebug log says

I: Connecting to configured address/port: <IP_ADDRESS>:10000.
W: Creating socket for '<IP_ADDRESS>:10000', poll success, but error: Operation now in progress (29).
E: Could not connect to client. :-(

(p.s. I changed
PHP_XDEBUG_REMOTE_PORT=10000
as well as in my IDE)
and according to PHPStorm 'Validate Debugger Configuation on Web Server' all the config settings are good to go.

Ok I got this working thanks to some posts, like 1, 2, and 3.
set
PHP_XDEBUG_REMOTE_CONNECT_BACK = 0
I could then connect with xdebug but there were problems with my path mappings. PHPStorm makes it simple to apply path mappings to the devilbox htdocs folder and debugging works like normal.

Generalized Xdebug documentation now available: https://devilbox.readthedocs.io/en/latest/intermediate/configure-php-xdebug.html


Need to update the cloudformation with new nodejs version number

In the following link, the NodeJS version in yaml is still 6.10, which will report not supported.
https://github.com/aws-samples/aws-serverless-workshops/tree/master/Auth/2_ServerlessAPI

`AWSTemplateFormatVersion: '2010-09-09'
Transform:

'AWS::Serverless-2016-10-31'
'AWS::CodeStar'

Description:
Creates a RESTful API using API Gateway, Lambda and DynamoDB for the Wild Rydes serverless devops workshop
Parameters:
ProjectId:
Type: String
Description: AWS CodeStar projectID used to associate new resources to team members
CodeDeployRole:
Type: String
Description: IAM role to allow AWS CodeDeploy to manage deployment of AWS Lambda functions
Stage:
Type: String
Description: The name for a project pipeline stage, such as Staging or Prod, for which resources are provisioned and deployed.
Default: ''
Resources:
LambdaExecutionRole:
Description: Creating service role in IAM for AWS Lambda
Type: AWS::IAM::Role
Properties:
RoleName: !Sub 'CodeStar-${ProjectId}-Execution${Stage}'
AssumeRolePolicyDocument:
Statement:
- Effect: Allow
Principal:
Service: [lambda.amazonaws.com]
Action: sts:AssumeRole
Path: /
ManagedPolicyArns:
- arn:aws:iam::aws:policy/service-role/AWSLambdaBasicExecutionRole
- arn:aws:iam::aws:policy/AmazonDynamoDBFullAccess
-  arn:aws:iam::aws:policy/AWSXRayDaemonWriteAccess
PermissionsBoundary: !Sub 'arn:${AWS::Partition}:iam::${AWS::AccountId}:policy/CodeStar_${ProjectId}_PermissionsBoundary'
Table:
Type: 'AWS::Serverless::SimpleTable'
Properties:
PrimaryKey:
Name: name
Type: String
ReadFunction:
Type: 'AWS::Serverless::Function'
Properties:
FunctionName: 'uni-api-read'
Runtime: nodejs8.10
CodeUri: app
Handler: read.lambda_handler
Description: View Unicorn by name
Timeout: 10
Tracing: Active
Events:
GET:
Type: Api
Properties:
Path: /unicorns/{name}
Method: get
Environment:
Variables:
TABLE_NAME: !Ref Table
Role: !GetAtt LambdaExecutionRole.Arn
ListFunction:
Type: 'AWS::Serverless::Function'
Properties:
FunctionName: 'uni-api-list'
Runtime: nodejs8.10
CodeUri: app
Handler: list.lambda_handler
Description: List Unicorns
Timeout: 10
Tracing: Active
Events:
GET:
Type: Api
Properties:
Path: /unicorns
Method: get
Environment:
Variables:
TABLE_NAME: !Ref Table
Role: !GetAtt LambdaExecutionRole.Arn
UpdateFunction:
Type: 'AWS::Serverless::Function'
Properties:
FunctionName: 'uni-api-update'
Runtime: nodejs8.10
CodeUri: app
Handler: update.lambda_handler
Description: Update Unicorn
Timeout: 10
Tracing: Active
Events:
PUT:
Type: Api
Properties:
Path: /unicorns/{name}
Method: put
Environment:
Variables:
TABLE_NAME: !Ref Table
Role: !GetAtt LambdaExecutionRole.Arn
DeleteFunction:
Type: 'AWS::Serverless::Function'
Properties:
FunctionName: 'uni-api-delete'
Runtime: nodejs8.10
CodeUri: app
Handler: delete.lambda_handler
Description: Delete Unicorn
Timeout: 10
Tracing: Active
Events:
DELETE:
Type: Api
Properties:
Path: /unicorns/{name}
Method: delete
Environment:
Variables:
TABLE_NAME: !Ref Table
Role: !GetAtt LambdaExecutionRole.Arn
`


Ingress error: Cannot connect to host <IP_ADDRESS>:5000 ssl:default [Connect call failed ('<IP_ADDRESS>', 5000)]

Version of the custom_component

Configuration

mqtt:
  host: <IP_ADDRESS>
  port: 1883

cameras:
  Reolink_410:
    ffmpeg:
      inputs:
        - path: rtsp://<IP_ADDRESS>:/8554/h264Preview_01_main
        - roles:
            - detect
            - rtmp
    width: 1280
    height: 720
    fps: 5
detetectors:
  cpu1:
    type: cpu
  cpu2:
    type: cpu

Add your logs here.
21-05-12 08:08:58 INFO (MainThread) [supervisor.snapshots] Found 28 snapshot files
21-05-12 08:09:17 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with ccab4aaf_frigate!
21-05-12 08:09:17 INFO (SyncWorker_2) [supervisor.docker.interface] Cleaning addon_ccab4aaf_frigate application
21-05-12 08:09:17 INFO (SyncWorker_2) [supervisor.docker.addon] Starting Docker add-on ccab4aaf/amd64-addon-frigate with version 1.13
21-05-12 08:09:47 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with ccab4aaf_frigate!
21-05-12 08:09:47 INFO (SyncWorker_4) [supervisor.docker.interface] Cleaning addon_ccab4aaf_frigate application
21-05-12 08:09:48 INFO (SyncWorker_4) [supervisor.docker.addon] Starting Docker add-on ccab4aaf/amd64-addon-frigate with version 1.13
21-05-12 08:10:07 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with ccab4aaf_frigate application!
21-05-12 08:10:07 INFO (SyncWorker_4) [supervisor.docker.interface] Cleaning addon_ccab4aaf_frigate application
21-05-12 08:10:07 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on ccab4aaf/amd64-addon-frigate with version 1.13
21-05-12 08:10:18 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with ccab4aaf_frigate!
21-05-12 08:10:18 INFO (SyncWorker_3) [supervisor.docker.interface] Cleaning addon_ccab4aaf_frigate application
21-05-12 08:10:18 INFO (SyncWorker_3) [supervisor.docker.addon] Starting Docker add-on ccab4aaf/amd64-addon-frigate with version 1.13
21-05-12 08:10:32 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host <IP_ADDRESS>:5000 ssl:default [Connect call failed ('<IP_ADDRESS>', 5000)]
21-05-12 08:10:48 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with ccab4aaf_frigate!
21-05-12 08:10:48 INFO (SyncWorker_4) [supervisor.docker.interface] Cleaning addon_ccab4aaf_frigate application
21-05-12 08:10:48 INFO (SyncWorker_4) [supervisor.docker.addon] Starting Docker add-on ccab4aaf/amd64-addon-frigate with version 1.13
21-05-12 08:11:18 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with ccab4aaf_frigate!
21-05-12 08:11:18 INFO (SyncWorker_0) [supervisor.docker.interface] Cleaning addon_ccab4aaf_frigate application
21-05-12 08:11:19 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on ccab4aaf/amd64-addon-frigate with version 1.13
21-05-12 08:11:49 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with ccab4aaf_frigate!
21-05-12 08:11:49 INFO (SyncWorker_2) [supervisor.docker.interface] Cleaning addon_ccab4aaf_frigate application
21-05-12 08:11:49 INFO (SyncWorker_2) [supervisor.docker.addon] Starting Docker add-on ccab4aaf/amd64-addon-frigate with version 1.13
21-05-12 08:11:50 INFO (SyncWorker_3) [supervisor.docker.interface] Stopping addon_ccab4aaf_frigate application
21-05-12 08:11:50 INFO (SyncWorker_3) [supervisor.docker.interface] Cleaning addon_ccab4aaf_frigate application
21-05-12 08:11:50 INFO (SyncWorker_3) [supervisor.docker.interface] Removing image ccab4aaf/amd64-addon-frigate with latest and 1.13
21-05-12 08:11:50 INFO (MainThread) [supervisor.addons.addon] Removing add-on data folder /data/addons/data/ccab4aaf_frigate
21-05-12 08:11:50 INFO (MainThread) [supervisor.ingress] Update Ingress as panel for ccab4aaf_frigate
21-05-12 08:11:50 INFO (MainThread) [supervisor.addons] Add-on 'ccab4aaf_frigate' successfully removed
21-05-12 08:12:46 INFO (MainThread) [supervisor.store.git] Removing custom add-on repository https://github.com/blakeblackshear/frigate-hass-addons
21-05-12 08:12:47 INFO (MainThread) [supervisor.store] Loading add-ons from store: 63 all - 0 new - 2 remove
21-05-12 08:12:47 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-05-12 08:12:47 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-05-12 08:17:37 INFO (MainThread) [supervisor.store.git] Cloning add-on https://github.com/blakeblackshear/frigate-hass-addons repository
21-05-12 08:17:38 WARNING (MainThread) [supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of Frigate NVR
21-05-12 08:17:38 WARNING (MainThread) [supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of Frigate NVR Beta (outdated)
21-05-12 08:17:38 INFO (MainThread) [supervisor.store] Loading add-ons from store: 65 all - 2 new - 0 remove
21-05-12 08:17:38 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-05-12 08:17:38 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-05-12 08:18:40 INFO (MainThread) [supervisor.addons] Creating Home Assistant add-on data folder /data/addons/data/ccab4aaf_frigate
21-05-12 08:18:40 INFO (SyncWorker_3) [supervisor.docker.addon] Starting build for ccab4aaf/amd64-addon-frigate:1.13
21-05-12 08:18:47 INFO (SyncWorker_3) [supervisor.docker.addon] Build ccab4aaf/amd64-addon-frigate:1.13 done
21-05-12 08:18:47 INFO (MainThread) [supervisor.addons] Add-on 'ccab4aaf_frigate' successfully installed
21-05-12 08:18:52 INFO (MainThread) [supervisor.ingress] Update Ingress as panel for ccab4aaf_frigate
21-05-12 08:18:58 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on ccab4aaf/amd64-addon-frigate with version 1.13
21-05-12 08:19:14 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host <IP_ADDRESS>:5000 ssl:default [Connect call failed ('<IP_ADDRESS>', 5000)]
21-05-12 08:28:08 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed
21-05-12 08:28:12 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-05-12 08:28:12 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-05-12 08:28:12 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_vscode
21-05-12 08:28:12 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-05-12 08:36:56 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed
21-05-12 08:36:59 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-05-12 08:36:59 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_vscode
21-05-12 08:36:59 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running```

## Describe the bug
A clear and concise description of what the bug is.

## Debug log

<!-- To enable debug logs check this https://www.home-assistant.io/components/logger/ -->

```text

Add your logs here.

I don't think this is an issue with the integration. Please post the logs from the addon. It appears to be crashing.

detetectors
At the very least, you have a spelling error in your config.

@mwy6283 Can we close this bug?

Please re-open if you believe this is an issue with the Frigate Home Assistant Integration. If the issue is with Frigate itself, please file a bug here: https://github.com/blakeblackshear/frigate
Thanks!


KOREScanner.l: Admit @ in identifiers for set variables

In kframework/kore#922, we begin to use set variables in prelude.kore, which requires this small extension to the C++ Kore parser.

Is @0 a valid set variable? It would be permitted by this regex.

Hm, if we take the Haskell parser to be the reference implementation, then that is not valid. (The document describing the syntax of Kore has fallen out of date.)


Update to MAPL 2.23.0

This PR updates MAPL to 2.23.0. This REQUIRES using ESMA_env v4.2.0 (aka Baselibs 7.5.0) due to a need for a newer yaFyaml library version. This allows for better error handling in ExtData2G.
This is a zero-diff update as nothing has really changed in MAPL, save for needing a new library.
NOTE: Keeping draft until MAPL 2.23.0 is released. For now, I've put in the branch we are using.

Undrafted. This should be good for testing!


Make FPM logging format configurable

By making the logging format configurable users of this image can use
their own desired format such as JSON, CSV, or something else.
Usabilla PHP Docker Template
Closes: #152
Reviewers: @usabilla/oss-docker
Type
Please specify the type of changes being proposed:

Q
A

Documentation?
yes

Dockerfile change?
yes

Build feature?
no

Apply CVE Patch?
no

Remove CVE Patch?
no

Changelog

Please make sure you have checked our Contributing guidelines

Opened an issue with hadolint for the linting error: https://github.com/hadolint/hadolint/issues/428

Opened an issue with hadolint for the linting error: hadolint/hadolint#428

Looks like hadolint is getting a new Dockerfile parser and the linting issue this PR has will be solved by it. E.T.A. for the parser is somewhere this week according to https://github.com/hadolint/language-docker/pull/53#issuecomment-634653154

Where do we centralize this in Usabilla-land?

I have some ideas, will open an internal issue about it.

@renatomefi the bug is in the Dockerfile parser, AFAIK there is no ignore for that

@renatomefi the bug is in the Dockerfile parser, AFAIK there is no ignore for that

Uh fair, is there any scaping we could do that won't change the effective value?

@renatomefi the bug is in the Dockerfile parser, AFAIK there is no ignore for that

Uh fair, is there any scaping we could do that won't change the effective value?

@renatomefi the irony here is that \" inside the "  is the cause of the parser breaking. Will look into that.

@renatomefi sooo funny story, the current format might be correct in the code, it doesn't translate correctly into the FPM conf. And as far as escaping goes, it's complicated. We can always consider consider doing a small BC break and drop the "'s

I know the hadolint docker language author said they'd release your patch somewhere last week, but given the cadence of the project I have a feeling it might take much longer, do we have a workaround?

@renatomefi they just released a new version with the new parser 🎉🎉🎉

@renatomefi yup, also managed to get the correct escaping in the Dockerfile, one of the culprits was not putting the format between quotes in the FPM pool .conf 😂 . Will fiddle with the example a bit, and come up with a working and tested JSON example. Not sure how to unit test the output of FPM yet

Updated it with a working JSON example and also added an example log line to the commit message.
{"cpu_usage":84.03,"memory_usage":8388608,"duration_microsecond":0.179,"script":"/opt/project/public/index.php","content_length":0,"request_method":"GET","pool_name":"www","process_id":"11","request_query_string":"key=value","request_uri_query_string_glue":"?","request_uri":"/index.php","request_url":"/index.php?key=value","remote_ip_address":"<IP_ADDRESS>","response_status_code":200,"time":"07/Jun/2020:21:24:20 +0000","remote_user":""}


In IE 11 not working

when I use it on ie 11, I get an error on the vendor js: "syntax error".
Is this library supported by ie 11? or is there a way to use it with ie?

me too, but i can use the file xlsx-populate.min.js and the problem solved.

if i use babel-loader compile this module(include this module) and remove the config of modules(.babelrc), the problem went away too.


Kaniko 500 internal server error retrieving Fedora image from cache

I had a set of builds false start because of this. ~5 minutes later, I was able to kick off the builds for real.
gcr.io/kaniko-project/executor:v1.8.1
time="2022-06-13T14:16:12Z" level=info msg="Using dockerignore file: /workspace/ci/.dockerignore"
time="2022-06-13T14:16:12Z" level=info msg="Retrieving image manifest fedora:35"
time="2022-06-13T14:16:12Z" level=info msg="Retrieving image fedora:35 from registry index.docker.io"
time="2022-06-13T14:16:13Z" level=error msg="Error while retrieving image from cache: fedora:35 GET https://auth.docker.io/token?scope=repository%3Alibrary%2Ffedora%3Apull&service=registry.docker.io: unexpected status code 500 Internal Server Error"
time="2022-06-13T14:16:13Z" level=info msg="Retrieving image manifest fedora:35"
time="2022-06-13T14:16:13Z" level=info msg="Retrieving image fedora:35 from registry index.docker.io"
error building image: GET https://auth.docker.io/token?scope=repository%3Alibrary%2Ffedora%3Apull&service=registry.docker.io: unexpected status code 500 Internal Server Error

I think github was also having some problems at this time...

No repeats in 90d, closing.


Added the Hydrawise component.

Description:
The hydrawise component allows you to integrate your Hunter Hydrawise Wi-Fi irrigation controller system in Home Assistant.
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):
# Example configuration.yaml entry
hydrawise:
  access_token: YOUR_API_KEY

Checklist:

[X] The code change is tested and works locally.
[X] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[X] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[X] New dependencies have been added to the REQUIREMENTS variable (example).
[X] New dependencies are only imported inside functions that use them (example).
[X] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[X] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Hi @ptcryan,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Thanks! I'll get started on these.

Ready for (re)review!

Thanks  @fabaff and  @MartinHjelmare for your time and support. You guys are awesome!
Hopefully this is good to go now.

Not sure why hound failed. I'll hold a bit on the merge to see what's up.

Is there something I need to do? I thought Hound passed when I pushed that last commit. I'm not sure what to do next?


Adjust rails version dependency

Relaxes the requirement for Rails a bit.

:+1:

this is old, and out-of-date. closing for now


Can the single number be supported?

Hello,
In my application, I will used from 0 to 9 as short key, are they be supported now?
Thanks!

Hi,
You can use numbers perfectly.
<section class="row" v-shortkey="['2']" @shortkey="doit()">


[firebase_crashlytics]  Should not use platform channels, dart port?

Since all firebase plugins are open source now, it seems good to have dart port and dont backport to platform channels?
That way plugin would have more control over logic and it would resolve problems like implementing android-ndk in plugin, one could add crashlytics to native platform if needed.
Code for native android https://github.com/firebase/firebase-android-sdk/tree/master/firebase-crashlytics

Hi @charafau - the plugins use the underlying Firebase SDKs which are built from the open sourced SDKs. It's also worth noting not all features have been open sourced yet either.
I'll close this one off to reduce noise - however if you feel like I have the wrong end of the stick, please let me know!


Make more secure

Before you start...

[x] Have you updated the FluentHub? You might be using an old version.
[x] Have you checked if similar issue have already been reported?

Resolved / Related Issues

Closes #56
Closes #95

Details of Changes

[ ] Handle all exceptions
[ ] Display message when there's no internet connection
[x] Colored repo's code block

Validation

[x] Built and ran the app
[x] Tested the changes for accessibility

Relevant Assets

nice!

Should I catch the exception in the main thread(viewmodel) to get the error message? @luandersonn

@onein528 Yes. Or you can use DispatcherQueue to update the UI.

haha i dont knwo sorry.

After the dddd5d15db442bb3f3db68bde7a018c5293bad26, you can send Notifications from any thread

ok

when theres no internet:

updated UI

On a4aedfc12182320727b355e41167ddf5c29f2f58

Add CancellationToken to ViewModel commands
Add Empty/Error State to some Views
Code refactoring

If you feel you've got secure(any likely exceptions handled and...).

i think it is high time to merge this.

Need final adjustment.

Fix margins.
Check changes if you expeced.

sub commit message:

Add FluentHub.Backend.
Update README.md.
Update some documentations.
Add customized logger.

Remove duplicated codes.

Add "Async" suffix to all async queries.
Update authorization method.
Add a converter ObjectToBoolConverter.
Update most ViewModel to DepencenctInjection.
Add notification infobar.
Update navigation service
Update to catch all exception from Octokit.
Add option to copy git clone command
Allow a viewer to access the .Viewer query when viewer viewing a page.

Co-authored-by: Luandersonn Airton<EMAIL_ADDRESS>Co-authored-by: Gabriel Fontán<EMAIL_ADDRESS>


calico-node pods being recreated every few seconds

Hello,
I am currently experiencing a strange behavior with Calico v 3.25.1 running on a 4 node Microk8s v1.30 cluster. The calico-node pods of each node keep being terminated and recreated after at most 30 seconds:
NAME                                       READY   STATUS     RESTARTS        AGE
calico-kube-controllers-749f88db4d-rctkf   1/1     Running    0               4h28m
calico-node-2fxmj                          0/1     Init:0/2   0               3s
calico-node-8p84q                          0/1     Init:0/2   0               2s
calico-node-bl6hq                          0/1     Init:1/2   0               3s
calico-node-g2gsx                          0/1     Running    0               7s

The nodes report network unavailability:
  Type                 Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----                 ------  -----------------                 ------------------                ------                       -------
  NetworkUnavailable   True    Thu, 30 May 2024 13:36:08 +0900   Thu, 30 May 2024 13:36:08 +0900   CalicoIsDown                 Calico is shutting down on this node
  MemoryPressure       False   Thu, 30 May 2024 13:33:10 +0900   Thu, 30 May 2024 02:36:59 +0900   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure         False   Thu, 30 May 2024 13:33:10 +0900   Thu, 30 May 2024 02:36:59 +0900   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure          False   Thu, 30 May 2024 13:33:10 +0900   Thu, 30 May 2024 02:36:59 +0900   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready                True    Thu, 30 May 2024 13:33:10 +0900   Thu, 30 May 2024 02:36:59 +0900   KubeletReady                 kubelet is posting ready status

Expected Behavior
calico-node pods should be running continuously
Current Behavior
calico-node pods get terminated and recreated after less than 30 seconds. The pods do not seem to error or enter a CrashLoopBackOff state.
Oddly enough, there does not seem to be any impact on applications running in the cluster.
Here are some logs from the pods for the the brief time they are running,:
2024-05-30 04:38:58.037 [INFO][76] felix/int_dataplane.go 1726: Received interface addresses update msg=&intdataplane.ifaceAddrsUpdate{Name:"calico_tmp_A", Addrs:set.Set[string](nil)}
2024-05-30 04:38:58.037 [INFO][76] felix/hostip_mgr.go 84: Interface addrs changed. update=&intdataplane.ifaceAddrsUpdate{Name:"calico_tmp_A", Addrs:set.Set[string](nil)}
2024-05-30 04:38:58.284 [INFO][76] felix/health.go 306: Overall health status changed: live=true ready=true
+---------------------------+---------+----------------+-----------------+--------+
|         COMPONENT         | TIMEOUT |    LIVENESS    |    READINESS    | DETAIL |
+---------------------------+---------+----------------+-----------------+--------+
| CalculationGraph          | 30s     | reporting live | reporting ready |        |
| FelixStartup              | 0s      | reporting live | reporting ready |        |
| InternalDataplaneMainLoop | 1m30s   | reporting live | reporting ready |        |
+---------------------------+---------+----------------+-----------------+--------+

2024-05-30 00:20:53.039 [INFO][25] tunnel-ip-allocator/node.go 99: Error updating Node resource error=Operation cannot be fulfilled on nodes "haspc": the object has been modified; please apply your changes to the latest version and try again

2024-05-30 00:20:53.039 [INFO][25] tunnel-ip-allocator/allocateip.go 686: Error updating node haspc: %!s(<nil>). Retrying. type="wireguardTunnelAddress"

2024-05-30 04:45:24.920 [INFO][31] tunnel-ip-allocator/config_params.go 647: Parsed value for FeatureDetectOverride: map[ChecksumOffloadBroken:true] (from environment variable)
2024-05-30 04:45:24.920 [INFO][31] tunnel-ip-allocator/config_params.go 611: Parsing value for DefaultEndpointToHostAction: ACCEPT (from environment variable)
2024-05-30 04:45:24.920 [INFO][31] tunnel-ip-allocator/config_params.go 647: Parsed value for DefaultEndpointToHostAction: ACCEPT (from environment variable)
2024-05-30 04:45:24.920 [INFO][31] tunnel-ip-allocator/config_params.go 611: Parsing value for IpInIpMtu: 0 (from environment variable)
2024-05-30 04:45:24.920 [INFO][31] tunnel-ip-allocator/config_params.go 647: Parsed value for IpInIpMtu: 0 (from environment variable)
2024-05-30 04:45:24.920 [INFO][31] tunnel-ip-allocator/config_params.go 611: Parsing value for Ipv6Support: false (from environment variable)
2024-05-30 04:45:24.920 [INFO][31] tunnel-ip-allocator/config_params.go 647: Parsed value for Ipv6Support: false (from environment variable)
2024-05-30 04:45:25.088 [INFO][31] tunnel-ip-allocator/allocateip.go 340: Current address is still valid, do nothing currentAddr="<IP_ADDRESS>" type="vxlanTunnelAddress"
CALICO_NETWORKING_BACKEND is vxlan - no need to run a BGP daemon
Calico node started successfully

I will post more as soon as I can catch something interesting
On the other hand, I don't see any error in the logs of the calico-kube-controllers pod
Possible Solution
I managed to get the pods running by having each Kubernetes node leave and re-join the cluster but after a week, the problem is back.
Unfruitful attemps
Those attempts did not succeed in solving the problem:

restarting the calico-node daemonset
restarting the calico-kube-controller deployment
restarting the nodes
updating calico as described here

Steps to Reproduce (for bugs)
I had no such issues when using Microk8s v1.24. From there, my changes to the cluster include:

Incremental update Microk8s v1.24 to v1.30
Installing Longhorn v1.61
Adding <IP_ADDRESS>/16,<IP_ADDRESS>/24,*.svc,*.cluster.local to the NO_PROXY environment variable for Longhorn to work
Enabled hugepages on each node

Context
Your Environment

Calico version: 3.25.1
Orchestrator version: Microk8s v1.30 (i.e. Kuberntes v1.30) with DNS addon enabled
Operating System and version: 4 x Ubuntu server 22.04 LTS running on physical machines

Additionally:
Kubelet configuration (/var/snap/microk8s/current/args/kubelet):
--cluster-dns=<IP_ADDRESS>
--cluster-domain=cluster.local
...

Kube-APIserver configuration (/var/snap/microk8s/current/args/kube-apiserver):
...
--service-cluster-ip-range=<IP_ADDRESS>/24
...

The cluster runs on-premise, behind a corporate proxy. Environment variables are set accordingly in /etc/environment of each node, as per recommended here
HTTP_PROXY=http://<IP_ADDRESS>:8118
HTTPS_PROXY=http://<IP_ADDRESS>:8118
NO_PROXY=localhost,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>,november,haspc,20khaa520,24khaa344,<IP_ADDRESS>/16,<IP_ADDRESS>/24,*.svc,*.cluster.local

Similarily, containerd environment variables are set in /var/snap/microk8s/current/args/containerd-env:
HTTPS_PROXY=http://<IP_ADDRESS>:8118
NO_PROXY=<IP_ADDRESS>/16,<IP_ADDRESS>/24,<IP_ADDRESS>/12,<IP_ADDRESS>,localhost

Probably unrelated, but Longhorn v1.6.1 is installed in the cluster using Helm.
I've got a similar cluster, composed of AWS EC2s that dot not require proxy settings and have no problems there.
Is there special proxy-related configuration needed by Calico to run properly?

I brought one node for maintenance today for maintenance today and the calico-node pods started running properly.
Bringing the node back up immediately triggered the recreation cycle mentioned in this issue.
I have no idea what makes this node special for the time being and also don't know if this would happen if any other node was taken down.

I found a deployment whose pod had been stuck pending state for a couple months.
Deleting it immediately solved the problems with calico-node pods.
As I didn't imagine those issues to be linked, I didn't check why the aforementioned pod was in pending state and am now unable to recreate the issue.
For anyone experiencing the same issue, check your pods and deal with any that is in pending state


[WIP] xcursor manager

fixes #133

I'm trying to figure out why it doesn't actually show the cursor with this.

Can you review the last commit for the implementation of get_xcursor?
It seems right, but there might be issues.
The XCursor returned should ideally not ever be dropped. If it is dropped, it must be dropped before the manager because it will be invalid after the manager is freed.
I am assuming that the xcursor will never be unloaded during the lifetime of the manager, which I think is a good assumption.

In the pointer example, the output_added callback never runs.

Please also fix the warnings in the pointer example that were introduced.
For results it's fine to unwrap.
Also can you remove the gl dependency from the Cargo.toml since we are no longer using it?

Looks like this PR is shaping up really nicely! Just a few things that needs fixing (and it looks like we still need the name function for XCursorManager).
Can you also copy and paste the documentation from the headers as doc comments above the functions? It makes it easier for the user to understand what it does when exploring the output of cargo doc. Please also update the references to NULL with None since that doesn't make sense in Rust.
Thanks again for doing this! I appreciate the hard work it took to learn enough Rust to do this and to put up with the weird style that wlroots-rs requires for working with unsafe C code.

I have #152 open to remove the gl stuff.
I think I addressed everything. Is there anything I'm missing?

Perfect, thanks!


Update dependencies

Fixing dependecies.

Coverage remained the same at 59.465% when pulling 312d29df8a1f54de707f98587975b0d16804b9ef on update_dependencies into 3102bf3a32d52221d905f4efa4afb58107bded29 on master.


fix: correctly set typedoc with npx

Current dependencies on/for this PR:

main

PR #180   👈

This stack of pull requests is managed by Graphite.


Spoul fruits should generate a lot more commonly

Closing as spoul fruit is not currently in the mod.


GeographyGroup is missed in az account list-locations result

az feedback auto-generates most of the information requested below, as of CLI version 2.0.80
Describe the bug
GeographyGroup is missed in az account list-locations result
To Reproduce
az account list-locations
Expected behavior
GeographyGroup info for each region should be return
Environment summary
cli version: 2.0.80
Additional context
This seems introduced by recent REST api upgrade, cli should be updated to include these new location metadatas

Corresponding PowerShell issue: https://github.com/Azure/azure-powershell/issues/10974

service issue

Any ETA for when the fix will be ready?

service team should look into this.

We have bumped the SDK and API version. The feature will be released in version 2.9.0 on 07/14/2020.


Font Viewer updates

Changes

Sample code for Italics and Bold was out of order
Removed the "Regular" font preview, as it basically duplicates the font sample above it anyway

@humphd - yeah I'll remove the string from Thimble.


Don't overwrite existing release body, if it exists.

It would be nice if create-release would not clear out an existing release body when its run when there is already a release existing at a particular tag.
Right now, it just clears out the body.
Essentially, I'm trying to use create-release as more of a get-release, in order to add assets to a pre-existing release from an action.

Nevermind this info is wrong.


Support executing .bat script as a compiler on Windows

rustc has code to execute a .bat script as a linker on Windows because it's difficult to otherwise use a script as a linker there:
https://github.com/rust-lang/rust/blob/d2048b6db375299b681d4f4728b8e7cad9f74d5f/src/librustc_codegen_llvm/back/link.rs#L59
In the Firefox build we don't currently pass compiler paths to cargo for build scripts to use because msys' path translation makes a mess of them (mostly because we're using sccache and having a space in the path breaks things):
https://searchfox.org/mozilla-central/rev/c07aaf12f13037c1f5a343d31f8291549e57373f/config/rules.mk#917
If this crate supported executing a .bat script as a compiler on Windows we could instead put everything we needed in there and simply pass the path to the .bat which ought to work.

Just want to chime in here that .cmd is another similar one. Android ndk is using .cmd in the replace of clang

Would the correct place to do this be around here?
https://github.com/alexcrichton/cc-rs/blob/388bf178f6c857bb07bcc333ceb31032fbee686c/src/lib.rs#L2901-L2908
Just test for *.bat or *.cmd and if so change the command to cmd and prepend the "/c "{command}" args?


feat: Add initial version of noir.js

Description
A simple package that exports acvm_js and noirc_abi
Problem*
Resolves https://github.com/noir-lang/Planning/issues/32, https://github.com/noir-lang/Planning/issues/31
Summary*
Creates a package that exports acvm_js and noirc_abi
Documentation

[ ] This PR requires documentation updates when merged.

[ ] I will submit a noir-lang/docs PR.

[ ] I will request for and support Dev Rel's help in documenting this PR.

Additional Context

PR Checklist*

[ ] I have tested the changes locally.
[ ] I have formatted the changes with Prettier and/or cargo fmt on default settings.

On second thoughts, might it be safer to require the version bump to have been done already manually?
This makes running the release workflow idempotent.

Not a blocker.

require the version bump to have been done already manually?

yeah I don't mind doing that

Actually, let's merge this and then we can address both workflows together.

Oh sorry already pushed it


Looks nothing like Google Inbox?

I'm a little confused. Is this not supposed to make your gmail look and function more like inbox? I downloaded the source, npm install/start and I get an electron app that just looks like a wrapper around the regular gmail.
There is no Google Inbox UI in sight.

This is my fault, let me explain. Inboxer worked by packaging the Inbox web-version as a desktop app. However, Google decided to discontinue Inbox by the end of March leaving us in a pickle. Either we accept that Inboxer will stop working at the end of the month or we attempt to implement all of Inbox features on top of regular Gmail. For now we have reworked Inboxer to work with regular gmail so that Inboxer will continue to work beyond this month.
I did not think about how confusing this sudden change would be, with a new release that simply shows gmail. This whole thing could have been done much better. I think it would make sense to have a dialog window that displays on 1st run explaining the situation, and maybe a more detailed explanation in the README file.

There's a new release (v1.3.1) that provides some info to the user on startup in the hopes of reducing the confusion this whole situation is creating. Nothing else is changed though, it still uses regular Gmail.
If you want to keep using Inboxer with Inbox you can use release v1.2.2, which is still based on Inbox. Be warned, that version will most likely stop working once Google pulls the plug on Inbox.

Cool. I just brought it up because this project has been referenced on Reddit as an alternative to inbox, once inbox is gone, which it obviously isn't as it relies on Inbox to provide the Inbox experience. Perhaps one day! Keep up the good work.

@jmarino is there a branch going for an inbox-on-top-of-gmail implementation?

We don't have anything towards an implementation of Inbox on top of Gmail at this point. And let me be honest, it sounds like a really difficult task that may not be worth the trouble. Google does not expose their API to access email, we are left with the final html product that Gmail/Inbox produces. Inboxer parses it to detect new messages and such.
In my mind to re-implement Inbox on top of Gmail we would have to parse email messages from Gmail and repackage them to make them look as Inbox. Have a background Gmail page from where we mine the data and a user facing one where we show an Inbox like view. This sounds like a nightmare but I would love to be proved wrong :P
I am sad that Inbox is going away, it was a really interesting interface for email. But I still see value in Inboxer working with Gmail, I like having a stand alone email client rather than a browser tab. So even if I'm forced to use Gmail and not Inbox, it's still preferable to do it though Inboxer than through imap and a regular email client.

I see, I kinda expected Google to have implemented a proper API, but probably it exist, and it's just not being used/accessible by the web interface but only the mobile apps

It would be interesting to reverse-engineer the  API that the mobile app uses, but there's a good chance they're going to turn that off anyway when they turn off Inbox, so it might be in vain.

Can we do something like sortd but instead have inbox by Gmail UI/UX?

Best alternative I’ve found is Edison mail. But it’s an app for iOS. No desktop/web version.

With the recent switch back to the classic Gmail UI it would make sense to rename the project Gmailer instead of Inboxer.
I think as long as it is called Inboxer people will expect the Inbox by Gmail UI experience. I'm one of them. By chance I found this issue otherwise I would not have known until downloading and installing which would have felt lame...

At the very least the readme needs to be heavily modified. THere’s still a screenshot that shows inbox. At this point I’m starting to suspect the author is intentionally not clarifying it to benefit from the residual inbox shutdown traffic.
I’m not trying not to be confrontational. It’s my honest view.

A new screenshot would be a great and fairly easy contribution to the project.

I want to close this project. Take a look at the explanation: https://github.com/denysdovhan/inboxer/issues/101
If you still need this project, please, fork the repo.


is_a!() contains a debugging println!()

On line 470.

Thanks for catching this! Fixed in 2270fb1


change event not called

Thanks for this. Looks like there might be a bug.
   <VCreditCard ref="creditCard" @change="creditInfoChanged" />
methods: {
 creditInfoChanged(values) {
   console.log("good")
   for (const key in values) {
     this.cardInfo[key] = values[key];
   }

   //validate logic
   this.validateCard = false;
 },
}

The creditInfoChanged function is never called. That's why I put ref and now using this.$refs.creditCard.form to get values when clicked submit button.
Could you look into this?

I have the same issue. Have you found a solution ?

I just looked into this issue, everything seams to work great. I've created a new vue-cli project, installed the v-credit-card package and using the same code as the example in the README file I was able to get this function log values on every change.
Please double check your setup and make sure it's all correct.
If you still have an issue, upload an example project that can reproduce this error and I'll do my best to fix it.

Closing this issue, can't reproduce..


add same person mask generator for comfyui node?

in automatic1111, its tooo good one , can you do it for comfy ui version

Already done.
https://github.com/djbielejeski/a-person-mask-generator?tab=readme-ov-file#install---comfyui


598 - Fix pydantic validation error

Pydantic validation error happens when using IterativeGraph module.
Problem arises when the IterativeGraph module tries to use the same instantiation of a  class for multiple execution, causing the class to not pass correctly llm into his functions.

Modified Search graphs to move instantiation inside IterativeGraph
IterativeGraph now creates multiple instances of the class we want to iterate over. This can be made better.

Will fix this merge commit


Replace unwrap()s by '?'

These unwrap()s lead to panic on the
real linux machine, but I don't know
what is cause of dbus error.

published to crates.io as 0.5.1

Thanks!

np, thanks for the pr
On Wed, Oct 4, 2017 at 2:27 PM, Aleksei Arbuzov<EMAIL_ADDRESS>wrote:

Thanks!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/hwchen/keyring-rs/pull/12#issuecomment-334247558, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADm0i12SWRQcVhMlXyDtirmvW2SLL_0_ks5so84ngaJpZM4Pt4H1
.