"git lfs locks --verify" hangs if there are more than 100 LFS locks

Issue Summary

When there are more than 100 LFS files with locks in a given repository, the git lfs locks --verify command never completes.

Steps to Reproduce

1. Lock >100 files in a Git LFS repository
2. Run git lfs locks --verify on a client machine

Expected Results

List of locked LFS files is displayed

Actual Results

The command never completes and the trace output shows the first page of locked files repeated continuously.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available