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

docs: Some verbose error messages #1022

Merged

Conversation

nderjung
Copy link
Member

Prerequisite checklist

  • Read the contribution guidelines regarding submitting new changes to the project;
  • Tested your changes against relevant architectures and platforms;
  • Ran make fmt on your commit series before opening this PR;
  • Updated relevant documentation.

Description of changes

This PR contains several adjustments across the project which pertain to better error message information.

@nderjung nderjung changed the title docs: Add several more verbose error messages docs: Some verbose error messages Nov 21, 2023
Signed-off-by: Alexander Jung <alex@unikraft.io>
Signed-off-by: Alexander Jung <alex@unikraft.io>
Signed-off-by: Alexander Jung <alex@unikraft.io>
Signed-off-by: Alexander Jung <alex@unikraft.io>
Signed-off-by: Alexander Jung <alex@unikraft.io>
Signed-off-by: Alexander Jung <alex@unikraft.io>
Signed-off-by: Alexander Jung <alex@unikraft.io>
@nderjung nderjung force-pushed the nderjung/fix/some-better-error-messages branch from 632fe42 to 4984090 Compare November 21, 2023 17:12
Copy link
Member

@craciunoiuc craciunoiuc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All good here. Thanks!

Reviewed-by: Cezar Craciunoiu cezar.craciunoiu@unikraft.io
Approved-by: Cezar Craciunoiu cezar.craciunoiu@unikraft.io

@craciunoiuc craciunoiuc merged commit 2e16186 into unikraft:staging Nov 23, 2023
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🚀 Done
Development

Successfully merging this pull request may close these issues.

2 participants