-
Notifications
You must be signed in to change notification settings - Fork 92
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
tell people which MirageOS version to use if they have the wrong one #338
Conversation
f10e677
to
d5de721
Compare
d5de721
to
83736d6
Compare
83736d6
to
b46be03
Compare
Not 100% sure the detailed check for |
extracted from mirage#338
extracted from mirage#338
The purpose is to render nice error messages to users: instead of some config.ml OCaml error, a message is printed that this unikernel is not compatible with the installed version of mirage, and please upgrade/downgrade. I also took the liberty to cleanup some of the example unikernels in terms of (a) using Duration (b) using Logs (c) a line break after the bind operator (>>=) This superseeds mirage#338
The purpose is to render nice error messages to users: instead of some config.ml OCaml error, a message is printed that this unikernel is not compatible with the installed version of mirage, and please upgrade/downgrade. I also took the liberty to cleanup some of the example unikernels in terms of (a) using Duration (b) using Logs (c) avoiding Printf This superseeds mirage#338
The purpose is to render nice error messages to users: instead of some config.ml OCaml error, a message is printed that this unikernel is not compatible with the installed version of mirage, and please upgrade/downgrade. I also took the liberty to cleanup some of the example unikernels in terms of (a) using Duration (b) using Logs (c) avoiding Printf This superseeds mirage#338
Thanks for your motivating work. We have since in Mirage 4.4 introduced a header In #395 I added these headers to all the example unikernels :) |
Thank you, Hannes. |
No description provided.