Results for find-import

Find unused Objective-C imports.

Descriptions are provided in doc and at fidius.me

A Github issues importing tool

A primitive in-memory collection of key-value records known as "facts," with an ability to insert facts, add properties to facts, and delete facts. There is no ability to modify facts. It is also possible to find facts using Lisp-alike query predicates. An entire factbase may be exported to a binary file and imported back.

Capistrano exts is a set of helper tasks to help with the initial server configuration and application provisioning. Things like creating the directory structure, setting up that database, and other one-off you might find yourself doing by hand far too often. It provides many helpful post-deployment tasks to help you import/export database and contents as well as sync one stage with another.

Code coverage details for your native extensions are at least as important as for ruby. This gem will help you get code coverage details for our native C code in your ruby gems, to find blindspots and prevent bugs from creeping in.

To support Black Lives Matter and create safer spaces, I wanted to rename all of the default branches in my Gitlab account. I wasn't able to find any tools to do that, so I wrote this one. If you're unsure why this is important or want to better understand why I wanted to make these changes, see this great {Twitter thread}[https://twitter.com/mislav/status/1270388510684598272].

DbValidator helps identify invalid records in your Rails application that don't meet model validation requirements. It finds records that became invalid after validation rule changes, and validates imported or manually edited data. You can use it to audit records before deploying new validations and catch any data that bypassed validation checks.

HAST stands for 'Hosting Account Status Tool'. HAST is a tool for fetching domains from Apache configuration files and from Postfix on a hosting server environment. It will then run a report, checking the DNS records for each domain to see if they match your server. This is important for finding "dead" domains where the domain either doesn't exist anymore or where the owner have moved it to another hosting provider. Before you can use HAST, you need to setup a config.yml file. Run 'hast --generate-config > config.yml' to create a sample config file that you can modify.

Guess gender by a first name using more detailed, better sourced data from Open Gender Tracker's Global Name Data.<br /> Beauvoir lets you set avg and lower bounds and choose countries from which to draw data. It's important to note that many people identify as neither a men nor a women. It's important, too, to note that many people who do identify as male or female have names that<br /> are held by far more people who identify as another gender. All of these people deserve not to be misgendered in public (or in private). Nevertheless, automatically classifying people by apparent gender can be a very useful tool to perform censuses of communities or publications to detect and quantify perhaps-invisible bias. VIDA is a pioneer in this field, but their "Count" is limited by a manual methodology that depends hundreds of person-hours of labor. There is a place for more automated counts and Beauvoir can help, but if you do a count like this, you should be careful in how you word your findings not to misgender anyone in particular and be responsive to the possibility of errors.

This gem is designed to provide a modular, complete, open-source, crowd-sourced mapping of the 650+ IANA/OLSON timezones of the world into Rails' 146 'important' timezones. A search for an existing solution showed that this has been an issue since the inception of ActiveSupport::Timezone as far back as 2012. Approaches which have been suggested included such ideas as: Making your own RTree in a spatially aware database and searching on boundaries, just don't use those timezones (yeah, that makes sense), rely on your users to set their own timezone (doesn't help if you do automated onboarding), find a better sourcing API for timezones based on GeoLookup (they almost all use OLSON/IANA). Rather than doing any of those things, it made more sense to simply complete the mapping that ActiveSupport::Timezone started on and then seemingly abandoned.

Have you ever wanted to call &lt;code&gt;exit()&lt;/code&gt; with an error condition, but weren't sure what exit status to use? No? Maybe it's just me, then. Anyway, I was reading manpages late one evening before retiring to bed in my palatial estate in rural Oregon, and I stumbled across &lt;code&gt;sysexits(3)&lt;/code&gt;. Much to my chagrin, I couldn't find a +sysexits+ for Ruby! Well, for the other 2 people that actually care about &lt;code&gt;style(9)&lt;/code&gt; as it applies to Ruby code, now there is one! Sysexits is a *completely* *awesome* collection of human-readable constants for the standard (BSDish) exit codes, used as arguments to +exit+ to indicate a specific error condition to the parent process. It's so fantastically fabulous that you'll want to fork it right away to avoid being thought of as that guy that's still using Webrick for his blog. I mean, &lt;code&gt;exit(1)&lt;/code&gt; is so passé! This is like the 14-point font of Systems Programming. Like the C header file from which this was derived (I mean forked, naturally), error numbers begin at &lt;code&gt;Sysexits::EX__BASE&lt;/code&gt; (which is way more cool than plain old +64+) to reduce the possibility of clashing with other exit statuses that other programs may already return. The codes are available in two forms: as constants which can be imported into your own namespace via &lt;code&gt;include Sysexits&lt;/code&gt;, or as &lt;code&gt;Sysexits::STATUS_CODES&lt;/code&gt;, a Hash keyed by Symbols derived from the constant names. Allow me to demonstrate. First, the old way: exit( 69 ) Whaaa...? Is that a euphemism? What's going on? See how unattractive and... well, 1970 that is? We're not changing vaccuum tubes here, people, we're &lt;em&gt;building a totally-awesome future in the Cloud™!&lt;/em&gt; include Sysexits exit EX_UNAVAILABLE Okay, at least this is readable to people who have used &lt;code&gt;fork()&lt;/code&gt; more than twice, but you could do so much better! include Sysexits exit :unavailable Holy Toledo! It's like we're writing Ruby, but our own made-up dialect in which variable++ is possible! Well, okay, it's not quite that cool. But it does look more Rubyish. And no monkeys were patched in the filming of this episode! All the simpletons still exiting with icky _numbers_ can still continue blithely along, none the wiser.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.