-
Notifications
You must be signed in to change notification settings - Fork 226
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(deps): Bump github.com/stretchr/testify to v1.10.0 #1114
Conversation
e01e70d
to
6c5ce18
Compare
@aalekseevx After that I'm seeing a few errors from the tests that I think are related to your changes. |
6c5ce18
to
dfbca93
Compare
@duglin, thank you for the quick reply! I'll investigate the issues |
Actually, it might be more dirs. Try: hack/go-mod-tidy.sh
|
fc9125b
to
649b5f0
Compare
@duglin Thank you for your help! Could you please review the new fixes and let me know if they work for you? |
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.
LGTM
ping @embano1 for the merge
} | ||
|
||
func TestCloneTime(t *testing.T) { | ||
original := time.Now() | ||
cloned := types.Clone(original).(types.Timestamp) | ||
|
||
require.Equal(t, original, cloned.Time) | ||
require.NotSame(t, original, cloned.Time) |
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 don't understand the original... how can it be equal and not equal?
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 believe it was intended to check whether the values are equal and their addresses differ.
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.
that really hurts my head :-)
Sure reads like a bug in "require" to me.
So, in this case did you remove it because "NotSame" fails or because it's redundant?
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.
Ah "same" vs "equal". I missed that!
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.
Yes! Removed because it seems redundant for me to check that &original
и &cloned.Time
are 2 different addresses
Signed-off-by: Aleksandr Alekseev <alekseev-dev@yandex-team.ru>
649b5f0
to
df16e77
Compare
Fantastic, 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.
LGTM
Updating testify introduces stricter rules for using
require.NotSame
. The implementation now enforces passing pointers, making certain checks that were previously always valid unnecessary. These redundant checks have been removed from the codebase.`