BT 0.99

[Pepo]

BT now seems to correctly display the originating project name in Notices. But "Notices from BOINC" (as (loosely translated) are they displayed in BOINC Manager) are headed just by a bold colon:

:
Nerozpoznaná značka v cc_config.xml: <force_auth_off>
26.01.11 17:40 viac...

and it looks a bit weird 

[fred]

BT now seems to correctly display the originating project name in Notices. But "Notices from BOINC" (as (loosely translated) are they displayed in BOINC Manager) are headed just by a bold colon:

:
Nerozpoznaná značka v cc_config.xml: <force_auth_off>
26.01.11 17:40 viac...

and it looks a bit weird 

This text is inserted on a condition. So it's not an actual notice text.
Do you have a way to generate a message, all the time and in English.

[Pepo]

Long story short: I've opened BT 0.99's window, started BOINC 6.12.11->6.12.14 update, finally launched BOINC. BT was again not able to reconnect, until I've "edited" (or touched) the localhost's IP address in BT (from "localhost" to the same "localhost" + <Enter>).

(As promised, I've later edited this post on Chrome - my IE was not willing to let me edit long text in small editing window of this forum )

While BT kept running, I've updated the client 6.12.10->6.12.11. BT lost connection to it (it was the only connected client, local) and did not get it again even many minutes after the client (in service mode) started. I remember already having seen this in the past.

After clicking through all tabs, Tasks and Messages and Gadget were emptied, but Projects keep displayed (for a not-connected client). And, the tray tooltip still displays "machinename, Running: 2".

After a couple of minutes, I've "edited" the local computer's IP definition (it is localhost, I've just clicked on it and pressed Enter). The connection was promptly created.

To add to my connection problem: the reconnect time is IIRC set to 710 seconds. I guess this does matter.

In such situation in the past, I've also tried to lower the reconnect interval to few seconds (while BT kept running, without IP editing), with no influence. Could it be that the (710 sec, in my case) countdown still kept running without reset?

One more note: The Expert settings' Reconnect delay was initially 0, I've later tried to change it after the BOINC client update (10.2.2011 22:44-22:50) to 10 seconds (can be seen in the log below).

Code Select Expand

06 február 2011 - 23:36:53
06 február 2011 - 23:36:54 Language ---- User: 1051 (SKY), System: 1051 (SKY), Selected: 1051 (SKY) Used: 1051 (SKY)
06 február 2011 - 23:36:58 Main ---- BoincTasks Version: 0.99
06 február 2011 - 23:37:01 Computers ---- vetroplach , localhost
06 február 2011 - 23:37:01 Computers ---- pavilon6 , pavilon6
06 február 2011 - 23:37:03 GetLocalDirectory ---- C:\Program Files\eFMer\BoincTasks
06 február 2011 - 23:37:09 Connect ---- Connected to: Host: localhost, vetroplach, Port: 31416, BOINC Version: 6.12.11
06 február 2011 - 23:37:10 Connect, init ---- Host: pavilon6, pavilon6,Port: 31416, Couldn't resolve hostname
06 február 2011 - 23:37:13 GetLocalDirectory ---- C:\Program Files\eFMer\BoincTasks
(deleted Memory log, shortened)
10 február 2011 - 20:51:54 GetLocalDirectory ---- C:\Program Files\eFMer\BoincTasks
10 február 2011 - 22:44:30 Connect ---- Lost connection to: Host: localhost, vetroplach, Port: 31416
10 február 2011 - 22:58:55 BoincTasks is closing down all threads
10 február 2011 - 22:58:55 BoincTasks has closed down all threads
10 február 2011 - 22:58:59 BoincTasks version: 0.99
10 február 2011 - 22:58:59 Maximum number of computers: 60
10 február 2011 - 22:58:59 Computers ---- localhost get local password: (C:\Documents and Settings\All .... aplikací\BOINC\\gui_rpc_auth.cfg) blahblahblabla
10 február 2011 - 22:58:59 Computers ---- vetroplach , localhost
10 február 2011 - 22:58:59 Computers ---- pavilon6 , pavilon6
10 február 2011 - 22:58:59 GetLocalDirectory ---- C:\Program Files\eFMer\BoincTasks
10 február 2011 - 22:58:59 GetLocalDirectory ---- C:\Program Files\eFMer\BoincTasks
10 február 2011 - 22:59:00 Connect ---- Connected to: Host: localhost, vetroplach, Port: 31416, BOINC Version: 6.12.14
10 február 2011 - 22:59:00 GetLocalDirectory ---- C:\Program Files\eFMer\BoincTasks
10 február 2011 - 22:59:01 Connect, init ---- Host: pavilon6, pavilon6,Port: 31416, Couldn't resolve hostname
10 február 2011 - 22:59:14 Connect, init ---- Host: pavilon6, pavilon6,Port: 31416, Couldn't resolve hostname
10 február 2011 - 22:59:29 Connect, init ---- Host: pavilon6, pavilon6,Port: 31416, Couldn't resolve hostname
10 február 2011 - 22:59:44 Connect, init ---- Host: pavilon6, pavilon6,Port: 31416, Couldn't resolve hostname
.......


[fred]

Long story short: I've opened BT 0.99's window, started BOINC 6.12.11->6.12.14 update, finally launched BOINC. BT was again not able to reconnect, until I've "edited" (or touched) the localhost's IP address in BT (from "localhost" to the same "localhost" + <Enter>).
I'll edit this post tomorrow on Chrome - am tired and my IE is not willing to let me edit long text in small editing window of this forum :-(
One more preliminary note: The Expert settings' Reconnect delay was initially 0, I've changed it after the update to 10 seconds - can be seen in the log.

When you install a new BOINC version, the BOINC installer doesn't gracefully close BOINC. It just kills the process and what happens to the still open connections, I don't know.
So probably the whole connection has to be reinitialized, and a reconnect is probably not enough.

So the best way is to close down the client, close down BT, install the new version and restart BT. BT will start the new client.
Changing something in the computer page, is close to closing down BT and restarting it.

[Pepo]

Long story short: I've opened BT 0.99's window, started BOINC 6.12.11->6.12.14 update, finally launched BOINC. BT was again not able to reconnect, until I've "edited" (or touched) the localhost's IP address in BT (from "localhost" to the same "localhost" + <Enter>).

When you install a new BOINC version, the BOINC installer doesn't gracefully close BOINC. It just kills the process and what happens to the still open connections, I don't know.

This is quite good possible, that it just kills the whole process subtree. (Maybe I'll ask Rom Walton how the installer closes the client.) I can imagine that in order to gracefully close it, it would have to read its gui_rpc_auth.cfg, connect to it, communicate and issue the exit command - apparently not worth the hassle :-(
OK, I'm convinced.

So probably the whole connection has to be reinitialized, and a reconnect is probably not enough.

Maybe worth the try, if the connection is anyway already lost, say, for (3 x reconnect_interval)?

So the best way is to close down the client, [...] install the new version [...]

OK, seems to be the clean way to go. I was thinking that the installer would close the client gracefully, but actually, for security reasons, this should be not possible without authentication, yes?

close down BT, [...] and restart BT.

Will maybe not be necessary, if the client was closed gracefully.

BT will start the new client.

This is unfortunately not an option for me, at least on that machine, because BOINC runs there as a service (it is a multi-user machine without any advanced graphic card) and BT simply ignores this fact and runs the client as own subprocess, instead of doing some equivalent of "net start BOINC"  (reported some 1/2 year ago).

[Beyond]

Not specific to 0.99 but quite often when clicking on a task in History the right slider jumps to near the bottom and the user has to scroll upwards to find the desired task again.

[fred]

Not specific to 0.99 but quite often when clicking on a task in History the right slider jumps to near the bottom and the user has to scroll upwards to find the desired task again.

Is this tasks still there and not deleted.
What is your sorting.
Anybody else who is recognizing this.

[Beyond]

Either tasks that are reported , not reported or missed.  Sort order: completed with newest first (on top).

[fred]

Either tasks that are reported , not reported or missed.  Sort order: completed with newest first (on top).

Hmm, is the task still selected?
I can't reproduce it.

[Beyond]

Either tasks that are reported , not reported or missed.  Sort order: completed with newest first (on top).

Hmm, is the task still selected?
I can't reproduce it.

Yes, still selected.  If it doesn't do it right away, click  around on various completed tasks.  At least here it doesn't take long until the slider jumps to near the bottom.  Maybe it's something else on my machine causing it but BT is the only app that does this.

[Pepo]

Not specific to 0.99 but quite often when clicking on a task in History the right slider jumps to near the bottom and the user has to scroll upwards to find the desired task again.

What is your sorting.
Anybody else who is recognizing this.

Never happened for me (similar sorting, "v1 Completed + v2 Reported").
I can just see Messages jumping once to the top and then to bottom when displayed after a couple of hours. (Unsorted, apparently equivalent to "^1 Nr.") But this is probably something much different and known.

[fred]

Either tasks that are reported , not reported or missed.  Sort order: completed with newest first (on top).

Hmm, is the task still selected?
I can't reproduce it.

Yes, still selected.  If it doesn't do it right away, click  around on various completed tasks.  At least here it doesn't take long until the slider jumps to near the bottom.  Maybe it's something else on my machine causing it but BT is the only app that does this.

What Windows version are you using.

[Beyond]

Either tasks that are reported , not reported or missed.  Sort order: completed with newest first (on top).

Hmm, is the task still selected?
I can't reproduce it.

Yes, still selected.  If it doesn't do it right away, click  around on various completed tasks.  At least here it doesn't take long until the slider jumps to near the bottom.  Maybe it's something else on my machine causing it but BT is the only app that does this.

What Windows version are you using.

Win7-64.  Even tried a different mouse.  No change.  Also found that if I set The "ready to start" filter (combine) to off so that the number of enries is larger the same thing often happens in Tasks.  Tried cutting my history to 8 hours, it made no difference.

[Pepo]

In BT I see now 2 correctly finished tasks (project 1) and 1 errored-out task (project 2). They are already waiting a couple of hours in this state. No uploads are pending.

The tray icon's "Report all finished tasks" displays their count as 2. I believe that all "Ready to report" tasks (so, 3) should be counted and displayed.

[fred]

In BT I see now 2 correctly finished tasks (project 1) and 1 errored-out task (project 2). They are already waiting a couple of hours in this state. No uploads are pending.

The tray icon's "Report all finished tasks" displays their count as 2. I believe that all "Ready to report" tasks (so, 3) should be counted and displayed.

Check.