Convert a date to a unix timestamp
Approximate (fast) current UNIX time.
A GraphQL scalar for representing unix time seconds
Convert Unix time to a relative time string e.g., "4 hours ago".
TypeScript definitions for unix-time
```ts import {unixTime} from 'unix-time-ts'
WebAssembly bindings for Unix Time Converter tool
Get Unix time exactly in seconds or offset.
datetime to unix-time, datetime add, datetime diff, datetime formatter...
A library to easily convert unix time, utc and gnss time into one another.
transformer conversion: js-date to unix-time
Parses times written in simple English to unix time
A simple object to interact with unix time
Get the current Unix time in milliseconds or converts an epoch to human readable time.
This is random code,exampele:Ru1zaWd2;this is have unix time
Converts unix time, date, string to Date
A TaiDate stores an instant in TAI (International Atomic Time), the same way that a Date stores an instant in Unix time
unix time to date
Tiny library to create and manipulate Unix timestamps
convert unix time to date
Datadog CI plugin for `dora` commands
Portable Unix shell commands for Node.js
wait-on is a cross platform command line utility and Node.js API which will wait for files, ports, sockets, and http(s) resources to become available
Unix datagram socket
A minimal crate to play with Instant based on UNIX epoch
A small utility for working with UNIX time.
A polymorphism-aware OpenAPI compiler
Minimal monotonic unix-time library
Exposes the method `unix_timestamp()`, returning the value in seconds
Gem used for conversion of tim from OLE float datetime to UNIX timestamp and viceversa
Simple UNIX shell time tracker
This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gemname. This gem is not a stand-alone program
Unix cron is a venerable program that turns the passage of time into program invokation. Traut does the same, but using AMQP events to trigger execution. AMQP message payloads are written to the stdin of invoked commands.
UUID v7 is a time-ordered UUID format that encodes a Unix timestamp in the most significant 48 bits, making UUIDs naturally sortable by creation time. This library provides both high-performance and monotonic (strictly ordered) variants.
This gem simplifies monitoring / reporting cron jobs on unix systems. It provides a number of configurable features. Specifically, it can log the output of cron jobs to a file or syslog, rotate the cron job log files, email the user the results of the cron job, time out cron jobs that run past a configurable time out, and more.
Allora (Italian for "at that time") provides a replacement for the classic UNIX cron, using nothing but ruby. It is very small, easy to follow and relatively feature-light. It does support a locking mechanism, backed by Redis, or any other custom implementation, which makes it possible to run the scheduler on more than one server, without worrying about jobs executing more than once per scheduled time.
Xelor was built for systems that require random bytes for processes faster than one second. Because normal random generation is based off of time as a seed, if there exists multiple calls towards SecureRandom or Rand within one second, the same number will be produced. This can be resolved on unix or linux based systems by making a system call to read /dev/urandom.
"The v9 UUID supports both sequential (time-based) and non-sequential (random) UUIDs with an optional prefix of up to four bytes, an optional checksum, and sufficient randomness to avoid collisions. It uses the UNIX timestamp for sequential UUIDs and CRC-8 for checksums. The version can be added if desired, but is omitted by default."
Temporally Ordered IDs. Generate universally unique identifiers (UUID) that sort lexically in time order. Torid exists to solve the problem of generating UUIDs that when ordered lexically, they are also ordered temporally. I needed a way to generate ids for events that are entering a system with the following criteria: 1. Fast ID generation 2. No central coordinating server/system 3. No local storage 4. Library code, that is multiple apps on the same machine can use the same code and they will not generate duplicate ids 5. Eventually stored in a UUID field in a database. So 128bit ids are totally fine. The IDs that Torid generates are 128bit IDs made up of 2, 64bit parts. * 64bit microsecond level UNIX timestamp * 64bit hash of the system hostname, process id and a random value.
When you have a project in which you are not using Mongoid::Timestamps and you want to mock an object's creation time, you have to do some cumbersome operations in order to get those first 4 bytes of the ObjectId to represent the seconds since the Unix epoch that you want for that object. Particularly, if you want to have two objects with the same creation time, it would not suffice to generate the IDs via the BSON::ObjectId.from_time method, since it would yield the same ID for both objects, and you probably do not want them to be seen as the same object. This gem solves this little annoying issue by generating a unique ID for the given timestamp by using the other 8 bytes in ObjectId to generate the needed additional entropy.
QA Robusta is an automation framework easing pain points away from automation test case writers. How is pain relieved? * Elements, such as links, buttons, and other html objects are defined in one location. This ensures over time the user won't have definitions spread out throughout different layers of code requiring time consuming updates if the application under test is modified. * Well defined flows allows the user to have a common means for navigating and controlling interactions with the application under test. This takes all logic out of test classes and yields in higher more modular code re-use. * When an application requiring testing has the elements and flows implemented less code savy resources can easily add new test cases once trained on how to access the flows and elements. * When ever a link or button is clicked a screen shot is taken * Results are available under site/results directory in html format. Report includes the rdoc on a per test class method along with any screen shots taken. Example report: https://cyberconnect.biz/opensource/demo_results.html * Transparent remote Unix command execution leading to well defined interfaces for common task. For example, one may have a class defined specifically for RemoteUnixNetwork. This class would have methods such as, assign_ip, ifup, ifdown, etc. This class then would be able to perform these task on any remote Unix machine. * Executes the same on Windows or Linux/Unix environments. Developers have the freedom to develop on the platform of choice. * Mechanize extension: Allows the user to define a web application's page elements in a YAML format and provide navigation paths accessing the YAML structure to interact with the web application. Users can also perform direct http.post or any other mechanize functionality when defining state-full interfaces to hit a web application without going through a browser.
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.