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

Build Error struct and use it #121

Merged
merged 1 commit into from
Oct 8, 2020
Merged

Conversation

puiterwijk
Copy link
Member

Signed-off-by: Patrick Uiterwijk [email protected]

Signed-off-by: Patrick Uiterwijk <[email protected]>
}

fn response_function(req: Request<Body>) -> BoxFut {
async fn response_function(req: Request<Body>) -> Result<Response<Body>> {
Copy link
Member

Choose a reason for hiding this comment

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

Is there any reason for changing to asynchronous , we historically only used async on the verifier (which is one to many) where as the agent has never been a performance factor (as it only deals serving with one verifier typically or talking to the TPM)

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, because that's technically what you always did with Hyper, it was just hidden behind a Future. I just rebased to Hyper 0.13 as part of this, so the types worked out.

Comment on lines +39 to +44
pub(crate) fn config_get(
conf_name: &str,
section: &str,
key: &str,
) -> Result<String> {
let conf = Ini::load_from_file(conf_name)?;
Copy link
Member

Choose a reason for hiding this comment

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

That's a lot more tidy!

@puiterwijk puiterwijk merged commit 76443fc into keylime:master Oct 8, 2020
@puiterwijk puiterwijk deleted the errorstruct branch October 8, 2020 15:01
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.

2 participants