Skip to content
This repository has been archived by the owner on Feb 9, 2024. It is now read-only.

Bump go version to 1.17.5 #2694

Merged
merged 7 commits into from
Dec 16, 2021
Merged

Bump go version to 1.17.5 #2694

merged 7 commits into from
Dec 16, 2021

Conversation

bernardjkim
Copy link
Contributor

@bernardjkim bernardjkim commented Dec 13, 2021

Description

Bump go version to 1.17.5.

Go 1.14 adds -d=checkptr as a compile-time option for adding instrumentation to check that Go code is following unsafe.Pointer safety rules dynamically. This option is enabled by default (except on Windows) with the -race or -msan flags, and can be disabled with -gcflags=all=-d=checkptr=0.

This lead to failed test cases related to some older dependencies. Disabling the check for now.

Go 1.17 changed how filenames were parsed in multipart forms golang/go#45789. Filename no longer includes directory path in filename. dd03d1e adds a workaround to this change.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Internal change (not necessarily a bug fix or a new feature)

Linked tickets and other PRs

TODOs

  • Self-review the change
  • Perform manual testing
  • Address review feedback
  • Update upstream references / tags / versions after upstream PR merges (linked above)

Testing

  • Basic manual testing by installing a cluster and joining nodes.

@bernardjkim bernardjkim changed the title Bernard/master/bump go Bump go version to 1.17.5 Dec 13, 2021
@bernardjkim bernardjkim force-pushed the bernard/master/bump-go branch from 2399c0f to e06d266 Compare December 13, 2021 23:03
@bernardjkim bernardjkim force-pushed the bernard/master/bump-go branch from a35f51f to 303644e Compare December 16, 2021 00:01
@bernardjkim bernardjkim marked this pull request as ready for review December 16, 2021 00:13
@bernardjkim bernardjkim requested review from a team, wadells and knisbet December 16, 2021 00:13
Copy link
Contributor

@wadells wadells left a comment

Choose a reason for hiding this comment

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

Is it worth writing any tests for ParseFilename?

@bernardjkim
Copy link
Contributor Author

Is it worth writing any tests for ParseFilename?

Wouldn't hurt to add unit tests. Added a few test cases in 4e2afbb

@bernardjkim bernardjkim merged commit 751e2b6 into master Dec 16, 2021
@bernardjkim bernardjkim deleted the bernard/master/bump-go branch December 16, 2021 20:25
bernardjkim added a commit that referenced this pull request Dec 23, 2021
* Disable check for unsafe.Pointer safety rules

* Fix multipart form parsing
bernardjkim added a commit that referenced this pull request Dec 23, 2021
* Disable check for unsafe.Pointer safety rules

* Fix multipart form parsing
bernardjkim added a commit that referenced this pull request Dec 23, 2021
* Disable check for unsafe.Pointer safety rules

* Fix multipart form parsing
bernardjkim added a commit that referenced this pull request Jan 18, 2022
* Disable check for unsafe.Pointer safety rules

* Fix multipart form parsing
bernardjkim added a commit that referenced this pull request Jan 19, 2022
* Disable check for unsafe.Pointer safety rules

* Fix multipart form parsing
bernardjkim added a commit that referenced this pull request Jan 19, 2022
* Bump go version to 1.17.5 (#2694)

* Disable check for unsafe.Pointer safety rules

* Fix multipart form parsing

* GO111MODULE=off while installing generate

* Bump planet to 8.0.10
bernardjkim added a commit that referenced this pull request Jan 19, 2022
* Bump go version to 1.17.5 (#2694)

* Disable check for unsafe.Pointer safety rules

* Fix multipart form parsing

* GO111MODULE=off while installing generate

* GO111MODULE=off with go build

* Bump go version for testbox

* GO111MODULE=off with go test

* Bump planet to 7.0.62
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants