panic: Sentry detected 18 stuck task(s):
	Task tid: 1449 (0x5a9), entered RunSys state 3m34.14s ago.
	Task tid: 4 (0x4), entered RunSys state 3m34.16s ago.
	Task tid: 2230 (0x8b6), entered RunSys state 3m34.16s ago.
	Task tid: 7 (0x7), entered RunSys state 3m34.15s ago.
	Task tid: 4582 (0x11e6), entered RunSys state 3m34.18s ago.
	Task tid: 5 (0x5), entered RunSys state 3m34.13s ago.
	Task tid: 12 (0xc), entered RunSys state 3m34.15s ago.
	Task tid: 13 (0xd), entered RunSys state 3m34.14s ago.
	Task tid: 1452 (0x5ac), entered RunSys state 3m34.15s ago.
	Task tid: 10 (0xa), entered RunSys state 3m34.15s ago.
	Task tid: 6 (0x6), entered RunSys state 3m34.16s ago.
	Task tid: 1451 (0x5ab), entered RunSys state 3m34.18s ago.
	Task tid: 11 (0xb), entered RunSys state 3m34.15s ago.
	Task tid: 9 (0x9), entered RunSys state 3m34.16s ago.
	Task tid: 3 (0x3), entered RunSys state 3m34.23s ago.
	Task tid: 4583 (0x11e7), entered RunSys state 3m34.13s ago.
	Task tid: 1446 (0x5a6), entered RunSys state 3m34.16s ago.
	Task tid: 2 (0x2), entered RunSys state 3m34.23s 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.