My understanding is that Tesla 16V LV batteries have a similar crash lockout in the BMS that also requires workarounds to reset: https://openinverter.org/wiki/Tesla_16v_li-ion_battery

Manufacturer locked crash resets for BMS are a common theme amongst EVs, especially European ones. Exclusive to neither this model year nor BMW, although some other makes have less arcane procedures than the ISTA one.

> Is this a Part 103 Ultralight?

Well, no, it's in the UK. It also has a gross weight of around 2000lbs, so it's probably not subject to any of the relaxed regulations anywhere, although I don't know how the UK homebuilt rules work these days.

Very bad performance per watt and higher maintenance needs. Bad performance per watt generally means a larger formfactor and more noise as well.

Still susceptible, TPUs need DRAM dies just as much as anything else that needs to process data. I think they use some form of HBM, so they basically have to compete alongside the DDR supply chain.

Here's a patch diff:

https://github.com/vercel/next.js/compare/v15.0.4...v15.0.5

It looks like the fix is checking hasOwnProperty, so it's almost certainly an issue with prototype chain pollution.

I think this is the fix for the React Server: https://github.com/facebook/react/pull/35277/files

It looks like it only affects dynamic reloading? If I understand correctly, the client can just politely ask the server to load arbitrary code, and the server agrees.

This should never be enabled in production in the first place. I'm not surprised that they are fundamentally vulnerable, and this is likely not going to be the last RCE in this part of the code.

Unrelated but... wow, this is... certainly some code.

      return "*" === metadata[2]
        ? moduleExports
        : "" === metadata[2]
          ? moduleExports.__esModule
            ? moduleExports.default
            : moduleExports
          : moduleExports[metadata[2]];

It's generated code ("compiled" Javascript); I found it easier to read than the "main" diff in React which was (intentionally, I think?) obfuscated with additional changesets.

Definitely tough. mmWave radar is useful for this use case; I know Amazon were testing it on earlier drones but I'm not sure if they still use it.

I think it's a typical retrofit outdoor coaxial cable run. The ridiculously haphazard installation method matches my usual experience with cable provider installations, too.

Video: https://www.youtube.com/shorts/089CBuGTkcY (it's also in the article; my ad blocker must have gotten me on this one). Amazon are not having a good run with these lately.

The double crane cable incident ( https://www.cnn.com/2025/10/02/us/arizona-amazon-drones-cras... ) and the LIDAR failsafe issue ( https://www.bloomberg.com/news/articles/2025-05-16/amazon-re... ) were both rather surprising from a process and management standpoint. This issue seems more like a run of the mill "problem with drone delivery conceptually" that Amazon will have to deal with.

I half expected the shared clip to be this scene from Pluribus: https://youtu.be/r3D3dg23tyA?t=129

That scene really cracked me up. The show is shot very well. It's good to have Vince Gilligan back on the TV again.

> not sure why it's not linked that I can find in the article from the same source?

the point is not news, its to keep you on their sites as long as possible with no escape

Link with playback controls: https://youtube.com/watch?v=089CBuGTkcY

The article contains the exact same clip without edited audio.

I think my ad blocker must have filtered the element. Post updated, thanks.

I suspect this too; between licensing and ads I bet there's a "screen type" (mobile vs. fixed/TV) that needs to be "correct" for some contract reason, and casting is skewing their numbers enough that someone called them on it.