summaryrefslogtreecommitdiff
path: root/history.txt
diff options
context:
space:
mode:
authorjmoenig <jens@moenig.org>2013-10-10 11:09:29 +0200
committerjmoenig <jens@moenig.org>2013-10-10 11:09:29 +0200
commit027388029f3a2b9e15b5552fce4cc01ea308feab (patch)
tree98444333c80d9f254be5e481dc91b3f78d253f51 /history.txt
parent24476a644e18b526f09dab730a09b88a6e501a5a (diff)
downloadsnap-027388029f3a2b9e15b5552fce4cc01ea308feab.tar.gz
snap-027388029f3a2b9e15b5552fce4cc01ea308feab.zip
"sanity check" for cloud-saving mechanism
errors if the serialized project data is corrupt and cannot be parsed as XML, addresses #203, #200, #171. I'm hoping that this might provide us a clue whether the corruption is happening in Snap's marshalling or on the backend side
Diffstat (limited to 'history.txt')
-rwxr-xr-xhistory.txt4
1 files changed, 4 insertions, 0 deletions
diff --git a/history.txt b/history.txt
index 4d26412..7452005 100755
--- a/history.txt
+++ b/history.txt
@@ -1950,3 +1950,7 @@ ______
131009
------
* Theads: added a variant for linked lists to the experimental MAP primitive reporter
+
+131010
+------
+* Cloud: added "sanity check" to cloud-saving mechanism that errors if the serialized project data is corrupt and cannot be parsed as XML, addresses #203, #200, #171