|
Gotta love Jason Statham
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
This scene from Spy[^] is my favorite Jason Statham moment 
Sorry for the bad quality... It's really just him talking anyway 
|
|
|
|
|
He is too violent: I cannot love him.
«When I consider my brief span of life, swallowed up in an eternity before and after, the little space I fill, and even can see, engulfed in the infinite immensity of spaces of which I am ignorant, and which know me not, I am frightened, and am astonished at being here rather than there; for there is no reason why here rather than there, now rather than then.» Blaise Pascal
|
|
|
|
|
I've spent hours, spread over days, on some #$&#$!*@!^#!* issue with Selenium and Protractor.
I had a test that sometimes worked fine (mostly the first two or three times) and most of the times didn't.
Searching, rewriting, waiting, logging, nothing seemed to help... I already found the server looped infinitely trying to get an element on my page.
And just now, I noticed the server always started looping at the same spot (which was pretty hard to see and remember sometimes it didn't loop at all and everything just worked).
So I fetch an element, click a button which removes the element from the DOM and then wait for the element to be removed from the DOM.
I guess sometimes the element removing would be a bit slower and the waiting occurred before the removal (it's all JavaScript multithreading/callbacks/promises, yuk...).
However, when the element would be gone before the waiting commenced the waiting would try to fetch the element to get it's status, couldn't find it, tried to find it again, couldn't find it, tried to find it again...
Fixed by just waiting a second.
So glad I've FINALLY found that issue!
Time to celebrate
|
|
|
|
|
With a glass of DOM perignon, no doubt.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Hold still Mark. We're going to have to hurt you now. 
Software Zen: delete this;
|
|
|
|
|
DOM == Destruction of Sanity
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Brisingr Aerowing wrote: DOM == Destruction of Sanity
Shouldn't that be "Definition of Madness"?
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Coincidentally, "Dom" is also the Dutch word for "Dumb"
|
|
|
|
|
So your "wait to see if the element is removed" would loop forever because it couldn't find the element if the element was already removed?
That is just too weird.
But congrats on finding the problem!
Marc
Latest Article - Merkle Trees
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
Marc Clifton wrote: So your "wait to see if the element is removed" would loop forever because it couldn't find the element if the element was already removed?
Exactly.
Marc Clifton wrote: That is just too weird.
That's why it took me so long to find
Marc Clifton wrote: But congrats on finding the problem!
Thanks!
|
|
|
|
|
Sander Rossel wrote: Fixed by just waiting a second.
Do I understand this right -- you "fixed" the bug by waiting a second instead of polling the element's status?
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
|
Yeah, because polling the element's status wasn't going to work.
Mind you, this is third-party software behavior.
If it were my own I'd fix the infinite loop instead.
Anyway, if this task takes longer than a second that's probably a bug too.
|
|
|
|
|
Sander Rossel wrote: Anyway, if this task takes longer than a second that's probably a bug too.
Or its running on someone else's machine
Poorly written third party software is the worst. Glad you found a way around them.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
|
Had similar problem reading paper tape input where the next read executed before the last read's physical movement had ceased. Wait of 1/10th second fixed it. In 1965 I think.
|
|
|
|
|
Glad to hear it. So everyone's invited to the bar Friday night? Sander's buying!
|
|
|
|
|
Just updated to Update 2.
Now all the code text is black on black.
WTF?
//edit
fixed it by changing the "theme" to "blue" and then back to "dark" in Tools > Options > Environment > General > Color Theme
 
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
modified 10-May-17 16:08pm.
|
|
|
|
|
I am so happy I backed off from this version! I am getting to Like VS 2015 more and more. 
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Give it three years, and you'll be longing for the days of VB6.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I too lost a long battle and had to upgrade to VS 2015 yesterday. I am not really sure what it is doing but it is almost always telling be that it is busy with some background work.
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
I found 2015 bit "heavy" on the machine and went back to 2013 - light, nimble, fast, and does everything needed.
Would be nice is if the new compiler could be retrofitted into the older IDE (like changing engine in a car). New C# got some nice items - not that they are deal breakers but already seeing some of of those new features showing up in posted codez.
|
|
|
|
|
had that "waiting for background task" all the time with VS2015. WTF? If it's in the background then why am I seeing it?
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
Black on black, I want my VB back
It's grey, it's grey, since C# went away, oh oh
What can I do, 'cause I, I'm theme-in' blue
|
|
|
|
|
LOL.
The New Studio
a change comes
black!
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
At least you got it downloaded.
I'm doing the offline install thing, using the --layout command line arg, so it can simply replace the files I already have. But no, that's not what it does...everything it downloads is placed in a folder with a name that contains a version number, so as the download is progressing, I can see the number of folders essentially doubling.
Problem is, it's downloading on a small VHD file (32GB) that I had made just large enough to hold all the files, plus a bit of free space to allow for growth for future versions. But, because files aren't being replaced (just added), the VHD's going to run out of space before the download is done...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
