Rendering Process Failed
- This topic has 1 reply, 2 voices, and was last updated 6 months, 1 week ago by .
- May 9, 2021 at 1:12 pm #5783itips3727
I have a weird problem that seems to have started to occur from Publii v0.38.xx.
Apple macOS Big Sur v11.3.1.
Tested on Publii v.0.38.2 (build 14204).
The problem seems to occur on any / all Publii-sourced themes. The following just uses the Sources theme as a test.
When rendering, on the first render attempt, the render fails. On the second render attempt (straight after), the render always succeeds. So two immediately successive render attempts always succeeds, but a single / first render attempt fails.
On render failure, the following text appears in render-errors.log:
(node:47500) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, mkdir ‘/Users/<name>/Documents/Publii/sites/sources-test/preview/media/posts’
(node:47500) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `–unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:47500) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
On the second successive render, of course the render-errors.log is empty.
Thanks.May 18, 2021 at 4:22 pm #5826Tomasz Dziuda
I saw this error few times, but to be honest I am unable to find a way which always allows me to reproduce this bug. If you will be able to find such way to reproduce this issue – please share it 🙂
Do you appreciate the support you've received today? If so, consider donating to the Publii team by clicking here; we'll be sure to use your donation to make Publii even better!
- You must be logged in to reply to this topic.