panic: Sentry detected 17 stuck task(s):
	Task tid: 8173 (0x1fed), entered RunSys state 3m32.29s ago.
	Task tid: 5 (0x5), entered RunSys state 3m27.66s ago.
	Task tid: 58 (0x3a), entered RunSys state 3m32.28s ago.
	Task tid: 2 (0x2), entered RunSys state 3m27.66s ago.
	Task tid: 8175 (0x1fef), entered RunSys state 3m32.27s ago.
	Task tid: 8179 (0x1ff3), entered RunSys state 3m32.29s ago.
	Task tid: 6 (0x6), entered RunSys state 3m27.65s ago.
	Task tid: 13 (0xd), entered RunSys state 3m27.65s ago.
	Task tid: 12 (0xc), entered RunSys state 3m27.66s ago.
	Task tid: 4 (0x4), entered RunSys state 3m27.66s ago.
	Task tid: 11 (0xb), entered RunSys state 3m27.66s ago.
	Task tid: 10 (0xa), entered RunSys state 3m27.66s ago.
	Task tid: 14 (0xe), entered RunSys state 3m27.66s ago.
	Task tid: 8176 (0x1ff0), entered RunSys state 3m31.5s ago.
	Task tid: 8 (0x8), entered RunSys state 3m27.66s ago.
	Task tid: 7 (0x7), entered RunSys state 3m27.66s ago.
	Task tid: 3 (0x3), entered RunSys state 3m27.66s ago.
Search for '(*Task).run(0x..., 0x<tid>)' in the stack dump to find the offending goroutine
Stack for running G's are skipped while panicking.