My overdue QCN task, mentioned in
Quote from: Pepo on April 08, 2011, 10:30:07 AM
Now already two weeks after its deadline...
Quote from: Pepo on April 09, 2011, 08:43:19 PM
Quote from: fred on April 09, 2011, 05:49:40 PM
Quote from: Pepo on April 09, 2011, 04:28:59 PM
Quote from: fred on April 08, 2011, 07:29:36 PM
on the bug list: Bug: Don't show negative time left and deadline.
No nooooo please hold on! Both are good indications of either buggy application or a time past deadline.
Ok I change this into ??, indicating an error in the number.
The values are way out of range and the actual numbers mean nothing.
With negative Time left you're probably right - meaningless value calculated out of meaningless values? "??" could be a good replacement.
But the red negative Deadline value is still correct, whether in "date+time" or relative "dd,hh:mm" format, isn't it?
The Remaining time estimate is still displayed as "-" instead of "??". In the task's Properties, the Estimate is being a copy of Elapsed time!!
Deadline time is still correctly displayed in date+time mode, correctly warn-lighted in both modes, but blank (instead of either "??" or "-ddd,hh:mm:ss" :'() in the second mode.
Now each right-mouse-click in any of the tabs is finally followed by having some line(s) selected and opening its/their context menu (unless someone will find some exception, like due to a missing or "zero-wide" or "unexpectedly placed" column).
But there are two groups of tabs with a bit different row (re)selection behavior, as a reaction to a right-mouse-click:
- Computers + Messages: the "usual" way:
- if no line is selected, right-clicking any line selects it
- if any (1 or more) lines are selected, right-clicking on one of them keeps the selection
- if any lines are selected, right-clicking on any other line moves the selection to the new line
- Projects + Tasks + Transfers + History: the "BoincTasks" way ::):
- if no line is selected, right-clicking any line selects it
- if any (1 or more) lines are selected, right-clicking on one of them keeps the selection
- if any lines are selected, right-clicking on any other line does not move, but still keeps the selection
Would it be possible to implement the first variant also for
Projects +
Tasks +
Transfers +
History tabs?
Quote from: Pepo on April 14, 2011, 09:59:31 AM
Would it be possible to implement the first variant also for Projects + Tasks + Transfers + History tabs?
No problem.
Quote from: Pepo on April 14, 2011, 09:59:31 AM
Now each right-mouse-click in any of the tabs is finally followed by having some line(s) selected and opening its/their context menu (unless someone will find some exception, like due to a missing or "zero-wide" or "unexpectedly placed" column).
... row (re)selection behavior, as a reaction to a right-mouse-click:
- Tasks:
- if no line is selected, right-clicking any line selects it
Spoken too soon :( I've just found an exception, just no rule to it. On the
Tasks tab, no line is selected and right-clicking any line does not select it. Computer column is fifth from the right, all columns are visible, so it must be something else. Since the installation yesterday, there were already "hundreds" of lines been selected and unselected.
I'm seeing more crashes here in 1.02 than in recent previous versions. 1.01 had a few more than previous and 1.02 has about double that of 1.01 (about 1 dmp file/day). It may well be related to clients that have a less than reliable connection (wireless).
Also, for all tabs except "Computer" (in which columns are all left justified) most columns are left justified while a few are right justified. For instance in the "History" tab all columns are left justified except "Completed", "Reported" and "Elapsed Time". Could they all be made left justified?
Quote from: Beyond on April 18, 2011, 05:56:02 PM
Also, for all tabs except "Computer" (in which columns are all left justified) most columns are left justified while a few are right justified.
It is so on purpose.
QuoteFor instance in the "History" tab all columns are left justified except "Completed", "Reported" and "Elapsed Time". Could they all be made left justified?
No, please not!
:o except that it would be a user settings. I can not imagine e.g. a left-justified debt column or credits, or relative-time values
:-X
Quote from: Beyond on April 18, 2011, 05:56:02 PM
I'm seeing more crashes here in 1.02 than in recent previous versions. 1.01 had a few more than previous and 1.02 has about double that of 1.01 (about 1 dmp file/day). It may well be related to clients that have a less than reliable connection (wireless).
Nice to have a couple of 1.02 dumps to see if I can find something.
And indeed, I expect it to be something deep, in the connection routines.
in read colour settings / record colour setting is not exported the colour for High Priority GPU.
Quote from: Corsair on April 18, 2011, 09:21:32 PM
in read colour settings / record colour setting is not exported the colour for High Priority GPU.
On the bug list.
Quote from: fred on April 18, 2011, 07:23:32 PM
Quote from: Beyond on April 18, 2011, 05:56:02 PM
I'm seeing more crashes here in 1.02 than in recent previous versions. 1.01 had a few more than previous and 1.02 has about double that of 1.01 (about 1 dmp file/day). It may well be related to clients that have a less than reliable connection (wireless).
Nice to have a couple of 1.02 dumps to see if I can find something. And indeed, I expect it to be something deep, in the connection routines.
Five of the little dears are uploaded, zipped:
BoincTasks_102_21-04-2011_13-04.zip
BoincTasks_102_23-04-2011_11-40.zip
BoincTasks_102_24-04-2011_22-56.zip
BoincTasks_102_25-04-2011_13-44.zip
BoincTasks_102_25-04-2011_15-16.zip
BT restarts many times a day but leaves a dmp file less regularly. In the last few days I've found that changing the BT priority to "below" works better and changing it to "low" is even better (
far fewer restarts and less CPU time used). History is set at 1 day.
An Einstein CPU task was suddenly highlighted with violet color, which I could not find to be defined for either Tasks or Warnings or whatever (except some downloads using a similar color). The task was using just some 9-12% of CPU and the corresponding value in CPU% column was highlighted accordingly. After limiting CPU throttle to max. 10%, other running tasks got their warning CPU% highlight too, but not this violet full-line highlight.
After some half hour the task used 91% of CPU and was already highlighted with usual 'running CPU task' color (green). High priority is defined as an absolutely different color (yellow).
Quote from: Beyond on April 25, 2011, 05:40:13 PM
Five of the little dears are uploaded, zipped:
BT restarts many times a day but leaves a dmp file less regularly. In the last few days I've found that changing the BT priority to "below" works better and changing it to "low" is even better (far fewer restarts and less CPU time used). History is set at 1 day.
All but one crash is in the history section. But.... as this is the only part of the program that's running, it's not that much of a clue.
I will check the history routines.
But these kind of errors can come from anywhere and point to some sort of memory corruption.
Fred, don't know if this is much of a hint: if I set the boinctasks64.exe to low priority I get no restarts (2 straight days now). Set to normal it restarts many times a day. I have no idea why setting BT to low priority helps. ???
Quote from: Beyond on April 26, 2011, 09:12:51 PM
Fred, don't know if this is much of a hint: if I set the boinctasks64.exe to low priority I get no restarts (2 straight days now). Set to normal it restarts many times a day. I have no idea why setting BT to low priority helps. ???
I will add an expert option in 1.03, to set the priority to below and low.
Probably a timing issue somewhere, not necessarily in BT.
Quote from: fred on April 26, 2011, 11:15:33 PM
Quote from: Beyond on April 26, 2011, 09:12:51 PM
Fred, don't know if this is much of a hint: if I set the boinctasks64.exe to low priority I get no restarts (2 straight days now). Set to normal it restarts many times a day. I have no idea why setting BT to low priority helps.
I will add an expert option in 1.03, to set the priority to below and low. Probably a timing issue somewhere, not necessarily in BT.
Thanks Fred! I started using Priority to set it low but your solution is better (as usual). After running a little over 2 days in "low" without a BT restart I finally closed it and reloaded BT manually. At that point the CPU time was 3 hours and 50 minutes. Is that normal or is it excessive here?
Quote from: Beyond on April 27, 2011, 02:17:04 PM
Thanks Fred! I started using Priority to set it low but your solution is better (as usual). After running a little over 2 days in "low" without a BT restart I finally closed it and reloaded BT manually. At that point the CPU time was 3 hours and 50 minutes. Is that normal or is it excessive here?
As I have no idea what is causing this, I have to wait a couple of weeks, before I have enough computer power to do some more testing.
Two
(http://www.chatsmileysemoticons.com/wp-content/uploads/2009/04/07-bug.gif) found:
- An errored-out (but not reported yet) task's Properties window is empty.
- My tasks are sorted according to 1. Progress % column, 2. Task state column. While computing is allowed, all is fine. While snoozed, the errored-out task's line (at 100%) is placed over my QCN task's line (now at 243%). When resumed, the sorting is again correct.
And one more
(http://www.chatsmileysemoticons.com/wp-content/uploads/2009/04/07-bug.gif) still trying to hide itself - the tray icon's "GPU suspended" indicator still gets out of sync:
Quote from: Pepo on March 01, 2011, 04:14:20 PM
- the tray icon's "GPU suspended" indicator is really still buggy... I'm using it multiple times daily and it often keeps solid red even if nothing is suspended (and BT also thinks so, according to its tray popup menu without any checkbox and countdown timer).
- and, related, the indicator is sometimes solid white, although the computation is snoozed.
Quote from: Pepo on April 28, 2011, 02:27:46 PM
And one more (http://www.chatsmileysemoticons.com/wp-content/uploads/2009/04/07-bug.gif) still trying to hide itself - the tray icon's "GPU suspended" indicator still gets out of sync:
Quote from: Pepo on March 01, 2011, 04:14:20 PM
- the tray icon's "GPU suspended" indicator is really still buggy... I'm using it multiple times daily and it often keeps solid red even if nothing is suspended (and BT also thinks so, according to its tray popup menu without any checkbox and countdown timer).
- and, related, the indicator is sometimes solid white, although the computation is snoozed.
Is there any pattern? Can you reproduce it?
Quote from: fred on April 28, 2011, 11:46:16 PM
Quote from: Pepo on April 28, 2011, 02:27:46 PM
And one more (http://www.chatsmileysemoticons.com/wp-content/uploads/2009/04/07-bug.gif) still trying to hide itself - the tray icon's "GPU suspended" indicator still gets out of sync:
Quote from: Pepo on March 01, 2011, 04:14:20 PM
- the tray icon's "GPU suspended" indicator is really still buggy... I'm using it multiple times daily and it often keeps solid red even if nothing is suspended (and BT also thinks so, according to its tray popup menu without any checkbox and countdown timer).
- and, related, the indicator is sometimes solid white, although the computation is snoozed.
Is there any pattern? Can you reproduce it?
I understand your needs...
Hard to say. I interact with BT pretty often. And as soon as I notice the screen interactions get slowed down, I open the tray's context menu and snooze GPU (for a hour). This can happen 5-10 x daily. And some time (hours to days) later I notice that the red (or white) circle is being constantly lit.
Language
:P corner: Just thinking of... hey, any Englishmen around? I believe have to write, correctly, "for
a hour", but is it then pronounced "for
en aur" (because of the omitted "h" when pronounced)? Because, I was tempted to write "for a
n hour", but I suspect it would be wrong.
Quote from: Pepo on April 29, 2011, 11:58:48 AM
the tray icon's "GPU suspended" indicator is really still buggy... I'm using it multiple times daily and it often keeps solid red even if nothing is suspended (and BT also thinks so, according to its tray popup menu without any checkbox and countdown timer).
Slightly off topic question, what GPU project? What settings for that project? It may be better to fix the slowdown at that level rather than snoozing.
Quote from: Pepo
Language :P corner: Just thinking of... hey, any Englishmen around? I believe have to write, correctly, "for a hour", but is it then pronounced "for en aur" (because of the omitted "h" when pronounced)? Because, I was tempted to write "for an hour", but I suspect it would be wrong.
"An hour" is correct at least in US English, or should that be North Americish ;D. The key is what the next sound is after "a" or "an". If it's a vowel sound it's "an". The reason is more or less logical. It's easier to say.
Quote from: fred on April 28, 2011, 11:46:16 PM
Quote from: Pepo on April 28, 2011, 02:27:46 PM
And one more (http://www.chatsmileysemoticons.com/wp-content/uploads/2009/04/07-bug.gif) still trying to hide itself - the tray icon's "GPU suspended" indicator still gets out of sync:
Is there any pattern? Can you reproduce it?
This morning I've restarted BT, in order to be able to notice any behavioral pattern. I've even created a shortcut to snooze GPU for just a couple of minutes, and used it a lot too (in addition to 1 hour standard snooze). Both at least 20-30 times today.
The indicator is still flashing correctly!!
(OK, let's see after the weekend. I'm sure it will turn wrong, just how to notice when? I suppose BT is flipping this indicator with some particular function, which has a callback somewhere to be regularly invoked each 1 second. Could the events be written in a log file (do we already have one?), when the callback is enabled or disabled? I could be then checking this...)
Quote from: Beyond on April 29, 2011, 02:03:06 PM
Quote from: Pepo on April 29, 2011, 11:58:48 AM
... I'm using [the "GPU suspend"] multiple times daily ...
Slightly off topic question, what GPU project? What settings for that project? It may be better to fix the slowdown at that level rather than snoozing.
Some projects produce nearly unnoticeable slowdown, some do it "more thoroughly"
:D and especially the PrimeGrid produces
THE killer app(s) for my graphics
;DYou can take a look at the discussion in Topic: Directed GPU Use Option??
?? (http://www.efmer.eu/forum_tt/index.php?topic=694)
Quote from: Beyond
Quote from: Pepo
Language :P corner: Just thinking of... hey, any Englishmen around? I believe have to write, correctly, "for a hour", but is it then pronounced "for en aur" (because of the omitted "h" when pronounced)? Because, I was tempted to write "for an hour", but I suspect it would be wrong.
"An hour" is correct at least in US English, or should that be North Americish ;D. The key is what the next sound is after "a" or "an". If it's a vowel sound it's "an". The reason is more or less logical. It's easier to say.
OK, this means, in contrast to what I've thought (but confirming what I've felt and wished), that the pronunciation of the following word is important, rather than its spelling, right?
(Learnt again something new (what I possibly knew a few decades ago
;D) Anyone speaking UK English around, for their point of view?)
Quote from: fred on April 28, 2011, 11:46:16 PM
Quote from: Pepo on April 28, 2011, 02:27:46 PM
And one more (http://www.chatsmileysemoticons.com/wp-content/uploads/2009/04/07-bug.gif) still trying to hide itself - the tray icon's "GPU suspended" indicator still gets out of sync:
For 1.03 I added snooze logging. Maybe this will show us what's going on.
I discover BT 1.02 running sluggish on an XP3 system with all the latest fixes. I started the system manager and discovered that notices was looping and using 48 percent of the CPU time consistently. This went on for several minutes. I was forced to end the process which broke everything loose to run normally. I have the notice update check set to every 60 minutes. BT is set to update every 2 minutes. I then exited BT and restarted it and observed the task manager as running okay. Did not see notices task in list.
If there is anything I can do to help you with this problem let me know. I have been running BT 1.02 since it came available and have not noticed this before. I usually check BT about every four hours, except during the night.
I might mention that I have a in house network of seven computers all running BOinc.
Quote from: idahofisherman on May 01, 2011, 09:30:59 PM
I discover BT 1.02 running sluggish on an XP3 system with all the latest fixes. I started the system manager and discovered that notices was looping and using 48 percent of the CPU time consistently. This went on for several minutes. I was forced to end the process which broke everything loose to run normally. I have the notice update check set to every 60 minutes. BT is set to update every 2 minutes. I then exited BT and restarted it and observed the task manager as running okay. Did not see notices task in list.
If there is anything I can do to help you with this problem let me know. I have been running BT 1.02 since it came available and have not noticed this before. I usually check BT about every four hours, except during the night.
I might mention that I have a in house network of seven computers all running BOinc.
It should update at the time interval set, but it only updates the screen when there are any changes.
Most likely something went wrong on the computer itself.
On a new notice, BT creates a new file in the user folder: eFMer\BoincTasks\html\notices.html
Next the file is read with some sort of internal copy of Microsoft's IE.
When you see this happen, maybe never again, check the notices.html time stamp, to see if a new copy is made, over and over again.
BT 1.02 does not pick up new notices from other computers on local network other than the computer that BT is on. Am I missing setting somewhere. When I look at C:\program files\emfer\boinctasts\html All I find is an example notice file which hasn't be updated since January.
I checked four of the machines and brought them upto 6.22.26 boinc. There are newer notices on one of the machines that is not displayed in BT.
Quote from: idahofisherman on May 02, 2011, 06:03:28 AM
I checked four of the machines and brought them upto 6.22.26 boinc.
I suppose you've meant 6.
12.26 boinc.
Quote from: Pepo on April 29, 2011, 05:04:27 PM
Quote from: fred on April 28, 2011, 11:46:16 PM
Quote from: Pepo on April 28, 2011, 02:27:46 PM
And one more (http://www.chatsmileysemoticons.com/wp-content/uploads/2009/04/07-bug.gif) still trying to hide itself - the tray icon's "GPU suspended" indicator still gets out of sync:
Is there any pattern? Can you reproduce it?
This morning I've restarted BT, in order to be able to notice any behavioral pattern. I've even created a shortcut to snooze GPU for just a couple of minutes, and used it a lot too (in addition to 1 hour standard snooze). Both at least 20-30 times today.
The indicator is still flashing correctly!!
(OK, let's see after the weekend. I'm sure it will turn wrong, just how to notice when?
So, the weekend is over. As my display was being slowed down, I've opened BT to check, whether it is, as expected, some "offending GPU task" - it was a "
GPUGRID 6.13 Long runs A535-TONI_AGG1-14-100-RND9332_0" task, so I've snoozed GPU - the tray icon circle stayed solid white.
It happens, just hard to predict, when.
Quote from: fred on April 29, 2011, 08:07:31 PM
Quote from: Pepo on April 29, 2011, 05:04:27 PM
Quote from: Pepo on April 28, 2011, 02:27:46 PM
And one more (http://www.chatsmileysemoticons.com/wp-content/uploads/2009/04/07-bug.gif) still trying to hide itself - the tray icon's "GPU suspended" indicator still gets out of sync:
I suppose BT is flipping this indicator with some particular function, which has a callback somewhere to be regularly invoked each 1 second. Could the events be written in a log file (do we already have one?), when the callback is enabled or disabled? I could be then checking this...)
For 1.03 I added snooze logging. Maybe this will show us what's going on.
I'm looking forward!
Quote from: idahofisherman on May 02, 2011, 06:03:28 AM
BT 1.02 does not pick up new notices from other computers on local network other than the computer that BT is on. Am I missing setting somewhere. When I look at C:\program files\emfer\boinctasts\html All I find is an example notice file which hasn't be updated since January.
I checked four of the machines and brought them upto 6.22.26 boinc. There are newer notices on one of the machines that is not displayed in BT.
BT only displays one computer at a time.
Select the computer from the sidebar computer selection.
The default machine is the localhost.
I've seen one
Notices notification issue. I've opened my locked Windows account session at around 12:17-12:19. A moment later I've opened BT, a brief glance at running and finished tasks, reported the few unreported yet. Then I've noticed BT reporting "
Notices (1)" on its tab. Clicked there (I assume at around 12:25), seen this (3 most recent out of approx. 19 notices (upper time is the notice's creation time, lower time is its delivery time)):
Quote from: BT Notices
26.04.11 12:55
World Community Grid: Earth Day 2011 event - The Clean Energy Project webcast replay
On Earth Day, April 22, 2011, Dr. Alan Aspuru-Guzik provided an update for The Clean Energy Project via webcast. Here are the links to the webcast and the related question and answer session.
(05.05.11 12:24) viac... (http://www.worldcommunitygrid.org/about_us/viewNewsArticle.do?articleId=159)
05.05.11 02:56
AQUA@home: Oznam od servera
AQUA's mt4 applications need at least 4 available cores
(05.05.11 02:56)
04.05.11 12:32
ibercivis: Oznam od servera
Nie je k dispozícii žiadna práca pre aplikácie, ktoré ste si zvolili. Skontrolujte si prosím Vaše nastavenia projektu na webovej stránke.
(04.05.11 12:32)
..........
A few seconds later I've switched back to
Tasks and minimized BT.
A bit (at most one minute) later (it was exactly at 12:26 according to the clock) a "New Notice" notification balloon popped up - "1 new notice". I've took a look, but nothing new - the most recent one was still the already read one from 12:24.
Quote from: Pepo on April 26, 2011, 04:13:28 PM
An Einstein CPU task was suddenly highlighted with violet color, which I could not find to be defined for either Tasks or Warnings or whatever (except some downloads using a similar color). The task was using just some 9-12% of CPU and the corresponding value in CPU% column was highlighted accordingly. After limiting CPU throttle to max. 10%, other running tasks got their warning CPU% highlight too, but not this violet full-line highlight.
After some half hour the task used 91% of CPU and was already highlighted with usual 'running CPU task' color (green). High priority is defined as an absolutely different color (yellow).
I've noticed I've indeed defined such color (or two similar) for two Rules - for tasks over 99.99% and tasks with < 1 second time remaining. I was hoping to notice Rosetta tasks, which finally checkpoint at 100.000% with 0 seconds remaining time estimate and are regularly preempted at this moment.
But never seen them highlighted before - apparently because the rules only apply to running tasks, and also with some delay. And the running Einstein task in question was somewhere in the middle of its life - none of both rules should have fired for it.
I've just some funky experience with the rules...
:-\
Quote from: Pepo on May 06, 2011, 01:37:09 PM
Quote from: Pepo on April 26, 2011, 04:13:28 PM
An Einstein CPU task was suddenly highlighted with violet color, which I could not find to be defined for either Tasks or Warnings or whatever (except some downloads using a similar color). The task was using just some 9-12% of CPU and the corresponding value in CPU% column was highlighted accordingly. After limiting CPU throttle to max. 10%, other running tasks got their warning CPU% highlight too, but not this violet full-line highlight.
After some half hour the task used 91% of CPU and was already highlighted with usual 'running CPU task' color (green). High priority is defined as an absolutely different color (yellow).
I've noticed I've indeed defined such color (or two similar) for two Rules - for tasks over 99.99% and tasks with < 1 second time remaining. I was hoping to notice Rosetta tasks, which finally checkpoint at 100.000% with 0 seconds remaining time estimate and are regularly preempted at this moment.
But never seen them highlighted before - apparently because the rules only apply to running tasks, and also with some delay. And the running Einstein task in question was somewhere in the middle of its life - none of both rules should have fired for it.
I've just some funky experience with the rules... :-\
The rules get there data from the history, not from what you see in Tasks, so the data may be off by a couple of minutes.
The only way to get a more current reading is by setting the maximum update time lower. But that gives more overhead.
Quote from: Pepo on May 02, 2011, 03:28:38 PM
Quote from: fred on April 28, 2011, 11:46:16 PM
Quote from: Pepo on April 28, 2011, 02:27:46 PM
And one more (http://www.chatsmileysemoticons.com/wp-content/uploads/2009/04/07-bug.gif) still trying to hide itself - the tray icon's "GPU suspended" indicator still gets out of sync:
Is there any pattern? Can you reproduce it?
It happens, just hard to predict, when.
I'm not reporting anymore
;), that a newly started BT's tray icon got solid red 3 days later, I've noticed it just after the weekend. I'm pretty confident, that it was not red, when I left the machine on Friday (but not absolutely sure). If so, this would mean that it can get out of sync even while not snoozing GPU. (Take it just as a conspiracy theory.)