Page MenuHomePhabricator

Allow diviner books to be permanently destroyed
ClosedPublic

Authored by joshuaspence on Feb 11 2015, 1:03 PM.
Tags
None
Referenced Files
Unknown Object (File)
Feb 9 2024, 8:23 PM
Unknown Object (File)
Jan 30 2024, 6:20 AM
Unknown Object (File)
Jan 30 2024, 6:20 AM
Unknown Object (File)
Dec 23 2023, 2:45 PM
Unknown Object (File)
Dec 14 2023, 6:41 PM
Unknown Object (File)
Nov 30 2023, 5:50 AM
Unknown Object (File)
Nov 24 2023, 2:34 PM
Unknown Object (File)
Nov 19 2023, 1:38 AM
Subscribers

Details

Summary

Fixes T7182.

Test Plan

Deleted a book with ./bin/remove destroy

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

joshuaspence retitled this revision from to Allow diviner books to be permanently destroyed.
joshuaspence updated this object.
joshuaspence edited the test plan for this revision. (Show Details)
joshuaspence added a reviewer: epriestley.
epriestley edited edge metadata.

One inline.

src/applications/diviner/storage/DivinerLiveBook.php
104

I don't think destroyObjectPermanently() should print to the console.

You can use --trace to monitor status, and it automatically keeps a log of deleted objects (bin/remove log).

If you want a progress bar specifically, we could add a destroyObjects(...) and let the Engine build the bar when run via a console? I'm generally onboard with bin/remove destroy being more verbose, but I think the Engine should be responsible, not the destroyObject...() implementations.

This revision is now accepted and ready to land.Feb 11 2015, 1:47 PM
src/applications/diviner/storage/DivinerLiveBook.php
104

Oh yep, I had intended to remove this. Basically, destroying a book took a lot longer than I had expected (maybe 5 minutes).

joshuaspence edited edge metadata.

Remove console logging

This revision was automatically updated to reflect the committed changes.