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.

add ability to not answer (not even SERVFAIL)

It seems that testbound has some support for this in TIMEOUT, see https://github.com/NLnetLabs/unbound/blob/release-1.6.4%404248/testcode/replay.c#L302 .

Example of test using this is: https://github.com/NLnetLabs/unbound/blob/release-1.6.4%404248/testdata/fwd_timeout.rpl

Investigation is needed as first step:

How does it behave in testbound?
Does it make sense to implement it in Deckard?
If not, how can we simulate timeouts?

Edited Aug 02, 2017 by Petr Špaček

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information