[Discussion] Slice uploaded data by default to visible threads/time
See original GitHub issueAka: WYSIWY-Upload
.
Match users expectations by only uploading what you see.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
[meta] Profile PII Data Sanitization · Issue #1802 - GitHub
[Profiler] Profile upload dialog with customizable PII removal ... [Discussion] Slice uploaded data by default to visible threads/time #1264.
Read more >Beginners Guide to Threading in .NET: Part 1 of n - CodeProject
When a threads time slice has expired, it doesn't just stop and wait its turn. ... The thread can allocate a data slot...
Read more >Time to Reevaluate the "Mirror your Slog (ZIL Drive ... - TrueNAS
If a SLOG is present, the system ZIL is placed on it. During async writes, ZFS will accept data for a write to...
Read more >Time.deltaTime Not Constant: VSync CameraFollow and Jitter
Physics in Unity run async to rendering by default, ... this can cause a lot of visible jitter if the devs don't enable...
Read more >TIME LAPSE - OnePlus Community
Title: TIME LAPSE; Device: OnePlus6T; Software Version: O2 Stable 190801; Topic: Suggestion; Photos: Feature Needed Background Description: Its better to ...
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 FreeTop 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
Top GitHub Comments
It depends how far we want to take it. Filtering out hidden threads is easy. Filtering visible threads to the visible range is a bit more tricky, depending on how fare we want to take it. We can just filter out the out-of-range samples, or we can blank out strings from the string table that are not needed for any funcs for frames for stacks in the in-range samples, or we can start culling things from the func / frame / stack table. But if we do that, the transforms in the URL will be wrong. So I would suggest keeping the shapes of our tables and just blanking out strings in the string table.
This is resolved with the MVP of the PII work in #1802, and follow-ups are filed under the privacy label.