-
Notifications
You must be signed in to change notification settings - Fork 32
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
Unexpected exception (non blocking for the web app) #604
Comments
Here is another test I tried : duplicate a tab of your browser opened on an os web app (with user connected).
|
ocsigenserver.2.16.1 Pausing and restarting a server a few hours later, with a running web app, caused the same Unexpected exception as described before..
|
Is |
As far as I know this is considered normal behaviour for the moment. If I remember correctly it is a minor problem, yet relatively difficult fix. I'm sorry that I cannot give you more details. @vouillon? |
ocsigen-start is supposed to use cohttp (since Jul 18, 2019 v 2.2.2 according to https://opam.ocaml.org/packages/ocsigen-start/ocsigen-start.2.0.1/ and https://opam.ocaml.org/packages/ocsigen-start/ocsigen-start.2.2.2/) Is it correct ? FYI, I saw the same error recently. I suspect that it may be caused by a desktop machine (for dev&test), that is suspended while ocsigen-start is executed, when resuming. |
This is an old and non blocking exception.
The ocsigenserver console displays the following.
You can try to reproduce it by clicking on the manual link generated in the console when you add a new user (instead of using the account activation email). However, I was not able to reproduce it systematically.
You can read
**Invalid_argument** Lwt.wakeup
with a backtrace involving src/core/lwt.ml to stdlib.ml .Is it a normally caught exception or is it something that needs to be fixed?
Thanks
The text was updated successfully, but these errors were encountered: