-
Notifications
You must be signed in to change notification settings - Fork 37
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
go.mod: Upgrade github.com/nspcc-dev/neofs-sdk-go
#3199
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #3199 +/- ##
==========================================
- Coverage 23.42% 22.15% -1.27%
==========================================
Files 760 761 +1
Lines 60848 60745 -103
==========================================
- Hits 14252 13460 -792
- Misses 45588 46301 +713
+ Partials 1008 984 -24 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
We don't need Go 1.23 for 0.45.1. |
I dont care about go much here, I want this fix to be released asap |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But otherwise OK. Even though I'm not excited about these changes (they better be for 0.46.0) we are using newer Go anyway already and we need to fix the problem. Workflows will fail though, so some adjustments are needed there.
Looks like we're not ready for this one. Let's roll out 0.45.1 with this known bug and upgrade Go and SDK properly then. |
Update GitHub workflows and Docker builders too. Refs #2918. Signed-off-by: Leonard Lyubich <leonard@morphbits.io>
It's available starting from Go 1.21 release. Signed-off-by: Leonard Lyubich <leonard@morphbits.io>
Signed-off-by: Leonard Lyubich <leonard@morphbits.io>
87bf323
to
23f68e0
Compare
2cd2f5e
to
5059b3c
Compare
5059b3c
to
b470836
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New iterators look good in many cases, simplifying flow, especially for early returns and things like that. But nspcc-dev/neofs-sdk-go#693 will certainly need to be fixed, current code around IterateNetworkEndpoints
is far from perfect.
@@ -70,7 +71,7 @@ func dumpNames(cmd *cobra.Command, _ []string) error { | |||
return len(iParts) < len(jParts) | |||
} | |||
for k := len(iParts) - 1; k >= 0; k-- { | |||
var c = strings.Compare(iParts[k], jParts[k]) | |||
var c = cmp.Compare(iParts[k], jParts[k]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With 1.23+ strings.Compare
is the same as cmp.Compare
performance-wise. This can be omitted, less packages to import.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dropped this commit
Only NeoFS SDK code which can be replaced trivially. Signed-off-by: Leonard Lyubich <leonard@morphbits.io>
The latest at the moment. No code changes involved. Also pulls Neo Go v0.108.1 upgrade and some others. Pre-release includes fix of `client/Client.ObjectRangeInit` method for zero range case. The bug first encountered while using `neofs-cli object range` cmd: ``` can't get object payload range: copy payload: payload range size overflow ``` This also prevents similar problems in inter-node communications while serving `ObjectService.Range` RPC. Upgrade of google.golang.org/grpc to v1.70.0 required moving to codec V2 usage. Similar to nspcc-dev/neofs-sdk-go@b7f8cd0. Signed-off-by: Leonard Lyubich <leonard@morphbits.io>
b470836
to
e875243
Compare
asserted the fix with the "big" object
to apply it, we need to upgrade SDK. It pulls Go 1.23 requirement. Current module hasn't bumped the min Go yet #2918. It's currently scheduled for v0.46.0. We can consider inclusion in v0.45.1. @roman-khimov @carpawell
other ways without updating the SDK seem practically impossible to me at the moment. This tie is generally inconvenient, although the node keeps up with the SDK