[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-7974":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":16,"stars30d":17,"stars90d":16,"forks30d":16,"starsTrendScore":16,"compositeScore":18,"rankGlobal":10,"rankLanguage":10,"license":19,"archived":20,"fork":20,"defaultBranch":21,"hasWiki":20,"hasPages":22,"topics":23,"createdAt":10,"pushedAt":10,"updatedAt":26,"readmeContent":27,"aiSummary":28,"trendingCount":16,"starSnapshotCount":16,"syncStatus":29,"lastSyncTime":30,"discoverSource":31},7974,"async","socketry\u002Fasync","socketry","An awesome asynchronous event-driven reactor for Ruby.","",null,"Ruby",2445,106,32,19,0,7,58.79,"MIT License",false,"main",true,[5,24,25],"asynchronous","ruby","2026-06-12 04:00:36","# ![Async](assets\u002Flogo.webp)\n\nAsync is a composable asynchronous I\u002FO framework for Ruby based on [io-event](https:\u002F\u002Fgithub.com\u002Fsocketry\u002Fio-event).\n\n> \"Lately I've been looking into `async`, as one of my projects –\n> [tus-ruby-server](https:\u002F\u002Fgithub.com\u002Fjanko\u002Ftus-ruby-server) – would really benefit from non-blocking I\u002FO. It's really\n> beautifully designed.\" *– [janko](https:\u002F\u002Fgithub.com\u002Fjanko)*\n\n[![Development Status](https:\u002F\u002Fgithub.com\u002Fsocketry\u002Fasync\u002Fworkflows\u002FTest\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fsocketry\u002Fasync\u002Factions?workflow=Test)\n\n## Features\n\n  - Scalable event-driven I\u002FO for Ruby. Thousands of clients per process\\!\n  - Light weight fiber-based concurrency. No need for callbacks\\!\n  - Multi-thread\u002Fprocess containers for parallelism.\n  - Growing eco-system of event-driven components.\n\n## Usage\n\nPlease see the [project documentation](https:\u002F\u002Fsocketry.github.io\u002Fasync\u002F) for more details.\n\n  - [Getting Started](https:\u002F\u002Fsocketry.github.io\u002Fasync\u002Fguides\u002Fgetting-started\u002Findex) - This guide shows how to add async to your project and run code asynchronously.\n\n  - [Scheduler](https:\u002F\u002Fsocketry.github.io\u002Fasync\u002Fguides\u002Fscheduler\u002Findex) - This guide gives an overview of how the scheduler is implemented.\n\n  - [Tasks](https:\u002F\u002Fsocketry.github.io\u002Fasync\u002Fguides\u002Ftasks\u002Findex) - This guide explains how asynchronous tasks work and how to use them.\n\n  - [Best Practices](https:\u002F\u002Fsocketry.github.io\u002Fasync\u002Fguides\u002Fbest-practices\u002Findex) - This guide gives an overview of best practices for using Async.\n\n  - [Debugging](https:\u002F\u002Fsocketry.github.io\u002Fasync\u002Fguides\u002Fdebugging\u002Findex) - This guide explains how to debug issues with programs that use Async.\n\n  - [Thread safety](https:\u002F\u002Fsocketry.github.io\u002Fasync\u002Fguides\u002Fthread-safety\u002Findex) - This guide explains thread safety in Ruby, focusing on fibers and threads, common pitfalls, and best practices to avoid problems like data corruption, race conditions, and deadlocks.\n\n## Releases\n\nPlease see the [project releases](https:\u002F\u002Fsocketry.github.io\u002Fasync\u002Freleases\u002Findex) for all releases.\n\n### v2.39.0\n\n  - `Async::Barrier#wait` now returns the number of tasks that were waited for, or `nil` if there were no tasks to wait for. This provides better feedback about the operation, and allows you to know how many tasks were involved in the wait.\n\n### v2.38.1\n\n  - Fix `Barrier#async` when `parent.async` yields before the child block executes. Previously, `Barrier#wait` could return early and miss tracking the task entirely, because the task had not yet appended itself to the barrier's task list.\n\n### v2.38.0\n\n  - Rename `Task#stop` to `Task#cancel` for better clarity and consistency with common concurrency terminology. The old `stop` method is still available as an alias for backward compatibility, but it is recommended to use `cancel` going forward.\n  - Forward arguments from `Task#wait` -\\> `Promise#wait`, so `task.wait(timeout: N)` is supported.\n\n### v2.37.0\n\n  - Introduce `Async::Loop` for robust, time-aligned loops.\n  - Add support for `Async::Promise#wait(timeout: N)`.\n\n### v2.36.0\n\n  - Introduce `Task#wait_all` which recursively waits for all children and self, excepting the current task.\n  - Introduce `Task#join` as an alias for `Task#wait` for compatibility with `Thread#join` and similar interfaces.\n\n### v2.35.3\n\n  - `Async::Clock` now implements `#as_json` and `#to_json` for nicer log formatting.\n\n### v2.35.2\n\n  - Improved handling of `Process.fork` on Ruby 4+.\n  - Improve `@promise` state handling in `Task#initialize`, preventing incomplete instances being visible to the scheduler.\n\n### v2.35.1\n\n  - Fix incorrect handling of spurious wakeups in `Async::Promise#wait`, which could lead to premature (incorrect) resolution of the promise.\n\n### v2.35.0\n\n  - `Process.fork` is now properly handled by the Async fiber scheduler, ensuring that the scheduler state is correctly reset in the child process after a fork. This prevents issues where the child process inherits the scheduler state from the parent, which could lead to unexpected behavior.\n\n### v2.34.0\n\n  - [`Kernel::Barrier` Convenience Interface](https:\u002F\u002Fsocketry.github.io\u002Fasync\u002Freleases\u002Findex#kernel::barrier-convenience-interface)\n\n## See Also\n\n  - [async-http](https:\u002F\u002Fgithub.com\u002Fsocketry\u002Fasync-http) — Asynchronous HTTP client\u002Fserver.\n  - [falcon](https:\u002F\u002Fgithub.com\u002Fsocketry\u002Ffalcon) — A rack compatible server built on top of `async-http`.\n  - [async-websocket](https:\u002F\u002Fgithub.com\u002Fsocketry\u002Fasync-websocket) — Asynchronous client and server websockets.\n  - [async-dns](https:\u002F\u002Fgithub.com\u002Fsocketry\u002Fasync-dns) — Asynchronous DNS resolver and server.\n  - [toolbox](https:\u002F\u002Fgithub.com\u002Fsocketry\u002Ftoolbox) — GDB & LLDB extensions for debugging Ruby applications with Fibers.\n\n## Contributing\n\nWe welcome contributions to this project.\n\n1.  Fork it.\n2.  Create your feature branch (`git checkout -b my-new-feature`).\n3.  Commit your changes (`git commit -am 'Add some feature'`).\n4.  Push to the branch (`git push origin my-new-feature`).\n5.  Create new Pull Request.\n\n### Developer Certificate of Origin\n\nIn order to protect users of this project, we require all contributors to comply with the [Developer Certificate of Origin](https:\u002F\u002Fdevelopercertificate.org\u002F). This ensures that all contributions are properly licensed and attributed.\n\n### Community Guidelines\n\nThis project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.\n","Async 是一个基于 Ruby 的可组合异步 I\u002FO 框架。它利用轻量级的 fiber 实现并发，无需回调，并支持多线程\u002F多进程容器以实现并行处理。其核心功能包括可扩展的事件驱动 I\u002FO，能够在一个进程中处理数千个客户端连接。该项目设计优雅，适用于需要非阻塞 I\u002FO 的场景，如高并发 Web 服务器、实时应用等。随着生态系统的不断扩展，Async 提供了丰富的事件驱动组件，帮助开发者构建高效、响应迅速的应用程序。",2,"2026-06-11 03:15:26","top_language"]