This morning I was created with 6 emails, all announcing FAILED: MASTER_PORT, one for each FreshPorts node. Each was sent at 5AM (1000 UTC). Something happened which upset every one of them. I have no idea why. However, I’m writing this down for future reference. This announcement came from one of the many system checks […]
FAILED: MASTER_PORT Read More »
Today, the UI on the website was updated. The primary changes are to the home page and the date pages (i.e. lists of commits). I have purposely not cleared the cache. This should help you see the before and after images. For comparison, see today’s commits and the commits from Dec 16. This latest work
The front page of FreshPorts is about to change, slightly. At present, the front page contains only the the commits to the main branch of the FreeBSD. More precisely, it does not include: Commits to Mk/ or other similar non-port entities within the ports tree Commits to the quarterly branch (whatever the latest quarter is;
Displaying all ports tree commits on the front page Read More »
Yesterday, an incident with a commit wound up taking up a lot of time to process on FreshPorts. The purpose of this post includes: document how the commit was handled on different nodes document the fixes for some nodes investigate how the code can be improved to detect such situations and abort See also How
When a commit goes wrong Read More »
The July 4th tweet announced “dev, test, and stage .freshports.org are now running Python 3.9”. Three days later, “Is it coincidental that dev, test, and stage are all stuck on commits from July 4?” I took notes as I explored the problem. The first clue was: 2022.07.07 00:12:03 git-delta.sh /usr/local/libexec/freshports/git-to-freshports-xml.py –repo ports –path /var/db/ingress/repos/ports –branch
Update to Python 3.9 broke commit processing Read More »
FreshPorts has three main daemons: ingress – waits for incoming commits and creates XML. freshports – processes the XML into the database. fp-listen – listens for events and clears cache The first two run on the backend (the ingress node, or jail), the last run runs on the webserver (nginx jail). The list of events
adding a new event to fp-listen Read More »
Following on from yesterdays Quarterly branches: what’s next? and Processing commits on branches with git, I’ve started in on clearing commits from cache. The code First step, create a table which looks like this: freshports.devgit=# \d cache_clearing_commits Table “public.cache_clearing_commits” Column | Type | Collation | Nullable | Default —————–+—————————–+———–+———-+——— commit_to_clear | text | | not
Commit cache clearing Read More »