20250116 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 Website

PR review: torrust/torrust-website#135

Torrust Tracker

Issues:

• Add more metrics torrust/torrust-tracker#1145 (See Add more metrics torrust/torrust-tracker#1176)
• Move logic to http-protocol and primitives packages torrust/torrust-tracker#1140
• Extract torrust-tracker-api-client workspace package torrust/torrust-tracker#1159
• Overhaul core Tracker: extract whitelist torrust/torrust-tracker#1182

New issues:

• Tracker Checker (UDP): add command to monitor uptime torrust/torrust-tracker#1178
• Overhaul core::Tracker torrust/torrust-tracker#1181 (EPIC)
  • Overhaul core Tracker: extract whitelist torrust/torrust-tracker#1182
  • Overhaul core Tracker: extract stats torrust/torrust-tracker#1184

I decided to start the core tracker overhaul because:

1. Writing E2E or unit tests for the new metrics added it's not easy. See Add more metrics torrust/torrust-tracker#1176. Specially the metrics that depends on time like the average request time.
2. The core tracker is too big and it's too coupled to everything and makes unit testing hard. That's something I was planning to do since more than one year ago.

And I guess now It's a good time to do it, before adding more functionality.

Torrust Demo

Issues:

• Deploy new tracker with new metrics and update Grafana dashboard torrust/torrust-demo#30
• Close non-used UDP ports torrust/torrust-demo#31

After deploying the new metrics and add them to the Grafana dashboard I could see that the announce processing time is low. Therefore I guess the low newtrackon uptime is a problem of bandwidth and not a problem of processing time on the server.

The average announce processing time:

See my comments here: torrust/torrust-demo#26 (comment)

While I was analyzing the new data I saw that there were a lot of packets received to unknown ports (1007279). So I decided to close non used UDP ports in the Digital Ocean firewall.

I also opened a new issue on the Tracker to investigate further why newtrackon uptime is so low. I'm planning to build a small UDP tracker monitor to collect data about: average response time including network, timeouts, etc. I want to confirm that the problem is only the server we are using for the demo does not have enough bandwidth.

Note: time spent on Torrust (14,5h)

[grmbyrn]

Torrust Website

• Updated dependencies in package.json and package-lock.json to ensure compatibility with the latest packages.
• Fixed issue with Markdown unordered lists not working as reported in Markdown unordered lists are not working torrust/torrust-website#126
• Fixed issue with links not having a special style in blog posts anymore as reported in Links don't have a special style in blog posts anymore torrust/torrust-website#127.
  • Fixed issue with selected text is not being highlighted as reported in Selected text is not highlithed torrust/torrust-website#132.
  • Adjusted styles in _markdown.scss and _typography.scss to improve text selection visibility.
    Modified TableOfContents.svelte to address the problem.
• Added highlight.js to the CodeBlock component for syntax highlighting of code snippets as reported in Improve code highlighter component? torrust/torrust-website#52 to improve the readability and appearance of code snippets within the component by leveraging syntax highlighting and indentation normalisation.

Nuxt

• https://www.youtube.com/playlist?list=PL8HkCX2C5h0XT3xWYn71TlsAAo0kizmVc

[mario-nt]

GUI

• Admins should be able to list users torrust/torrust-index-gui#658 (∼3h)
  • Issues encountered:
    1. Issue with imports not showing, I needed to use the local version of the API and Types libraries instead of the one found in the node_modules/ folder (Asked Jose how to fix it)
    2. Had to import the userProfile type manually from the Types lib (Repeating step 1 on API and Types libs)
    3. Types and API libs where using the npm version, had to link the local version so they applied the development changes (Repeating step 1 on API and Types libs)
    4. User tab was not showing the list of user profiles even though they could be seen in the response
  • Worked on:
    • New function wrapper for getting all user profiles from the API
    • Admin panel tab for listing users without styles
    • Understanding all the steps needed to get data from the index API to GUI and Types and API libraries

Index

• New API endpoint for listing users  torrust/torrust-index#796 (∼9h)
• • Issues encountered:
    1. E2E mysql tests failing, due to a snippet of unfinished code that was pushed by mistake (Fixed by copy/pasting the correct snippet of code from the develop branch
    2. API was not returning any data (fixed by add the missing user profiles listing endpoint to the v1 API - /users)
• Worked on:
  • Fixed Mysql E2E tests failing
  • Modified naming to make the code more self explanatory
  • Added new API endpoint for listing user profiles
  • Review the PR before marking it as pending for review

Other

• One to one with Constantin and Jose discussing my performance in the last few months, suggestions on how to improve and future plans and expectations from the company (∼30-40')

API and TYPES lib

• New API endpoint for listing users torrust/torrust-index-api-lib#49 (∼45')
  • Issues encountered:
    1. Mentioned on the GUI
• Worked on:
  • Adding the new type for the listing user profiles endpoint of the API
• Types for new API endpoint for listing users torrust/torrust-index-types-lib#28 (∼45')
  • Issues encountered:
  1. Mentioned on the GUI
• Worked on:
  • Adding the new type and functions for the listing user profiles endpoint of the API

Github

• Worked on opening new issues Admins should be able to list users torrust/torrust-index-gui#658 depends on to improve progress tracking: (∼45')
  • New API endpoint for listing users  torrust/torrust-index#796
  • New API endpoint for listing users torrust/torrust-index-api-lib#49
  • Types for new API endpoint for listing users torrust/torrust-index-types-lib#28

Next

• Finish Admins should be able to list users torrust/torrust-index-gui#658:
• Release new Types and API libs versions to NPM
• Add styles to admin panel for listing users
• Mark New API endpoint for listing users  torrust/torrust-index#796 as pending for review
• Continue working on similar issues from the same EPIC
• Possibly adding test for the new listing user profiles service