20241226 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) -
• Mario Melchor(@mario-nt) -
• Graeme Byrne(@grmbyrn) -

---

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 Demo

Issues:

• Disk usage is 94.4% on the live demo droplet torrust/torrust-demo#25 (increased droplet size)
  • Trying to reduce connection ID erroe requests:
    • Check UDP errors after increasing IP ban duration from 2 minutes to 1 hour torrust/torrust-demo#28
    • Increase cookie lifetime from 2 minutes to 2 hours to investigate clients behavior torrust/torrust-demo#29

After running experiments torrust/torrust-demo#28 and torrust/torrust-demo#29, I concluded some clients ignore the connections ID and send random data.

Opened new issues:

• Tracker uptime in newtrackon.com is too low (60.80%) torrust/torrust-demo#26
• Improve tracker performance by adjusting docker network configuration torrust/torrust-demo#27

Torrust Tracker

Issues:

• Sdterror output from tracing running tests torrust/torrust-tracker#1069
  • Override default response failed error response in logs from TraceLayer in tower-http torrust/torrust-tracker#1146
  • Write assertions for logged errors torrust/torrust-tracker#1150
    • Log assertions: add assertions for API log errors torrust/torrust-tracker#1152 (WIP)

I closed the issue torrust/torrust-tracker#1069 only hiding errors when you run tests without any arguments and showing tracing errors when you run them with option --nocapture. Then I opened a new issue (torrust/torrust-tracker#1150) to write assertions in tests for log errors).

PRs:

• New feature: capture recent logs for testing torrust/torrust-tracker#1148 superseded by New feature: capture recent logs for testing (rework) torrust/torrust-tracker#1149
• Fix missing logs for HTTP requests torrust/torrust-tracker#1153 (needed to implement Log assertions: add assertions for API log errors torrust/torrust-tracker#1152)

I tried to use the tracing-test crate to write log assertions, but It did not work because I could not add a new span (to identify logs with a unique scope) for all events emitted inside the tests. It's not easy to move the span between Tokyo tasks. I think we need to instrument all spawned tasks. It should be possible (I created this example). Still, I could not make it work without code, so I decided to identify the logs for assertions with unique IDs I specifically inject when I run the tests (the ways to inject the ID depends on the tests, for example, for HTTP requests we can use the request-id header).

Torrust Index GUI

Issues:

• ERROR 503 torrust/torrust-index-gui#680

Note: time spent on Torrust (21.5h)