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.

Sign up for GitHub

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

Jump to bottom

Quickfix: Ensure start epoch of LookupInEpochRequest and MonitoringRequest is in PAD #108

Closed
wants to merge 3 commits into from
Closed

Quickfix: Ensure start epoch of LookupInEpochRequest and MonitoringRequest is in PAD #108

wants to merge 3 commits into from

Commits on Oct 23, 2016

  1. Ensure start epoch of LookupInEpochRequest and MonitoringRequest is i… 

    …n PAD

Otherwise directory.LookupInEpoch() fails with ErrorDirectory, though a start epoch that is > the latest epoch indicates a malformed client message.
    @masomel
    masomel committed Oct 23, 2016
    Configuration menu
    Copy the full SHA
    1758a01 View commit details
    Browse the repository at this point in the history

Commits on Oct 24, 2016

  1. Create tests for invalid KeyLookupInEpoch and Montoring requests

    @masomel
    masomel committed Oct 24, 2016
    Configuration menu
    Copy the full SHA
    c5bcfdb View commit details
    Browse the repository at this point in the history

Commits on Oct 25, 2016

  1. Fix typo

    @masomel
    masomel committed Oct 25, 2016
    Configuration menu
    Copy the full SHA
    c4ae362 View commit details
    Browse the repository at this point in the history