rx error handler
Viral Propagation Simulator, icluding pathogen parameters, social isolation, health care system overloading, fatality rates
No description provided.
git repository tools and related utilities
A simple logging utility with a save function.
New Updated script v-u98k5y
A simple and lightweight keybindings for Ember applications.
Download ebook pdf mobi epub Alex Gray Pitch Black is available now
Fatality extension to `thiserror::Error`
Fatality extension to `thiserror::Error`
What a bother. I want to logging it without setting it.
Lightweight and efficient rust structured log library with support for log level, file shred, compressed archive
Potentially fatal diagnostics and diagnostic handling for compilers
Allows non-fatal errors in a tree of subfunctions to easily be collected by a caller
A parser for json data found at 'Vision Zero Chicago Traffic Fatalities | Chicago Data Portal' into GeoJson without unecessary properties.
Differentiate errors and fatal errors
Code generation for the maybe-fatal crate
Retry-as-a-value: zero-cost, ownership-friendly retries with diagnosable outcomes with full async and lib/app boundaries support
Fatality extension to crate thiserror - proc-macro part
Fatality extension to crate thiserror - proc-macro part
raise CRuby internal fatal error by calling rb_fatal()
Ernr builds on the power of Rails 3 validations. It lets you use validations to identify situations which are warnings rather than errors. It also lets you define a callback on the model which is executed after save if there are any warnings.
If you want to get an email with errors and fatal log lines you can use this gem.
Ha! Art thou Bedlam? Dost thou thirst base Trojan, to have me fold up Parca's fatal web? Hence!\ I am qualmish at the smell of leek.
Soft semantics for Ruby to automatically recover from fatal exceptions and to repair damaged programs. Used to improve robustness, expressiveness and performance in Grammatical Evolution.
The Logging email appender provides a way to send log messages via email from a Ruby application. This is useful if you wish to be notified of exceptions or fatal errors as they arise. The email appender was originally part of the Logging framework proper, but with the release of Logging 2.0.0, it has been extracted into its own gem.
A Free Software, multi-threaded, non-blocking network application server designed for low _idle_ power consumption. It is primarily optimized for applications with occasional users which see little or no traffic. yahns currently hosts Rack/HTTP applications, but may eventually support other application types. Unlike some existing servers, yahns is extremely sensitive to fatal bugs in the applications it hosts.
# Fancy Logger An easily customizable logger with style. ## Install ### Bundler: `gem 'fancy_logger'` ### RubyGems: `gem install fancy_logger` ## Usage Simply use as if you were using the normal Ruby `Logger` class: ```ruby require 'fancy_logger' logger = FancyLogger.new(STDOUT) logger.info "Hello" ``` ### Config The `config` instance method allows you to modify the configuration of the Logger within a DSL. Continuing with our last example: ```ruby logger.config do timestamp_format "%c" styles do info do foreground :yellow blink true end end end logger.debug 'Look here!' logger.info 'Doing things...' logger.warn 'Watch out!' logger.error 'Bad' logger.fatal 'VERY bad' logger.unknown 'Weird unknown stuff' ``` #### Output ![][output_example] ### Config ```ruby # The format of the timestamp in the log. Follows the strftime standards. timestamp_format "%F %r" # On the first logged message, FancyLogger will prepend a help message # containing a list of all the severities (debug, info, warn, etc) styled # according to your config as reference. # You can disable this by setting the below option to false. show_help_message true # Under styles, you have a configuration for each severity. # Each severity has a configuration with the following valid options: # Key: foreground # Value: # :default, :black, :red, :green, :yellow, :blue, :magenta, :cyan, :white # # Key: background # Value: # :default, :black, :red, :green, :yellow, :blue, :magenta, :cyan, :white # # Key: reset # Value: true or false # # Key: bright # Value: true or false # # Key: italic # Value: true or false # # Key: underline # Value: true or false # # Key: # blink # Value: true or false # # Key: inverse # Value: true or false # # Key: hide # Value: true or false styles do debug do foreground :black background :cyan end info do foreground :default background :default end warn do foreground :yellow background :default blink true end error do foreground :red background :default end fatal do foreground :black background :red bold true underline true end unknown do foreground :black background :white underline true end end ``` ## Contributing * Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet * Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it * Fork the project * Start or switch to a testing/unstable/feature/bugfix branch * Commit and push until you are happy with your contribution * Make sure to add tests for it. This is important so I don't break it in a future version unintentionally. * Please try not to mess with the Rakefile, VERSION or gemspec. ## Copyright Copyright © 2012 Ryan Scott Lewis <ryan@rynet.us>. The MIT License (MIT) - See LICENSE for further details. [output_example]: http://oi44.tinypic.com/sfwlkp.jpg