jimp-dev/jimp

The "chunk" argument must be of type string or an instance of Buffer or Uint8Array. Received an instance of Promise

Open

#980 opened on Jan 12, 2021

View on GitHub
 (8 comments) (0 reactions) (0 assignees)JavaScript (785 forks)batch import
bughelp wanted

Repository metrics

Stars
 (13,218 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Expected Behavior

I need it will not kill the program because of an error I dont know why is happening

Current Behavior

I get sometimes error, I dont know when, but it not on my code.

events.js:292 throw er; // Unhandled 'error' event ^ TypeError [ERR_INVALID_ARG_TYPE]: The "chunk" argument must be of type string or an instance of Buffer or Uint8Array. Received an instance of Promise at WriteStream.Writable.write (internal/streams/writable.js:285:13) at WriteStream. (/home/XXX/domains/XXX.com/public_html/server/node_modules/@jimp/core/dist/index.js:589:18) at WriteStream.emit (events.js:315:20) at internal/fs/streams.js:380:12 at FSReqCallback.oncomplete (fs.js:171:23) Emitted 'error' event on process instance at: at emitUnhandledRejectionOrErr (internal/event_target.js:545:11) at MessagePort.[nodejs.internal.kHybridDispatch] (internal/event_target.js:358:9) at MessagePort.exports.emitMessage (internal/per_context/messageport.js:18:26) { code: 'ERR_INVALID_ARG_TYPE' }

Failure Information (for bugs)

An error, it happening 1 - 2 times in a day I dont know why, but I using your library to resize and compress images.

Steps to Reproduce

Screenshots

Context

  • Jimp Version: 0.13.0
  • Operating System: Centos 7 64bit
  • Node version: 14.15.4

Failure Logs

Thank you!

Contributor guide

Research direction
The error occurs in @jimp/core/dist/index.js:589 where the write method receives a Promise instead of a Buffer. Investigate the write method in packages/core/src/index.js and ensure that any asynchronous operations resolve before writing to the stream. Check if there is a missing await or improper handling of the image buffer. The user's code shows they are calling Jimp.read with a callback, but the error suggests an unhandled Promise is being passed to write. Examine the internal flow of Jimp.write to see if it incorrectly passes a Promise to the stream's write method.
Tech stack
javascriptnodejs
Domain
backendapi
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Unclear
Prerequisites
Node.js streamsUnderstanding of async/await
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30