runData fails on MDK example

[repolainen]

When trying to run gradle task 'runData' on fresh downloaded MDK mod example I'm getting an error "An existing connection was forcibly closed by the remote host"

What I did:

1. Downloaded & unzipped forge-1.15.2-31.1.18-mdk.zip 

2. Opened the project in IDEA (up-to date version)

... gradle project import downloads stuff, generates runs

3. run 'runData' task

4. got an error "An existing connection was forcibly closed by the remote host"

 

latest.log:

[11Mar2020 02:18:29.191] [main/INFO] [cpw.mods.modlauncher.Launcher/MODLAUNCHER]: ModLauncher running: args [java.util.stream.ReferencePipeline$3@3b07b04d, --gameDir, ., --launchTarget, fmluserdevdata, --fml.mcpVersion, 20200122.131323, --fml.mcVersion, 1.15.2, --fml.forgeGroup, net.minecraftforge, --fml.forgeVersion, 31.1.18]
[11Mar2020 02:18:29.194] [main/INFO] [cpw.mods.modlauncher.Launcher/MODLAUNCHER]: ModLauncher 5.0.0-milestone.4+67+b1a340b starting: java version 1.8.0_102 by Oracle Corporation
[11Mar2020 02:18:29.373] [main/INFO] [net.minecraftforge.fml.loading.FixSSL/CORE]: Added Lets Encrypt root certificates as additional trust
[11Mar2020 02:18:30.235] [main/INFO] [cpw.mods.modlauncher.LaunchServiceHandler/MODLAUNCHER]: Launching target 'fmluserdevdata' with arguments [--gameDir, ., java.util.stream.ReferencePipeline$3@3b07b04d]
 

debug.log is quite long but there is nothing about any remote host

[DaemonUmbra]

That's normal

[repolainen]

Can you be more explicit? What this error message means, what it is caused by?

[DaemonUmbra]

I don't 100% know what causes it, but it's probably due to Forge forcibly stopping the game from fully loading, as DataGen runs on an instance of Minecraft that is JUST started enough to have the registries populated, but no further

[repolainen]

This is not exactly helpful, because MDK is not the only project where runData doesn't work, it is just a reproducer. Also I'm not the only person with such a problem.

I may upload the --debug logs, and try any necessary experiments.

[DaemonUmbra]

What do you mean it "doesn't work"?

The only thing you've posted is that it is closing in an abnormal but expected way.

[repolainen]

"doesn't work" as in: generates no data and logs an error?

[DaemonUmbra]

Where are you telling it to generate data? and what data?

At this point I might as well ask if your mod's source is on GitHub

Edited March 12, 2020 by DaemonUmbra

[repolainen]

Let's talk just MDK example, ok?

[DaemonUmbra]

The ExampleMod that has absolutely no code to generate data and that shows the error that I already said is expected?

[repolainen]

Ah, I see, thanks for the explanation. Well, the other mod I get the same message from totally has code to generate resources, and it does not do that with exactly the same symptoms, so I assumed the reason must be the same. The mod in question is https://github.com/GregTech-Intergalactical/GregTech Also, having gradle task return an expected error even if it has nothing to do is a bit misleading.

 

Actually, I added the following code to the MDK example class:

@SubscribeEvent
public static void onDataGather(GatherDataEvent e) {
    DataGenerator gen = e.getGenerator();
    if (e.includeClient()) {
        LOGGER.info("HELLO from client data gather");
    }
    if (e.includeServer()) {
        LOGGER.info("HELLO from server data gather");
    }
}

and at the top

@Mod.EventBusSubscriber(bus = Mod.EventBusSubscriber.Bus.MOD)

tried runData again, and there was nothing about data gather in the logs. So, how do I receive GatherDataEvent, and if not, then what is the correct place to register resources?

Edited March 12, 2020 by repolainen

[P3pp3rF1y]

I had the exact same problem with my project where runData worked last I ran it 1-2 months ago and now stopped working with similar messages. Tracked it down to bug in how arguments are grabbed for run configs in ForgeGradle and there's apparently a fix for it that's already approved as well https://github.com/MinecraftForge/ForgeGradle/pull/657.

[repolainen]

Great, thanks. Perhaps you know some duct tape workaround, to manually fix the arguments, until the fix will be merged?

[DaemonUmbra]

The fix was merged an hour after P3pp3rF1y posted

[repolainen]

Ok, nice, will test this evening.