Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Do not trim large extra data?
See original GitHub issueVersion 0.8.0 introduced trimming of large data. Is it possible to optionally not to trim extra data which I specify with scope.set_extra(...)?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:11
- Comments:11 (3 by maintainers)
Top Results From Across the Web
Excel TRIM function - quick way to remove extra spaces
You use the TRIM function in Excel removes extra spaces from text. It deletes all leading, trailing and in-between spaces except for a...
Read more >How to Remove Spaces in Excel Data | Pryor Learning
Click in the first cell of the Trim column. On the Formulas tab, click the Text dropdown menu in the Functions group and...
Read more >What to do if a data set is too large for the Excel grid
What to do if a data set is too large for the Excel grid · Open the file in Excel for PC using...
Read more >How to Avoid Data Overage Charges: A Comprehensive Guide
Wondering the best way to avoid data overage charges? Our comprehensive guide can give you the answers you're looking for.
Read more >Cleaning Up Data with TRIM, PROPER, and Text to Columns
In this Excel tutorial, you'll learn how to clean up data using the TRIM, PROPER, and Text to Columns functions (and more )....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m monkey-patching this, but it would be great if the size of the extra data follows what is described in the Data Handling section of Sentry Docs (https://docs.sentry.io/development/sdk-dev/data-handling/).
Any plans on the fix? This really impacts the debugging experience