Tried to test last build for version 8, but had a cyclical dependency error

Question

Tried to test last build for version 8, but had a cyclical dependency error

kotoroshinoto opened this issue 10 years ago · 4 comments

kotoroshinoto commented 10 years ago

[16:52:29] [Server thread/ERROR] [FML]: A dependency cycle was detected in the input mod set so an ordering cannot be determined
[16:52:29] [Server thread/ERROR] [FML]: The first mod in the cycle is FMLMod:EnderIO{1.7.10-2.2.8.349}
[16:52:29] [Server thread/ERROR] [FML]: The mod cycle involves
[16:52:29] [Server thread/ERROR] [FML]: Dummy Container (After) @2097918299 : before: [], after: []
[16:52:29] [Server thread/ERROR] [FML]: APIContainer{MekanismAPI|core:8.0.0} : before: [EnderIO], after: [Mekanism]
[16:52:29] [Server thread/ERROR] [FML]: FMLMod:Mekanism{8.0.0} : before: [], after: [ForgeMultipart, BuildCraftAPI|power, BuildCraftAPI|tools, BuildCraftAPI|transport, IC2API, CoFHAPI|energy, ComputerCraft, Galacticraft API, MineFactoryReloaded, MetallurgyCore, EnderIO, ExtraUtilities, Railcraft, Forestry, RedstoneArsenal]
[16:52:29] [Server thread/ERROR] [FML]: Dummy Container (AfterAll) @398228595 : before: [], after: []
[16:52:29] [Server thread/ERROR] [FML]: FMLMod:EnderIO{1.7.10-2.2.8.349} : before: [], after: [[email protected],), MineFactoryReloaded]
[16:52:29] [Server thread/ERROR] [FML]: The full error
cpw.mods.fml.common.toposort.ModSortingException: There was a cycle detected in the input graph, sorting is not possible
at cpw.mods.fml.common.toposort.TopologicalSort.explore(TopologicalSort.java:190) ~[TopologicalSort.class:?]
at cpw.mods.fml.common.toposort.TopologicalSort.explore(TopologicalSort.java:199) ~[TopologicalSort.class:?]
at cpw.mods.fml.common.toposort.TopologicalSort.explore(TopologicalSort.java:199) ~[TopologicalSort.class:?]
at cpw.mods.fml.common.toposort.TopologicalSort.explore(TopologicalSort.java:199) ~[TopologicalSort.class:?]
at cpw.mods.fml.common.toposort.TopologicalSort.explore(TopologicalSort.java:199) ~[TopologicalSort.class:?]
at cpw.mods.fml.common.toposort.TopologicalSort.explore(TopologicalSort.java:199) ~[TopologicalSort.class:?]
at cpw.mods.fml.common.toposort.TopologicalSort.topologicalSort(TopologicalSort.java:145) ~[TopologicalSort.class:?]
at cpw.mods.fml.common.toposort.ModSorter.sort(ModSorter.java:133) ~[ModSorter.class:?]
at cpw.mods.fml.common.Loader.sortModList(Loader.java:256) [Loader.class:?]
at cpw.mods.fml.common.Loader.loadMods(Loader.java:472) [Loader.class:?]
at cpw.mods.fml.server.FMLServerHandler.beginServerLoading(FMLServerHandler.java:87) [FMLServerHandler.class:?]
at cpw.mods.fml.common.FMLCommonHandler.onServerStart(FMLCommonHandler.java:314) [FMLCommonHandler.class:?]
at net.minecraft.server.dedicated.DedicatedServer.func_71197_b(DedicatedServer.java:117) [lt.class:?]
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:387) [MinecraftServer.class:?]
at net.minecraft.server.MinecraftServer$2.run(MinecraftServer.java:685) [li.class:?]
[16:52:29] [Server thread/ERROR]: Encountered an unexpected exception
cpw.mods.fml.common.toposort.ModSortingException: There was a cycle detected in the input graph, sorting is not possible��

kotoroshinoto · Answer 1 · 2015-03-11T21:26:40.000Z

looking at the repo, the file:
./src/main/java/mekanism/common/Mekanism.java:
contains the line "after:MineFactoryReloaded;after:MetallurgyCore;after:EnderIO;after:ExtraUtilities;after:Railcraft;after:Forestry;after:RedstoneArsenal")

so why would the API think that it was supposed to load BEFORE enderio?

kotoroshinoto · Answer 2 · 2015-03-11T21:13:55.000Z

Mekanism api has condition Before enderio and and after mekanism
Mekanism has condition: after enderio.

(it also reports : enderio has condition: after forge and after MFR but i dont think thats the problem here)

aidancbrady · Answer 3 · 2015-03-13T02:16:52.000Z

Merging with #2180

codewarrior0 · Answer 4 · 2015-03-14T09:11:02.000Z

Is there a good reason why Mekanism v8 needs to be loaded after EnderIO?

The problem is that EnderIO uses v8's MekanismAPI|gas, which implicitly requires Mekanism, which explicitly requires EnderIO in its required-after dependency. Removing EnderIO from Mek's required-after resolves the cycle and allows the game to start up.

Share to