Test #18
Merged
Test #18
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…aul-tests Fix longhaul tests when running on fresh cluster
The existing workflows are out of date and insecure. This change updates the relevant workflows to the current state of the repository, corrects some issues, and disables workflows that will be handled through other means.
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.17.0 to 0.23.0. - [Commits](golang/net@v0.17.0...v0.23.0) --- updated-dependencies: - dependency-name: golang.org/x/net dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: dabradley <[email protected]>
…owners-development Add t-mialve to owners
…ley/trivy-on-development Run trivy on development branch as well
This helps prevent the workflows from getting out of sync with the version of go we are using in the project.
Version 4 of the setup-go action has caching enabled by default, but reads the existing go.mod and go.sum files in the checkout. If these do not exist, it issues a warning and avoids the cache behavior. To prevent this, this commit follows the suggested practice of performing the code checkout before running the setup-go action.
Upgrades and updates
Upgrade sidecars
…upgrade Bump client to 2.15.5
Any locking operation should have its unlock in a defer statement so that the lock is cleanly unlocked in the event of any issues that occur during the processing that occurs while the lock is held.
This helps make the method more readable since the concerns it works on remain near the same level of abstraction. Pushing these details into helper methods makes the logic of the publish method more clear, while giving a clear name to these operations.
These are unnecessary in golang, so keeping all conditionals in the expected format makes glancing through the logic easier by ensuring each check is consistent.
Instead of having different linters and configuration options in the various places we call golangci-lint, this changes how we run it so that it uses a shared configuration. This prevents the case where one of these checks would pass only to fail for the user when the workflows are run prior to merging.
When testing for the existence or lack of errors, it is beneficial to have the test fail at the first unexpected assertion. If we don't, then it is likely that any further processing will obscure the original failure, or even cause a panic in the test.
Improves failure reporting to have the function configured as a testing helper to make the actual failure more clear.
It's not necessary to change the actual process's actual environment to test these values. The t.Setenv functionality ensures that these values are reset at the end of the test so that other testing is not affected.
Shadowing existing language identifiers is unexpected and creates error-prone expectations of how a given identfier might be used.
Since Go 1.22, the scope of loop variables has changed. It is no longer necessary to copy loop vars to prevent accidental reuse.
The '%w' format automatically works with the unwrapping and wrapping of the existing error to provide more useful debugging information.
Accessing nested protobuf fields directly allows for nil pointer deferences. By forcing the use of getter methods, these chains will not cause these errors and will simply return a nil/zero value for the entire expression if one of the links does not exist.
Using named returns can create very brittle logic where zero values are automatically created and returned and can easily be missed by later maintainers. The existing usage did not leverage the actual named return logic and can be safely removed.
GCI ensures consistent and readable import ordering
For consistent logging and debugging, we should always be using the existing logging framework, rather than printing to standard out.
We are alroady running gofmt, so this just adds further formatting consistency.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Requirements:
Special notes for your reviewer:
Release note: