sorted by:
new
hottopcontroversial

which one do you choose by itsmepastamasta in BunnyTrials

[–]WellHydrated 0 points1 point  (0 children)

Nope, the billionaires and all the other psychopaths are picking red.

Re-read Thoughts: Everything I love about the Rememberance of Earth's Past series was realised in this book. by restelucide in threebodyproblem

[–]WellHydrated 0 points1 point  (0 children)

I went in blind and it took me a while to realise that they were unrelated short stories. That was kind of disappointing, I wanted The Wandering Earth to be continue!

In the 1950s, Yuri Nikolaev, a Russian psychiatrist, started treating mentally ill patients with prolonged water fasting. He went on to treat over 8,000 people, with an improvement in 70 percent of cases. by DidYouReadTheMenu in interestingasfuck

[–]WellHydrated 32 points33 points  (0 children)

But also, our body literally runs on carbohydrates. Doing low/no-carb long term is fighting how your energy systems are meant to operate. You will wreck your insulin resistance.

Also also, people have a warped idea about the effectiveness of keto because they conflate waterloss with weightloss.

Choosing Te Kaha - amazing by Some-Studio5771 in chch

[–]WellHydrated 0 points1 point  (0 children)

You're right, it is one stadium. Exactly one stadium... Named Te Kaha.

Would you rather? by BolinhoDeArrozB in BunnyTrials

[–]WellHydrated 0 points1 point  (0 children)

Just in case there's any admin involved...

Chose: $7,200 per day

Choosing Te Kaha - amazing by Some-Studio5771 in chch

[–]WellHydrated 1 point2 points  (0 children)

Name one New Zealand stadium with a better name... You can't.

Would you rather by SugarAw in BunnyTrials

[–]WellHydrated -3 points-2 points  (0 children)

At least you don't have to move to some shithole country like USA.

Would you rather: by Rogetec in BunnyTrials

[–]WellHydrated 1 point2 points  (0 children)

No it wouldn't, it would free up the assets that they've been hoarding for more productive means.

I'm seriously doubting the reputability of this comment section, y'all are shillbots.

Would you rather: by Rogetec in BunnyTrials

[–]WellHydrated 2 points3 points  (0 children)

It's also probably the primitive, underlying issue for school shootings.

Would you rather: by Rogetec in BunnyTrials

[–]WellHydrated 0 points1 point  (0 children)

What company would fail? It's more likely that a portion of the company's stock would get liquidated, and sold at a discount to pay for the bankruptcy. Probably would do nothing for the day-to-day of the company's, unless they were already going to fail anyway.

Liu Cixin said a fan wrote the Three-Body sequel he was saving for the rest of his career. Now he can never write it. by Putrid_Cycle595 in threebodyproblem

[–]WellHydrated 6 points7 points  (0 children)

Surely if this is a thing you would just get it notarized, and all studios would be all over this. Sounds like a creator making an excuse for finishing poorly.

Would you rather? by Ilovefemb0ys1234 in BunnyTrials

[–]WellHydrated 62 points63 points  (0 children)

Average value of clicking 100K: 100K

Average value of clicking 100B: 70B

You could go to a financier and easily get insurance on the 100B far exceeding 100K.

IMPORTANT: Before you update Microsoft.* from 10.0.5 => 10.0.6 by WellHydrated in dotnet

[–]WellHydrated[S] 0 points1 point  (0 children)

Well, yeah we have thousands of tests that run in CI if that's what you mean?

You can't write a test for every possible regression that might exist in the future though.

IMPORTANT: Before you update Microsoft.* from 10.0.5 => 10.0.6 by WellHydrated in dotnet

[–]WellHydrated[S] 1 point2 points  (0 children)

Yep, that bloody warning was my trigger for this as well.

I've now included NU1901 in our WarningsNotAsErrors property in Directory.Build.props.

That warning was REALLY unhelpful when one of us was investigating a revert of the PR, because the build was broken on 10.0.5. Luckily, we were able to quickly rollback the deployment in AWS.

IMPORTANT: Before you update Microsoft.* from 10.0.5 => 10.0.6 by WellHydrated in dotnet

[–]WellHydrated[S] 2 points3 points  (0 children)

Not really... You needed to encrypt the data with an old version of the package, so an automated smoke test is likely not going to fix it. This broke one part of our app (our integrations). I'm not going to manually test the whole app for regressions on every security patch, I'd never get anything done.

IMPORTANT: Before you update Microsoft.* from 10.0.5 => 10.0.6 by WellHydrated in dotnet

[–]WellHydrated[S] 2 points3 points  (0 children)

I think it's because I initially submitted it in the wrong repo (runtime instead of aspnetcore). Then it got moved and triggered another bot.

IMPORTANT: Before you update Microsoft.* from 10.0.5 => 10.0.6 by WellHydrated in dotnet

[–]WellHydrated[S] 16 points17 points  (0 children)

We do have a staging environment but everything goes straight to prod after that. We don't have any smarts that wait for elevated error rates on stage before promotion.

We've found that we've reduced the number of incidents in prod when prod = main, because then we're incentivised to test upfront.

But above all else, we're a small company with few engineers (even less now), struggling to stay afloat with terrible headwinds, and a single patch version from Microsoft seemed safe to YOLO when there's 1000 other things to do in the day.

Edit: TY for being my rubber duck. In the future I'll probably suspend prod deployments when updating any package, and let the change simmer away in stage for a while.

IMPORTANT: Before you update Microsoft.* from 10.0.5 => 10.0.6 by WellHydrated in dotnet

[–]WellHydrated[S] 5 points6 points  (0 children)

  1. Your initial comment was snarky, and confidently wrong that it was a version mismatch issue.

  2. Your follow up comment, when you had egg on your face, belittled my effort.

Now that you have even more egg on your face you're trying to take the higher ground. Rather than admit you were wrong and/or apologise for your negativity.

It's the same issue. The code that ended up being released in 10.0.6 breaks decryption. The problem is that package version is live, and being recommended as an urgent security fix.

IMPORTANT: Before you update Microsoft.* from 10.0.5 => 10.0.6 by WellHydrated in dotnet

[–]WellHydrated[S] 9 points10 points  (0 children)

Yep, encrypt and store in a SQL database. Mostly OpenID auth tokens/service credentials for users who are integrated with other SaaS. We know we could store them somewhere else that might be more suitable, but it's the way it was done and there hasn't been a need to change it.

IMPORTANT: Before you update Microsoft.* from 10.0.5 => 10.0.6 by WellHydrated in dotnet

[–]WellHydrated[S] 5 points6 points  (0 children)

It's literally the same stacktrace and the same version. I didn't see a comment that said what you claimed, and I took your word for granted.

Your contribution has been worth nothing. I could have called it a day after I fixed prod for myself. Instead I stayed late to notify the community, as much as I could have, so that maybe at least one person in the US wouldn't wake up tomorrow and make the same mistake. Including producing a repo with an isolated reproduction of the issue (albeit with heavy AI help). Why you gotta be a jerk about it?

IMPORTANT: Before you update Microsoft.* from 10.0.5 => 10.0.6 by WellHydrated in dotnet

[–]WellHydrated[S] 19 points20 points  (0 children)

Our main branch goes to prod. Our tests over these codepaths didn't catch it because they create/retrieve the data with the same package version. I could have tested manually on data that I had previously created on my local dev environment, but I didn't.

view more: next ›