Skip to content

Apigee Local Tracer issues regarding ordering of requests and stability #1085

@sedghi

Description

@sedghi

I understand the local trace session is in beta. I have two pieces of feedback:

  1. The messages in an ongoing session don't seem to be ordered in any consistent way. It looks like they start with a timestamp, but after a few more requests, the order gets mixed up, and I can't tell which request is new. An indicator like "NEW" or just a consistent order would be really helpful. For instance in the image below it is my 1, 3, 2, 4 requests

Image

  1. For some reason, after hitting the tracer more than 5-6 times, further requests aren't traced or shown. It's a bummer that I have to stop the container and then restart everything.

Environment:
(Hint: "Report Extension Issue on Github" command will fill these out for you.)

Version information

Cloud Code Extension version: 2.31.1

VSCode version: Version: 1.100.2 (Universal)

OS: MacOS 15.5

Cloud SDK:

Skaffold:

Kubectl:

Description:

Repro step:

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions