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
When we run the stacks command to extract information from recent stacks, it would be extremely useful to associate stack information with source links to go.googlesource.com or cs.opensource.google.
In order to do so, we'd need to:
For each stack program, check out the repo for that program at the correct version (for now, we can hard-code a list of program repos, but eventually we can also use origin information from the proxy (e.g., for gopls.
Use go/packages to load package information for the stack using the correct GOOS/GOARCH combination corresponding to the report.
Look up symbols in in the package, and translate line offsets in function bodies to absolute line positions.
Update the output of the stacks command to support html output, so that we can format nicely linkified stack information (perhaps an -html flag can generate an html summary which can be opened in the browser? I'm not sure here how best to serve the information.
For now, the stacks command is the most appropriate place to implement this logic, but one can imagine that it could also be useful as integration with e.g. gaby, or telemetry.go.dev.
The text was updated successfully, but these errors were encountered:
gopherbot
added
Tools
This label describes issues relating to any tools in the x/tools repository.
gopls
Issues related to the Go language server, gopls.
labels
Aug 6, 2024
When we run the
stacks
command to extract information from recent stacks, it would be extremely useful to associate stack information with source links to go.googlesource.com or cs.opensource.google.In order to do so, we'd need to:
For now, the stacks command is the most appropriate place to implement this logic, but one can imagine that it could also be useful as integration with e.g. gaby, or telemetry.go.dev.
CC @adonovan @h9jiang @golang/telemetry
The text was updated successfully, but these errors were encountered: