-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
ipfs name publish doesn't take the TTL into account when caching locally #6670
Labels
kind/bug
A bug in existing code (including security flaws)
Comments
Stebalien
added a commit
that referenced
this issue
Sep 24, 2019
No fix is complete without a test. fixes #6670
I can't reproduce but I've written a regression test for this: #6671. |
Stebalien
added a commit
that referenced
this issue
Jan 17, 2020
No fix is complete without a test. fixes #6670
Stebalien
added a commit
that referenced
this issue
Jan 17, 2020
No fix is complete without a test. fixes #6670
ralendor
pushed a commit
to ralendor/go-ipfs
that referenced
this issue
Jun 6, 2020
No fix is complete without a test. fixes ipfs#6670
ralendor
pushed a commit
to ralendor/go-ipfs
that referenced
this issue
Jun 8, 2020
No fix is complete without a test. fixes ipfs#6670
ralendor
pushed a commit
to ralendor/go-ipfs
that referenced
this issue
Jun 8, 2020
No fix is complete without a test. fixes ipfs#6670
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version information:
Description:
From ipfs/notes#391 (comment) by @postables:
I've been doing some testing on the fix for #6656, and it doesn't seem like its working. For whatever reason the ttl value in the context seems to be getting overwritten somewhere.
If you modify the
cacheEntry
to also include a ttl, and run the following test:it will fail on the test named
TTL-Set
which is the test which derives the ttl value through the passed in context valueThe text was updated successfully, but these errors were encountered: