|
Wordle 332 5/6
⬜⬜🟩🟨⬜
🟨⬜🟩⬜⬜
⬜🟩🟩⬜⬜
⬜🟩🟩🟨🟨
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 332 4/6
⬜⬜🟩⬜🟨
🟨⬜⬜⬜⬜
🟩⬜⬜⬜⬜
🟩🟩🟩🟩🟩
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Wordle 332 5/6
⬛⬛⬛⬛🟨
⬛⬛🟨⬛⬛
⬛🟨⬛🟨⬛
⬛🟨🟨🟩⬛
🟩🟩🟩🟩🟩
|
|
|
|
|
A good choice of first word for me:
Wordle 332 3/6
⬜🟨🟨🟨⬜
⬜🟩🟩🟩⬜
🟩🟩🟩🟩🟩
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Wordle 332 3/6
⬜⬜⬜⬜🟨
🟩🟩🟨🟨🟨
🟩🟩🟩🟩🟩
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
Wordle 332 5/6
⬜⬜🟩🟩⬜
⬜⬜🟩🟩🟩
⬜⬜🟩🟩🟩
⬜⬜🟩🟩🟩
🟩🟩🟩🟩🟩
GAH!
|
|
|
|
|
Wordle 332 3/6
🟩⬜⬜⬜⬜
⬜🟩🟩🟨🟨
🟩🟩🟩🟩🟩
Somewhat lucky second guess...
|
|
|
|
|
Wordle 332 5/6*
⬜⬜🟨⬜🟨
🟨🟩⬜⬜⬜
⬜🟩⬜🟩⬜
⬜🟩🟩🟩⬜
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 332 3/6*
⬜⬜⬜⬜🟨
🟩⬜⬜🟨⬜
🟩🟩🟩🟩🟩
Happiness will never come to those who fail to appreciate what they already have. -Anon
|
|
|
|
|
Another lucky day!
Wordle 332 2/6
⬛🟨⬛⬛🟨
🟩🟩🟩🟩🟩
Get me coffee and no one gets hurt!
|
|
|
|
|
I'm just figuring out all the neat stuff i can do with it. Like octocoupling a circuit to prevent a ground loop, with just a tiny IC chip. =)
Turns out I can build a reliable MIDI breakout without the pain of a non silicon based coupler like they used to use.
I know it's not new tech, but it's new to me, because I'm relatively new to *this*.
I actually picked up circuit building 2 years before I started coding, but once I learned to code I put it down because it was hard to keep myself in materials at such a young age. Software is vapor, once you have the machine.
To err is human. Fortune favors the monsters.
|
|
|
|
|
Careful! The blue ringed octopus has no less than two deadly poisons, When it octocouples you, you are done.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
hahaha I meant optocouplers.
To err is human. Fortune favors the monsters.
|
|
|
|
|
Who would have thought.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
I first thought you meant the wonders of silicone. (Did some plumbing recently; don't try without it).
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
That stuff is pretty handy too, but it never does anything exciting when I apply current to it.
To err is human. Fortune favors the monsters.
|
|
|
|
|
That depends very much on where the silicone is implanted.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
So, why? Well, I bought a new phone from (whisper it) Amazon back in December. It's a Nokia G20, and it's great. But, after I'd had it for a few days it wouldn't power up one morning so I sent it back for repair.
(Time passes, no sign of it being returned to me, working or otherwise.)
So, tl;dr; Amazon gave me another one.
(Time passes, and meanwhile I learn that all G20's sometimes do this and will only come back on if you hold down the power button for like 3 days. Conclusion: old phone was working fine all along. Hey-ho.)
And then, nearly FIVE MONTHS after I sent it back, guess what? Yep, here it is, back from the great beyond. Bizarre.
So now I have two (even down to them having identical cases - more fool me), and of course I'm always picking up the wrong one. First world problem. But we plan to give one to my mother-in-law so that she can watch the tennis, so it's an ill wind etc. Result.
And thanks to all for putting up with bipolar me. I'll try to keep a lid on things when times are bad.
Paul Sanders.
Some of my best work is in the undo buffer.
|
|
|
|
|
So.. I take it the G@0 is a good phone hey? mmm.... I was thinking I might buy a new one before end of next year...
|
|
|
|
|
Not sure if that's a serious question, but yes, if it's man enough for what you want to use it for it's excellent. Specs are modest but it does everything I want, the battery lasts for 2-3 days, and it has what, for me, is a must-have, to whit a micro SD card slot. If you direct all your photos and vids there, 64 GB of internal storage goes a long way. 'Amazon Basics' cards seem to work well. Avoid the cheapies.
Android 11, two years of updates (IIRC), £130 odd all-in, what's not to like? I have no affiliations to disclose.
Question: how do you get that clickety thing in your post?
Paul Sanders.
Some of my best work is in the undo buffer.
|
|
|
|
|
nice. price seems alright as well!
probably will wait next year and his successor... but we'll keep an eye out for Nokia now!
|
|
|
|
|
Yes, it's a bargain.
Paul Sanders.
Some of my best work is in the undo buffer.
|
|
|
|
|
So I have this problem with an Azure Function.
It's triggered by a Service Bus queue.
The normal flow would be:
1. Message gets posted on the queue.
2. Function picks up the message and start processing.
3a. If message is released before Function exits, Function auto-renews lock.
3b. Repeat a until Function exits.
4. Function exits and marks the message as completed.
5. Message is removed from the queue.
What happens:
1. Message gets posted on the queue.
2. Function picks up the message and start processing.
3. Function does not auto-renew lock and message gets processed again.
4. Function exits, but does not remove message from queue.
5. Message is ultimately moved to dead-letter queue.
Apparently, the problem is that when a Function's CPU's usage goes above 90%, it starts acting weird (which is mentioned nowhere)
The CPU, over which I have zero control, is the problem.
It doesn't throw an error, it just runs correctly and acts weird in the background.
Now Microsoft wants me to update to a plan that's $150 a month (from a few bucks now) for a process that runs less than five minutes a day
Just limit CPU usage and double the time my Function runs
|
|
|
|
|
Can you limit it yourself? Make your code less demanding at a time? Maybe spin off a task on a low priority thread, or sleep it periodically or something?
To err is human. Fortune favors the monsters.
|
|
|
|
|
I'm not sure how to make my code less demanding.
It's just a foreach with some 4000 records, that I put in an Excel file (ultimately a huge XML string).
I'm using Spreadsheetlight for this.
I'm not multi-threading or anything, for as far as I know (I don't even think Spreadsheetlight is thread-safe).
I could use a Thread.Sleep, I guess, but it also need to finish in 10 minutes max because of the Azure Functions limitations.
The task as a whole only takes about three minutes right now (and runs to completion, which is why it's even weirder it still fails).
|
|
|
|