Closed markstos closed 2 years ago
I also had sup 0.22.1 crash today because of invalid paths configured in the config-file. I would suggest to check the paths on startup and exit clean with a sensible errormessage if they are not valid.
The stack trace is from loading sources.yaml
but the issue description only includes config.yaml
so it's hard to be sure exactly what was going wrong.
This is likely related to the Syck-to-Psych transition which Ruby went through in 1.9 -> 2.0. From version 0.14.0 onwards, sup included a tool sup-psych-ify-config-files
to handle the migration, but from version 0.16.0 onwards the tool refuses to run on Ruby 2.1+, presumably because Psych would no longer successfully parse the old Syck-generated YAML at that point.
At this point anybody hitting this issue would presumably be best to just re-create their sources.yaml
from scratch.
I installed
sup-mail
on Ubuntu 16.04, ransup-mail
for the first time, and it crashed on startup. Below is.sup/exception-log.txt
.I believe the issue is apparently I tried
sup
in 2009, and still had a.sup/config.yml
from then. It would be nice ifsup-mail
could not crash in the presence of a bad config file.Here's the old .sup/config.yaml which triggered the exception: