A simulated bash environment with virtual filesystem
List of binary file extensions
List of text file extensions
Check if a file path is a binary file
Like which(1) unix command. Find the first instance of an executable in the PATH.
Run the Node.js binary no matter what
Detects if a file is binary in Node.js. Similar to Perl's -B.
Helper function to build binary assignment operator visitors
Cross-Platform Binary API
The linux x64 distribution of the Sentry CLI binary.
Utility to wait for a TCP port to open.
A node cli to control Firefox
Different binary search tree implementations, including a self-balancing one (AVL)
Conversion of JavaScript primitives to and from Buffer with binary order matching natural primitive order
> Rewrite a WASM binary
The Linux 64-bit binary for esbuild, a JavaScript bundler.
The linux arm64 distribution of the Sentry CLI binary.
High-performance JSON serialization library
The windows arm64 distribution of the Sentry CLI binary.
The darwin distribution of the Sentry CLI binary.
Check whether a binary version satisfies a semver range
Native bindings for Rollup
The linux x86 and ia32 distribution of the Sentry CLI binary.
The windows x86 and ia32 distribution of the Sentry CLI binary.
A Ruby frontend to the pdftk binary, including FDF and XFDF creation. Also works with the PDFTK Java port. Just pass your template and a hash of data to fill in.
Lazily loads large columns on demand. By default, does this for all TEXT (:text) and BLOB (:binary) columns, but a list of specific columns to load on demand can be given. This is useful to reduce the memory taken by Rails when loading a number of records that have large columns if those particular columns are actually not required most of the time. In this situation it can also greatly reduce the database query time because loading large BLOB/TEXT columns generally means seeking to other database pages since they are not stored wholly in the record's page itself. Although this plugin is mainly used for BLOB and TEXT columns, it will actually work on all types - and is just as useful for large string fields etc.
A simple gem to warn you if there is a string similar to an API key in any of your ruby files. As of now, it cannot read binary files and it gives trouble when dealing with files written in other languages. Just run 'warner' without the quotes in your working directory and it will search in that folder an every child of it for a string that looks like an API key
Implements a gateway server to allow barebone basic sensor components to report state change updates as simple via TCP/UDP ports without the 'overhead' of the HTTP protocol. A power sensor for example might just broadcast a four byte floating point binary number once every second to an UDP port or an arduino board sends a UDP datagram whenever a button is pushed. You get the idea, this is how to bring embedded devices into the world of HTTP and Javascript...
This Rails plugin provides serialization using Marshal in the same way Rails provides builtin serialization using YAML. You can register any kind object (not just arrays and hashes…). Be aware that Marshal defines a binary format, which may change in incoming Ruby releases and is currently not portable outside the Ruby scripting world. For a portable yet slower alternatives, you may try JSON or YML serializers.
Log2json lets you read, filter and send logs as JSON objects via Unix pipes. It is inspired by Logstash, and is meant to be compatible with it at the JSON event/record level so that it can easily work with Kibana. Reading logs is done via a shell script(eg, `tail`) running in its own process. You then configure(see the `syslog2json` or the `nginxlog2json` script for examples) and run your filters in Ruby using the `Log2Json` module and its contained helper classes. `Log2Json` reads from stdin the logs(one log record per line), parses the log lines into JSON records, and then serializes and writes the records to stdout, which then can be piped to another process for processing or sending it to somewhere else. Currently, Log2json ships with a `tail-log` script that can be run as the input process. It's the same as using the Linux `tail` utility with the `-v -F` options except that it also tracks the positions(as the numbers of lines read from the beginning of the files) in a few files in the file system so that if the input process is interrupted, it can continue reading from where it left off next time if the files had been followed. This feature is similar to the sincedb feature in Logstash's file input. Note: If you don't need the tracking feature(ie, you are fine with always tailling from the end of file with `-v -F -n0`), then you can just use the `tail` utility that comes with your Linux distribution.(Or more specifically, the `tail` from the GNU coreutils). Other versions of the `tail` utility may also work, but are not tested. The input protocol expected by Log2json is very simple and documented in the source code. ** The `tail-log` script uses a patched version of `tail` from the GNU coreutils package. A binary of the `tail` utility compiled for Ubuntu 12.04 LTS is included with the Log2json gem. If the binary doesn't work for your distribution, then you'll need to get GNU coreutils-8.13, apply the patch(it can be found in the src/ directory of the installed gem), and then replace the bin/tail binary in the directory of the installed gem with your version of the binary. ** P.S. If you know of a way to configure and compile ONLY the tail program in coreutils, please let me know! The reason I'm not building tail post gem installation is that it takes too long to configure && make because that actually builds every utilties in coreutils. For shipping logs to Redis, there's the `lines2redis` script that can be used as the output process in the pipe. For shipping logs from Redis to ElasticSearch, Log2json provides a `redis2es` script. Finally here's an example of Log2json in action: From a client machine: tail-log /var/log/{sys,mail}log /var/log/{kern,auth}.log | syslog2json | queue=jsonlogs \ flush_size=20 \ flush_interval=30 \ lines2redis host.to.redis.server 6379 0 # use redis DB 0 On the Redis server: redis_queue=jsonlogs redis2es host.to.es.server Resources that help writing log2json filters: - look at log2json.rb source and example filters - http://grokdebug.herokuapp.com/ - http://www.ruby-doc.org/stdlib-1.9.3/libdoc/date/rdoc/DateTime.html#method-i-strftime
== ABOUT A simple program and library to conjugate french verbs. Parses responses to requests to an online reference site. === Executable ConjugateFR comes with the executable binary +conjugatefr+. To view information about it's supported arguments, run conjugatefr --help === Custom Renderers To make a custom renderer, just type require conjugatefr/renderer and then make a class that extends +Renderer+. An example is as follows: require 'conjugatefr/renderer' class ExampleRenderer < Renderer def pre puts "This goes before the words." end def word (name, words) print "#{name}:" words.each do |word| print " #{word}" end end def post puts "This goes after the words." end def description; "Renders an example format."; end end # Add to the Renderers list (For CLI and other programs that use it.) $renderers["Example"] = ExampleRenderer.new To try this out, save it as +erend.rb+ and then run: conjugatefr -R ./erend.rb -r Example It will produce the output: This goes before the words. someword: someconjugation etc etc ... (more words will be here) This goes after the words. === The Library The library can be included with +require conjugatefr+. It includes the +ConjugateFR+ class.
Log2json lets you read, filter and send logs as JSON objects via Unix pipes. It is inspired by Logstash, and is meant to be compatible with it at the JSON event/record level so that it can easily work with Kibana. Reading logs is done via a shell script(eg, `tail`) running in its own process. You then configure(see the `syslog2json` or the `nginxlog2json` script for examples) and run your filters in Ruby using the `Log2Json` module and its contained helper classes. `Log2Json` reads from stdin the logs(one log record per line), parses the log lines into JSON records, and then serializes and writes the records to stdout, which then can be piped to another process for processing or sending it to somewhere else. Currently, Log2json ships with a `tail-log` script that can be run as the input process. It's the same as using the Linux `tail` utility with the `-v -F` options except that it also tracks the positions(as the numbers of lines read from the beginning of the files) in a few files in the file system so that if the input process is interrupted, it can continue reading from where it left off next time if the files had been followed. This feature is similar to the sincedb feature in Logstash's file input. Note: If you don't need the tracking feature(ie, you are fine with always tailling from the end of file with `-v -F -n0`), then you can just use the `tail` utility that comes with your Linux distribution.(Or more specifically, the `tail` from the GNU coreutils). Other versions of the `tail` utility may also work, but are not tested. The input protocol expected by Log2json is very simple and documented in the source code. ** The `tail-log` script uses a patched version of `tail` from the GNU coreutils package. A binary of the `tail` utility compiled for Ubuntu 12.04 LTS is included with the Log2json gem. If the binary doesn't work for your distribution, then you'll need to get GNU coreutils-8.13, apply the patch(it can be found in the src/ directory of the installed gem), and then replace the bin/tail binary in the directory of the installed gem with your version of the binary. ** P.S. If you know of a way to configure and compile ONLY the tail program in coreutils, please let me know! The reason I'm not building tail post gem installation is that it takes too long to configure && make because that actually builds every utilties in coreutils. For shipping logs to Redis, there's the `lines2redis` script that can be used as the output process in the pipe. For shipping logs from Redis to ElasticSearch, Log2json provides a `redis2es` script. Finally here's an example of Log2json in action: From a client machine: tail-log /var/log/{sys,mail}log /var/log/{kern,auth}.log | syslog2json | queue=jsonlogs \ flush_size=20 \ flush_interval=30 \ lines2redis host.to.redis.server 6379 0 # use redis DB 0 On the Redis server: redis_queue=jsonlogs redis2es host.to.es.server Resources that help writing log2json filters: - look at log2json.rb source and example filters - http://grokdebug.herokuapp.com/ - http://www.ruby-doc.org/stdlib-1.9.3/libdoc/date/rdoc/DateTime.html#method-i-strftime
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.