<feed xmlns='http://www.w3.org/2005/Atom'>
<title>soledad.git/client/changes/bug_fix-sync-enc-close-queue-error, branch release/bitmask-0.9.x-alpha</title>
<subtitle>[soledad]
</subtitle>
<link rel='alternate' type='text/html' href='https://leap.se/git/soledad.git/'/>
<entry>
<title>[bug] do not block when getting doc for async enc</title>
<updated>2015-06-03T19:07:50+00:00</updated>
<author>
<name>drebs</name>
<email>drebs@leap.se</email>
</author>
<published>2015-06-02T11:40:06+00:00</published>
<link rel='alternate' type='text/html' href='https://leap.se/git/soledad.git/commit/?id=36d3fe05282bbc586c52536962cebf636a9b499f'/>
<id>36d3fe05282bbc586c52536962cebf636a9b499f</id>
<content type='text'>
Previous to this change, the actual encryption method used to run on its own
thread. When the close method was called from another thread, the queue could
be deleted after the encryption method loop had started, but before the queue
was checked for new items.

By removing that thread and moving the encryption loop to the reactor, that
race condition should disappear.

Closes: #7088.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Previous to this change, the actual encryption method used to run on its own
thread. When the close method was called from another thread, the queue could
be deleted after the encryption method loop had started, but before the queue
was checked for new items.

By removing that thread and moving the encryption loop to the reactor, that
race condition should disappear.

Closes: #7088.
</pre>
</div>
</content>
</entry>
</feed>
