The injected client.js will try to reconnect to the sse endpoint as soon as the port is bound

Open
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
backend

Research direction

Reproduce the sequence with webdev_proxy serve, a Chrome tab on the served port, termination, and restart. Start by inspecting the injected client.js and the SSE endpoint handling; done means the initial reconnect during startup no longer produces a server-log error while the connection succeeds once webdev serve is ready.

Written by the indexing model from the issue text.

Description

  1. Run webdev_proxy serve
  2. Open the served port in a chrome browser tab
  3. Terminate the webdev_proxy serve instance
  4. Restart webdev_proxy serve and note that the browser tab immediately tries to reestablish its SSE connection which produces an error in the server logs because the underlying webdev serve process has not yet started

We likely just need to detect this scenario during startup and silence the error on first request to that endpoint (it ends up succeeding as soon as webdev serve has started up).

Dominant language
JavaScript
Stars
11
Forks
7
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Workiva/webdev_proxy

All issues in Workiva/webdev_proxy

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.