Gusted 3f44b97b5f feat: add limited execution tracing support ... - For every process that is spawned (every new non-trivial goroutine such as http requests, queues or tasks) start a [execution tracer](https://pkg.go.dev/runtime/trace). This allows very precise diagnosis of how each individual process over a time period. - It's safe and [fast](https://go.dev/blog/execution-traces-2024#low-overhead-tracing) to be run in production, hence no setting to disable this. There's only noticable overhead when tracing is actually performed and not continuous. - Proper tracing support would mean the codebase would be full of `trace.WithRegion` and `trace.Log`, which feels premature for this patch as there's no real-world usage yet to indicate which places would need this the most. So far only Git commands and SQL queries receive somewhat proper tracing support given that these are used throughout the codebase. - Make git commands a new process type. - Add tracing to diagnosis zip file.		2025-01-05 04:07:49 +01:00
..
actions
activities
admin
asymkey
auth
avatars
db	feat: add limited execution tracing support	2025-01-05 04:07:49 +01:00
dbfs
fixtures
forgefed
forgejo/semver
forgejo_migrations
git
issues
migrations
organization
packages
perm
project
pull
quota
repo
secret
shared/types
system
unit
unittest
user
webhook
error.go
main_test.go
org.go
org_team.go
org_team_test.go
org_test.go
repo.go
repo_test.go
repo_transfer.go
repo_transfer_test.go