This tool is a rewrite of the Hatnote Hashtags tool.
The tool should do most if not all of what the previous tool did but with some changes and improvements:
Most notably, this version monitors the recentchanges EventStream rather than periodically reading from the recentchanges database. This means all Wikimedia projects and languages are monitored (except Wikidata, see below), and new hashtag uses are ingested into the tool's database almost as soon as they happen.
This version of the tool runs on Django, rather than Flask. No important reason for this, it's just the framework Sam knows best. This does mean that the backend has almost separate code to the old tool.
Bot edits are excluded. One of the reasons the old Hashtags tool slowed to a crawl and had to be taken down was the huge number of bot edits that made their way into the database. While in an ideal world we would collect these too, it's simply too easy to overload the database with millions of entries that very few people are interested in. If individual bot edits need to be tracked, the better solution would be to do so directly via the bot or by looking at the bot account's contributions.
Wikidata is currently excluded too, for similar reasons. A huge number of automated or semi-automated edits happen there utilising hashtag edit summaries, and from initial testing it looked like similar problems were going to present themselves. This will be revisited once the tool is up and running and stable.
This tool is also running on a Horizon VPS instance, rather than Toolforge, to ensure it has the database resources it needs and doesn't disrupt other tools.
To set the tool up for local development, you will need:
If you are installing Docker on Mac or Windows, Docker Compose is likely already included in your install.
After cloning the repository, copy
.env and start the tool by running:
docker-compose up --build
-d option will allow you to run in detached mode.
You should now be able to access the tool in your browser on
When the tool is first run the scripts container will fail because migrations haven't finished running yet. There are solutions to this that will be implemented eventually.
To fix this problem, simply restart the container with:
docker start hashtags_scripts_1
An old error message may be printed if you're not running in detached mode, but the container should start successfully.
Run tests with:
docker exec -it hashtags_app_1 python manage.py test
This is helpful in case the script appears to be stuck so we can determine what it is trying to do.
Open a privileged shell in the scripts container:
docker exec --privileged -ti hashtags_scripts_1 bash
The next steps should all be run in that terminal, inside the container.
Install gdb and a text editor of your choosing with:
apt update && apt install gdb nano
Download the source code for the Python version used in the scripts:
wget https://www.python.org/ftp/python/3.5.2/Python-3.5.2.tgz -O - | tar -xzvf -
The version (3.5.2, in this case) should match the one in the
Dockerfile-scripts file in this repository.
Now, copy the Python gdb library to a suitable place where gdb can find it:
cp Python-3.5.2/Tools/gdb/libpython.py /usr/local/bin/python3.5-gdb.py
/root/.gdbinit so it looks like this:
add-auto-load-safe-path /usr/local/bin/python3.5-gdb.py set auto-load python-scripts on
Find the process ID of the script through any of the usual means (e.g.
pgrep -lf python, or
Finally, you can attach gdb to the process with:
gdb python <pid>
py-bt to view the stack,
py-down to navigate it, and
py-locals to view local variables!