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.
Update (9/15/2016 - 4:48 PM): I updated to the new glimpse-node umbrella package, and the NaN issue displayed below is fixed, but I still don't see the actual service call in the list.
Repro steps:
Add a call to http.get (or http.request, or any "higher-level" library which uses them under the covers) within one of your app's routes.
Run the app in order to exercise the code that generates the above GET request
Open up the Glimpse client and select the respective request
Select Web Services tab
Expected: To see the get request Actual: The get request isn't displayed, however, the heading bar displays "1 Requests".
If I open up the dev tools, I can see an error logged that may be the source of the issue, so this may not be specific to http.get, but rather, simply an issue with the web services UI in general.
The text was updated successfully, but these errors were encountered:
lostintangent
changed the title
[Web Services] http.get calls now showing up
[Web Services] http.get\request calls now showing up
Sep 15, 2016
I've tried to replicate but can't. I know there was an earlier issue with the above NaN but I think that was fixed in 0.12.0. Assigning to @nikmd23 to get verification on my investigation.
Update (9/15/2016 - 4:48 PM): I updated to the new
glimpse-node
umbrella package, and theNaN
issue displayed below is fixed, but I still don't see the actual service call in the list.Repro steps:
http.get
(orhttp.request
, or any "higher-level" library which uses them under the covers) within one of your app's routes.Web Services
tabExpected: To see the get request
Actual: The get request isn't displayed, however, the heading bar displays "1 Requests".
If I open up the dev tools, I can see an error logged that may be the source of the issue, so this may not be specific to
http.get
, but rather, simply an issue with the web services UI in general.The text was updated successfully, but these errors were encountered: