Page MenuHomePhabricator

Add "--force" and "--quickly" flags to `bin/lipsum`
ClosedPublic

Authored by epriestley on Feb 27 2017, 1:14 PM.
Tags
None
Referenced Files
F15411619: D17421.id41890.diff
Wed, Mar 19, 9:29 AM
F15394052: D17421.id41890.diff
Sat, Mar 15, 11:19 PM
F15374833: D17421.id41890.diff
Wed, Mar 12, 8:18 PM
F15335416: D17421.id41890.diff
Sat, Mar 8, 3:08 PM
F15285436: D17421.diff
Tue, Mar 4, 1:42 PM
Unknown Object (File)
Fri, Feb 21, 3:12 PM
Unknown Object (File)
Thu, Feb 20, 2:57 AM
Unknown Object (File)
Feb 9 2025, 3:23 AM
Subscribers
None

Details

Summary

Ref T12319.

  • Lipsum can trash an install by creating a lot of junk that's hard to get rid of, so we're cautious about letting you run it. Add a --force flag if you're sure you know what you're doing. This makes the edit/test cycle a bit easier when actually writing Lipsum generators.
  • Lipsum normally sleeps for a second before creating objects, to give users more control over how much stuff they create and limit the amount of damage caused by mistakes. Sometimes, you want to generate a LOT of stuff because you want to reproduce a performance/scale issue (like T12319). Add a --quickly flag to generate objects as fast as possible.
  • When loading random users (used as authors, assignees, etc), also load user settings so we can ConduitCall with them.
  • Allow generators to return a PHID instead of an actual object (more convenient for Conduit-based generators).
Test Plan
  • With next change, ran lipsum generate badges --force --quickly.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Feb 27 2017, 3:42 PM
This revision was automatically updated to reflect the committed changes.