Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: fatal errors are swallowed #1139

Closed
jberdine opened this issue Nov 12, 2019 · 6 comments · Fixed by #1180
Closed

Bug: fatal errors are swallowed #1139

jberdine opened this issue Nov 12, 2019 · 6 comments · Fixed by #1180
Milestone

Comments

@jberdine
Copy link
Collaborator

Describe the bug
Since #1127 fatal errors such as Fatal error: exception ("User Error: malformed .ocamlformat file" that used to exit 2 with an uncaught exception now just silently succeed without doing anything.

@emillon
Copy link
Collaborator

emillon commented Nov 13, 2019

Ah, that's not great. I think we'll need to cut a point release for this. @Julow do you know how to fix this?

@emillon
Copy link
Collaborator

emillon commented Nov 13, 2019

Ah my bad it's not in the release. All good then. Still needs to be fixed though :)

@Julow
Copy link
Collaborator

Julow commented Nov 13, 2019

A minor release for that is not needed, #1127 is not released.

The error message changed from

Fatal error: exception ("User Error: malformed .ocamlformat file" ...
backtrace

to

ocamlformat: internal error, uncaught exception:
             ("User Error: malformed .ocamlformat file" ...
             backtrace

and the exit status changed from 2 to 1. That's a regression indeed.

I can't reproduce silently succeed without doing anything. What was the full error message ?

@jberdine
Copy link
Collaborator Author

Sorry, the 'silently succeeding' I see is through the emacs integration, but on the command line it does exit with status 1.

I'm not sure what is going on in the emacs integration to do that. Can anyone else repro, or is it just here?

@jberdine
Copy link
Collaborator Author

I think the problem is that the error output now is sent to stdout instead of stderr

@Julow
Copy link
Collaborator

Julow commented Dec 10, 2019

@jberdine #1180 should fix this issue. Is it working for you ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants