-
Notifications
You must be signed in to change notification settings - Fork 33
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
Support dolmen frontend in JS worker #1232
Comments
When I try to run the worker example as follows:
Is it the issue you ran into? |
I don't think calling The issue is that the worker always uses the legacy frontend, but tries to find a "dolmen" type. The easy fix is to force the use of the "legacy" frontend in the JS worker; the long-term fix is to modify the JS worker to use the dolmen frontend instead of the legacy frontend. |
The way I run the worker is as follows (you can't simply open the $ make js-example
$ python -m http.server -d www Sending a file with "Ask Alt-Ergo" returns an error in the dev console:
and if I print the exception in diff --git a/src/bin/js/worker_js.ml b/src/bin/js/worker_js.ml
index 4d79920d..484d7812 100644
--- a/src/bin/js/worker_js.ml
+++ b/src/bin/js/worker_js.ml
@@ -259,11 +259,11 @@ let main worker_id content =
Worker_interface.diagnostic =
Some [Format.asprintf "%a" Errors.report e]
}
- | _ ->
+ | exn ->
let res = Worker_interface.init_results () in
{ res with
Worker_interface.worker_id = worker_id;
- Worker_interface.status = Error "Unknown error";
+ Worker_interface.status = Error ("Unknown error: " ^ Printexc.to_string exn);
}
(** Worker initialisation
we get a more detailed error:
|
Done in #556 |
More precisely
worker_js.ml
does not seem to be compatible with dolmen.Originally posted by @bclement-ocp in #1218 (comment)
The text was updated successfully, but these errors were encountered: