CodeProject's rodents attacking my motherboard's chipset!!
-
I've been trying to modify my profile for the last few days, and I've been systematically presented with the rodents. See an example at http://www.rilhas.com/CodeProject/rodents.jpg[^]. Today I tried changing my picture and saving, and that worked. But trying to turn on the daily newsletter continues to fail. I have no idea about what may be happening, but I'm starting to think the CodeProject's crew doesn't get informed of these occurrences, so here is one.
-
I've been trying to modify my profile for the last few days, and I've been systematically presented with the rodents. See an example at http://www.rilhas.com/CodeProject/rodents.jpg[^]. Today I tried changing my picture and saving, and that worked. But trying to turn on the daily newsletter continues to fail. I have no idea about what may be happening, but I'm starting to think the CodeProject's crew doesn't get informed of these occurrences, so here is one.
This is a new friendly error message. I have the same problem but my article is lost and same error is shown see My article is lost[^] Jovan
-
I've been trying to modify my profile for the last few days, and I've been systematically presented with the rodents. See an example at http://www.rilhas.com/CodeProject/rodents.jpg[^]. Today I tried changing my picture and saving, and that worked. But trying to turn on the daily newsletter continues to fail. I have no idea about what may be happening, but I'm starting to think the CodeProject's crew doesn't get informed of these occurrences, so here is one.
We watch all error logs carefully, but the logs often tell us what happened, not what the user was trying to do. My guess it's related to a network issue we've seen, so your report here could be the bit we've been waiting for.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
We watch all error logs carefully, but the logs often tell us what happened, not what the user was trying to do. My guess it's related to a network issue we've seen, so your report here could be the bit we've been waiting for.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
When you write "network issue" I immediately think of "intermittent problem". But so far it has happened to me very consistently, of the 4 or 5 times I've tries to activate the daily newsletter the rodents appeared 100.000% of the time. So if you need help traking it I'm pretty confident I can generate the error on demand. Let me know if you need someone to push the button on this end.
-
When you write "network issue" I immediately think of "intermittent problem". But so far it has happened to me very consistently, of the 4 or 5 times I've tries to activate the daily newsletter the rodents appeared 100.000% of the time. So if you need help traking it I'm pretty confident I can generate the error on demand. Let me know if you need someone to push the button on this end.
We've been seeing network errors but I've just tried logging in as you, updating your newsletter settings, and saving, and it all went through without even a burp. :doh:
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
We've been seeing network errors but I've just tried logging in as you, updating your newsletter settings, and saving, and it all went through without even a burp. :doh:
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
I made some more tests and I found a pattern. I wrote you an extensive message about it, but maybe because my tests were made during a period where the message page was open the whole message got lost to the rodents. So I'll type it again (highlights only without many details of the tests, sorry!). I noticed a pattern: a) login b) edit some setting c) save the settings d) succeed e) edit some other setting f) save the settings g) get the rodents (and the settings are not saved) h) manually edit the address to go back to CodeProject's home page i) edit some setting j) login is required so I login k) go back to c) On my previous tests I tried again by clicking "back" on the browser, getting some "page expired" error, insisting, getting some more errors, insisting again, and insisting some more until I got to a CodeProject page that I recognized. This because the rodents page does not have a link for me to go back to CodeProject (which I think it should, by the way, in order to be friendly). In this new sequence of tests I manually edited the address bar link to go back to CodeProject's home page, which consistently required me to login at some point. So I guess the problem is probably related to some corruption or invalid state that occurs when I save the settings once. So saving the settings a second time manifests the problem. Logging in seems to clear this corrupted state, and so I'm able to edit and save settings after that. This explains why I so consistently got rodents on my first tests (no re-login), and why I now so consistently succeeded in saving after logging in but got the rodents on the second save attempt. It also explains why you were able to log in as me, edit, and save, in case you happened to do it only once. The obvious follow up test is to try a shorter login->edit->save->login->edit->save... loop to confirm the rodents never show up, but I don't have more time today and I fear I may lose this message to the rodents too if I do any more tests before sending it. I hope this helps.
-
I made some more tests and I found a pattern. I wrote you an extensive message about it, but maybe because my tests were made during a period where the message page was open the whole message got lost to the rodents. So I'll type it again (highlights only without many details of the tests, sorry!). I noticed a pattern: a) login b) edit some setting c) save the settings d) succeed e) edit some other setting f) save the settings g) get the rodents (and the settings are not saved) h) manually edit the address to go back to CodeProject's home page i) edit some setting j) login is required so I login k) go back to c) On my previous tests I tried again by clicking "back" on the browser, getting some "page expired" error, insisting, getting some more errors, insisting again, and insisting some more until I got to a CodeProject page that I recognized. This because the rodents page does not have a link for me to go back to CodeProject (which I think it should, by the way, in order to be friendly). In this new sequence of tests I manually edited the address bar link to go back to CodeProject's home page, which consistently required me to login at some point. So I guess the problem is probably related to some corruption or invalid state that occurs when I save the settings once. So saving the settings a second time manifests the problem. Logging in seems to clear this corrupted state, and so I'm able to edit and save settings after that. This explains why I so consistently got rodents on my first tests (no re-login), and why I now so consistently succeeded in saving after logging in but got the rodents on the second save attempt. It also explains why you were able to log in as me, edit, and save, in case you happened to do it only once. The obvious follow up test is to try a shorter login->edit->save->login->edit->save... loop to confirm the rodents never show up, but I don't have more time today and I fear I may lose this message to the rodents too if I do any more tests before sending it. I hope this helps.
That was great info. Are you still seeing this issue? I've been unable to replicate, but we have made some changes that should have helped.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
