Message boards :
Number crunching :
Boinc v7.8.0 for linux
Message board moderation
Previous · 1 . . . 6 · 7 · 8 · 9 · 10 · Next
Author | Message |
---|---|
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
Look at my Pull Request #2065 for what's missing/broken. |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
Hmmm, appears a number of those were prior to July 23. Of the rest I see maybe 3 that affect the Client that aren't Windows related. OK, I'll be on the lookout for any of these problems with My Ubuntu BOINC, but, so far I haven't heard any reports of boinc client problems. The 7.4.53 build also doesn't have any problems with Time Tags in the Event Log. This Identifies the 7.5.0/7.6.0 release as the creator of the Time Tag Bug. https://github.com/BOINC/boinc/releases/tag/client_release%2F7.6%2F7.5.0 Apr 2, 2015, another Multi-Year Bug. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
Yes, they were all fixes which were available for deployment, but were left on the shelf - not included in any of the v7.8.x builds. That's why my pull request would transfer them from master to release. (correction - lib/filesys.cpp was updated for v7.8.2, but outside the proper commit/PR process) |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
I see, so, if I do start seeing problems with the client I'll know where to look. Right now I see changes to 7.6.0 DlgEventLog.cpp starting at line 339 that I can't find the the Change log, http://boinc.berkeley.edu/dev/forum_thread.php?id=10204#61459 Seems some of the 7.4.53 code was left out of 7.6.0. That appears the only change in 7.6.0 DlgEventLog.cpp. Any ideas? |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
The change logs are just an honest attempt by volunteers to write up what has happened in the past - you can't rely on them as the definitive record of history. For that, you have to use the git tools, and for that I'll have to use the big machine downstairs with the multiple monitors for comparisons. But I'm not going there until after Jeremy Corbyn has finished his conference speech. |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
Well, the obvious choice to replace the missing code doesn't work. 7.6.0 still has the missing Time Tags where 7.4.53 doesn't. Hmmm, this sounds interesting; MGR: continue updating Advanced Preferences dialog to new specification: split each day-of-week time span text field into separate starting and ending time text fields; rearrange source code to match new order of items on dialog; add missing validators; fix bugs; begin expanding tooltips to cover static text and checkboxes in addition to text edit fields. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
Right now I see changes to 7.6.0 DlgEventLog.cpp starting at line 339 that I can't find the the Change log, http://boinc.berkeley.edu/dev/forum_thread.php?id=10204#61459Well, I don't know where you get your code from, but I've just * Refreshed my comprehensive git clone * Exported the code as at tag 7.4.52 (there's no tag 7.4.53) * Exported the code as at tag 7.6.1 (there's no tag 7.6.0) * opened the two copies of DlgEventLog.cpp side-by-side on a big screen. The files seem to be the same until CDlgEventLog::CreateControls on line 282 Then tag 7.4.52 creates a new wxContextHelpButton in lines 339-354, which tag 7.6.1 doesn't have Then the files re-synchronise again with CDlgEventLog::SetFilterButtonText on line 357 of 7.4.52 / line 338 of 7.6.1, and remain in sync until the end of the file. So, the only difference is that they didn't bother with the context help button in v7.6 - that would be 06304700bae080d4e295c82dbda2907e84e22857 MGR: Remove context-sensitive help button. I don't think that takes us much further forward. |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
Well, I don't know where you get your code from, but I've just 7.4.53 Tag https://github.com/BOINC/boinc/blob/client_release/7/7.4/version.h 7.6.0 Tag https://github.com/BOINC/boinc/releases/tag/client_release%2F7.6%2F7.5.0 The problem is between those two. I'll let someone else sort it...good luck. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
Ah. You were picking up the tag for the Android hotfix - https://github.com/BOINC/boinc/commits/client_release/7/7.4 Not much for you there. |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
Any progress? If someone has any suggestions I can try the change and see if it makes a difference. It only takes about 5 minutes to compile a new version with the change. It appears someone else has noticed the Activity Indicator button doesn't work as expected in 16.04. That one is going to be fun as All the versions of BOINC that can run in Ubuntu 16.04 have that problem. Kinda hard to find a starting point when it happens on All the versions. At least with the Time Tags we have a starting point, not so with the Activity Menu; BTW, if you run BOINC 7.4.44 or 7.8.2 in Ubuntu 14.04 you won't have either of these two problems, plus, the Tasks page doesn't flip and the Simple View Works ;-) In fact, the only problem 7.4.44 has in 16.04 and above is the Activity button, and they All have that problem. |
W3Perl Send message Joined: 29 Apr 99 Posts: 251 Credit: 3,696,783,867 RAC: 12,606 |
I've upgraded to 7.8.2 from TBar (latest from September 28th) but I have problem running : ./boinccmd --host <hostname>:31416 --passwd <password> --get_cc_status Authorization failure: -102 Running on Ubunttu 16.04.3 with driver 375 or 384 Most of the time, it works fine but sometines, it don't. I had to revert back to 7.2.47. |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
I can't help you with the cmdline stuff, but have you tried the newer 7.4.44? 7.4.44 works better in 16.04 than 7.2.47. |
W3Perl Send message Joined: 29 Apr 99 Posts: 251 Credit: 3,696,783,867 RAC: 12,606 |
I can't help you with the cmdline stuff, but have you tried the newer 7.4.44? 7.4.44 works better in 16.04 than 7.2.47. I will try..thanks for the suggestion :) |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
Hmmmm, still nothing on the Outstanding Linux problems. This one hasn't received any attention at all, Linux Manager: bug/workround no longer needed? It's completely reproducible and quite easy to fix. This one has hit three weeks, Network activity radio button not following status in BOINC Just hit the Same Selection twice to avoid that one. The Time Tags from the 7.6.0 release is barely even annoying. Maybe we should run a Lottery? The choices could be; When will the Current Manager Bugs be fixed? 1) A Month 2) Within 6 Months 3) A year? 4) Not in My lifetime Well, seems the gang is trying to make a New Manager that doesn't use libWebView, so, I wouldn't count on the problems with the Old Manager being fixed anytime soon, MGR: support wxWidgets without webview Choice #4 seems possible, at least with the Manager for 16.04 and below. Fortunately, we have a current Manager for 12.04 to 17.04 that works better than any of the previous ones. It might be around for a while... |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
I actually read through all the referred links on GitHub in your last link. Wow. I came away with the impression of a big clu#4erF*@k. Too many cooks in the kitchen trying to bake a BOINC cake. And I cannot fathom why having videos in Notices is so damn important. Notices in the first place is just a PR device by the project. There hasn't been any real information provided there in years since Matt left. I barely ever give it any notice. :-} The only thing that the Manager needs to do is give us a FUNCTIONAL interface to the Client. If WxView or WxWebView breaks the Manager so badly now or in future Linux distributions, just get rid of it. I can do without Notices just fine. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
Yes, not having Videos or Images in the Notices wouldn't bother me at all. At one point it was suggested to have Social Media in the Manager, now that would have been a cluster. Fortunately, the Social Media angle seems to be gone. It might take a while to get BOINC working without WebView. I tried a build last night and of course it failed. This might take a while. |
Darrell Send message Joined: 14 Mar 03 Posts: 267 Credit: 1,418,681 RAC: 0 |
I actually read through all the referred links on GitHub in your last link. Wow. I came away with the impression of a big clu#4erF*@k. Too many cooks in the kitchen trying to bake a BOINC cake. And I cannot fathom why having videos in Notices is so damn important. Notices in the first place is just a PR device by the project. There hasn't been any real information provided there in years since Matt left. I barely ever give it any notice. :-} The only thing that the Manager needs to do is give us a FUNCTIONAL interface to the Client. If WxView or WxWebView breaks the Manager so badly now or in future Linux distributions, just get rid of it. I can do without Notices just fine. You are forgetting the big picture again. The Boinc system is designed for many projects. Some projects make extensive use of the Notices tab to inform their users of project outages and discoveries. ... and still I fear, and still I dare not laugh at the Mad Man! Queen - The Prophet's Song |
Darrell Send message Joined: 14 Mar 03 Posts: 267 Credit: 1,418,681 RAC: 0 |
When it comes to Linux, Choice #4 will be it unless you and other make the fixes. Remember, a few years backs the controlling developers decided to stop implementing changes for Linux and left it to the distro package managers to make and implement changes and fixes. ... and still I fear, and still I dare not laugh at the Mad Man! Queen - The Prophet's Song |
W3Perl Send message Joined: 29 Apr 99 Posts: 251 Credit: 3,696,783,867 RAC: 12,606 |
The job of distro package managers is not to find and resolve bug fixes...but to build package for their own distro. Maybe some of them post bug fixes on the boinc website but as there is no linux people, it is useless. We need a linux team to improve the client but if nobody commit the bug's Tbar have found, once again, this is useless. I will try to find why boinccmd is broken in 7.8 but it will be difficult as the problem cannot be reproduced every time. It seems to appear randomly :( |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
I will try to find why boinccmd is broken in 7.8 but it will be difficult as the problem cannot be reproduced every time. It seemsThe one difference I see is the boinccmd in 7.8 adds another variable to the cmdline. 7.2.47 int main(int argc, char** argv) { RPC_CLIENT rpc; int i, retval, port=0; MESSAGES messages; NOTICES notices; char passwd_buf[256], hostname_buf[256], *hostname=0; char* passwd = passwd_buf, *p; 7.8.2 int main(int argc, char** argv) { RPC_CLIENT rpc; int i, retval, port=0; MESSAGES messages; NOTICES notices; char passwd_buf[256], hostname_buf[256], *hostname=0; char* passwd = passwd_buf, *p, *q; bool unix_domain = false; For 7.8.2 and 7.4.44 you need to use, boinccmd [--host hostname] [--passwd passwd] [--unix_domain] command default hostname: localhost default password: contents of gui_rpc_auth.cfg Don't ask me what a unix_domain is, the descriptions I saw didn't provide an example. When I run it locally on the one machine it works every time. The App seems to be self contained, have you tried running the boinccmd from 7.2.47 with the other Apps from 7.8.2? I certainly hope No One is waiting for me to make any Code changes or Bug fixes. It will be a very long wait indeed as I don't do code. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.