async-service 0.14.1 → 0.14.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- checksums.yaml.gz.sig +0 -0
- data/lib/async/service/container_environment.rb +3 -0
- data/lib/async/service/environment.rb +1 -1
- data/lib/async/service/formatting.rb +2 -2
- data/lib/async/service/version.rb +1 -1
- data.tar.gz.sig +0 -0
- metadata +1 -2
- metadata.gz.sig +0 -0
- data/agent.md +0 -129
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 5bf58f1f4d3360157f75523fe3d56436342b11525030576ad126f45c8f56a370
|
4
|
+
data.tar.gz: 7d533968b6ac28f46286975da289038fd2ef780b23490b98257f32d061287ed3
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: '02199ca643a1a5b835f24cee99a465007af16d657af0b698839970b95a1a27aa436ee9ea82632865926627f060b101159224128a0f66bdac235c2cd8e485a27c'
|
7
|
+
data.tar.gz: 62be7258148f98eb823efa015a98f4beef5ac9fa05763ec364cb1b9b006710eeb38c9c08a7508b7a0875de00fc64de54f82e482e830de0928916fb1a6cc9bba8
|
checksums.yaml.gz.sig
CHANGED
Binary file
|
@@ -18,7 +18,7 @@ module Async
|
|
18
18
|
# @parameter units [Array] The units to use for formatting (default: UNITS).
|
19
19
|
# @returns [String] A formatted string representing the count.
|
20
20
|
def format_count(value, units = UNITS)
|
21
|
-
value = value
|
21
|
+
value = value
|
22
22
|
index = 0
|
23
23
|
limit = units.size - 1
|
24
24
|
|
@@ -27,7 +27,7 @@ module Async
|
|
27
27
|
value = value.abs
|
28
28
|
|
29
29
|
while value >= 1000 and index < limit
|
30
|
-
value = value / 1000
|
30
|
+
value = value / 1000.0
|
31
31
|
index += 1
|
32
32
|
end
|
33
33
|
|
data.tar.gz.sig
CHANGED
Binary file
|
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: async-service
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.14.
|
4
|
+
version: 0.14.3
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Samuel Williams
|
@@ -71,7 +71,6 @@ executables:
|
|
71
71
|
extensions: []
|
72
72
|
extra_rdoc_files: []
|
73
73
|
files:
|
74
|
-
- agent.md
|
75
74
|
- bin/async-service
|
76
75
|
- context/best-practices.md
|
77
76
|
- context/getting-started.md
|
metadata.gz.sig
CHANGED
Binary file
|
data/agent.md
DELETED
@@ -1,129 +0,0 @@
|
|
1
|
-
# Agent
|
2
|
-
|
3
|
-
## Context
|
4
|
-
|
5
|
-
This section provides links to documentation from installed packages. It is automatically generated and may be updated by running `bake agent:context:install`.
|
6
|
-
|
7
|
-
**Important:** Before performing any code, documentation, or analysis tasks, always read and apply the full content of any relevant documentation referenced in the following sections. These context files contain authoritative standards and best practices for documentation, code style, and project-specific workflows. **Do not proceed with any actions until you have read and incorporated the guidance from relevant context files.**
|
8
|
-
|
9
|
-
**Setup Instructions:** If the referenced files are not present or if dependencies have been updated, run `bake agent:context:install` to install the latest context files.
|
10
|
-
|
11
|
-
### agent-context
|
12
|
-
|
13
|
-
Install and manage context files from Ruby gems.
|
14
|
-
|
15
|
-
#### [Getting Started](.context/agent-context/getting-started.md)
|
16
|
-
|
17
|
-
This guide explains how to use `agent-context`, a tool for discovering and installing contextual information from Ruby gems to help AI agents.
|
18
|
-
|
19
|
-
### async
|
20
|
-
|
21
|
-
A concurrency framework for Ruby.
|
22
|
-
|
23
|
-
#### [Getting Started](.context/async/getting-started.md)
|
24
|
-
|
25
|
-
This guide shows how to add async to your project and run code asynchronously.
|
26
|
-
|
27
|
-
#### [Scheduler](.context/async/scheduler.md)
|
28
|
-
|
29
|
-
This guide gives an overview of how the scheduler is implemented.
|
30
|
-
|
31
|
-
#### [Tasks](.context/async/tasks.md)
|
32
|
-
|
33
|
-
This guide explains how asynchronous tasks work and how to use them.
|
34
|
-
|
35
|
-
#### [Best Practices](.context/async/best-practices.md)
|
36
|
-
|
37
|
-
This guide gives an overview of best practices for using Async.
|
38
|
-
|
39
|
-
#### [Debugging](.context/async/debugging.md)
|
40
|
-
|
41
|
-
This guide explains how to debug issues with programs that use Async.
|
42
|
-
|
43
|
-
#### [Thread safety](.context/async/thread-safety.md)
|
44
|
-
|
45
|
-
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.
|
46
|
-
|
47
|
-
### decode
|
48
|
-
|
49
|
-
Code analysis for documentation generation.
|
50
|
-
|
51
|
-
#### [Getting Started with Decode](.context/decode/getting-started.md)
|
52
|
-
|
53
|
-
The Decode gem provides programmatic access to Ruby code structure and metadata. It can parse Ruby files and extract definitions, comments, and documentation pragmas, enabling code analysis, documentation generation, and other programmatic manipulations of Ruby codebases.
|
54
|
-
|
55
|
-
#### [Documentation Coverage](.context/decode/coverage.md)
|
56
|
-
|
57
|
-
This guide explains how to test and monitor documentation coverage in your Ruby projects using the Decode gem's built-in bake tasks.
|
58
|
-
|
59
|
-
#### [Ruby Documentation](.context/decode/ruby-documentation.md)
|
60
|
-
|
61
|
-
This guide covers documentation practices and pragmas supported by the Decode gem for documenting Ruby code. These pragmas provide structured documentation that can be parsed and used to generate API documentation and achieve complete documentation coverage.
|
62
|
-
|
63
|
-
#### [Setting Up RBS Types and Steep Type Checking for Ruby Gems](.context/decode/types.md)
|
64
|
-
|
65
|
-
This guide covers the process for establishing robust type checking in Ruby gems using RBS and Steep, focusing on automated generation from source documentation and proper validation.
|
66
|
-
|
67
|
-
### falcon
|
68
|
-
|
69
|
-
A fast, asynchronous, rack-compatible web server.
|
70
|
-
|
71
|
-
#### [Getting Started](.context/falcon/getting-started.md)
|
72
|
-
|
73
|
-
This guide gives an overview of how to use Falcon for running Ruby web applications.
|
74
|
-
|
75
|
-
#### [Rails Integration](.context/falcon/rails-integration.md)
|
76
|
-
|
77
|
-
This guide explains how to host Rails applications with Falcon.
|
78
|
-
|
79
|
-
#### [Deployment](.context/falcon/deployment.md)
|
80
|
-
|
81
|
-
This guide explains how to deploy applications using the Falcon web server. It covers the recommended deployment methods, configuration options, and examples for different environments, including systemd and kubernetes.
|
82
|
-
|
83
|
-
#### [Performance Tuning](.context/falcon/performance-tuning.md)
|
84
|
-
|
85
|
-
This guide explains the performance characteristics of Falcon.
|
86
|
-
|
87
|
-
#### [WebSockets](.context/falcon/websockets.md)
|
88
|
-
|
89
|
-
This guide explains how to use WebSockets with Falcon.
|
90
|
-
|
91
|
-
#### [Interim Responses](.context/falcon/interim-responses.md)
|
92
|
-
|
93
|
-
This guide explains how to use interim responses in Falcon to send early hints to the client.
|
94
|
-
|
95
|
-
#### [How It Works](.context/falcon/how-it-works.md)
|
96
|
-
|
97
|
-
This guide gives an overview of how Falcon handles an incoming web request.
|
98
|
-
|
99
|
-
### sus
|
100
|
-
|
101
|
-
A fast and scalable test runner.
|
102
|
-
|
103
|
-
#### [Using Sus Testing Framework](.context/sus/usage.md)
|
104
|
-
|
105
|
-
Sus is a modern Ruby testing framework that provides a clean, BDD-style syntax for writing tests. It's designed to be fast, simple, and expressive.
|
106
|
-
|
107
|
-
#### [Mocking](.context/sus/mocking.md)
|
108
|
-
|
109
|
-
There are two types of mocking in sus: `receive` and `mock`. The `receive` matcher is a subset of full mocking and is used to set expectations on method calls, while `mock` can be used to replace method implementations or set up more complex behavior.
|
110
|
-
|
111
|
-
#### [Shared Test Behaviors and Fixtures](.context/sus/shared.md)
|
112
|
-
|
113
|
-
Sus provides shared test contexts which can be used to define common behaviours or tests that can be reused across one or more test files.
|
114
|
-
|
115
|
-
### utopia-project
|
116
|
-
|
117
|
-
A project documentation tool based on Utopia.
|
118
|
-
|
119
|
-
#### [Getting Started](.context/utopia-project/getting-started.md)
|
120
|
-
|
121
|
-
This guide explains how to use `utopia-project` to add documentation to your project.
|
122
|
-
|
123
|
-
#### [Documentation Guides](.context/utopia-project/documentation-guidelines.md)
|
124
|
-
|
125
|
-
This guide explains how to create and maintain documentation for your project using `utopia-project`.
|
126
|
-
|
127
|
-
#### [GitHub Pages Integration](.context/utopia-project/github-pages-integration.md)
|
128
|
-
|
129
|
-
This guide shows you how to use `utopia-project` with GitHub Pages to deploy documentation.
|