node-red-node-serialport node makes the Docker container infinite boot cycle

Abierto

#1,027 abierto el 30/8/2023 22 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad: 4/5
Tiempo estimado: 3-5 días
Aptitud para principiantes: 35/100

Tipo de issue: Error
Claridad: Necesita aclaración
Estado de actividad: Tranquilo
Stack tecnológico: docker, javascript
Área: backend, devops

Línea de trabajo

Comienza reproduciendo npm install para node-red-node-serialport 1.0.4 dentro del contenedor Docker con las versiones de Node.js y npm indicadas, y después inspecciona toda la salida de instalación y arranque. Se considera completado cuando el paquete se instala sin provocar un ciclo infinito de arranque del contenedor; el payload no indica archivos fuente ni pruebas a los que dirigirse.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

OK to Close ? upstream

          I'm having the same problem with 1.0.4.

Install log:

901e3f2035fd:/usr/src/node-red# npm i node-red-node-serialport --loglevel verbose
npm info it worked if it ends with ok
npm verb cli [
npm verb cli   '/usr/local/bin/node',
npm verb cli   '/usr/local/bin/npm',
npm verb cli   'i',
npm verb cli   'node-red-node-serialport',
npm verb cli   '--loglevel',
npm verb cli   'verbose'
npm verb cli ]
npm info using [email protected]
npm info using [email protected]
npm verb npm-session 1a2b8f09188d40b6
npm http fetch GET 200 https://registry.npmjs.org/node-red-node-serialport 125ms (from cache)
npm timing stage:loadCurrentTree Completed in 2109ms
npm timing stage:loadIdealTree:cloneCurrentTree Completed in 10ms
npm timing stage:loadIdealTree:loadShrinkwrap Completed in 1191ms
npm http fetch GET 200 https://registry.npmjs.org/serialport 17ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/@serialport%2fparser-cctalk 69ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/@serialport%2fbindings-cpp 76ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/@serialport%2fparser-byte-length 79ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/@serialport%2fparser-inter-byte-timeout 77ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/@serialport%2fparser-delimiter 86ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/@serialport%2fparser-packet-length 89ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/@serialport%2fbinding-mock 103ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/@serialport%2fparser-readline 95ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/@serialport%2fparser-ready 109ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/@serialport%2fparser-regex 110ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/@serialport%2fparser-slip-encoder 24ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/@serialport%2fparser-spacepacket 28ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/@serialport%2fstream 29ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/@serialport%2fbindings-interface 6ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/node-addon-api 24ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/node-gyp-build 29ms (from cache)
npm timing stage:loadIdealTree:loadAllDepsIntoIdealTree Completed in 1732ms
npm timing stage:loadIdealTree Completed in 3287ms
npm timing stage:generateActionsToTake Completed in 130ms
npm verb correctMkdir /data/.npm/_locks correctMkdir not in flight; initializing
npm verb lock using /data/.npm/_locks/staging-4c3c7748ae1d116d.lock for /usr/src/node-red/node_modules/.staging
npm timing action:extract Completed in 551ms
npm timing action:finalize Completed in 92ms
npm timing action:refresh-package-json Completed in 200ms
npm info lifecycle @serialport/[email protected]~preinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~preinstall: @serialport/[email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle @serialport/[email protected]~preinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~preinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~preinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~preinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~preinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~preinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~preinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~preinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~preinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~preinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~preinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~preinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~preinstall: @serialport/[email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle @serialport/[email protected]~preinstall: @serialport/[email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm timing action:preinstall Completed in 33ms
npm info linkStuff @serialport/[email protected]
npm info linkStuff @serialport/[email protected]
npm info linkStuff [email protected]
npm info linkStuff @serialport/[email protected]
npm info linkStuff @serialport/[email protected]
npm info linkStuff @serialport/[email protected]
npm info linkStuff @serialport/[email protected]
npm info linkStuff @serialport/[email protected]
npm info linkStuff @serialport/[email protected]
npm info linkStuff @serialport/[email protected]
npm info linkStuff @serialport/[email protected]
npm info linkStuff @serialport/[email protected]
npm info linkStuff @serialport/[email protected]
npm info linkStuff @serialport/[email protected]
npm info linkStuff @serialport/[email protected]
npm info linkStuff @serialport/[email protected]
npm info linkStuff [email protected]
npm verb linkBins [
npm verb linkBins   {
npm verb linkBins     'node-gyp-build': 'bin.js',
npm verb linkBins     'node-gyp-build-optional': 'optional.js',
npm verb linkBins     'node-gyp-build-test': 'build-test.js'
npm verb linkBins   },
npm verb linkBins   '/usr/src/node-red/node_modules/.bin',
npm verb linkBins   false
npm verb linkBins ]
npm timing audit submit Completed in 1097ms
npm http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/audits/quick 1098ms
npm timing audit body Completed in 5ms
npm info linkStuff @serialport/[email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm timing action:build Completed in 96ms
npm info lifecycle @serialport/[email protected]~install: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~install: @serialport/[email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle @serialport/[email protected]~install: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~install: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~install: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~install: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~install: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~install: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~install: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~install: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~install: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~install: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~install: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~install: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~install: @serialport/[email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle @serialport/[email protected]~install: @serialport/[email protected]

> @serialport/[email protected] install /usr/src/node-red/node_modules/@serialport/bindings-cpp
> node-gyp-build

npm verb lifecycle @serialport/[email protected]~install: unsafe-perm in lifecycle false
npm verb lifecycle @serialport/[email protected]~install: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/src/node-red/node_modules/@serialport/bindings-cpp/node_modules/.bin:/usr/src/node-red/node_modules/.bin:/usr/src/node-red/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
npm verb lifecycle @serialport/[email protected]~install: CWD: /usr/src/node-red/node_modules/@serialport/bindings-cpp
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm timing action:install Completed in 507ms
npm info lifecycle @serialport/[email protected]~postinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~postinstall: @serialport/[email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle @serialport/[email protected]~postinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~postinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~postinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~postinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~postinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~postinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~postinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~postinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~postinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~postinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~postinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~postinstall: @serialport/[email protected]
npm info lifecycle @serialport/[email protected]~postinstall: @serialport/[email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle @serialport/[email protected]~postinstall: @serialport/[email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm timing action:postinstall Completed in 43ms
npm verb unlock done using /data/.npm/_locks/staging-4c3c7748ae1d116d.lock for /usr/src/node-red/node_modules/.staging
npm timing stage:executeActions Completed in 1705ms
npm timing stage:rollbackFailedOptional Completed in 2ms
npm timing stage:runTopLevelLifecycles Completed in 7543ms
npm verb saving [
npm verb saving   {
npm verb saving     name: 'node-red-node-serialport',
npm verb saving     spec: '^1.0.4',
npm verb saving     save: 'dependencies'
npm verb saving   }
npm verb saving ]
npm info lifecycle [email protected]~preshrinkwrap: [email protected]
npm info lifecycle [email protected]~shrinkwrap: [email protected]
npm info lifecycle [email protected]~postshrinkwrap: [email protected]
+ [email protected]
added 20 packages from 100 contributors and audited 310 packages in 8.192s

55 packages are looking for funding
  run `npm fund` for details

found 13 vulnerabilities (3 low, 10 moderate)
  run `npm audit fix` to fix them, or `npm audit` for details

node-red:

Welcome to Node-RED
===================

30 Aug 20:13:15 - [info] Node-RED version: v3.0.2
30 Aug 20:13:15 - [info] Node.js  version: v14.21.3
30 Aug 20:13:15 - [info] Linux 5.10.92-v7l+ arm LE
30 Aug 20:13:16 - [info] Loading palette nodes
30 Aug 20:13:18 - [info] Worldmap version 2.42.2
30 Aug 20:13:18 - [info] Dashboard version 3.5.0 started at /ui
30 Aug 20:13:18 - [info] Settings file  : /data/settings.js
30 Aug 20:13:18 - [info] Context store  : 'default' [module=memory]
30 Aug 20:13:18 - [info] User directory : /data
30 Aug 20:13:18 - [warn] Projects disabled : editorTheme.projects.enabled=false
30 Aug 20:13:18 - [info] Flows file     : /data/flows.json
30 Aug 20:13:18 - [warn] 

---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

30 Aug 20:13:18 - [warn] Encrypted credentials not found
30 Aug 20:13:18 - [info] Server now running at http://127.0.0.1:1880/
30 Aug 20:13:18 - [info] Starting flows
./entrypoint.sh: line 14:     9 Segmentation fault      (core dumped) /usr/local/bin/node $NODE_OPTIONS node_modules/node-red/red.js --userDir /data $FLOWS "${@}"

Flow:

cat /usr/blueos/userdata/node-red/flows.json 
[
    {
        "id": "a645a811594eb0f0",
        "type": "tab",
        "label": "Flow 1",
        "disabled": false,
        "info": "",
        "env": []
    },
    {
        "id": "e1649fb4f7544b2b",
        "type": "serial-port",
        "serialport": "/dev/ttyACM2",
        "serialbaud": "115200",
        "databits": "8",
        "parity": "none",
        "stopbits": "1",
        "waitfor": "",
        "dtr": "none",
        "rts": "none",
        "cts": "none",
        "dsr": "none",
        "newline": "\\n",
        "bin": "false",
        "out": "char",
        "addchar": "",
        "responsetimeout": "10000"
    },
    {
        "id": "d64a0f61d894d39e",
        "type": "serial in",
        "z": "a645a811594eb0f0",
        "name": "",
        "serial": "e1649fb4f7544b2b",
        "x": 530,
        "y": 740,
        "wires": [
            [
                "12d22d769a98c1b1"
            ]
        ]
    },
    {
        "id": "12d22d769a98c1b1",
        "type": "debug",
        "z": "a645a811594eb0f0",
        "name": "debug 1",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": true,
        "complete": "payload",
        "targetType": "msg",
        "statusVal": "payload",
        "statusType": "auto",
        "x": 700,
        "y": 720,
        "wires": []
    }
]

Originally posted by @patrickelectric in https://github.com/node-red/node-red-nodes/issues/894#issuecomment-1699778378

Lenguaje dominante: JavaScript
Estrellas: 1.1k
Forks: 610
Merge medio: 18 h 41 min
PR fusionados (30 d): 4

Preparar el entorno

Sin Dockerfile ni archivo de Docker Compose
Tiene una plantilla de pull request
Leer la guía de contribución

Primeros pasos

Lee el issue completo y luego la guía de contribución del proyecto.
Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
Haz un fork del repositorio y trabaja en una rama.
Abre un pull request que haga referencia al número del issue.

Más de node-red/node-red-nodes

Breaking changes in node-red-node-mysql dependency
Abierto
- ¿Algo no está bien?
Dificultad 3/5 1-2 días Aptitud para principiantes 58/100

node-red/node-red-nodes#1142 · 11 comentarios · Abierto el 16/7/2026
XMPP node issue (follow #1135)
Abierto
- ¿Algo no está bien?
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100

node-red/node-red-nodes#1141 · 15 comentarios · Abierto el 9/7/2026
email-in node crashed node-red
Abierto
- ¿Algo no está bien?
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100

node-red/node-red-nodes#1130 · 4 comentarios · Abierto el 20/4/2026
node-red-node-sqlite dependency `sqlite3` is DEPRECATED and has upstream high severity vuln
Abierto
- ¿Algo no está bien?
dependencies

Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100

node-red/node-red-nodes#1121 · 5 comentarios · Abierto el 26/1/2026
node-red-node-email does not fallback to IPv4 if IPv6 connection fails
Abierto
- ¿Algo no está bien?
upstream

Dificultad 3/5 1-2 días Aptitud para principiantes 50/100

node-red/node-red-nodes#1116 · 5 comentarios · Abierto el 18/12/2025

Todos los issues de node-red/node-red-nodes

Issues similares

navigator.sendBeacon() leaves its fetch() promise unhandled, so a failed beacon becomes an unhandled rejection
Abierto
- ¿Algo no está bien?
bug

Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100

capricorn86/happy-dom#2485 · Abierto el 10/10/2026

Los mantenedores suelen responder en 2 días
Windows frontend tests fail on the map host session file path assertion
Abierto
- ¿Algo no está bien?
Dificultad 2/5 Menos de una hora Aptitud para principiantes 74/100

siyuan-note/siyuan#20429 · Abierto el 10/10/2026

Los mantenedores suelen responder en 1 día
Type definition for TilemapLayer.getTileAt is wrong
Abierto
- ¿Algo no está bien?
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100

phaserjs/phaser#7396 · Abierto el 10/10/2026

Los mantenedores suelen responder en 2 días
建议：injector 面板 render 期注入的 <style> 补 data-plugin 归属（DSH 客户端样式账本会误认领）
Abierto
- ¿Algo no está bien?
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100

yjh051108/dsh-routing-suite#216 · Abierto el 10/10/2026
[Bug] Completion info popup (.cm-completionInfo) ignores the configured editor font
Posiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
- ¿Algo no está bien?
bug user-priority/P2

Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100

t8y2/dbx#11718 · 1 comentario · Abierto el 10/10/2026

Los mantenedores suelen responder en 1 día

Más issues de JavaScript

node-red-node-serialport node makes the Docker container infinite boot cycle

¿Algo no está bien?

Evaluación

Línea de trabajo

Descripción

Preparar el entorno

Primeros pasos

Más de node-red/node-red-nodes

¿Algo no está bien?

¿Algo no está bien?

¿Algo no está bien?

¿Algo no está bien?

¿Algo no está bien?

Issues similares

¿Algo no está bien?

¿Algo no está bien?

¿Algo no está bien?

¿Algo no está bien?

¿Algo no está bien?

Recibe los nuevos issues en tu correo