Change Log 5.8.3 - Revision history

Jord: adding date

2016-05-28T16:41:43Z

adding date

Jord: missed one

2016-05-28T15:06:13Z

missed one

Jord: normalizing, MGR for manager, client for core client etc.

2016-05-28T15:05:53Z

normalizing, MGR for manager, client for core client etc.

Jord: adding 5.8.3

2016-05-28T15:04:27Z

adding 5.8.3

New page

* manager: use user-friendly app names (fix to work w/ 5.4.11)
* MGR: Possble fix for the Simple GUI messages dialog?
* manager: don't prepend "(Activities suspended by user)" to result status. There is no longer a notion of "activities"
* MGR: Copy missing source file from HEAD branch for Frank Weiler's pie charts updates.
* MGR: Streamline the message dialog sync operation a little bit.
* core client: lots of debugging messages for cpu_sched (may remove later)
* Manager: check for ERR_DB_NOT_UNIQUE, not ERR_NONUNIQUE_EMAIL
* Update libCurl to 7.16.0 and use sync name resolves instead of async name resolves.
* core client: fix a bug that could cause computation to stop.
:• The problem: if we suspended a task by sending it a <quit/> message, we were changing its scheduler state to CPU_SCHED_PREEMPTED but not changing its task state (PROCESS_EXECUTING). If, for some reason, the process didn't exit right away, the scheduler would treat it as still running, since it builds its "currently running" list based on task_state.

:• Solution: the scheduler shouldn't be looking at task_state. Use scheduler_state instead. It's still a mystery why the app wasn't quitting.

← Older revision		Revision as of 16:41, 28 May 2016
Line 1:		Line 1:
		+	'''Date unknown, copied 25 March 2007'''
		+
	* MGR: use user-friendly app names (fix to work w/ 5.4.11)		* MGR: use user-friendly app names (fix to work w/ 5.4.11)
	* MGR: Possible fix for the Simple GUI messages dialog?		* MGR: Possible fix for the Simple GUI messages dialog?

@@ Line 5: / Line 5: @@
 * MGR: Streamline the message dialog sync operation a little bit.
 * client: lots of debugging messages for cpu_sched (may remove later)
-* Manager: check for ERR_DB_NOT_UNIQUE, not ERR_NONUNIQUE_EMAIL
+* MGR: check for ERR_DB_NOT_UNIQUE, not ERR_NONUNIQUE_EMAIL
 * Update libCurl to 7.16.0 and use sync name resolves instead of async name resolves.
 * client: fix a bug that could cause computation to stop.

@@ Line 1: / Line 1: @@
-* manager: use user-friendly app names (fix to work w/ 5.4.11)
+* MGR: use user-friendly app names (fix to work w/ 5.4.11)
-* MGR: Possble fix for the Simple GUI messages dialog?
+* MGR: Possible fix for the Simple GUI messages dialog?
-* manager: don't prepend "(Activities suspended by user)" to result status. There is no longer a notion of "activities"
+* MGR: don't prepend "(Activities suspended by user)" to result status. There is no longer a notion of "activities"
 * MGR: Copy missing source file from HEAD branch for Frank Weiler's pie charts updates.
 * MGR: Streamline the message dialog sync operation a little bit.
-* core client: lots of debugging messages for cpu_sched (may remove later)
+* client: lots of debugging messages for cpu_sched (may remove later)
 * Manager: check for ERR_DB_NOT_UNIQUE, not ERR_NONUNIQUE_EMAIL
 * Update libCurl to 7.16.0 and use sync name resolves instead of async name resolves.
-* core client: fix a bug that could cause computation to stop.
+* client: fix a bug that could cause computation to stop.
 :• The problem: if we suspended a task by sending it a <quit/> message, we were changing its scheduler state to CPU_SCHED_PREEMPTED but not changing its task state (PROCESS_EXECUTING). If, for some reason, the process didn't exit right away, the scheduler would treat it as still running, since it builds its "currently running" list based on task_state.
 :• Solution: the scheduler shouldn't be looking at task_state. Use scheduler_state instead. It's still a mystery why the app wasn't quitting.