20241107 Weekly Development Meeting

[josecelano]

• Time: 9:30 in Canary Islands (WET (UTC+0)).
• Time: 10:30 in Vaduz (CET (UTC+1)).

Location:
https://meeting.blockfinance-eco.li/NautilusCyberneeringWeeklyDevMeeting

Expected duration: 2 to 4 hours with breaks

Communicated attendants:

• Cameron Garnham(@da2ce7) - x
• Jose Celano(@josecelano) - x
• Constantin Bosse(@cgbosse) - x
• Mario Melchor(@mario-nt) - x
• Graeme Byrne(@grmbyrn) - x

---

Agenda:

1. Everyone will take their turn and:

• Go over his notes added as comments for the meeting which will have been added in advance to give an update of all the work done during the previous week indicating.
  • The issues worked on
  • The progress made on them
  • Other things done
• Inform of any faced challenges and request help if necessary to work on specific issues.
• Highlight the encountered difficulties, especially if there is a risk of them causing delays or affecting end product's quality.
• Communicate what will be the next week's tasks.
• List any new topics for further discussion in an additional Technical meeting that he noted for future discussion in comments to this discussion either before the meeting or after his turn so that they get considered.

During the meeting every team member will take their turns and follow this sequence.
The topics for further discussion will be noted in advance by each the team member and to the meetings agenda.

2. At the end of the meeting if there any new technical topics to be discussed further it will be decided to
   set another meeting date for the discussion of these or to hold the meeting hereafter.

Also the persons to be part of the meeting will be decided on so that the others will be free to continue their own work.

[josecelano]

Torrust (14h)

Bittorrent Primitives

• Updated licence to use the same one we are using in the Bencode2Json package.

Bencode2Json

• Published version 0.1.0
• Someone on reddit gave me feedback and I opened an issue. There is no way to espace the <hex> tag we are using to identify byte sequences in the JSON. Therefore, there is no way to convert back to bencode deterministically. For example, if the encoded string is like this 11:<hex>ff</hex> (valid UTF-8), you would get this JSON string "<hex>ff</hex>" that does not come from the encoded string 1:\xFF.

Torrust Index

• Update dependencies torrust/torrust-index#757

Tracker

• Update dependencies torrust/torrust-tracker#1068
• Extract package bittorrent-tracker-client torrust/torrust-tracker#1067

4 months ago I was working on a new workflow to upload the code coverage to codecov:

https://github.com/josecelano-test/pull_request_target

There was an issue with the new version of the action (codecov/codecov-action@v4):

codecov/codecov-action#1508

They have made some changes in the backend. I wanted to try again but there has also been a change in Rust and I can't generate the code coverage. The Rust unstable flag profile was removed. There is no update for the action we are using alekitto/grcov@v0.2. I'm trying to generate the report without an action:

torrust/torrust-tracker#1075

The report looks fine locally and it's also uploaded to codecov on the sample project but codecov doesn't show any data. I'm waiting for their feedback but I'm considering simpler alternatives like publishing the HTML report to GitHub Pages. The problem is we would not have the report for PRs.

Community Support

I'm helping a torrust user to install it on a VM.

[mario-nt]

Index

• User context autorization tests torrust/torrust-index#759
• Proxy context authorization tests torrust/torrust-index#764

Other

• Renew expired GPG key