|
"Immortality kills web site"
Read all about it in tomorrow's Insider...
|
|
|
|
|
Hmmm, I can't seem to reply to your message. Let me try again...
|
|
|
|
|
So, I could reply with that message, but not with some other messages I tried. I wonder if perhaps the I couldn't reply based on something in the message. Let me try that again...
|
|
|
|
|
Luc Pattyn wrote: Immortality kills web site
There can be only one.
|
|
|
|
|
Finally, I was able to reply with that message... that was the message that wouldn't quite take when I tried to reply with it.
|
|
|
|
|
Whatever you're on, I suggest you reduce the dose.
|
|
|
|
|
You post just a few messages about a higher dimensional immortal black hole super being, and people think you're on something. And yet nobody says anything when somebody mentions the concept of God.
|
|
|
|
|
You're right, there are simpler explanations for the thread you composed almost single-handedly.
|
|
|
|
|
This sounds like a network issue, not a code issue. If the page times out then we show a message saying something clever, witty, and helpful like "The command timed out".
You obviously know there's database timeouts, execution timeouts, and then network timeouts. If the network timed out then the browser may simply just present a big fat nothing.
I've checked the error logs and there's not a single record of any timeouts (page or data) ocurring.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Interesting. I'm not really sure what it could be. I wouldn't think it is just a random network issue, as there was completely valid HTML returned. Only, that HTML didn't contain any visible content. Would seem strange for that to be a network issue, especially considering another member experienced the exact same issue and I myself experienced it twice and only with messages which took me a long time to compose.
Oh well, perhaps I'll try to reproduce it tomorrow and send you some steps to reproduce.
|
|
|
|
|
I was able to reproduce it.
I picked one of my old messages in the lounge. I clicked reply, waited 30 minutes, then posted the reply. This posted just fine.
I then replied to that reply, waited over an hour, then posted the reply. This FAILED to post (got the blank page). I then modified the message and posted it without delay here.
So it looks like the trick is to spend an hour composing a message. Losing such a message would be a tragedy. Thankfully, I haven't been so unlucky (always copy before posting).
|
|
|
|
|
I'm not sure what it is, but it sure is getting frakking annoying to copy a post before posting it.
I have had it happen several times today and yesterday.
Chris Meech
I am Canadian. [heard in a local bar]
In theory there is no difference between theory and practice. In practice there is. [Yogi Berra]
|
|
|
|
|
Just tested it. Looks like you need to wait about an hour (over 30 minutes for sure) for a message to be lost to the white screen of death.
|
|
|
|
|
I just had it happen again today. The time was somewhere between 2 to 3 minutes.
Chris Meech
I am Canadian. [heard in a local bar]
In theory there is no difference between theory and practice. In practice there is. [Yogi Berra]
|
|
|
|
|
Interesting. Next time it happens, can you view the source of the blank page and copy the HTML, then paste it here to compare to mine?
|
|
|
|
|
I clicked a link in the weekly Newsletter and got the error:
This job is not available in your area. Sorry!
I'm curious as to why this filter is in place? What if I'm not looking for jobs in my area, but in other areas? I'm constantly looking for a reason to move to somewhere else, software development in particular makes this possible.
Unless there are legal reasons you can't display something, I would prefer if you not filter me in anyway, it is just annoying, and never relevant.
Ken Foster
|
|
|
|
|
I agree 100%
|
|
|
|
|
I'd be more impressed if you agreed something like 38% - it would be much more entertaining.
|
|
|
|
|
Me agreeing with you for only 38% would have seemed quite unlikely until very recently, however I just read your neighborly anecdote, where you failed to properly explain the channels button for the better part of one hour, so a partial agreement suddenly became quite conceivable; not sure anyone would consider it entertaining though.
And now I'll continue my reading (a set of TV manuals, as I am in the middle of choosing a new TV set).
|
|
|
|
|
Luc Pattyn wrote: a set of TV manuals, as I am in the middle of choosing a new TV set
If you need any advice then feel free to...
...seek it elsewhere.
|
|
|
|
|
you're denying me the benefit of your unfathomable avuncularity?
|
|
|
|
|
I am only avuncular when the plane ticket is provided.
|
|
|
|
|
Hmm[^], I can get a couple of TV's at that price.
PS: it was avuncular, not avioncular.
|
|
|
|
|
Ken and our team have had an email chat about this so I thought I'd post Dave's explanation so others could see:
The ability to limit showing geographically is by design and is stipulated by the employer at the time of posting. The feature was actually added after launch at the request of the employers.
The problem was that employers were being literally inundated with responses from developers who wanted employment visa sponsorship and it was badly degrading the signal to noise ratio for the employers.
We fully (truly) understand your point but in the end this is what the employers wanted.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Perhaps you can temporarily modify your profile so that it shows you from a different location, then check out the job listings and they will hopefully appear with your updated location. When you're done searching, you can go back to your profile to reflect your true location. Just a suggestion... not sure if you can change your location in your profile or if it is determined by IP address or something.
|
|
|
|