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

dep: update tm-db to latest release #194

Merged
merged 4 commits into from
Jan 14, 2020
Merged

dep: update tm-db to latest release #194

merged 4 commits into from
Jan 14, 2020

Conversation

tac0turtle
Copy link
Member

Signed-off-by: Marko Baricevic [email protected]

nodedb.go Show resolved Hide resolved
@tac0turtle tac0turtle self-assigned this Jan 8, 2020
@tac0turtle tac0turtle added the T:dependencies Pull requests that update a dependency file label Jan 8, 2020
@tac0turtle tac0turtle marked this pull request as ready for review January 8, 2020 12:40
nodedb.go Show resolved Hide resolved
nodedb.go Show resolved Hide resolved
nodedb.go Show resolved Hide resolved
nodedb.go Outdated Show resolved Hide resolved
nodedb.go Outdated Show resolved Hide resolved
rootHash := tree.ndb.getRoot(targetVersion)
rootHash, err := tree.ndb.getRoot(targetVersion)
if err != nil {
return 0, err
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so here is the question: at which point we should retry DB operation (say 5 times) before bubbling up an error to the caller?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in my view, I would prefer the application to handle this and here we present the error each time. @alexanderbez do you have a preference. The sdk is the main user of this repo so your preference matters most

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change looks fine and behaves as I'd expect. If the version provided cannot be fetched, then the upstream caller should handle that error (either retry another version or fail completely).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree. My question of course goes beyond this case.

@tac0turtle tac0turtle merged commit fa6bbe6 into master Jan 14, 2020
@tac0turtle tac0turtle deleted the marko/update_tmdb branch January 14, 2020 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T:dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants