20250130 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) -
• 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 Tracker

I have finished refactoring the core tracker (but there are still some tasks to complete the core tracker overhaul).

• Overhaul core Tracker: extract torrents context (part 1) torrust/torrust-tracker#1201
• Overhaul core Tracker: extract torrents context (part 2) torrust/torrust-tracker#1203
• Overhaul core Tracker: extract scrape handler torrust/torrust-tracker#1205
• Overhaul core Tracker: extract announce handler torrust/torrust-tracker#1207
• Overhaul core Tracker: remove deprecated core::Tracker torrust/torrust-tracker#1209
• Overhaul core Tracker: refactor tests torrust/torrust-tracker#1211
• Overhaul core Tracker: remove complexity (type_complexity) torrust/torrust-tracker#1215
• Overhaul core Tracker: create dependency containers for UDP tracker, HTTP tracker and Tracker API torrust/torrust-tracker#1217
• Overhaul core Tracker: reorganize code torrust/torrust-tracker#1221
• Overhaul core Tracker: extract workspace package for the tracker core lib torrust/torrust-tracker#1223

What I'm going to do next is to write unit tests for the new package, review crate docs, ...

The core mod before the refactor:

src/core/
├── auth.rs
├── databases
│   ├── driver.rs
│   ├── error.rs
│   ├── mod.rs
│   ├── mysql.rs
│   └── sqlite.rs
├── error.rs
├── mod.rs
├── peer_tests.rs
├── services
│   ├── mod.rs
│   ├── statistics
│   │   ├── mod.rs
│   │   └── setup.rs
│   └── torrent.rs
├── statistics
│   ├── event
│   │   ├── handler.rs
│   │   ├── listener.rs
│   │   ├── mod.rs
│   │   └── sender.rs
│   ├── keeper.rs
│   ├── metrics.rs
│   ├── mod.rs
│   └── repository.rs
└── torrent
    └── mod.rs

7 directories, 22 files

The core mod after the refactor:

src/core/
├── announce_handler.rs
├── authentication
│   ├── handler.rs
│   ├── key
│   │   ├── mod.rs
│   │   └── repository
│   │       ├── in_memory.rs
│   │       ├── mod.rs
│   │       └── persisted.rs
│   ├── mod.rs
│   └── service.rs
├── core_tests.rs
├── databases
│   ├── driver.rs
│   ├── error.rs
│   ├── mod.rs
│   ├── mysql.rs
│   ├── setup.rs
│   └── sqlite.rs
├── error.rs
├── mod.rs
├── peer_tests.rs
├── scrape_handler.rs
├── statistics
│   ├── event
│   │   ├── handler.rs
│   │   ├── listener.rs
│   │   ├── mod.rs
│   │   └── sender.rs
│   ├── keeper.rs
│   ├── metrics.rs
│   ├── mod.rs
│   ├── repository.rs
│   ├── services.rs
│   └── setup.rs
├── torrent
│   ├── manager.rs
│   ├── mod.rs
│   ├── repository
│   │   ├── in_memory.rs
│   │   ├── mod.rs
│   │   └── persisted.rs
│   └── services.rs
└── whitelist
    ├── authorization.rs
    ├── manager.rs
    ├── mod.rs
    ├── repository
    │   ├── in_memory.rs
    │   ├── mod.rs
    │   └── persisted.rs
    ├── setup.rs
    └── whitelist_tests.rs

11 directories, 43 files

Note: time spent on Torrust 28,5h.

[mario-nt]

GUI

• Admins should be able to search users torrust/torrust-index-gui#659

  • Worked on:

    • Adding search box
    • Styling the searchbox
    • Add magnifying glass icon to input text box (I will finish this in a different PR as it is a little bit out of the scope of this issue. Also will implement the same for the torrents search box)

  • Issues encountered:

  1. With a page size of 100 results, only 30 are shown

Index

• Add searching option to listing user profiles endpoint torrust/torrust-index#799
  • Worked on:
    • Adding search option param to get user profiles endpoint
• New API endpoint to reset user's passwords torrust/torrust-index#802
  • Worked on:
    • Added reset user password endpoint
    • Generate random password code
    • New mailer code with reset password emails
    • Send email with new password code
• Issues encountered:
  1. I wasn't sure about what to do when the password has been reset but sending the email to the user fails
  2. Took me a bit of time to write the code for resetting the password

API LIB

- https://github.com/torrust/torrust-index-api-lib/issues/51
  - Worked on:
    - [x] Adding search option param to get user profiles endpoint

New Issues

• Add searching option to listing user profiles endpoint torrust/torrust-index#799

[da2ce7]

@grmbyrn you still have not created a post for the work that you did the previous week. It would be good if you could post a link to the code of the Svelte-only experenent that you demonstrated in the meeting.

[da2ce7]

@grmbyrn In addition, I looked at the https://github.com/torrust/torrust-website/issues and found no epic or issue that tracks the progress and the results of the Svelte-only blog experiment.

[grmbyrn]

Website

• Continue with the epic for the Torrust website without Markdown.
• Try to use module='context' and +load.ts and have both options working.
• Write a presentation on which is better to use, as well as if they are better options than using Markdown for blogs.
• Install and apply Cypress e2e tests to website.

Cypress testing

• Learn about Cypress testing and how to implement it https://www.youtube.com/watch?v=u8vMu7viCm8&t=7870s&ab_channel=freeCodeCamp.org