-
-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed concurrent access to cache file #146
Conversation
This will fix my problem also. 👍 |
@CalebFenton @thomasperrot #144 might also address this issue. In my case I needed the lock to work across multiple non-communicating but local processes. I think this method should work for threads as well. |
marked as |
I thought that other PR was farther along, but turned out to be contentious and a breaking change. We can merge this one now and easily revert if #144 accomplishes the same. Thank you! |
Is there a way to suppress the tldextract.lock.json messages? I get it on stdout when I do multiprocessing. I am trying to selectively suppress messages on stdout (I have other log messages that I need to see on stdout). Here are the messages I get on stdout:
I tried contextlib, but still unable to suppress:
Any suggestions? |
You're not the only one. Check out tox-dev/filelock#59. Gives code how to manually restrict the log level just for that package. |
Thanks for the link! It suppresses the messages as I wanted to!!
…On Fri, Nov 6, 2020 at 1:10 PM John Kurkowski ***@***.***> wrote:
You're not the only one. Check out tox-dev/filelock#59
<tox-dev/filelock#59>. Gives code
how to manually restrict the log level just for that package.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#146 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHBR5N7QFLWBQ2WB526QCLSORC37ANCNFSM4EVBVJBA>
.
--
Thanks,
Srini. <http://csc.lsu.edu/%7Essrini1/>
|
An error occures when tldextract is used with multithreading. Some threads try to write the cache file while some threads try to read it. Putting a lock on the read/write operation fixed this issue.