What version of the IDE extension are you using?
2.1.119
What subscription do you have?
Pro
Which IDE are you using?
VS Code
What platform is your computer?
Linux 6.8.0-107-generic x86_64 x86_64
What issue are you seeing?
The Codex VS Code extension becomes laggy when typing prompts, while the Codex log rapidly fills with repeated warnings and telemetry errors.
The main warning is:
[warning] [IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed
In my current log, this warning reached 7974 entries.
I also see repeated telemetry/analytics 403 errors:
text
[error] Error fetching httpStatus=403 statusText=Forbidden url=https://chatgpt.com/ces/v1/rgstr?
I am not sure whether the 403 /ces/v1/rgstr telemetry errors directly cause the Received broadcast but no handler is configured warnings. They may be separate bugs. However, they happen during the same laggy period, while the Codex extension/app-server has high CPU and the log grows quickly.
What steps can reproduce the bug?
Type prompts into the Codex prompt box.
What is the expected behavior?
- Internal broadcast messages should have a handler, or should be ignored quietly if no handler is needed.
- The extension should not log thousands of repeated
Received broadcast but no handler is configured warnings.
- Telemetry
403 Forbidden failures should not be repeatedly logged as user-visible errors.
- Failed telemetry requests should back off or be disabled for the session.
- These background warnings/errors should not cause high CPU usage or prompt input lag.
Additional information
The prompt input may also be stalling because the extension keeps doing background work after failed requests.
I am not sure if the lag is caused directly by the repeated 403 /ces/v1/rgstr telemetry failures, but while the lag happens, the log keeps growing with telemetry 403 errors and many broadcast warnings:
Also getting this warning:
[warning] [IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed
What version of the IDE extension are you using?
2.1.119
What subscription do you have?
Pro
Which IDE are you using?
VS Code
What platform is your computer?
Linux 6.8.0-107-generic x86_64 x86_64
What issue are you seeing?
The Codex VS Code extension becomes laggy when typing prompts, while the Codex log rapidly fills with repeated warnings and telemetry errors.
The main warning is:
[warning] [IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed
In my current log, this warning reached 7974 entries.
I also see repeated telemetry/analytics 403 errors:
text
[error] Error fetching httpStatus=403 statusText=Forbidden url=https://chatgpt.com/ces/v1/rgstr?
I am not sure whether the 403 /ces/v1/rgstr telemetry errors directly cause the Received broadcast but no handler is configured warnings. They may be separate bugs. However, they happen during the same laggy period, while the Codex extension/app-server has high CPU and the log grows quickly.
What steps can reproduce the bug?
Type prompts into the Codex prompt box.
What is the expected behavior?
Received broadcast but no handler is configuredwarnings.403 Forbiddenfailures should not be repeatedly logged as user-visible errors.Additional information
The prompt input may also be stalling because the extension keeps doing background work after failed requests.
I am not sure if the lag is caused directly by the repeated
403 /ces/v1/rgstrtelemetry failures, but while the lag happens, the log keeps growing with telemetry 403 errors and many broadcast warnings:Also getting this warning:
[warning] [IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed