Information for RPM golang-github-bugsnag-panicwrap-1.3.2-6.0.riscv64.fc38.src.rpm
ID | 1037829 | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Name | golang-github-bugsnag-panicwrap | ||||||||||||||||
Version | 1.3.2 | ||||||||||||||||
Release | 6.0.riscv64.fc38 | ||||||||||||||||
Epoch | |||||||||||||||||
Arch | src | ||||||||||||||||
Summary | Go library for catching and handling panics in Go applications | ||||||||||||||||
Description | Panicwrap is a Go library that re-executes a Go binary and monitors stderr output from the binary for a panic. When it find a panic, it executes a user-defined handler function. Stdout, stderr, stdin, signals, and exit codes continue to work as normal, making the existence of panicwrap mostly invisble to the end user until a panic actually occurs. Since a panic is truly a bug in the program meant to crash the runtime, globally catching panics within Go applications is not supposed to be possible. Despite this, it is often useful to have a way to know when panics occur. panicwrap allows you to do something with these panics, such as writing them to a file, so that you can track when panics occur. Panicwrap is not a panic recovery system. Panics indicate serious problems with your application and should crash the runtime. panicwrap is just meant as a way to monitor for panics. If you still think this is the worst idea ever, read the section below on why. | ||||||||||||||||
Build Time | 2023-07-07 16:50:17 GMT | ||||||||||||||||
Size | 35.15 KB | ||||||||||||||||
fa55e876e5c7af3695bf43cf66f6406d | |||||||||||||||||
License | MIT | ||||||||||||||||
Provides |
|
||||||||||||||||
Obsoletes | No Obsoletes | ||||||||||||||||
Conflicts | No Conflicts | ||||||||||||||||
Requires |
|
||||||||||||||||
Recommends | No Recommends | ||||||||||||||||
Suggests | No Suggests | ||||||||||||||||
Supplements | No Supplements | ||||||||||||||||
Enhances | No Enhances | ||||||||||||||||
Files |
|
||||||||||||||||
Component of | No Buildroots |