~dr|z3d
@RN
@StormyCloud
@T3s|4
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%Liorar
%acetone
%cumlord
+DirtyHarry
+FreefallHeavens
+Xeha
+ardu
+bak83_
+mareki2p
+onon_
+profetikla
+r00tobo
+radakayot
+uop23ip
AHOH
Arch2
Danny
DeltaOreo
FreeB
Irc2PGuest59581
Irc2PGuest64993
Irc2PGuest70083
Irc2PGuest70134
Irc2PGuest96449
Meow
Onn4l7h
Onn4|7h
b4dab00m
boonst
duck
enoxa
maylay
not_bob_afk
phobos_
pisslord
poriori_
qend-irc2p
segfault
shiver_1
simprelay
solidx66
u5657
zer0bitz_
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*