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.

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

Please correct the tag and add a go.mod file #1

Closed
curiosport opened this issue Jan 22, 2023 · 5 comments
Closed

Please correct the tag and add a go.mod file #1

curiosport opened this issue Jan 22, 2023 · 5 comments

Comments

@curiosport
Copy link

The following command:
go get github.com/fpessolano/jac@latest
download version v0.1.0

I had to do this mischief in the go.mod file:
require github.com/fpessolano/jac v.0.2.0

And return this:
downgrading to v0.1.1-blabla

The version "v0.1.1" is equal to v.0.2.0

Correct tag to: v0.2.0

@fpessolano
Copy link
Owner

As far as i can see 0.2.0 is set as latest release.

@curiosport
Copy link
Author

As far as i can see 0.2.0 is set as latest release.

Did you at least execute the command I showed you?
go get github.com/fpessolano/jac@latest

This command installs version v0.1.0 and that happens because Go does not understand the numbering of the latest version v.0.2.0
https://github.com/fpessolano/jac/tags

v.0.2.0 -> Bad numbering
v0.2.0 -> Good numbering


I asked for a go.mod because I thought you were using the go-cache package but it wasn't that, it was that your example in the README is wrong.

jac is a persistent in-memory key:value/store cache based on go-cache

// Set a persistent value of the key "one" to "1", with the default expiration time
test.Set("one", 1, cache.DefaultExpiration, true)

// Set a non-persistent value of the key "b" to "2", with no expiration time
test.Set("two", "two", cache.NoExpiration, false)

// Correct:
// test.Set("one", 1, jac.DefaultExpiration, true)
// test.Set("two", "two", jac.NoExpiration, false)

@fpessolano
Copy link
Owner

sorry but I am not maintaining this any longer. It has served its purpose and will be archived

@fpessolano fpessolano reopened this Mar 1, 2023
@fpessolano
Copy link
Owner

Got some time and curiosity to play with go again. The readme file is wrong and will eb fixed and will look into your suggestion.

@fpessolano
Copy link
Owner

Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants