Releases: PabloLec/RecoverPy
1.5.1
1.5.0
What's new ?
-
The project structure has been refactored.
-
Test coverage has been greatly improved, currently 90%.
-
Binary file search has been improved, for you madlads that might do it.
Before, and because of how grep is used, a result was a line containing your searched string. The thing is, grep is expecting a newline character in order to consider this line over, which might not at all be present in a binary file.
That caused displayed results to be quite random for binary files, they might have been way too long and the given result block number, being calculated from grep output, was off by a few blocks.
Now this offset is taken into account, you will always see your searched string in the results and the associated partition block will always be precisely the one with your string in it. -
In order to fix old issues related to
py_cui
, RecoverPy now depends on its ownpy_cui
fork. Depending on how this upstream library is maintained in the future, it might or might not be permanent. -
Multiple UI related bugs were fixed, let's call it quality of life.
Known Issues
None 👍
Future plans
- Explore MacOS compatibility. See #8.
1.4.1
1.4.0
What's new ?
- An independent view has been added to edit configuration in order to avoid touching the raw yaml file. The view is accessible via a "Settings" button on first menu.
- Fix UI bugs appearing when going back from one view to another.
- Catch any missing system dependency at start up.
- Verify writing rights on saving and logging path.
- Python 3.10 compatibility is verified.
- Some overall refactoring.
- Better dev environment with falke8 plugins and pre-commit hooks.
- Better test suite.
Known Issues
2 issues are currently caused by py_cui
. They should be fixed with its next version.
- You may encounter
ValueError: embedded null character
when opening some partition blocks. py_cui #127 - Arrow keys navigation is currently broken in Settings menu. Mouse navigation works correctly. py_cui #151
Future plans
- Explore MacOS compatibility. See #8.
- Implement any relevant new
py_cui
features.
1.3.2
- Embedded null characters used to raise an error when displayed in a text box. This issue will be fixed in
py_cui
next update. Meanwhile, the null characters are escaped locally by RecoverPy. - User can no longer try to display a block with a number below zero.
- Keys handling was broken when going back from results saving window to search window. This is now fixed.
Resolved Issues
Known Issues
None
Future plans
- Explore MacOS compatibility. See #8.
- Create local docker environment for full test coverage.
- Implement any relevant new
py_cui
features.
1.3.1
New features:
- Results previews get matching searched text parts highlighted.
- Block inodes (useless for user) are removed from results lines.
- Progress used to hang just before reaching 100%. Fixed.
- Title bar gets colored at the end of search, red if no results, else, blue.
- Better popup messages and titles.
- User used to be able to save a block before selecting one, resulting in nonsense. Fixed.
- Some code refactoring.
- Adapted tests.
Resolved Issues
None
Known Issues
Issue #1. This mouse integration bug is still present with py_cui
v1.3.0, its fix should finally be implemented in v1.4.0
Future plans
- Explore MacOS compatibility. See #8.
- Create local docker environment for full test coverage.
- Implement any relevant new
py_cui
features.
1.3.0
Major project refactoring.
macOS version is yet to be done. Refer to #8 to give it a go.
Resolved Issues
None
Known Issues
Issue #1. This mouse integration bug is still present with py_cui
v1.3.0, its fix should finally be implemented in v1.4.0
Future plans
- If possible, make RecoverPy compatible with macOS.
- Create a testing environment with Docker to have a full test coverage.
- Implement any relevant new
py_cui
features.
1.2.2
Minor workflow fix.
Resolved Issues
None
Known Issues
Issue #1. This mouse integration bug is still present with py_cui
v1.3.0, its fix should finally be implemented in v1.4.0
Future plans
- Try to create a testing environment with Docker to have a full test coverage.
- Implement any relevant new
py_cui
features.
1.2.1
Minor workflow fix.
Resolved Issues
None
Known Issues
Issue #1. This mouse integration bug is still present with py_cui
v1.3.0, its fix should finally be implemented in v1.4.0
Future plans
- Try to create a testing environment with Docker to have a full test coverage.
- Implement any relevant new
py_cui
features.
1.2.0
The entire project has been refactored. Modules logic has changed a bit, for better separation and readability.
Some exception handling has also been added.
Switched from setup.py
to pyproject.toml
Finally, test coverage has been improved.
Resolved Issues
None
Known Issues
Issue #1. This mouse integration bug is still present with py_cui
v1.3.0, its fix should finally be implemented in v1.4.0
Future plans
- Try to create a testing environment with Docker to have a full test coverage.
- Implement any relevant new
py_cui
features.