20240418 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) -
• Jose Celano(@josecelano) - x
• Constantin Bosse(@cgbosse) - x
• Mario Melchor(@mario-nt) - x
• Graeme Byrne(@grmbyrn) - x
• Mick van Dijke(@mickvandijke) -
• Iván Santana(@ivan9989-pkj) - x
• Ismael Torrado(@Lepisma07) - x
• Borja (@BorjaPractica) - 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 Tracker

Refactor:

• Extract peer list in torrent repository entry. PR.
• Segregate command and query for announce request. PR

Performance:

I've been trying to improve the performance with small tasks. New torrent repository implementations:

• With a concurrent writes collection SkipMap. PR.
• With a HaspMap for the peer list instead of a BTreeMap: PR.
• With faster hash algorithms. FxHashMap for Peer List. PR.
• With faster locks. With parking_lot crate locks. PR

Ultimately, the performance was similar to what we have now, so I didn't change the default implementation.

Issues:

• Tracker API: Add a timeout to the TLS handshake, waiting for headers, and waiting for receiving headers torrust/torrust-tracker#612. I rechecked this issue to see if that problem was solved after migrating to Hyper 1.0. But it's not solved yet. I've created a new repo with the details of the problem: https://github.com/josecelano/axum-server-timeout
• Enable test should_fail_with_ssl_enabled_and_bad_ssl_config torrust/torrust-tracker#521. This is a refactor for the configuration that makes it easier to test configuration and allows failing earlier when the configuration is wrong. PR. Waiting for feedback from @da2ce7.

Torrust Index GUI

Discussions:

• Torrent completions and images torrust/torrust-index-gui#519

Issues:

Debugging error with canvas dependency in Mac OS 14.