Matthias Beyer cc11162dd4 Fix: In-Memory filesystem backend did not remove on rename ... The implementation of the in-memory filesystem for testing imag code did not actually use `HashMap::remove()` when an entry was moved, but `HashMap::get().cloned()`, which caused the original entry to exist _after_ the move. I'm not sure why this did not fail much earlier, but it was clearly wrong. This commit adjust the test to check the "filesystem" before checking the store and fixes the bug. Signed-off-by: Matthias Beyer <mail@beyermatthias.de>		2018-10-09 17:37:56 +02:00
..
core	Fix: In-Memory filesystem backend did not remove on rename	2018-10-09 17:37:56 +02:00
domain	Update dependency: filters: 0.2 -> 0.3	2018-10-06 12:22:15 +02:00
entry	Roll back mdcat update	2018-10-06 12:22:15 +02:00
etc	Fix: Do not pass --rtp in testing environment	2018-10-09 17:37:56 +02:00