REditorSupport / REditorSupport/vscode-R

Suddenly httpgd plots stopped working

Open
#1,447 10 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
1.2k
Forks
139
Avg merge
2h 46m
Merged PRs (30d)
5

Description

This is not the first time I have the issue. Sometimes httpgd just stops working and no plot panel is shown after a plot command. Even if I restart VSCode the error persists. I don't know how to fix it. It may be related to my previous report (https://github.com/REditorSupport/vscode-R/issues/1445) to solve which I had to recreate my workspace from scratch.

The output pane I see errors like these:

2023-11-13 10:22:41.418 [error] FetchError: request to http://127.0.0.1:50505/plot?id=0&renderer=svgp&width=800&height=600&zoom=1 failed, reason: socket hang up
	at ClientRequest.<anonymous> (/Users/carlos/.vscode/extensions/reditorsupport.r-2.8.2/dist/extension.js:2:1878046)
	at ClientRequest.emit (node:events:513:28)
	at Socket.socketOnEnd (node:_http_client:526:9)
	at Socket.emit (node:events:525:35)
	at endReadableNT (node:internal/streams/readable:1359:12)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2023-11-13 10:22:41.546 [error] Error: ENOENT: no such file or directory, open '/var/folders/sz/t88v7mcx541gn9wn9cjsv1600000gn/T/RtmpAVrQQg/vscode-R/workspace.lock'
2023-11-13 10:22:41.810 [error] FetchError: request to http://127.0.0.1:50518/plot?id=0&renderer=svgp&width=800&height=600&zoom=1 failed, reason: socket hang up
	at ClientRequest.<anonymous> (/Users/carlos/.vscode/extensions/reditorsupport.r-2.8.2/dist/extension.js:2:1878046)
	at ClientRequest.emit (node:events:513:28)

To Reproduce

This is just too random to give you a recipe. Hope the trace above helps.

Can you fix this issue by yourself? (We appreciate the help)

No.

Contributor guide

Open the contributing guide

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.

Research direction

Start by comparing the socket hang-up and workspace.lock ENOENT errors in the reported extension output with the related issue #1445. Investigate the httpgd plot-panel path and gather a reproducible sequence, since the report says the failure is random. Done means plot commands reliably show the plot panel without either error.

Written by the indexing model from the issue text.

Assessment

Tech stack
r, typescript, vscode
Domain
data-visualization, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.