-
Notifications
You must be signed in to change notification settings - Fork 913
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
Fix some minor warnings in the matching package #4608
Conversation
service/matching/db.go
Outdated
func (db *taskQueueDB) GetUserData( | ||
ctx context.Context, | ||
) (*persistencespb.VersionedTaskQueueUserData, chan struct{}, error) { | ||
func (db *taskQueueDB) GetUserData(context.Context) (*persistencespb.VersionedTaskQueueUserData, chan struct{}, error) { |
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.
nit: I thought the original version is better and makes the line shorter?
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.
Reverted except removing the param name
service/matching/task_reader.go
Outdated
type tasksBatch struct { | ||
Tasks []*persistencespb.AllocatedTaskInfo | ||
ReadLevel int64 | ||
IsReadBatchDone bool | ||
} |
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.
nit: getTasksBatchResponse maybe? read level and the done flag look like metadata to the returned batch of tasks.
do those fields have to be exported?
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.
Renamed and made them unexported
What changed?
I went through all the GoLand IDE inspection errors in the matching package, and I fixed the ones that seemed relevant. Most of them are little typos.
Why?
To clean things up a bit, make it easier to find actual errors from inspection, make sure these don't have to get included in other actual behavioral changes.
How did you test it?
I made sure not to include any behavioral changes, even small things like replacing
err ==
witherrors.Is
.Potential risks
Is hotfix candidate?