mcptask-rails-runner 0.3.19 → 0.3.21
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
- data/CHANGELOG.md +77 -1
- data/lib/mcptask_rails_runner/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 1a16efd850f25eb14fe6e39f4add7e8745f936902de1fdb02232a43d6c8856b7
|
|
4
|
+
data.tar.gz: d95a764a4de48c021d9e0326fe6238ed9e948ca1d1dd5b4f33a9990b12d3ddf7
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: ac0b2f59414b13a490e6fede3b5456cbd358c4988d6767b5aa083404fb105ba24f7629302e3c1f9a197561406514b65efa8c7d63465409be2381e6b0a41ec458
|
|
7
|
+
data.tar.gz: 051244f93e212c6f3d07c406e917689a41ea8216be09f9e5af6e56b5fd88016e82223a59c3b6e8074abd7bc6954326f97fb7002a9f74663c28b0292f2ddb88c6
|
data/CHANGELOG.md
CHANGED
|
@@ -5,7 +5,83 @@ entries below describe wrapper changes only. Binary changes are listed in the
|
|
|
5
5
|
[mcptask-releases](https://github.com/jchsoft/mcptask-releases/releases)
|
|
6
6
|
release notes for the same tag.
|
|
7
7
|
|
|
8
|
-
##
|
|
8
|
+
## 0.3.21
|
|
9
|
+
|
|
10
|
+
No wrapper changes. Full notes in
|
|
11
|
+
[mcptask-releases v0.3.21](https://github.com/jchsoft/mcptask-releases/releases/tag/v0.3.21).
|
|
12
|
+
|
|
13
|
+
**Upgrading:** run `mcptask_runner update --self` on each host. Both changes are
|
|
14
|
+
binary behaviour, and the first of them only stops costing you a working day
|
|
15
|
+
once the host is actually running the new binary.
|
|
16
|
+
|
|
17
|
+
Binary changes carried by this version:
|
|
18
|
+
|
|
19
|
+
- A deploy of mcptask.online now costs one attempt instead of the working day.
|
|
20
|
+
While the site is being deployed the MCP server is unreachable for minutes and
|
|
21
|
+
then comes back by itself. The runner used to spend its entire recovery budget
|
|
22
|
+
inside about forty seconds — a child dies in ten, five seconds between
|
|
23
|
+
restarts, two restarts — so all three attempts lost the same race before the
|
|
24
|
+
server could possibly be back, and the run ended with `error`. That status is
|
|
25
|
+
what ends the day, so one deploy could end a day that had already completed
|
|
26
|
+
eighteen tasks.
|
|
27
|
+
|
|
28
|
+
The two situations that reach that path are now told apart where they are
|
|
29
|
+
detected, rather than by reading the message afterwards. A deferred tool that
|
|
30
|
+
never loaded is the child's own miss: it keeps its two fast restarts and still
|
|
31
|
+
ends in an error, because it is not going to fix itself. An outage gets six
|
|
32
|
+
restarts at twelve times the wait — about six minutes, which spans a deploy —
|
|
33
|
+
and when that runs out it ends the way a stall does: a verdict the loop
|
|
34
|
+
carries on from, the task left `in_progress` for the next triage, and no bug
|
|
35
|
+
piece, because a deploy is not a defect anybody can fix. The wait keeps the
|
|
36
|
+
heartbeat going, so a card watched through a deploy says the runner is waiting
|
|
37
|
+
rather than falling silent.
|
|
38
|
+
|
|
39
|
+
Like every binary fix, it reaches a host only once that host runs the new
|
|
40
|
+
binary — `mcptask_runner update --self` — and until then a deploy goes on
|
|
41
|
+
costing the day.
|
|
42
|
+
|
|
43
|
+
- Today's skip list is visible. A task the runner has set aside — out of scope,
|
|
44
|
+
failed, already taken by somebody else, a merge it cannot finish — is skipped
|
|
45
|
+
by every later triage that day, and until now the only trace of that decision
|
|
46
|
+
was one line in the log at the moment it was made. It now shows on the startup
|
|
47
|
+
banner, in every wait, and on the dashboard card, so an operator looking at a
|
|
48
|
+
quiet runner can see what it has already declined rather than wondering why a
|
|
49
|
+
piece keeps not being picked up.
|
|
50
|
+
|
|
51
|
+
## 0.3.20
|
|
52
|
+
|
|
53
|
+
No wrapper changes. Full notes in
|
|
54
|
+
[mcptask-releases v0.3.20](https://github.com/jchsoft/mcptask-releases/releases/tag/v0.3.20).
|
|
55
|
+
|
|
56
|
+
**Upgrading:** run `mcptask_runner update --self` on each host, and do it for
|
|
57
|
+
this one rather than at leisure — the fix below can only reach a runner that is
|
|
58
|
+
running the new binary, and the situation it fixes keeps happening until then. A
|
|
59
|
+
daily process picks the new copy up at its night swap, but only once that copy
|
|
60
|
+
is on disk. The project bump alone still changes nothing about what the 08:00
|
|
61
|
+
job runs.
|
|
62
|
+
|
|
63
|
+
Binary changes carried by this version:
|
|
64
|
+
|
|
65
|
+
- A piece assigned to somebody else while this runner is working it now stops
|
|
66
|
+
the child, instead of being worked to the end by a runner it no longer belongs
|
|
67
|
+
to. The dashboard socket has always carried both halves of an assignment —
|
|
68
|
+
"given to you" cut an idle wait short, and "given to somebody else" reached
|
|
69
|
+
nothing — so a task moved between two agents was picked up by its new owner
|
|
70
|
+
while its old one carried on: two agents on one piece, the same branch name
|
|
71
|
+
pushed twice, two sets of efforts logged. The runner now abandons the piece,
|
|
72
|
+
says so, and goes back to the queue for one that is still its own. It is not a
|
|
73
|
+
reason to stop the day, and the piece is deliberately not set aside: the queue
|
|
74
|
+
has already stopped offering it, and it stays workable if it is handed back.
|
|
75
|
+
- The run log is coloured as it is read, and the file itself stays plain. The
|
|
76
|
+
two lines that matter in a wall of uniform text — the ones `Warn` and `Error`
|
|
77
|
+
already mark with a glyph — are painted red and yellow, a child's stderr is
|
|
78
|
+
yellow, and the `[Component]` tags, cost lines and phase separators are dimmed
|
|
79
|
+
so the shape of a run is visible in a scroll. Only what the runner itself
|
|
80
|
+
marked is coloured; guessing a severity from the wording would be wrong on the
|
|
81
|
+
day it mattered. Nothing is written to the file, which is what bug reports
|
|
82
|
+
attach and what people grep. `runner-log --paint` is the same filter over
|
|
83
|
+
stdin, so `tail -f any.log | runner-log --paint` works for a log read some
|
|
84
|
+
other way.
|
|
9
85
|
|
|
10
86
|
## 0.3.19
|
|
11
87
|
|
|
@@ -10,5 +10,5 @@ module McptaskRailsRunner
|
|
|
10
10
|
# Binary::INSTALL_DIR. So the pin is per project and per foreground rake
|
|
11
11
|
# invocation; the installed copy is per machine, and the newest binary any of
|
|
12
12
|
# those projects offers is the one that stays.
|
|
13
|
-
VERSION = "0.3.
|
|
13
|
+
VERSION = "0.3.21"
|
|
14
14
|
end
|