@RN
@ReturningNovice
@StormyCloud
@T3s|4
@T3s|4_
@orignal
@postman
@zzz
%acetone
%mareki2p
%snex
+Atticfire
+FreefallHeavens
+Onn4l7h
+Onn4|7h
+Over
+fa
+marek22k
+onon_
+poriori
+profetikla
+qend-irc2p
+r00tobo
+sexy
+uberius
+uop23ip
Arch
Danny
Irc2PGuest21708
Irc2PGuest28384
Irc2PGuest66257
Irc2PGuest75631
Irc2PGuest99986
RTP_
U1F642
Watson
ahiru
anontor
cims
i2potus
interesting
justaperson
lokzz
luvme
mahlay
makoto
n2_
nilbog
not_bob_afk
pinotto
r00tobo[2]
rednode
user_ygg2__
dr|z3d
sounds good. feel free to send over a merge request if you update the docs.
y2kboy23
will do.
T3s|4
o/ dr|z3d - is it possible for a + update to break the wrapper script - or is/was that problem on my end only? iirc, you pushed 3 updates earlier today, and I after restarting into the second one, my wrapper was hosed. However, this only happened on one of my 2 laptops. Both rigs have been running: java-19-openjdk (default) for months without issue
dr|z3d
T3s|4_: not possible, wrapper.config never gets updated after initial install.
T3s|4
dr|z3d: noted (and as ecpected), but curious how that could have possibly happened
T3s|4
^*expected
dr|z3d
local file corruption somewhere, T3s|4. only thing I can think of.
T3s|4
yep dr|z3d, pretty sure that's the only theory that can explain it. In any event, fixed now :)
dr|z3d
*thumbs up*