nuttertools

With ‘google_cloud_run_v2_service’ I’m seeing 2 issues with volumes and 1 of them I don’t follow.

1. Inside the ‘template’ block there are two ‘volumes’ blocks. The docs and google provider 6.30 both agree these are blocks. The problem is on every run the content of these two blocks switches despite having unique ‘name’ properties. Is my expectation that a nested argument is keyed and deterministic correct here? Other arguments do not behave this way but it seems to me like this is a TF state issue not a provider implementation thing.
   An abomination dynamic block where the types share no content in common might pinpoint state vs provider. What would your next troubleshooting steps be

All my devices suddenly started freaking out. Hard locking, power loss, HTTP server failing, occasional connection to cloud but Cloud API commands not changing device state.

See in logs that iot.shelly.cloud is redirecting to shelly-52-eu.shelly.cloud which is not a geo-region near me. Also see the message “Server keys do not exist”.

Anyone else have sudden onset schizo devices or loss of cloud connectivity?

Solved: This is a well-known issue with meanwell supplies used in lighting applications. The LPV series is unsuitable to power most PWM controllers and this is applicable to a variety of other meanwell class II products. Grabbed a no-name/rebranded junk that is not class II and it works great.

EDIT: Direct-wire no whine and the controller is terrible. Still don’t understand the whine.

Used a Meanwell LPV-60-24 with a PWM controller and the supply makes a very loud whine at all duty cycles (some wine at 100% too). Is there a characteristic I missed and need to be looking for within the LED Driver class of power supplies or did I just pick cheap crap?

Have been using a no-name l

What router should I buy for a best-case ideal Shelly connectivity experience? Devices just don’t stay online and every day I’m resetting something. No pattern aside from 1 device that actually is in a poor area for reception.
Ideally I would buy whatever router Shelly is testing against to remove any potential router issues. This would be dedicated for just Shelly devices so there are no other considerations.

I get all the usual Shelly stuff, lighting in infinite reboots, sockets hard locking, devices rebooting causing other devices to start looping, yada yada. I need whatever “the” vendor recommendation is so I don’t continually get the expressif WiFi bug run-around. None of my othe

When you get the blue update popup of impending doom is there a way to cancel it for a set period other than just catching the popups?
I wouldn't want to damage any systems, any measure should at worst require a restart to resume normal operation.
The scenario is my workflow interruption being...fml let's say high, but so rarely interrupted it's not worth adding inefficiency to improve loss on update.
Ideally I'd find some quick hacky fix like a localhost update server or a way to crash windows update.

Any ideas?

Just pulled a 1TB barracuda and there was a stabilizing force so great I nearly dropped it. Have I just been pulling drives carefully my whole life and that's expected or is spinning fast enough to act as a gyroscope not expected 5 seconds after pulling?

I sincerely doubt that M$ forgot to assign a record for office and www.office. Is there some kind of user facing component that allows [email protected] to be delivered that requires this?
Related does anyone have a set of general logic they are proud of that handles neutral SPF from major companies or is the logic really domain by domain.

iPhone 6S
Swapped my broken screen out but some magic smoke escaped.
Done enough testing now to say that everything works fine, except the backlight is completely off save for a few seconds here and there were it lights up. It is often in motion when the light does come on but I've done a lot of pressure testing now with no backlight success. I have had iPhones with bad backlights before and this is not the same, flashlight reveals nothing but direct sunlight I can just make out icons and movement.
Pretty sure whatever drives the backlight got fried when I was attaching the new screen (left battery plugged in). Speaker good, loudspeaker good, mic good, home button good, flashlight goo

Just replaced the screen on my 6S and from the first boot the screen will only light for 2-3 seconds every few minutes (variable).
When plugging in the digitizer cable it got hot for a second and I smelled something magical, no actual smoke though. Thought I saw a pin on the board connector red hot for a microsecond, but there was no residue in the area and it might have been my imagination.
Can interact with the screen fine, charge fine, power off, really everything but actually see what I'm doing.

Would very much appreciate some help on what to start checking first, hopefully I've done something obvious...

There was one thing of note on my disassembly, the screw holding the L

I just can't wrap my head around this one.

Windows 7 Pro on an iMac 14,1. No do not tell me anything about Bootcamp, reproduced on a flat install with latest vendor drivers.

Initially this looked like a bad disk so I ran an extended self-test. Passed and SMART values actually looked quite good, nothing near maximum values and nothing remapped.

What keeps bringing me to disk is... A) This is exactly how a system acts when the drive has no spare sectors but needs to remap. Counterpoint is that this seems to intermittently be all applications and files instead of a specific subset of files. Not really a counterpoint if something is up on the disk and part of windows itself is stored there. B

EDIT: kind of important to say this is w10 Professional, not enterprise or education.

I'm finding the never ending configuration maintenance on w10 for my personal machine cumbersome bordering crazy.

An hour into DSC and I'm not seeing any reason to use it. Seems like I will have to create so many resources that a simple script might actually do a better job. Is there something major I am missing that is an advantage of DSC over more mature tools like puppet? I do like the pretty much zero configuration to get dsc running on a fresh install but that is also true of a script...

I'm coming up on day 100 of phantom cookies which should be 70-77 days. Consensus seems to be not too strange, don't harvest early. I'm getting concerned though as I havn't seen any growth since ~60. I have a lot to correct next round so I'm not really looking for how to not get into this boat again, just whether it's a lost cause.

Sorry for this being so scattered and w/o pics, I'll post an actual post-mortem once the new batch is going.

For 4 weeks I've been saying another week but I'm worried they may have been so shocked that it's a lost cause. Any suggestions on whether giving them more time is worth it greatly appreciated.

First grow 4x2x5 tent 6 plants dwc in a 17gal storage tote (

I either don't know something's about the Windows 7 activation process or have something very wrong with my deployment chain. I don't believe the only idea I have, any alternate ideas?

Restored partition image to new partition (I don't sysprep, don't care about sids) and proceeded through my configuration diffs. I definitely did not touch licensing. Go to activate and it's already activated with the right OEM_COA_SLP key for this machine!

The only thing I can think of is the image was prepared on this machine and had the key added and activated before imaging. There are a lot of machines running this image so the odds of that are pretty long.

EDIT: For shits and giggles I just launched of

Started off my day with finance and operations blowing up my inbox about how they can't run payroll as the reporting system is missing everything from yesterday.

I figure fuck, something went wrong with the year changeover. 2 hours later still can't find a problem, must be the remote source system, right? Take a look at that and wouldn't you know, no data from yesterday.

Before starting an all day shouting match with that systems maintainer, asked the person across from me "were we open yesterday?"

Had to tell the CFO and COO that the reason there is no data from yesterday is that we were not open yesterday and the cost to determine that was 2 hours of my day.