You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version of orchestrion
Tried: 1.0.2, 1.0.3 and 1.0.4
Describe what happened:
Application was built using orchestrion in Docker: orchestrion go build -mod=readonly -ldflags='-s -w' -o /app/bin/main ./cmd/${APP_NAME}
We receive the following error message at runtime:
This is a side-effect of using github.com/DataDog/dd-trace-go/v2 together with orchestrion, which injects using gopkg.in/DataDog/dd-trace-go.v1... and there is currently a conflict with access to the goroutine local storage (which is enabled by orchestrion).
Current GLS accessors for V1 and V2 conflict because they use the same
slot to store different value types. Renaming those accessors means
orchestrion will stop populating the accessors for V2, which will
address the crasher reported at DataDog/orchestrion#520
Current GLS accessors for V1 and V2 conflict because they use the same slot to store different value types. Renaming those accessors means orchestrion will stop populating the accessors for V2, which will address the crasher reported at DataDog/orchestrion#520
Version of orchestrion
Tried: 1.0.2, 1.0.3 and 1.0.4
Describe what happened:
Application was built using orchestrion in Docker:
orchestrion go build -mod=readonly -ldflags='-s -w' -o /app/bin/main ./cmd/${APP_NAME}
We receive the following error message at runtime:
![Image](https://private-user-images.githubusercontent.com/1439383/408079912-fb517595-0c73-4042-a524-52266e0e42f7.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxNjQxNjQsIm5iZiI6MTczOTE2Mzg2NCwicGF0aCI6Ii8xNDM5MzgzLzQwODA3OTkxMi1mYjUxNzU5NS0wYzczLTQwNDItYTUyNC01MjI2NmUwZTQyZjcucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxMCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTBUMDUwNDI0WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9OTg2NDNmODJjNjQwY2ZmZTRlMDUyNmQxMDY1NmU1NTU2NWZjN2VhYzk0ZjExMTFiMDliNjNmODhmYTMxYjBhYiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.vY2NeIbNE1QaUCDraqLmGQmPa7LcTsBZIqJWCvXxwzU)
Downgrading to dd-trace-go v.1 fixes the issue.
Describe what you expected:
No error message :) Or at least an error message during build time
Steps to reproduce the issue:
I assume.. build and run dd-trace-go v2 with orchestrion and fiber
Additional environment details (Version of Go, Operating System, etc.):
Go 1.23
github.com/gofiber/fiber/v2 v2.52.6
github.com/DataDog/dd-trace-go/v2 v2.0.0-rc.2
github.com/DataDog/dd-trace-go/contrib/gofiber/fiber.v2/v2 v2.0.0-rc.2
github.com/DataDog/orchestrion v1.0.2
The text was updated successfully, but these errors were encountered: