Closed repligator closed 2 months ago
Different file, different version of MML, same NPE.
Linux Java 17 MML Code Revision: b1b0bee27fee84bfe1af4375aba9a5423258cea7
This is a weird one for a few reasons:
Nevertheless, the NPE shows that it is possible to hit this state, and it is conceivable that the call to get a unit's engine entry might return a null
value, so I'll safety this.
I normally run MM/MML/MHQ from IDEA, but I have some nightlies installed on an old Thinkpad. When I open the attached files on the computer I normally use, running the latest MML from IDEA, they work fine. But there haven't been any commits in time between the https://github.com/MegaMek/megameklab/commit/b1b0bee27fee84bfe1af4375aba9a5423258cea7 and the present version of MML. Is it possible something changed in MM?
It's possible, yeah. The code MML is calling at the bottom of that stack of calls is actually in MegaMek. I'm just finishing up adding a unit test for this, then I'll try rolling the MM code back a bit and see if I can get a reliable repro with your files.
Environment
Linux Java 17 MegaMekLab Nightly CI 1578
Description
Received the NPE when trying to preview or export a PDF of the attached BLK file.
Files
RMS Titanic Titanic.blk.zip megameklab.log