You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for reaching to us. Yes, the tool tries the default location to place the .lock file. Nevertheless your instance should still run even on read-only file system. Is that the case? My understanding that you have database files in other than default directory and you are just concerned about this error message? The .lock mechanism was more designed for HPC system when several tool instances could trigger ETE3 library update and crush the server. Let us know more specifics please and will try to fix this minor issue in the next release
Nevertheless your instance should still run even on read-only file system. Is that the case?
Yes, and the creatiion of the lock ETE3_DB.lock breaks.
Ideally, I would suppress creating this lock file because we are not updating the ETE3 library while running mob_recon.
The issue is that ETE3 will trigger its own update if it detects there has been a change in the NCBI database. I have removed the locking mechanism from the new pending release but there is a risk to cascade multiple attempts to update the ncbi taxonomy database
The text was updated successfully, but these errors were encountered: