abe33 / abe33/atom-pigments

Issue with pigments

Aberta
#471 0 comentários 0 reações 0 responsáveis Ver no GitHub
Linguagem predominante
CoffeeScript
Estrelas
518
Forks
70
Métricas de merge de PRs
Nenhum PR com merge em 30d

Descrição

[Enter steps to reproduce:]

1. ...
2. ...

**Atom**: 1.57.0 x64
**Electron**: 9.4.4
**OS**: Unknown macOS version
**Thrown From**: [pigments](ssh://git@github.com/abe33/atom-pigments) package 0.40.6

### Stack Trace

Uncaught Error: write EPIPE

```
At events.js:200

Error: write EPIPE
at ChildProcess.target._send (internal/child_process.js:806:20)
at ChildProcess.target.send (internal/child_process.js:676:19)
at Task.send (/Applications/Atom.app/Contents/Resources/app/static/:14:43868)
at Task.start (/Applications/Atom.app/Contents/Resources/app/static/:14:43700)
at Function.Task.once (/Applications/Atom.app/Contents/Resources/app/static/:14:42819)
at /packages/pigments/lib/color-buffer.coffee:425:20
at new Promise ()
at ColorBuffer.module.exports.ColorBuffer.scanBufferForColors (/packages/pigments/lib/color-buffer.coffee:424:5)
at /packages/pigments/lib/color-buffer.coffee:160:8
```

### Commands

```
3x -0:52.7.0 core:backspace (input.hidden-input)
-0:51 core:undo (input.hidden-input)
24x -0:49.7.0 core:backspace (input.hidden-input)
```

### Non-Core Packages

```
atom-beautify 0.33.4
atom-html-preview 0.2.6
atom-ternjs 0.20.0
autoclose-html 0.23.0
csslint 1.2.0
emmet 2.4.3
hex-view 1.0.1
language-ejs 0.4.0
linter 3.1.1
linter-eslint 8.5.5
linter-ui-default 2.1.5
pigments 0.40.6
Sublime-Style-Column-Selection 1.7.5
```

Guia de contribuição

Abrir o guia de contribuição

Direção de pesquisa

The error occurs in color-buffer.coffee at line 425, where a ChildProcess write fails with EPIPE. Start by examining the Task.send and Task.start calls in Atom's embedded API, then look at how pigments spawns subprocesses for color scanning. Check if the process is being terminated prematurely or if there's a race condition. Running the package in development mode and reproducing the error will be necessary to understand the IPC lifecycle.

Escrita pelo modelo de indexação a partir do texto da issue.

Avaliação

Stack de tecnologia
javascript
Domínio
desktop, devtools
Tipo de issue
Bug
Dificuldade
4/5
Tempo estimado
3-5 dias
Status de atividade
Estagnada
Clareza
Precisa de esclarecimento
Facilidade para iniciantes
30/100

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.