-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
requests are not appearing in chronological order #133
Comments
Hello, Could you give me more context? In NB: This order may differ than a sort based on the value of the HTTP response header |
I'm doing sequential calls, so time of first byte should work. I suppose it's not an ordering issue, but a grouping issue. I see most requests grouped under the "console" heading. But others are split into their own "res = session.post" sections. So not all requests are under one section.... can that be done? I see if I hide initiator rows, the grouping sections go away, but it's still out of order in that case. Hopefully that makes sense. |
It looks like this is indeed a grouping issue. I haven't been able to reproduce this issue but I tried to made a fix based on your description. Could you try with Also, could you tell me what HTTP client you are using? |
Nice, thanks for that. I can't repro the issue anymore, no requests show up under "console" anymore, so if I hide the initiator rows, I get a good sequential view. I'm not sure which request showed up under console and which didn't, it was kinda random before... behind the scenes it's an app that utilizes the latest langchain framework, so it's making the http calls. I can tell you that looking at the 200 POST requests, some of them have stack info and in others it's blank... so perhaps that's related. |
In v 0.18.0 the request are not in order (can be seen by looking at Date in response headers).
Is it possible to fix, or allow to sort? Thanks!!
The text was updated successfully, but these errors were encountered: