Limit test session record size
See original GitHub issueCurrently, we have some recordings as large as 25mb per file like AbortCopyFromUriAsync*
in storage they are also full of random data and are uncompressible growing the repo size considerably with every re-recording.
Considering we are making it very easy to mass re-record tests we might want to have an upper limit on recording size that would prevent us from checking in very large files.
cc @weshaggard @tg-msft @JoshLove-msft @kasobol-msft
Related: https://github.com/Azure/azure-sdk-for-net/issues/6903
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
javascript - How large is HTML5 session storage?
According to this site, Firefox's and Safari's storage limit is 5MB per domain, Internet Explorer's limit is 10 MB per domain.
Read more >How do you limit/control the records a test method can test ...
For example im trying to setup records to test with in my test method, ... ProfileAppropriateAlerts.size() ); // change three solutions, ...
Read more >localStorage size limit test
for (var i = 0; i < 10000; i++){. try {. localStorage.setItem(i, a);. } catch(e) {. console.log("Failed on setting item " + i);....
Read more >Maximum number of students in test session
When you search for students to add to a test session, the search results are limited to 200 students. However, you can perform...
Read more >Storage quotas and eviction criteria - Web APIs
Web Storage Browsers can store up to 5 MiB of local storage, and 5 MiB of session storage per origin. Once this limit...
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
This issue is good to close. I think https://github.com/Azure/azure-sdk-for-net/issues/6903 still makes sense to consider because I wouldn’t want a 100GB file of random noise checked into the other repo either.
@pallavit, no concerns from me.