Also, if you are taking the time to backport fixes to 0.9.x already, you
might want to send a PR to the 0.9.x branch on github, I'm happy to make
a new release then.
On 02.04.19 12:38, Filip Pytloun wrote:
Hello Jonas,
thank you for uploading this change.
You can push changes into Git and
advise you to skip those tests for now, as their failing
does not indicate a bug in khal, but a peculiarity in Debian's test
system.
Best regards,
Christian Geier
Quoting Guido Günther (2017-08-24 18:55:50)
> Hi,
> On Tue, Jul 18, 2017 at 03:41:33PM +0300, Adrian Bunk wrote:
> >
@Debian maintainers:
This has been fixed in master, the relevant commit is this:
https://github.com/pimutils/khal/commit/d756792adcf9b89186fbdba91c90a38d433f949c
I'm not going to backport any fixes that don't have data loss as a
consequence, but feel free to ping me if you need help.
Best
ersion.
>
>Filip
>
>On 2016/12/19 19:06, Christian Geier wrote:
>> Hi,
>> I could reproduce the issue and have fixed it, see the PR on github
>[1].
>> Depending on how urgent this is, you can either just take the
>os.sync()
>> commit and apply that to the
it
> for you, I'll apply it and make new release.
>
> Anyway wouldn't it better to ensure data is written to disk directly
> during db updates and other operations? Eg. use O_SYNC for safety as
> these operations doesn't happen so often.
>
> Filip
>
> On 2016/12/11 01:
Hi Filip,
could you perhaps try to change all those sleep()s to `os.sync()`? For
me it seems to fix the issue.
See [0] for a patch.
If this doesn fix the issue, we obviously need to move the sync call out
of the tests and into the db update.
Best regards,
Christian
[0]
Hi Filip,
could you perhaps run the attached file on the test machine (with
`py.test vdir_test.py`, py.test is needed for the creation of a temp
directory).
On my machine the output looks like this:
[(0, 10), (0.0001, 8), (0.001, 0), (0.01, 0), (0.1, 0), (1, 0)]
Similar experiments before made
and re-reading the mtime .
Best regards,
Christian Geier
8 matches
Mail list logo
