Skip to content

armgit / laya

Public Imported from GitHub
0

Non-autoregressive System 1 decision engine. Typed choice, score and yes/no decisions over any text in a single forward pass, in 100+ languages, with a router that picks the right checkpoint per request.

ci: two parity cells at a time, not one; the guard is the half that matters

Adeshina Lasisib7cc4dab56d5
diff --git a/.github/workflows/dotnet.yml b/.github/workflows/dotnet.yml
index 9042e251..83adc68d 100644
--- a/.github/workflows/dotnet.yml
+++ b/.github/workflows/dotnet.yml
@@ -117,7 +117,15 @@ jobs:
# incomplete snapshot at the fetch, so this is no longer the only thing between a
# truncated download and a confusing failure; not provoking the throttle is simply
# cheaper than diagnosing it, and this lane is advisory.
- max-parallel: 1
+ #
+ # TWO, not one. One was the first attempt and it cost too much: measured from this PR's own
+ # cells, serialising takes the parity critical path from 10:56 to 30:08. Two keeps the peak
+ # well below the seven concurrent fetches that provoked the throttle while costing roughly
+ # half of that. And serialising is no longer the load-bearing half of the fix -- the
+ # download sites now refuse an incomplete snapshot AT THE FETCH, naming the file, so a
+ # throttled fetch fails immediately and legibly instead of three minutes later inside a
+ # tokenizer constructor. This only reduces how often that path is taken.
+ max-parallel: 2
matrix:
include:
- name: english
diff --git a/.github/workflows/java.yml b/.github/workflows/java.yml
index 8b9e509f..1182858b 100644
--- a/.github/workflows/java.yml
+++ b/.github/workflows/java.yml
@@ -410,7 +410,15 @@ jobs:
# 0-byte or unparseable one -- and the fetching step carries `HF_TOKEN` so the higher rate
# limit applies where the secret exists. The guard is what matters; not provoking the
# throttle is merely cheaper than diagnosing it.
- max-parallel: 1
+ #
+ # TWO, not one. One was the first attempt and it cost too much: measured from this PR's own
+ # cells, serialising takes the parity critical path from 10:56 to 30:08. Two keeps the peak
+ # well below the seven concurrent fetches that provoked the throttle while costing roughly
+ # half of that. And serialising is no longer the load-bearing half of the fix -- the
+ # download sites now refuse an incomplete snapshot AT THE FETCH, naming the file, so a
+ # throttled fetch fails immediately and legibly instead of three minutes later inside a
+ # tokenizer constructor. This only reduces how often that path is taken.
+ max-parallel: 2
matrix:
include:
# Tokenizers and configs only -- no weights, nothing traced. The three families here