Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cache preparation, non-fatal error from Now

See original GitHub issue

There is a (new) build-time error I’ve just been seeing today. It is non-fatal, and deployments still work with no problems. The error message is:

TypeError: Path must be a string. Received undefined
    at assertPath (path.js:28:11)
    at Object.join (path.js:1236:7)
    at Object.prepareCache (/tmp/{project-directory}/.build-utils/.builder/node_modules/@nuxtjs/now-builder/lib/prepare-cache.js:9:25)
    at uploadCacheStep (/var/task/sandbox-worker.js:26330:55)
    at <anonymous>
    at process._tickDomainCallback (internal/process/next_tick.js:228:7)
done

Could this be the result of an upstream API change? However, others have experienced it previously. Is anyone else seeing this in their logs?

Edit: Posted in Now chat.

Issue Analytics

State:
Created 4 years ago
Reactions:2
Comments:10 (3 by maintainers)

Top GitHub Comments

1reaction

danielroecommented, Sep 9, 2019

As I read it, this error doesn’t actually negatively impact the lambdas produced at all, just make the build take slightly longer as it doesn’t benefit from the Now cache. It seems it was caused by a silent change to the name of the property holding the cache directory, and I’ve now submitted a PR.

(You are welcome to test danielroe/now-builder#cache-error-fix - any feedback gratefully received.)

0reactions

danielroecommented, Sep 10, 2019

@LasaleFamine Would you be able to share a reproduction with me, and maybe create a new issue?

Top Results From Across the Web

Types of Errors - Informatica Documentation

A non-fatal error is an error that does not force the session to stop on its first occurrence. A fatal error occurs when...

Excessive cache flushing can occur during recompilation of a ...

Excessive cache flushing is observed during recompilation of a flow. Cache flush happens every time the flow is recompiled.

I/O cache encountered error while updating data

Hi I have VirtualBox installed on my laptop. I created a Windows 7 VM (25GBs, 2 CPUs), removed it from VirtualBox (I didn't...

15.10 - 5701 Insufficient memory for workload cache.

Explanation: The maximum amount of workload cache memory has been exceeded ... text logged after the Dispatcher hit a non-fatal exception.

Warnings and Errors - Oracle Help Center

Error number Error or warning message Details 403 Attempt to read from checkpoint truncated 412 Bad file‑open mode Internal error. Contact TimesTen C... 413 Bad file‑exists...