Nextjs stucks at compiling all of a sudden i do not know why. I change something in code and save then it stucks at compiling, when i refresh the page it throws internal server error.
[Error: UNKNOWN: unknown error, open 'C:\Users\Omer\stateskop-deployment\src\client\.next\build-manifest.json'] {
errno: -4094,
code: 'UNKNOWN',
syscall: 'open',
path: 'C:\\Users\\Omer\\stateskop-deployment\\src\\client\\.next\\build-manifest.json'
}
I serve my app with Nestjs backend, i think this problem started after i implemented localization with next-translate. I deleted every file relevant to that but still couldnt fix the problem and i have no idea why this problem occurs
Related
We use next.js with knex.js as query builder, in all pages everything is OK except in one page that we have ISR aka getStaticPaths and in that method we get the following error whenever we try to execute a query, but in other pages that do not have getStaticPaths everything works fine:
Server Error
Error: getaddrinfo ENOTFOUND undefined
This error happened while generating the page. Any console logs will be displayed in the terminal window.
Call Stack
GetAddrInfoReqWrap.onlookup [as oncomplete]
node:dns (71:26)
no more info is provided anywhere else. as it is shown in the error message, the database host is undefined but why it read correctly everywhere except in getStaticPaths??
Turns out we had this experimental feature tuned on in next.config.js, when it is turned on .env variables are all undefined and not loaded correctly inside getStaticPaths but once the getStaticProps is called everything is OK, I do not know the reason for this, but turning workerThreads off solved the problem:
experimental: {
workerThreads: false //fixed the problem
},
I've made a Shinyapp, and try to turn it into a standalone application through Nodejs and Electron.
I've sucessfully made it on Windows. However, when I work on macOS, I encounter this error:
A JavaScript error occurred in the main process
Uncaught Exception: Error: spawn {path of electron file} Enoent at ...the error displayed
Guess there's something wrong in Nodejs, but I'm a total newbie to nodejs. Have tried to add the file path into PATH environment variable, but it did not wrok. The same error appears.
Looking for someone who can help me sort it out.
I appreciate any help from you!!
I have just put some changes to a wordpress theme live, it all works on the staging server but for some reason it's giving a critical error on the live site.
As normal i go and look at the debug.log file and there is no fatal error is showing in that file, and no error_log is showing it either.
Any ideas on why it's not recording the fatal error (usually that is what causes the wordpress critical error)
Probably, the "fatal error" you're talking about occurred before WordPress was initialized. For example, if the code, that triggers the error is located in index.php of your active theme.
In this case, try to find error messages not in wp-content/debug.log, but in webserver logs folder /var/log/httpd/error_log/ or /var/log/apache2/error.log
I just installed a copy of Sylius on my dev server (Ubuntu), configured the database parameters, resolved all dependencies, and ran sylius:install. Install completed successfully, and all looked good.
When trying to access the front-end (web/app_dev.php), however, I get an error thrown during template rendering:
Uncaught PHP Exception Twig_Error_Runtime: "An exception has been
thrown during the rendering of a template ("Channel could not be
found!") in "SyliusWebBundle:Frontend:layout.html.twig" at line 55."
at
/var/www/mysite.com/public_html/vendor/twig/twig/lib/Twig/Template.php
line 182 Context: { "exception": "Object(Twig_Error_Runtime)" }
I'm not entirely sure what channel it's unable to find, or how to resolve this.
In my meteor app I'm getting this error
Error: Cannot find module 'connect'
I haven't installed connect in my local server and its working fine there.The issue occurred when the code was moved to server. Why is this happening ? What else data should I provide for anyone to help me !