upgrade to lbry.go v2.4.0 #30
No reviewers
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
dependencies
Epic
good first issue
hacktoberfest
help wanted
icebox
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/reflector.go#30
Loading…
Reference in a new issue
No description provided.
Delete branch "lbry_tv"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This includes updated references to the latest
lbry.go
version.I also downgraded some excessive INFO-level logging calls to DEBUG.
one small change requested. lgtm besides that
doing this is not a good idea. just set the 0 as the Client timeout. that already signals the Client to use a default.
if you do this here, not only is this duplicating code, but now if the Client's default changes, you'll be stuck on 5 seconds here (unless this was your intention???)
i dont love this design here, but maybe there's no better way to do optional arguments in Go?
no need to spend much time on improving this. just thinking out loud.
❤️
Seems to be the default method of accepting optional parameters for functions (especially for constructors), I see it all the time in 3rd party code too. I personally would've preferred pattern matching (a la Elixir) or optional arguments (Python) but I simply don't see a better way in Go.