munola 0.5.1 → 0.5.2
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 +35 -0
- data/lib/munola/providers_config.rb +4 -1
- data/lib/munola/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: 634f7369a35be4b04097f3539bdf6c41b0419836242450170c07d0937de85c76
|
|
4
|
+
data.tar.gz: 916ec77f29fefc76fabb0229c10078677ba01407d02fa02e71dd6973933961a2
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 044d6b03723fe94d321d1024927e9691c82cdf5a763aecd9a64709b6c4e6ffab4cb92b1555a15e812e7647b496cd1852f7d5dfb7cb3e470a789a64b0851be7f5
|
|
7
|
+
data.tar.gz: 2dc4d4e98eb5d60d948913b0dd3c69bb93077f372e76b4eddc11e2d5f96091cf7e32c7c9ded1759c1e5b96f6d5783d11a87459bea58f95cf43d874b866b2c56d
|
data/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,38 @@
|
|
|
1
|
+
## enola 0.5.2, enola-rb 0.5.2, munola 0.5.2 and munola-rb 0.5.2 (2026-08-23)
|
|
2
|
+
|
|
3
|
+
Rubydex is off in the config these gems write, and named in a comment beside
|
|
4
|
+
the reason. The release each gem drives carries a walk that can fail to
|
|
5
|
+
return: a constant reference spanning lines could be treated as its own
|
|
6
|
+
predecessor, so a tree with vendored gems could snapshot for twenty-six
|
|
7
|
+
minutes and several gigabytes without finishing. Two of the three Rails trees
|
|
8
|
+
it was tried on did exactly that.
|
|
9
|
+
|
|
10
|
+
The fix exists and is not yet in a published enola, so the default cannot
|
|
11
|
+
depend on it. Prism is unaffected and stays on: it parses a monolith in 13.7
|
|
12
|
+
seconds. Uncommenting the two lines brings Rubydex back for anyone who wants
|
|
13
|
+
it deliberately, and the default returns the moment the binary each gem drives
|
|
14
|
+
carries the fix.
|
|
15
|
+
|
|
16
|
+
## enola 0.5.1 (2026-08-23)
|
|
17
|
+
|
|
18
|
+
The resolver no longer probes its own binstub. It read a candidate's first 512
|
|
19
|
+
bytes looking for the marker RubyGems writes, and a real binstub carries a
|
|
20
|
+
`/bin/sh` + `ruby -x` preamble holding the interpreter's absolute path, which puts
|
|
21
|
+
that marker around byte 580 — outside the window. So the guard missed every
|
|
22
|
+
RubyGems-generated binstub, the wrapper ran itself, and running itself has no
|
|
23
|
+
bottom: `enola --version` on a cold cache spawned Ruby processes until it was
|
|
24
|
+
killed. The whole file is read now, capped at 64 KiB so a released binary is never
|
|
25
|
+
slurped only to be rejected, and `Gem.bin_path` is recognised beside
|
|
26
|
+
`Gem.activate_bin_path`. A probe also marks its child's environment, and a resolver
|
|
27
|
+
that sees the marker declines to look at PATH at all, so the recursion is bounded
|
|
28
|
+
by construction rather than by how well a heuristic reads a file.
|
|
29
|
+
|
|
30
|
+
The marker is written where it is spawned: every probe passes it into the child,
|
|
31
|
+
so a wrapper reached under another name leaves PATH alone instead of probing in
|
|
32
|
+
turn. That bound is what covers the wrappers the content check cannot see, a
|
|
33
|
+
version manager's shim among them, which carries none of the markers a binstub
|
|
34
|
+
does. Reported and fixed by dejo1307 in #1.
|
|
35
|
+
|
|
1
36
|
## munola 0.4.4.2 and munola-rb 0.4.4.2 (2026-08-23)
|
|
2
37
|
|
|
3
38
|
munola follows the channel it drives. Its binary is now cut from the stable
|
|
@@ -27,7 +27,10 @@ module Munola
|
|
|
27
27
|
else
|
|
28
28
|
lines << " # prism: the enola gem on this machine carries no provider script; add one here to run it"
|
|
29
29
|
end
|
|
30
|
-
lines += ["
|
|
30
|
+
lines += [" # rubydex is off until the channel release carries the walk fix:",
|
|
31
|
+
" # a reference spanning lines could be its own predecessor, so a tree with",
|
|
32
|
+
" # vendored gems could snapshot without ever finishing. Uncomment to run it.",
|
|
33
|
+
" # - name: rubydex", " # expected_version: \"#{RUBYDEX_VERSION}\""]
|
|
31
34
|
"#{lines.join("\n")}\n"
|
|
32
35
|
end
|
|
33
36
|
|
data/lib/munola/version.rb
CHANGED