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

affected/package: sys #55078

Closed
ddelbosque-bread opened this issue Sep 14, 2022 · 11 comments
Closed

affected/package: sys #55078

ddelbosque-bread opened this issue Sep 14, 2022 · 11 comments

Comments

@ddelbosque-bread
Copy link

ddelbosque-bread commented Sep 14, 2022

What version of Go are you using (go version)?

$ go version
1.13

Does this issue reproduce with the latest release?

No

What operating system and processor architecture are you using (go env)?

go env Output
$ go env
GO111MODULE="auto"
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/dominickdelbosque/Library/Caches/go-build"
GOENV="/Users/dominickdelbosque/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"

What did you do?

Nothing. Issue appeared as of 9/9/22 due to

ba1ef54

Which switches to using unsafe.Slice

What did you expect to see?

Nothing since this change should've just affected latest versions i.e. 1.17 and 1.18

What did you see instead?

1.13 fails build due to

golang.org/x/sys/unix
  | src/golang.org/x/sys/unix/syscall.go:83:16: undefined: unsafe.Slice
  | src/golang.org/x/sys/unix/syscall_unix.go:118:7: undefined: unsafe.Slice
  | src/golang.org/x/sys/unix/sysvshm_unix.go:33:7: undefined: unsafe.Slice
 

@seankhliao
Copy link
Member

We don't support 1.13 anymore.

@seankhliao seankhliao closed this as not planned Won't fix, can't repro, duplicate, stale Sep 14, 2022
@ddelbosque-bread
Copy link
Author

ddelbosque-bread commented Sep 14, 2022

Fair enough - However I do see the same error on 1.15 - 1.16

@seankhliao
Copy link
Member

We only support the 2 most recent releases, right now 1.18 and 1.19

@michael-sharethis
Copy link

michael-sharethis commented Sep 16, 2022

i'm experiencing the same issue. it looks like the go devs introduced a bug affecting older versions? does anyone have any workarounds for this? I'm a new Go developer - I've inherited a project that runs on 1.15 using GOPATH (I think rather than go.mod) and am looking to get it to build so I can release some new code.

@ddelbosque-bread
Copy link
Author

@michael-sharethis I agree, this is a breaking change for older versions.

@ianlancetaylor
Copy link
Contributor

The workaround is to use an older version of golang.org/x/sys.

@michael-sharethis
Copy link

michael-sharethis commented Sep 16, 2022

@ianlancetaylor i've tried that but I get errors like this when trying to specify an older version, this project is in GOPATH mode

Step 15/32 : RUN go get golang.org/x/sys@0.0.0-20220909162455-aba9fc2a8ff2
---> Running in 20e2beb39bae
[91mgo: cannot use path@version syntax in GOPATH mode
[0mThe command '/bin/sh -c go get golang.org/x/sys/unix@0.0.0-20220909162455-aba9fc2a8ff2' returned a non-zero code: 1

i didn't see golang.org/x/sys having any version listed in it's gittags...

@Expaso
Copy link

Expaso commented Sep 17, 2022

Yep!, me affected too:

Anoyone knows a fix?

@dmgk
Copy link
Member

dmgk commented Sep 17, 2022

Something like this might work:

go get -d golang.org/x/sys/... && git -C $(go env GOPATH)/src/golang.org/x/sys reset --hard aba9fc2a8ff2

@kartik7153
Copy link

How do we fix the for dependency which is indirect?

@seankhliao
Copy link
Member

Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.

For questions please refer to https://github.com/golang/go/wiki/Questions

@golang golang locked as off-topic and limited conversation to collaborators Sep 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants