In rails 3.2, it’s easier than that: Add this to config/application.rb: config.exceptions_app = self.routes That causes errors to be routed via the router. Then you just add to config/routes.rb: match “/404”, :to => “errors#not_found” I got this info from item #3 on the blog post “My five favorite hidden features in Rails 3.2” by By … Read more
AFAIK you cannot make the red thingies go away, when returning error status-codes (4xx, 5xx). They are used by the browser to indicate that something might have not gone as expected. Still these are mere decorations, since 4xx and 5xx status codes are perfectly valid, so I don’t see a reason for you wanting to … Read more
Have any of you tried Expected; in practice? It’s quite natural, I used it even before I saw this talk. How would you apply this idiom to functions returning nothing (that is, void functions)? The form presented in the slides has some subtle implications: The exception is bound to the value. It’s ok to handle … Read more
Here’s one technique you could use. Define an ErrorsController which will serve the error pages: public class ErrorsController : Controller { public ActionResult Http404() { Response.StatusCode = 404; return Content(“404”, “text/plain”); } public ActionResult Http500() { Response.StatusCode = 500; return Content(“500”, “text/plain”); } public ActionResult Http403() { Response.StatusCode = 403; return Content(“403”, “text/plain”); } } … Read more
I consider fatal errors to be when your application can’t do any more useful work. Non-fatal errors are when there’s a problem but your application can still continue to function, even at a reduced level of functionality or performance. Examples of fatal errors include: Running out of disk space on the logging device and you’re … Read more
cerr is the C++ stream and stderr is the C file handle, both representing the standard error output. You write to them the same way you write to other streams and file handles: cerr << “Urk!\n”; fprintf (stderr, “Urk!\n”); I’m not sure what you mean by “recover” in this context, the output goes to standard … Read more
Error is a trait and you want to return a trait object (note the dyn keyword), so you need to implement this trait: use std::error::Error; use std::fmt; #[derive(Debug)] struct MyError(String); impl fmt::Display for MyError { fn fmt(&self, f: &mut fmt::Formatter) -> fmt::Result { write!(f, “There is an error: {}”, self.0) } } impl Error for … Read more
According to docs: %v the value in a default format … %s the uninterpreted bytes of the string or slice Also, more information about error: The error type is an interface type. An error variable represents any value that can describe itself as a string. So, treat it as %s.
Handling a stack overflow is not the right solution, instead, you must ensure that your program does not overflow the stack. Do not allocate large variables on the stack (where what is “large” depends on the program). Ensure that any recursive algorithm terminates after a known maximum depth. If a recursive algorithm may recurse an … Read more