Mailman 3 October 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

Github contributors with commit rights: Future working model to assure code quality?
by BiT dev 30 Oct '22

30 Oct '22

Dear bit-team members, I have received commit right by Germar (THX!) and just pushed my first direct commit (just changing the README file). This brings up the question of how we collaborate in the future to assure code quality. At least I must admit that "night shifts" do not always lead to correct and "error-free" solutions in my code ;-) I suggest: 1. Documentation-only commits can be pushed directly 2. Code changes shall be send via PR to establish a 4-eyes principle ("review"): - Apply the "approve" workflow in PRs - Review comments are used for discussions and feed-back - A PR can be merged by an bit-team member (even by the PR opener) if - all changes are approved - discussions have stabilized without an explicit "merge veto" - In case of controverse "merge veto's" we need a way to solve this in a constructive way eg. (@emtiu as "esacalation instance" or a democratic vote)

2 1

FYI: I have added a new label "Wayland"
by BiT dev 30 Oct '22

30 Oct '22

... to the "backintime" repo to tag issues that occur on Wayland since I have already seen several bugs with wayland (icon etc.). Used for the first time to tag this issue: https://github.com/bit-team/backintime/issues/1349

2 1

Warning about Udev and DBus
by c.buhtz＠posteo.jp 29 Oct '22

29 Oct '22

Moin, from time to time I see warnings like this Failed to connect to Udev serviceHelper daemon via D-Bus: org.freedesktop.DBus.Error.ServiceUnknown I can reproduce it in a VM with a fresh Debian testing and BIT from upstream master repo. Which package is might be missing here? This is the full terminal output user@Barclay ~/backintime/common (master)$ ./backintime Back In Time Version: 1.3.2 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. WARNING: Failed to connect to Udev serviceHelper daemon via D-Bus: org.freedesktop.DBus.Error.ServiceUnknown WARNING: D-Bus message: The name net.launchpad.backintime.serviceHelper was not provided by any .service files WARNING: Udev-based profiles cannot be changed or checked due to Udev serviceHelper connection failure

3 7

Travis CI says: Owner bit-team does not have enough credits
by BiT dev 26 Oct '22

26 Oct '22

I always wanted to say these words: We push to much ;-) https://app.travis-ci.com/github/bit-team/backintime/requests I don't know the billing schema of Travis CI but perhaps we can reduce the build by focusing on certain branches and events... @Michael: Do you have the login credentials for Travis CI to check this? Or: We find a decicated sponsor...

3 3

Definition Of GPU – Features, Specifications, Size & More
by mileseli9＠gmail.com 25 Oct '22

25 Oct '22

Definition Of GPU GPU is the acronym for Graphics Processing Unit and represents exactly the coronary heart of a snap shots card, much like the CPU does in a PC. Apart from the heart, your mind is likewise in price of carrying out all of the complex calculations that allow us to enjoy our video games on the display. Usually it is the piece of silicon that had both AMD and NVIDIA or Intel manufacture( in which the transistors are recorded). To put it generally, it's miles the so-called pics card chip. This idea is crucial from the factor of view of utility when you consider that, as we've got referred to, a GPU isn't a graphics card in itself. On the opposite hand, a pix card does integrate a GPU under its belt. In addition, it desires a PCB, resistors, SMDs, capacitors, voltage drivers, phase regulators, VRAM, display outputs, and extra. Main Features And Specifications A GPU is based on a silicon chip that is a series of tens of millions of transistors under a selected structure and has committed capabilities for each model. The importance of the idea itself comes to us from APUs (as an instance) wherein in addition they residence a GPU, best they accomplish that on a far smaller substrate and hand in hand with a CPU. The Technical traits of a GPU depend on the specific version; it relies upon at the precise chip, so we will handiest generalize whilst speaking about the concept. The Average Size of a GPU The length of GPU is an awful lot large than a CPU die, and these days, it isn’t easy to get them below 100 mm2, even inside the maximum advanced lithographic procedures. It consists of a substrate size that is normally among three and 4 instances the place of the chip, in particular due to the quantity of factors linked to it. It is a very basic interposer to wire connections with the chip . GPU connects the bus, the VRAM, the manipulate alerts, voltages, and clocks with our protagonist. The maximum advanced GPU techniques is a vertical scaling known as 2.5D IC. It remains a separate unit and ought to be dealt with as such. Currently the design is being puzzled considering that soon we will be not able to speak about one GPU according to pictures card.@https://www.techiesstar.com/gpu/

1 0

Increase BiT version number now to indicate DEV status?
by BiT dev 24 Oct '22

24 Oct '22

Our VERSION file at Github currently indicates "1.3.2" https://github.com/bit-team/backintime/blob/master/VERSION but it differs from the code of git tag "v1.3.2" due to our further development. Also the dev version has still a hard-coded "version 1.3.2": https://github.com/bit-team/backintime/blob/4b09eba80237d64b84a3ed2c4aba1c4… In the CHANGES file we already call the HEAD of master "Upcoming Release" (without any version number). ============================================================================================= How about updating the version number in VERSION file and config.py now to "1.3.3_dev" or similar to make it easier for us to recognize if a reported issue is related to the released 1.3.2 or a dev version from Github? ============================================================================================= This makes at least supporting Arch Linux easier since their packages are quite often directly pulled from Git (using a tag, commit ID or nothing) and I need to know the source code base for debugging... Possible process for the future: For a final release - both version number locations must be updated again, the release created - and then immediately a new dev version number set (potentially on a new branch than master).

3 11

Working vagrant file for Arch Linux with a desktop (Xfce, KDE Plasma or Gnome)?
by BiT dev 22 Oct '22

22 Oct '22

Has anybody of you a working vagrant file for me to quickly setup Arch with a desktop? I want to check and fix some BiT issues and working on the cmd line ain't no fun for this but neither Plasma nor Xfce will work whatever I try. I can login but get a black screen after seeing a rotating gear for a few seconds. Guest extensions are installed... THX!

1 0

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