Custom Query (981 matches)

Custom preferences are ignored when the project that provided the web preferences is removed

Problem:
Removing the project where the web preferences came from, deletes the global_prefs.xml file, and BOINC then ignores the global_prefs_override.xml file, and uses stock-install preferences.

Expected behavior / Proposed changes:
1) Removing the project where the web preferences came from, should NOT delete global_prefs.xml (since contacting another project recreates it).
2) If global_prefs_override.xml exists, then it should be used for preferences, even if global_prefs.xml is missing

Test scenario / steps:

Project A: The Lattice Project
Project B: ralph@home
Project C: Einstein@Home
"global_prefs.xml" exists and is from Project A
"global_prefs_override.xml" exists and is being used
All 3 projects know about (are synchronized with) Project A's updated settings

Steps:
- Remove/Detach? Project B
"global_prefs.xml" exists and is from Project A
"global_prefs_override.xml" exists and is being used

- Remove/Detach? Project A
"global_prefs.xml" NO LONGER EXISTS
"global_prefs_override.xml" exists, but IS NOT USED
STOCK DEFAULT PREFERENCES are being used

- Contact Project C
"global_prefs.xml" gets re-created (with the note that it is actually from Project A)
"global_prefs_override.xml" is used again

As done by other BOINC Managers. E.g. while attaching ​http://boinc.ucd.ie/fmah/

the Android NDK (ie C/C++ libraries compiled for android) don't seem to provide much output on a crash (ie segfault etc). It seems that with the "Jelly Bean" Android (v 4.1) a lot of the facility for printing out a stack trace was removed. About the only avenue left is using the "CallStack?" class in the shared library (which seems to be in all Android distros/versions) -- libutils.so. Unfortunately, after figuring out how to use this class "CallStack?" -- the output is not very good, just one line printed with an unknown address and the calling program (not even the calling routine/function). I will attach my results to this ticket. I'm not sure if it's worth incorporating into BOINC (just a few lines in lib/diagnostics.cpp) since the output from Android is so poor.