vercel / vercel/hyper

Syntax error in .hyper.js causes process running in terminal to be suspended

Open
#3,456 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
44.7k
Forks
3.6k
Avg merge
21m
Merged PRs (30d)
1

Description

  • I am on the latest Hyper.app version
  • I have searched the issues of this repo and believe that this is not a duplicate

-OS version and name: MacOS 10.13.6 High Sierra

  • Hyper.app version: 2.1.1
  • The issue is NOT reproducible in vanilla Hyper.app:

Issue

I have been doing a lot of work on my .hyper.js to try to set up the environment I want. From time to time I save the file with a syntax error and I get a popup saying A JavaScript error occurred in the main process with a stack trace. That's OK, there's an OK button and I can dismiss the popup and fix the error and continue.

But apparently it suspends any process that is running in any hyper window until the popup is dismissed. This is unexpected.

I have set up my environment so that my .hyper.js gets automatically synced to another machine, because I want the same environment on both machines. The other night I was working on .hyper.js on one machine, and with my typical butterfingers, I was generating a lot of syntax errors.

The next day I sat in front of my other machine, which had a server process running in a hyper terminal. There was a hyper error popup. I dismissed it and saw a bunch of errors like this:

{ ExpiredRequestError: clock skew of 43038.489s was greater than 300s

An unpleasant surprise.

Is there any way to turn off the feature of hyper that (sometimes) automatically updates when .hyper.js is changed?

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.

Research direction

Start with the reported behavior by causing a syntax error in .hyper.js while a process runs in a Hyper window, then observe whether dismissing the error popup resumes it. Trace how Hyper reacts when .hyper.js changes and how the main-process error is surfaced. Done means configuration errors no longer suspend running terminal processes, or the automatic update behavior can be disabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.