Matthias Beyer 5202c5112a Add flag for _update() whether precense should be modified ... This is a bugfix for an very particular issue. Here's what happens: If we create() an FileLockEntry and then update() it, we are running into a problem because update() calls _update() which changes the precense status of a FileLockEntry. Because update() is _consuming_, the FileLockEntry gets drop()ed afterwards. This _again_ causes _update() to be called, but with a new presence status, which is not true in this moment (as the FileLockEntry is still borrowed, but we already marked it as present). This patch is a short-term fix. The real problem is, that our Store interface is consuming. If the Store interface would be non-consuming, this issue wouldn't happen, as the drop() call would not happen. I'm rather sure that this patch will not be reverted in the process of rewriting the Store interface to be non-consuming. But we never know.		2016-10-07 21:59:37 +02:00
..
hook	Export result-helper here	2016-09-06 15:31:55 +02:00
configuration.rs	Rewrite config validity checker to return Result<()>	2016-09-19 21:52:28 +02:00
error.rs	Rewrite config validity checker to return Result<()>	2016-09-19 21:52:28 +02:00
file_abstraction.rs	Fix: FileAbstraction::remove_file(): Add implementation	2016-09-21 10:20:16 +02:00
lib.rs	Rename lazyfile file to file_abstraction	2016-08-24 16:58:47 +02:00
store.rs	Add flag for _update() whether precense should be modified	2016-10-07 21:59:37 +02:00
storeid.rs	Remove StoreId::is_dir()	2016-09-08 15:05:25 +02:00