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 has been archived by the owner on Jan 15, 2021. It is now read-only.
In some scenarios, the status code categories (e.g. 200s, 300s, etc.) could get confused with timing data as they have very similar styling in the HUD.
In the screenshot, it almost looks like there was one request that took 200 seconds (i.e. 200s) in addition to the one that took 352ms:
Maybe we should try to differentiate the summaries a bit more?
The text was updated successfully, but these errors were encountered:
In some scenarios, the status code categories (e.g.
200s
,300s
, etc.) could get confused with timing data as they have very similar styling in the HUD.In the screenshot, it almost looks like there was one request that took 200 seconds (i.e.
200s
) in addition to the one that took352ms
:Maybe we should try to differentiate the summaries a bit more?
The text was updated successfully, but these errors were encountered: