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

Add Mirage bounds in config.ml (since mirage 4.4.1, mirage/mirage#1466) #395

Merged
merged 1 commit into from
May 16, 2024

Conversation

hannesm
Copy link
Member

@hannesm hannesm commented May 10, 2024

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 #338

@hannesm
Copy link
Member Author

hannesm commented May 10, 2024

NB: some unikernels (without parameters) are supposed to work with mirage 4.4.0 -- that's why the bounds are not always >= 4.5.0 in this PR. This is intentional.

@hannesm
Copy link
Member Author

hannesm commented May 10, 2024

oh, excuse my ignorance -- I wasn't aware we use ocamlformat here -- so I force-pushed to adhere to the formatting.

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
@hannesm hannesm merged commit 493360d into mirage:main May 16, 2024
3 checks passed
@hannesm hannesm deleted the add-bounds branch May 16, 2024 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant