-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
078bab7
commit b0390e0
Showing
2 changed files
with
23 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
--- | ||
sidebar_position: 6 | ||
sidebar_label: FAQ | ||
--- | ||
|
||
# FAQ | ||
|
||
## Pyra Shows a `filelock._error.Timeout` Exception | ||
|
||
In theory it is possible that Pyra encounters a deadlock when reading state or log files - although we have never encountered it yet. The error message will say something like this: | ||
|
||
``` | ||
filelock._error.Timeout: The file lock 'C:\Users\ga56fem\Downloads\pyra\pyra-4.0.6\config\.state.lock' could not be acquired. | ||
``` | ||
|
||
You can use the CLI command `pyra-cli remove-filelocks` to resolve that. | ||
|
||
```note | ||
We are using the python library `filelock` to enforce exclusive use of state- and log-files: There should not be two processes interacting with one of these files at the same time. This is necessary because we have at least 4 processes that work with these files: the CLI and the main-, upload- and helios-thread. | ||
``` |