Sorry, my forum notifications are not coming through so I missed some questions->
1. Sven Åke -> from that error it seems that your network share was not available, this shouldn't cause any exception and is already fixed in the next release.
2. Napoleon -> The default historical view shows submitted results ordered by download time, the 'Filters->stored filters->Submitted' filter returns the same records ordered by submission time.
You can use date's but you need to use this format-> yyyy-MM-ddThh:mm:ss or if you're only looking for date's not timeofday leave out the T and anything following it
- Code: Select all
6/15/2009 1:45:30 PM should be formatted like -> '2009-06-15T13:45:30'
OR -> '2009-06-15'
So a search for submitted files between 1/2/2012 and 8/2/2012 ( *you might have to swap the <= to =<, sqlite is picky about the order and I haven't checked myself right now ).
- Code: Select all
WHERE Submitted => '2012-02-01' AND Submitted <= '2012-02-01' AND ServerResponse like 'WORCK_ACK%'
I don't think 'like' is supported with datetime fields, you need to wrap it between max and min allowed values.
3. Grandpa_01
I upgraded my FAHClient install today and I have not seen ( all ) of those errors. The first one's are about frametime's which appear to be out of order ( a frame being parsed being earlier then the previous frame ). Those errors I did have when my kids messed with clock settings. Am I wrong to assume you're monitoring a vm with a linux client? If so, check your logs from that client and verify if there are overlapping time entries. Some premade vm's have time syncing enabled which corrects the vm's time to actual time, this is because the operating system in the vm does not have access to the hardware performance counters needed for accurate time keeping. It might be that the time sync interval happens right before you complete a frame, and this could cause times being logged which appear to be in conflict. If you log looks normal, please send them to my email so I can check why it gives that error.
The overflow error is caused by a parsing error where your submission time is recorded correctly and thus the 'simulation time' is invalid. This error is handled cleanly in the next version.
The reason it quits right after the error is because the error happens during startup and any exception there are considered to be 'deal breakers'. So it displays the logwindow, and when that's closed, it exits. Again, I don't want to mess with that logic, the startup should never give exceptions, unless they are catched and dealt with ( which is already done in the next version ).
@All
Sorry, been a long time between the previous update and I don't know how close I am to the next one. But, that does mean it's going to be a big update
I'll give you a short list of the things coming soon:
- No more 'blank borderless' forms on your desktop ( finished )
- Sortable and selectable columns in history ( this is working great I can tell you and I considered dropping the sql filters completely.. which I won't because they can limit the actual amount of work units loaded into memory ) ( finished )
- Live monitor with frametime graphs, logs and queued work units ( 80% to 90% finished? )
- The ppd calculator will have a graphical implementation which will ( initially ) show ppd for each hour between 0 and final deadline ( and will offer zoom levels generating points for every minute ) ( just started )
- Working notifications including email notifications with scheduler ( 60% done )
- Working tools wrapper for stresscpuv2, memtestG80 and memtestCL ( 30% done )
- Updated graphing code which should make it much easier to quickly see relevant information ( 50% done )
- Exception dialog for submitting Exception report through email ( 80% done )
- Exceptions where are reported are added to a list which will prevent popups on errors ( they will still be logged, and you will still get the animated icon indicating an exception is logged, but it won't pop up messages ).
- New installer which will support retaining database between upgrades ( finished )
- Upgrade functionality for 0.1.0.6 databases to the new format ( 99% finished, which means finished but not sure I missed something )
- Ability to reset settings to default.
The version after that get's Harlam's FAHClient interface class implemented and will offer control options, which enables adding things like schedulers and 'stop x slot(s) when y process is running'. It will also enable monitoring in semi real time. I am also going to add a multi select capability to the history overview, depending on the detail tab which is selected this will draw multiple tpf graphs on top of each other, or show how the selection correlates to each other in tpf/ppd.
If anyone wants any details just ask and I'll see if I can answer or maybe post a screenshot to show what's coming
Edit:
I forgot something ( and it was nagging me.. what did I forget?? : oops : )
Next version, or the one after, will support affinity and priority overrides.
Something is better then nothing... and afaik it should be pretty accurate. Hasn't lost track of any clients overnight either 
).
)
