|
The weight is important - it stops the elliptical cam gradually sliding up the beam shaft and catching on the flange rebate, with disastrous results as you can no doubt imagine.
"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!
|
|
|
|
|
Hmmm,
After reading this thread I'll need to perform the AshkEnte. 
|
|
|
|
|
Don't disturb HIM if he is at another cocktail party ...
"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!
|
|
|
|
|
|
I'm sorry for your small python problem, but the solutions in your e-mails don't work either. Consider that the world average is not that big either and there are a lot of ways you can compensate for that.
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Change 'upper' to 'lower' or "l" & "k" to "L" & "K".
|
|
|
|
|
there you went and spoiled all the "fun"
To err is human to really elephant it up you need a computer
|
|
|
|
|
So I just had to move some Azure resources from one subscription to another.
Started with my development environment and everything went well.
Did the test environment and everything went to hell.
Application didn't start... Just not at all.
Checked the logs, nothing.
Checked additional logs, nothing.
Checked some other services that I had deployed, all worked.
Did a fresh release from my build pipeline, nothing.
Checked every setting my application needs, nothing.
Did a fresh release from Visual Studio, nothing.
Decided to try a debug build from Visual Studio... And all worked as though nothing ever happened!
Set it back to a release build and all kept working.
Did a re-release from my build pipeline and all is fine.
What the ![Elephant | [mastadon]](https://www.codeproject.com/script/Forums/Images/elephant.gif) was the problem!?
This thing just cost me a couple of hours, what the , Mickeysoft!? 
|
|
|
|
|
Between your post and raddevus', I think Mercury is in retrograde. And maybe more than one planet!
|
|
|
|
|
At first I thought you meant the source control, but that's called Mercurial.
Maybe I should take some distance from programming 
|
|
|
|
|
Comfort (or not): I thought that too at the first glance.
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
This seems like a situation where you have put something back together, it works, and there are parts left over.
It makes me uneasy.
To err is human. Fortune favors the monsters.
|
|
|
|
|
He didn't sacrifice the right chickens. It will blow up on him in the future.
|
|
|
|
|
I've done that with motorcycle engines.
"What's that spring? Shouldn't it be in there somewhere?"
Engine runs fine, so ignore it.
Gear change return spring: can change up, but not down ... discover this a mile away from home, in top gear. Balls. Did not make that mistake again!
"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!
|
|
|
|
|
Yes, it feels that way and it doesn't sit right with me either.
Nothing I can do about it anymore though.
Hopefully I'll be able to locate the problem sooner when (not if) it happens again in the future 
|
|
|
|
|
Sincerely, I wish you the best of luck there. 
To err is human. Fortune favors the monsters.
|
|
|
|
|
Could it be an accidental rebuild all proces clogged in mystery which did the job?
Probably I'm approaching this too simple. No offense (ever) meant
|
|
|
|
|
Mystical elephants disguising themselves as unicorns...again. Fairly certain that is your problem.
There really is no solution for this. Well, there is, but I can't mention it here.
modified 6-Apr-22 12:52pm.
|
|
|
|
|
Slacker007 wrote: There really is no solution for this. Well, there is
As an old coworker of mine once said to another coworker "You know what you should do? You should go and get a job in health care."
I guess it would make this problem go away, sort of.
Slacker007 wrote: here
I see what you did their 
|
|
|
|
|
Sander Rossel wrote: I see what you did their
|
|
|
|
|
My guess is that it thought the build was already deployed in the new subscription.
Same hash, no reason to deploy?
Switching to debug changed all of items so it had to deploy?
|
|
|
|
|
Don't know.
It should've been deployed.
Did the same to my DEV environment without problems, but it broke in TEST.
Maybe the debug build added some missing file that TEST somehow doesn't add.
Who knows, and no way to know now
|
|
|
|
|
This probably isn't very helpful, but your story has further cemented my resolve never to use "the cloud" for development.
|
|
|
|
|
I've had such issues on on-prem servers as well.
Heck, I've had weird stuff like that during debugging on my development machine.
Ask yourself if you're not just a cloud-hater grabbing every opportunity to hate the cloud
|
|
|
|
|
I've also had weird problems like that on my own machine too but I feel (possibly unreasonably) that I have more control when my machine is right here.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
