summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess2018-08-16 11:18:42 -0400
committerJoey Hess2018-08-16 11:18:42 -0400
commitb3878e8d28f15178ef39f13c2ba437fd593ef864 (patch)
treea4e7ae1b0180a0d7211a350d334b62b0d2ac15af
parentc9582ef73cf18ccd0c3c9a49e80416c2b1849a7d (diff)
response
-rw-r--r--doc/forum/Privdata_corrupted_when_spinning_from_macOS/comment_5_f12c57263372437edbcdfe89cd69b95d._comment17
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/forum/Privdata_corrupted_when_spinning_from_macOS/comment_5_f12c57263372437edbcdfe89cd69b95d._comment b/doc/forum/Privdata_corrupted_when_spinning_from_macOS/comment_5_f12c57263372437edbcdfe89cd69b95d._comment
new file mode 100644
index 00000000..51f25ecc
--- /dev/null
+++ b/doc/forum/Privdata_corrupted_when_spinning_from_macOS/comment_5_f12c57263372437edbcdfe89cd69b95d._comment
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 5"""
+ date="2018-08-16T15:12:58Z"
+ content="""
+Ah, good debugging!
+
+The code that runs on the remote side is Propellor.Spin.update,
+and it uses Propellor.Protocol.req which reads from stdin. So,
+I think that putting `hSetEncoding stdin utf8` in the update function
+may fix it for you.
+
+If so, the real fix will involve making propellor force utf8 on both sides
+of its protocol, because the spin might be run in some other locale too.
+(Or chainging to a binary protocol that doesn't suffer
+from encoding mismatch problems, if someone is ambitious!)
+"""]]