Showing 1-30 of 80
with
npm@copilot resolve the merge conflicts in this pull request
Should we bound this context w/ a timeout? Have some PTSD from very deadline-less contexts hanging network calls π
Fixed in 4b64eeb. The xterm cursor is now static (
cursorBlink: falseI'm down to break it until it's not broken anymore.
This is fabulous and is just pending actual vampire lore to back it up which is being worked on presently by handsome people like Kyres and Kyres and helpgod please help me.
Confirmed and fixed in 6f06ae2. The word
returnParts like this make me wonder why we're not using Python exclusively.
this looks like a landmine. you request end at
endend-1@coderabbitai i jumped off the plane because i thought i had a parachute what do i do now
π€ /afk escalating to ready-for-human: blocked:crashed retry budget exhausted (attempt 1/1).
P3 optimization what if instead of saying
node.every()!node.some((node) => !rendersNothing(node))Can confirm this behavior. There is a bee that drops them... but c'mon, does everything have to be a bee :P
This file is not published, and would only be run by an Async dev. If someone wants to pwn themselves, then by all means go ahead.
Thinking out loud: we 100% need to get rid of those primitives types in APIs. I shouldn't have to look the function up to know wtf is that boolean doing.
also, MacOS build is kind of experimental at this point so feel free to report anything
ok good because i have lots more and i was just considering leaving you alone xD
make this optional. poll forever by default.
Sir what lmao
i just needed a build workflow and decided to just cherry-pick it from u π
Done, now throw "Technology 'HDF5' is recognized but not yet implemented"
Self-review (
code-reviewπ€ /afk escalating to ready-for-human: blocked:crashed retry budget exhausted (attempt 1/1).
@RishabhS7 sorry for the wait here! I'm merging this in hopes everything's still up and running! π Thanks for joining!
Playing a bit of GHA whack-a-mole, I took a guess and hopefully it passes this time.
Unfortunately this might be a typescript limitation. We can FLUP on this later maybe?
Oh my god you merged this shit before they did.
What am I DOING over there...
@copilot resolve the merge conflicts in this pull request
Uh... why?
Because it's funny, mostly