RecoverPy

• 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

• #1

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.

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.

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.

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.

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.

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.

Added a temporary tests suite covering most of recoverpy.
Also implemented Github Actions workflows.

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

• Maybe use poetry for version control.
• Implement any relevant new py_cui features.

The progress of grep is now displayed in the title of the search menu.
The progress tool is now an optional dependancy, if not installed recoverpy will still run but the grep progression will not be displayed.

Minor code changes have also been implemented:

• Most of the .format() has been converted to f-strings.
  This implies that recoverpy now only support python 3.6+. Which would have been the case anyway since py_cui will soon only support 3.6+ too.
• The message box appearing when a result file is saved now displays the file path and name.
• Recoverpy checks if progress is present on user system.

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

• Implement any relevant new py_cui features.

When selecting certain partitions in the first menu, an index error could be raised if it contained hyphens in its name.

Resolved Issues

Issue #6. Regex has been modified.

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

• Implement any relevant new py_cui features.

Parts of raw lsblk output fetching were modified to allow other types than part.

Resolved Issues

Issue #5. lvm parts were ignored due to an inline filter.

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

• Implement any relevant new py_cui features.

Switched from os.path to pathlib.

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

• Implement any relevant new py_cui features.

An error was raised on startup with terminal not supporting xterm 256 colours scheme. This is a terminal/curses related issue that should be fixed in all terminals by now but a quick hacky fix has been added. It verifies system TERM env variable and set it to xterm-256color if needed.

Resolved Issues

Issue #3

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

• Replace os.path by pathlib.
• Implement any relevant new py_cui features.

Modifications were made to the submodules import procedure that was currently causing problems with older Python versions.

Resolved Issues

Issue #2. Circular import related errors were occuring on older Python versions.

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

• Replace os.path by pathlib.
• Implement any relevant new py_cui features.

This first release marks the first fully working version of recoverpy.

The utility has been tested on different systems. UI and backend works the same way, and performances are acceptable.

Known Issues

Issue #1. Currently, only one bug has been noticed. It raises IndexError with mouse integration on text blocks. This bug is caused by py_cui and will be fixed in its next version (0.1.3).

Future plans

• Improve UX by including more py_cui features in UI.
• Speed up the search process. Maybe with better threading/processing implementation.