Ablog isn't safe for parallel reading #297
Labels
Comments
|
I just marked it safe since I thought it was. |
liborjelinek
added a commit
to liborjelinek/ablog
that referenced
this issue
Nov 1, 2024
liborjelinek
added a commit
to liborjelinek/ablog
that referenced
this issue
Nov 1, 2024
liborjelinek
added a commit
to liborjelinek/ablog
that referenced
this issue
Nov 1, 2024
liborjelinek
added a commit
to liborjelinek/ablog
that referenced
this issue
Nov 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
It looks Ablog isn't safe for parallel reading (introduced in ad5665a).
But it's safe for parallel writing (4f9ae64).
Both changes are recent (summer this year) and made by @nabobalis :-) What lead you to these changes? :-)
I've add
-j autoto sphinx-build (use as many CPU cores as possible) recently and noticed Ablog doesn't detect any single post and allpostlistswere empty. With-j 1(use single core, default value) Ablog works again.It would be nice to fix it, but I am unsure about the reasons. As "workaround" I suggest change to
"parallel_read_safe": False, "parallel_write_safe": True.To Reproduce
No response
Screenshots
No response
System Details
No response
Installation method
No response
The text was updated successfully, but these errors were encountered: