|
1. The lounge is for the CodeProject community to discuss things of interest to the community, and as a place for the whole community to participate. It is, first and foremost, a respectful meeting and discussion area for those wishing to discuss the life of a Software developer.
The #1 rule is: Be respectful of others, of the site, and of the community as a whole.
2. Technical discussions are welcome, but if you need specific programming question answered please use Quick Answers[^], or to discussion your programming problem in depth use the programming forums[^]. We encourage technical discussion, but this is a general discussion forum, not a programming Q&A forum. Posts will be moved or deleted if they fit better elsewhere.
3. No sys-admin, networking, "how do I setup XYZ" questions. For those use the SysAdmin[^] or Hardware and Devices[^] forums.
4. No politics (including enviro-politics[^]), no sex, no religion. This is a community for software development. There are plenty of other sites that are far more appropriate for these discussions.
5. Nothing Not Safe For Work, nothing you would not want your wife/husband, your girlfriend/boyfriend, your mother or your kid sister seeing on your screen.
6. Any personal attacks, any spam, any advertising, any trolling, or any abuse of the rules will result in your account being removed.
7. Not everyone's first language is English. Be understanding.
Please respect the community and respect each other. We are of many cultures so remember that. Don't assume others understand you are joking, don't belittle anyone for taking offense or being thin skinned.
We are a community for software developers. Leave the egos at the door.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
modified 16-Sep-19 9:31am.
|
|
|
|
|
Wordle 332 5/6
⬜⬜🟩🟨⬜
🟨⬜🟩⬜⬜
⬜🟩🟩⬜⬜
⬜🟩🟩🟨🟨
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 332 4/6
⬜⬜🟩⬜🟨
🟨⬜⬜⬜⬜
🟩⬜⬜⬜⬜
🟩🟩🟩🟩🟩
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
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.
|
|
|
|
|
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.
|
|
|
|
|
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've been thrown into the deep end to learn Google's People API. It seems that 99% of the documentation is Google's, which isn't as complete as I figured it would be.
Are the any other resources that I can look into? I need entry level docs.
Thanks
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
try one simple demo to pull just one person to play around ...
diligent hands rule....
|
|
|
|
|
|
I'm working on an app that uses it and it's giving us trouble with oAuth & scopes, so I'm looking for a resources outside of what Google prodvides.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
better ask at stack overfloe what u really face as issue
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
|
|
Yes I have.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Recently a cargo ship with thousands of expensive cars sank and the treehuggers are howling now about the environmental hazard posed by the cars. Am I stupid or are they? Whatever fuel may be left in the cars, it's a joke against the fuel oil in a wreck of this size. And does that not also go for every sunken ship, and not only for one loaded with cars?
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.
|
|
|
|
|
Certainly a lack of perspective, not necessarily stupidity. On their part, not yours.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
