> A number of New Zealand petrol pumps stopped working on Thursday due to a "leap year glitch" in payment software, fuel stations and the payment service provider said.
Even today the LEGO-compatible knock-offs are complete junk, my kids occasionally end up picking up a loose bag for £1 from the local charity shop. Pieces don't stick together properly (with each other, let alone LEGO pieces); legs, arms, and hands come off the minifigs; etc. You can instantly tell — even ignoring the assault rifles that would never make it in a LEGO box.
> Spotify reported that it had 9,400 employees at the end of the third quarter of 2023. It had already cut back employee numbers by 6% in January and by a further 2% in June.
There's a company working to build a 3600km long cable between solar + wind farms in Morocco, and the UK. 3.6GW cable, 10GW of generation, 20GW of battery storage, and the cable should run at full load for 20h a day.
> Are the raw files in the working repository GeoPackages?
The working copy for a vector/table dataset can be in a GeoPackage or a SQL database like PostGIS. For rasters/point-clouds they're flat files.
> How is it tracking the changes made inside the geopackages?
In general, triggers which store RowIDs/PKs of inserts/updates/deletes. Then when you ask for a diff or make a commit Kart figures out any actual row-level (or schema) differences.
> What happens if it's replaced with an updated copy of the geopackage the was edited via some other application?
If it's edited by something else (QGIS, ArcGIS, python/go/whatever application, SQL CLI, whatever) it'll work: you do edits where you want to. If it's replaced by something else, it won't work.
> How does it diff the changes?
Comparing the features/rows in the repository (and their schemas) against the rows in the working copy database. It uses the stored list of modified rowids to make this fast.
Nurdles are everywhere... https://www.nurdlehunt.org.uk/nurdle-finds.html