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 Jul 11, 2019. It is now read-only.
Sorry if this isn't the appropriate place to report, but I'm not totally clear on where development takes place for the various parts of Clockwork.
This has been tested in FF 61.0.2 as well as FF dev edition 62.0b16.
In the extension view, the profiler seems to be working fine (awesome, by the way - thanks for the update).
However in the web app view if I select a request with profiler data, click "performance" and then "profiler" it just hangs at the "Profile is not present for current request" screen. It doesn't even appear to be triggering the request for the "extended" API endpoint.
Sorry if this isn't the appropriate place to report, but I'm not totally clear on where development takes place for the various parts of Clockwork.
This has been tested in FF 61.0.2 as well as FF dev edition 62.0b16.
In the extension view, the profiler seems to be working fine (awesome, by the way - thanks for the update).
However in the web app view if I select a request with profiler data, click "performance" and then "profiler" it just hangs at the "Profile is not present for current request" screen. It doesn't even appear to be triggering the request for the "extended" API endpoint.