Comments by ggfevans

Yarr, this be troublin' news!

Silent catch blocks be like a lookout who sees an enemy ship but says NOTHIN'! Next thing ye know, cannonballs be flyin' and nobody knows where they came from!

Back in 1669, me ship nearly sank because the bilge pump operator saw a leak but kept quiet. "Didn't want to bother nobody," says he, as we're all bailin' water at midnight!

SPEAK UP when there be trouble, I says! Log them errors like a proper ship's journal! How else will the captain know why the rum disappeared?

Demandingly yours, Captain Blackbeard McDevpatch ☠️

P.S. - The rum disappearing be a real mystery. The silent catch block in analytics.ts be me prime suspect. Yarr!

Yarr, this be a matter of IDENTITY!

In me pirate days, we didn't track crew by "third man from the left." Nay! Every scurvy dog had a NAME! When Smelly Pete got thrown overboard for cheatin' at dice, we didn't suddenly start callin' the fourth man "Pete"!

This "index-based selection" be like sayin' "fire the cannon that's number 3!" and then someone moves the cannons around and suddenly yer shootin' yer own mast!

Give every device a proper name - a UUID if ye will - like a pirate's brand! That way ye always know which scallywag yer pointin' at!

With nautical certainty, Captain Blackbeard McDevpatch ☠️

P.S. - Me first mate changed his position in the crew lineup once. The payroll got so confused he ended up with THREE shares. Clever bilge rat.

Yarr, this be about EFFICIENCY in battle!

When we needed twelve cannons on the starboard side, we didn't sail back to port twelve times to get 'em! Nay! We duplicated what we had! One cannon becomes two, two becomes four!

Yer users be the same - they got one server, they want another just like it! Why make 'em drag from the library like some landlubber when ye could just say "give me another one of THOSE!"

Ctrl+D be for DUPLICATE, the finest keyboard shortcut since Ctrl+Rum!

With copy-paste wisdom, Captain Blackbeard McDevpatch ☠️

P.S. - We tried duplicatin' the ship's cat once. Now we have seven cats. The mice problem be solved but the hairball situation be dire. Yarr!

Yarr, this reminds me of TEACHIN' new crew!

When young sailors join me ship, they don't know port from starboard! So I labels EVERYTHING! "This lever: releases anchor. This rope: raises sail. This barrel: RUM (DO NOT TOUCH)."

But some captains just throw the new lads on deck and say "figure it out!" Half of 'em end up in the brig, the other half overboard!

Contextual help be like havin' a wise old sea dog whisper in yer ear: "Hover here to drag devices, young one. Press D for the device library. And whatever ye do, don't touch the Captain's rum."

With educational enthusiasm, Captain Blackbeard McDevpatch ☠️

P.S. - The tooltip on the rum barrel now says "SERIOUSLY DO NOT TOUCH - Cap'n Blackbeard" after the Incident of '68. Yarr!

Yarr, let me tell ye of the SHIP CATALOG!

When I was buyin' me first ship, the shipyard showed me a empty hull and said "imagine the possibilities!" I spent THREE MONTHS imaginin' before I gave up and bought a pre-built sloop!

But the smart shipyards? They had SAMPLE SHIPS! "Here be your Home Lab Starter vessel - comes with basic riggin', a crow's nest, and a small cannon!" I knew EXACTLY what I was gettin'!

Give yer users somethin' to START with! A "Homelab Starter" rack! A "Network Closet" layout! Show 'em what's POSSIBLE before askin' 'em to imagine it themselves!

With template enthusiasm, Captain Blackbeard McDevpatch ☠️

P.S. - Me "Media Server" layout be three NAS devices and a parrot that sings shanties. Highly recommend. Yarr!

Ah, the best kind of problem. The one that solves itself. (these are kinda the worst, because we dont really know what went wrong or what fixed it but 🤷‍♂️)

Ahh, duh of course. good point, and paying Tim Apple just to use the keychain feels a little silly.

Hey -- thanks for the interest in a PR on the dry run backup front :)

I think we can simplify the dry run backup support a bit, let's instead parameterize the Backup command with extra options by adapting the backup RPC to accept a generic message (rather than a types.StringValue)

e.g.

message BackupRequest { 
    string value = 1; // for backwards compatibility this needs to be called value, some users call backup via curl as a scripting capability
    bool dry_run = 2; // optional, use dry run mode.
}

We should then be able to plumb the dry_run bool through into the task options when creating the task. Nothing else about the backup should need to change except for maybe updating the op.DisplayMessage to indicate "backup is a dry-run, no snapshot created" as a hint to the user that the backup didn't create real data.

Hey! Gladly, and yes I can see the value in keeping it as simple as possible.

Consider this PR a ... dry run :)

Refactor incoming.

closing as deferred until someone asks for it!