You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The error it says is Failure "Nested calls to Lwt_main.run are not allowed", which seems like a weird result.
I know that maybe exit(1) is not the "lwt"-ish way but maybe this error should say something else?
context: I got it as an issue in fnm: Schniz/fnm#181
I fixed it with returning a result, instead of exiting, which is probably a better way of doing it.
The text was updated successfully, but these errors were encountered:
Thanks, that was a bug in Lwt_main. The linked commit should fix it. I'll release this next Monday, mainly because there was a release this weekend, and I think I should limit the rate a little :)
Seems that Lwt 5 throws a weird error when using `exit(1)` inside a
promise. So instead of exiting in the command, making all executable
modules a function that returns a `result((), status_code)` is a better fit.
Relates to: ocsigen/lwt#758
The error it says is
Failure "Nested calls to Lwt_main.run are not allowed"
, which seems like a weird result.I know that maybe
exit(1)
is not the "lwt"-ish way but maybe this error should say something else?context: I got it as an issue in fnm: Schniz/fnm#181
I fixed it with returning a
result
, instead of exiting, which is probably a better way of doing it.The text was updated successfully, but these errors were encountered: