The Russians!
yes, same problem
Yep. Freerepublic is getting to be unusable.
It’s my fault.
Last night I realized FR seemed to be running pretty quick...so, in my preferences, I clicked over from 20 threads and comments to 50.
Pszzt...it went kablooie.
YES!!! Someone please fix it!
Not seeing that, I get twenty threads loaded correctly, plus sidebars. What I am seeing is the Texas state board is not loading. In a way, that might be OK, since there have been no new posts on it since July 13, with the exception of one of mine. I think the way it works is it shows up if there are NEW messages, so if there are no new messages, maybe it is working right. Could someone else (that is on the TX State board in their locale) please check it for me? Maybe post a message there?
Thanks,
matthew fuller
Hope it’s working better for you now now. I talked to John and he said he’d look into it. I see he got some of it fixed already. Thanks.
Problem (for me) ended about 20 minutes ago. Back to normal.
I’m blaming my computer, now I see I am not alone.
Me too
PROFILING SOFTWARE
and fixing problems.
o “Isolate & Replace” is better than “Try this Try that”
Intentional Isolating a recurring software problem is the preferred method of troubleshooting. Therefore we will discuss software Profiling.
o Profiling
Software Profiling means printing out to memory, but usually to a hard drive file, the relevant functions, with specific relevant data, referenced by objects and modules. For example, the debug profiling file may read:
obj DoSomething func DoingIt dataNumber 327 dataName Bob
obj More func DoMore dataMore 489blahblah
. . .
Profiling is real time. Can be turned on/off real time by a simple setting property/variable. Reading such a file is the easiest, and probably the only way to understand quickly how a complex software operates. No more guessing.
o Debug Object
Yes a troubleshooting object is global everywhere. But it is the only global object. It can be local, with more difficulty.
Fortunately when the failure is isolated, solved, and fixed, the Debug Object is removed.
Example is simply: oDebug.printf( blah blah )
o Logging
Faulty problems can be Internal or External, Client or Server or else. Locate all relevant log files, but if possible, a Debug Log file, also called Profiling, should eliminate guessing.
It is amazing how programmers can take years or never, to slowly understand how a specific software operates. By Profiling, in only days not years, can complex software be made easy to understand, then isolate and fix.
o Interrmittency vs Hard Fail
Intermittent problems are far more difficult to solve unless Profiled with Debug files.
o Concurrency
Search & identify all concurrency such as threads, semaphores and such, in the language used.
—
Also replies...
The Russians or the NSA, your choice.