There was a logic error that would cause every load of
the project page to initiate a web request to GPUgrid.
When GPUgrid was down, this could create lots of sockets,
which eventually would prevent incoming connections.
I think this is the reason for the sporadic slowdowns
of the BOINC web site.
Originally, the idea for remote file management was that
the physical name of a file was its md5, or jf_md5.
This was changed to let the submitter choose the name.
But in the DB (job_file.md5) we only kept 64 chars.
Change the field name to job_file.name, and change it to varchar(255)
This define was introduced to winternl.h on 2012-07-12 but I couldn't find out which version that corresponds to. At least version 2.0.1-1 of mingw-w64-dev in Ubuntu 12.04 LTS does not define it.
The hostname "localhost" was recognized as a special name which always prompted the Manager to try to read contents of gui_rpc_auth.cfg. The Manager used an empty password if the file is not readable but then can't connect because the Client actually uses a password. Any user supplied password was overwritten which made the dialog not work when using "localhost" but work when used with "127.0.0.1".
Now the dialog checks if the user has entered an empty password which prompts reading gui_rpc_auth.cfg and uses the user supplied password otherwise.
Fixes#1306
This adapts the header used in POT and PO exports from Drupal to what is currently used in BOINC. Some caveats:
- Project-Id-Version normally contains the SHA1 of the commit where the generic template was generated from but this is not available in Drupal. In the project-specific case I use the current date just so there is a value that can be used later on.
- POT-Creation-Date is always the same as PO-Revision-Date because Drupal internally does always use the latest strings when exporting languages (not relevant for BOINC-Drupal.pot)
We need to let users have https:// URLs.
Originally http:// was assumed, and the URLs were stored without the prefix.
For compatibility, allow either form to exist in the DB
Also update the "other account info" form to user bootstrap.
On IE11, pages using recaptcha (like profile edit)
weren't showing the recaptcha.
On reloading, it would appear.
Mysterious.
Anyway, removing the
'<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" >
fixed the problem.
David Anderson