The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2023-07-19T15:58:34Zhttps://gitlab.torproject.org/tpo/core/arti/-/issues/958RetryError doesn't report error sources when used in the most obvious way2023-07-19T15:58:34ZIan Jacksoniwj@torproject.orgRetryError doesn't report error sources when used in the most obvious way`RetryError` expects to be provided with things that are `Display`. It then `Display`s as the inners' `Display`s.
But usually the innert things are errors. When they are errors, per EHWG policy, the `Display` impl is broken: it doesn'...`RetryError` expects to be provided with things that are `Display`. It then `Display`s as the inners' `Display`s.
But usually the innert things are errors. When they are errors, per EHWG policy, the `Display` impl is broken: it doesn't display the source.
### Consequences
This can result in bad log output, eg:
```
2023-07-14T16:00:58Z WARN tor_dirmgr::bootstrap: error while downloading: error: Problem downloading directory object: Error while getting a circuit: Tried to find or build a circuit 3 times, but all attempts failed
Attempt 1: Problem opening a channel to [scrubbed]
Attempt 2: Problem opening a channel to [scrubbed]
Attempt 3: Problem opening a channel to [scrubbed]
```
instead of
```
Attempt 1: Problem opening a channel to [scrubbed]: No plugin available for the transport obfs4
```
etc.
(In my current error handling test setup, this bug composes badly with #880 and the lack of !1229 )
### Option A
Declare that it's `RetryError`'s job to report sources.
This means `RetryError` will have to accept only an `E` implementing `std::error::Error`. That would be a breaking change.
It *might* mean moving some of the report machinery from `tor-error`, but really we only want the colon printing contraption which is simple enough that we could just copy it - and, arguably, `RetryError` has a different job to do since it must be able to print multiple errors.
### Option B
Declare that it's `E`'s job to report sources.
This means that putting an implementor of `std::error::Error` into a `RetryError` is a bug.
In practice, most call sites would need to be updated to use `RetryError<tor_error::Report<E>>` instead of `RetryError<E>`. (This is already done in `tor-hsclient`.)
Ideally we would find some way to detect these bugs. The only way I can think of is to invent a marker trait `DisplayImplIsNotBroken` and deprecate `RetryError::in_attempt_to` in favour of a new constructor.
### Option C
Embark on a campaign to drain this swamp in Rust upstream. It would involve:
1. Define an entirely new way for traits to be different between editions, with some kind of bidirectional trait gateway between `Error2024` and `Error2021`.
2. Use this to define `Error2024` which doesn't have `Display` as a supertrait but instead has a `fmt` method on the `Error2024` trait.
3. Wait until mid-2025 and try to start using the new stuff.
4. Discover all the "useless error output" bugs (not just the ones due to `tor_error::Report`, but everywhere an `Error2021`'s `Display` is used without inspecting sources), and fix them.Ian Jacksoniwj@torproject.orgIan Jacksoniwj@torproject.orghttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40898Add doc from tor-browser-spec/processes/ReleaseProcess to gitlab issue templates2023-10-03T15:38:12ZboklmAdd doc from tor-browser-spec/processes/ReleaseProcess to gitlab issue templatesWith tor-browser-spec#40049 we're going to remove
`tor-browser-spec/processes/ReleaseProcess`. Before doing that we should
add anything from that file not yet in the issue templates.With tor-browser-spec#40049 we're going to remove
`tor-browser-spec/processes/ReleaseProcess`. Before doing that we should
add anything from that file not yet in the issue templates.boklmboklmhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41262convert forum-01 to the DRBD backend2023-07-19T18:05:06Zanarcatconvert forum-01 to the DRBD backendthe `forum-01` server is setup with the `plain` backend, which is an oversight: it should run on the `drbd` backend.the `forum-01` server is setup with the `plain` backend, which is an oversight: it should run on the `drbd` backend.anarcatanarcathttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41886Downloads drop-down panel has new-line/line-break between every word in the '...2023-10-03T13:29:07ZrichardDownloads drop-down panel has new-line/line-break between every word in the 'Be careful opening downloads' warning![image](/uploads/9d0653d230c2564fab17130d6192fdad/image.png)![image](/uploads/9d0653d230c2564fab17130d6192fdad/image.png)henryhenryhttps://gitlab.torproject.org/tpo/network-health/team/-/issues/314New round of contacting operators for DNS issues and badexiting problematic r...2023-08-23T08:07:33ZGeorg KoppenNew round of contacting operators for DNS issues and badexiting problematic relays (07/11/2023)We got a new report this week:
```
Relay 2B3AAC97B269D59E6D642C8BFB174EDD13741C38 failed DNS check 5/5 times
Relay 2EE7F49728D03F8BC0DC1D67558499290C5F09FF failed DNS check 5/5 times
Relay 75A92E0354C0D40EDFB3C8398423159A1904D59B failed ...We got a new report this week:
```
Relay 2B3AAC97B269D59E6D642C8BFB174EDD13741C38 failed DNS check 5/5 times
Relay 2EE7F49728D03F8BC0DC1D67558499290C5F09FF failed DNS check 5/5 times
Relay 75A92E0354C0D40EDFB3C8398423159A1904D59B failed DNS check 1/1 times
Relay A0B5B5906EB13F213D7CA9AFEC91934BE3A5930F failed DNS check 5/5 times
Relay CB3B9D9932A51F2A2E120EAE0B5F9409EE371E80 failed DNS check 5/5 times
Relay F314580EA22CB3DCB135D64E92108BFB8FD209AF failed DNS check 5/5 times
```
`A0B5B5906EB13F213D7CA9AFEC91934BE3A5930F` is dealt with in #309, the reported issues are new.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/web/manual/-/issues/149improve instructions to 'Prioritize .onion sites'2023-07-11T08:54:12Zchampionquizzerchampionquizzer@torproject.orgimprove instructions to 'Prioritize .onion sites'A translator has reported:
> Currently on Windows, the suggested menu-address is "Settings" rather than Options.A translator has reported:
> Currently on Windows, the suggested menu-address is "Settings" rather than Options.championquizzerchampionquizzer@torproject.orgchampionquizzerchampionquizzer@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41258materculae out of disk space2023-09-21T01:51:41ZKezmaterculae out of disk spaceprevious ticket: #40826
it's been a year, and nagios is complaining about materculae's /srv partition
```
# df -h /srv
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_materculae-srv 147G 135G 4.3G 97%...previous ticket: #40826
it's been a year, and nagios is complaining about materculae's /srv partition
```
# df -h /srv
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_materculae-srv 147G 135G 4.3G 97% /srv
```
in the previous ticket (#40826) @anarcat changed the warning threshold, which is why this warning popped up now.
according to grafana, the usage has only been about 15G in the past year, and the growth is linear. we could add another 20G and revisit in a year, or throw 40G or 60G at it to push things further down the road.
![image](/uploads/e8ddf8b69703273f73d891586f7fc137/image.png)anarcatanarcat2023-09-22https://gitlab.torproject.org/tpo/tpa/team/-/issues/41257install MinIO in a VM2023-07-25T14:02:16Zanarcatinstall MinIO in a VMSetup a new virtual machine in the gnt-dal cluster with 1TB of SSD-backed storage, running MinIO in "single node" mode.
This should get the container registry running (tpo/tpa/gitlab#89) without running out of disk space, but also provi...Setup a new virtual machine in the gnt-dal cluster with 1TB of SSD-backed storage, running MinIO in "single node" mode.
This should get the container registry running (tpo/tpa/gitlab#89) without running out of disk space, but also provide us with a generic object storage system that could be used for other GitLab components.
More discussion and specifications in tpo/tpa/team#40478, this is also part of scaling up GitLab in general (#40479).
launch checklist:
* [x] install VM
* [x] install MinIO
* [x] testing
* [ ] ~~backups~~ we're sticking with the ad-hoc solution for now.
* [x] auto-upgrades
* [x] monitoring
* [x] documentation
* [x] security: review checklist https://min.io/docs/minio/container/operations/checklists/security.html
* [x] run as a normal user (with `podman --user`, not systemd `User=`!)
* [x] test `--network=host` to fix #41259(next) cluster scalinganarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41256Please add sarthikg to the weather group and let him access weather-012023-07-10T18:26:30ZGeorg KoppenPlease add sarthikg to the weather group and let him access weather-01```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Please add sarthikg to the weather group and let him access weather-01 to help
with Tor Weather development and testing.
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEV+BCWXPceMSRn284...```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Please add sarthikg to the weather group and let him access weather-01 to help
with Tor Weather development and testing.
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEV+BCWXPceMSRn284y3isMjDqp+oFAmSrw/gACgkQy3isMjDq
p+otqQ/9G6v5713isnQ3be9l8n6TsYnMCo8CLKzBZWD9p2cZ2lGD7a/P/xiZdpKs
M0ZnJYo78hWgY64PX4xj8ZlRhQJeM2qcNcaSnw3Jn8hDiviW6nd5jFbYZ9GyHhi/
l+bpJQ9tAeyYBu2bh7uto4C31jatMpFy1hlEGB9mtSn/lAmYmB1lE+4JQs3VYvUO
mmPD6lRiLPZbS10xgoQo5MlDZF98kx0KVRMXDPzIQOtsJrJ6ICVsyxKGkU6tMkS5
fQsGvkrGZBSBEccz/1jkFrOeG6+0fbTkJKK8nZXa2vM95p+mxOJcJO9WbN91+nfW
UiU0qM1R4a9WHh7MsDwFBBdaEsULYEdrEEQylGYHrFV6j31iYh+Dsm8vSIpry8em
rqyDEzA63k3cxVdR81m64H130wQWTa3zqtbkcZHXA3+3BtCyUdihIfAQvAfaHomT
2L/TZ420WkJ8cKDynEw8Yd1eSEUSns7DA0Y0Dgb3uNLT8AbONDNXPwm5XboIs4fM
xf/g7DNz17TZjljSu4rjmYZOXgatkMwOldeEWdUzJFi6D3iSGhfd+TGxO2Ho5Zxp
MRC5MlxQLhNereYVAe7CbVVbJ50+zBfSlVmWf+nPRG3nhLPhioXiIfdJ0eLSMaWv
/yjIoJ5NpzY4G4dW1+BKe3FLvCGng+ci2B45T8/keD8117gwACI=
=xFKf
-----END PGP SIGNATURE-----
```https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41882Update DuckDuckGo icons2023-10-03T13:29:11ZThorinUpdate DuckDuckGo iconsupdate DDG icon(s)
- FF117: [1836958](https://bugzilla.mozilla.org/show_bug.cgi?id=1836958) desktop
- FF117: [1841978](https://bugzilla.mozilla.org/show_bug.cgi?id=1841978) android
the svgs are in the commits
cc @donuts see https://git...update DDG icon(s)
- FF117: [1836958](https://bugzilla.mozilla.org/show_bug.cgi?id=1836958) desktop
- FF117: [1841978](https://bugzilla.mozilla.org/show_bug.cgi?id=1841978) android
the svgs are in the commits
cc @donuts see https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/27156#note_2818051richardrichardhttps://gitlab.torproject.org/tpo/applications/mullvad-browser/-/issues/208Improve letterboxing's dimensions2023-10-03T13:30:02ZrichardImprove letterboxing's dimensionsMeta issue for our various letterboxing issues we should fix in ~"13.0 stable"
- [ ] ~~Change the default start window size from 1000x1000 #175~~ (duplicate of the below ticket)
- [ ] Increase max width of new windows tor-browser#33282...Meta issue for our various letterboxing issues we should fix in ~"13.0 stable"
- [ ] ~~Change the default start window size from 1000x1000 #175~~ (duplicate of the below ticket)
- [ ] Increase max width of new windows tor-browser#33282
- [ ] Re-evaluate letterboxing dimension choices tor-browser#30556
Let's plan on doing this work in base-browser so tor-browser can get these improvements also.ma1ma1https://gitlab.torproject.org/tpo/core/arti/-/issues/951Carefully consider: should we be deny()ing any built-in warnings?2023-08-04T14:20:54ZNick MathewsonCarefully consider: should we be deny()ing any built-in warnings?Inspired by #950
We currently use `deny` on the following built-in compiler warnings:
```
#![deny(missing_docs)]
#![deny(unreachable_pub)]
```
These are both warnings that we never want to ship with, but `deny()`ing them creates a ris...Inspired by #950
We currently use `deny` on the following built-in compiler warnings:
```
#![deny(missing_docs)]
#![deny(unreachable_pub)]
```
These are both warnings that we never want to ship with, but `deny()`ing them creates a risk. If any future version of rustc extends these warnings so that they trigger in more cases of code, then all current versions of arti would fail to compile with those versions of rustc.
Possible decisions:
1. We trust that rustc will never make `missing_docs` or `unreachable_pub` apply in more cases than it does today.
2. We declare that we don't care if future versions of rustc won't compile existing versions of arti.
3. We change these `deny`s to `warn`s, but add `-D warnings` or whatever the flag is to our CI build flags, and encourage people to do the same in their local development environments.
4. ... something else?
(Every other lint that we deny is from `clippy`; this issue doesn't apply to clippy warnings, since failing to pass future versions of clippy won't keep our code from compiling.)Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41878firefox-mobile: refactor tor bootstrap off deleted onboarding path2023-10-03T13:29:13ZDan Ballardfirefox-mobile: refactor tor bootstrap off deleted onboarding path- Bug 1809998 - Part 1: Refactor CurrentMode to OnboardingAccountObserver - https://github.com/mozilla-mobile/firefox-android/commit/dc33c0942cd8c104a98448933b0400ec6c31c7e8
- Bug 1809998 - Part 2: Refactor Onboarding adapter items in t...- Bug 1809998 - Part 1: Refactor CurrentMode to OnboardingAccountObserver - https://github.com/mozilla-mobile/firefox-android/commit/dc33c0942cd8c104a98448933b0400ec6c31c7e8
- Bug 1809998 - Part 2: Refactor Onboarding adapter items in the homepa… - https://github.com/mozilla-mobile/firefox-android/commit/bf66c03ac48fe9af3fbcc4a12c0e8687cdf37b3a
- Bug 1809998 - Part 3: Add an OnboardingView for displaying the list o… - https://github.com/mozilla-mobile/firefox-android/commit/e43f574929bdd54ea6717dac9a3cbfacde520c8c
- Bug 1809998 - Part 4: Refactor OnboardingInteractor from SessionContr… - https://github.com/mozilla-mobile/firefox-android/commit/a69ee66b2957986dab6acd2de2b7bd1e6254728b
- Bug 1809998 - Part 5: Refactor Onboarding from HomeFragment into its … - https://github.com/mozilla-mobile/firefox-android/commit/d2dbf9b847de192a8a355010413c6b927837c7bf
Onboarding radically changed and our current work, a lot in Mode.kt and HomeFragment.kt are no longer triggered, which mean tor does not bootstrap, so tor brow2ser mobile doesn't torDan BallardDan Ballardhttps://gitlab.torproject.org/tpo/applications/mullvad-browser/-/issues/197Develop Crowdin to Gitlab translations repo pipeline2023-10-03T13:30:03ZrichardDevelop Crowdin to Gitlab translations repo pipelineMullvad will be using [crowdin](https://crowdin.com/) for localizing Mullvad Browser. We need a process/pipeline for getting the first batch of strings and any new strings in the future from crowdin into our translations repo.
[MB-tran...Mullvad will be using [crowdin](https://crowdin.com/) for localizing Mullvad Browser. We need a process/pipeline for getting the first batch of strings and any new strings in the future from crowdin into our translations repo.
[MB-translations.zip](/uploads/adab386c9b719c47e519aeea0f9f0276/MB-translations.zip)emmapeelemmapeelhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41255Enabling 2 factor authentication in the forum not possible without QR code2023-07-24T20:48:15ZSebastian HahnEnabling 2 factor authentication in the forum not possible without QR codeWhen logging in without a 2FA-enabled account and then being requested to enable 2FA, it isn't possible to manually add an authenticator. Once I click "enter manually", the previous page is reloaded instead of showing the necessary detai...When logging in without a 2FA-enabled account and then being requested to enable 2FA, it isn't possible to manually add an authenticator. Once I click "enter manually", the previous page is reloaded instead of showing the necessary details to set up 2FA.Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/network-health/onbasca/-/issues/157Functional bridges without ratio2023-10-05T19:22:46Zmeskiomeskio@torproject.orgFunctional bridges without ratioSome relays operators are [starting to notice](https://lists.torproject.org/pipermail/tor-relays/2023-July/021231.html) that we publish the bandwidth ratio from onbasca in their status page, and asking why some bridges have it and some d...Some relays operators are [starting to notice](https://lists.torproject.org/pipermail/tor-relays/2023-July/021231.html) that we publish the bandwidth ratio from onbasca in their status page, and asking why some bridges have it and some don't. Triggered by that I added to grafana a visualization of how many bridges are functional by bridgestrap but untested by onbasca. Out of 1914 obfs4 bridges 289 are in that state, so 15% of obfs4 bridges.
It looks like onbasca is failing to test those 15% of bridges.
Let me know if you need logs or something to help you debugging this problem.jugajugahttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41252bookworm upgrades, second batch2024-02-06T18:22:35Zanarcatbookworm upgrades, second batchupgrade all those servers to Debian bookworm
- [x] bacula-director-01.torproject.org (@lavamind)
- [x] btcpayserver-02.torproject.org (@anarcat)
- [x] bungei.torproject.org (@lavamind, `crypttab` had a typo, had to boot rescue to recove...upgrade all those servers to Debian bookworm
- [x] bacula-director-01.torproject.org (@lavamind)
- [x] btcpayserver-02.torproject.org (@anarcat)
- [x] bungei.torproject.org (@lavamind, `crypttab` had a typo, had to boot rescue to recover, grub KVM console seems inaccessible)
- [x] carinatum.torproject.org (@kez, had issues during upgrade, followup in https://gitlab.torproject.org/tpo/network-health/doctor/-/issues/40034)
- [x] check-01.torproject.org (@kez, had a prolonged outage: https://gitlab.torproject.org/tpo/network-health/metrics/tor-check/-/issues/40017, mod_qos broken, followup in https://gitlab.torproject.org/tpo/tpa/team/-/issues/41509)
- [x] colchicifolium.torproject.org (@anarcat)
- [x] collector-02.torproject.org (@anarcat)
- [x] crm-ext-01.torproject.org (@anarcat, PHP 8 compatibility issue, followup in #41511)
- [x] crm-int-01.torproject.org (@anarcat)
- [x] dangerzone-01.torproject.org (@kez)
- [x] donate-review-01.torproject.org (@kez)
- [x] gayi.torproject.org (@anarcat)
- [x] gitlab-02.torproject.org (@anarcat, migrated to standalone postgresql following upgrade issue #41426)
- [x] henryi.torproject.org (@kez)
- [x] majus.torproject.org (@anarcat, obsolete transifex-client package left around)
- [x] materculae.torproject.org (@lavamind, noticed extra load on the server, filed https://gitlab.torproject.org/tpo/tpa/team/-/issues/41507)
- [x] meronense.torproject.org (@lavamind, possible OOM regression see #41515)
- [x] metrics-store-01.torproject.org (@anarcat)
- [x] nevii.torproject.org (@anarcat, handful of issues with paths moved from `/usr/sbin` to `/usr/bin`)
- [x] onionbalance-02.torproject.org (@anarcat)
- [x] onionoo-backend-01.torproject.org (@anarcat)
- [x] onionoo-backend-02.torproject.org (@anarcat)
- [x] onionoo-frontend-01.torproject.org (@anarcat)
- [x] onionoo-frontend-02.torproject.org (@anarcat)
- [x] polyanthum.torproject.org (@lavamind)
- [x] probetelemetry-01.torproject.org (@anarcat)
- [x] rdsys-frontend-01.torproject.org (@anarcat)
- [x] rude.torproject.org (@lavamind)
- [x] survey-01.torproject.org (@lavamind)
- [x] telegram-bot-01.torproject.org (@anarcat)
- [x] weather-01.torproject.org (@anarcat, catastrophic data loss, see #41388)
31 machines
like the first batch, due date is approximate here, used to ping the team to organise this before the actual week planned in TPA-RFC-57, which is "last week of october".
an announcement need to be sent to remind people of this upcoming batch when the first due date is hit.Debian 12 bookworm upgradeanarcatanarcat2024-01-29https://gitlab.torproject.org/tpo/core/arti/-/issues/950Clippy nightly now gives a "missing panics doc" warning for expect()2023-07-07T12:59:34ZNick MathewsonClippy nightly now gives a "missing panics doc" warning for expect()This change seems to be the cause of our latest nightly fails: https://github.com/rust-lang/rust-clippy/pull/10953 .
There are around 54 affected functions in our codebase.
Before applying a fix here we should decide what we want to do...This change seems to be the cause of our latest nightly fails: https://github.com/rust-lang/rust-clippy/pull/10953 .
There are around 54 affected functions in our codebase.
Before applying a fix here we should decide what we want to do about this change. Should we...
1. Stop caring about the `missing_panics_doc` warning?
2. See if we can get the `clippy` maintainers to split this into a separate lint?
3. Add either an `allow(missing_panics_doc)` annotation or a `# Panics` section to every function that calls `expect()`?
1 would be fastest, but I think 3 would not be totally out of line. I don't think our chances for 2 are great.Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/team/-/issues/193Kickoff Sponsor 149 trainings in MENA2023-07-07T16:27:29ZGabagaba@torproject.orgKickoff Sponsor 149 trainings in MENAGabagaba@torproject.orgGabagaba@torproject.orghttps://gitlab.torproject.org/tpo/applications/tor-browser-bundle-testsuite/-/issues/40075Move nightly builds to tb-build-062023-08-22T17:06:37ZboklmMove nightly builds to tb-build-06With tpo/tpa/team#40984 we have a new machine for nightly build.
While moving nightly builds there, we should configure the build to use
`/tmp` during the build.
List of tasks:
- [x] Update references to `tb-build-01` on wiki page: htt...With tpo/tpa/team#40984 we have a new machine for nightly build.
While moving nightly builds there, we should configure the build to use
`/tmp` during the build.
List of tasks:
- [x] Update references to `tb-build-01` on wiki page: https://gitlab.torproject.org/tpo/applications/tor-browser/-/wikis/Nightly_Builds_Setup
- [x] Update references to `tb-build-01` in tor-browser-bundle-testsuite.git: !33
- [ ] Use `/tmp` in `rbm.local.conf`: !34
- [x] Generate two new ssh key on `tb-build-06` for user `tb-builder`, and add them to `tbb-nightlies-master` (with `command` option, following https://gitlab.torproject.org/tpo/applications/tor-browser/-/wikis/Nightly_Builds_Setup#rsync-between-tb-build-06-and-tbb-nightlies-master)
- [x] Remove old ssh keys from `/etc/ssh/userkeys/tbb-nightlies` on `tbb-nightlies-master`
- [x] Copy gpg key (CB91EDC56B9E276D7144ABD567509BB73B8DE954) from `tb-build-01` to `tb-build-06`
- [x] Copy `/home/tb-builder/nightly-builds` from `tb-build-01` to `tb-build-06`
- [x] Copy `/home/tb-builder/tor-browser-builds-archive` from `tb-build-01` to `tb-build-06`
- [x] Clone `/home/tb-builder/tor-browser-bundle-testsuite` on `tb-build-06`
- [x] Disable cron job on `tb-build-01`
- [x] Add cron job on `tb-build-06`boklmboklm