(Of course, it'll probably just work the first time now...)
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 13 2024
Feb 12 2024
The export process is already robust at a coarse level: the dump is retained on disk and the process can be retried at the "upload the whole file again" level, then picked up with bin/host export using the --database or --database-file flags (probably with --keep-file).
The (anonymized) error the process encountered occurred while transferring the dump to central storage was:
Oct 26 2022
There are some remaining non-security bugs with this that I'll follow up on in T13682. I believe the security side of this is now resolved.
The details of this attack will be disclosed at a later date, once installs have had some sort of plausible chance to upgrade.
I filed T13687 as a followup for preventing this particular sort of error (where a Phobject is incorrectly serialized directly).
Jul 8 2022
That's very likely the same problem, and I think it should be fixed by updating to the current stable (rPf2a7db1 or newer).
I believe we may be hitting either the problem one of the above commit fixes, or suffering from a similar caused as side-effect from it.
Jun 14 2022
...ideally this sort of thing should fail loudly at serialization time...