a

yeah this happens to me multiple times a day during regular usage (working on 2-3 code bases) it's sort of upsetting that a conversation history/state is stored here where my...

me too. they appeared for me on reboot when i guess i restarted my computer without closing every claude code session gracefully. i dont really care that much about losing...

> .. I'm pretty sure it's parallel claude code instances - but it might've been fixed, because I haven't run into it since tbh - might try to reproduce on...

thank you. i will try to figure out how to get some possible blobs that reproduce. in the mean time @eskirk what would be the easiest way using the web+react...

> [@elee1766](https://github.com/elee1766) a temporary workaround to avoid any stack trace parsing would be to remove the `ErrorsInstrumentation` from your Faro config. > > if you are using `getWebInstrumentations` in your...

Would it be "correct" to simply "skip/give up" running regex on lines that are longer than some "accepted" length?

@eskirk so we've been running basically a modified version of the stack trace parser to ignore stack traces over a certain size, which has reduced the occurrence of these problems...

> hi @elee1766 sorry this has flown under the radar for so long. > > can you share the changes to the stack trace parser that you are using? even...

ok so looking more, https://github.com/grafana/faro-web-sdk/commit/24e8359b1cd9ea78bfc5089a93b83935ab7ff1cc#diff-857838e0e3c266f9280baf037a3d02eef9e6c13c05644de864f83e012c6f17b0 this change made the error instrumentation also parse stack traces in this way, which resulted in my patch not working, and I think i need...

yeah that would probably resolve the problems. would you like me to try my hand at this ?