Closed saleyn closed 1 year ago
I seem to be able to bypass the crash by passing the -i patch
option to hex cut
, but as I understand it, the -i
option is documented as optional, so I don't expect to see a crash if the option is not given.
Closed via #317
I closed this an error. It seems you have pointed out there still might seem to be a place to crash. I'll look further in a bit.
Hey @saleyn , I can't seem to replicate this (I cloned erlcron repo and ran cut), but I did find a bug if you choose other as the version type to go with when incrementing. Maybe you went down that path? Doesn't seem like it per your issue (i.e., you just ran cut and it blew up).
Presently I cannot reproduce it either. Maybe it's because my fix to rebar3_hex was merged or some other change was made to the head of the repo?
Presently I cannot reproduce it either. Maybe it's because my fix to rebar3_hex was merged or some other change was made to the head of the repo?
That's possible. It's also possible you were on an older version of rebar3_hex at the time. I'm glad it's all resolved, at least for now! 👍
Description
When running
rebar3 hex cut
in the source of the erlcron repository, I get a rebar3.crashdump.Here's the
rebar.config
:Environment