Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Erro no deploy após atualização 2.2.2, intalação via NVM #1188

Open
1 task done
joaokrabbe opened this issue Jan 31, 2025 · 0 comments
Open
1 task done

Erro no deploy após atualização 2.2.2, intalação via NVM #1188

joaokrabbe opened this issue Jan 31, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@joaokrabbe
Copy link

Welcome!

  • Yes, I have searched for similar issues on GitHub and found none.

What did you do?

Tenho a evolution instalada em Cloud Ubuntu 24.10, utilizei o metodo direto com NVM.
Estava na versão 2.2.0, e fiz a atualização para 2.2.2 seguindo o doc de instalação NVM, para pegar a corregaõa da biblioteca Bailes.
Porem estou tendo erro na hora do deploy "Error: The service was stopped: write EPIPE".
Segue log abaixo.

What did you expect?

Instruções de como realizar a atualização direta sem uso do docker.

What did you observe instead of what you expected?

Não consigo realizar o build na versão 2.2.2, apenas as anteriores.

Screenshots/Videos

No response

Which version of the API are you using?

2.2.2

What is your environment?

Windows

Other environment specifications

Ubuntu 24.10
Node.js v20.10.0

If applicable, paste the log output

`
CLI Using tsconfig: tsconfig.json
CLI tsup v8.3.6
CLI Using tsup config: /var/www/evolution-api/tsup.config.ts
CLI Target: es2020
CLI Cleaning output folder
CJS Build start
ESM Build start
CJS You have emitDecoratorMetadata enabled but @swc/core was not installed, skipping swc plugin
ESM You have emitDecoratorMetadata enabled but @swc/core was not installed, skipping swc plugin
Error: The service was stopped: write EPIPE
at /var/www/evolution-api/node_modules/esbuild/lib/main.js:816:34
at responseCallbacks. (/var/www/evolution-api/node_modules/esbuild/lib/main.js:622:9)
at afterClose (/var/www/evolution-api/node_modules/esbuild/lib/main.js:613:28)
at /var/www/evolution-api/node_modules/esbuild/lib/main.js:1989:18
at onwriteError (node:internal/streams/writable:589:3)
at process.processTicksAndRejections (node:internal/process/task_queues:84:21)
/var/www/evolution-api/node_modules/esbuild/lib/main.js:677
else callback(null, packet.value);
^

TypeError: callback is not a function
at handleIncomingPacket (/var/www/evolution-api/node_modules/esbuild/lib/main.js:677:12)
at Socket.readFromStdout (/var/www/evolution-api/node_modules/esbuild/lib/main.js:600:7)
at Socket.emit (node:events:514:28)
at addChunk (node:internal/streams/readable:545:12)
at readableAddChunkPushByteMode (node:internal/streams/readable:495:3)
at Readable.push (node:internal/streams/readable:375:5)
at Pipe.onStreamRead (node:internal/stream_base_commons:190:23)

Node.js v20.10.0
`

Additional Notes

No response

@joaokrabbe joaokrabbe added the bug Something isn't working label Jan 31, 2025
@joaokrabbe joaokrabbe changed the title Atualização 2.2.2 via NVM Erro no deploy após atualização 2.2.2, intalação via NVM Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant