You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 23, 2018. It is now read-only.
This improves debugging in relation to my issue where the Performance API exceeded 150 entries and produced errors.
If there are 150 performance entries and the Network JS latency request is not one of them, the script will fail. This could be handled gracefully by providing the user a warning and/or by adding a flag to Network JS to flush performance entries prior to executing the latency test.
note: I realize 150 requests is way too many. If anyone wonders what the use case is, it's an angular app in the development environment, and without concatenation 400 requests is not uncommon.