Next>> Scroll to Bottom
Stuff goes here
L1[11:38:03] ⇨
Joins: Neo (Neo!~Neo@eos.pc-logix.com)
L3[11:38:16]
<Bob>
fooled
L4[11:38:16] <Mimiru> There he is.
L5[11:38:16] <Mimiru> welp, who knows how
long that was down.
L6[11:38:16] <Mimiru> answer, roughly 2
days
L7[11:38:16]
<Forecaster>
all of time, and none of it!
L8[11:38:17] <Mimiru> ffs.
L10[11:38:20] <MichiBot>
Better Than
Minecon 2016 - Opening Ceremony | length:
14m 6s |
Likes:
15 Dislikes:
2 Views:
1,394 | by
Corjaantje |
Published On 2/1/2016
L11[11:38:27]
<Bob>
N~~SA~~ EO is spying again on us
L12[11:38:30]
<Forecaster>
polyzium ^
L13[11:38:53]
<Forecaster>
that shows the video thingy asie made I think
L14[11:39:05]
<Bob> bad
apple
L16[11:39:55] <MichiBot>
Better Than
Minecon 2016 - Opening Ceremony | length:
14m 6s |
Likes:
15 Dislikes:
2 Views:
1,394 | by
Corjaantje |
Published On 2/1/2016
L17[11:40:35] <Inari> Stil waiting fro
charset
L18[11:41:35] <polyzium> Is that
160x50?
L19[11:41:51]
<Forecaster>
possibly
L20[11:41:54] <polyzium> I'm talking about
his 320x200 codec
L21[11:41:56] <polyzium> lemme send a
link
L23[11:42:03] <polyzium> oops
L24[11:42:05] <polyzium> full source
link
L25[11:42:36]
<ayangd> Can
a robot differentiate different floppies?
L26[11:43:20]
<Forecaster>
floppies have ids
L27[11:43:47]
<Bob>
^
L28[11:44:03]
<Bob> their
filesystem component addresses are different
L29[11:44:05]
<Bob> so
component proxy
L30[11:44:09]
<Bob> or mnt
if open ops is here
L31[11:44:15]
<Bob> or mnt
if openos is here [Edited]
L32[11:44:48]
<ayangd> Ah,
yes.. Right..
L33[11:47:45] <payonel> @Bob copying over
natives for oc won't work. oc verifies the natives before loading
them
L34[11:48:54] <payonel> @tell th3freddy
your issue with oc and natives on ubuntu -- this issue is important
to me. please make a github issue or contact me here again to
discuss
L35[11:49:11] ⇨
Joins: Kleadron
(Kleadron!~kleadron@c-73-254-147-9.hsd1.wa.comcast.net)
L36[11:49:20]
<EveryOS>
%help
L38[11:50:46] <polyzium> Only on
ubuntu?
L39[11:50:52] <polyzium> Why is ubuntu
having so much trouble recently
L40[11:51:10] <payonel> i run ubuntu
without issue, and it isn't only ubuntu
L41[11:51:19] <Mimiru> payonel, %tell, not
@tell :P
L42[11:51:24] <payonel> agris has the same
issue, on denvua...or something like that
L43[11:51:43] <payonel> %tell @tell tell
the thing for me
L44[11:51:43] <MichiBot> payonel: @tell
will be notified of this message when next seen.
L45[11:51:50] <Mimiru> ._.
L46[11:51:52] <payonel> %tell th3freddy
your issue with oc and natives on ubuntu -- this issue is important
to me. please make a github issue or contact me here again to
discuss
L47[11:51:52] <MichiBot> payonel: th3freddy
will be notified of this message when next seen.
L48[11:51:53] <payonel> :)
L49[11:51:53] *
Mimiru pokes payonel
L50[11:51:58] <Mimiru> lol
L51[11:52:05] <polyzium> Seems fine for
me
L52[11:52:12] <payonel> polyzium: fine for
me as well :)
L53[11:52:18] <payonel> but i need to
figure out what is going on
L54[11:53:29] <polyzium> Can you
debug?
L55[11:53:41] <payonel> i could, but i dont
have a repro
L56[11:56:01] <polyzium> payonel, remember
last time we talked about the cursor in my client thingy?
L57[11:56:32] <polyzium> Is there any way
to make it blink slowly without affecting events?
L58[11:57:03] <payonel> polyzium: it's
probably not an issue to slow down blinking with the latest
openos
L59[11:57:33] <polyzium> Yeah but your
cursor code is tied to events right
L60[11:58:30] <polyzium> If I try to slow
it down, keyboard polling also slows down
L61[11:59:21] <payonel> "cursor code
is tied to events" no, not really
L62[11:59:25] <payonel> there are layers of
indirection
L63[11:59:48] <payonel> but there was a bug
that the "current" pulling event coroutine was disrupting
the lowest timeout
L64[11:59:57] <payonel> so anyways, with
the latest version of openos, you should be fine
L65[12:00:43] <polyzium> I'll try putting
cursor blinking into a coroutine and see
L66[12:05:08] <payonel> polyzium: it
already is
L67[12:05:09] <payonel> :)
L68[12:05:13] <payonel> everything is a
coroutine
L69[12:05:19] <payonel> that's not the
point i was trying to make
L70[12:05:48] <payonel> get the latest
builds from our dev server and test a slower cursor, let me know if
it is an issue
L71[12:07:39]
<Bob> what
is the coroutine switch order
L72[12:07:47]
<Bob> im
wondering how does it switches from many coroutines
L73[12:08:22] <payonel> switch order? at
its core there is a call to pairs to cycle registrants
L74[12:08:28] <payonel> so, it is
"unordered"
L75[12:09:18] <polyzium> I'm currently
playing on a server rn
L76[12:09:23] <polyzium> so can't download
(yet)
L77[12:09:49] <bauen1> payonel: btw if you
have too much time a slight explanation of the magic behind
'cursor.read' would be helpfull
L78[12:11:47] <polyzium> The problem is
that if I have a second handleEvent() with blinkCursor(0.5) in it,
it pulls all the screen data in half a sec
L79[12:12:03] <polyzium> I want it to pull
all the time but remain the cursor to blink at 0.5
L80[12:13:38] <polyzium> and if I use the
function as is the printing stuff derps
L81[12:13:48] <polyzium> So I'm kinda lost
now
L82[12:31:37]
<Ariri>
%choose eBay or Amazon
L83[12:31:37] <MichiBot> Ariri: Out of
these two choices? I'd say "Amazon".
L84[12:31:50]
<Ariri>
Tch
L85[12:37:10]
<EveryOS>
%choose Minecraft with necessary computer mods or Terraria
L86[12:37:10] <MichiBot> EveryOS: My
grandfather always told me that "Minecraft with necessary
computer mods" is the way to go!
L87[12:39:03]
<EveryOS>
With the computer mods, MC rules, otherwise, it is Terraria, even
though I have an out of date XBox version.
L88[12:41:51]
<Bob> ~~ho
dare you not play modded terraria~~
L89[12:43:30] <payonel> polyzium: you want
to pull data all the time, without affecting the cursor, and you
want that handler to also print?
L90[12:44:29] <payonel> bauen1: the cursor
doesn't have docs partially because docs for it would take a lot of
work, but also because i'm not in love with its current form. i
think i can clean it up further
L91[12:44:50] <polyzium> payonel, other
function does the printing, not handleEvent()
L92[12:44:55] <payonel> but the main
benefit of the cursor lib was to allow applications to define
custom cursor behavior, without having to reimplement a lot of what
the cursor does
L93[12:45:00] <polyzium> But roughly
speaking yes
L94[12:45:06] <payonel> polyzium: but the
same coroutine?
L95[12:45:41] <payonel> polyzium: the
reason i ask is because multithreading is simple, unless you're
also trying to print
L96[12:45:54] <polyzium> Same coroutine
yes
L97[12:45:59] <payonel> it is best to have
1 thread manage user input/output
L98[12:46:11] <polyzium> Because if I do in
separate threads everything starts to derp
L99[12:46:17] <payonel> yeah, derpy
L100[12:46:23] <payonel> i have good plans
to improve that, btw
L101[12:46:27] <payonel> make it more
realisitic
L102[12:46:30] <payonel> but not
today
L103[12:47:04] <payonel> polyzium: so does
your system take user input?
L104[12:47:11] <polyzium> Yes, using
events
L105[12:47:19] <payonel> ah
L106[12:47:30] <payonel> you want to use
events, but with cursor blinking
L107[12:47:34] <payonel> but not for
io.read()
L108[12:47:50] <polyzium> io.read()
doesn't IMMEDIATELY send the character after receiving it
L109[12:47:53] <AmandaC> %8ball
chair?
L110[12:47:54] <MichiBot> AmandaC: I don't
think that's a question...
L111[12:48:00] <AmandaC> %8ball steal
chair?
L112[12:48:00] <MichiBot> AmandaC: Reply
hazy, try again
L113[12:48:02] <bauen1> payonel: that's
why i'm asking lol
L114[12:48:10] <payonel> polyzium: oh you
specifically want key codes, not just any event?
L115[12:48:10] <AmandaC> bah
L116[12:48:14] <polyzium> Yeah
L117[12:48:16] <polyzium> key codes
L118[12:48:21] <polyzium> Once a key is
received it gets sent
L119[12:48:31] <payonel> yeah. openos io
could really use a raw mode
L120[12:48:32] <polyzium> Not just a
string like io.read()
L121[12:49:15] <bauen1> if i'm
understanding everything correctly 'cursor.read' does the event
dispatching and 'cursor.echo' does the magic of displaying the
cursor ?
L122[12:49:50] <bauen1> and handle does
some more magic to append pressed keys onto the buffer ?
L123[12:49:56] <payonel> bauen1: yes.
cursor has 4 functions: read, echo, move, and handle
L124[12:50:25] <payonel> oh and update ...
i need to check the code
L125[12:51:58] <bauen1> i think that does
the actually appending of the buffer and doing the right move
L126[12:52:05] <payonel> ah yep. read()
returns the data (btw, for polyzium's concern, cursor read is where
the raw input mode would go)
L127[12:52:09] <polyzium> Actually my
client code is quite shit, I should do a rewrite at some
point
L128[12:52:46] <payonel> echo should be
the only place output is written. move is for logical movement of
the cursor data and offset, and update is to update its internal
buffer
L129[12:53:44] <payonel> bauen1:
cursor.read reads until a newline in the buffer, splits at the
newline, and returns the first part
L130[12:54:12] <payonel> cursor is the
"keyboard driver", the idea was to separate the tty from
the internals of keyboard events
L131[12:54:28] <payonel> so cursor.read
takes events and handles them until there is a "line" of
input
L132[12:55:02] <bauen1> that makes sense,
thanks a lot
L133[12:55:09] <bauen1> %tonk
L134[12:55:10] <MichiBot> Consarn it!
bauen1! You beat Lizzy's previous record of 2 hours, 11 minutes and
48 seconds (By 1 hour, 2 minutes and 32 seconds)! I hope you're
happy!
L135[12:55:11] <MichiBot> bauen1's new
record is 3 hours, 14 minutes and 20 seconds! bauen1 also gained
0.00312 (0.00104 x 3) tonk points for stealing the tonk.
L136[12:55:30] <payonel> polyzium: in the
future, you would be able to switch the input mode to raw, and get
each key code, not line
L137[12:55:41] <Mimiru> %msp
L138[12:55:43] <MichiBot> Ping reply from
Mimiru 1237.0ms
L139[12:55:48] <Mimiru> ._.
L140[12:55:52] <Mimiru> %msp
L141[12:55:53] <MichiBot> Ping reply from
Mimiru 508.0ms
L142[12:55:59] <payonel> polyzium: but for
today, you can write some code that will likely break in future
openos updates, if that is okay with you
L143[12:56:01]
<Forecaster>
that's a lot of miniseconds
L144[12:56:59]
<ayangd>
*mini*seconds
L145[12:57:21] <Mimiru> %msp
L146[12:57:22] <MichiBot> Ping reply from
Mimiru 504.0ms
L147[12:57:31] <Mimiru>
butwhythough.gifv
L148[12:57:51] <polyzium> payonel, so
should I leave it as-is or use cursor's read thingy?
L149[12:58:31] <payonel> polyzium: do you
have oc open and can test something?
L150[12:58:37] <payonel> @msp
L151[12:58:42] <payonel> %msp
L152[12:58:43] <MichiBot> Ping reply from
payonel 417.0ms
L153[12:58:50]
<Forecaster>
well it's not tinyseconds
L154[12:58:53]
<Forecaster>
or ts
L155[12:59:02] <Mimiru> %p
L156[12:59:03] <MichiBot> Ping reply from
Mimiru 0.52s
L157[12:59:08] <payonel> %p
L158[12:59:09] <MichiBot> Ping reply from
payonel 0.48s
L159[12:59:18] <payonel> %mimiru
L160[12:59:21] <Mimiru> I wonder if
something is limiting MichiBot's timing..
L161[12:59:22] <payonel> hmm. not a
command
L162[12:59:28] <polyzium> payonel, Yep I
do
L163[12:59:40]
<Forecaster>
it's all the counting she has to do for tonks
L164[12:59:49]
<Forecaster>
definitely
L165[13:00:21] <polyzium> This new stuff
right now is undocumented
L166[13:00:44] <payonel> polyzium: imagine
you have an event handler: `local function event_handler(...)
end`
L167[13:00:59] <payonel> polyzium:
correct, undocumented because i need to be free to change it
L168[13:01:14] <payonel> but, the changes
i make will be similar enough that you should be able to adapt
it
L169[13:01:20] <payonel>
"should" :)
L170[13:01:55] <polyzium> Nothing special
about event handlers
L171[13:02:00] <polyzium> they are jsut
copied from the docs
L172[13:02:06] <payonel> but, try this
(again, might change): term.read( { handle = function(self, ...)
event_handler(...) return self.super.handle(self, ...) end }
)
L173[13:02:27] <payonel> polyzium: THAT
wasn't the part that would change, my term read's handle is the
"not promised" part
L174[13:06:35] <polyzium> What should that
do?
L175[13:06:43] <polyzium> For me it just
takes a string
L176[13:06:49] <polyzium> like how
io.read() would behave
L177[13:06:56] <payonel> it should call
event handler for every event that occurs during the
term.read
L178[13:07:20] ***
Mimiru is now known as Katie
L179[13:07:23] ***
Katie is now known as Caitlyn
L180[13:07:37] ***
Caitlyn is now known as Michiyo
L181[13:07:49] ***
Michiyo is now known as Mimiru
L182[13:07:51] ***
payonel is now known as sugoi
L183[13:08:07] <Mimiru> gotta save my
nicks groupings :P
L184[13:08:18] ***
sugoi is now known as payonel
L185[13:08:19] <polyzium> So in order to
read from the socket I need to emit an event from it or what
L186[13:08:51] <polyzium> TCP connections
don't emit events or do they
L187[13:09:20] <polyzium> Or maybe I'm
just tired and having trouble understanding
L188[13:09:50] <payonel> the code i gave
you provides you a hook, an access, into the internal workings of
the cursor
L189[13:10:06] <payonel> right now openos
doesn't have a "raw mode" io -- which irl is how we read
all key codes
L190[13:10:43] <payonel> this handle hook
sample i gave you lets you see the events right when the cursor
keyboard-driver is getting them
L191[13:13:05]
<Forecaster>
Mimiru is a creature of many names
L192[13:26:33]
⇨ Joins: Rahix
(Rahix!~Rahix@p5B122E90.dip0.t-ipconnect.de)
L193[13:26:56] <polyzium> payonel, yep I
can see the events but the whole thread seems to be stuck on this
read thing
L194[13:26:59] <polyzium> so it's
blocking
L195[13:27:02] <polyzium> What's the
point
L196[13:30:22]
⇨ Joins: Stary (Stary!znc@thonk.9net.org)
L197[13:31:15]
⇨ Joins: Fridtjof (Fridtjof!znc@thonk.9net.org)
L198[13:31:55]
⇨ Joins: CompanionCube
(CompanionCube!znc@thonk.9net.org)
L199[13:39:31] <payonel> polyzium: press
enter
L200[13:39:48] <polyzium> Tried multiple
times
L201[13:39:57] <payonel> or, return false
when you want it to end
L202[13:40:17] ⇦
Quits: ben_mkiv (ben_mkiv!~ben_mkiv@88.130.158.198) (Ping timeout:
206 seconds)
L203[13:40:44] <payonel> polyzium: don't
print or do anything "cursor" with your event_handler(),
btw
L204[13:41:55] ⇦
Quits: Renari (Renari!~Renari@24.229.184.254.res-cmts.sm.ptd.net)
(Read error: Connection reset by peer)
L205[13:42:02] <polyzium> I'm just sending
stuff to the socket
L206[13:42:04] <polyzium> nothing
else
L207[13:42:30] <payonel> what
socket?
L208[13:42:53] <polyzium> the TCP
socket
L209[13:43:08] <polyzium>
sock.write()
L210[13:43:20] <payonel> well anyways, the
handle code i provided should do what you need
L211[13:43:32] <payonel> when you want the
term.read to finish, you can have your custom handle method return
false
L212[13:43:49] <polyzium> So send the
letter and then return false
L213[13:44:38] <payonel> 'sending the
letter' i assume is your own event_handler's decision
L214[13:44:47] <payonel> but yes, if
handle returns false, the read will end
L215[13:45:07] <polyzium> handleEvent()
calls key_down() handler
L216[13:45:23] <polyzium> and key_down()
sends characters to the socket
L217[13:45:24] <payonel> sounds like youre
talking about your own user code
L218[13:46:33] <payonel> you can also
specify `pwchar = ''` if you don't want term to echo the
chars
L219[13:46:51] <payonel> so, term.read( {
handle = ...., pwchar = '' } )
L220[13:47:21] <polyzium> It still gets
blocked. wtf
L221[13:47:38] <payonel> works for me
:shrug:
L222[13:47:50] <payonel> are you using a
recent build of oc?
L223[13:47:59] <polyzium> Lemme check
which version
L224[13:48:19] <polyzium> 1.7.4.153
L225[13:48:40] <payonel> release builds? i
thought i mentioned you should be using dev builds
L226[13:49:00] <polyzium> YOu did but I'm
on a server right now
L227[13:49:08] <polyzium> so I can't
install anything
L228[13:49:39] <payonel> well, you can
patch it, but, i bet it should still work on 153, let me check
something
L229[13:51:41]
<Kaos> hi
m8
L230[13:52:12]
<Kaos> in
latest version of oc when i type 'rs right 15' the screen (tier 3)
stop working
L231[13:52:27]
<Kaos> can't
type anything until i break the item and replace the screen
L232[13:53:21]
⇨ Joins: ben_mkiv
(ben_mkiv!~ben_mkiv@88.130.157.36)
L233[13:53:56]
<Bob> @Kaos
because when the screen gets a redstone signal, it turns off
L234[13:54:07]
<Bob> so
your screen is on the right and you turn it off
L235[13:54:08]
<Kaos> ok
lol
L236[13:54:16]
<Bob>
Yea
L237[13:54:23] <polyzium> payonel, what
does self.super.handle do
L238[13:54:40] <polyzium> Superclass's
handle() of sorts?
L239[13:54:43] <payonel> yes
L240[13:54:52] <polyzium> Why is that
needed
L241[13:55:47] <payonel> it's not, but if
you dont call it, you'll need to decide for yourself when to return
true or false from handle
L242[13:56:02] <AmandaC> ... why does
minecraft have a recipie to turn 3 string into 4?
L243[13:56:14] <payonel> the handle code
worked for me on 153's version of the code, sorry
L244[13:56:16] <polyzium> I replaced that
with return false and it doesn't block but I get lots of
derps
L245[13:56:28] <polyzium> Maybe I'm
screwing something up
L246[13:56:46] <AmandaC> wait, I can
count. 3 into 2
L247[13:58:03] <polyzium> I tried putting
return false into both handleEvent() and key_down() but term.read
still blocks stuff
L248[13:58:36] <payonel> i dont see why
your own methods return false would have any impact on returning
from cursor.handle
L249[13:59:02] <polyzium> However instead
of returning that super function I returned false
L250[13:59:09] <polyzium> and doesn't
block anymore
L251[13:59:19] <payonel> if you return
falsey from cursor.handle, that'll end the read
L252[13:59:30] <polyzium> but in exchange
I got a lot of derps
L253[13:59:56] <polyzium> Like pressing
the up arrow key gives me the vietnamese letter D
L254[14:00:14] <payonel> this is all your
own user code's issues
L255[14:00:42] <payonel> btw, term.read()
returns nil when the cursor.handle terminates the read (i.e.
returns false)
L256[14:02:35] <polyzium> payonel, oops.
Apparently your event handler doesn't return keyboard address
L257[14:02:39] <polyzium> That's why I got
derps
L258[14:02:46] <payonel> oh yeah...
L259[14:03:12] <polyzium> Now everything
works fine
L260[14:03:16] <payonel> cool :)
L261[14:03:22] <polyzium> I gotta test
some live ncurses apps before I push
L262[14:03:52] <payonel> polyzium: again,
handle may change in the future
L263[14:05:21] <polyzium> Alright so
L264[14:05:28] <polyzium> I don't need
that blinking cursor code anymore
L265[14:05:35] <polyzium> Everythign works
fine
L266[14:05:42] <polyzium> only reads from
socket on demand
L267[14:08:24] <polyzium> phew
L268[14:08:29] <polyzium> Almost melted my
brain
L269[14:08:33] <polyzium> but glad to see
it working
L270[14:10:26] <polyzium> payonel, thank
you a lot man
L271[14:11:00] <polyzium> Also we should
work together on doing all the VT100 rules so it can pass vttest
testing program
L272[14:11:06] <Inari> %pet payonel
L273[14:11:07] *
MichiBot pets payonel with A sense of dread. 8 health
gained!
L274[14:20:05]
<Kaos> can i
assign in the server rack all sides to a server?
L275[14:21:30] <ben_mkiv> no only
one
L276[14:21:37]
<Kaos>
rip
L277[14:21:38]
<Kaos>
ok
L278[14:24:45] <Inari> %pet Temia
L279[14:24:50] <Inari> %pet Temia
L280[14:24:51] *
MichiBot brushes Temia with (╯°□°)╯hahahahahaha╯)°□°╯). 1 health
gained!
L281[14:24:58] <Inari> o.o
L282[14:25:00] <Inari> Creepy
L283[14:31:02] ⇦
Quits: ben_mkiv (ben_mkiv!~ben_mkiv@88.130.157.36) (Ping timeout:
206 seconds)
L284[14:49:51] ⇦
Quits: lopezt (lopezt!~Adium@v22018076567069662.quicksrv.de) (Quit:
Leaving.)
L286[15:05:37] <MichiBot>
25m Men's
Rapid Fire Pistol final - Munich 2013 ISSF World Cup | length:
39m 36s | Likes:
24,965
Dislikes:
5,778 Views:
7,923,761 | by
ISSF - International Shooting Sport
Federation | Published On 28/5/2013
L287[15:06:52]
⇨ Joins: Renari
(Renari!~Renari@24.229.184.254.res-cmts.sm.ptd.net)
L288[15:18:51] <Inari> AmandaC: I found
perfection
L289[15:19:18]
<Bob>
Hmm
L290[15:19:36] <AmandaC> Inari: oh?
L292[15:19:50] <MichiBot>
(羊羔毛斗篷)Weaving a Cloack with Fluffy and Soft Lambswool, Never
Dread Winter Anymore|Liziqi Channel | length:
5m 49s |
Likes:
305,111 Dislikes:
2,162 Views:
6,349,754 | by
李子柒 Liziqi | Published On 19/3/2019
L293[15:27:09] <Izaya> good news
everyone!
L294[15:27:11] <Izaya> no work today
L295[15:42:41] <Inari> AmandaC: Where do I
get that MC mod
L296[15:42:50] <AmandaC> Inari: which
one?
L297[15:42:56] <Inari> The one from the
vid I linked
L298[15:42:56] <Inari> :f
L299[15:43:21] <AmandaC> oh, the wool
thing? No idea. :D
L300[15:43:48] <Inari> Preferably with VR
and beautiful graphics
L301[15:46:45] <CompanionCube> %tonk
L302[15:46:45] <MichiBot> I'm sorry
CompanionCube, you were not able to beat bauen1's record of 3
hours, 14 minutes and 20 seconds this time. 2 hours, 51 minutes and
35 seconds were wasted! Missed by 22 minutes and 45 seconds!
L303[15:46:49] <CompanionCube> :(
L304[15:51:09] <Inari> AmandaC: You don't
seem to agree with it being perfection though
L305[15:51:27] <AmandaC> Inari: didn't
watch it all yet, currently watching something on my own
L306[15:51:35] <Inari> Ah :p
L307[16:04:36] ⇦
Quits: polyzium (polyzium!~polyzium@89.207.223.202) (Remote host
closed the connection)
L309[16:20:52] ⇦
Quits: Rahix (Rahix!~Rahix@p5B122E90.dip0.t-ipconnect.de) (Remote
host closed the connection)
L310[16:22:04] <AmandaC> Inari:
brushie-brushie
L311[16:22:45]
<EveryOS>
%warp europe
L312[16:22:45] <MichiBot> You end up in a
dimension populated by fish shark girls.
L313[16:23:24]
<Forecaster>
I guess I could make that accept arguments
L314[16:23:37]
<Forecaster>
or maybe this is good
L315[16:33:27]
⇨ Joins: Thutmose
(Thutmose!~Patrick@host-69-59-79-181.nctv.com)
L316[16:55:31]
<Joco223>
Does `filesystem.remove` remove everything from inside the
directory too?
L317[17:06:10] ⇦
Quits: Vexatos (Vexatos!~Vexatos@port-92-193-14-47.dynamic.qsc.de)
(Quit: Insert quantum chemistry joke here)
L318[17:09:18] ⇦
Quits: t20kdc
(t20kdc!~20kdc@cpc139326-aztw33-2-0-cust441.18-1.cable.virginm.net)
(Ping timeout: 190 seconds)
L319[17:32:13] ⇦
Quits: flappy (flappy!~flappy@88-113-149-197.elisa-laajakaista.fi)
(Ping timeout: 190 seconds)
L321[18:05:00]
<Kodos>
%warp
L322[18:05:00] <MichiBot> You end up in a
dimension inhabited by water.
L323[18:05:08]
<Kodos>
Welp
L324[18:20:45] <AmandaC> By water,
eh?
L325[18:43:55] <Skye> %sip random
L326[18:43:55] <MichiBot> You drink a
bubbly emerald potion (New!). Skye looks confused as nothing
happens.
L327[18:44:00] <Skye> %warp
L328[18:44:00] <MichiBot> You end up in a
world inhabited by clowns.
L329[18:44:05] <Skye> No.
L330[18:44:08] <Skye> %warp
L331[18:44:09] <MichiBot> You end up in a
dry world.
L333[18:44:19] <Skye> %warp
L334[18:44:19] <MichiBot> You end up in a
dimension populated by lava goat boys.
L335[18:44:26] <Skye> %sip random
L336[18:44:26] <MichiBot> You drink a
seeping bavarium potion (New!). It tastes sour.
L338[18:44:33] <Skye> Goodnight
L339[18:52:15] <Mimiru> %sip random
L340[18:52:15] <MichiBot> You drink a
gloopy octiron potion (New!). Mimiru now has a mullet for 30
minutes.
L341[18:52:21] <Mimiru> ...
L342[19:37:10]
⇨ Joins: lopezt
(lopezt!~Adium@v22018076567069662.quicksrv.de)
L343[20:05:55]
⇨ Joins: glasspelican
(glasspelican!~quassel@2607:5300:201:3100::325)
L344[20:08:38] ⇦
Quits: Away_21 (Away_21!crystal@bronyville.me) (Ping timeout: 190
seconds)
L345[20:09:12]
<EveryOS> I
am not done writing my new GUI scoring system. I feel like it will
be a huge improvement over my previous blitting approach, but it
probably still won't be perfect. First of all, it is only going to
use set for now, secondly, just a few random characters could throw
it off from the quickest solution. Obviously, I will eventually get
to optimizing it now, but for now, I wish to finish a basic
approach.
L346[20:09:38]
<EveryOS> I
am not done writing my new GUI scoring system. I feel like it will
be a huge improvement over my previous blitting approach, but it
probably still won't be perfect. First of all, it is only going to
use set for now, secondly, just a few random characters could throw
it off from the quickest solution. Obviously, I will eventually get
to optimizing it, but for now, I wish to finish a basic approach.
[Edited]
L347[20:10:29]
<EveryOS> It
is quite annoying how the IRC shows edit's by reprinting the entire
message with the edits, meaning that the message essentially gets
shown multiple times on the screen.
L348[20:11:39] <Izaya> Just don't make
mistakes :^)
L349[20:11:53] <Izaya> or correct them
like a normal person, by repeating the short part that was wrong
and putting a * at the end
L350[20:12:42]
<EveryOS>
Discord has an "edit" button, and I tend to forget that
it doesn't work that well with the IRC until after I make the
edit.
L351[20:13:21]
<EveryOS>
*At least I didn't go back and edit the word "edit's" to
be "edits" in my one message*
L352[20:15:08] <Izaya> Well, it'd just
send another message saying "replace message x with this new
version, y" to the client
L353[20:15:40]
<EveryOS> I
was once told it shows all of the edits on the IRC
L354[20:15:45]
⇨ Joins: Away_21 (Away_21!crystal@bronyville.me)
L355[20:15:45]
<EveryOS> or
something
L357[20:20:05]
<EveryOS>
Yea, it redisplayed my one message.
L358[20:20:18] <Izaya> Two messages
:^)
L359[20:21:24] <Izaya> No such thing as
message deletion, either. Deleting a message is just another
message saying to delete a message.
L360[20:21:35]
<EveryOS>
(:
L361[20:22:02]
<EveryOS> I
think deletions appear in Discord's audit logs anyways? Or am I
mistaken?
L362[20:22:07] <CompanionCube> y u no sort
buffers
L363[20:22:18] <Izaya> Dunno, never used
Discord myself.
L364[20:22:23] <Izaya> CompanionCube:
sorted by network.
L366[20:24:29]
<EveryOS>
/part
L367[20:24:41]
<EveryOS>
What does that do
L368[20:24:50] <Izaya> departs a
channel
L369[20:24:53] <CompanionCube> well /part
is the opposite of /join
L370[20:25:02]
<EveryOS>
Ah, ok
L371[20:28:17] ⇦
Quits: Thutmose (Thutmose!~Patrick@host-69-59-79-181.nctv.com)
(Quit: Leaving.)
L372[20:36:45]
<EveryOS>
Gonna test out my new GUI drawing method. Here is hoping that there
is not too much debugging that needs done!
L373[20:37:48]
<EveryOS>
Ok, CTRL+ALT+C is terminate, right? It is not working, gonna have
to turn off the thing and repower.
L374[20:38:38]
<EveryOS>
Ok, first error, field buffer is nil, wow.
L375[20:38:57]
<EveryOS>
Ah, I see
L376[20:39:44]
<EveryOS>
Now data is nil
L377[20:39:44]
<EveryOS>
Ok, hopefully not everything is nil.
L378[20:39:46] <agris> payonel,
L379[20:40:02] <agris> payonel, do you got
any more builds for me to test
L380[20:40:24] <agris> payonel, also,
don't know if this could be the cause, but a while back in the
linux ecosystem there was a big change
L381[20:40:46] <agris> it was either the
switch to GCC 5 to 6 or 6 to 7
L382[20:40:48]
⇨ Joins: DFU (DFU!~DFU@194.125.251.201)
L383[20:40:54] <agris> I think 6 to
7
L384[20:41:14] <agris> the big change was
an ABI switch in the way binaries are stored
L385[20:41:53] <agris> I think the switch
was the linux world switching to ELF executables rather than a.out
executable
L386[20:42:01] <agris> not sure if that
could be the issue
L387[20:43:13] <CompanionCube> agris:
no
L388[20:43:23] <CompanionCube> GCC5 was a
C++ ABI change
L389[20:43:38] <CompanionCube> also
L390[20:43:45] <CompanionCube> >using
a.out executables for anything ever
L391[20:43:48] <CompanionCube> what decade
is this
L392[20:45:12] <CompanionCube> 'Linux also
used a.out until kernel 1.2 (March 1995), when it was superseded by
ELF for that platform as well' huh, thought it was earlier.
L393[20:50:03] ⇦
Quits: DFU (DFU!~DFU@194.125.251.201) (Ping timeout: 202
seconds)
L394[20:51:22] <agris> hmm
L395[20:51:29] <agris> this server doesn't
track idle times
L396[20:51:44] <Izaya> %seen agris
L397[20:51:44] <MichiBot> agris has not
been seen
L398[20:51:48] <Izaya> neat
L399[20:51:53] <agris> CompanionCube, well
Gentoo hasn't switched to it till like last year
L400[20:52:04] <agris> %seen payonel
L401[20:52:05] <MichiBot> payonel was last
seen 24d 2h 56m 36s ago. Joining
L402[20:52:15] <CompanionCube> %seen
CompanionCube
L403[20:52:15] <MichiBot> CompanionCube
was last seen 10h 37m 56s ago. Quitting
L404[20:52:34] <CompanionCube> agris: i
remember rebuilding @world for 17.0 + GCC
L405[20:52:35] <agris> payonel, when you
get the chance, I finished setting up your dev machine. just ssh
root@206.212.234.149 with your key
L406[20:53:56] <agris> please be mindful
of disk space
L407[20:54:35] <Izaya> >The RC’s
crankshaft was assembled from 13 individual pieces with extreme
precision using jigs that weighed more than the entire bike’s 250
or so pounds.
L408[20:54:38] <agris> otherwise it's 8G
of namespaced bare-metal with 48 cores allocated so builds won't
take long
L409[20:54:54] <CompanionCube> wow
L410[20:54:57] <CompanionCube> such
power
L411[20:55:01] <CompanionCube> many
cores
L412[20:55:56] <agris> cpu and ram I have,
disc space not so much
L413[20:56:17] <Izaya> tfw only 15TB
disk
L414[20:57:09] <CompanionCube> Izaya: more
disk than me :p
L415[20:57:22] <agris> lzaya, how
redundant?
L416[20:58:03] <Izaya> that's raw, it's in
RAID5 so I only get 12TB usable space
L417[20:58:12] <Izaya> and that's an I not
an l
L418[20:58:24] <agris> oh
L419[20:58:30] <Izaya> may I suggest using
a font that differentiates better
L420[20:58:35] <agris> you really
shouldn't use raid5
L421[20:58:46] <agris> it's
dangerous
L422[20:58:48] <CompanionCube> depends on
disk size, no?
L423[20:58:49] <Izaya> I should use RAID6
but $$$
L424[20:59:17] <agris> well raid6 is
better than raid5 but ideally you'd use a multi-block-device aware
filesystem like OpenZFS or HAMMER2
L425[20:59:44] <CompanionCube> i think
Izaya is more a btrfs person
L426[20:59:47] <agris> that also has
silent corruption detection via checksumming, and the ability to
correct them
L427[20:59:49] <Izaya> apparently btrfs'
multi-device support is fairly mature now
L428[20:59:58] <agris> CompanionCube,
btrfs is not stable
L429[21:00:06] <agris> nor do it's modes
make any practical sense
L430[21:00:17] <CompanionCube> Izaya:
RAID5/6 is still somewhat shit though, no?
L431[21:00:17] <Izaya> but when I set it
up it was not, so ext4 over md
L432[21:00:25] <agris> I've literally raid
a btrfs in raid1 corrupt itself
L433[21:00:25] <Izaya> CompanionCube:
depends who you ask
L434[21:00:55] <CompanionCube> isn't RAID1
supposed to be one of the good bits
L435[21:01:22] <agris> the only thing
btrfs has over zfs is the ability to expand existing
non-mirrors
L436[21:01:28] <agris> which, will come to
zfs in the future
L437[21:01:46] <CompanionCube> agris: i
mean, you can also expand single-disks to mirrors
L438[21:01:52] <CompanionCube> but that's
being pedantic :p
L439[21:01:55] <Izaya> I'll use btrfs when
it's in the main tree :^)
L440[21:01:59] <Izaya> s/btrfs/zfs/
L441[21:01:59] <MichiBot> <Izaya>
I'll use zfs when it's in the main tree :^)
L442[21:01:59] <agris> CompanionCube, well
you can already do that in zfs
L443[21:02:14] <CompanionCube> agris:
that's my point
L444[21:02:17] <agris> mirrors in zfs are
just fancy raid1s, unless it's a mirror of a nested raidz
L445[21:02:37] <CompanionCube> Izaya: so
you'll use bcachefs eventually then?
L446[21:02:47] <Izaya> bcachefs sounds
interesting
L447[21:02:50] <agris> If I were you, I
wouldn't ever put any data i cared about losing on btrfs
L448[21:03:02] <CompanionCube> agris: you
don't need to tell me
L449[21:03:08] <Izaya> t. been using btrfs
without incident since 2014 or so
L450[21:03:16] <CompanionCube> lookup
'btrfs' in the logs :
L451[21:03:27] <agris> lzaya with how many
disk failures or corrupted sectors?
L452[21:03:51] <CompanionCube> (okay, it
was not entirely btrfs's fault and it does have good recovery
tools.)
L453[21:03:51] <agris> and have you
verified externally your files have not changed?
L454[21:04:31] <agris> CompanionCube,
again, my experience with modern btrfs is having a raid1 corrupt
itself after testing yanking 1 one the disks while the system was
off, and powering it back on
L455[21:04:45] <agris> when it powred back
on not even the btrfs recovery tools could save the
filesystem
L456[21:04:52] <agris> despite it being a
fully balanced raid1
L457[21:05:20] <agris> if a filesystem
can't even do a raid1 right I have absolutely no faith in it's
ability to do anything even slightly more complex
L458[21:06:29] <agris> and if you actually
look at the way the other raidlevels work at the block level in
btrfs you wouldn't want to put your data there either. unless you
running balance after every single transaction, if the right disk
fails at the worst possible moment even your multi-redudant array
will fault
L459[21:07:03] <agris> btrfs , as least in
the state it's in right now; a gimmick like most hipster javascript
frameworks nowadays
L460[21:10:04] <agris> it's really a
wonder how it ever got into a linux release rather than staying in
the beta or rc kernels
L461[21:15:06]
<Gary Gygax>
does anyone know when ther Server Rack as added to Open Computers
and is it compatible with 1.7.10?
L462[21:17:15]
<Gary Gygax>
@Zef
L463[21:21:36]
<Gary Gygax>
@Kodos yo bud
L464[21:21:47]
<Gary Gygax>
I have a question for yo
L465[21:28:04]
⇨ Joins: Thutmose
(Thutmose!~Patrick@host-69-59-79-181.nctv.com)
L466[21:31:44] ⇦
Quits: Thutmose (Thutmose!~Patrick@host-69-59-79-181.nctv.com)
(Client Quit)
L467[21:40:32]
<Kodos>
Shoot
L468[21:40:56]
<Kodos>
@Gary Gygax
L469[21:41:46]
<Kodos>
¯\_(ツ)_/¯
L470[21:57:18]
<Gary Gygax>
@Kodos if there is an issue with OC what do i do
L471[22:07:52]
<Kodos>
Depends on the issue
L472[22:08:07]
<Kodos>
Generally you check GitHub to see if it’s known
L473[22:08:13]
<Kodos> Or
ask about it here
L474[22:11:14] ⇦
Quits: Renari (Renari!~Renari@24.229.184.254.res-cmts.sm.ptd.net)
(Read error: Connection reset by peer)
L475[22:11:48]
<Kodos>
However ask me soon because I’m going to sleep in a bit.
L476[22:12:04]
<Kodos> And
won’t receive highlights
L477[22:23:51]
<Gary Gygax>
no its fine
L478[22:24:01]
<Gary Gygax>
go to bed, the issue was resolved by magic i guess
L479[22:24:05]
<Gary Gygax>
because now it all works
L480[23:04:25] ⇦
Quits: Aedda (Aedda!~aedda@2600:3c00::19:cace) (Quit:
esper)
L481[23:24:08]
⇨ Joins: ben_mkiv
(ben_mkiv!~ben_mkiv@88.130.158.171)
L482[23:35:53] <payonel> agris: cool,
thanks! i'll see what i can learn
L483[23:36:04] <payonel> agris: also, like
izaya, i've been using btrfs since around 2014
L484[23:36:09] <payonel> it has worked
very very well for me
L485[23:36:23] <agris> payonel, make sure
you backup your shit then
L486[23:37:24] <payonel> yeah, i do. but
like i said, i've been using it for over 5 years. no incident,
works great
L487[23:37:45] <payonel> i swear, it'll be
20 years from now and people will stay love to hate and distrust
btrfs
L488[23:38:25] <payonel>
s/stay/still/
L489[23:38:25] <MichiBot> <payonel>
i swear, it'll be 20 years from now and people will still love to
hate and distrust btrfs
L490[23:38:30] <agris> It's only been 5
months since dealing with my last btrfs catastrophic failure
L491[23:38:48] <agris> on known good disks
and hardware
L492[23:39:02] <agris> in a lab
environment
L493[23:39:22] <agris> on a recent stable
kernel
L494[23:39:53] <payonel> what was the
failure?
L495[23:40:57] <agris> complete
unrepairable filesystem corruption rendering the filesystem
unmountable and irrecoverable
L496[23:41:10] <payonel> yeah, but what
was the failure?
L497[23:41:53] <agris> I don't know why it
failed
L498[23:42:09] <agris> I didn't persue
that
L499[23:42:50] <payonel> what kind of
"lab environment" does one have when they don't
investigate a failure?
L500[23:42:52] <agris> well I did a little
but I wasn't going to waste time pulling out a kernel debugger
after heading the raw disks, checking logs, dmesgs, and running
fsck rooling didn't work
L501[23:43:23] <agris> I determined that
the filesystem was not stable enough after that
L502[23:43:38] <payonel> it doesn't take a
kernel debugger or logs. you can inspect a btrfs pool with just
btrfs tools. there are very detail analysis tools that tell you
what type of failure occurred and where
L503[23:47:45] <ben_mkiv> whoever made the
new curseforge design.... deserves a special place in some UI
Design School
L504[23:48:21]
<Mimiru> Oh
what in the fuck?
L505[23:48:43] <ben_mkiv> why is the
footer not at the end of the page? xD
L507[23:58:23] <agris> uh ok
L508[23:58:27] <agris> *uh oh
L509[23:58:29] <agris> what happened
L510[23:58:40] <agris> did they turn it
into a tablet interface or something?
L511[23:58:45] *
agris dares to look
L512[23:59:24] <ben_mkiv> it looks like
they parsed curse.com layout through microsoft frontpage and use it
for curseforge.com now