lib/resolve kr_request_ensure_answer(): allow it to fail (cc734c25) · Commits · Knot projects / Knot Resolver · GitLab

Snippets Groups Projects

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Self sign-up has been disabled due to increased spam activity. If you want to get access, please send an email to a project owner (preferred) or at gitlab(at)nic(dot)cz. We apologize for the inconvenience.

Verified Commit cc734c25 authored 4 years ago by

Vladimír Čunát

lib/resolve kr_request_ensure_answer(): allow it to fail

For now I was too afraid to use "multi-flag" kr_request::state,
so I kept it at _FAIL; anyone can recognize it by NULL answer anyway.

Lua wrapper: using exception was considered but didn't seem good.
I utilized the fact that modules can return nil meaning no state change.

parent 273fe41a

Branches

Tags

1 merge request!985change API for reply packet buffers

Pipeline #70860 waiting for manual action with stages

in 6 minutes and 11 seconds

Hide whitespace changes

Inline Side-by-side

Showing with 65 additions and 42 deletions

Please register or to comment