Re: [boinc_dev] Bug - BOINC 7.8.4 truncates CUDA driver version number

[David Anderson]

BOINC encodes the driver number into an integer in a way that assumes the minor 
number is < 100.


This is bad, of course - BOINC has no business encoding other peoples' version 
numbers -
but fixing it is not easy.
That's because the plan classes used by projects refer to
driver version numbers using these encoded integers.
If we change the representation of version it might break these projects.

Projects: do you in fact have plan classes that use nvidia driver version?

-- David

On 1/13/2018 8:31 PM, TarotApprentice wrote:

The CUDA device driver version number is being truncated.

Background: Nvidia released CUDA driver 384.111 (for Linux) to resolve one of the 
Spectre variants. The minor version number of 111 is being truncated to two digits 
(ie 11). The OpenCL detection seems to get it right though.


Event log:
14-01-2018 03:04 PM Starting BOINC client version 7.8.4 for x86_64-pc-linux-gnu
14-01-2018 03:04 PM log flags: file_xfer, sched_ops, task
14-01-2018 03:04 PM Libraries: libcurl/7.52.1 OpenSSL/1.0.2l zlib/1.2.8 
libidn2/0.16 libpsl/0.17.0 (+libidn2/0.16) libssh2/1.7.0 nghttp2/1.18.1 librtmp/2.3

14-01-2018 03:04 PM Data directory: /var/lib/boinc-client
14-01-2018 03:04 PM CUDA: NVIDIA GPU 0: GeForce GTX 1060 3GB (driver version 
384.11, CUDA version 9.0, compute capability 6.1, 3014MB, 2918MB available, 3936 
GFLOPS peak)
14-01-2018 03:04 PM OpenCL: NVIDIA GPU 0: GeForce GTX 1060 3GB (driver version 
384.111, device version OpenCL 1.2 CUDA, 3014MB, 2918MB available, 3936 GFLOPS peak)





___
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] Client Release 7.10

[David Anderson]

Laurence:
Yes.  Testing instructions are here:
https://boinc.berkeley.edu/trac/wiki/SimpleAttach#Whatprojectsmustdotousethisfeature
Currently it only works with Windows 64 bit clients
(I've build 7.9 only for that platform).

Let me know if problems/questions.

-- David

On 1/10/2018 10:03 AM, Laurence Field wrote:

The lhc@home server was upgraded in December. Can you test with that?

Send from Huawei SCL-L01

 Original Message 
Subject: Re: [boinc_dev] Client Release 7.10
From: David Anderson
To: boinc_dev@ssl.berkeley.edu
CC:

The main new feature is streamlined download/attach.
To fully test this we need a production project with latest server code.
SETI@home is close to having this.
We'll start testing 7.10 at that point.
-- David

On 1/10/2018 5:33 AM, Laurence wrote:
> Are there any plans to start the 7.10 client release?
>
> Cheers,
>
> Laurence
>
> ___
> 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.


___
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

[David Anderson]

On 1/11/2018 1:29 PM, Marius Millea wrote:


I was under the impression the server release is just a tag of a specific commit, 
so what's "included" is the whole source tree at that point, no?


Yes; the question is what part of the tree is "stable".
For example, in the client_release_xx branches,
only the client-side software is stable (i.e. tested);
the server software is just a random snapshot.



In the limited number of "releases 
" of 
boinc-server-docker that I've made to-date, I struggled with using semantic 
versioning (like 1.1.1) because it was always tough to know whether something was 
a backwards compatible change (if we're being honest, I think *alot* of server 
commits are technically backwards incompatible), and whether something was a 
bug-fix or true feature. Ultimately, it wasn't clear it really mattered or will 
matter for us, the real goal is just having a stable point. For that reason, I 
would recommend just doing something easy and clear like "calendar versioning" 
(https://calver.org/) with e.g. YY.MM.MINOR. Anyway, I don't feel extremely 
strongly about this, but thought I'd suggest it.



Most server software releases would involve changes to the DB structure
and would therefore be backward incompatible.

In the client, our convention is that test and release versions
have odd and even minor versions respectively.
This is handy for keeping things clear.



Our of curiosity, have we decided which git model we're using for the server 
releases, is it the same as for the client releases?



I had assumed so (this is described here, BTW:
https://boinc.berkeley.edu/trac/wiki/AdminReleaseManagement

-- David
___
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] server stable release issues

[David Anderson]

Issues involving potential "server stable" releases:

1)  What's included in the server release?
My recommendation: everything except the client,
i.e. web code, API, server code, scripts, wrappers.
The complete package of what a new project would need.

2) Should the client and server release cycles be independent?
I think so.
Although there are exceptions, changes generally involve only one or the other.
The points at which we want to branch and start testing will generally be 
different.

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.

Thoughts/comments?

-- David
___
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] Client Release 7.10

[David Anderson]

The main new feature is streamlined download/attach.
To fully test this we need a production project with latest server code.
SETI@home is close to having this.
We'll start testing 7.10 at that point.
-- David

On 1/10/2018 5:33 AM, Laurence wrote:

Are there any plans to start the 7.10 client release?

Cheers,

Laurence

___
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] New Vboxwrapper builds

[David Anderson]

What's the COM vs. non-COM tradeoff?  Why maintain both?

Also, which one does the VS project file build, and how to switch?

-- David

On 1/10/2018 6:25 AM, Laurence wrote:
Now that PR 1946  has been merged, 
please could we have new official builds of the VBox wrapper? This would require 
two builds for Windows (with and without the COM interfaces). Is the download 
folder  the official repository for these files? We 
can of course do the builds ourself and provide the binaries but are not sure if 
that is acceptable.


Cheers,

Laurence

___
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.

[boinc_dev] server release branch

[David Anderson]

I propose creating a server_release branch (from master)
that we can start testing using beta projects.
Any objections?
-- David
___
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] Rewriting BOINC Manager from scratch using Typescript

[David Anderson]

Keep in mind that there already is a "multiclient" GUI, namely BoincTasks.
It's excellent, but it's Win-only and is geared toward power users (lots of 
info).

I think that the top priorities is malleability:
being able to easily change the layout, add/remove features etc.
We currently have the simple and advanced views;
we may need even simpler and more advanced views.

My choice would be HTML + Javascript,
and I've experimented in this direction by making GUI RPCs work with HTTP.
However this failed because of cross-domain rules in browsers.

Laurence Field for CERN is trying something similar using "WebSockets":
https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API
... which don't have the cross-domain restriction.
I'd recommend communicating with him.

Java is also a possibility though it would be hard to make it malleable.
The Android GUI is written in Java, and there are some pieces (e.g. RPC stubs) that 
could be used.


-- David
___
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] Fwd: Build completed: boinc 1.0.129-umgiqxbh

[David Anderson]

AppVeyor shouldn't be configured to send emails to boinc_...@googlegroups.com


 Forwarded Message 
Subject:Build completed: boinc 1.0.129-umgiqxbh
Date:   Thu, 16 Nov 2017 11:58:47 +
From:   AppVeyor 
To: boinc_...@googlegroups.com



 Build boinc 1.0.129-umgiqxbh completed
 

Commit cd0db1476e  by Charlie 
Fenton  on 11/16/2017 11:48 AM:
Mac installer: correctly replace screensaver when installing an older version of 
BOINC to replace a newer version


Configure your notification preferences 

--
You received this message because you are subscribed to the Google Groups 
"boinc_pmc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 
boinc_pmc+unsubscr...@googlegroups.com .
To post to this group, send email to boinc_...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/boinc_pmc/20171116115846.35258.E8D09EB06924BA54%40appveyor.com 
.

For more options, visit https://groups.google.com/d/optout.
___
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] Fwd: Project app selection reset

[David Anderson]

The project could use a larger value for :
https://boinc.berkeley.edu/trac/wiki/ProjectOptions#Appversionselection

If the project sets  they'll see info in
the scheduler log that will clarify what's happening.

-- David

On 11/11/2017 2:03 PM, TarotApprentice wrote:


Since the message below I have found the below config_aux entry. I have asked the 
project admin what values he has set. Other users have suggested its taking 1024 
tasks before trying a different app. Other than this is there anything else the 
project admin can do so it tries the various apps more quickly?


MarkJ

X
In predicting which app version will be faster for a given host, multiply 
the
projected FLOPS by a uniform random variable with mean 1 and this standard
deviation (default 0.1).


Begin forwarded message:

*From:* TarotApprentice >

*Date:* 5 November 2017 at 5:08:27 pm AEDT
*To:* BOINC Alpha >

*Subject:* *Project app selection reset*

I have an issue with Asteroids where the project app selection doesn’t work 
properly. They have 3 period search apps for the CPU, being sse2, sse3 and avx. 
All my x64 machines support avx as the highest instruction set available from the 
project. I have 4 identical Ryzen 7 Machine, two of which have received and are 
running the avx app. One got the sse2 and another got the sse3 app. None of them 
have tried the other apps according to the application details for each host.


Its not limited to AMD, I also have 8 i7’s-6700’s again identical builds and its 
a similar story. Six got the avx app, one the sse2 and the other one got the sse3 
app. Again no history of trying the other apps to determine the one with the 
highest APR. For these two “slow app” machines I have detached them from the 
project and am waiting on their 90 days of no contact before I can delete the 
host before reattaching it in the hope a new host record will start with the avx app.


Is there any way to get it to try the other apps like its supposed to, or at 
least to reset the host app details? I have contacted the admin, Kyong but he 
isn’t aware of anything he can do. I have also seen other people on their message 
boards complaining of the same problem.


MarkJ


___
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] Linux Releases on BOINC Download Page ??

[David Anderson]

On 11/13/2017 10:53 AM, Art Masson wrote:

The links and recommended versions on the BOINC download site for Linux are 
very old.

Can links to the latest Linux released versions be added to the BOINC Download 
site at

https://boinc.berkeley.edu/download_all.php  ??


Because of the differences between Linux distros,
the recommended way of installing BOINC is using a package manager.

However, we should offer our own installer, at least for testing purposes.
In the past our policy has been to offer a self-extracting archive installer
for the latest Ubuntu distribution.
Instructions for building this are here:
https://boinc.berkeley.edu/trac/wiki/CompileClient

This hasn't been done since 7.4.22 (Sept. 2014) because no one has
volunteered for the role of "linux builder" as described here:
https://boinc.berkeley.edu/trac/wiki/AdminRoles

If someone would like to volunteer, let me know.

-- David
___
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.4 for Mac

[David Anderson]

i added a tag

On 11/10/2017 2:57 PM, Laurence Field wrote:

Hi Charlie,

I don't see a 7.8.4 tag in git.

Cheers,

Laurence


On 10/11/17 23:27, Charlie Fenton wrote:
I have built BOINC 7.8.4 for the Mac and uploaded it to 
. This fixes the calculation of GPU memory when 
running under OS 10.13 High Sierra.


Cheers,
--Charlie

___
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.


___
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

[David Anderson]

Rom,
Where does that version # (7.9.26197.0) come from?
-- D

On 11/5/2017 5:08 PM, Jacob Klein wrote:

David:
I tested this "Release 2" version of the 26200 wrapper. We're very close.

The good:
- The crashes starting LHC tasks on 5.2, and crashes resuming RNA World tasks on 
5.2, appear to be resolved. No more crashes. I suspect Release 1 had the stale tlb 
file.

The bad - *2* issues:
- The "File Version" of the exe is still incorrect, and is being written to 
stderr.txt. We need to fix this, so we can keep track of what version of the 
wrapper is being used at points in the log.

- The x86 version will need rebuilt too, with the fixes.

Once you get that "File Version" resolved, maybe consider doing another version 
bump to 26201, for reasons of sanity :) Then let me know when to retest it - I'm 
getting good at it.


Thanks,
Jacob


*From:* Jacob Klein <jacob_w_kl...@msn.com>
*Sent:* Sunday, November 5, 2017 5:37 PM
*To:* David Anderson; Juha Sointusalo
*Cc:* Rom Walton; BOINC Developers Mailing List; Boinc Projects; BOINC Alpha
*Subject:* RE: [boinc_dev] BOINC - October 2017 VirtualBox and VBoxWrapper 
updates

Thanks David, I don't suppose there's any chance you could test, too, to see if 
you can get any repro? Wishful thinking? :)


----
*From:* David Anderson <da...@ssl.berkeley.edu>
*Sent:* Sunday, November 5, 2017 4:53:53 PM
*To:* Juha Sointusalo; Jacob Klein
*Cc:* Rom Walton; BOINC Developers Mailing List; Boinc Projects; BOINC Alpha
*Subject:* Re: [boinc_dev] BOINC - October 2017 VirtualBox and VBoxWrapper 
updates
I rebuilt everything and uploaded it (same .zip filename).
The .exe size didn't change, but diff says it's different.
-- David

On 11/5/2017 12:09 PM, Juha Sointusalo wrote:
On 5 November 2017 at 11:14, Jacob Klein <jacob_w_kl...@msn.com 
<mailto:jacob_w_kl...@msn.com>> 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] BOINC - October 2017 VirtualBox and VBoxWrapper updates

[David Anderson]

I rebuilt everything and uploaded it (same .zip filename).
The .exe size didn't change, but diff says it's different.
-- David

On 11/5/2017 12:09 PM, Juha Sointusalo wrote:
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] BOINC - October 2017 VirtualBox and VBoxWrapper updates

[David Anderson]

I built new versions of vboxwrapper for Windows, which may work with VBox 5.2.0:
https://boinc.berkeley.edu/trac/wiki/VboxApps#Premadevboxwrapperexecutables
-- David

On 11/4/2017 10:49 AM, Juha Sointusalo wrote:
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.

[boinc_dev] translations out of date

[David Anderson]

Many of the translations
(e.g. the web-site translations in html/languages/*.po)
are out of date and I don't know how to update them.

The document for this:
https://boinc.berkeley.edu/trac/wiki/AdminLocalize
is very incomplete.
It should be a cookbook for someone in my position.

-- David
___
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] release 7.8.3?

[David Anderson]

https://boinc.berkeley.edu/trac/wiki/AdminTasks
and
https://boinc.berkeley.edu/trac/wiki/AdminAlphaTest

On 10/16/2017 2:16 AM, Laurence wrote:
Thanks,  I did not know about this. Is this documented anywhere? How are the 
results collected? I notice that there is an absence for the Linux operating 
system but as 3/4 of the resources are from Windows user, the Windows client is 
obviously more important.


Laurence



On 16/10/17 10:47, Jord van der Elst wrote:
Laurence, the test number comes from 
https://boinc.berkeley.edu/alpha/test_summary.php with no red reports at all: 
https://boinc.berkeley.edu/alpha/test_details.php?version=7.8.3


The only (major) problem still there is for the Spanish person, but I think 
that's either a missing character and thus easily fixed, or it requires a major 
Spanish translation of everything and that's then a slightly bigger problem. But 
this problem will continue until it's been fixed in Transifex and tested.



-- Jord van der Elst.

On Mon, Oct 16, 2017 at 10:17 AM, Laurence <laurence.fi...@cern.ch 
<mailto:laurence.fi...@cern.ch>> wrote:


    On 16/10/17 00:49, David Anderson wrote:

    7.8.3 has 90% test coverage and it looks good.

    Where does the 90% come from?

    Any objections to releasing it?

    A few issues need to be addressed before releasing on Linux. There
    is no reason why this should block the Windows and Mac releases
    though. We can skip 7.8.3 for Linux and release 7.8.4.

    Cheers,

    Laurence
    ___
    boinc_dev mailing list
    boinc_dev@ssl.berkeley.edu <mailto:boinc_dev@ssl.berkeley.edu>
    https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
<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.


___
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] release 7.8.3?

[David Anderson]

Our policy for a long time was:

- provide a .sea release (including manager) for current Ubuntu/x86,
  with no effort to make it run anywhere else.
- provide a client-only (no manager) release built on an old Linux system,
  everything static, for maximum compatibility.
  We have a "compatability VM" in which to build this.

At some point (maybe when Rom left) we stopped doing this.
I suggest that we start again.
Maybe change to 64 bit.

-- David


On 10/16/2017 7:46 AM, Steffen Möller wrote:

On 16.10.17 15:07, Laurence wrote:

Hi Jord,

On 16/10/17 12:24, Jord van der Elst wrote:

On Mon, Oct 16, 2017 at 12:06 PM, Richard Haselgrove
>
wrote:

     Berkeley has outsourced the distribution of Linux clients to the
     package maintainers for individual distributions, for several
     years now.


Laurence is the release manager for Linux, I suspect he knows about
all of that. :-)

No I didn't, so thanks.  Only stepped forward after the September
workshop.

But even if the distro package maintainers release these versions,
they also do so first for testing and can then still ask people to
report their results on the Alpha project. Their source code is still
coming from github as well.

Even if the package maintainers build and release, as you pointed out
the versioned upstream code still comes from the project. I have just
discovered that Gianfranco is doing daily builds (every 4h) and
creating packages for Debian from the git master. This is a nice step
towards CI.

And he also builds the complete packages together with the server side
components afterwards that go to the experimental section of Debian -
see the boinc-server-maker package
https://packages.qa.debian.org/b/boinc/news/20171005T094923Z.html.  It
would help a lot if the server bits in master are always be at a stage
that it could be released.

In my mind this goes as far as that for automated testing we could have
dummy project set up in an automated fashion and do few workunits on those.

Cheers,

Steffen

___
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.

[boinc_dev] release 7.8.3?

[David Anderson]

7.8.3 has 90% test coverage and it looks good.
Any objections to releasing it?
-- David
___
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] 7.8.3 client released for testing

[David Anderson]

The 7.8.3 client is now being tested.
This is a release candidate, so please test soon and thoroughly.

The changes since 7.8.2.:

- fixed bug where slot directories aren't cleaned out
- fixed possible buffer overflow when a task fails with
  lots of file transfer failures
- fixed bug involving repeated account manager requests every 10 sec

The Mac version includes changes that will enable the screensaver
to work with Mac OS 10.13.
This will require projects to rebuild their graphics apps.
I believe that SETI@home plans to do this in the next few days.

Thanks -- David
___
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] Bug lets manager connect to BAM! repeatedly.

[David Anderson]

That looks right; I'll use it.

On 10/2/2017 1:33 PM, Jord van der Elst wrote:

Isn't that https://github.com/BOINC/boinc/pull/2128 ??


-- Jord van der Elst.

On Mon, Oct 2, 2017 at 10:23 PM, David Anderson <da...@ssl.berkeley.edu 
<mailto:da...@ssl.berkeley.edu>> wrote:


Is this fixed in master?
Does anyone know what commit fixed it?
-- David


On 10/2/2017 2:15 AM, Willy wrote:

Hi,

A bug introduced in (I think) version 7.8.2 let's the manager ignore the
repeat_sec in the AMS response XML and it connects repeatedly without 
delay.

So far my server seems to be able to keep up but as more hosts upgrade 
to
7.8.2 or higher I may run into problems.

Since I pay for every byte transferred (even from my web server to the
database server) I would appreciate a speedy fix, as do users with a
metered internet connection I think.

Thanks,

Willy.
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu <mailto:boinc_dev@ssl.berkeley.edu>
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
<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 <mailto:boinc_dev@ssl.berkeley.edu>
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
<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] Bug lets manager connect to BAM! repeatedly.

[David Anderson]

Is this fixed in master?
Does anyone know what commit fixed it?
-- David

On 10/2/2017 2:15 AM, Willy wrote:

Hi,

A bug introduced in (I think) version 7.8.2 let's the manager ignore the
repeat_sec in the AMS response XML and it connects repeatedly without delay.

So far my server seems to be able to keep up but as more hosts upgrade to
7.8.2 or higher I may run into problems.

Since I pay for every byte transferred (even from my web server to the
database server) I would appreciate a speedy fix, as do users with a
metered internet connection I think.

Thanks,

Willy.
___
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_alpha] 7.8.2 released

[David Anderson]

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 
<mailto: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
<mailto: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
<mailto: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
<mailto: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
<https://boinc.berkeley.edu/alpha/test_form.php>
>>>
>>> Thanks --
>>>
>>> David
>>> ___
>>> boinc_alpha mailing list
>>> boinc_al...@ssl.berkeley.edu <mailto:boinc_al...@ssl.berkeley.edu>
>>> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
<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 <mailto:boinc_al...@ssl.berkeley.edu>
>> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
<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 <mailto:boinc_al...@ssl.berkeley.edu>
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
<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 <mailto:boinc_al...@ssl.berkeley.edu>
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
<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 client link broken at main download page

[David Anderson]

Oops!  Fixed now - thanks.
-- David

On 9/28/2017 7:45 AM, Vidal, Patricio J wrote:

Hi,

The client download link at https://boinc.berkeley.edu/download.php is broken. 
It is pointing to https://boinc.berkeley.edu/boinc_7.8.2_windows_x86_64.exe but 
it should be https://boinc.berkeley.edu/dl/boinc_7.8.2_windows_x86_64.exe 
according to https://boinc.berkeley.edu/download_all.php

Regards,
Patricio.
Please be advised that this email may contain confidential information. If you 
are not the intended recipient, please notify us by email by replying to the 
sender and delete this message. The sender disclaims that the content of this 
email constitutes an offer to enter into, or the acceptance of, any agreement; 
provided that the foregoing does not invalidate the binding effect of any 
digital or other electronic reproduction of a manual signature that is included 
in any attachment.
___
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.

[boinc_dev] 7.10 release

[David Anderson]

It's clear that we need to start testing for a 7.10 release soon.
I'll go ahead and make a client_release/7/7.10 branch
unless anyone has an important PR planned.
-- David
___
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] 7.10 client release

[David Anderson]

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?

Thanks -- David
___
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] AMD's CAL

[David Anderson]

If no projects have CAL apps, I don't see any reason to keep the CAL
device enumeration code.  Anyone else?
-- D

On 8/21/2017 7:01 PM, Darrell Holz wrote:

From the client_state xml file:


   1
   Radeon (TM) RX 480 Graphics
8589934592.00
   0
   1
   59904.00
   
   0
   8192
   0
   0
   1300
   0
   0
   0
   0
   0
   0
   0
   0
   0
   
  Radeon (TM) RX 480 Graphics
  Advanced Micro Devices, Inc.
  4098
  1
  0
  190
  63
  1
1
  cl_khr_fp64 cl_amd_fp64 cl_khr_global_int32_base_atomics 
cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics 
cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics 
cl_khr_int64_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store 
cl_khr_fp16 cl_khr_gl_sharing cl_khr_gl_depth_images cl_amd_device_attribute_query 
cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt 
cl_khr_d3d10_sharing cl_khr_d3d11_sharing cl_khr_dx9_media_sharing 
cl_khr_image2d_from_buffer cl_khr_spir cl_khr_subgroups cl_khr_gl_event 
cl_khr_depth_images cl_khr_mipmap_image cl_khr_mipmap_image_writes 
cl_amd_liquid_flash

8589934592
  32768
1300
  36
0
0
4
  16
1
  OpenCL 2.0 AMD-APP 
(2442.8)
  OpenCL 2.0 AMD-APP (2442.8)
2442.8
   


Correct me if I am wrong, but the first section would be populated with values if 
the CAL detection code was working properly. Even when the ATI library was found, 
the values were not reported because Boinc I believe was not enumerating the CAL 
targets correctly. In the Opencl section notice that the number of SIMD units is 
correctly reported, but for some reason Boinc is detecting an error returned by 
the driver. Don't know if it is a problem in our code or in AMD's.



-Original Message-
From: David Anderson <da...@ssl.berkeley.edu>
To: boinc_dev <boinc_dev@ssl.berkeley.edu>
Sent: Mon, Aug 21, 2017 8:07 pm
Subject: Re: [boinc_dev] AMD's CAL

What GPU info does the CAL function provide that OpenCL doesn't?
-- David

On 8/21/2017 2:39 PM, Darrell Holz wrote:
> I am moving this response over from the Boinc Alpha list about the 7.8.1 
startup, because the discussion is more appropriate here. Yes AMD has publically 
switched from CAL to OpenCl a few years back, but the CAL files are still apart of 
the driver. Even the new RX Vega drivers still has the files included in them. The 
question is what are they using them for? I don't believe it is to maintain 
backwards compatibility, because AMD is very quick at cutting off support for 
anything they consider legacy. I thought that maybe they were using them as some 
sort of low level access to the GPU for Opencl, and to test this I renamed the 
files and restarted Boinc. Low and behold, Opencl has been and is working 
correctly for over 24 hours now with out the files, so again why are they still 
apart of the driver and what are they using them for? Here is a link to a project 
on Github for a AMD GPU assembler and disassembler that uses the CAL and the 
modifications to get it working on an RX4

80
>
> :
>
> 
[url]https://github.com/zawawawa/CLRX-mirror/commit/05ed08a1cbf1af589a22e329b755592df4b6b61e[/url]

>
> I think that the problem in the Boinc detection of CAL is that it does not 
properly enumerate all of the possible CAL targets.

>
> Even if Boinc gets the enumeration correct, about the only good thing that the 
CAL provides now is more information about the capabilities of the GPU. And since 
no projects that have tasks that run on an AMD GPU that still use a CAL program, 
the time it might take to get it working correctly might not be worth it for just 
the increase in info. So in fact it might be better to just remove the CAL 
detection completely from Boinc reducing its size and startup time.

>
> Log from last restart:
>
> 20-Aug-2017 09:44:08 [---] Starting BOINC client version 7.8.1 for 
windows_x86_64
> 20-Aug-2017 09:44:19 [---] log flags: file_xfer, sched_ops, task, coproc_debug, 
cpu_sched, cpu_sched_debug
> 20-Aug-2017 09:44:19 [---] log flags: cpu_sched_status, idle_detection_debug, 
scrsave_debug, task_debug

> 20-Aug-2017 09:44:19 [---] log flags: unparsed_xml, work_fetch_debug
> 20-Aug-2017 09:44:19 [---] Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8
> 20-Aug-2017 09:44:19 [---] Data directory: C:\ProgramData\BOINC
> 20-Aug-2017 09:44:19 [---] Running under account Darrell
> 20-Aug-2017 09:44:22 [---] [coproc] launching child process at C:\Program 
Files\BOINC\boinc.exe

> 20-Aug-2017 09:44:22 [---] [coproc] relative to directory C:\ProgramData\BOINC
> 20-Aug-2017 09:44:22 [---] [coproc] with data directory "C:\ProgramData\BOINC"
> 20-Aug-2017 09:44:22 [---] OpenCL: AMD/ATI GPU 0: Radeon (TM) RX 480 Graphics 
(driver version 2348.4, device version OpenCL 2.0 AMD-APP (2348.4), 8192MB, 8192MB 
available, 5990 GFLOPS peak)

> 20-Aug-2017 09:44:22 [---] [co

Re: [boinc_dev] AMD's CAL

[David Anderson]

What GPU info does the CAL function provide that OpenCL doesn't?
-- David

On 8/21/2017 2:39 PM, Darrell Holz wrote:

I am moving this response over from the Boinc Alpha list about the 7.8.1 
startup, because the discussion is more appropriate here. Yes AMD has 
publically switched from CAL to OpenCl a few years back, but the CAL files are 
still apart of the driver. Even the new RX Vega drivers still has the files 
included in them. The question is what are they using them for? I don't believe 
it is to maintain backwards compatibility, because AMD is very quick at cutting 
off support for anything they consider legacy. I thought that maybe they were 
using them as some sort of low level access to the GPU for Opencl, and to test 
this I renamed the files and restarted Boinc. Low and behold, Opencl has been 
and is working correctly for over 24 hours now with out the files, so again why 
are they still apart of the driver and what are they using them for? Here is a 
link to a project on Github for a AMD GPU assembler and disassembler that uses 
the CAL and the modifications to get it working on an RX4

80
  
  :


[url]https://github.com/zawawawa/CLRX-mirror/commit/05ed08a1cbf1af589a22e329b755592df4b6b61e[/url]

I think that the problem in the Boinc detection of CAL is that it does not 
properly enumerate all of the possible CAL targets.

Even if Boinc gets the enumeration correct, about the only good thing that the 
CAL provides now is more information about the capabilities of the GPU. And 
since no projects that have tasks that run on an AMD GPU that still use a CAL 
program, the time it might take to get it working correctly might not be worth 
it for just the increase in info. So in fact it might be better to just remove 
the CAL detection completely from Boinc reducing its size and startup time.

Log from last restart:

20-Aug-2017 09:44:08 [---] Starting BOINC client version 7.8.1 for 
windows_x86_64
20-Aug-2017 09:44:19 [---] log flags: file_xfer, sched_ops, task, coproc_debug, 
cpu_sched, cpu_sched_debug
20-Aug-2017 09:44:19 [---] log flags: cpu_sched_status, idle_detection_debug, 
scrsave_debug, task_debug
20-Aug-2017 09:44:19 [---] log flags: unparsed_xml, work_fetch_debug
20-Aug-2017 09:44:19 [---] Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8
20-Aug-2017 09:44:19 [---] Data directory: C:\ProgramData\BOINC
20-Aug-2017 09:44:19 [---] Running under account Darrell
20-Aug-2017 09:44:22 [---] [coproc] launching child process at C:\Program 
Files\BOINC\boinc.exe
20-Aug-2017 09:44:22 [---] [coproc] relative to directory C:\ProgramData\BOINC
20-Aug-2017 09:44:22 [---] [coproc] with data directory "C:\ProgramData\BOINC"
20-Aug-2017 09:44:22 [---] OpenCL: AMD/ATI GPU 0: Radeon (TM) RX 480 Graphics 
(driver version 2348.4, device version OpenCL 2.0 AMD-APP (2348.4), 8192MB, 
8192MB available, 5990 GFLOPS peak)
20-Aug-2017 09:44:22 [---] [coproc] No NVIDIA library found
20-Aug-2017 09:44:22 [---] [coproc] No ATI library found.
20-Aug-2017 09:44:22 [---] [coproc] clGetDeviceInfo failed to get 
CL_DEVICE_SIMD_PER_COMPUTE_UNIT_AMD for device 0
20-Aug-2017 09:44:22 [---] Host name: darrell-II
20-Aug-2017 09:44:22 [---] Processor: 6 AuthenticAMD AMD Phenom(tm) II X6 1100T 
Processor [Family 16 Model 10 Stepping 0]
20-Aug-2017 09:44:22 [---] Processor features: fpu vme de pse tsc msr pae mce 
cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 htt pni cx16 
popcnt syscall nx lm svm sse4a osvw ibs skinit wdt page1gb rdtscp 3dnowext 3dnow
20-Aug-2017 09:44:22 [---] OS: Microsoft Windows 7: Professional x64 Edition, 
Service Pack 1, (06.01.7601.00)
20-Aug-2017 09:44:22 [---] Memory: 8.00 GB physical, 16.00 GB virtual
20-Aug-2017 09:44:22 [---] Disk: 931.41 GB total, 461.93 GB free
20-Aug-2017 09:44:22 [---] Local time is UTC -5 hours
20-Aug-2017 09:44:22 [---] VirtualBox version: 5.1.26
20-Aug-2017 09:44:22 [BURP] Found app_config.xml
20-Aug-2017 09:44:22 [Collatz Conjecture] Found app_config.xml
20-Aug-2017 09:44:22 [Cosmology@Home] Found app_config.xml
20-Aug-2017 09:44:22 [Einstein@Home] Found app_config.xml
20-Aug-2017 09:44:22 [Enigma@Home] Found app_config.xml
20-Aug-2017 09:44:22 [LHC@home] Found app_config.xml
20-Aug-2017 09:44:22 [Milkyway@Home] Found app_config.xml
20-Aug-2017 09:44:22 [Moo! Wrapper] Found app_config.xml
20-Aug-2017 09:44:22 [PrimeGrid] Found app_config.xml
20-Aug-2017 09:44:22 [SETI@home] Found app_config.xml
20-Aug-2017 09:44:22 [SETI@home Beta Test] Found app_config.xml
20-Aug-2017 09:44:22 [XANSONS for COD] Found app_config.xml
20-Aug-2017 09:44:22 [---] Config: event log limit 4000 lines
20-Aug-2017 09:44:22 [---] Config: report completed tasks immediately
20-Aug-2017 09:44:22 [---] Config: use all coprocessors
20-Aug-2017 09:44:23 [Asteroids@home] URL http://asteroidsathome.net/boinc/; 
Computer ID 9594; resource share 100
20-Aug-2017 09:44:23 [BURP] URL http://burp.renderfarming.net/; Computer ID 
50245; resource share 120
20-Aug-2017 09:44:23 

Re: [boinc_dev] boinc unsafe symlink in doc/sym_web.php

[David Anderson]

Done.
-- D

On 8/21/2017 2:17 AM, Gianfranco Costamagna wrote:

Hello, can anybody please fix this unsafe and wrong symlink in boinc source 
tree?
ls -l doc/sim_web.php
doc/sim_web.php -> /home/boincadm/boinc/doc/sim/sim_web.php


https://github.com/BOINC/boinc/blob/master/doc/sim_web.php

thanks

G.
___
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] User web notice

[David Anderson]

Fixed.
-- D

On 8/20/2017 2:09 PM, Richard Haselgrove wrote:

Reported and confirmed at SETI:

Notice: Undefined property: BoincWorkunit::$keywords in 
/disks/carolyn/b/home/boincadm/projects/sah/html/user/workunit.php on line 53
___
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.

[boinc_dev] Fwd: Re: [BOINC/boinc] project preference to set number of used cpu's (#1414)

[David Anderson]

There have been many cases where the BOINC client caused a problem,
such as running too many VMs and bogging down the system.
Volunteers then ask for a preference that lets them manually fix the problem.

In such cases it's better to figure out the root cause of the original problem
(e.g. that VM memory usage isn't being accounted correctly)
and change BOINC so it doesn't happen.
BOINC should compute invisibly without fiddling with preferences.

Also, job scheduling and work fetch are intertwined.
The work fetch algorithm does a simulation of job scheduling
in deciding how much work to request for the various resources (CPU, GPU).
Changes to the job scheduling policy (e.g. by new prefs)
typically lead to problems with work fetch (e.g. starved resources).

-- D


 Forwarded Message 
Subject:Re: [BOINC/boinc] project preference to set number of used 
cpu's (#1414)
Date:   Thu, 17 Aug 2017 21:43:57 + (UTC)
From:   Jord 
Reply-To: 	BOINC/boinc 
 


To: BOINC/boinc 
CC: Subscribed 



Is this still being asked for?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub 
, or mute the 
thread 
.


___
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.8.0 or 7.8.1 ??

[David Anderson]

?? download_all.php shows 7.8.1, not 7.8.0
-- David

On 8/14/2017 8:46 AM, Art Masson wrote:

Hi all,

A few days ago, I downloaded 7.8.1 for Windows and Mac OS for testing on my 
machines, but now I've noticed that 7.8.1 is no longer listed on the public 
download site ... and we are back to 7.8.0.   Has 7.8.1 been removed from the 
public site due to problems?  Should we still be testing the 7.8.1 version or 
revert back to 7.8.0?


Public Download Site -- Which now shows 7.8.0 only now:
https://boinc.berkeley.edu/download_all.php

Download Site which still has 7.8.1 versions:
https://boinc.berkeley.edu/dl/



___
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_wg] Re: [boinc_alpha] Time for version 7.8.1?

[David Anderson]

Because as of now I'm the release manager for the client:
https://boinc.berkeley.edu/trac/wiki/AdminRoles

I've solicited volunteers to fill this role but no one has offered.

-- David

On 8/12/2017 3:18 PM, Richard Haselgrove wrote:

I thought BOINC was under community development now.

Why is this "your" release plan?


On Saturday, 12 August 2017, 23:14, David Anderson <da...@ssl.berkeley.edu> 
wrote:


My release plan is:
- test and release 7.8
- test and release 7.10, which will include keyword features and other recent 
fixes.
Ideally each of these should take about 2 weeks.

Anything else we should try to put in 7.10?

-- David

On 8/12/2017 2:36 PM, Vitalii Koshura wrote:
> Hello all,
>
>
>> Further, "Run daemon?"... is it wise to put it like that? Does the general
>> public know what a daemon is?
> I see the fundamental problem here: we have a lot of open issues but they
> are not reviewed and clarified. If I'll take a look at the issue with 'Run
> daemon' enhancement request I'll see just the request with this parameter
> name. And nothing more. No one owner left a comment with a better name. And
> also there was no questions about the name when this pull request was
> merged. It's not a problem to change the title, it will take 5 minutes to
> do this. The problem is that issues are not really reviewed and no release
> plans are made (I'm aware about the releases on GitHub but they are too
> abstract and do not contain real plans for release). I think this should be
> changed also.
>
> Thanks
>
> Best regards,
> Vitalii Koshura
>
> 2017-08-12 14:30 GMT+03:00 Jord van der Elst <els...@gmail.com 
<mailto:els...@gmail.com>>:

>
>> I have a couple of niggles about the Options->More Options... menu, and
>> then in particular the mouse-overs. In this menu the mouse-over text only
>> works when mousing over the input boxes. Everywhere else in BOINC Manager's
>> menus the mouse-over works over the text as well.
>>
>> Further, "Run daemon?"... is it wise to put it like that? Does the general
>> public know what a daemon is?
>> For us translators, it's even more difficult. Should we just use the word
>> 'daemon' if it also exists in our language, or immediately describe what it
>> means, like "background running program"?
>>
>>
>> -- Jord van der Elst.
>> ___
>> boinc_alpha mailing list
>> boinc_al...@ssl.berkeley.edu <mailto: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 <mailto: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 <mailto: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] Time for version 7.8.1?

[David Anderson]

My release plan is:
- test and release 7.8
- test and release 7.10, which will include keyword features and other recent 
fixes.
Ideally each of these should take about 2 weeks.

Anything else we should try to put in 7.10?

-- David

On 8/12/2017 2:36 PM, Vitalii Koshura wrote:

Hello all,



Further, "Run daemon?"... is it wise to put it like that? Does the general
public know what a daemon is?

I see the fundamental problem here: we have a lot of open issues but they
are not reviewed and clarified. If I'll take a look at the issue with 'Run
daemon' enhancement request I'll see just the request with this parameter
name. And nothing more. No one owner left a comment with a better name. And
also there was no questions about the name when this pull request was
merged. It's not a problem to change the title, it will take 5 minutes to
do this. The problem is that issues are not really reviewed and no release
plans are made (I'm aware about the releases on GitHub but they are too
abstract and do not contain real plans for release). I think this should be
changed also.

Thanks

Best regards,
Vitalii Koshura

2017-08-12 14:30 GMT+03:00 Jord van der Elst :


I have a couple of niggles about the Options->More Options... menu, and
then in particular the mouse-overs. In this menu the mouse-over text only
works when mousing over the input boxes. Everywhere else in BOINC Manager's
menus the mouse-over works over the text as well.

Further, "Run daemon?"... is it wise to put it like that? Does the general
public know what a daemon is?
For us translators, it's even more difficult. Should we just use the word
'daemon' if it also exists in our language, or immediately describe what it
means, like "background running program"?


-- Jord van der Elst.
___
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] Time for version 7.8.1?

[David Anderson]

I just added a PR for this.
I used "Run the client when launching the Manager?"
(we should use "the" either in both or in neither).

-- David

On 8/12/2017 3:02 PM, Vitalii Koshura wrote:

Hello David,

What label should be?
'Run client?' with the tooltip 'Run client when launching the Manager?'?
I'll fix this fast.

Thanks

Best regards,
Vitalii Koshura

2017-08-13 0:58 GMT+03:00 David Anderson <da...@ssl.berkeley.edu 
<mailto:da...@ssl.berkeley.edu>>:


Good point.
The GUI should never use "daemon".

The goal is to conceal the fact that there are two programs.
We use "BOINC Manager" to refer to both.
Where we need to refer to the client, we call it "client".

-- David


On 8/12/2017 4:30 AM, Jord van der Elst wrote:

I have a couple of niggles about the Options->More Options... menu, and
then in particular the mouse-overs. In this menu the mouse-over text 
only
works when mousing over the input boxes. Everywhere else in BOINC 
Manager's
menus the mouse-over works over the text as well.

Further, "Run daemon?"... is it wise to put it like that? Does the 
general
public know what a daemon is?
For us translators, it's even more difficult. Should we just use the 
word
'daemon' if it also exists in our language, or immediately describe 
what it
means, like "background running program"?


-- Jord van der Elst.
___
boinc_alpha mailing list
boinc_al...@ssl.berkeley.edu <mailto:boinc_al...@ssl.berkeley.edu>
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
<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 <mailto:boinc_al...@ssl.berkeley.edu>
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
<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] Time for version 7.8.1?

[David Anderson]

Good point.
The GUI should never use "daemon".

The goal is to conceal the fact that there are two programs.
We use "BOINC Manager" to refer to both.
Where we need to refer to the client, we call it "client".

-- David

On 8/12/2017 4:30 AM, Jord van der Elst wrote:

I have a couple of niggles about the Options->More Options... menu, and
then in particular the mouse-overs. In this menu the mouse-over text only
works when mousing over the input boxes. Everywhere else in BOINC Manager's
menus the mouse-over works over the text as well.

Further, "Run daemon?"... is it wise to put it like that? Does the general
public know what a daemon is?
For us translators, it's even more difficult. Should we just use the word
'daemon' if it also exists in our language, or immediately describe what it
means, like "background running program"?


-- Jord van der Elst.
___
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] Time for version 7.8.1?

[David Anderson]

Great.  I'll use 5.1.26.

On 8/11/2017 3:19 PM, Jacob Klein wrote:


VirtualBox 5.1.24 will be, at this point in time, the bare minimum necessary to 
work correctly on the upcoming Windows 10 Version 1709 release (Fall Creator's 
Update - September 2017). This is because of Microsoft's changes, with the 
VirtualBox breakage detailed here, with the solution version mentioned midway 
through the thread:

https://forums.virtualbox.org/viewtopic.php?f=38=83732


As you suggest, I recommend including ***VirtualBox 5.1.26***, which includes 
additional fixes, including 5.1.24 regression fixes.. and has been out for a few 
weeks with no major problems reported.



For your reference, there is a VirtualBox 5.2 Beta 1 version. I'm sure it's quite 
buggy. I haven't played with it yet.



Regards,

Jacob




*From:* boinc_alpha <boinc_alpha-boun...@ssl.berkeley.edu> on behalf of David 
Anderson <da...@ssl.berkeley.edu>

*Sent:* Friday, August 11, 2017 5:54 PM
*To:* Juha Sointusalo; Charlie Fenton
*Cc:* boinc_dev email List; boinc_alpha email list
*Subject:* Re: [boinc_alpha] [boinc_dev] Time for version 7.8.1?
From looking at the VirtualBox change log,
it looks like 5.1.26 has a lot of bug fixes relative to 5.1.22.
I'll use it unless I hear otherwise.

-- 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_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?

[David Anderson]

From looking at the VirtualBox change log,
it looks like 5.1.26 has a lot of bug fixes relative to 5.1.22.
I'll use it unless I hear otherwise.

-- David
___
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?

[David Anderson]

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

In the meantime, VirtualBox has moved from 5.1.22 to 5.1.26.
Is there any reason to use the newer version?

-- David

On 8/3/2017 12:35 PM, Juha Sointusalo wrote:

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.


___
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] Software development and branches, was Re: [boinc_projects] keywords

[David Anderson]

Please read
https://boinc.berkeley.edu/trac/wiki/SoftwareTesting
-- David

On 8/7/2017 10:28 PM, Bernd Machenschalk wrote:

On 07.08.17 21:40, David Anderson wrote:

I've proposed creating server release branches,
similar to the exiting client release branches.
Hopefully this will satisfy everyone's needs.


What I (and others) need is a "stable" branch (whatever named) I can
- branch off my own development to work without being affected by others
- compare and test my changes against, which requires that the original branch is 
"stable"
- merge my development (branch) into when I'm done and I and others are convinced 
that my development does what it should and doesn't destabilize the branch.


I don't see how server release branches would do that.

Bernd



___
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] Software development and branches, was Re: [boinc_projects] keywords

[David Anderson]

On 8/7/2017 5:20 PM, Steffen Möller wrote:

No. It won't it is very much off the problem. Offer
separate repositories ( as in github.com/BOINC/client
and github.com/BOINC/server, not branches, and you
make people happier. Of course the two repositories
have zero code redundancy.

Perhaps you haven't seen /lib.
___
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] Software development and branches, was Re: [boinc_projects] keywords

[David Anderson]

Please read https://boinc.berkeley.edu/trac/wiki/SoftwareTesting
-- David

On 8/4/2017 3:38 PM, Laurence Field wrote:

Hi David,

On 04/08/17 23:17, David Anderson wrote:


It's simple:

1) fork master, e.g. to client_release_xxx.  It's not stable at this point.
2) test client_release_xxx (e.g. using Alpha testers) fix bugs, repeat.  Now it's 
stable.

3) only backport bug fixes to client_release_xxx.  It remains stable.
You can also build and test from master, fix the issues then make the release. A 
branch can then be created but would only be updated to include major issues and 
not any new features. Once the master is 'stable' it should in theory never break 
again as changes in the PRs should have already been tested. If we are able to 
have nightly builds with automated tests, this should speed up the process on the 
long term.


We've always used this approach for the client, and it's worked perfectly.
That does not mean it is necessary it is the best method. This kind of 
argumentation is not Computer Science.

We can use the same approach for server if we create
a distributed testing system based on Beta projects (analogous to the client 
Alpha test)
Having a versioned release of the server would be helpful. I hope that we can have 
working server packages for Debian and CentOS soon. I don't think we need to 
target any other platform but please let me know if there are others.


Cheers,

Laurence
___
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] Software development and branches, was Re: [boinc_projects] keywords

[David Anderson]

Steffen:
I agree - git is here to serve us, not vice versa :-)

I've proposed creating server release branches,
similar to the exiting client release branches.
Hopefully this will satisfy everyone's needs.

-- David

On 8/7/2017 7:21 AM, Steffen Möller wrote:

Well, git makes one's "senses reeling", at least when one has started a
career with CVS. Linus had helped us escape, and he possibly gets more
respect from me for that than for his kernel work. For me, it was the
git repository for BOINC _packaging_ that had forced me into it, long
before BOINC transitioned to git. I am still thankful for it.

So, please find a way to stop this so very outdated discussion. When you
get together now, just vote for the individual or set of individuals who
shall be in charge of what is the new_master branch from which releases
are to be branched off.  And you can have the same or other sets of
individuals in charge of any of these 7.8.x or 7.10.x branches. And you
can have individuals in charge for various features of BOINC. Heck, the
git-creator-Linus' Linux kernel just gives a very nice model of how it
can be done once it gets any complicated, just, BOINC is comparatively
simple. No need to outsmart them.

Best,

Steffen


On 07.08.17 12:20, Jord van der Elst wrote:


Thanks for that last paragraph, Oliver. You put into words what has been
running through my mind since Friday.


-- Jord van der Elst.

On Mon, Aug 7, 2017 at 9:55 AM, Oliver Bock <oliver.b...@aei.mpg.de> wrote:


On 06/08/17 22:40 , David Anderson wrote:

Testing a feature in isolation is not the same as testing the system.

True.


No one is advocating committing untested or buggy code into master.

Yet it happens most of the time, mostly because *development* happens in
master. And even if one sees a seldom feature branch for development
it's more often than not merged to master after incomplete feature
testing (e.g. not even a full build on all platforms). In any case
master is broken.


However, feature testing doesn't mean that master is stable.

Right, but it should be as stable as possible which requires a
continuous improvement effort. Why is it broken and what can you do to
actively avoid it next time?


For that, we need to do system-level testing in a separate release

branch.

You're right that system-level (a.k.a. integration) testing should take
place in a *specific* branch. However that branch should be master in
our opinion. As Laurence pointed out: release branches are to stabilize
and fix releases.

I agree with Bernd: can it be that your resistance to use master for
integration just stems from the fact that you don't like developing in
feature branches because you're still used to CVS or SVN, and in your
mind branching and merging still is a pain?


This is what we've done for years with the client software.

Thing is, it's probably time to reconsider your view on BOINC. That "we"
means 2-3 developers running their "own" project. BOINC is different
now, at least it officially wants to be. You said BOINC is now a
community project. If you really mean it, then please listen to the
community. From what I can tell, the community is in agreement on how
things should be done nowadays. Why are you opposing *all* of us? Also,
you haven't yet given any concrete arguments/reasons why the model we
propose *really* wouldn't work. So far, you stated personal
impressions/facts that were often misinformed or in fact unrelated to
what we discussed. All of this could be resolved constructively, it
would just take some open mindedness. Please consider this: when you're
thinking "why is everyone but me headed in the wrong direction?", it's
probably about time to reconsider you own course.

Best,
Oliver



___
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.

___
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] Software development and branches, was Re: [boinc_projects] keywords

[David Anderson]

Please read https://boinc.berkeley.edu/trac/wiki/SoftwareTesting
in particular the definition of "stable".

I think you're laboring under a misapprehension.
Testing a feature in isolation is not the same as testing the system.
No one is advocating committing untested or buggy code into master.
However, feature testing doesn't mean that master is stable.
For that, we need to do system-level testing in a separate release branch.

This is what we've done for years with the client software.
It works well and is efficient.
We should use the same approach for server software.

-- David


On 8/6/2017 12:15 PM, Bernd Machenschalk wrote:

On 04.08.17 23:17, David Anderson wrote:


On 7/21/2017 5:47 AM, Bernd Machenschalk wrote:


This might be one of the fundamental (pun intended) misunderstandings here. It 
is the opposite of everything I ever heard or read, and I think I know why:


How can one (expect to) fork a 'stable' branch from an 'unstable' one? How can 
one grow a tree (of branches) from an unstable foundation and expect it to be 
stable?

It's simple:

1) fork master, e.g. to client_release_xxx.  It's not stable at this point.
2) test client_release_xxx (e.g. using Alpha testers) fix bugs, repeat.  Now it's 
stable.

3) only backport bug fixes to client_release_xxx.  It remains stable.


This is like stabilizing a tree with an unstable trunk by supporting every branch 
with numerous tree props. The problem with that is not that it's impossible; it's 
just highly inefficient.


In the early times of CVS, where branching was a pain and merging was impossible, 
this once was the only feasible (yet not optimal) model. However already at that 
time there were people thinking of ways to stabilize the trunk, i.e. by 
introducing tests that should be ran locally (and pass) before committing anything 
into trunk.


There is one big lesson that has been learned from various small and large 
(software) projects: the later a problem is discovered, the more work is required 
to fix it. Thus a major effort in software engineering is to develop methods and 
tools to discover errors as early as possible. This is not for academic 
discussion, it is there to save everyone who develops software as much work as 
possible (The best work is one that you don't have to do at all). Examples of what 
we arrived at can be seen at github: Static code analysis and continuous 
integration (or continuous testing), integrated with flexible source code 
management systems. All of this is there to work for you so you don't have to do 
that work yourself.


If the trunk is completely unstable, problems pile up and even start to interact 
there. Disentangling these to later stabilize a branch might be difficult up to 
impossible, and it's certainly work that can be saved by testing each 
feature/development.commit separately, and only commit/push/merge it back to trunk 
if it works by itself.


The model of a completely unstable single development trunk may work for a small 
group of closely connected developers. It fails badly if there are multiple 
developers working on different features in parallel. One will always feel that 
the own development is ruined by the commits of someone else. Avoiding that 
requires a level of coordination that would be difficult to achieve among multiple 
developers spread over different timezones; at least it would slow down the actual 
development quite significantly.


Consequently I know of no (other) software project that still sticks to that 
model, in particular not in the distributed Open Source community. I may be wrong, 
though, corrections are welcome.



We've always used this approach for the client, and it's worked perfectly.
We can use the same approach for server if we create
a distributed testing system based on Beta projects (analogous to the client 
Alpha test)


The server is much more complex than the client, with all its components (that are 
project-specific to a large part) and options. What might have worked for the 
client will not work effectively for the server. Starting testing only at 
pre-release stage and then trying to fix the bugs that come up then is so 
inefficient that it wouldn't work at all for such a complex system.


Having learned and benefited from modern methods of software development I am no 
longer willing to waste my time on work that can be avoided altogether, and I know 
that quite a few BOINC developers feel the same.


I think if BOINC is willing to survive (with its currently limited resources) its 
software development process needs to become much more efficient by adopting 
modern methods. This will also help to increase the resources in terms of 
volunteer software developers. If that's not going to happen, BOINC will die.


Bernd


___
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 bott

Re: [boinc_dev] Software development and branches, was Re: [boinc_projects] keywords

[David Anderson]

On 7/21/2017 5:47 AM, Bernd Machenschalk wrote:


This might be one of the fundamental (pun intended) misunderstandings here. It is 
the opposite of everything I ever heard or read, and I think I know why:


How can one (expect to) fork a 'stable' branch from an 'unstable' one? How can one 
grow a tree (of branches) from an unstable foundation and expect it to be stable?

It's simple:

1) fork master, e.g. to client_release_xxx.  It's not stable at this point.
2) test client_release_xxx (e.g. using Alpha testers) fix bugs, repeat.  Now it's 
stable.

3) only backport bug fixes to client_release_xxx.  It remains stable.

We've always used this approach for the client, and it's worked perfectly.
We can use the same approach for server if we create
a distributed testing system based on Beta projects (analogous to the client 
Alpha test)

-- David
___
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?

[David Anderson]

Having the branch in a separate directory makes it easier
to keep track of what branch you're in.
That step is optional but Rom and I find it useful.
-- David

On 8/4/2017 3:10 AM, Richard Haselgrove wrote:

In that case, the workflow document linked by David earlier - 
https://boinc.berkeley.edu/trac/wiki/AdminReleaseManagement - contains totally 
unnecessary extra work steps:

* Clone branch: clone ​https://github.com/boinc/boinc.git into new dir w/ 
version num
* Right-click on dir; switch to new branch
* set version numbers in
* /: configure.ac, version.h, version.h.in, version.log
* in version.h, version.h.in: comment out pre-release with C syntax
* android: TODO; Oliver: textual representation, numerical value (increment) in 
7.6, it's 146, so use 147
* commit
* create tag client_release/7.8/7.8.0
* git push, check "include tags"

The only reasons I can see for creating a new directory are:

To create clean build folders for the development tools to work in
To create an offsite archival backup in case of disaster

and both of those should be done *after* the version number updates and tagging 
have taken place.

 On Friday, 4 August 2017, 10:54, Charlie Fenton 
 wrote:
  


  Hi Oliver,

Perhaps I'm not understanding what you meant by "contains", but if I create a new branch named 
"newbranch" from an existing branch named "oldbranch", then any commits made to oldbranch 
after that are not included in a build I make using newbranch unless I specifically port them over, such as 
by cherry picking them from oldbranch into newbranch or by merging one branch into the other. Is that not so?

I agree that your local repository always does contain all commits made to all branches as of the last time 
you synced with the remote repository, so you can "check out" any branch or tag you wish. As I 
understand it, checking out a branch or tag simply "hides" from your development tools anything 
that is not considered part of that branch or tag, while "revealing" to your developer tools 
everything that is considered part of the branch or tag.

This allows us to perform a build at any time from exactly the same source 
files as were originally used to build the version represented by the tag. And 
it allows us to build from a feature branch without including subsequent 
changes made outside that branch, which can be useful while developing a 
feature.

Since the client_release/7/7.8 branch was created from master and was then immediately 
tagged as client_release/7/7.8.0, Richard is correct that, as a result of the way the 
branch was created, all the Drupal source code up to that time became available in the 
branch and under that tag, along with everything else in master at that point. I believe 
that is what he meant by "included".

Cheers,
--Charlie

On Aug 4, 2017, at 12:45 AM, Oliver Bock  wrote:

On 03/08/17 17:03 , Richard Haselgrove wrote:

it also means that the whole of the Drupal source code was included in the 
v7.8.0 'client' tag.

Just to avoid potential confusion: we're not using SVN anymore. A git
branch always "contains" the whole repo, not some copy of specific parts
of it.

Best,
Oliver


___
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.


___
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?

[David Anderson]

On 8/4/2017 1:41 AM, Oliver Bock wrote:

hype, but because of its blatant advantages for what we do. Sadly BOINC
is still barely making use of it.

Actually we are.
___
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?

[David Anderson]

Branches and tags are different things in git.
The release process is described here:
https://boinc.berkeley.edu/trac/wiki/AdminReleaseManagement

-- David

On 8/4/2017 12:58 AM, Richard Haselgrove wrote:

Indeed. I'm slowly getting my head round the other differences that affect our 
workflow.

Is there also a change in the definition of a 'tag'? In SVN days, a tag - which 
we used to identify client code, nothing else - included only:

code which was used to build the client-related parts
code which Rom deemed fit and ready for use

If that selectivity is no longer available, does that mean we have to be 
careful to clear all client-related issues and bugs, before the 'tag-and-build' 
process for the next release? That we can't leave behind any unfinished 
business for the next cycle?

 On Friday, 4 August 2017, 8:45, Oliver Bock  wrote:
  


  On 03/08/17 17:03 , Richard Haselgrove wrote:

it also means that the whole of the Drupal source code was included in the 
v7.8.0 'client' tag.

Just to avoid potential confusion: we're not using SVN anymore. A git
branch always "contains" the whole repo, not some copy of specific parts
of it.

Best,
Oliver
___
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.


___
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] account managers and keywords

[David Anderson]

Account managers (BAM!, Gridrepublic) now have the option
of letting their users specify "keyword preferences"
indicating kinds of jobs they do or don't want to handle:
https://boinc.berkeley.edu/trac/wiki/JobKeywords

The keyword preferences can be included in the AM reply message:
https://boinc.berkeley.edu/trac/wiki/AccountManagement

This will become important when we get new umbrella projects
that host hundreds of research areas and research groups.

-- David
___
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 Travis CI builds

[David Anderson]

On 7/31/2017 1:04 AM, Jason Groothuis wrote:

change requests on all levels, in that the primary contributors have precisely 
zero understanding of operating systems or the nature of their differences, 
especially with respect to multi-threading and corresponding protocols for 
process handling.

Go away.
-- D
___
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] keywords

[David Anderson]

On 7/20/2017 2:11 AM, Oliver Bock wrote:

just meant to improve things - to make BOINC better. For instance, I for
one just can't take over a responsible (!) role as release manager for,
say, Android unless there's a codebase and a workflow I can trust. If

As you know, client releases (including Android) are build from
a stable branch like client_release/7/7.8.
Not from master.
The workflow for master isn't relevant here.
Let's not confuse things.

Adopting a particular SCM model isn't a magic wand that will somehow fix 
everything.
The issues you mention are, I think, not much related to SCM; e.g.:
- The reasons small research groups aren't creating BOINC projects is that the
  risk/reward economics are unfavorable and the documentation is sub-par.
- Some projects made changes to the server code and didn't do the 10% extra work
  of merging them into master, so it becomes progressively harder for them to 
upgrade.


___
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] keywords

[David Anderson]

This discussion comes down to two contrasting models for software development:

1) The "waterfall model":
https://en.wikipedia.org/wiki/Waterfall_model
New features are done as a unit, with sequential phases
(requirements, design, implementation, verification, maintenance).
E.g., requirements and design don't change during implementation.
Typically, development is done in a separate branch,
which is merged with master at the end.

2) The "agile model":
https://en.wikipedia.org/wiki/Agile_software_development
New features are divided into smaller self-contained pieces,
which are completed and merged with master frequently.
Requirements and design can change on the fly.
Development need not be done in a separate branch.

The role of master differs somewhat.
It changes more frequently in the agile model.
Master is unstable in both models; releases are done from stable branches.
In both models there may be periods when master doesn't work.
These periods are more frequent in the agile model.

---

Each model has pros and cons.
The waterfall model is generally regarded as old and ineffective.
The corporate software world has found that the agile model generally works better 
for them,

and has moved to it en masse.
For distributed open-source projects like BOINC,
the agile model has some aspects - such as a daily face-to-face "scrum" meeting 
-
that would be difficult to do, so it must be adapted somewhat.

Oliver prefers the waterfall model,
so strongly that he won't work with people who use agile.
I'll leave it to him to explain this preference.

I prefer the agile model for several reasons:

1) In the way I develop, requirements/design/implementation proceed iteratively and 
in parallel.

I find many situations where the implementation has become difficult or awkward,
and I can fix this by changing the design or even the requirements.

2) I often work on several things at once.
If I do each one in a separate branch,
I inevitably commit code to the wrong branch,
and it's hard to untangle things later.

3) I want my code reviewed and tested by others ASAP.
I have only Win7 and Linux computers.
If my code doesn't work on other platforms, I want to know this ASAP.
I want to commit to master in small-size, frequent units.

4) It's worked extremely well so far.
BOINC has evolved rapidly and continuously over 15 years.
It's still very malleable and well-structured, making it easy to change and add.
Very few big software systems can say this.


Which model should we use in BOINC?
I don't think we need to pick one or the other.
The owner of each software area (client, manager, etc.) could choose one.
Or we could leave it up to the developer.

And, as I've said repeatedly, the major problems facing BOINC -
such as the inadequacy of documentation
and the lack of volunteers for software release management -
don't involve software development,
the choice of model doesn't have much bearing on them.
Let's not get hung up on it.

Also, let's not confuse the choice of model with how we do stable branches.
Of course we need stable branches for server software and API.
The agile model doesn't preclude this.

-- David

___
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] keywords

[David Anderson]

As far as I can tell, none of the issues you mention have anything to do with 
whether
we call master a "development branch" or an "integration branch".

You seem to think that people who don't buy into your world view are resistant to 
change.

Not the case.

If we had more energy going to understanding code, fixing bugs, writing 
documents, etc.,
from the people who are able to do so, rather than dogmatic posturing, we'd all be 
better off.


On 7/20/2017 2:11 AM, Oliver Bock wrote:

On 20/07/17 10:09 , David Anderson wrote:

Sorry, but this isn't a sustainable model.

Well, it's sustained us this far.

Well, in that case we have a different understanding of "sustainable".
Yes, BOINC survived, barely, but did it strive? Is it easy (let alone
fun) to use for downstream projects? Did it attract a healthy number of
volunteer developers after the alleged transition into a community
driven open source software (OOS) project? Sure, source code management
(SCM) isn't all there's to it but it's a significant part of it. Maybe
you underestimate its effect? I'm also nearing a ten-year involvement in
BOINC and way too often it's been a pain to use it as a downstream
project because of the way its SCM is done. It's codebase is brittle and
just can't be trusted, unnecessarily. 15 years ago the tools and best
practices were different. But these things are moving. Why not
participate in the progress that's been made since then, making
everyone's professional life easier and BOINC more attractive? Yes, that
means change, but it doesn't hurt. If you don't adapt and progress it
can only get worse, in particular from the point of view of newly
interested scientists and contributors.

What I'm trying to say is: responding to constructive criticism with
"that's how we've done it for 10+ years, no need to change" isn't very
helpful if you want to see things improve. My proposal is (once again)
just meant to improve things - to make BOINC better. For instance, I for
one just can't take over a responsible (!) role as release manager for,
say, Android unless there's a codebase and a workflow I can trust. If
ideas, proposals or contributions aren't discussed at all or rejected
without meaningful reasoning people will stop trying. I'm sure that's
not in your interest.

Best,
Oliver



___
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] keywords

[David Anderson]

On 7/20/2017 12:37 AM, Oliver Bock wrote:


Sorry, but this isn't a sustainable model.

Well, it's sustained us this far.
We could have a server stable branch, as you've suggested,
if we could figure out how to test the server software.
___
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] keywords

[David Anderson]

On 7/19/2017 2:57 AM, Christian Beer wrote:

understand that some exploratory implementation should be done in the
meantime and I'm fine with that. But this should be happening in a
separate branch NOT in the master branch which is currently used to
build a 7.8 release.

The 7.8 client release uses the "client_release/7/7.8" branch, not master.
Master is for new development.
This is explained here:
https://boinc.berkeley.edu/trac/wiki/AdminReleaseManagement

-- David
___
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] keywords

[David Anderson]

Richard:
Thanks for the comments.
In the current framework, keywords have "symbols" as well as integer IDs:
https://boinc.berkeley.edu/keywords.php?header=c
https://boinc.berkeley.edu/keywords.php?header=python
This makes it easy to specify them e.g. in job-submission programs.

I think it's better not to encode hierarchy into the symbols,
because we may want to change the hierarchy over time:
e.g. to move Cosmology from Astronomy to Physics,
or create new levels.

This doesn't preclude hierarchical search;
it would be based on the actual hierarchy as encoded, e.g., in
https://boinc.berkeley.edu/keywords.php
rather than on symbols.

-- David

On 7/17/2017 3:40 AM, Richard Haselgrove wrote:

That intervention has prompted me to look more closely at the 'Job and Project 
Keywords' design document.
It reminds me very much of a project I was involved in between 1990 and about 
2005. I was the sole coder on the team, but the philosophy and design were led 
by a project leader above me.
Our project was called 'FunderFinder', and was intended to help UK community 
groups raise funds from UK charitable trusts, some of which had trust deeds 
dating back to the seventeenth century - so the terminology was arcane, to say 
the least. Our matching had to be more precise, so we did develop a 'complete 
taxonomy of charity funding' (with the help of a cataloguing expert from the 
British Library), but in general terms our solution was very similar to yours.
I would identify two differences - the first trivial, the second perhaps 
significant.
We used a three-way classification: People, Subjects, Places - that enabled us 
to distinguish between, for example, medical research into cancer (a subject), 
and the care of patients with cancer (people).
More importantly, instead of your integer to represent a keyword, we used an 
alphanumeric code: to keep the structure clear in our own minds, we used lower 
case letters for people, upper case letters for subjects, and numerals for 
places.
I can't match your examples exactly, but we had
HMedicine and HealthHM  Diseases and disordersHMWTumours 
(including cancer)HMWC  CancerHMWL  LeukaemiaHMWM  Melanoma
and for the patients,
jdgwc  Cancer
We found that seven-character codes were sufficient to cover the worst case, 
from 2 (UK) / 5 (rest of the world) down to a single historic parish council 
via the modern local government administrative structure.
The advantage of using a hierarchical coding was that I could use sub-string 
pattern matching to include and exclude higher or lower level matches. That's 
probably overkill for the current proposal, but it seems to be a shame to 
design out the possibility of a hierarchical search at this stage.

 On Monday, 17 July 2017, 9:04, Christian Beer <christian.b...@aei.mpg.de> 
wrote:
  


  I just want to voice my disagreement with the process in which this
proposal was handled. There was barely time to comment and so far no one
did but implementation into the master branch has already started for
what seems to be a major change to Client and Server code.

As a volunteer contributor and committer to BOINC and as a BOINC PMC
member this proposal and the process in which it is done does not have
my approval.

Regards
Christian

P.S.: Although this mail is sent from my AEI email the opinion expressed
above is my personal one.

On 14.07.2017 01:04, David Anderson wrote:

I propose adding a mechanism for associating keyword attributes
(such as science area) with jobs and projects.
https://boinc.berkeley.edu/trac/wiki/DesignKeywords
Comments welcome.
-- David
___
boinc_projects mailing list
boinc_proje...@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_projects
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.



___

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.

[boinc_dev] keywords

[David Anderson]

I propose adding a mechanism for associating keyword attributes
(such as science area) with jobs and projects.
https://boinc.berkeley.edu/trac/wiki/DesignKeywords
Comments welcome.
-- David
___
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] Bug#790222: wxwidgets3.0: depends on libwebkitgtk-1.0-0 which is deprecated

[David Anderson]

The wxHtmlWindow options sounds good.  We don't use CSS or JS.
-- D

On 7/6/2017 2:06 AM, Christian Beer wrote:

Olly Betts and Gianfranco explained a bit more about what the Debian
maintainer want to do. I'm not cross posting here. The gist is they want
to migrate wxWidgets to a maintained version of GTK and webkitgtk while
in the meantime drop the old unmaintained webkitgtk from Debian testing
and unstable.

Our options are to sit out the migration and have boinc-manager removed
from unstable and testing in the meantime or disable the in-app browser
for this period so we still have a boinc-manager package just without
Notification support (or switch to a limited text/html support).

In the debian bug thread Olly Betts wrote that there is wxHtmlWindow
available in wxWidgets which has limited HTML support (no CSS, no JS)
and is still available during the migration. We should investigate if we
can switch from wxWebView to this for the time of the wxWidgets
migration on Debian. Since we don't really use CSS or JS in the
notification system it seems rather straight forward and we wouldn't
even loose image or video support.

Regards
Christian

On 06.07.2017 10:32, David Anderson wrote:

If needed, BOINC can switch to showing notices in textual form on Linux;
I haven't seen many notices that use images or video anyway.
-- David

On 7/5/2017 7:18 AM, Gianfranco Costamagna wrote:

Hello All,

(boinc developers, this is a serious issue for Debian and I think
this will become an issue
for other distributions soon),

libwebkitgtk-1 is going to be removed soon from the archive, and
wxwidgets webview depends on it.


On Sat, Jul 01, 2017 at 08:23:08PM -0400, Jeremy Bicha wrote:

On Fri, Jun 30, 2017 at 8:47 PM, Olly Betts <o...@survex.com> wrote:

It seems the only rdep needing the webkit integration is boinc, so
dropping support would not cause widespread pain - if it gets to the
stage where wxwidgets3.0 is blocking removal of webkitgtk, I suggest
we just drop the dependency and the libwxgtk-webview3.0-0v5, etc
packages and get boinc to update not to use them.

Wouldn't libwxgtk-webview3.0-0v5 need to be renamed anyway? So maybe
it's ok to drop it and later you can reintroduce it with the new name
when you're ready to do your transition.

If there's an ABI change, it'll need renaming.  It's not clear to me if
there will be one without further investigation.

Either way, dropping it would affect boinc in unstable while it's gone,
which is really more of a concern than a trip through NEW.  I don't
know
what boinc does with webview, so I'm not sure if removing it renders
boinc almost useless or if it only affects some minor features, but
previously Gianfranco seemed unkeen on dropping it.  I've CCed him.

webview is used by boinc for notifications coming from server side,
does wxwidgets offer some better maintained webview support?
we might switch to gtk-3, this will switch the
libwebkitgtk-1.0-0 dependency to
libwebkitgtk-3.0-0, but I'm not sure how much we will gain from that
move.

G.


___
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.


___
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] Bug#790222: wxwidgets3.0: depends on libwebkitgtk-1.0-0 which is deprecated

[David Anderson]

If needed, BOINC can switch to showing notices in textual form on Linux;
I haven't seen many notices that use images or video anyway.
-- David

On 7/5/2017 7:18 AM, Gianfranco Costamagna wrote:

Hello All,

(boinc developers, this is a serious issue for Debian and I think this will 
become an issue
for other distributions soon),

libwebkitgtk-1 is going to be removed soon from the archive, and wxwidgets 
webview depends on it.


On Sat, Jul 01, 2017 at 08:23:08PM -0400, Jeremy Bicha wrote:

On Fri, Jun 30, 2017 at 8:47 PM, Olly Betts  wrote:

It seems the only rdep needing the webkit integration is boinc, so
dropping support would not cause widespread pain - if it gets to the
stage where wxwidgets3.0 is blocking removal of webkitgtk, I suggest
we just drop the dependency and the libwxgtk-webview3.0-0v5, etc
packages and get boinc to update not to use them.

Wouldn't libwxgtk-webview3.0-0v5 need to be renamed anyway? So maybe
it's ok to drop it and later you can reintroduce it with the new name
when you're ready to do your transition.

If there's an ABI change, it'll need renaming.  It's not clear to me if
there will be one without further investigation.

Either way, dropping it would affect boinc in unstable while it's gone,
which is really more of a concern than a trip through NEW.  I don't know
what boinc does with webview, so I'm not sure if removing it renders
boinc almost useless or if it only affects some minor features, but
previously Gianfranco seemed unkeen on dropping it.  I've CCed him.


webview is used by boinc for notifications coming from server side,
does wxwidgets offer some better maintained webview support?
we might switch to gtk-3, this will switch the
libwebkitgtk-1.0-0 dependency to
libwebkitgtk-3.0-0, but I'm not sure how much we will gain from that move.

G.


___
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.

[boinc_dev] bug if missing all_projects_list.xml

[David Anderson]

If the Manager and client start up and there is no all_projects_list.xml file,
the client starts an HTTP op to get it.
But before it's done, the Manager does an RPC to get the project list.
The RPC returns an empty list,
and the Manager brings up a Wizard with empty project list.

This is a bug in the Manager.
If it gets an empty project list it should try again in 10 sec or so.
It should never bring up an empty wizard.

(this may not have anything to do with the problem people are seeing).

-- David
___
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

[David Anderson]

Rom:
Any ideas on how to debug this problem?
-- David

On 7/3/2017 2:24 PM, Jacob Klein wrote:


This doesn't make sense to me. I had the problems with Windows 10 Creator’s 
update, and continue to have problems with Windows 10 Insider builds newer than 
that. My hunch is that Art has a scenario that masks/hides the issue. I still show 
it as broken.


*From: *David Anderson <mailto:da...@ssl.berkeley.edu>
*Sent: *Monday, July 3, 2017 5:14 PM
*To: *Art Masson <mailto:artmas...@gmail.com>; boinc_alpha email list 
<mailto:boinc_al...@ssl.berkeley.edu>
*Subject: *Re: [boinc_alpha] Disappearing BOINC Icon in System Tray (7.7.2) 
Requiring Manual Restart on Boot-Up


Thanks.
Jacob Klein, is this compatible with what you're seeing?
-- D

On 7/3/2017 11:23 AM, Art Masson wrote:
>
> I've just tested this with BOINC 7.8.0 and the application starts correctly 
when
> Windows reboots or starts up on my machine.  From my standpoint this incorrect
> behavior appears to have been fixed with Windows 10 Creators release and was 
not a
> BOINC application problem.
>
> Art Masson
>
>
>
> On 7/3/2017 12:04 PM, Art Masson wrote:
>> REF: Disappearing BOINC Icon in System Tray (7.7.2)  Requiring Manual 
Restart on
>> Boot-Up
>>
>> Hi...I'm not seeing this problem with BOINC 7.7.2 now that I've upgraded to
>> Windows 10 Creators version (10.00.15063.00) (newest release).  I did see 
this
>> problem with 7.7.2 and 7.6.33 with the previous Windows 10 release
>> (10.00.14393.00).  This appeared to be a problem with Windows startup actions
>> because there were other apps that didn't start as well with the older 
Windows 10
>> release -- this was a known problem apparently. I have not tried with 7.8 
yet.
>>
>> Art Masson
>>
>>
>
> --

___
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.

[boinc_dev] various

[David Anderson]

Various opinions about BOINC:

1) Our top priority at this point is to build, test, and release clients and 
wrappers
that work on the latest versions of all platforms, including Android, and with the 
latest VBox.

Installing/using BOINC needs to be easy and seamless for everyone.
Currently this is not the case; e.g. the BOINC/VBox client
doesn't work on Win10 because it has an old VBox.
And there have been critical bug fixes since 7.6.33.

This process consists of many tasks: see
https://boinc.berkeley.edu/trac/wiki/AdminTasks
Rom Walton used to do most of them.
Since he left, most of the roles are unfilled.
We're trying to remedy this.
If you're interested in any of the roles, let me know.

2) The client and server software are in maintenance mode.
AFAIK they don't need any new capabilities.
They're already packed with features (like storage management) that no one is 
using.
There are a few code areas that are overly complex:
app version selection in the scheduler comes to mind.
Other than these, the code is well organized, terms of both files and 
directories.
And it's not clear that the cost/benefit of rewriting the problem areas is 
worth it.

3) The GUI code is a mixed bag.
The BOINC Manager is sort of a mess code-wise, partly because of WxWidgets.
Also, the UI/UX needs to be rethought, with the goal of incentivizing non-techie 
volunteers.

Eventually we'll need new GUIs for both desktop and mobile.
This is a long-term goal, and it needs to involve UI/UX expertise we don't currently 
have.


4) The web code (PHP) is mostly in good shape.
The factorization into functions is nice; it makes it easy to change things;
e.g. using Bootstrap wasn't that hard,
and using a different CSS framework would be pretty easy if we wanted to.
A few areas (e.g. forums) have become overly complex;
I periodically try to simplify them.
The preferences code (esp. project-specific preferences) is a weak link.
We need to supply both simple and advanced versions, as the Drupal code does.
And we need to simplify the implementation.

5) The server documentation is a major weak link.
When scientists look at BOINC this is what they see - not the code.
We need to think about separating it more into "Getting Started" and 
"Reference".
Right now it's just Reference, which is overwhelming to first-time readers.

-- David
___
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] master branch broken?

[David Anderson]

Oops!  Fixed.
-- D

On 6/7/2017 8:52 AM, Gianfranco Costamagna wrote:

Hello, latest commits are not building anymore
libtool: link: /usr/bin/g++ -Wall -Wextra -Wshadow -Wredundant-decls -Wdisabled-optimization -Wpointer-arith 
-Wstrict-aliasing -Wcast-align -g -O3 
"-fdebug-prefix-map=/<>/boinc-7.7.0+dfsg~git20170607+r23753~r7~ubuntu17.04.1=." -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -O3 -funroll-loops -fforce-addr -ffast-math -flto -Wall 
-Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -flto -g -O3 
"-fdebug-prefix-map=/<>/boinc-7.7.0+dfsg~git20170607+r23753~r7~ubuntu17.04.1=." -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -O3 -funroll-loops -fforce-addr -ffast-math -flto -o 
.libs/cgi credit.o edf_sim.o handle_request.o hr.o hr_info.o plan_class_spec.o sched_array.o sched_assign.o sched_check.o 
sched_customize.o sched_files.o sched_hr.o sched_limit.o sched_locality.o sched_main.o sched_nci.o sched_resend.o 
sched_result.o sched_score.o sched_send.o sched_timezone.o sched_vda.o sched_ve

rs

  ion.o sched_types.o time_stats_log.o  ../sched/.libs/libsched.so 
../lib/.libs/libboinc_crypt.so ../lib/.libs/libboinc.so 
-L/usr/lib/powerpc64le-linux-gnu -lmysqlclient -lpthread -lz -lm -lrt -latomic 
-ldl -L/usr -L/usr/lib -lssl -lcrypto -pthread
/tmp/ccrjyqlW.ltrans0.ltrans.o: In function `log_request':
./sched/handle_request.cpp:1139: undefined reference to 
`SCHED_MSG_LOG::set_indent_level(int)'
/tmp/ccrjyqlW.ltrans3.ltrans.o: In function `handle_request(_IO_FILE*, 
_IO_FILE*, char*)':
./sched/handle_request.cpp:1496: undefined reference to 
`SCHED_MSG_LOG::set_indent_level(int)'
collect2: error: ld returned 1 exit status

https://launchpadlibrarian.net/322962429/buildlog_ubuntu-zesty-ppc64el.boinc_7.7.0+dfsg~git20170607+r23753~r7~ubuntu17.04.1_BUILDING.txt.gz

thanks

G.
___
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] Problems at The Lattice Project

[David Anderson]

Thanks; I removed it from the web-site list for now.
-- D

On 6/5/2017 5:54 PM, Robert Miles wrote:
I finally reached someone at the project, who replied that it is shut down for a 
number of reasons and not expected to restart.


No details given about just what those reasons are.


Date: Fri, 19 May 2017 18:23:04 -0500
From: Robert Miles 
Subject: [boinc_dev] Problems at The Lattice Project

Do any of you know what happened to The Lattice Project?

For about a week, their web site has been unreachable on the internet.

I was able to reach a site that appears to be for their department at
their university; no relevant news there.


___
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] master broken

[David Anderson]

Oops!  Fixed; thanks!

This is a warning that not all compilers might flag;
printf("foo")
is technically valid but not generally what you want.

-- D

On 5/12/2017 2:20 AM, Gianfranco Costamagna wrote:

Hello David,

boinc_client-app.o `test -f 'app.cpp' || echo './'`app.cpp
/usr/bin/g++ -DHAVE_CONFIG_H -I. -I..  -I.. -I../api -I../db -I../lib -I../lib/mac 
-I../sched -I../tools -I../vda -pthread -Wdate-time -D_FORTIFY_SOURCE=2  -Wall -Wextra 
-Wshadow -Wredundant-decls -Wdisabled-optimization -Wpointer-arith -Wstrict-aliasing 
-Wcast-align  -I/usr/include -I/usr/include/openssl  -g -O3 
-fdebug-prefix-map=/<>/boinc-7.7.0+dfsg~git20170511+r23716~r6~ubuntu16.10.1=.
 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wall -O3 -funroll-loops 
-fforce-addr -ffast-math -flto -Wall -c -o boinc_client-app_config.o `test -f 
'app_config.cpp' || echo './'`app_config.cpp
app_config.cpp: In function ‘void 
print_msgs(std::vector, PROJECT*)’:
app_config.cpp:128:58: error: format not a string literal and no format 
arguments [-Werror=format-security]
msg_printf_notice(p, false, NULL, msgs[i].c_str());
^
cc1plus: some warnings being treated as errors


+static void print_msgs(vector msgs, PROJECT* p) {
+for (unsigned int i=0; i

Re: [boinc_dev] Android 5.0 Issues

[David Anderson]

Thanks; I added an issue on Github.
-- David

On 4/29/2017 9:50 PM, James Whitley wrote:

Tablet: RCA
Model #RCT6773W22B
Android version 5.0
BOINC Version 7.4.53

Though I have preferences set to run on charger or with USB power
connection, and tablet is connected to charger (verified by seeing battery
is charging), BOINC continues with message "Connect your device to a charger
to continue computing." I've tried couple chargers, and connected via USB to
couple computers. However, continue with above message.

Also note that when I add "allow use with battery (set to be 90% or
greater)" to preferences, I'll then get the message "Computing will resume
when battery charge reaches 90% (currently 100%)." Strange!  It MAY crunch
for a short time (no longer than 2-3 days) and then stop again after I
restart BOINC Mgr. or abort a WU, or maybe at its own whim.
  
Tablet otherwise works well on all other apps installed. Note that above

BOINC version is working well on phones with Android 4.1.1 and 6.01 (though
very slow crunching on 4.4.1 phone with 1 processor, as expected).
  
Sincerely,
  
James Whitley

___
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] cert_all.php issues

[David Anderson]

Odd - it works on SETI@home and my test project.
Anyone else seeing problems?

The URL is right, but there needs to be something after cpid=

-- David

On 4/27/2017 10:15 AM, David E Kim wrote:

I’m working on a BOINC server upgrade and “cert_all.php” doesn’t seem to work.

The following is hard coded in user.inc but gives a forbidden error response:

http://boinc.netsoft-online.com/get_user.php?cpid=



Is there another url that we should use?

thanks in advance,

David Kim

Rosetta@home developer

___
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] Two bugs

[David Anderson]

On 4/10/2017 11:45 PM, Krzysztof Piszczek wrote:

1. If you create two projects on same server, then on old sources
(downloaded 14/02/2017) works fine, but just tested new sources create a
bug where daemons not works correct  - daemons from project "1" try to
work with work units from project "2", even if you change it's names etc.

Each project should have its own MySQL database,
whose name is the name of the project.
The DB names are in ~/projects/projname/config.xml

Can you check whether the DB names there () are correct?

-- David
___
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] Requesting advice on releasing hot fix 7.6.34 for Mac

[David Anderson]

Sounds good to me.
Charlie, thanks for all your work!
-- David

On 4/8/2017 4:20 PM, Charlie Fenton wrote:

The good news is that I have received confirmation from several Mac users that 
I have found a fix for the serious BOINC Manager problem with Notices on Mac OS 
10.12.4. So I want to quickly release a fix for this urgent problem.

My plan is to build a version 7.6.34 for the Mac using the identical sources as are in 
7.6.33 except for the one line change needed to NoticeListCtrl.cpp (and a new version.h.) 
This will allow me to bypass the need for alpha testing and immediately promote the build 
to "recommended version."

But there is a problem doing this in the GIT repository client_release/7/7.6 
branch. In the past, commits were ported to that branch only in the process of 
doing a release for alpha testing, and a new tag (such as 
client_release/7.6/7/6.33) was then immediately made at the most recent commit. 
 But there have been many commits ported to that branch since the release of 
7.6.33.

If I just commit this change at the end of the branch, all those untested 
changes will also be included, and these should not be released without proper 
alpha testing.

So my current thinking is to create an OSX_notices_hotfix branch off the 
client_release/7.6/7/6.33 tag, add my change (and the new version.h, etc.) in 
that branch, and create the 7.6/7/6.34 tag there. I would also add my commits 
to the end of both the client_release/7/7.6 branch and the GIT master, to 
ensure they are included in future builds.

Though I am confident my change will also work on other platforms, it should be 
alpha tested on those platforms before being fully released for them. By adding 
this commit to the client_release/7/7.6 branch and the GIT master, they will 
automatically be tested the next time a new build is made available for alpha 
testing.

Is this what I should do, or does anyone have a better suggestion?

Cheers,
--Charlie

--
Charlie Fentoncharl...@ssl.berkeley.edu
BOINC / SETI@home Macintosh & Windows Programmer
Space Sciences Laboratory
UC Berkeley



___
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 API issue with android arm?

[David Anderson]

I added it.
Uncomment the #define MSGS_FROM_FILE,
then put msgs like "" in msgs.txt.
When the API sees this, it will handle it and delete the file.

-- David

On 4/7/2017 5:28 PM, David E Kim wrote:

I’ll can test this.  That’s the only way I’d know if it’s ok.

It will be easier for me to test if you include the text file messaging if you 
don’t mind/ or I’d just re-implement the signals.

Thanks David!

David K





On Apr 7, 2017, at 5:13 PM, David Anderson <da...@ssl.berkeley.edu> wrote:

I made some revisions to David Kim's code and put it in a branch:
https://github.com/BOINC/boinc/tree/android_api_dpa

The main changes:

- I added and fixed comments about the thread/signal structure

- In exit_from_timer_thread():
  removed the "boinc_status.suspended = false" and the first "sleep(2.0)".
  I don't see why either of these is needed.

- in timer_handler():
  If detect heartbeat failure, don't bother sending signal to work thread;
  exit_from_timer_thread() already does this.

- in worker_signal_handler, don't bother checking that we're the timer thread.
  Now that we use pthread_kill() instead of setitimer(),this will always be the 
case.

- I didn't include the stuff about debugging using external signals.
  That's a good idea, but there's a simpler way to do it:
  have the API look for control messages in a file instead of shared memory.
  e.g. you could tell the app to quit by writing  to the file.
  This would work on Win too.
  (I didn't add this, but will on request; it's a two-line change)

- didn't include the "in_critical_section > 0" changes; not needed.

David K, can you take a look at this and see if it's OK?

Thanks -- David


___
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 API issue with android arm?

[David Anderson]

I'll add the text-file way now.
-- D

On 4/7/2017 5:28 PM, David E Kim wrote:

I’ll can test this.  That’s the only way I’d know if it’s ok.

It will be easier for me to test if you include the text file messaging if you 
don’t mind/ or I’d just re-implement the signals.

Thanks David!

David K





On Apr 7, 2017, at 5:13 PM, David Anderson <da...@ssl.berkeley.edu> wrote:

I made some revisions to David Kim's code and put it in a branch:
https://github.com/BOINC/boinc/tree/android_api_dpa

The main changes:

- I added and fixed comments about the thread/signal structure

- In exit_from_timer_thread():
  removed the "boinc_status.suspended = false" and the first "sleep(2.0)".
  I don't see why either of these is needed.

- in timer_handler():
  If detect heartbeat failure, don't bother sending signal to work thread;
  exit_from_timer_thread() already does this.

- in worker_signal_handler, don't bother checking that we're the timer thread.
  Now that we use pthread_kill() instead of setitimer(),this will always be the 
case.

- I didn't include the stuff about debugging using external signals.
  That's a good idea, but there's a simpler way to do it:
  have the API look for control messages in a file instead of shared memory.
  e.g. you could tell the app to quit by writing  to the file.
  This would work on Win too.
  (I didn't add this, but will on request; it's a two-line change)

- didn't include the "in_critical_section > 0" changes; not needed.

David K, can you take a look at this and see if it's OK?

Thanks -- David


___
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 API issue with android arm?

[David Anderson]

I made some revisions to David Kim's code and put it in a branch:
https://github.com/BOINC/boinc/tree/android_api_dpa

The main changes:

- I added and fixed comments about the thread/signal structure

- In exit_from_timer_thread():
  removed the "boinc_status.suspended = false" and the first "sleep(2.0)".
  I don't see why either of these is needed.

- in timer_handler():
  If detect heartbeat failure, don't bother sending signal to work thread;
  exit_from_timer_thread() already does this.

- in worker_signal_handler, don't bother checking that we're the timer thread.
  Now that we use pthread_kill() instead of setitimer(),this will always be the 
case.

- I didn't include the stuff about debugging using external signals.
  That's a good idea, but there's a simpler way to do it:
  have the API look for control messages in a file instead of shared memory.
  e.g. you could tell the app to quit by writing  to the file.
  This would work on Win too.
  (I didn't add this, but will on request; it's a two-line change)

- didn't include the "in_critical_section > 0" changes; not needed.

David K, can you take a look at this and see if it's OK?

Thanks -- David
___
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 API issue with android arm?

[David Anderson]

I'll look at this now; I was swamped earlier.
-- David

On 4/5/2017 11:39 AM, David E Kim wrote:

Hi all,

I’m not sure if this is the right list to use but thought I’d mention it here.  
 I tried to contact David Anderson via email but have not heard back.

I was wondering if anyone has random seg fault issues with their android apps 
for their BOINC projects.  Our Rosetta@home android application had pretty bad 
success rates and I found that the main cause was the use of “setitimer” in the 
“start_worker_signals” function in the boinc_api.cpp code.  Our Rosetta app 
runs stable without the BOINC api, but when using the default api, it crashed 
randomly.

I developed a workaround which avoids “setitimer" in the api code and our app 
is stable with the modified BOINC api and is now in production for our Rosetta@home 
project.  Our success rates for android arm have gone from 40-60% to 95%.

I’m wondering if this is just a Rosetta application induced bug (it’s a pretty 
substantial scientific app) or a general android issue.

Thanks,

David Kim
___
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] An additional preference to prevent, downloading when on WiFi, to enable downloading only on when connected, to cable

[David Anderson]

I agree: having BOINC estimate the current bandwidth of network interfaces
or end-to-end paths is a can of worms.

By using Docker, a VM image can be broken up into multiple files, or "layers",
most of which don't change as apps evolve, and thus are downloaded once to a 
given host.
These files are typically on the order of 25 MB.
On a 20 Mbps link such a file can potentially be downloaded in 10 seconds.
So in some cases network performance is not a big issue.

-- David

On 4/3/2017 1:37 PM, AgentB wrote:

Sorry for being late to the party, maybe i'm missing something but sometimes it is better 
not to add functionality which belongs elsewhere, to make boinc "network interface 
aware" may open a large number of issues.

boinc is not a network monitoring application so it will struggle with this.

There a myriad of network adapters such as - dual and paired adapters /  
virtual adapters  / adapters in fail-over pairs to name a couple.

There are many types of wired and wireless adapters USB wireless etc.

Each OS has its own way of naming, measuring and managing them
Each users will have "preferences" of what is best - fastest least cost and 
most won't care etc.

boinc would have to make sense of them all.

If the OP wants to do this, it is easy to write a basic script tailored to the 
host to achieve this - this is what boinccmd is good for.

In linux this is easy with a if-up and if-down scripts

My windows skill are a little rusty but something like this - totally untested 
script - which turn boinc network off when some interface is enabled.

The script will only work if the netsh output is tuned indicative of the state 
for the host/adapter in question.



---
ECHO OFF

:REPEATLOOP

netsh interface show interface | find "EnabledConnected  Dedicated
wifi" > nul
IF ERRORLEVEL 1 GOTO NoWifi

ECHO Connected to wifi
boinccmd --set_network_mode always

GOTO END

:NoWifi
ECHO Not Connected
boinccmd --set_network_mode never

:END
TIMEOUT 60
GOTO REPEATLOOP


I'd also add a current state environment variable and only run boinccmd if the 
state changed to make it more efficient.



Best regards
Mike


On 02/04/17 15:04, Charles Elliott wrote:

A computer can have as many connections to an IP address as it has free
ports (numbered up to 65535, although many of the numbers less than 32768
are reserved) and memory for the software implementation of an abstract
concept called a "socket."

A TCP/IP connection is defined by four numbers: client IP address, client
port; server IP address, server port.  For example, right now I have, inter
alia, the following connections displayed in the connections table of my
router:

192.168.0.100:61266  151.101.22.2:80
192.168.0.100:61368  151.101.22.2:80
192.168.0.100:61367  151.101.22.2:80
192.168.0.100:61265  151.101.22.2:80
192.168.0.100:61268  151.101.22.2:80
192.168.0.100:61269  151.101.22.2:80


151.101.22.2 is an IP address owned by fastly.com, a CDN, which I believe
stands for Content Delivery Network.  When a browser accesses a webpage, it
is told to download the advertisements from fastly.com.  Advertisers upload
their content to fastly.com, and it is delivered when and where requested.
Fastly may also help with billing issues and generating statistics on
impressions delivered and viewed and possibly follow thru, but I am not
certain about that.

I don't understand what this discussion is about, though I suspect it is
fundamentally about net neutrality.  At one point the Oxford project person,
David, wrote:


It would be much easier if the clients did this. My Mac for example
is able to tell me the latest network bandwidth it has for any of its
interfaces.

If by client he means his application, then all he has to do is put the
download timing code in his application.  Then if he wants to refuse to
deliver very large files to computers with very narrow bandwidth
connections, it is all on him and the school.  I believe that if you just
explain to people with clear, jargon-less statements why it is infeasible to
deliver very large files in kilobit dribbles, they will not object.  I did
not like it when GPU Grid told me I could not participate when I signed up
because my video cards were inadequate, but I got over it (and eventually
bought new video cards, which I used elsewhere).

Charles Elliott


-Original Message-
From: boinc_dev [mailto:boinc_dev-boun...@ssl.berkeley.edu] On Behalf Of
Robert Miles
Sent: Sunday, April 2, 2017 1:26 AM
To: boinc_dev@ssl.berkeley.edu
Subject: Re: [boinc_dev] An additional preference to prevent, downloading
when on WiFi, to enable downloading only on when connected, to cable

  From what I've seen, Windows operating systems do not allow multiple
connections to the internet to be active at once, which means that only one
such connection can be reachable from BOINC at 

Re: [boinc_dev] An additional preference to prevent downloading when on WiFi, to enable downloading only on when connected to cable

[David Anderson]

The existing network features are:
- use network only when computer is idle
- time of day and day of week exclusion
- the ability to manually stop network use

These seem to have been sufficient for many years.
If there's a large set of volunteers who know about these features
and feel that they need something else,
I'd be interested in reading their comments.

-- David
___
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] Fwd: Re: [boinc_alpha] R: BOINC 7.7.2 released for Win

[David Anderson]

The server code was never versioned per se.
It has a change log that is not up to date:
http://boinc.berkeley.edu/trac/wiki/ServerUpdates
-- David

On 3/29/2017 1:16 AM, Richard Haselgrove wrote:

And these particular change logs -


http://boinc.berkeley.edu/wiki/Release_Notes_for_BOINC_7.6

https://boinc.berkeley.edu/dev/forum_thread.php?id=10204


are for the Client and GUI only - the server code isn't versioned any longer. 
Sadly.


On Wednesday, 29 March 2017, 9:09, David Anderson <da...@ssl.berkeley.edu> 
wrote:


The change logs are for volunteers,
so that they can see a summary of functional changes and decide whether to 
upgrade.
People who want to see commit notes can read them easily enough.
-- David

On 3/29/2017 1:04 AM, Oliver Bock wrote:
> On 29/03/2017 9:40 , Vitalii Koshura wrote:
>>  From my POV the the most hard part of this is to select important
>> commits only.
> As long as you ignore merge commits, which is easy given their common
> commit message prefix, EVERY commit is important. Changelogs are for
> *various* user groups and thus should be complete (you won't know what's
> "important"!). Sure, this all depends on having proper commits (atomic,
> message prefixes) in the first place, but that's a different problem.
>
> tl;dr: given our scarce resources changelogs should be created
> automatically, as part of a proper release process. Proper commit
> discipline is needed to facilitate that but it's easy to come by.
> Disregarding commit discipline "in favor of" manual changelog harvesting
> would be ridiculous.
>
> Cheers,
> Oliver
>
> ___
> boinc_dev mailing list
> boinc_dev@ssl.berkeley.edu <mailto: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 <mailto: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] Fwd: Re: [boinc_alpha] R: BOINC 7.7.2 released for Win

[David Anderson]

The change logs are for volunteers,
so that they can see a summary of functional changes and decide whether to 
upgrade.
People who want to see commit notes can read them easily enough.
-- David

On 3/29/2017 1:04 AM, Oliver Bock wrote:

On 29/03/2017 9:40 , Vitalii Koshura wrote:

 From my POV the the most hard part of this is to select important
commits only.

As long as you ignore merge commits, which is easy given their common
commit message prefix, EVERY commit is important. Changelogs are for
*various* user groups and thus should be complete (you won't know what's
"important"!). Sure, this all depends on having proper commits (atomic,
message prefixes) in the first place, but that's a different problem.

tl;dr: given our scarce resources changelogs should be created
automatically, as part of a proper release process. Proper commit
discipline is needed to facilitate that but it's easy to come by.
Disregarding commit discipline "in favor of" manual changelog harvesting
would be ridiculous.

Cheers,
Oliver

___
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_alpha] BOINC 7.7.2 released for Win

[David Anderson]

I merged https://github.com/BOINC/boinc/pull/1514. 
<https://github.com/BOINC/boinc/pull/1514>


Are there any other pull requests that should be merged at this point?

-- David

On 3/27/2017 5:19 PM, Vitalii Koshura wrote:

Hello David,

I can go through the list of commits and create a list of issues which were 
fixed.
Also I have 2 questions to you:
1 - Will the branch client_release/7/7.7 be created? Without this it is quit hard 
to understand what was included into new release.
2 - If you build new release (as well as 7.6.33) from master branch then I need to 
ask you to merge https://github.com/BOINC/boinc/pull/1514 and manually resolve the 
conflicts because this PR put back the fixes which were accidentally deleted by 
this commit: 
https://github.com/BOINC/boinc/commit/6beafff6936a59b44fa923dc4d12a1564310f8eb
Without this the changes I made for https://github.com/BOINC/boinc/issues/79 are 
not complete and the feature doesn't works.


Also I do not see the reason why we need to drop Windows XP support. I understand 
that this OS is not supported by Microsoft but the BOINC is stable on it (I can 
make additional checks on Windows XP SP2, possibly on SP3 too).


Thanks

Best regards,
Vitalii Koshura

2017-03-28 1:39 GMT+03:00 David Anderson <da...@ssl.berkeley.edu 
<mailto:da...@ssl.berkeley.edu>>:


We'll extend the current log.
http://boinc.berkeley.edu/trac/wiki/VersionHistory
<http://boinc.berkeley.edu/trac/wiki/VersionHistory>

Speaking of which, is anyone interested in going through the list of commits
and writing up the changes in 7.7.2 (and possibly for 7.6.33 as well?)

Thanks
-- David


On 3/26/2017 9:51 PM, Clifton L. Harding Jr wrote:

Will the change log be a continuation of the current 7.5/7.6 log or 
will a
new one be established?


 From the desk of:


Clifton L. Harding Jr.

  mailto:chard...@ix.netcom.com>>
clharding...@verizon.net <mailto:clharding...@verizon.net>


___
boinc_alpha mailing list
boinc_al...@ssl.berkeley.edu <mailto:boinc_al...@ssl.berkeley.edu>
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
<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 <mailto:boinc_al...@ssl.berkeley.edu>
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
<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] Fwd: Re: [boinc_alpha] R: BOINC 7.7.2 released for Win

[David Anderson]

Vitalii:
Yes, please do that.
For me, the most significant change is:
https://github.com/BOINC/boinc/commit/d7f4551f6f4aa782ce8a1ae510e9eed23b8b588f
which fixes a client bug that causes file corruption when downloading
multiple large files concurrently.

7.7.2 was mostly to see if I could actually do a release; Rom did all previous 
ones.
I'll make a branch for the next release.

--D

On 3/28/2017 12:34 AM, Vitalii Koshura wrote:

Hello all,

I agreed. Release should be done next way:
1 - create new release branch 'client_release/7/7.7' based on
'client_release/7/7.6'
2 - merge necessary commits using 'cherry-pick' from master branch.

I can do the hard job and prepare the list of commits for 7.7 release and
also prepare the list of fixes with issue numbers.
This can help testers to check all fixes and report their status.

@David, if you want me to help you to do this - just tell me. Otherwise
I'll not do this because I do not want to do unnecessary work.

Thanks

Best regards,
Vitalii Koshura

2017-03-28 9:54 GMT+03:00 Christian Beer <christian.b...@aei.mpg.de>:


This is already documented here:
http://boinc.berkeley.edu/trac/wiki/TranslationSystem

The last translation update into master was 8 days ago. Since I don't
know what SHA1 was used to build 7.7.2 (as there is no tag or
documentation) I can't say if translations are up to date or not.

I strongly disagree with the way this alpha release was done and for now
I won't participate in fixing it.

Regards
Christian

On 28.03.2017 00:22, David Anderson wrote:

I don't know how to update the translations;
Christian, can you please check
http://boinc.berkeley.edu/trac/wiki/AdminLocalize
and add instructions?
Thanks -- David

 Forwarded Message 
Subject: Re: [boinc_alpha] R: BOINC 7.7.2 released for Win
Date: Mon, 27 Mar 2017 22:30:19 +0100
From: Miguel Veiga <miguel.v...@gmail.com>
To: Kathryn Marks <kathryn.bo...@gmail.com>
CC: David Anderson <da...@ssl.berkeley.edu>, BOINC Alpha list
<boinc_al...@ssl.berkeley.edu>



David, dont forget to update the translations into this new build

<https://www.avast.com/sig-email?utm_medium=email_

source=link_campaign=sig-email_content=webmail>

 Sem vírus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email_

source=link_campaign=sig-email_content=webmail>



2017-03-27 21:55 GMT+01:00 Kathryn Marks <kathryn.bo...@gmail.com
<mailto:kathryn.bo...@gmail.com>>:

I think he wants support for XP dropped.

On Mon, Mar 27, 2017 at 4:17 PM, David Anderson
<da...@ssl.berkeley.edu
<mailto:da...@ssl.berkeley.edu>>
wrote:

 > I don't understand what you're requesting.
 > -- David
 >
 >
 > On 3/27/2017 2:42 AM, bobo...@libero.it
<mailto:bobo...@libero.it> wrote:
 >
 >> Ok, i try 7.7.2 on Window Xp 32bit SP3
 >> It runs.
 >> Stop this support, please.
 >>
 >>
 >> Messaggio originale
 >>> Da: "David Anderson" <da...@ssl.berkeley.edu
<mailto:da...@ssl.berkeley.edu>>
 >>> Data: 26/03/2017 8.59
 >>> A: "BOINC Alpha list"<boinc_al...@ssl.berkeley.edu
<mailto:boinc_al...@ssl.berkeley.edu>>, "BOINC Developers
 >>>
 >> Mailing List"<boinc_dev@ssl.berkeley.edu
<mailto:boinc_dev@ssl.berkeley.edu>>
 >>
 >>> Ogg: [boinc_alpha] BOINC 7.7.2 released for Win
 >>>
 >>> I released a new version of the client for Win.
 >>> Changes:
 >>>
 >>> - An accumulation of enhancement/fixes in the manager and
client since
 >>> June
 >>>
 >> 2016.
 >>
 >>> - The Vbox versions include VBox 5.1.18
 >>> - not code-signed (I didn't have the $200 needed to renew the
 >>> certificate).
 >>> - built by me rather than Rom (hopefully I did it right).
 >>>
 >>> Please give it a try.
 >>> Alpha testers can report bugs here:
 >>> http://boinc.berkeley.edu/alpha/test_form.php
<http://boinc.berkeley.edu/alpha/test_form.php>
 >>>
 >>> -- David
 >>> ___
 >>> boinc_alpha mailing list
 >>> boinc_al...@ssl.berkeley.edu
<mailto:boinc_al...@ssl.berkeley.edu>
 >>> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
<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] Fwd: Re: [boinc_alpha] BOINC 7.7.2 released for Win

[David Anderson]

This sounds like a Manager issue.
Can those who have changed the manager since 7.6.33 please try to repro and fix 
this?
Thanks -- David


 Forwarded Message 
Subject:Re: [boinc_alpha] [boinc_dev] BOINC 7.7.2 released for Win
Date:   Tue, 28 Mar 2017 01:03:12 +
From:   Jacob Klein 
To: SETI Alpha 



I am noticing this behavior too!


When I restart my PC, then login to Windows, BOINC Manager correctly launches, but I'm 
erroneously greeted with the "Choose a project" page, and the Categories 
combobox is completely empty, and the Projects selection grid is completely blank. 
Clicking Cancel, then Yes to confirm, allows the Manager to proceed normally.


Can we please get it fixed?


PS: Clifton: You might want to edit your email address book; the "BOINC Alpha" email 
address is not known as "SETI Alpha" :)


- Jacob




From: boinc_alpha  on behalf of Clifton L. 
Harding Jr 
Sent: Sunday, March 26, 2017 10:49 AM
To: SETI Alpha
Subject: Re: [boinc_alpha] [boinc_dev] BOINC 7.7.2 released for Win



Each time that I recycle my machine BOINC acts as if it is the first time
that I have used the application and enters the panel to  either start a new
project or sign-on to an existing one.  When 'cancel' is clicked BOINC
reverts to its normal state and processing begins normally.

From the desk of:



Clifton L. Harding Jr.

  clharding...@verizon.net



___
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] BOINC 7.7.2 released for Win

[David Anderson]

We'll extend the current log.
http://boinc.berkeley.edu/trac/wiki/VersionHistory

Speaking of which, is anyone interested in going through the list of commits
and writing up the changes in 7.7.2 (and possibly for 7.6.33 as well?)

Thanks
-- David

On 3/26/2017 9:51 PM, Clifton L. Harding Jr wrote:

Will the change log be a continuation of the current 7.5/7.6 log or will a
new one be established?

  


 From the desk of:

  


Clifton L. Harding Jr.

   clharding...@verizon.net

  


___
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.

[boinc_dev] Fwd: Re: [boinc_alpha] R: BOINC 7.7.2 released for Win

[David Anderson]

I don't know how to update the translations;
Christian, can you please check
http://boinc.berkeley.edu/trac/wiki/AdminLocalize
and add instructions?
Thanks -- David

 Forwarded Message 
Subject:Re: [boinc_alpha] R: BOINC 7.7.2 released for Win
Date:   Mon, 27 Mar 2017 22:30:19 +0100
From:   Miguel Veiga <miguel.v...@gmail.com>
To: Kathryn Marks <kathryn.bo...@gmail.com>
CC: 	David Anderson <da...@ssl.berkeley.edu>, BOINC Alpha list 
<boinc_al...@ssl.berkeley.edu>




David, dont forget to update the translations into this new build

<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> 
	Sem vírus. www.avast.com 
<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> 




2017-03-27 21:55 GMT+01:00 Kathryn Marks <kathryn.bo...@gmail.com 
<mailto:kathryn.bo...@gmail.com>>:


   I think he wants support for XP dropped.

   On Mon, Mar 27, 2017 at 4:17 PM, David Anderson <da...@ssl.berkeley.edu
   <mailto:da...@ssl.berkeley.edu>>
   wrote:

> I don't understand what you're requesting.
> -- David
>
>
> On 3/27/2017 2:42 AM, bobo...@libero.it <mailto:bobo...@libero.it> wrote:
>
>> Ok, i try 7.7.2 on Window Xp 32bit SP3
>> It runs.
>> Stop this support, please.
>>
>>
>> Messaggio originale
>>> Da: "David Anderson" <da...@ssl.berkeley.edu 
<mailto:da...@ssl.berkeley.edu>>
>>> Data: 26/03/2017 8.59
>>> A: "BOINC Alpha list"<boinc_al...@ssl.berkeley.edu
   <mailto:boinc_al...@ssl.berkeley.edu>>, "BOINC Developers
>>>
>> Mailing List"<boinc_dev@ssl.berkeley.edu 
<mailto:boinc_dev@ssl.berkeley.edu>>
>>
>>> Ogg: [boinc_alpha] BOINC 7.7.2 released for Win
>>>
>>> I released a new version of the client for Win.
>>> Changes:
>>>
>>> - An accumulation of enhancement/fixes in the manager and client since
>>> June
>>>
>> 2016.
>>
>>> - The Vbox versions include VBox 5.1.18
>>> - not code-signed (I didn't have the $200 needed to renew the
>>> certificate).
>>> - built by me rather than Rom (hopefully I did it right).
>>>
>>> Please give it a try.
>>> Alpha testers can report bugs here:
>>> http://boinc.berkeley.edu/alpha/test_form.php
   <http://boinc.berkeley.edu/alpha/test_form.php>
>>>
>>> -- David
>>> ___
>>> boinc_alpha mailing list
>>> boinc_al...@ssl.berkeley.edu <mailto:boinc_al...@ssl.berkeley.edu>
>>> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
   <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 <mailto:boinc_al...@ssl.berkeley.edu>
> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
   <https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha>
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.
>



   --
   ~Kathryn
   ___
   boinc_alpha mailing list
   boinc_al...@ssl.berkeley.edu <mailto:boinc_al...@ssl.berkeley.edu>
   https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
   <https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha>
   To unsubscribe, visit the above URL and
   (near bottom of page) enter your email address.




--
Carpe Diem
___
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] Vbox and OpenSSL versions

[David Anderson]

I did a release with vbox 5.1.18.

I didn't update OpenSSL; does someone want to do this?
Instructions are here:
http://boinc.berkeley.edu/trac/wiki/AdminDepLibs

-- David

On 3/19/2017 5:01 PM, Mark James wrote:

Seeing as we're discussing Vbox, they have released 5.1.18. The .16 didn't last 
long.

Also I understand OpenSSL 1.0.x versions are unsupported so can we get onto 
1.1.x

Cheers
MarkJ
___
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.

[boinc_dev] BOINC 7.7.2 released for Win

[David Anderson]

I released a new version of the client for Win.
Changes:

- An accumulation of enhancement/fixes in the manager and client since June 
2016.
- The Vbox versions include VBox 5.1.18
- not code-signed (I didn't have the $200 needed to renew the certificate).
- built by me rather than Rom (hopefully I did it right).

Please give it a try.
Alpha testers can report bugs here:
http://boinc.berkeley.edu/alpha/test_form.php

-- David
___
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 Account Manager & Password Keys

[David Anderson]

Good point!
I changed the client so that it reports the account key only for
projects attached using the account manager.
-- David

On 3/16/2017 10:06 AM, Brian wrote:

Hi,

I am working on a research pool for Gridcoin. Part of this development involves an 
account management piece to the site. During the development of the account 
manager, I noticed when BOINC client makes an account manager request to my 
server, it passes all projects that are attached to it into the account manager 
regardless of what attached it. This data includes the password keys to the 
projects which are not currently attached to my account manager. It appears I 
could take these account keys to gain access to individuals accounts for those 
projects.


Just mostly an observation, not sure if this has been discussed or not...

Thanks for your time,

Brian Burkhardt...

___
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 running project memory overload

[David Anderson]

This will be fixed in the next client release,
which I hope to put into testing shortly.
-- David

On 3/14/2017 12:28 PM, Paul Haneline wrote:

BOING is running too many projects at one time that needs lots of memory.

ATLAS needed 2 Gigs of ram and BOING decide to run 10 totaling 20 Gigs.

LHCb needed 2 Gigs each and ran 8 work units totaling 16 Gigs not even
leaving room for OS and other programs running in the background.

TLP needs according to Task Manger at least 7 Gigs of RAM to run and BOINC
decided to run 12 totaling *120 Gigs or RAM.*

*I left Task Manger running and when I came to my computer the last thing I
see on Task Manger is full ram every time and computer was frozen and
sometimes hearing my Hard Drive heads thrash for swap files.*

I had BOINC running for years without porblems and when it decided to run
large work units it over fills my ram. I shouldn't have to do any changing
to BOINC settings or go into the BOINC folder and edit anything. BOINC is a
program to *"Set it and forget it"* it did for years until now.

Eather BOINC is ignoring MAX RAM installed, NON-BOINC work in the
background and/or how much each work unit needs before it starts the
projects.

BOINC 7.6.33
CPU 12 core, *16 RAM.*
___
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] Windows 10 installation options changing...

[David Anderson]

I added a github issue for this:
https://github.com/BOINC/boinc/issues/1804

If anyone wants to investigate, that would be great.

-- David

On 3/6/2017 12:05 PM, David Anderson wrote:

According to this CreateProcess() is available in UWP:
https://social.msdn.microsoft.com/Forums/en-US/537da783-f8af-4ce4-853e-d68bd97e2e88/uwpdesktop-bridgecreateprocess-not-working?forum=wpdevelop

-- David

On 3/1/2017 12:15 PM, Rom Walton wrote:


It still looks like it is missing:

https://msdn.microsoft.com/en-us/library/windows/apps/mt644399.aspx#_api-ms-win-core-processenvironment-l1-2-0.dll

- Rom

*From:*Rom Walton
*Sent:* Wednesday, March 1, 2017 12:13 PM
*To:* 'David Anderson' <da...@ssl.berkeley.edu>; Jord van der Elst 
<els...@gmail.com>
*Subject:* RE: Windows 10 installation options changing...

As of the last time I went looking…  CreateProcess() was not an API that was 
exposed to applications in the sandboxed environment app store applications run in.


- Rom

*From:*David Anderson [mailto:da...@ssl.berkeley.edu]
*Sent:* Wednesday, March 1, 2017 12:06 PM
*To:* Jord van der Elst <els...@gmail.com <mailto:els...@gmail.com>>
*Cc:* Rom Walton <r...@romwnet.org <mailto:r...@romwnet.org>>
*Subject:* Re: Windows 10 installation options changing...

Why do you think it would be hard to add BOINC to the MS Store?
It looks potentially easy:
https://docs.microsoft.com/en-us/windows/uwp/porting/desktop-to-uwp-root

On 3/1/2017 9:44 AM, Jord van der Elst wrote:

Hi David,

With the upcoming Creators Edition of Windows 10, how people can install
applications is going to change. There are going to be three options, with
the first default on for now:

1. Install apps from anywhere.

2. Install apps from anywhere but warn me about that and where possible 
point
out similar apps from the Microsoft Store.

3. Install only apps from the Microsoft Store.

Thoughts are that MS will eventually set the third option as default and for
users to be completely with their hands in their hair if they want to 
install
something else.

I doubt BOINC can be added to the MS Store, but this is probably something
you'll want to look into.


https://blogs.windows.com/windowsexperience/2017/02/28/announcing-windows-10-insider-preview-build-15046-pc/#UTxOfzBp9rjJegw9.97


Cheers.


-- Jord van der Elst.





___
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] Windows 10 installation options changing...

[David Anderson]

According to this CreateProcess() is available in UWP:
https://social.msdn.microsoft.com/Forums/en-US/537da783-f8af-4ce4-853e-d68bd97e2e88/uwpdesktop-bridgecreateprocess-not-working?forum=wpdevelop

-- David

On 3/1/2017 12:15 PM, Rom Walton wrote:


It still looks like it is missing:

https://msdn.microsoft.com/en-us/library/windows/apps/mt644399.aspx#_api-ms-win-core-processenvironment-l1-2-0.dll

- Rom

*From:*Rom Walton
*Sent:* Wednesday, March 1, 2017 12:13 PM
*To:* 'David Anderson' <da...@ssl.berkeley.edu>; Jord van der Elst 
<els...@gmail.com>
*Subject:* RE: Windows 10 installation options changing...

As of the last time I went looking…  CreateProcess() was not an API that was 
exposed to applications in the sandboxed environment app store applications run in.


- Rom

*From:*David Anderson [mailto:da...@ssl.berkeley.edu]
*Sent:* Wednesday, March 1, 2017 12:06 PM
*To:* Jord van der Elst <els...@gmail.com <mailto:els...@gmail.com>>
*Cc:* Rom Walton <r...@romwnet.org <mailto:r...@romwnet.org>>
*Subject:* Re: Windows 10 installation options changing...

Why do you think it would be hard to add BOINC to the MS Store?
It looks potentially easy:
https://docs.microsoft.com/en-us/windows/uwp/porting/desktop-to-uwp-root

On 3/1/2017 9:44 AM, Jord van der Elst wrote:

Hi David,

With the upcoming Creators Edition of Windows 10, how people can install
applications is going to change. There are going to be three options, with 
the
first default on for now:

1. Install apps from anywhere.

2. Install apps from anywhere but warn me about that and where possible 
point
out similar apps from the Microsoft Store.

3. Install only apps from the Microsoft Store.

Thoughts are that MS will eventually set the third option as default and for
users to be completely with their hands in their hair if they want to 
install
something else.

I doubt BOINC can be added to the MS Store, but this is probably something
you'll want to look into.


https://blogs.windows.com/windowsexperience/2017/02/28/announcing-windows-10-insider-preview-build-15046-pc/#UTxOfzBp9rjJegw9.97


Cheers.


-- Jord van der Elst.



___
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 sourcecode license ambiguity

[David Anderson]

I changed COPYING back to the GPL license.
-- David

On 3/6/2017 8:02 AM, Nicolás Alvarez wrote:

2017-03-06 4:47 GMT-03:00 Christian Beer :

Hi David,

on Aug 6 2008 you changed the file COPYING in BOINC
(https://github.com/BOINC/boinc/commit/9baf78fe5f5deb3c4f642842a1ef29cfc0cb2348).
This file now contains the text of the GPL while COPYING.LESSER contains
the text of the LGPL. This makes it ambiguous under what license BOINC
is. Could you please clarify why COPYING contains the GPL instead of
LGPL and maybe correct that?

This is because the LGPLv3 is written as supplemental clauses on top
of GPLv3. The text of the LGPLv3 alone is not a complete license.
"This version of the GNU Lesser General Public License incorporates
the terms and conditions of version 3 of the GNU General Public
License, supplemented by the additional permissions listed below."

And from the howto https://www.gnu.org/licenses/gpl-howto.html:
"If you are releasing your program under the LGPL, you should also
include the text version of the LGPL, usually in a file called
COPYING.LESSER. Please note that, since the LGPL is a set of
additional permissions on top of the GPL, it's important to include
both licenses so users have all the materials they need to understand
their rights."



___
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] Definition of 'md5' column in 'job_file' table missing from schema.sql

[David Anderson]

Oops!  Fixed now.
-- David

On 3/6/2017 7:58 AM, Andy Bowery wrote:

Hi,

The definition of the column 'md5' in the 'job_file' table is missing in 
db/schema.sql. This conflicts with the line in db/constraints.sql:

alter table job_file
 add unique jf_md5(md5);

This results in the following error message when running the 'make_project' 
script:

"Key column 'md5' doesn't exist in table"

With regards,

Andy


[X]
Oxford e-Research Centre
University of Oxford
7 Keble Road, Oxford, OX1 3QG
Tel: +44(0)1865 610600
www.oerc.ox.ac.uk
  [X]     [X] 
  [X] 

___
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 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 sourcecode license ambiguity

[David Anderson]

error; I fixed it.
-- D

On 3/5/2017 11:47 PM, Christian Beer wrote:

Hi David,

on Aug 6 2008 you changed the file COPYING in BOINC
(https://github.com/BOINC/boinc/commit/9baf78fe5f5deb3c4f642842a1ef29cfc0cb2348).
This file now contains the text of the GPL while COPYING.LESSER contains
the text of the LGPL. This makes it ambiguous under what license BOINC
is. Could you please clarify why COPYING contains the GPL instead of
LGPL and maybe correct that?

Regards
Christian



___
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] BOINC workshop 2017

[David Anderson]

Right now we're trying to assess whether there is sufficient interest
to merit holding a workshop.
If there is, I'll poll to find a time and place that works for the most people.
-- David

On 3/2/2017 2:58 PM, David Wallom wrote:

Hi David,

We (CPDN) would also support a date in July but would prefer if we could 
arrange this through an organising committee drawn from the community . Could 
we have a skype call or similar open to all to discuss?

David

From: boinc_projects [boinc_projects-boun...@ssl.berkeley.edu] on behalf of 
David Anderson [da...@ssl.berkeley.edu]
Sent: 02 March 2017 22:34
To: Boinc Projects; BOINC Developers Mailing List
Subject: [boinc_projects] BOINC workshop 2017

The responses so far to my query about workshop dates/places:

David Anderson: any date or place
Filip Rydio: prefer 19-20 June, Paris
Rytis Slatkevicius: prefer 19-20 June; later months difficult
Marius Millea: prefer Paris
David Wallom/CPDN: only 12-13 June; either Geneva or Paris
Vitalii Koshura: any date or place

expressed interest earlier but didn't give time/place prefs:
Laurence Field, Nils Hoimyr (CERN)
Steffen Moller
Valter Cavecchia

Can't attend:
Luke Wilson, TACC
Travis Desell: can't attend until end of July

Based on this, I don't think we have the critical mass for a workshop in June;
if anyone is interested but hasn't responded yet, please do so ASAP.

Alternatives:

1) people who are interested in using Docker (for app deployment and/or server)
could set up a smaller meeting with Marius in Paris.

2) we could try again later in the year, like Sept or Oct.
perhaps my new collaborators at Purdue and TACC will be available then.

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


___
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] BOINC workshop 2017

[David Anderson]

The responses so far to my query about workshop dates/places:

David Anderson: any date or place
Filip Rydio: prefer 19-20 June, Paris
Rytis Slatkevicius: prefer 19-20 June; later months difficult
Marius Millea: prefer Paris
David Wallom/CPDN: only 12-13 June; either Geneva or Paris
Vitalii Koshura: any date or place

expressed interest earlier but didn't give time/place prefs:
Laurence Field, Nils Hoimyr (CERN)
Steffen Moller
Valter Cavecchia

Can't attend:
Luke Wilson, TACC
Travis Desell: can't attend until end of July

Based on this, I don't think we have the critical mass for a workshop in June;
if anyone is interested but hasn't responded yet, please do so ASAP.

Alternatives:

1) people who are interested in using Docker (for app deployment and/or server)
could set up a smaller meeting with Marius in Paris.

2) we could try again later in the year, like Sept or Oct.
perhaps my new collaborators at Purdue and TACC will be available then.

-- David
___
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] BOINC Workshop

[David Anderson]

I've been dragging my feet about a potential BOINC workshop because my funding 
situation
is uncertain, and it's not sure that I can go.
However, it might be good to have a workshop even if I can't attend; there's always 
Skype.


So far there have been generous offers to host the workshop at
- Zaragoza
- Trento, Italy
- Geneva (CERN)
- Paris

I'd like any of these; I'd lean toward Paris because it's cheaper to get to,
and Marius Millea is there, whose work with Docker is important to all of us.

As for dates, I propose either

12-13 June (mon/tues) or
19-20 June (mon/tues).
(I'd stay for the rest of the week, and would welcome those who want to talk and/or 
hack).


---

So. if you're potentially interested in attending a BOINC workshop, please let 
me know ASAP

- what location you prefer
- what date you prefer (or if you have a conflict with both, suggest other 
dates)

... and I'll tabulate the results and make a decision so that we can all start 
planning.

Thanks -- David
___
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_cvs] [BOINC/boinc] c2350c: web: try to get Recaptcha working on IE

[David Anderson]

I saw the same problem on WinXP/IE11.  Fixed now.
-- D

On 2/2/2017 2:29 PM, Jord van der Elst wrote:

The report was done via
https://setiathome.berkeley.edu/forum_thread.php?id=80955
I did ask the user if it truly was IE, seeing how he's using Windows 10. It
may have been Edge. No reply on that though.
But in that case it would be IE 11. Or Edge.


-- Jord van der Elst.

On Thu, Feb 2, 2017 at 8:43 PM, Christian Beer <christian.b...@aei.mpg.de>
wrote:


Quoting my own email for the other commit that actually adds the parameter:

Again, which problem is this trying to fix? Is there a report? The used
parameter is not listed as a supported one. See:
https://developers.google.com/recaptcha/docs/display

If the parameter is not supported this is not a fix. It's most likely
breaking again soon. I also don't see a difference when requesting the
script with "?ver=2" added (through wget with a faked user agent). Also
what version of IE are we talking about? Is this workaround mentioned
somewhere else? Why doesn't the official implementation mention this?

Regards
Christian


On 02.02.2017 20:29, David Anderson wrote:

html/inc/recaptchalib.php

https://www.google.com/recaptcha/api.js?ver=2&quot</a>; async
defer>

added ?ver=2

On 2/2/2017 2:53 AM, Christian Beer wrote:

So the extra linebreak after the script line fixes this? I don't see any
other change that affects how the page is rendered. As it is now the
commit message is misleading.

Regards
Christian

On 02.02.2017 11:36, David Anderson wrote:

recaptcha didn't work on IE

On 2/2/2017 12:00 AM, Christian Beer wrote:

On 02.02.2017 07:13, GitHub wrote:

 Branch: refs/heads/master
 Home:   https://github.com/BOINC/boinc
 Commit: c2350c7f5747dc3109d7a33aa2f12a3161258fda

https://github.com/BOINC/boinc/commit/c2350c7f5747dc3109d7a33aa2f12a

3161258fda

 Author: David Anderson <da...@ssl.berkeley.edu>
 Date:   2017-02-01 (Wed, 01 Feb 2017)

 Changed paths:
   M html/inc/account.inc
   M html/inc/recaptchalib.php
   M html/inc/util.inc

 Log Message:
 ---
 web: try to get Recaptcha working on IE

I don't see how this commit fixes anything that is related to a
specific
problem with Internet Explorer. Is there a bug report?

Regards
Christian

___
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 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 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 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 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 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 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_cvs] [BOINC/boinc] c2350c: web: try to get Recaptcha working on IE

[David Anderson]

html/inc/recaptchalib.php

https://www.google.com/recaptcha/api.js?ver=2&quot</a>; async 
defer>

added ?ver=2

On 2/2/2017 2:53 AM, Christian Beer wrote:

So the extra linebreak after the script line fixes this? I don't see any
other change that affects how the page is rendered. As it is now the
commit message is misleading.

Regards
Christian

On 02.02.2017 11:36, David Anderson wrote:

recaptcha didn't work on IE

On 2/2/2017 12:00 AM, Christian Beer wrote:

On 02.02.2017 07:13, GitHub wrote:

Branch: refs/heads/master
Home:   https://github.com/BOINC/boinc
Commit: c2350c7f5747dc3109d7a33aa2f12a3161258fda
   
https://github.com/BOINC/boinc/commit/c2350c7f5747dc3109d7a33aa2f12a3161258fda

Author: David Anderson <da...@ssl.berkeley.edu>
Date:   2017-02-01 (Wed, 01 Feb 2017)

Changed paths:
  M html/inc/account.inc
  M html/inc/recaptchalib.php
  M html/inc/util.inc

Log Message:
---
web: try to get Recaptcha working on IE

I don't see how this commit fixes anything that is related to a specific
problem with Internet Explorer. Is there a bug report?

Regards
Christian

___
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 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 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 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] Input templates

[David Anderson]

I made two changes to the input template mechanism:

1) I got rid of the  and  elements.
The list of s now corresponds to the list of s
(i.e. the first  goes with the first , etc.)
If you have input templates where the lists are in different orders,
you'll need to reorder them.

2) I added support for "constant input files",
listed in the input template with a  specifying the file.
These files aren't included in the list of input files passed to create_work
or other job-submission APIs.
This supports the nanoHUB use case, where Docker layers are input files
but the job submitter doesn't know about them.

This is described here:
http://boinc.berkeley.edu/trac/wiki/JobTemplates

I've tested all the various cases, but I may have missed something.
Let me know if any problems.

-- David
___
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] http://boinc.berkeley.edu/ is down

[David Anderson]

For about a month, the server has sporadically become extremely slow for web 
access,
usually for an hour or two.
Today was slow all day long.
Our sysadmins are investigating.
It's mysterious.
The load average is normal, and the rate of HTTP requests is normal.
Hopefully we'll fix it soon.
-- David

On 1/9/2017 1:02 AM, Vitalii Koshura wrote:

Hello everyone,

http://boinc.berkeley.edu/ is down. Is this OK or smth happened?

Thanks

Best regards,
Vitalii Koshura
___
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 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] Question: BOINC client: remote DNS via configured socks5 proxy

[David Anderson]

I added this feature and it will appear in 7.7
-- David

On 10-Oct-2016 8:07 AM, Łukasz Świerczewski wrote:

Hello,

I have a question.

Does BOINC client with configured socks5 proxy can use remote DNS via
configured proxy?

I mean something like: "network.proxy.socks_remote_dns" as true in Mozilla
Firefox when we want the broweser to use DNS proxy.

Is it implemented in BOINC client if yes from which version?

Best Regards
Lukasz Swierczewski
___
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 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...

[David Anderson]

It's OK in this case because it's in the scheduler, which runs a limited number of 
times then exits.

It's not OK in the client.

On 1/3/2017 7:34 AM, Christian Beer wrote:

As for memory leaks occurring in BOINC I'd like to quote
sched/sched_version.cpp line 515:

// This is a memory leak, but that's OK




___
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.