Common stack frames between all traces are common occurrence even in our testing code—this is noisy. The problem is even worse when users of FloatTracker are utilizing a library (e.g. Rocket.jl from the example) which can explode stack traces and make the files waaaaay bigger than necessary.
Including a parameter of a certain number of stack frames would be useful too.
From feedback on RxInfer.jl#116.
Common stack frames between all traces are common occurrence even in our testing code—this is noisy. The problem is even worse when users of FloatTracker are utilizing a library (e.g.
Rocket.jlfrom the example) which can explode stack traces and make the files waaaaay bigger than necessary.Including a parameter of a certain number of stack frames would be useful too.