"locks --verify" can be combined with "--cached" option now in the same way as for "plain" remote queries. Cached data is stored in a separate file "path/to/ref/verifiable", next to the "plain" remote query cache file. This resolves issue #3252.
Latest commit
ce1c1c0
Mar 28, 2019
| Type | Name | Latest commit message | Commit time |
|---|---|---|---|
| .. | |||
| Failed to load latest commit information. | |||
|
|
schemas |
|
|
|
|
api.go |
|
|
|
|
api_test.go |
|
|
|
|
cache.go |
|
|
|
|
cache_test.go |
|
|
|
|
lockable.go |
|
|
|
|
locks.go | ||
|
|
locks_test.go |
|
|