Mailman 3 September 2022 - Bit-dev

Skipped/empty test functions
by c.buhtz＠posteo.jp 06 Nov '22

06 Nov '22

Hello, I setup my localhost ssh to make all skipped tests run. But there are still 13 skipped tests. I checked and found out that they are simply not implemented. They looking like this: @unittest.skip('Not yet implemented') def test_rsyncPrefix(self): pass That's it. I would like to "transform" those tests to an Issue ticket about "not implemented tests". Just collect all such skipped and empty tests in an issue. And then deleted that code to make unittest run without errors, fails, warnings or skips. Beside that tests I also assume that there is much more untested code.

2 1

Docu: Code reference
by c.buhtz＠posteo.jp 06 Nov '22

06 Nov '22

Hello together, it seems that BIT does use Sphinx. I can see the reStructuredText in the codes docstrings. But I can't find the HTML docu generated from that docstrings. Not sure what the correct term is here for documentation that was generated out of docstrings: "Reference"? Does anyone know if there is such a docu? If not is anyone able to generate such a docu quick and dirty from the current main branch and can send it to me or somewhere else? It doesn't have to go into the official repo yet. It just would help me a lot to better understand the code and the structure of the project. I have used Sphinx a bit but I'm not quit familiar with it. And I won't touch Sphinx. ;) Btw: I am aware of the separate docu repo: https://github.com/bit-team/doc But it seems to me that this only is kind of a "User manual" and does not reference to the code. Kind Christian

4 6

Status report: Open Issues and Labels
by Michael Büker 22 Oct '22

22 Oct '22

Hi, everyone! I have some great news :) When this new team got started in June, the backintime repo had roughly: - 430 open Issues, of which there were - 250 unlabelled Issues Over the past ~three weeks, I've managed to whittle this down to: - 310 open Issues, of which there remain - 150 unlabelled Issues We currently have 20 Labels, all of which I created myself. That means that I've "touched" all of the 160 Issues that are currently open and labelled. This has given me a decent overview of current problems with the code, though obviously, there are still 150 Issues to go. If you'd like to help, some of the best ways are to: - check out unlabelled Issues and suggest labels / duplicates / resons to close / related Issues in a comment, - look at Issues marked "Bug" (but not "Reproduced"), and try to reproduce them, - look at Issues marked "Discuss" and see if you'd like to give an opinion, - look at Issues marked "High" and see if you can figure out what the hell is going on ;) I'm happy with the direction in which the project is moving. We have a lot in front of us, but it doesn't seem so impossible anymore :) Cheers! Michael

3 5

Issue statistic
by c.buhtz＠posteo.jp 03 Oct '22

03 Oct '22

Hello, I played a bit around with the Github API and build a little statistic about the Back In Time issues. https://codeberg.org/buhtz/spielwiese/src/branch/main/bit.md Maybe this is a nice eye catcher for Germar. :D The migration from Launchpad to Github is taken into account and the creation and closing dates of that Launchpad issues are integrated in the data I used. The creation_date was extracted from the first comment. And the close date was extracted directly from Launchpad. Good night Christian

3 5

Preferred docstring style for Sphinx?
by J. A. 02 Oct '22

02 Oct '22

Which docstring style do we use in Bit? Google or RST/Sphinx or anything else? See: https://www.sphinx-doc.org/en/master/usage/extensions/napoleon.html To get rid of all Sphinx warnings like "unexpected indentation" or "definition list ends without a blank line" when I doc-dev/make html if have to use indentations that make the docstrings hard to read in the code. And the Sphinx warnings are also somehow difficult to interpret or solve sometimes...

2 3

qt/test folder
by c.buhtz＠posteo.jp 29 Sep '22

29 Sep '22

Hi, can we have a test folder like "qt/test" as an equivalent to "common/test"? I tried to understand the configure files in "qt" and "common" but they are different. Bash scripts not my thing and very hard to read. I'm scared that I would mess up something. Background: I would like to have a "qt/test/test_qt.py" that only does an "import PyQt5" and doesn't raise an ImportError. This is in preparation of updating ".travis.yml". There where problems "installing" PyQt5 on ppc64le architecture. I'm sure I solved that problem. But to "fix the condition" I would like to add a qt-import-test that would fail if someone else in the future mess up the travis config. Kind Christian

2 3

Why environment variables und user-site packages ignored?
by c.buhtz＠posteo.jp 28 Sep '22

28 Sep '22

Hey folks, I was looking into "common/backintime" [1] a shell script that is also shiped via Debian and maybe with other distros, too. It just starts BIT with that line python3 -Es $APP_PATH/backintime.py "$@" The option "-E" make "Ignore environment variables like PYTHONPATH and PYTHONHOME". And "-s" make "Don't add user site directory to sys.path." Why does BIT use it that way? In practice this means that packages I installed via "pyhton3 -m pip install packaging" is not found by BIT. I have to do it via "sudo python3 -m pip". What is the advantage here? Does anyone has an idea or strong opinion about it? I can ask on the python mailing list what are the indications to do it that way. Kind Christian [1] -- <https://github.com/bit-team/backintime/blob/master/common/backintime>

2 1

Understand pid-files and flock in context of BIT
by c.buhtz＠posteo.jp 27 Sep '22

27 Sep '22

Good morning folks, I discovered "common/application_instance.py" and the class in it. I was wondering what it does. In my current state of investigation I would describe it as a "PID file and flock manager". I've never used PID files or flock in my own projects but I do understand the basics. I also found a good explanation [1] why PID and flock is used in combination. My problem is to understand that technology in the context of Back In Time. In which situation does Back In Time need it. Maybe someone else understand that better? Maybe I will dive deeper into the code and document my findings in the modules docstring. I want to understand in which situations PID and flock is used by BIT and why. Kind Christian [1] -- <https://unix.stackexchange.com/a/12816/136851>

2 2

Current FAQ
by c.buhtz＠posteo.jp 26 Sep '22

26 Sep '22

Hey Folks, maybe not everyone noted that and I was remember on that today. BIT still has a FAQ in the Wiki. https://github.com/bit-team/backintime/wiki/FAQ If someone like to work on that... I would prefer to have the FAQ in restructured text file "FAQ.md" an deactivate the Wiki. But this decision is not important today. Kind Christian

2 1

Do not talk about holidays
by c.buhtz＠posteo.jp 26 Sep '22

26 Sep '22

Hello Folks, please keep in mind that mailing list is archived and public now. Because of security reasons I would recommend not to talk about the status of your private and work life; e.g. holidays. This would have some security implications. In most situations I don't need to know if someone is off or not. If you would like to inform someone I would say write to the maintainers directly and private. Currently it is not officially clear who is the "activate maintainer". ;) Without pressure I would say if you really want to inform someone just write to Michael Büker. Kind Christian

1 0