error-handling
Here are 833 public repositories matching this topic...
This stackoverflow post outlines a different method of using namedParameters than the readme and seems to be correct. Readme could be updated to match.
https://stackoverflow.com/questions/6212219/passing-parameters-to-a-bash-function
In documentation, should point out, tracing source maps using
StackTrace.fromError() causes UI blocking a lot.
It seems like tracing source maps is a very CPU intensive job. Ideally everybody would avoid it.
We need to look into this and possibly file a bug as the event's end point isn't returning a sample json model for events.
Update Release Notes
I see that there is a new version showing in my Nuget Package Manager. However, the Release Notes haven't been updated since Nov. 2017. It would be nice to not have to dig thru recent commit(s) to see what's been changed. Can you please update the Release Notes?
(Beginner here, apologies if this is not valid issue.)
This guide example seems not to compile. There's this line:
use failure::err_msg;
but the called macro is:
return Err(format_err!("Input did not begin with
$"));
So should the use statement be:
use failure::format_err;
?
Also there's [other example](https://boats.gitlab
-
Updated
May 24, 2020 - PHP
-
Updated
Oct 11, 2019 - Java
-
Updated
May 29, 2020 - JavaScript
Awesome project
Perhaps add an example that shows best practice of using StatusProvider
with a UITableViewController
. This would be very helpful
I'm not sure if I should make use of tableView.backgroundView
or set tableView.separatorStyle = .none
or show a view that covers the tableView.
-
Updated
Mar 14, 2020 - JavaScript
-
Updated
Mar 14, 2020 - JavaScript
-
Updated
May 21, 2020 - PHP
I am trying to use your package for certain use cases and i am confused beyond a point. For instance, i have scenarios for custom errors and error types or error codes etc. I am looking at adding namespaces etc and your documentation is not helping me move forward. Could someone please address it and help me or developers like me understand how to go about using your library better?
Add eris.As(...)
For completion, we should offer an As
method like the one in Go 1.13 errors (https://golang.org/pkg/errors/#As). We should try to make this more reliable than Go's version by preventing panics: "As will panic if target is not a non-nil pointer to either a type that implements error, or to any interface type." Seems like we could just return false in these cases instead.
-
Updated
Mar 15, 2019 - Go
-
Updated
Mar 14, 2020 - TypeScript
RxJava throws these, we should add a test to capture behavior changes
Can you guys update your example to include a custom express.js server? The Next.js example you have is too trivial for real world situations so it'd be much more helpful to show how to use bugsnag in cases where you'd have custom routes being served by express. (I know that API routes exist now. but they didn't exist before so it'd be nice to show case common use cases within Next.js)
We're cu
A common error is attempting to use MyErrorEnum::Variant
when the context selector Variant
should be used instead. It's worth documenting this.
Are there any other common issues?
I am bundling rollbar in my webpack build, so I am importing rollbar from its npm package. E.g.
import Rollbar from 'rollbar';
// ... somewhere else
new Rollbar({ accessToken: ..., ... })
The Rollbar
constructor accepts a bunch of options, and the type definition says that it should accept code_version
as well as codeVersion
([here](https://github.com/rollbar/
-
Updated
May 28, 2020 - PHP
-
Updated
May 31, 2020 - JavaScript
-
Updated
Jan 30, 2019 - Java
Description
A lot of console.warn yellow warning message when the data pass to leaveBreadcrumbs contains functions.
Describe the solution you'd like
-
Updated
Mar 1, 2020 - Python
-
Updated
Feb 28, 2020 - Swift
-
Updated
Feb 25, 2020 - Scala
-
Updated
Mar 12, 2019 - Go
Improve this page
Add a description, image, and links to the error-handling topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the error-handling topic, visit your repo's landing page and select "manage topics."
Package version eg. v8, v9:
v9
Issue, Question or Enhancement:
If a fqdn starts with an integer f.e. "0.de.pool.ntp.org", the validation fails. The example "0.de.pool.ntp.org" is a valid ntp-server (see https://www.pool.ntp.org/zone/de).
Code sample, to showcase or reproduce: