e-chip / redis-rwlock Goto Github PK

When running go build in my project, following error is shown:

go: finding github.com/e-chip/redis-rwlock latest
go: downloading github.com/e-chip/redis-rwlock v0.0.0-20191030182710-122e3f7ba621
build xxx: cannot load github.com/e-chip/redis-rwlock/v1: cannot find module providing package github.com/e-chip/redis-rwlock/v1

Failed to run go get with go module:

$ go get github.com/e-chip/redis-rwlock/v1
go: finding github.com/e-chip/redis-rwlock latest
go: downloading github.com/e-chip/redis-rwlock v0.0.0-20191030182710-122e3f7ba621
go get github.com/e-chip/redis-rwlock/v1: go.mod has post-v0 module path "github.com/e-chip/redis-rwlock/v1" at revision 122e3f7ba621

After reexamine with the go module documentation. There is a statement in the section of Semantic Import Versioning:

If the module is version v0 or v1, do not include the major version in either the module path or the import path.

Furthermore, the semver VCS tag is also required if you would like to support to get specific version by semver. (What happens if I create a go.mod but do not apply semver tags to my repository?)

Currently I use lock in web api to prevent concurrent requests for the same resource. Each resource is given unique GLOB_LOCK_KEY, READ_LOCK_REF_COUNT, and WRITER_LOCK_INTENT keys.

Nevertheless, I found READ_LOCK_REF_COUNT is not deleted when read unlock, and it is not set TTL. It is only deleted when requesting write lock.

In my case, write lock is necessary but rarely used. It makes redis full of unused READ_LOCK_REF_COUNT keys.