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

Ready for universal CI #187

Merged
merged 4 commits into from
Aug 5, 2021
Merged

Ready for universal CI #187

merged 4 commits into from
Aug 5, 2021

Conversation

hannahhoward
Copy link
Collaborator

@hannahhoward hannahhoward commented Aug 5, 2021

Goals

Fix all go vet / staticcheck errors

Implementation

  • updated go-ipld-prime to latest get code gen that does not have go vet errors
  • mean we had to change one test due to a traversal order effect from now properly sorting map fields for DAG-JSON / DAG-CBOR
  • re-codegen sections to resolve go vet Unkeyed fields errors
  • resolve all static check issues
  • remove one unneeded wrapper method

For discussion

go-graphsync has some unreliable tests on Circle-CI, and I'm sure those will be accentuated when we switch over to Universal CI, as they were with go-bitswap. So we'll need to do seperate work there.

Copy link
Contributor

@mvdan mvdan left a comment

Choose a reason for hiding this comment

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

LGTM, except the nolint bit, which should be unnecessary and unrelated. If it isn't, please provide details, because I'm not sure I follow :)

p peer.ID
amount uint64
p peer.ID //nolint:structcheck
amount uint64 //nolint:structcheck
Copy link
Contributor

Choose a reason for hiding this comment

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

what warning is this preventing? as far as I know our unified CI only enforces vet and staticcheck, so structcheck should not be a part of any of this.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

it gets the CURRENT CI to pass :P

Copy link
Contributor

Choose a reason for hiding this comment

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

🤦 need to rush to remove golangci-lint, then :P

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I'll remove the nolint comment in the PR where we switch over.

@hannahhoward hannahhoward merged commit aa3b445 into master Aug 5, 2021
@Stebalien Stebalien deleted the feat/ready-for-ci branch August 5, 2021 15:45
@aschmahmann aschmahmann mentioned this pull request Dec 1, 2021
80 tasks
marten-seemann pushed a commit that referenced this pull request Mar 2, 2023
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.

2 participants