RIP to my control, c, and v keys ):

@DanielRuf lol yes, thank you.

though, given i copy pasted it, it seems dprk was actually exfiltrating

.netfily

they still keep the cool sickass cloaks right those things rock

FUCK NO.

I changed it to

can_use_step_higher_than_a_block_range_length_and_out_not_equal_to_a_range_boundaries

Make it so, Jenkins.

Tested enough to be dangerous. Launch it! 🏴‍☠️

Writing

failIfNoFirstInvocation: unknown = true

I still need to make CI happy.

To my surprise, PIE isn't the default everywhere yet.

Missing the "f" in "if" next to xenomorph and you.

Not overdue. Still QA on prod

Yes I had to restore a backup. 5385 slots hit the ground at once. The work around is to break the cable going to the SAP before breaking the SAP itself.

But we can call the compiler from Ecstasy code, so in theory we could write XUnit compiler tests. We just need to find more hours in the day.

I don't think we need tests for code that doesn't run in production

Merging without review because everyone is on holiday

I added the log crate because it's quite common even if we never log in the codebase :sweat_smile: Should not be a problem and maybe in the future we will add some logs

Changes look good to me, but I cannot verify that @doronbehar is true a human, so I will not merge this :smiling_imp:

Why would you make a test specifically to ensure that a flag is only one character on some shuttle text. Im so fucking scared rn. Let me see if I can find an 18+ icon thats like...one character.

Do you expect the combine to set cruise control and drive itself?

We use -Werror. Warnings are errors.

src/sirthreadpool.c(189): error C2220: the following warning is treated as an error

Claude said we should just

#pragma warning

Works for me when you don't stuff the corpse into the pit, which is definitely not what's intended, but it's a workaround for now.

Can I add a TODO instead of fixing it right here and now? In the next PR I'm going to operate on SLM anyway.

Fixed this, and also fixed the logic because I was originally returning the opposite of what the function name said. 🙃

		ghostize(FALSE,SENTIENCE_RETAIN) //0 parameter is so we can never re-enter our body, "Charlie, you can never come baaaack~" :3

Expected results

Scrolls through time.

hey so um these are prundles.. not… time machines… we’ll see what we can do.

Ubuntu host freezes, Fleet agent's dance too fervent. A calm choreography waits.

This looks slow. Should it have a TODO to optimize it? (Don't optimize it now.)

Looks good to me, but getting an "outside opinion" from another iteration of you 🙃

Let's give it a try (test in production 🥳 🦜 )

CI needs a kick (rate limits 🫠)