I used to program with Ruby on rails and I have just started SailsJS.
With rails when I had an error in my backend, it didnt kill my server. I used to have a nice error displayed in my web browser and I even used the gem better error to have a live console displayed in my webbrowser when an error occured.
How can I prevent the server to shut down everytime there's an error in Sails JS ?
Is there a way to have a nice way to display errors with Sails (with the live console in the web browser, just like with the gem better errors) ?
For running your server despite errors, take a look at foreverjs. However, I'd advise you to be defensive about your programming and properly handle errors.
Related
This app is built using umijs and antdesign pro for frontend and node js express server for backend hosted on a Ubuntu server and Cloudflare is used for DNS management.
If the app is being loaded for the first time on any browser, it works as intended. But if we refresh it, it gets stuck on loading and outputs this specific problem:
for chrome:
for firefox
The app is then only re-usable after purging cache (Cloudflare) and then persists again when refreshing. The problem does not exist when using "serve" and serving the files locally.
This issue produces by a service-worker. try without service-worker.
Currently using Selenium + ChromeDriver to execute automated functional tests through Azure DevOps VsTest task but whenever the task tries to execute tests pointing to a website in NetCore, it times out very quickly and sometimes (a lot of times) I get the standard error message from the registered screenshot on error of "This site can't be reached".
I tried running this locally and pointing to the same website but this issue doesn't seem to happen at all and I've got no clue on what's going on due to the big inconsistency between the results that the VsTest task provides.
I also tried opening Chrome on the machine that executes the task but it seems to open the URL fine there.
One thing to note is that the website I'm using uses Windows Authentication mechanism and I'm sending my credentials directly through the URL with https:\\credentialuserexample1:credentialpassexample2#thewebsiteaddress.com and it seems to open the page without issue there too.
After upgrading an application from .NET Core 1.0 to 2.1, I am receiving the following error when I try to debug it with IIS Express:
Unable to start process C:\Program Files\dotnet\dotnet.exe. The web server request failed with status code 502, Bad Gateway.
However, this only happens every second time I launch the application. Otherwise it works just fine if I just launch it again.
This creates a mild nuisance to my debugging process, as I constantly have to keep closing the error windows popping up.
The full response shows some additional info:
HTTP Error 502.3 - Bad Gateway
The specified CGI application encountered an error and the server terminated the process.
And the error code "0x80072efe" is shown.
Logging is enabled in web.config, but the crashing launches are not shown at logs at all. I have also tried looking Event Viewer for additional information, but I have not found anything.
The only fix for this I have found so far is to set Kestrel use libuv instead of sockets, but I have no idea why it works. Does anyone have any idea how to fix this?
I encountered the same problem after I upgraded, regardless of what I did it would always show the 502 error on the second load. It appears this problem was introduced in ASP.NET Core 2.1. I tracked it down to the asp-prerender-module tag in my view. Remove the prerender and it goes away.
I was able to fix the problem and keep my prerendering by upgrading to ASP.NET Core 2.2.
I have setup airbrake in my app but it doesn't seem to log any 500 errors I get in production. The error is most certain an action mailer issue but Airbrake is not catching this error.
I have no custom error handling in my app at this point removed it.
What would be a good way to determine why it doesn't log?
First, please make sure you're using the latest GEM http://rubygems.org/gems/airbrake .
Please send a support ticket to support#airbrake.io and we'll do our best to resolve this issue for you.
I'm a web application developer, who runs a site http://myfav.es. We've been struggling with this issue for about a month now.
We use the HTML application cache spec - www.w3.org/TR/offline-webapps/ - with dynamically generated manifest files - myfav.es/personal.manifest - to speed page delivery. These dynamically generated manifest files use proper headers, and PHP to serve up custom manifests for users.
We also use gzip compression to serve the site from a linux/apache host.
For the life-cycle of our site, users report getting a err_failed similar to this screenshot in chrome. twitpic.com/272237.
This error is intermittent, occuring once every 200-300 visits, but will persists on every page refresh, including hard refreshes, which presumably means that an error using app cache is causing them to continuously load a failed version of the site. However, mysteriously JUST clearing cookies causes the error to fix itself.
I'm completely out of ideas on how to approach this error, and googling the error message appears to get a ton of confused users with voodoo-ish approaches to solving it. I've personally seen the error, along with a number of complaint from other users of chrome, so I'm fairly certain it cannot be caused by a particular user having abnormal settings or browser preferences.
Does anyone have any insight into the cause of this browser error and its origins? Whether its likely server-side or a byproduct of app design?