-
Notifications
You must be signed in to change notification settings - Fork 252
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
chore!: upgrade to celestia-core v1.8.0-tm-v0.34.20
#1023
Conversation
v1.6.0-tm-v0.34.20
d709d9a
to
15475e4
Compare
v1.6.0-tm-v0.34.20
v1.8.0-tm-v0.34.20
Codecov Report
@@ Coverage Diff @@
## main #1023 +/- ##
===========================================
+ Coverage 27.15% 51.16% +24.00%
===========================================
Files 81 71 -10
Lines 9021 4372 -4649
===========================================
- Hits 2450 2237 -213
+ Misses 6335 1911 -4424
+ Partials 236 224 -12
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
v1.8.0-tm-v0.34.20
v1.8.0-tm-v0.34.20
@@ -165,7 +165,7 @@ func TestMessageInclusionCheck(t *testing.T) { | |||
// require.NoError(t, err) | |||
|
|||
// require.NoError(t, err) | |||
// eds, err := da.ExtendShares(input.BlockData.OriginalSquareSize, shares) | |||
// eds, err := da.ExtendShares(input.BlockData.SquareSize, shares) |
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.
I think we should be deleting these tests rather than leaving them commented out. Created #1026
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.
left one possible change, but we will likely change it soon anyway, so pls feel free to ignore if it takes too long
firstNS := []byte{2, 2, 2, 2, 2, 2, 2, 2} | ||
firstNamespace := []byte{2, 2, 2, 2, 2, 2, 2, 2} |
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.
[non-blocking][for future reference]
is this change related at all? its already completed, so pls keep, but if its 100% not related, in the future I would appreciate it if we try to not arbitrarily change variable names and put them into unrelated PRs. I don't mind this specific change, and I don't wan't to discourage renaming things, and I've been guilty of this too, but if any of us did it would be silly to block on an otherwise perfect PR.
thx 🙂
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.
Agreed completely. This change isn't necessary in this PR. While working on this PR, I noticed that we use two names to refer to the same thing ns
and namespace
. I started correcting in this PR which was a mistake, should've been a new issue and PR.
Closes celestiaorg#1022 Does not rename all instances of `message` to `blob` see celestiaorg#995
Closes #1022
Does not rename all instances of
message
toblob
see #995