Octokit
Polyphony
Our great sponsors
Octokit | Polyphony | |
---|---|---|
4 | 22 | |
3,817 | 651 | |
0.2% | 0.3% | |
8.4 | 8.3 | |
2 days ago | about 1 month ago | |
Ruby | C | |
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.
Octokit
-
Automate GitHub API Calls With Ruby, Keyboard Maestro, and 1Password CLI
After extracting the GitHub username from the Paddle payload, I would use the octokit gem to add the customer as a read-only collaborator to the repo. Something like this:
-
Lazy Load Form Fields In Rails Using StimulusReflex
Some important things in this reflex. One, since our partial requires a form object, we use ActionView::Helpers::FormBuilder to create a form for a user building an initial repository. Since it requires a view_context, we leverage a delegate to access it from the controller. Two, the Octokit client requires a user authentication token, so we add delegate to the connection so we can access the current_user. Three, rather than triggering a full page morph, we instead can use a selector morph so it only updates the div with id #repositories.
-
I'm losing my mind on concurrency
Here's an example of doing that on octokit gem: https://github.com/octokit/octokit.rb#debugging
Polyphony
-
Should You Be Scared of Unix Signals?
When using green threads/fibers/coroutines, an interesting technique to make signal handling safer is to run the signal handler asynchronously on a separate fiber/green thread. That way most of the problems of dealing with signals go away, and there's basically no limitation on what you can do inside the signal handler.
I've successfully used this technique in Polyphony [1], a fiber-based Ruby gem for writing concurrent programs. When a signal occurs, Polyphony creates a special-purpose fiber that runs the signal handling code. The fiber is put at the head of the run queue, and is resumed once the currently executed fiber yields control.
[1] https://github.com/digital-fabric/polyphony
-
Polyphony 1.4 Released
Read the release notes here: https://github.com/orgs/digital-fabric/discussions/110 The Polyphony docs: https://www.rubydoc.info/gems/polyphony The Polyphony repository: https://github.com/digital-fabric/polyphony
- Polyphony: Fine-Grained Concurrency for Ruby
-
Polyphony 0.99 released. Last release before 1.0!
Polyphony is a gem for building highly-concurrent Ruby programs. It utilizes Ruby fibers to provide a high-performance safe environment for launching any number of concurrent operations. Under the hood, Polyphony employs io_uring to maximize I/O performance (libev is used on platforms other than recent Linux kernels).
- Polyphony – Fine-grained concurrency for Ruby
-
About that monkey-patching business...
Is monkey-patching inherently bad? Should its use make Polyphony illegitimate? These are the questions I'm exploring in my latest article.
-
Async Ruby
how is this diff from: https://github.com/digital-fabric/polyphony
-
Embracing Infinite Loops with Ruby and Polyphony
Infinite loops are great for expressing long-running concurrent operations. In this article I’ll discuss the use of infinite loops as a major construct when writing concurrent apps in Ruby using Polyphony. I’ll show how infinite loops differ from normal, finite ones; how they can be used to express long-running tasks in a concurrent environment; and how they can be stopped. Read it now!
-
What's new in Polyphony and Tipi - August 2021 edition
Polyphony is a library for writing highly concurrent Ruby apps. Polyphony harnesses Ruby fibers and a powerful io_uring-based I/O runtime to provide a solid foundation for building high-performance concurrent Ruby apps.
-
Sorbet Compiler: An experimental, ahead-of-time compiler for Ruby
> Curious if there’s anything public about improving ruby performance from the I/O angle mentioned in the post.
I'm currently working on Polyphony [0], a Ruby gem for writing highly-concurrent Ruby apps. It uses Ruby fibers under the hood, and does I/O using io_uring (on Linux, there is also a libev-based backend).
[0] https://github.com/digital-fabric/polyphony
What are some alternatives?
gitlab - Ruby wrapper and CLI for the GitLab REST API
Async Ruby - An awesome asynchronous event-driven reactor for Ruby.
Slack ruby gem
Concurrent Ruby - Modern concurrency tools including agents, futures, promises, thread pools, supervisors, and more. Inspired by Erlang, Clojure, Scala, Go, Java, JavaScript, and classic concurrency patterns.
google-api-ads-ruby - Ad Manager SOAP API Client Libraries for Ruby
EventMachine - EventMachine: fast, simple event-processing library for Ruby programs
twitter - A Ruby interface to the Twitter API.
Celluloid - Actor-based concurrent object framework for Ruby
redd - Redd is a batteries-included API wrapper for reddit.
render_async - render_async lets you include pages asynchronously with AJAX
ruby-trello - Implementation of the Trello API for Ruby
Opal-Async - Non-blocking tasks and enumerators for Opal.