Metadata
- Source
- KETTLE-17
- Type
- Bug
- Priority
- Major
- Status
- Open
- Resolution
- N/A
- Assignee
- y z
- Reporter
- Antranig Basman
- Created
2013-08-14T19:02:35.150-0400 - Updated
2013-08-14T19:02:35.150-0400 - Versions
-
- 0.1
- Fixed Versions
- N/A
- Component
- N/A
Description
For example, the current windows loader contains the following code:
kettle.config.makeConfigLoader({
nodeEnv: kettle.config.getNodeEnv("fm.ps.sr.dr.mm.os.development"),
configPath: kettle.config.getConfigPath() || "../node_modules/universal/gpii/configs"
});
If "../node_modules/universal/gpii/configs" is changed to a nonexistent path, the system simply silently exits with no report. Since this is such a typical failure mode for node.js anyway, this misleads the user into believing that something is wrong with the binary modules. Kettle should provide a helpful report indicating the filesystem path or URL that was queried and found empty.