Max Bittker

hi @hogggy thanks for opening the issue. what version of raven are you on? investigating this now

the problem is that too much data is being attached to an event - are you using any of the Raven context methods or adding custom breadcrumbs? something very large...

are you using minified code? a few things to try: upgrading to 2.1.0 to take advantage of https://github.com/getsentry/raven-node/pull/329 editing your node_modules a putting a `console.log(kwargs)` before ``` File "/app/node_modules/raven/lib/client.js", line...

hmmm.. us failing gracefully here and adding more debug output is all I can think of for the time-being, is there anything either of you could do to help us...

I think this makes sense, but not going to be a high priority issue right away. Thanks @BigPrimeNumbers

Sorry if it's obnoxious to follow up so quickly, but I don't think the live demo build has been updated to reflect this fix (I still get this error). retrace...

linux, chrome, 2560 x 1440  the problem is the same in the scene links i tried from the readme, and persisted since I restarted my browser I haven't tried...

:( I know it sounds silly, but I'm attached to this theme and it's one of the things keeping me on atom now.

https://github.com/be5invis/vscode-custom-css i wonder if we could hack something with this? I might look into it when i have time.

this getting this issue