I will be updating the OS for the forum server around 4am GMT tomorrow (about 22 hours from now).
The forum will probably be down for a couple hours (mostly due to the time required to take a snapshot of the server) unless things go horribly wrong (in which case, that snapshot will come in very handy!).
Other Stairways / Keyboard Maestro servers are mostly being done today, so if you notice any of those being down for a short while, don’t be too alarmed - but if you notice any services being disrupted for more than a couple hours, do let me know (via email or via Twitter to @peternlewis if other methods are broken).
Well, that could have gone better. And worse I suppose.
Took a snapshot, installed the upgrade, which proceeded to corrupt the disk and fail to boot properly. Restored from the snapshot, everything works again. Repeated the upgrade, got the same results, restored from the snapshot, everything works again.
So no upgrade today. I’ll await some guidance from Digital Ocean and try again.
It proved the Snapshot worked. I also have a series of forum backups and a whole backup of the all the files on the server which in turn is incrementally backed up, so there is essentially no chance of losing the forum, it’s just a question of how much downtime is involved.
An alternative process is to spin up a new server and transfer the forum to it, but it’s hard to avoid a significant amount of downtime with that.
There is still an issue with the disk which might require some further downtime (any time I take a full snapshot, to be safe it needs to be powered off and snapshot takes an hour or so, so that is unavoidable downtime in the interests of not losing anything).
The select-code-block code Rob wrote hasn’t been working properly in Safari, since the update to macOS 10.12.4 and Safari 10.1. (No text is returned.)
Since around that time the text in Chrome won’t stay selected either, although the code-block text IS returned to AppleScript before the selection is lost.
None of this has anything to do with Keyboard Maestro.
I’ve talked to Rob about trying to fix things, but he’s overly busy right now.
No I didn't. I've tested the scripts I mentioned on the Script Debugger forum, and they have had similar problems there starting around the same time as the Safari issues.
Perhaps the fact you're still using El Capitan has keep you from seeing this.
So, I am saying that the JavaScript in Chrome scripts that I am running in El Capitan no longer work in the KM Forum AFTER the update, but they STILL work in the SD Forum.
I doubt it has anything to do with the forum update - it is the server the forum runs on that I updated, and the forum itself runs within a “docker” container, which is like it’s own virtual machine, and the forum itself wasn’t updated, it remains at 1.7.8 (plus patches for the mail subject line thing).
So while nothing is impossible, I’d say it’s highly unlikely it has anything to do with the forum server update. Maybe that the server was restarted, but other than that, very unlikely I’d guess.
As for the specifics of the Web Clipper or the JavaScript XPath stuff, I don’t know anything about them so I don’t have any suggestions as to what might be the problem or if there might be a solution.
If it is working in the SD Forum, then perhaps it will come back when the forum goes to 1.8 (which wont happen until 1.8 is finalised).
It is possible that I just did not happen to use these scripts until after the forum OS update, so the issue could have started after the 1.7.8 & patch update.
