starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

0.16 panic: go 1.19 go4.org/unsafe/assume-no-moving-gc #305

New Issue
Closed
opened 2025-12-29 01:26:26 +01:00 by adam · 1 comment
adam commented 2025-12-29 01:26:26 +01:00
Owner
Copy Link

Originally created by @shanna on GitHub (Aug 10, 2022).

The 0.16 docker container panics with the following:

goroutine 1 [running]:
go4.org/unsafe/assume-no-moving-gc.init.0()
	go4.org/unsafe/assume-no-moving-gc@v0.0.0-20211027215541-db492cf91b37/untested.go:25 +0x1f4
panic: Something in this program imports go4.org/unsafe/assume-no-moving-gc to declare that it assumes a non-moving garbage collector, but your version of go4.org/unsafe/assume-no-moving-gc hasn't been updated to assert that it's safe against the go1.19 runtime. If you want to risk it, run with environment variable ASSUME_NO_MOVING_GC_UNSAFE_RISK_IT_WITH=go1.19 set. Notably, if go1.19 adds a moving garbage collector, this program is unsafe to use.

go mod why -m go4.org/unsafe/assume-no-moving-gc reports this is due to :

# go4.org/unsafe/assume-no-moving-gc
github.com/juanfont/headscale
inet.af/netaddr
go4.org/intern
go4.org/unsafe/assume-no-moving-gc

inet.af/netaddr might need a version bump?

Reproduce

To reproduce I think starting the 0.16 docker container with a valid configuration should be enough though you can probably just run the 0.16 binary.

Originally created by @shanna on GitHub (Aug 10, 2022). <!-- Headscale is a multinational community across the globe. Our common language is English. Please consider raising the bug report in this language. --> The 0.16 docker container panics with the following: ``` goroutine 1 [running]: go4.org/unsafe/assume-no-moving-gc.init.0() go4.org/unsafe/assume-no-moving-gc@v0.0.0-20211027215541-db492cf91b37/untested.go:25 +0x1f4 panic: Something in this program imports go4.org/unsafe/assume-no-moving-gc to declare that it assumes a non-moving garbage collector, but your version of go4.org/unsafe/assume-no-moving-gc hasn't been updated to assert that it's safe against the go1.19 runtime. If you want to risk it, run with environment variable ASSUME_NO_MOVING_GC_UNSAFE_RISK_IT_WITH=go1.19 set. Notably, if go1.19 adds a moving garbage collector, this program is unsafe to use. ``` `go mod why -m go4.org/unsafe/assume-no-moving-gc` reports this is due to : ``` # go4.org/unsafe/assume-no-moving-gc github.com/juanfont/headscale inet.af/netaddr go4.org/intern go4.org/unsafe/assume-no-moving-gc ``` `inet.af/netaddr` might need a version bump? <!-- A clear and concise description of what the bug is. Describe the expected bahavior and how it is currently different. If you are unsure if it is a bug, consider discussing it on our Discord server first. --> **Reproduce** To reproduce I think starting the 0.16 docker container with a valid configuration should be enough though you can probably just run the 0.16 binary.
adam added the bug label 2025-12-29 01:26:26 +01:00
adam closed this issue 2025-12-29 01:26:26 +01:00
adam commented 2025-12-29 01:26:27 +01:00
Author
Owner
Copy Link

@shanna commented on GitHub (Aug 10, 2022):

Sorry this is a bad report. We were using an image built against go 1.19.

@shanna commented on GitHub (Aug 10, 2022): Sorry this is a bad report. We were using an image built against go 1.19.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#305
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?