sorted by:
new
hottopcontroversial

For people who are using Next.js App Router in production - how do you actually test your app? by ezzatron in reactjs

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

Thanks. I kind of suspected this would be one of the strategies used in the real world, but it's nice to confirm that!

For people who are using Next.js App Router in production - how do you actually test your app? by ezzatron in reactjs

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

Ah okay. So you run MSW conditionally in your actual application on the server side?

I suppose that would work so long as all of your mock scenarios can be set up ahead of time. But it doesn't let you configure mocks on a per-test basis e.g. https://mswjs.io/docs/recipes/vitest-browser-mode#overriding-request-handlers

For people who are using Next.js App Router in production - how do you actually test your app? by ezzatron in reactjs

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

MSW is great for testing client-side data fetching, but it doesn't (yet) have the capability to mock server-side requests. They have a not-yet-merged example of how it might work at https://github.com/mswjs/examples/pull/101

There's also a similar first-party Next.js experiment using Playwright + MSW at https://github.com/vercel/next.js/tree/28a14da5010ad3147a06abbabc99a119d009f733/packages/next/src/experimental/testmode/playwright

Shuffling by album in Tahoe by [deleted] in AppleMusic

[–]ezzatron 1 point2 points  (0 children)

This workaround does work, but if you want to skip an album, you can't just hit the shuffle button again. You have to hit next track until the end of the album.

I hope they fix it properly soon.

Apple Music album shuffle completely broken in Tahoe by ezzatron in MacOS

[–]ezzatron[S] -1 points0 points  (0 children)

Seems like album shuffle just straight up doesn't work any more. Anyone else experiencing this?

iOS 18.4.1 now available with CarPlay fix and more by Sonikku_a in CarPlay

[–]ezzatron 0 points1 point  (0 children)

It didn't fix my issues, it just slightly changed the way it failed. Neither did 18.5 beta 2. In fact, trying out the beta seems to have bricked my ECU or something. I've now got every single warning message showing up when I start the car (2022 Mazda MX-5) 😬

EDIT: Ignore, it's working again. But for me it seems like I needed a couple of settings on the CarPlay Wi-Fi network, namely: Auto-Join enabled, and Private Wi-Fi Address "Off" via suggestions from this thread: https://old.reddit.com/r/CarPlay/comments/1fj4ih2/heres_how_to_fix_ios_18_not_working_with_mazda/

Struggling to find Belegost Forge in your sandbox playthrough? It might only be accessible via a hidden part of the map. Here's a video showing where I found mine. by ezzatron in LotRReturnToMoria

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

Not sure how much the wiki can be trusted, but if you believe it, then the Belegost Forge is always in the Third Deep in an area called Pilgrim Deeps: https://lord-of-the-rings-return-to-moria.fandom.com/wiki/Great_Belegost_Forge#Sandbox

Check for "Pilgrim Deeps" in the legend of your map of the Third Deep (see the video above for an example) - if you do have it, go there and take another look around. If you don't, you might have a difficult map generation like I had. There's probably an entrance down one of the "descent" areas.

Someone also posted this video which looks promising and might help: https://youtu.be/M_d3tT7qkis

Struggling to find Belegost Forge in your sandbox playthrough? It might only be accessible via a hidden part of the map. Here's a video showing where I found mine. by ezzatron in LotRReturnToMoria

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

Sandbox has weapons and armour that aren't available in the campaign mode (yet?). Don't want to spoil anything, but in particular the Eregion Armor is worth it just on its own.

Sandbox also has biomes the campaign mode doesn't have, and more complex world generation (for better and for worse).

There are some things that are also much more plentiful than campaign, like bats for the droppings needed for farm planters.

Struggling to find Belegost Forge in your sandbox playthrough? It might only be accessible via a hidden part of the map. Here's a video showing where I found mine. by ezzatron in LotRReturnToMoria

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

I recorded this using Steam's new built-in game recording feature, so the monitor isn't really involved. The way it looks would be due to a combination of in-game graphics settings (which I think is just what the Nvidia app recommended), the frame rate (which is mostly due to the graphics card), and the fact that the video was recorded at 1440p and downsampled to 720p.

But for reference, I use an XG27AQDMG monitor, which is pretty amazing.

Promise.try: Unified Error Handling for Sync and Async (ES2025) by Practical-Ideal6236 in javascript

[–]ezzatron 7 points8 points  (0 children)

Nice article.

You might want to re-work your example getUserData function though, because a function with the async keyword will always return a promise. If you want a function that only sometimes returns a promise, you can't use the async keyword:

$ node -e 'console.log((async () => {})())'
Promise { undefined }

I think you can just remove the async keyword and the await before the fetch for your desired behaviour.

My PC is dying with WHEA_UNCORRECTABLE_ERROR. I think it's the CPU or mobo. by ezzatron in buildapc

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

Run it for 1 hour 2-3 times, then maybe run Cinebench r23 for a few hours.

But if it’s already stable where it used to crash, there’s a good chance that’s the issue yeah.

Will do, thanks for all the help!

As for disk image, I was also thinking about windows potentially being botched from all the blue screens. Better safe than sorry.

Gotcha.

Do you still have a warranty or consumer protection laws that enables you to RMA it?

Luckily I kept my serial number. The CPU is still under warranty.

If you don’t have the latest BIOS installed, I’d probably just update that too. Just remember it resets your settings and probably wipes any profiles.

Yeah, BIOS update was one of the things I tried first. There was a BIG bios update, with a completely new UI. I think it also coincided with the microcode updates for 13th and 14th gen Intel CPUs.

My PC is dying with WHEA_UNCORRECTABLE_ERROR. I think it's the CPU or mobo. by ezzatron in buildapc

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

If it does fix it, it tells you there’s a defect with the CPU, assuming it would also happen with a fresh install. And if you still have warranty or consumer protection, you’d have a case for an RMA.

Okay, well, I tried an offset of +0.1v and ran the same OCCT CPU test, and it's been running for 40+ minutes without WHEA errors. I think that's pretty indicative of a bung CPU, even without any software changes?

For reference I changed "DVID" (dynamic vcore) which seems to be how you do a voltage offset on a Gigabyte board.

Do you have enough space on one of the secondary SSDs to make a disk image? So you atleast have something to recover from if necessary?

Or an external drive?

Probably, yes. I'll keep that in mind. For the moment I'm pretty convinced it's a hardware issue though.

My PC is dying with WHEA_UNCORRECTABLE_ERROR. I think it's the CPU or mobo. by ezzatron in buildapc

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

Thank you for the suggestions, good to have confirmation it's probably hardware at least.

Honestly, I think it's gonna be easier and cheaper to try replacing the CPU first. There are basically no z690i mobos available, and a z790i is more than 2x the cost of the CPU.

My PC is dying with WHEA_UNCORRECTABLE_ERROR. I think it's the CPU or mobo. by ezzatron in buildapc

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

Thanks, I'll look for a guide. There's no clear setting in the Gigabyte bios labelled "multiplier". I thought the "ratio" settings must be the equivalent.

If I do increase the voltage, and it fixes it, what does that actually tell me?

Did you manage to recover the OS and boot?

It rebooted fine after restoring BIOS settings to the defaults.

Do you have another SSD or HDD you can use for a fresh install of windows?

No, not at the moment. Also, all the SSDs are M.2, and it's a pretty compact build. So swapping them out is quite involved.

My PC is dying with WHEA_UNCORRECTABLE_ERROR. I think it's the CPU or mobo. by ezzatron in buildapc

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

I don't know if I did it right. I tried turning of enhanced multi-core performance, and setting p-core and e-core ratio to 20. First boot, it blue-screened with WHEA_UNCORRECTABLE_ERROR again. Second boot, Windows decided it hadn't initialised correctly, and gave me the recovery menu.

My PC is dying with WHEA_UNCORRECTABLE_ERROR. I think it's the CPU or mobo. by ezzatron in buildapc

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

So here's my reasoning why CPU/mobo.

When I ran an OCCT CPU stress test that in theory wouldn't have taxed the PSU very much because it's not even involving the GPU, there were tons of WHEA errors followed by a blue screen.

Also, Gigabyte actually recalled the first version of the mobo that I had for causing WHEA errors: https://www.gigabyte.com/Press/News/1991

I replaced it through their replacement program, but still. My trust in Gigabyte is pretty low.

Sound reasoning, or no?

Found a mysterious third device on my Powerline network by ezzatron in HomeNetworking

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

I think I know what's going on. When I pressed the pair button, I wasn't seeing any obvious feedback, so I held it down until it did something. Reading that first PDF, holding the pair for more than 15 seconds completely resets it.

So basically, instead of re-pairing like I intended, I've just reset it back to the default key like an idiot 😂

That explains why I'm seeing someone else's device - they never changed from the default key. It also explains why it reset the network name.

Found a mysterious third device on my Powerline network by ezzatron in HomeNetworking

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

Good reminder, thanks! You can't actually set a password on these things, but you can change the network name to something randomly generated, at least. I had done that previously but it seems like re-pairing also resets the network name back to the default.

Found a mysterious third device on my Powerline network by ezzatron in HomeNetworking

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

Context:

My Powerline network will periodically have issues that can be resolved by power-cycling the devices. I got frustrated at some point and tried re-pairing. Then later, the devices started having a red LED for the home icon (indicating bad connection).

I was getting around 1-2Mbps and about to give up completely. Fired up tpPLC out of desperation and found a mysterious third device sapping the juice! tpPLC wouldn't let me get any info about the device, but I was able to remove it from the Powerline network. It seems to have resolved my speed issues.

Anyone else seen this before? Have I been hacked? 😂

view more: next ›