.42.?

[moosetags]

Does anyone have any idea when Rivian plans a proper update to replace the ill-fated .42 debacle. In my experience with Rivian updates, this is the first time the update process has turned into a goat rope.

Up until now, we have always taken the update as soon as it was offered. Fortunately for us, we were not initially offered .42.0 so we did not experience any of the problems. Then when we were offered .42.1, we were a little gun shy and didn't jump right in. This was a good move as the updated update also had problems and, within a day or two, the update offer disappeared from Opal's screen and the app.

We doubt if we will ever again grab a Rivian update when first offered. Rivian has lost some of our trust.

Brian

Sponsored

 

[Marchin_MTB]

Hate to say it but I also feel like this has shaken overall confidence in the updates. We just returned from a long road trip and I was refusing the update the whole week. It is no longer showing up as available and my guess is that it will be the .46 release cycle when the next one appears.

 

[moosehead]

Good idea to wait and stick with 38 which IME was superb.

No response yet from Rivian on my fungued 2023.42.1 with multiple errors: https://www.rivianforums.com/forum/threads/multiple-errors-update-version-2023-42-1.21454/

I also xposted on Reddit's Rivian subforum and copied Wassym:

Many others report that push notice 2023.42.1 has since been pulled.

 

[COdogman]

WTH is a goat rope?

 

[EBEG]

My 42.1 is fine so far. Having said that, I think I'll wait a bit when then next update is available.

 

[azbill]

WTH is a goat rope?

1. A confusing, disorganized situation often attributed to or marked by human error.
2. A convoluted issue that is contested by many parties.
3. A rodeo event in which competitors attempt to lasso a goat, usually for younger participants

You are obviously a "city slicker".

 

[moosehead]

WTH is a goat rope?

Feeding goat to Trex in Jurrasic Park.

 

[COdogman]

1. A confusing, disorganized situation often attributed to or marked by human error.
2. A convoluted issue that is contested by many parties.
3. A rodeo event in which competitors attempt to lasso a goat, usually for younger participants

You are obviously a "city slicker".

I am. But I have lived close enough to agriculture for most of my life that I thought I had heard most of the lingo that crosses over. I was wrong

 

[DuoRivians]

It’ll be fixed and made ready again soon. I can see the hesitation with not being the first to install an update. But, I wouldn’t generalize this too much.

 

[moosehead]

It’ll be fixed and made ready again soon. I can see the hesitation with not being the first to install an update. But, I wouldn’t generalize this too much.

That's what Wassym said in his 11/15 mea culpa on 42.0 (dorked). We've since had 42.1 (double dorked for some) and 42.2 (to fix 42.0), and are clearly headed to 42.3. While I agree with you it will get figured out, the goat rope analogy is fairly accurate for this particular update series.

It could not have been a great holiday for Rivian SW.

 

[SDH]

I was wondering the same. Didn't want to take the update just before Thanksgiving and now it doesn't appear on the car or the app at all (I have 38.0 and it says I'm up to date).

I reckon they're going to be a bit more slow and steady with futures OTAs now.

 

[Electrified Outdoors]

If I were Rivian, I wouldn't bother any more with .42. I would turn my focus to the December update instead.

 

[moosetags]

WTH is a goat rope?

A goat rope is a similar exercise to herding a large group of cats.

Brian

 

[tcole]

If I were Rivian, I wouldn't bother any more with .42. I would turn my focus to the December update instead.

They still need to fix the bugs though. The version number is probably just tagging a release and running a build. Unless they have some convoluted release train type methodology where they are cherry picking features or fixes between branches. I don't see why they would do that because they don't seem to have any need to support or fix older releases. It's always just fix forward and make everyone upgrade.

Since I seem to love speculating about how they do their software engineering, I would guess they develop on main and create a tag or branch for each release. They could do release hot fixes in that branch, but those fixes are going into main first most likely.

If I were running Rivian software engineering I'd hit pause on new features and have teams invest more in their test and release infrastructure and processes. Then, depending on how hard it is to fix the critical known bugs in 2023.42, push a hot fix asap, and then make the December release mostly bug fixes.

Not that anyone is suggesting this, but also in my experience you really want to avoid slowing down your release cadence. Otherwise you end up with a big backlog of things that should go into a release making the next release really big, and also much more risky. More frequent and smaller units of change are usually safer.

 

[Stevetom84]

I had the .42 update (second iteration) installed on my R1T. Today I took it in to service to have a set of 20” AT wheels/tires I acquired put on and the software update to reflect the change in tire size. Interestingly they had to roll back my software to .38 to get the tire change done. In talking to the service tech, .42 has been pulled completely and I won’t get updated back to .42. I’ll just get whatever the next update is.

I’m good with it, but found it interesting that .42 was pulled completely.

Sponsored