Some errors are very vague

[235]

Thanks to buildandrun we can get a line number in an unknown file, however this still does not help.

$ ./buildandrun --config topology.yaml
Adding resources/logconfig.ini
Adding resources/petrel-0.0.0-py2.7.egg
Adding resources/__submitter__.yaml
Adding resources/__topology__.yaml
Adding resources/randomsentence.py
Adding resources/setup_randomsentence.sh
Adding resources/wordcount.py
Adding resources/setup_wordcount.sh
Adding resources/splitsentence.py
Adding resources/setup_splitsentence.sh
Adding resources/topology.ser
[Errno 2] No such file or directory
Error on or near line 24; exiting with status 1

[barrywhart]

It's failing on this line of buildandrun:

petrel submit --sourcejar ../../jvmpetrel/target/storm-petrel-*-SNAPSHOT.jar $@

You probably forgot to build the jvmpetrel project. Make sure you follow the instructions in the README. There are a few manual setup steps before you can build and run a topology.

[235]

problem just found, storm was not in $PATH. It would be nice to have a sanity check before this command: os.execvp('storm', submit_args)

[kbourgoin]

I think the larger issue, which I ran into, is that full stack traces weren't being printed out on errors. It looks like the line to do so was commented out, so I put it back in: https://github.com/Parsely/Petrel/commit/9aca6e0ca6e1cb0af3335256e62c6e2bac8ddae7

[barrywhart]

Good idea -- I will make that change in my repo. When writing tools like this, it's often a struggle to know whether to show stack traces or not. They are great for developers, but they can terrify other people!