From b1a44f1de65135a14d3f1088875879b5163caee1 Mon Sep 17 00:00:00 2001 From: Ahmed Alaa <92916738+ahmedalaa4611@users.noreply.github.com> Date: Wed, 3 Sep 2025 19:55:10 +0300 Subject: [PATCH 1/3] Update cache.md --- cache.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cache.md b/cache.md index 1635c8f6b7..bc74a3b85d 100644 --- a/cache.md +++ b/cache.md @@ -237,7 +237,7 @@ $value = Cache::rememberForever('users', function () { When using the `Cache::remember` method, some users may experience slow response times if the cached value has expired. For certain types of data, it can be useful to allow partially stale data to be served while the cached value is recalculated in the background, preventing some users from experiencing slow response times while cached values are calculated. This is often referred to as the "stale-while-revalidate" pattern, and the `Cache::flexible` method provides an implementation of this pattern. -The flexible method accepts an array that specifies how long the cached value is considered "fresh" and when it becomes "stale." The first value in the array represents the number of seconds the cache is considered fresh, while the second value defines how long it can be served as stale data before recalculation is necessary. +The flexible method accepts an array that specifies how long the cached value is considered "fresh" and when it becomes "stale". The first value in the array represents the number of seconds the cache is considered fresh, while the second value defines how long it can be served as stale data before recalculation is necessary. If a request is made within the fresh period (before the first value), the cache is returned immediately without recalculation. If a request is made during the stale period (between the two values), the stale value is served to the user, and a [deferred function](/docs/{{version}}/helpers#deferred-functions) is registered to refresh the cached value after the response is sent to the user. If a request is made after the second value, the cache is considered expired, and the value is recalculated immediately, which may result in a slower response for the user: From 3cd2e0b1bdd901869562ee66d200b1038de279f4 Mon Sep 17 00:00:00 2001 From: Ahmed Alaa <92916738+ahmedalaa4611@users.noreply.github.com> Date: Wed, 3 Sep 2025 19:56:09 +0300 Subject: [PATCH 2/3] Update horizon.md --- horizon.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/horizon.md b/horizon.md index beb24a88e4..a181fe8389 100644 --- a/horizon.md +++ b/horizon.md @@ -200,7 +200,7 @@ Similarly, you can set a `timeout` value at the supervisor level, which specifie ``` > [!WARNING] -> When using the `auto` balancing strategy, Horizon will consider in-progress workers as "hanging" and force-kill them after the Horizon timeout during scale down. Always ensure the Horizon timeout is greater than any job-level timeout, otherwise jobs may be terminated mid-execution. In addition, the `timeout` value should always be at least a few seconds shorter than the `retry_after` value defined in your `config/queue.php` configuration file. Otherwise, your jobs may be processed twice. +> When using the `auto` balancing strategy, Horizon will consider in-progress workers as "hanging" and force-kill them after the Horizon timeout during scale down. Always ensure the Horizon timeout is greater than any job-level timeout, otherwise jobs may be terminated mid-execution. In addition, the `timeout` value should always be at least a few seconds shorter than the `retry_after` value defined in your `config/queue.php` configuration file. Otherwise, your jobs may be processed twice. ### Job Backoff @@ -535,7 +535,7 @@ sudo supervisorctl start horizon ## Tags -Horizon allows you to assign "tags" to jobs, including mailables, broadcast events, notifications, and queued event listeners. In fact, Horizon will intelligently and automatically tag most jobs depending on the Eloquent models that are attached to the job. For example, take a look at the following job: +Horizon allows you to assign "tags" to jobs, including mailables, broadcast events, notifications, and queued event listeners. In fact, Horizon will intelligently and automatically tag most jobs depending on the Eloquent models that are attached to the job. For example, take a look at the following job: ```php Date: Wed, 3 Sep 2025 19:56:51 +0300 Subject: [PATCH 3/3] Update dusk.md --- dusk.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dusk.md b/dusk.md index e05d4788b9..24c73b5425 100644 --- a/dusk.md +++ b/dusk.md @@ -2392,7 +2392,7 @@ $browser->visit(new Dashboard) ## Components -Components are similar to Dusk's "page objects", but are intended for pieces of UI and functionality that are re-used throughout your application, such as a navigation bar or notification window. As such, components are not bound to specific URLs. +Components are similar to Dusk's "page objects", but are intended for pieces of UI and functionality that are re-used throughout your application, such as a navigation bar or notification window. As such, components are not bound to specific URLs. ### Generating Components

AltStyle によって変換されたページ (->オリジナル) /