Skip to content
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.

[Web Services] http.get\request calls not showing up #26

Closed
lostintangent opened this issue Sep 15, 2016 · 4 comments
Closed

[Web Services] http.get\request calls not showing up #26

lostintangent opened this issue Sep 15, 2016 · 4 comments

Comments

@lostintangent
Copy link

lostintangent commented Sep 15, 2016

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:

  1. 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.
  2. Run the app in order to exercise the code that generates the above GET request
  3. Open up the Glimpse client and select the respective request
  4. Select Web Services tab

Expected: To see the get request
Actual: The get request isn't displayed, however, the heading bar displays "1 Requests".

norequests

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.

error

@lostintangent lostintangent changed the title [Web Services] http.get calls now showing up [Web Services] http.get\request calls now showing up Sep 15, 2016
@newtonjain newtonjain changed the title [Web Services] http.get\request calls now showing up [Web Services] http.get\request calls not showing up Sep 16, 2016
@nikmd23
Copy link
Member

nikmd23 commented Sep 21, 2016

It looks like there are several related issues here. We'll track down the problem and get them all resolved.

@nikmd23 nikmd23 added this to the Backlog milestone Sep 26, 2016
@avanderhoorn avanderhoorn self-assigned this Sep 26, 2016
@avanderhoorn avanderhoorn modified the milestones: M013, Backlog Sep 26, 2016
@avanderhoorn
Copy link
Member

React errors have been fixed here though I don't think its responsible for the described issue - https://github.com/Glimpse/Glimpse.Client/commit/f52012c305d79caeab6b6fc207296c68c3d5dee5. Still testing root cause of main issue.

@avanderhoorn
Copy link
Member

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.

@nikmd23
Copy link
Member

nikmd23 commented Oct 5, 2016

This appears to be fixed. When a build is available with this in it, I'll close this issue.

@nikmd23 nikmd23 closed this as completed May 10, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants