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.
Admin message
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.
when a IXFR response contains just one SOA (= up-to-date response), Knot is not able to handle it. With this patch, Knot handles and logs it correctly. (This issue is not severe since Knot normally checks with SOA query first, thus not asking for IXFR in up-to-date case.)
when a IXFR response (possibly, but not only AXFR-styled) is divided into messages such way that the first message contains just the leading SOA, Knot was misinterpreting it in some cases. This patch thoroughly inspects what has been received and decides how to handle it.
The first commit is just a little refactoring, keeping Knot functionality unchanged. The second commit does all the change.
Please check the code, it seems to me the code is not very elegant. Can it be simplified/improved?
