Re: [boinc_dev] Mac builds in master are currently broken

2018-01-27 Thread Juha Sointusalo
On 27 January 2018 at 21:23, Christian Beer 
wrote:

> The restart is available on the webpage: click "Show all
> checks" on the PR than on "Details" next to travis-ci In the top right
> corner there should be a "Restart build" button this will restart all
> builds OR you can click on the build job number on the page and restart
> the individual jobs button "restart job" on the page that opens. You
> must be logged into Travis-CI (using your github account) to do this,
> permissions are automatically transfered from github.
>

Thanks. I've never been logged in to Travis so that explains why I have
never seen restart button.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] Mac builds in master are currently broken

2018-01-27 Thread Juha Sointusalo
On 27 January 2018 at 18:14, Christian Beer 
wrote:

> 1. A committer (other than Charlie or me to retain the 4 eyes principle)
> needs to merge PR#2323 which contains the fix for the Mac build, this
> will automatically refresh the buildcache for mac for the master branch
>

Done.


> 2. The cherry-pick in PR#2324 needs to be removed (by resetting the
> branch to the previous commit, not reverting the commit!)
>

Please do.


> 3. Once the cache is rebuilt the already failed mac build in PR#2327
> needs to be restarted (every committer can do that)
>

Is restarting available in web pages or is it necessary to use the command
line client?

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] server stable release issues

2018-01-14 Thread Juha Sointusalo
On 11 January 2018 at 21:59, David Anderson  wrote:

> 3) Assuming the cycles are independent, how should we number server
> releases?
> We could use the same numbering for both, but this has problems:
> - A sequence of releases in one part would cause gaps in the release
> numbers
>   of the other part.
> - It would create the false impression that there's a connection or
>   dependency between client and server releases with the same number.
> So my recommendation is that we start with 1.1.1 for the server version
> number.
>

Since you are going to include building apps in server release that
includes API_VERSION but you can't rewind API_VERSION without breaking
everything. The client also checks scheduler version when deciding if it's
going to accept preferences from the server. I don't know if there is any
third party code that is checking server version for, say, feature checking
or something else.

The version number is also used in various forms as library version, either
embedded in the library or in its filename. I don't know what happens when
you rewind those version numbers. Maybe break all Debian packages?

If you add a new version number that is only used for tagging the release
and internally the code uses something else I think that will only end up
being confusing.

So I think that either it would be best to stay with only one version
number or that you need to break all BOINC components apart and even in
that case you can't rewind version numbers.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] BOINC 7.8.5 for Mac

2018-01-13 Thread Juha Sointusalo
I agree that screensavers are good for marketing. We do get questions about
screensavers in forums every now and then so clearly there are people
interested in running them.

Sometimes when people upgrade BOINC and see benchmark numbers go up they
get excited that now their computer does more work and then we have to
explain that "sorry, that's not how it works". I was just curious if this
would be the first time when BOINC version actually does make a difference.
I didn't think about screensaver going to blank screen after a while. That
certainly mitigates any slowdown.

-Juha

On 13 January 2018 at 03:11, Charlie Fenton <charl...@ssl.berkeley.edu>
wrote:

> I have not checked task run times. As I understand how the IOSurface APIs
> work, once the graphics app has been rebuilt with the latest libraries, it
> does not move bitmaps around; it uses the GPU directly and shared memory.
>
> However, the fallback method I just added is quite inefficient because it
> does copy bitmaps in RAM, and so is likely to slow things down. That is why
> I initially implemented the IOSurface method. Hopefully, all projects will
> upgrade their graphics apps sooner rather than later by relinking with the
> new libraries.
>
> Adding the new fallback method is definitely a tradeoff. As I wrote in the
> PR <https://github.com/BOINC/boinc/pull/2294>, I felt that the project
> "screensavers" are an important marketing tool. When people see the
> graphics on a friend's computer, they can become curious and ask about what
> they see, helping spread word of mouth about BOINC And I believe that few
> BOINC projects have yet updated their graphics apps to work with the BOINC
> screensaver under Mac OS 10.13. I asked David's opinion and he agreed that
> I should proceed with this change.
>
> On versions of OS X older than the latest OS 10.13, there will be no
> difference in how the screensaver displays the graphics so there will be no
> new effect on CPU caches or task run times.
>
> Running the screensaver has always had some effect on task run times,
> since it is an additional process. That is why the default is to go to a
> blank screen after several minutes.
>
> Cheers,
> --Charlie
>
> > On Jan 12, 2018, at 10:13 AM, Juha Sointusalo <juha.sointus...@gmail.com>
> wrote:
> >
> > On 12 January 2018 at 13:38, Charlie Fenton <charl...@ssl.berkeley.edu>
> > wrote:
> >
> >> This allows older project graphics apps to be displayed by the Mac
> >> screensaver under OS 10.13 High Sierra, though at a slower frame rate
> than
> >> project graphics apps which have been relinked with the BOINC graphics
> >> libraries version 7.8.3 or later. The slower frame rate can make
> animations
> >> appear less smooth.
> >>
> >
> > I don't know how these changes work on the OS side, under the hood.
> > Assuming the worst, that this works by copying bitmaps around, I wonder
> > what kind of effect this has on task run times. It might not use CPU time
> > all that much but it could slow down apps by trashing CPU caches.
> >
> > Did you happen to check task run times before and after this change?
> >
> > -Juha
> > ___
> > boinc_dev mailing list
> > boinc_dev@ssl.berkeley.edu
> > https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> > To unsubscribe, visit the above URL and
> > (near bottom of page) enter your email address.
> >
>
>
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] BOINC 7.8.5 for Mac

2018-01-12 Thread Juha Sointusalo
On 12 January 2018 at 13:38, Charlie Fenton 
wrote:

> This allows older project graphics apps to be displayed by the Mac
> screensaver under OS 10.13 High Sierra, though at a slower frame rate than
> project graphics apps which have been relinked with the BOINC graphics
> libraries version 7.8.3 or later. The slower frame rate can make animations
> appear less smooth.
>

I don't know how these changes work on the OS side, under the hood.
Assuming the worst, that this works by copying bitmaps around, I wonder
what kind of effect this has on task run times. It might not use CPU time
all that much but it could slow down apps by trashing CPU caches.

Did you happen to check task run times before and after this change?

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] Build Windows Client

2017-11-16 Thread Juha Sointusalo
On 16 November 2017 at 23:04, Kevin Reed  wrote:

> That makes sense.  Thanks for letting me know.  Has there been a decision
> about when BOINC will stop supporting Windows XP?
>

David said recently, somewhere can't remember where, that he would like
that XP is still supported. I think Seti still has/had a couple of thousand
XP host.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] Build Windows Client

2017-11-16 Thread Juha Sointusalo
On 15 November 2017 at 23:40, Kevin Reed  wrote:

> The dependencies included in the 7.8.2 client version appear to be newer
> than the ones in the boinc_depends_win_vs2013 repository so I was wondering
> if there was a different source.
>

I believe there was some problem with XP compatibility with VS2013 builds
so Rom and David went back to building the official releases with VS2010. I
suppose at that point keeping the VS2013 dependencies up-to-date was
forgotten.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] Linux build issues

2017-11-16 Thread Juha Sointusalo
On 16 November 2017 at 21:28, Kathryn Marks  wrote:

> I've tried to install SSL through the package manager (I'm, not fluent in
> apt-get).  I found a old post on the boinc message boards that someone
> solved the problem by installing libculibcurl4-openssl-devrl4-openssl-dev
> but that didn't help me.
>

Did you try installing libssl-dev package?

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] [boinc_projects] BOINC - October 2017 VirtualBox and VBoxWrapper updates

2017-11-06 Thread Juha Sointusalo
On 6 November 2017 at 10:17, Laurence  wrote:

> Hi Jacob,
> On 05/11/17 10:14, Jacob Klein wrote:
>
> David / Juha / Rom:
>
> I have concluded my testing (took about 6 hours), and 26200 has some serious 
> problems!
>
> Attached is a .zip of my full results, across my testing with LHC@Home and 
> RNA World. It includes a results summary, results detail files of stderr.txt 
> logs, and the app_info.xml files I used.
>
> You don't need to test on LHC@home as are building our own vboxwrapper
> while we are waiting for PR 1946
>  to be merged.
>

The reason I tested on LHC is that I wanted to test on real world apps, LHC
has real world apps and I have already signed up there. That's all. Maybe
LHC-dev would have been better choice or maybe I should have asked you for
permission first but at that time the risk of VirtualBox 5.2 acting bad and
tasks returning bad science results seemed low enough.

I haven't run CMS or LHCb tasks for a while and I think the VM images and
job scripts were outdated so I had to test with ATLAS and Theory only.
There's a few completed tasks now and no sign of problems so far.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] BOINC - October 2017 VirtualBox and VBoxWrapper updates

2017-11-05 Thread Juha Sointusalo
On 5 November 2017 at 22:22, Jacob Klein  wrote:

> Maybe Juha gave hints, not sure.
>

Other than making sure the source tree is up to date and full rebuild, not
much hints.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] BOINC - October 2017 VirtualBox and VBoxWrapper updates

2017-11-05 Thread Juha Sointusalo
On 5 November 2017 at 11:14, Jacob Klein  wrote:

> David / Juha / Rom:
>
> I have concluded my testing (took about 6 hours), and 26200 has some
> serious problems!
>

There seems to be something wrong in the vboxwrapper David built. I can
reproduce the problems with it.

I re-built vboxwrapper myself, with VS2010 and VS2013 to see if it's
something with VS version. Neither had problems with my test app. Now I
have ATLAS and Theory task running with vboxwrapper built with VS2013 and
the tasks seem to be working fine, or at least started fine.

Jacob, here's something for you to test:
https://drive.google.com/open?id=13naXH8_mPg3b4kVrvRLPUfw2yY6cGnaW .
Version numbers are off, don't worry about them.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] Small tweak to next release would be appreciated

2017-11-04 Thread Juha Sointusalo
On 4 November 2017 at 21:11, Chris Raisin  wrote:

> All other switches of view keep the BOINC Manager on the screen currently
> in use, only switching to either
>
> “Simple View” or “Advanced View” sends the Manager careering back to the
> Main Screen. If this switch of views does
> that, why don’t all changes of views (such as changing to Statistics or
> back to Tasks) also do this?
>

 Technicalities I think: the Simple View and Advanced View are different
windows and the Manager checks window's position when it's just about to
show it.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] BOINC - October 2017 VirtualBox and VBoxWrapper updates

2017-11-04 Thread Juha Sointusalo
On 4 November 2017 at 16:27, Jacob Klein  wrote:

> Rom has a checkin to fix the tlb to use the v5.2.0 release version instead
> of a pre-release version.
> I think it needs merged.
> It is located here:
> https://github.com/BOINC/boinc/pull/2198
>
> Could somebody please merge that, then convert that into a new VBoxWrapper
> that I can test?
>

Merged.

David, could you build a new version so that Jacob can start testing 5.2.0?
I could send Jacob the one I compiled but I think a more official version
would be appropriate.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] Small tweak to next release would be appreciated

2017-11-04 Thread Juha Sointusalo
I don't think that having a setting for everything makes good software. It
tends to be an awful experience to try to configure a software that has a
hundred different settings. I would prefer a software that automatically
does the right thing.

Since the Manager already saves the window size and position, using the
same display as the previously would, in my opinion, be the right thing to
do. I think the Manager already has code that checks that the window
titlebar is at least partially visible on primary display so all that would
need to be done is change that check to make sure the titlebar is visible
on some available display.

Dialogs would need some additional care. At least some dialogs have their
position (and therefore display) saved, but since they are modal dialogs I
think they should open on the same display as the Manager main window.
Event Log would be ok to open on the same display as previously.

I don't think a broken backlight is a problem. If a monitor doesn't work
you power it off or disconnect and therefore it is not available. If others
firmly believe that it could be a problem I would suggest a "safe mode"
that starts the Manager with default everything.

-Juha

On 2 November 2017 at 11:47, Richard Haselgrove <
r.haselgr...@btopenworld.com> wrote:

> Thanks Vitali - that might do it.
>
> Although it isn't clear from the way that Chris worded the original
> request, BOINC does already remember the position of the Manager window
> between sessions: all that would be needed is to provide controls to
> over-rule the 'automatic re-home to display 1 at startup' code. Window
> location is stored in registry keys like
>
> [HKEY_CURRENT_USER\Software\Space Sciences Laboratory, U.C.
> Berkeley\BOINC Manager]
> "WindowIconized"=dword:
> "WindowMaximized"=dword:
> "Width"=dword:05ba
> "Height"=dword:040e
> "XPos"=dword:01c6
> "YPos"=dword:
> "GUISelection"=dword:0001
>
> On Thursday, 2 November 2017, 9:38, Vitalii Koshura <
> lestat.de.lion...@gmail.com> wrote:
>
>
>  Hello Richard,
>
> Thank you for you comments.
> In this case, I guess, we can make this configurable and let user decide
> whether he or she wants to keep BOINC window position or to see it always
> of the first display.
>
> Thanks
>
> Best regards,
> Vitalii Koshura
>
> 2017-11-02 11:30 GMT+02:00 Richard Haselgrove <
> r.haselgr...@btopenworld.com>
> :
>
> > I think we should be a little cautious about changing this: I think the
> > original decision to make all windows appear first on display 1 may have
> > been deliberate, and done for a purpose. Check the code for comments
> first.
> >
> > I use dual displays as well (1920x1200 and 1600x1200): I also have
> > multiple computers set up to use both those displays, via two separate
> KVM
> > switches. It gets quite complicated, especially because the machines have
> > three GPUs each, one an intel running headless. It can get confusing.
> >
> > The problem is, from experience: if a hardware display becomes
> unavailable
> > for any reason, but an application is set to start up on it, it can be
> > extremely difficult to restore the application to the visible primary
> > monitor. Software which is designed to 'always start on display 1', like
> > BOINC, is intended to be easily recoverable during hardware failure or
> > configuration changes. Remember that in some failure modes (e.g.
> backlight
> > failure), the monitor firmware can report 'all is well and usable' to
> > Windows during hardware detection at startup.
> >
> >
> > On Wednesday, 1 November 2017, 23:39, Vitalii Koshura <
> > lestat.de.lion...@gmail.com> wrote:
> >
> >
> > Hello Chris,
> >
> > Thank you.
> > I'll try to reproduce and fix it.
> >
> > Best regards,
> > Vitalii Koshura
> >
> > 2017-11-01 23:56 GMT+02:00 Chris Raisin :
> >
> > > Hi Vitalii,
> > >
> > > I run under Windows 10 (Latest public release)
> > >
> > >
> > >
> > > Cheers
> > >
> > > Chris
> > >
> > >
> > >
> > > *From:* Vitalii Koshura [mailto:lestat.de.lion...@gmail.com]
> > > *Sent:* Thursday, 2 November 2017 8:36 AM
> > > *To:* Chris Raisin
> > > *Cc:* BOINC Developers Mailing List
> > > *Subject:* Re: [boinc_dev] Small tweak to next release would be
> >
> > > appreciated
> > >
> > >
> > >
> > > Hello Chris,
> > >
> > >
> > >
> > > Just wondering which OS do you use to run BOINC?
> > >
> > >
> > >
> > > Thanks
> > >
> > >
> > > Best regards,
> > >
> > > Vitalii Koshura
> > >
> > >
> > >
> > > 2017-11-01 23:05 GMT+02:00 Chris Raisin :
> > >
> > > I have been a user of BOINC Manager for many years, but one thing
> > > continually "bugs" me.
> > >
> > >
> > >
> > > I run a system on which I have multiple screens, and I keep BOINC on
> > > screen
> > > 2
> > >
> > > (away from my general "Work Area" on Screen 1).
> > >
> > >
> > >
> > > Every time I start up my system (albeit not often since it is normally
> > > running 24 hours per day)
> > > I have to 

Re: [boinc_dev] [boinc_alpha] 7.8.2 released

2017-09-30 Thread Juha Sointusalo
I don't know if my suggestion of including account manager fix prompted
this question. I think there has been quite a lot of changes to account
manager code. If the fix to non stop account manager contacts isn't easily
separated from other changes, that is, it would pull lot of unrelated
changes, then we just have to forget about including it in 7.8.3.

I agree with Charlie. 7.10 should have a good amount of testing, say, 2+
weeks. If it doesn't have any hard bugs, great. But it might have and it
might take 2+ months to fix bugs. Compare that to 7.8.3. You build it
today, we test it and it should be good to release next week.

-Juha


On 30 September 2017 at 01:10, David Anderson <da...@ssl.berkeley.edu>
wrote:

> At this point master has lots of fixes and nothing obviously destabilizing.
> Should we go for a 7.10 release rather than 7.8.3?
> -- D
>
> On 9/29/2017 7:44 AM, Juha Sointusalo wrote:
>
> Please include also the fix to the non stop account manager contacts.
> There has been a few questions about it as well.
>
> -Juha
>
> On 29 September 2017 at 10:08, Richard Haselgrove <
> r.haselgr...@btopenworld.com> wrote:
>
>> Could you please include your
>>
>> client: eliminate possible buffer overflow in reporting result errors
>>
>>
>> at the same time? We ran into a big problem with CPDN about 10 days after
>> v7.8.2 was released, which demonstrated exactly that problem.
>>
>> On Friday, 29 September 2017, 3:15, David Anderson <
>> da...@ssl.berkeley.edu> wrote:
>>
>>
>>  I plan to do a 7.8.3 test release when Charlie finishes;
>> this will have the slot directory cleanup fix as well.
>>
>> After that I'll do a 7.9 release based on the current code,
>> which has lots of changes and fixes.
>>
>> -- David
>>
>> On 9/28/2017 5:50 PM, Charlie Fenton wrote:
>> > Project graphics apps do not appear in the BOINC screensaver on OS
>> 10.13. I'm working on a fix.
>> >
>> > Cheers,
>> > --Charlie
>> >
>> > On Sep 28, 2017, at 12:36 PM, Georges Vinotte <g.vino...@laposte.net>
>> wrote:
>> >> Hi Guys,
>> >>
>> >> I tested BM 7.8.2 and 7.6.34 on Mac OS High Sierra (10.13)
>> >>
>> >> No specifics bugs, both are running as well as under Mac OS Sierra
>> (10.12.6)
>> >>
>> >> Cheers,
>> >> Georges
>> >>
>> >>
>> >>> Le 29 août 2017 à 21:45, David Anderson <da...@ssl.berkeley.edu> a
>> écrit :
>> >>>
>> >>> A new client is available for testing on Win and Mac.
>> >>> The changes relative to 7.8.1 are:
>> >>> - fix slow startup problem on Win
>> >>> - update translation files.
>> >>>
>> >>> This is a release candidate.
>> >>> Please report test results soon:
>> >>> https://boinc.berkeley.edu/alpha/test_form.php
>> >>>
>> >>> Thanks --
>> >>>
>> >>> David
>> >>> ___
>> >>> boinc_alpha mailing list
>> >>> boinc_al...@ssl.berkeley.edu
>> >>> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
>> >>> To unsubscribe, visit the above URL and
>> >>> (near bottom of page) enter your email address.
>> >> ___
>> >> boinc_alpha mailing list
>> >> boinc_al...@ssl.berkeley.edu
>> >> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
>> >> To unsubscribe, visit the above URL and
>> >> (near bottom of page) enter your email address.
>> >>
>>
>> ___
>> boinc_alpha mailing list
>> boinc_al...@ssl.berkeley.edu
>> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
>> To unsubscribe, visit the above URL and
>> (near bottom of page) enter your email address.
>>
>>
>> ___
>> boinc_alpha mailing list
>> boinc_al...@ssl.berkeley.edu
>> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
>> To unsubscribe, visit the above URL and
>> (near bottom of page) enter your email address.
>>
>
>
>
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] [boinc_alpha] 7.8.2 released

2017-09-29 Thread Juha Sointusalo
Please include also the fix to the non stop account manager contacts. There
has been a few questions about it as well.

-Juha

On 29 September 2017 at 10:08, Richard Haselgrove <
r.haselgr...@btopenworld.com> wrote:

> Could you please include your
>
> client: eliminate possible buffer overflow in reporting result errors
>
>
> at the same time? We ran into a big problem with CPDN about 10 days after
> v7.8.2 was released, which demonstrated exactly that problem.
>
> On Friday, 29 September 2017, 3:15, David Anderson <
> da...@ssl.berkeley.edu> wrote:
>
>
>  I plan to do a 7.8.3 test release when Charlie finishes;
> this will have the slot directory cleanup fix as well.
>
> After that I'll do a 7.9 release based on the current code,
> which has lots of changes and fixes.
>
> -- David
>
> On 9/28/2017 5:50 PM, Charlie Fenton wrote:
> > Project graphics apps do not appear in the BOINC screensaver on OS
> 10.13. I'm working on a fix.
> >
> > Cheers,
> > --Charlie
> >
> > On Sep 28, 2017, at 12:36 PM, Georges Vinotte 
> wrote:
> >> Hi Guys,
> >>
> >> I tested BM 7.8.2 and 7.6.34 on Mac OS High Sierra (10.13)
> >>
> >> No specifics bugs, both are running as well as under Mac OS Sierra
> (10.12.6)
> >>
> >> Cheers,
> >> Georges
> >>
> >>
> >>> Le 29 août 2017 à 21:45, David Anderson  a
> écrit :
> >>>
> >>> A new client is available for testing on Win and Mac.
> >>> The changes relative to 7.8.1 are:
> >>> - fix slow startup problem on Win
> >>> - update translation files.
> >>>
> >>> This is a release candidate.
> >>> Please report test results soon:
> >>> https://boinc.berkeley.edu/alpha/test_form.php
> >>>
> >>> Thanks --
> >>>
> >>> David
> >>> ___
> >>> boinc_alpha mailing list
> >>> boinc_al...@ssl.berkeley.edu
> >>> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
> >>> To unsubscribe, visit the above URL and
> >>> (near bottom of page) enter your email address.
> >> ___
> >> boinc_alpha mailing list
> >> boinc_al...@ssl.berkeley.edu
> >> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
> >> To unsubscribe, visit the above URL and
> >> (near bottom of page) enter your email address.
> >>
>
> ___
> boinc_alpha mailing list
> boinc_al...@ssl.berkeley.edu
> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.
>
>
> ___
> boinc_alpha mailing list
> boinc_al...@ssl.berkeley.edu
> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.
>
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

2017-09-28 Thread Juha Sointusalo
On 28 September 2017 at 10:02, Charlie Fenton 
wrote:

> But you are correct that my proposed change may be useful only for the
> default screensaver graphics app (boincscr), which should never have
> multiple instances running simultaneously.
>

I think the default screensaver already does that. I have stderrscr.txt,
stderrscrgfx.txt, stdoutscr.txt and stdoutscrgfx.txt in
C:\Users\Juha\AppData\Roaming\BOINC.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

2017-09-28 Thread Juha Sointusalo
The client needs to know that some program is still using the slot
directory. stderrgfx.txt isn't a perfect solution to the problem but I
don't think there is any other mechanism to do it. I don't think the client
really knows about graphics apps other than being some extra files it needs
to download.

I suppose a better solution would be using memory mapped files to
communicate between science app and graphics app but that would be API
change.

In other words, I think it's better to keep stderrgfx.txt for now.

-Juha

On 28 September 2017 at 00:54, David E Kim <de...@u.washington.edu> wrote:

> Yes, I’ll probably disable that.
>
> > On Sep 27, 2017, at 2:51 PM, Charlie Fenton <charl...@ssl.berkeley.edu>
> wrote:
> >
> > On Sep 27, 2017, at 12:49 PM, Juha Sointusalo <juha.sointus...@gmail.com>
> wrote:
> >> I did see that the graphics app opens stderrgfx.txt file in slot
> directory
> >> and keeps it open as long as the graphics are open.
> >
> > That is not terribly useful, since it will be gone after the slot
> directory is cleaned. It should go in the per-user directory, which on
> Windows is C:/Users/{username}/AppData/Roaming/BOINC/ or at least in the
> project directory.
>
>
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

2017-09-27 Thread Juha Sointusalo
On 27 September 2017 at 23:39, David E Kim  wrote:

> Thanks for running these tests!
>
> So is it a windows only issue?  It appears so for R@h.
>

Yep.

Who is responsible for the BOINC client releases?
>

David Anderson.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

2017-09-27 Thread Juha Sointusalo
On 27 September 2017 at 22:49, Juha Sointusalo <juha.sointus...@gmail.com>
wrote:

> I installed 7.8.2 a few minutes ago to make sure I can see the bug with
> that version. It will take about one hour to get results.
>

Yep, it's the bug in 7.8.2.

A Rosetta task exits and client tries to clean the slot directory:

27-Sep-2017 22:50:15 [---] [slot] cleaning out slots/5: handle_exited_app()
27-Sep-2017 22:50:15 [---] [slot] removed file
slots/5/boinc_checkpoint_count.txt
...
27-Sep-2017 22:50:17 [---] [slot] failed to remove file
slots/5/stderrgfx.txt: Error 32
27-Sep-2017 22:50:17 [---] [slot] removed file slots/5/stdout.txt
27-Sep-2017 22:50:17 [---] [slot] removed file slots/5/t000_.200.3mers.gz
27-Sep-2017 22:50:17 [---] [slot] removed file slots/5/t000_.200.9mers.gz
27-Sep-2017 22:50:17 [---] [slot] removed file slots/5/t000_.fasta
27-Sep-2017 22:50:17 [Rosetta@home] Computation for task
rb_09_27_71535_120475__t000__ab_robetta_IGNORE_THE_REST_516294_956_0
finished

Starting a new task in slot 5 even though it wasn't clean:

27-Sep-2017 22:50:17 [Rosetta@home] [slot] assigning slot 5 to
tj_9_24_juncA_X_1na0A_DHR54_l2_t3_t3_fragments_abinitio_SAVE_ALL_OUT_515776_399_0
27-Sep-2017 22:50:19 [---] [slot] removed file slots/5/init_data.xml
27-Sep-2017 22:50:19 [Rosetta@home] setup_file:
projects/boinc.bakerlab.org_rosetta/minirosetta_3.73_windows_x86_64.exe
(input)
...
27-Sep-2017 22:50:19 [Rosetta@home] [cpu_sched] Restarting task
tj_9_24_juncA_X_1na0A_DHR54_l2_t3_t3_fragments_abinitio_SAVE_ALL_OUT_515776_399_0
using minirosetta version 373 in slot 5
27-Sep-2017 22:50:20 [Rosetta@home] [sched_op] Reason: Unrecoverable error
for task
tj_9_24_juncA_X_1na0A_DHR54_l2_t3_t3_fragments_abinitio_SAVE_ALL_OUT_515776_399_0
27-Sep-2017 22:50:20 [---] [slot] cleaning out slots/5: handle_exited_app()
27-Sep-2017 22:50:20 [---] [slot] removed file slots/5/boinc_lockfile
27-Sep-2017 22:50:20 [---] [slot] removed file slots/5/default.out.gz
27-Sep-2017 22:50:20 [---] [slot] removed file slots/5/graphics_app
27-Sep-2017 22:50:20 [---] [slot] removed file slots/5/Helvetica.txf
27-Sep-2017 22:50:20 [---] [slot] removed file slots/5/init_data.xml
27-Sep-2017 22:50:20 [---] [slot] removed file
slots/5/minirosetta_3.73_windows_x86_64.exe
27-Sep-2017 22:50:20 [---] [slot] removed file
slots/5/minirosetta_database.zip
27-Sep-2017 22:50:20 [---] [slot] removed file slots/5/stderr.txt
27-Sep-2017 22:50:20 [---] [slot] failed to remove file
slots/5/stderrgfx.txt: Error 32
27-Sep-2017 22:50:20 [---] [slot] removed file slots/5/stdout.txt
27-Sep-2017 22:50:20 [---] [slot] removed file
slots/5/tj_9_24_juncA_X_1na0A_DHR54_l2_t3_t3_fragments_fold_data.zip
27-Sep-2017 22:50:20 [Rosetta@home] Computation for task
tj_9_24_juncA_X_1na0A_DHR54_l2_t3_t3_fragments_abinitio_SAVE_ALL_OUT_515776_399_0
finished
27-Sep-2017 22:50:20 [Rosetta@home] Output file
tj_9_24_juncA_X_1na0A_DHR54_l2_t3_t3_fragments_abinitio_SAVE_ALL_OUT_515776_399_0_r2138012187_0
for task
tj_9_24_juncA_X_1na0A_DHR54_l2_t3_t3_fragments_abinitio_SAVE_ALL_OUT_515776_399_0
absent

Starting one more task, still using slot 5:

27-Sep-2017 22:50:20 [Rosetta@home] [slot] assigning slot 5 to
ProBinder_S_15_fragments_fold_SAVE_ALL_OUT_516202_914_0
27-Sep-2017 22:50:22 [---] [slot] removed file slots/5/init_data.xml
27-Sep-2017 22:50:22 [Rosetta@home] setup_file:
projects/boinc.bakerlab.org_rosetta/minirosetta_3.73_windows_intelx86.exe
(input)
...
27-Sep-2017 22:50:22 [Rosetta@home] [cpu_sched] Restarting task
ProBinder_S_15_fragments_fold_SAVE_ALL_OUT_516202_914_0 using minirosetta
version 373 in slot 5
27-Sep-2017 22:50:23 [Rosetta@home] [sched_op] Deferring communication for
00:03:49
27-Sep-2017 22:50:23 [Rosetta@home] [sched_op] Reason: Unrecoverable error
for task ProBinder_S_15_fragments_fold_SAVE_ALL_OUT_516202_914_0
27-Sep-2017 22:50:23 [---] [slot] cleaning out slots/5: handle_exited_app()
27-Sep-2017 22:50:23 [---] [slot] removed file slots/5/boinc_lockfile
27-Sep-2017 22:50:23 [---] [slot] removed file slots/5/default.out.gz
27-Sep-2017 22:50:23 [---] [slot] removed file slots/5/graphics_app
27-Sep-2017 22:50:23 [---] [slot] removed file slots/5/Helvetica.txf
27-Sep-2017 22:50:23 [---] [slot] removed file slots/5/init_data.xml
27-Sep-2017 22:50:23 [---] [slot] removed file
slots/5/minirosetta_3.73_windows_intelx86.exe
27-Sep-2017 22:50:23 [---] [slot] removed file
slots/5/minirosetta_database.zip
27-Sep-2017 22:50:23 [---] [slot] removed file
slots/5/ProBinder_S_15_fragments_data.zip
27-Sep-2017 22:50:23 [---] [slot] removed file slots/5/stderr.txt
27-Sep-2017 22:50:23 [---] [slot] failed to remove file
slots/5/stderrgfx.txt: Error 32
27-Sep-2017 22:50:23 [---] [slot] removed file slots/5/stdout.txt
27-Sep-2017 22:50:23 [Rosetta@home] Computation for task
ProBinder_S_15_fragments_fold_SAVE_ALL_OUT_516202_914_0 finished
27-Sep-2017 22:50:23 [Rosetta@home] Output file
ProBinder_S_15_fragments_fold_SAVE_ALL_OUT_516202_914_0_r90796

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

2017-09-27 Thread Juha Sointusalo
On 27 September 2017 at 01:17, David E Kim  wrote:

> Would a reversion or fix to the BOINC client be the best option to save
> wasted computing and bandwidth?  If indeed there is a bug?
>

I added Rosetta to my Windows host earlier today and run it on self built
development version of BOINC. On this version the app worked ok which
strongly hints that the problem is using dirty slot directories. I
installed 7.8.2 a few minutes ago to make sure I can see the bug with that
version. It will take about one hour to get results.

I did see that the graphics app opens stderrgfx.txt file in slot directory
and keeps it open as long as the graphics are open. And that the graphics
app runs a few seconds longer than the corresponding task. In working
clients the open stderrgfx.txt prevents the client from using the slot
directory until the graphics app is closed.

In 7.8.2 the client's check for empty slot directory is broken and the
client uses slot directories for new tasks even if the directory still has
some files left over from the previous task. In Rosetta's case this means
the client starts a new task in a slot that was just used by previous task.
The app then tries to create a shared memory segment with name
"boinc_minirosetta_". But a segment with this name is already open
in the graphics app for the previous task and creating a new one fails.

The bug with client using dirty slot directories is already fixed (the fix
was actually available well before 7.8.2 was released). I don't know when
there will be a bug fix release.

Until everyone has downgraded to 7.6.33 or there has been a bug fix release
and everyone has upgraded to it you could change your app so that it
doesn't crash if boinc_graphics_make_shmem() fails. If you can't easily
disable graphics if boinc_graphics_make_shmem() fails you could malloc() a
same size memory chunk and use that as a dummy shared memory. Some tasks
then might not have graphics available but at least they won't crash.

Do you know if the scheduler has a way to skip client versions per platform
> type?
>

I'm not seeing a way to block a specific client version. There is
 and >min_core_client_version> in plan classes but
having to use those to block client versions could get ugly pretty fast.
http://boinc.berkeley.edu/trac/wiki/AppPlanSpec


> So this has been a general finding with other projects?
>

Rosetta is the first one I know to have tasks crash after failing to create
shared memory segment. Other projects have had tasks being aborted by the
client due to task supposedly exceeding disk limit. The limit was exceeded
because the slot directory had files left over from the previous task,
often a VM task with GB sized VM image file.

And there was one report about VM task using VM image from another app.

Sorry for this long thread.
>

No problem.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

2017-09-26 Thread Juha Sointusalo
On 27 September 2017 at 00:47, David E Kim  wrote:

> But the errors only recently started to occur consistent with our recent
> app release.
>

Yep. And 7.8.2 was just released three weeks ago just to muddy things.

So it is a boinc client issue and not a boinc api issue?  The latest
> official client release for windows platforms is buggy?
>

At the moment it looks to me like it's the client. And yes, the latest
client release is buggy.

But check the failed tasks, are they all or mostly from 7.8.2 clients?

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

2017-09-26 Thread Juha Sointusalo
On 26 September 2017 at 23:59, David E Kim  wrote:

> Ok, if that’s the case maybe it is related to using the same “prog_name”.
> That definitely wouldn’t help the situation.
>
> I’ll test that change.  Thanks!
>

That could help at start while you still have tasks for both apps but
assuming you plan on moving all tasks to the new app I think you'll only
get a temporary reduction in error rate. If the problem is what I think it
is the only real solution is to get users to move to a working client
version.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

2017-09-26 Thread Juha Sointusalo
Windows only, BOINC version 7.8.2 only? And it's
boinc_graphics_make_shmem() that fails?

If it's 7.8.2 it looks like yet another case of using dirty slot
directories. The shared memory segment's name that is really used contains
the number of the slot directory. If the segment already exists
boinc_graphics_make_shmem() fails. The segment might still be open in
graphics app for the previous task using the slot directory.

The graphics app probably has some file open in the slot directory, like
stderr, and that prevented previous client versions from using the slot
directory.

If it's 7.8.2 you'll just have to tell everyone to skip that version.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

2017-09-26 Thread Juha Sointusalo
On 26 September 2017 at 20:55, David E Kim  wrote:


> failed to create shared mem segment: minirosetta Size: 25001672
>

Are you trying to create 25 GB shared memory segment?

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] 7.10 client release

2017-09-18 Thread Juha Sointusalo
On 18 September 2017 at 00:47, David Anderson 
wrote:

> Master has a number of improvements relative to 7.8.2,
> so I'd like to make a release branch and start testing soon.
>
> Is there any work in progress that I should wait for?
>

I broke client's logging and I'd like to fix it before the next version.
Please wait a few days.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] BOINC and NAT64

2017-08-22 Thread Juha Sointusalo
On 17 August 2017 at 12:18, Jord van der Elst  wrote:

> HI all,
>
> On the BOINC forums a user asks the following:
> ***
> Has anyone tried using BOINC in a NAT64+DNS64 network? I've moved my laptop
> to such network (after previously using it in IPv4-only and dual-stack
> Internet-connected networks), and nothing seems to work


Charlie,

The client has this code in it:

#ifdef __APPLE__
// cURL 7.19.7 with c-ares 1.7.0 did not fall back to IPv4 when IPv6
// DNS lookup failed on Macs with certain default settings if connected
// to the Internet by an AT U-Verse 2-Wire Gateway.  This work-around
// may not be needed any more for cURL 7.21.7, but keep it to be safe.
curl_easy_setopt(curlEasy, CURLOPT_IPRESOLVE, CURL_IPRESOLVE_V4);
#endif

Now that there seems to be IPv6-only networks perhaps that workaround needs
to be reconsidered.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] [boinc_alpha] Time for version 7.8.1?

2017-08-12 Thread Juha Sointusalo
On 12 August 2017 at 00:50, David Anderson  wrote:

> I'm building a Win 7.8.1;
> I backported only the GUI RPC-related changes,
> because they fixed crashes that I personally saw.
>

The bug in boinc_file_exists() is regression since 7.6.33 and can cause bad
results (a task can end up using files from previous task).

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] Time for version 7.8.1?

2017-08-04 Thread Juha Sointusalo
On 4 August 2017 at 16:12, Oliver Bock <oliver.b...@aei.mpg.de> wrote:

> On 04/08/17 14:39 , Juha Sointusalo wrote:
> > I think there is one benefit from having a new, empty directory for
> > building release versions. You can be certain that the build will not
> > include files left over from previous development work.
>
> True, but that's why I recommended to actively manage your working tree
> which includes taking care of untracked files (see previous mail).
>

Oh but they are taken care of. They are ignored :/

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] Time for version 7.8.1?

2017-08-04 Thread Juha Sointusalo
On 4 August 2017 at 14:31, Oliver Bock  wrote:

> On 04/08/17 12:10 , Richard Haselgrove wrote:
> > The only reasons I can see for creating a new directory are:
> > To create clean build folders for the development tools to work in
>
> Yes, but even that is not necessary.


I think there is one benefit from having a new, empty directory for
building release versions. You can be certain that the build will not
include files left over from previous development work. BOINC's Unix build
system has a bug that allows one to, for example, compile a new version of
client and link it with an older version of libboinc. Been there, done that
and it took a while to figure out while the client is crashing in a place
where it possibly couldn't crash.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] Time for version 7.8.1?

2017-08-04 Thread Juha Sointusalo
On 4 August 2017 at 14:53, Laurence  wrote:

> However the corresponding link for 7.8.1 does not exist
>
> https://github.com/BOINC/boinc/archive/client_release/7.1/7.8.1.tar.gz
>
> I would need this link so that I can start the Fedora build and test
> process.
>

7.8.1 doesn't exist yet. We are only discussing if we should have 7.8.1 and
what should be in it.

If you are going to build Linux release packages should you be listed
in Software
maintenance roles ?

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] Time for version 7.8.1?

2017-08-03 Thread Juha Sointusalo
There's also the matter of Linux version which doesn't exists at the
moment. There's one user who compiled 7.8.0 himself and immediately found
two bugs in it.
http://boinc.berkeley.edu/dev/forum_thread.php?id=11719=79576
(Although the bugs existed in earlier releases too.)

Christian has some reservations against building a version that targets a
recent Ubuntu. But I think that until there is something better then one
that targets Ubuntu is better than nothing. If nothing else maybe it'll
send a signal to other distro users that it's time to start testing again.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] Time for version 7.8.1?

2017-08-03 Thread Juha Sointusalo
On 3 August 2017 at 23:17, Vitalii Koshura 
wrote:

> I guess it would be better to release without new version check because
> now I'm making some changes around this and I'm realising that it would be
> better to make this feature if a different way and this will require
> changes on both client and manager side. And this should be written and
> tested very carefully.
>

Do you think if it would be better to just revert the feature and retry it
for v8?

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] Time for version 7.8.1?

2017-08-03 Thread Juha Sointusalo
On 3 August 2017 at 22:35, Juha Sointusalo <juha.sointus...@gmail.com>
wrote:

> and another PR which I'll make soon
>

And that became #2008 "lib: fix boinc_file_exists() on Windows".

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] Time for version 7.8.1?

2017-08-03 Thread Juha Sointusalo
On 2 August 2017 at 05:11, Charlie Fenton  wrote:

> Are there any other changes in GIT master that should be ported into the
> 7.8 branch before we tag and build BOINC 7.8.1 and release it for alpha
> testing?


This command lists commits that are in master but not in 7.8 branch,
ignoring Drupal commits:

git cherry -v  origin/client_release/7/7.8  master  | grep -viE -e drupal
-e "^-"

Of the listed commits, these look like they could/should be included in 7.8:

de26ed56746c0af95afe99c00b798b6d5384e84c Increase the number of use cases
file_size() works correctly, per JuhaSointusalo.
ff7633a65def104b81a82b839f98fbe4b383f42f client: fix bug in URL-escaping
that fails for non-ASCII chars
6c0a92d1b1eafbb6560157762a5d3a68f750379c Manager: code formatting; no
functional change
8b06de2d28cc4f6a43c4f090d0a56bbc2635741c change comment; not functional
change
824b3e76543b834ae912d47e3f11e21d73bb0380 Manager: don't crash if GUI RPC
returns empty reply
3a96e95d02c97c20779bcb783cd3a5177fe8d96d GUI RPC client: use std::string
instead of fixed-size buffer for requests
a91f4c64088e805702e446516e2abb1faff9dfb2 LIB: Prevent the possible issue of
dereferencing a NULL pointer.
13fbb84d7347befa11a391bd9ef795cc03742d87 Manager: get rid of out_of_range
exception and handle such situation in a more graceful way.

I'll let Christian comment on this:

16a13e7e32379fdf016028dc0b5fd56668fed539 Travis: use Trusty image and use
apg-get to install dependencies

I included commits that only change formatting and such so that the
difference between master and 7.8 stays smaller and adding other commits is
perhaps easier.

Then there is this:

a0a6881818215e7f389417d57521af6537c1989d Manager: Use wxHTMLWindow in task
property window
86468699f0f6c3442dd8f9935e06b02d8bf034fd Manager: Fix typo

When Rom was release manager new features were developed in release branch
which is IMHO totally wrong and I'm more than happy if those days are over.
But right now we don't yet have a stable release. So is 7.8 open for new
features or not? (I'd also like the feature to be changed a bit. I'll write
a comment later.)

Of the changes not yet even in master I'd like #1979 "client/lib: don't
flush stdout and stderr in main loop" and another PR which I'll make soon
to be included. I can live without the others.


Should the new keyword stuff be included in the 7.8.1 builds?


IMHO, as long as it can't be tested it has no place in any release, whether
the release is beta or stable.



> Is anyone other than me still using VS 2010 for local Windows builds?
>

David uses VS2010. I may be wrong but I think at some point Rom tried using
VS2013 for building but the executables didn't run on XP and he went back
to VS2010.


> Opinions? Thoughts?
>

>From my perspective the only change is disabling the version check at
Manager startup. There's some Mac changes too but I don't know about those.
So what would we be testing with 7.8.1? IMHO, the remaining parts of the
version check don't work properly and need fixing. Should we give Vitalii
more time to fix it or do you want to release a new version just because it
doesn't crash on host startup?

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] [boinc_alpha] Disappearing BOINC Icon in System Tray (7.7.2) Requiring Manual Restart on Boot-Up

2017-07-04 Thread Juha Sointusalo
On 4 July 2017 at 19:33, Richard Haselgrove <r.haselgr...@btopenworld.com>
wrote:

> Yes, as just reported - but you need to be running a build later than .479
> for that to work.
>
>
> On Tuesday, 4 July 2017, 17:19, Juha Sointusalo <juha.sointus...@gmail.com>
> wrote:
>
> These days Windows hides notification icons rather aggressively.
>

Missed the part about Creators Update, still on Anniversary Update here.
Sorry.

I figured I'd go and test how the Manager behaves with Anniversary Update
and to my surprise it actually crashes.

I rebooted the computer and logged in. Manager is set to start
automatically, minimized to notification icon. At first the icon said
Connecting to client (or whatever the precise wording is) and I waited
until it said it was connected. I clicked the icon which promptly
disappeared. I verified with Task Manager that it was crash, no
boincmgr.exe anywhere. Crash log attached, good luck getting anything
useful out of it. To others: Manager's logs are in
C:\Users\you\AppData\Roaming\BOINC.

On related note. The client sometimes takes a very long time to start up,
20+ seconds. The following is with most of the logging options enabled:

04-Jul-2017 21:21:44 [---] Starting BOINC client version 7.8.0 for
windows_x86_64
...
04-Jul-2017 21:21:46 [---] [cpu_sched_debug] Request CPU reschedule: Prefs
update
04-Jul-2017 21:21:46 [---] [cpu_sched_debug] Request CPU reschedule: Startup
04-Jul-2017 21:21:46 [ATLAS@home] Task
YMzLDmXegrpnDDn7oo6G73TpABFKDmABFKDmIPMKDmABFKDmSd7sNm_0 is 142.90 days
overdue; you may not get credit for it.  Consider aborting it.
04-Jul-2017 21:21:46 [---] [gui_rpc] Local control only allowed
04-Jul-2017 21:21:46 [---] [gui_rpc] Listening on port 31416
04-Jul-2017 21:22:05 [---] [http] HTTP_OP::init_get():
http://boinc.berkeley.edu/project_list.php
04-Jul-2017 21:22:05 [---] [http] HTTP_OP::libcurl_exec(): ca-bundle
'C:\BOINC\ca-bundle.crt'
04-Jul-2017 21:22:05 [---] [http] HTTP_OP::libcurl_exec(): ca-bundle set
04-Jul-2017 21:22:05 [---] [proxy] HTTP_OP::no_proxy_for_url():
http://boinc.berkeley.edu/project_list.php
04-Jul-2017 21:22:05 [---] [proxy] returning false
...
04-Jul-2017 21:22:05 Initialization completed

(Ignore the Atlas task.)

There are really no messages between 21:21:46 and 21:22:05. I've seen this
multiple times but it is not reliably reproducible. This delay could be
what is triggering the Add project dialog in Manager.

-Juha
Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc005) at address 0x7FF61D15DFC6 write 
attempt to address 0x

Engaging BOINC Windows Runtime Debugger...






BOINC Windows Runtime Debugger Version 7.8.0


Dump Timestamp: 07/04/17 21:22:05
Loaded Library: dbghelp.dll
LoadLibraryA( symsrv.dll ): GetLastError = 126
LoadLibraryA( symsrv.dll ): GetLastError = 126
LoadLibraryA( srcsrv.dll ): GetLastError = 126
LoadLibraryA( srcsrv.dll ): GetLastError = 126
Loaded Library: version.dll
Debugger Engine   : 4.0.5.0
Symbol Search Path: C:\BOINC data;C:\BOINC;srv*C:\BOINC 
data\symbols*http://msdl.microsoft.com/download/symbols;srv*C:\BOINC 
data\symbols*http://boinc.berkeley.edu/symstore


ModLoad: 1d15 0089f000 C:\BOINC\boincmgr.exe (7.8.0.0) 
(-nosymbols- Symbols Loaded)
Linked PDB Filename   : 
C:\Users\David\Documents\BOINC_git\boinc_7.8\win_build\Build\x64\Release\boincmgr.pdb
File Version  : 7.8.0
Company Name  : Space Sciences Laboratory
Product Name  : BOINC client
Product Version   : 7.8.0

ModLoad: 16ec 001d1000 C:\WINDOWS\SYSTEM32\ntdll.dll 
(6.2.14393.479) (-exported- Symbols Loaded)
Linked PDB Filename   : ntdll.pdb
File Version  : 10.0.14393.206 (rs1_release.160915-0644)
Company Name  : Microsoft Corporation
Product Name  : Microsoft® Windows® Operating System
Product Version   : 10.0.14393.206

ModLoad: 1623 000ac000 C:\WINDOWS\System32\KERNEL32.DLL 
(6.2.14393.1198) (-exported- Symbols Loaded)
Linked PDB Filename   : kernel32.pdb
File Version  : 10.0.14393.206 (rs1_release.160915-0644)
Company Name  : Microsoft Corporation
Product Name  : Microsoft® Windows® Operating System
Product Version   : 10.0.14393.206

ModLoad: 13c3 0021d000 C:\WINDOWS\System32\KERNELBASE.dll 
(6.2.14393.1358) (-exported- Symbols Loaded)
Linked PDB Filename   : kernelbase.pdb
File Version  : 10.0.14393.206 (rs1_release.160915-0644)
Company Name  : Microsoft Corporation
Product Name  : Microsoft® Windows® Operating System
Product Version   : 10.0.14393.206

ModLoad: 1695 00165000 C:\WINDOWS\System32\USER32.dll 
(6.2.14393.576) (-exported- Symbols Loaded)
Linked PDB Filename   : user32.pdb
File Version  

Re: [boinc_dev] [boinc_alpha] Disappearing BOINC Icon in System Tray (7.7.2) Requiring Manual Restart on Boot-Up

2017-07-04 Thread Juha Sointusalo
On 4 July 2017 at 17:54, Richard Haselgrove 
wrote:

> I'm working through the same tests - currently downloading June '17
> cumulative security patch.
> But I'm seeing no BOINC Manager icon in the system tray - either with a
> previous homebuild, or with v7.8.0
> But BOINC *does run* after restart, as can be confirmed in Task Manager -
> all three components (BOINC.exe, BoincMgr, BoincTray) are running. But I
> haven't (yet) found a way of restoring the auto-start copy of BOINC Manager
> to the screen. The best I can do is to launch a second instance to control
> the beast. Still looking.
>

These days Windows hides notification icons rather aggressively. You can
tell if it's hidden by clicking the "up arrow" near the clock, the same
since, about, XP. If it's hidden you can unhide it by right clicking task
bar, selecting Settings and selecting Select which icons appear on the
taskbar in Notification area.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


[boinc_dev] boinc web: project list bugs

2017-07-03 Thread Juha Sointusalo
Hi

http://boinc.berkeley.edu/project_list.php crashes with HTTP 500.

http://boinc.berkeley.edu/projects.php

Platform details popup doesn't work. Seems like it needs the same change as
project details popup.

W3C validator reports Stray end tag ul, line 354.

The page loads two different popup Javascipt files.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] [BOINC/boinc] 341001: lib: remove safe_copy(); not used, generated compi...

2017-01-04 Thread Juha Sointusalo
On 4 January 2017 at 02:24, Artem Vorotnikov  wrote:

> For the record, strdup() is *not* standard, it is a GNU extension and
> not part of ANSI/ISO C.
>

It is in POSIX. MSVC knows it as _strdup() .

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] [BOINC/boinc] 341001: lib: remove safe_copy(); not used, generated compi...

2017-01-03 Thread Juha Sointusalo
On 3 January 2017 at 17:13, Christian Beer 
wrote:

> So the safe_copy()
> function serves two purposes. It copies a string into a new char array
> to make it modifiable and usable outside of the string context.
>

Putting aside the bigger issues for a moment. The next time you need a copy
of a C string just use strdup(). It's standard and everybody knows it
allocates memory that needs to be free()d.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] [boinc_projects] Bootstrap

2016-12-08 Thread Juha Sointusalo
On 8 December 2016 at 10:26, Jord van der Elst  wrote:

> This doesn't look good on my mobile browser, Dolphin.
>

Is it still bad or was it just a temporary glitch? I could understand that
the Post view would change but there isn't anything obviously wrong in the
main index page source. The only change there is width: 100%; but I don't
understand why the browser would now feel obligated to follow it when it
normally doesn't.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] [boinc_projects] Bootstrap

2016-12-07 Thread Juha Sointusalo
With all the layout and colour updates how about a fresh new set of icons?
Einstein is using symbols from Font Awesome. I think they look very nice.

The symbols Einstein is using are:

new posts - fa-star-o
sticky - fa-thumb-tack
locked - fa-lock

BOINC's forum code uses a few symbols Drupal stuff doesn't so here's a few
suggestions for them.

profile - fa-user or fa-user-o
donor - fa-star
red x - fa-times
rate plus - fa-plus or fa-thumbs-o-up
rate minus - fa-minus or fa-thumbs-o-down
hidden - fa-ban

There's no good match for the stock donor symbol crown. Maybe fa-diamond
would work. If fa-star-o for new posts looks too much like Seti's green
star fa-comment-o would work too.

Another font is Bootstrap Glyphicons. The CSS for it is bundled with the
theme CSS. So that would be less downloading and parsing. On the downside
that font has less symbols.

http://fontawesome.io/cheatsheet/
http://getbootstrap.com/components/

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] [boinc_projects] Bootstrap

2016-12-01 Thread Juha Sointusalo
On 11 November 2016 at 23:10, David Anderson  wrote:

> Please send me comments/feedback.
>

Ok, pre-formatted text stretching table cells and allowing other text to go
off-screen.

Tables that have pre-formatted text need to be fixed to 100% width:

width: 100%;
table-layout: fixed;

These tables are in Thread view, Post to thread, PM Inbox, Forum search
results, Posts by user and  Profile: user (the inner table). The theme used
in Seti website seems to have tables set to 100% width already but it
doesn't hurt to make sure the width stays that even if the theme is changed.

When table layout is fixed browser doesn't adjust column widths based on
their content any more. Instead the browser divides the available space
evenly across the columns unless the browser is told otherwise.

Thread view and Post to thread needs width: 8em; set for the author column,
PM Inbox needs width: 8em; set for subject and sender columns. The previous
style used width: 136px; but that is not exactly responsive to font size
changes. I chose 8em because it looks good on my screen.

Team search results and Team display are a bit harder. Both could use fixed
layout but I'm not sure what to do next. If I limit column widths in Team
search results the page looks bad on narrow displays; if I don't it looks
bad on wide displays. On Team display page the header that spans the entire
table seems to prevent setting width to columns. Anyway, I guess it's rare
enough to have very long lines in these two pages so they could probably be
left as they are now.

The theme used on Seti has black on light grey for  blocks which makes
large blocks of text to stand out quite a lot on dark theme. I think
monospace font would be enough and would use normal text colour for it.

You changed [code] BBcode element to render to  with white-space:
pre-wrap;. For some reason the previous style had made  a block level
element. Normally it's an inline element, that is, it can be used within
text like I have done throughout this message. I would like [code] to be
rendered to  with slight adjustment. To keep compatibility with
existing uses of [code],  needs white-space: pre-wrap; set. (There's
a small snag with using  for multiple lines; the first line is
slightly indented.) The colour used for  in Seti theme is... eh,
eye-catching, so same treatment as with .

Putting those two together:

code {
color: inherit;
background-color: inherit;
white-space: pre-wrap;
}

pre {
color: inherit;
background-color: inherit;
white-space: pre;
}

That leaves borders for theme designers to decide.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] [boinc_projects] Bootstrap

2016-11-28 Thread Juha Sointusalo
On 11 November 2016 at 23:10, David Anderson  wrote:

>
> Please send me comments/feedback.
>

Here's a few more:

- Buttons have various styles. If we decide Reply and Quote buttons to be
what all buttons should be then at least these have different style:

Sort (thread order) (larger font)
Preview and Post reply in Post to thread
Preview and OK in Edit post
Preview and Send Message in Send private message
Create/edit profile in Create a profile

I think some of the other buttons are different on purpose. There's small,
primary, default and dangerous buttons and maybe some more. I'm trusting
those are the way they should be.

- Edit post has "Forum" as title

- In thread view, avatar and Send message button touch each other

- And the above makes it easy to notice that avatar is a bit to the left of
the button. Maybe both of them could be centred with a small empty space
between them.

As for the colour scheme, here's a quick sketch on how to make it work:
First you or project admins pre-selects a few themes, adding custom
overrides to them if necessary.
Users select their theme from the pre-selected list.
In page_head you link to the CSS file corresponding to the user's
selection, or since themes seem to require fixing, link to a list of CSS
files.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] [boinc_projects] Bootstrap

2016-11-28 Thread Juha Sointusalo
On 28 November 2016 at 21:20, David Anderson  wrote:

> I noticed that, and was unable to fix it.
>
> The Bootstrap css (both the standard one and the dark one I'm using)
> indicate links by making them bold (no underline).
> I don't know why we're getting underlines.
>
> Can anyone figure this out?
>

Both Opera and Firefox shows a stack of styles and their source when you
inspect an element. Styles that are overridden by later ones are
crossed-out. The underlines come from

table a:not(.btn), .table a:not(.btn) {
text-decoration: underline;
}

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] [boinc_projects] Bootstrap

2016-11-27 Thread Juha Sointusalo
On 11 November 2016 at 23:10, David Anderson  wrote:

> I revised the BOINC web code (PHP) to use Bootstrap CSS
>
> Please send me comments/feedback.
>

Collected from forums:

- Font size of quoted text is larger than normal text. I see that you
adjusted it for Seti Main but it's still one notch larger.

- If author panel is taller than message panel the message and buttons are
kinda vertically centred or something. It would look better if message text
was top aligned and buttons bottom aligned.

- Task list's Application column has two rows even when there would enough
room to put it all in one row. (I'm not sure what prompted that request -
it doesn't look like you changed anything there.)

- Pre-formatted text appears to be always black on light grey. It doesn't
work too well on dark themes.

- Seti server status page links to custom.css and sah_logo_wb.png are
hardcoded to use HTTP even when the page itself is retrieved over HTTPS.

Also, links to RSS feed, Seti home page, BOINC addons page and BOINC home
use HTTP always. I'd rather have them use the same protocol that was used
for the status page.

Now realising that it's a static HTML page, maybe just use HTTPS everywhere.

- Two images in signature used to be side by side. Now they are one above
the other.

- Menus don't open on mouse hover. (I suppose whether they open by clicking
or hover is a matter of personal preference. I don't mind clicking.)

- Post to thread page is apparently not so responsive and on phones in
portrait mode the text box is pretty narrow.

- Top participants, Top teams, Team membership lists and some more (ask
Richard) have some column heading aligned differently from the actual data.

- Stats site icons and dark theme don't work well together, Free-DC icon is
barely visible.

- Post to thread text box is still black on white on dark themes.

- In private message preview the word "Preview" and the message are merged.

- Stock server status page (Seti Beta) doesn't render correctly at widths
~770 to ~990.

- Text wrapping and colours, which will get their own posts tomorrow.

Apart from the usual "Changes? Over my dead body!" you did get some
positive feedback too.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] Fwd: Re: 'client_state.xml' : GPU info for workunit/result

2016-11-27 Thread Juha Sointusalo
On 27 November 2016 at 17:20, Jean Philippe EIMER  wrote:

>
> I agree, I also noticed  has the info.
> But, the  info is not in  or .
>

You need to use app_name, app_version, platform and plan_class quadruplet
to identify an app version.

Workunit has app_name and app_version, result has platform, version_num and
plan_class and a reference to workunit.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] Bootstrap status

2016-11-26 Thread Juha Sointusalo
On 26 November 2016 at 00:05, David Anderson  wrote:

> I'm pretty much done with changing the BOINC web code to use Bootstrap.
>
> This is on Github in a branch called "bootstrap".
> Any objections to merging this into master?
>

I think it would be best to give people some time to find all the remaining
smaller issues. There seems to be more coming in every day. And I think
that even though they are smaller you should still address them before
merge. That way those projects that switch to Bootstrap will get to enjoy
bugless site right away.

You probably already know but just in case you don't, there are comments /
improvement requests in the Seti news thread and in BOINC's cafe thread.

http://setiathome.berkeley.edu/forum_thread.php?id=80569
http://boinc.berkeley.edu/dev/forum_thread.php?id=11137

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


[boinc_dev] Join button when logged in

2016-11-26 Thread Juha Sointusalo
I already have an account at Seti@home. In fact, I'm already logged in to
the web site.

When I go to their homepage there is a big Join Seti@home button. If I
click that button I'm taken to a page that at first gives instructions for
new volunteers. A tad silly.

I think it would be better if the Join button takes to the page with
instructions for existing volunteers when the volunteer is already logged
in. I suppose the word "Join" could in that case be something different but
I can't come up with anything better right now.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] 4th Gen BOINC credit system

2016-10-07 Thread Juha Sointusalo
On 15 August 2016 at 01:44, David Anderson  wrote:

> 2) We need a simulator that models credit calculations for various
> scenarios
> (synthetic, or based on trace data from a project).
> Such a simulator would help identify the problems with the current system,
> or would demonstrate that a new scheme works better.
>

Just came across a link to EmBOINC
 in Trac. From the
description it sounds like it could form a good basis for such simulator.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.