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

Update dependencies. Requires go 1.18 and BasicLimiter -> ScalingLimitConfig #529

Merged

Conversation

neelvirdy
Copy link
Contributor

@neelvirdy neelvirdy commented Nov 14, 2022

quic-go dropped support for go 1.17 in 0.29.0 so we have to require go 1.18 moving forward.

libp2p's rcmgr lib did a migration from BasicLimiter to ScalingLimitConfig in 0.21.0. This hardly effects us since we run with the NoLimiter flag set to true, so we dont even go down the impacted code path. But the migration is done and tested in case we switch. If we have any json-loading of the Node config struct we will need to adapt that wherever that lives to fit ScalingLimitConfig's schema.

Next blocker for getting to latest is filclient: https://github.com/application-research/filclient/blob/master/go.mod#L39-L41. Will track a follow-up to get filclient updated and then continue updating estuary.

@en0ma
Copy link
Contributor

en0ma commented Nov 15, 2022

If we have any json-loading of the Node config struct we will need to adapt that wherever that lives to fit ScalingLimitConfig's schema.

We do not

en0ma
en0ma previously approved these changes Nov 15, 2022
config/shuttle.go Outdated Show resolved Hide resolved
go.mod Show resolved Hide resolved
alvin-reyes
alvin-reyes previously approved these changes Nov 15, 2022
Copy link
Contributor

@alvin-reyes alvin-reyes left a comment

Choose a reason for hiding this comment

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

I ran the build on my local and executed a few regression tests and this seems to work as expected. I have a few minimal feedback but mostly nits. Great work on adding more assertions.

One thing I'm concerned with this update is if it's somehow impacts Graphsync and/or boost transfers. It shouldn't but it be good to test it.

Let's just merge this to dev and see if we can test those out. If it's ok, maybe let's run some graphsync and boost transfers with this bumps? It would be interested to know if this somehow impacts AR/filclient.

@en0ma @neelvirdy @elijaharita @gmelodie

@neelvirdy neelvirdy dismissed stale reviews from alvin-reyes and en0ma via 601c9b6 November 15, 2022 20:41
Copy link
Contributor

@alvin-reyes alvin-reyes left a comment

Choose a reason for hiding this comment

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

LGTM

@neelvirdy neelvirdy merged commit d5f6b54 into application-research:dev Nov 16, 2022
@neelvirdy neelvirdy deleted the nvirdy/update-dependencies branch November 16, 2022 17:05
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

Successfully merging this pull request may close these issues.

None yet

4 participants