TZinfo
ice_cube
Our great sponsors
| TZinfo | ice_cube | |
|---|---|---|
| 5 | 6 | |
| 354 | 2,269 | |
| 0.3% | 0.3% | |
| 6.0 | 0.0 | |
| 3 months ago | 4 days ago | |
| Ruby | Ruby | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
TZinfo
-
Hacker News top posts: Jul 22, 2022
Arbitrary file execution in TZinfo\ (15 comments)
- CVE-2022-31163: Arbitrary file execution in TZinfo (Ruby)
-
CVE-2022-31163: Arbitrary file execution through TZinfo (Ruby)
For everyone who is panicking about this - to be affected, you either need to use a really old version of tzinfo (0.3.60 and earlier), have the tzinfo-data gem installed, or explicitly set TZInfo::DataSource to DataSources::RubyDataSource.
Otherwise, by default, tzinfo will use TZInfo::ZoneinfoDataSource, which does not seem to be affected.
https://github.com/tzinfo/tzinfo/blob/d9b289e1be30d29a2cb23b...
https://github.com/tzinfo/tzinfo/commit/b98c32efd61289fe6f00...
ice_cube
-
ice_cube VS Recurrence - a user suggested alternative
2 projects | 25 Sep 2023
-
Rails way of doing a table with fixed records?
Check https://github.com/ice-cube-ruby/ice_cube
-
Recurring events, looking for recommendations
Hi I've got a project which requires normal one off events, as well as recurring events. Looking at the resources available it seems like there are really just three gems available(montrose, recurrence and ice_cube). Of the three I've had the best results with recurrence because it allows me to pass a hash of arguments to the schedule builder. As well as handling exceptions which montrose doesn't seem to offer.
-
Using IceCube to check for scheduled availabilities?
I'm currently trying out IceCube (https://github.com/ice-cube-ruby/ice_cube) to do some sort of scheduling. Let's say I have a bunch of Employees and I setup a few rules.
-
What is the best way to structure a model to handle recurring time slots (defined by a day of the week and a time of the day)?
I reach for Business Time and Ice Cube when I need to manage recurrence tied to business hours.
What are some alternatives?
Chronic - Chronic is a pure Ruby natural language date parser.
Recurrence - A simple library that handles recurring events.
local_time - Rails engine for cache-friendly, client-side local time
ByStar - Lets you find ActiveRecord + Mongoid objects by year, month, fortnight, week and more!
time-lord - time-lord is a ruby gem that adds extra functionality to the time class.
groupdate - The simplest way to group temporal data
business_time - Support for doing time math in business hours and days
time_diff - Gem which calculates the difference between two times
fugit - time tools (cron, parsing, durations, ...) for Ruby, rufus-scheduler, and flor