Community
Participate
Working Groups
The MOOSE Launcher will throw an EntryComposite disposed widget error and halt the launching process (FormStatus = InfoError) if no input file specified. There are 2 different ways this fails: * I don't allow the YAML/syntax generator to have any Input File entries (as it should be) * I try to launch a BISON problem without all the additional input files (power history, fast neutron flux, etc.) specified For the former scenario, the MOOSE Launcher pointlessly has an Input File entry that does nothing (since the uploadInput flag is false), that allows it to be at least functional for now. The latter scenario should eventually become a non-issue once the filename validator is implemented, but for now, all fields need to have a filename put in whether or not they actually get used.
I guess this was fixed *** This bug has been marked as a duplicate of bug 454640 ***
It was fixed. This was not a MOOSE-specific issue, but yes, it has been fixed. My apologies for creating a duplicate.
This still occurs for me. To reproduce it: 1.) Delete your itemDB and all CSV and exodus files from your workspace. 2.) Set up a MOOSE Launcher and specify a BISON input file that references other additional files (mesh, power history, etc.) 3.) The additional input FileEntries will render, but leave them blank. 4.) Try to run the job. Obviously the BISON problem will not solve without those additional files, but ICE doesn't not even attempt to launch the job. We could throw an error to say the user must specify all files, but I don't think a pre-disposed widget error is the way to do it...
Added a check on the JobLauncher to throw FormStatus = InfoError and print a console message if any Entries on the Form's "Input File" DataComponent have an invalid value (null or empty). This way the issue will never reach the UI so it doesn't have to be addressed there.
