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 packages_raw gets reloaded. A lot. Every time a new set of packages is available from the FreeBSD packages table, data gets deleted and reloaded. So I manually vacuum the table. Well, it’s automated, as part of the code, but it doesn’t wait for the daily scripts. I was seeing these errors on server r720-02:
Fixing permissions on the packages_raw table Read More »
When setting up a new FreshPorts ingress node, the repositories must be configured with tags so FreshPorts knows the last commit it has processed. This is the starting point each time FreshPorts goes to search for new commits. This post about Processing commits on branches with git might help with background. Those tags must be
Configuring the repo for a new ingress node Read More »
The commits.php page has a long history dating back to 2006 in GitHub and before that in another repo. Soon, it is going away. The justification is in issue 337: it’s not used much, and it’s not doing as it should (loading the last 100 commits). In the early days, the front page showed only
/commits.php is going away Read More »
This post documents how I’m changing the search methods for pkg-message. It uses full-text search, but instead of using a special column, I’m going to use an index. I will elaborate. When searching pkg-message was added to the website, a different approach was taken than in the past. In Converting a column-based expression to a
Moving from storing the tsvector values to a tsvector index Read More »
One of the primary uses for FreshPorts is searching various characteristics of the ports. One highly used search feature is pkg-messages (background at pkg-message). A problem which has been vexing me for about 2 months was the lack of results on prod, but results which worked on dev. The issue was raised on GitHub. Initially,
When tsvector was working as expected on most hosts, but not one Read More »
Tonight I was setting up a new FreshPorts node for development. It took me a while to remember the steps. sudo su -l postgres psql template1 < globals.sql createdb -T template0 -E SQL_ASCII freshports.org psql freshports.org create language plperl; exit; time pg_restore -j 32 -d freshports.org ~dan/dump/freshports.org.dump
note to self: restoring a database Read More »
Based on the Add links to GitHub and GitLab mirrors for ports and commits request, the website has some new links arriving soon. Link to GitHub from each commit A similar link to GitLab Use the one you like. Each git web interface has it’s own followers. Also, while there, the commit hash at the
New links to GitLab and GitHub, in addition to the exist cgit.freebsd.org Read More »
The Libreoffice homepages seem wrong. dev and test do not show a homepage for arabic/libreoffice, but stage and prod do. Could this be a commit which corrected something after dev and test were corrected? I think so. I think this commit did that. Let’s check from the command line. I’m doing this in my empty
What’s up with libreoffice homepages Read More »
By “post correction”, I meant “post-correction script”, i.e. after the correction script completed. A recent commit started the process of moving the WWW from pkg-descr to Makefile. These were huge commits, about 27930 ports each. FreshPorts is dumb. It sees a commit and it refreshes all ports touched by that commit. Refreshing every port takes
homepage – post correction Read More »