A somewhat generic way to do this is to create the notion of a variable such as is_in_deployment and allow Herald rules to check to see if this is set/true/a specific value. If the API to expose the variable is exposed to conduit then also allows for far more interesting workflows (especially when combined with relying on other Herald rules).
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 12 2015
Nov 11 2015
In T9767#144214, @chad wrote:Maybe add a "View Options" button to "File Contents" in Diffusion? That seems most consistent.
Oh, right... it's not explicit in Differential. But rather when the file is too large for syntax highlighting.
Maybe add a "View Options" button to "File Contents" in Diffusion? That seems most consistent.
@epriestley correct.. basically we have an external system (a Jenkins-like CI tool) that we're effectively using as a workflow engine. The timing isn't strictly defined, it's basically "when the user presses the button, do all these things".
Hmm, why not?
Hmm, why not? I'd prefer it (and it would be more consistent) if it wasn't editable, as in Differential.
(I don't see a reason to remove this feature, specifically)
From the code, Diffusion has always rendered non-highlighted code in a textarea.
Just to clarify, you would rather rely on an external script to activate and deactivate this rule every day instead of having a Herald condition like "Current time is between 5PM and 9AM"?
I don't plan to support this in the upstream. This configuration is inherently dangerous because the custom application has access to Phabricator's cookies, and not one we recommend.
Would love love love to see shortcuts, even just the ability to close a task and return to the previous board would be huge...
Dropping in here to +1 keyboard shortcutrs on on Maniphest. Would be of huge help to us.
Are you using VCS password for cloning?
Ah OK, good to know.
You should be able to batch edit infinite tasks.
Sorry, I got it. I have to leave an empty line between youtube url and text.
Thanks.
How exactly are you embedding it?
Hi @joshuaspence I'm unable to embed youtube video in wikis. I've enabled remarkup.enable-embedded-youtube. But adding youtube link in wiki or adding youtube embedding html in wiki is not helping!
In T7053#144090, @epriestley wrote:
- When editing the small amount of config which can't auto-restart (phd.user, phd.start-taskmasters). I think phd.user already has an existing warning anyway.
Yeah, I would like to handle this properly but I'm not sure if it is worthwhile doing so?
In T3670#144082, @epriestley wrote:This is currently difficult to do because it involves bulk editing our entire workboard
What's difficult about this? Can't you just use the bulk editor to "Remove project X" and "Add project Y"?
Thanks for putting this together, it was very insightful.
@epriestley I'll keep an eye on blueprints and the merge configurability. Thank you. Phabricator is awesome/and getting awesomer.
In T9759#144069, @epriestley wrote:We don't show a specific amount of history: we show all activity since your last activity.
Nov 10 2015
In T9760#144113, @epriestley wrote:Right, Almanac does not support autoscaling.
Right, Almanac does not support autoscaling. We'll have an EC2 blueprint (and similar) in the future which can manage autoscaling more simply. Almanac is the ground level "I have a list of IPs" version of things.
bin/almanac register is just a shortcut for "put the private half of a key in the right place on disk, and the public half on the specified Almanac device". Maybe a clearer name would be bin/almanac install-keys.
Right okay, but I can't autoscale the Drydock Pool right? Because I need to manually create new devices through the UI.
This just means adding a device interface?
In T9760#144107, @epriestley wrote:
- Bind it to your pool to actually put it in service.
So what does ./bin/almanac register actually do?
Right. You just need to:
Ok thanks. So I don't need to register my build agent with ./bin/almanac register?
Don't do steps (3) or (4)! Those are useless at best, and dangerous at worst.
- The view page doesn't actually show the short URL anywhere. You can copy it from "View URL", but I think this isn't totally obvious, and we probably have enough room to reasonably add it (e.g., "Short URL: ..." under "Original URL: ...").
- If a link has an alias, "View URL" still links to the non-alias version (e.g. U6 links to /u/6, but a more-preferred link would be /u/bug).
- The "Remarkup Reference" document (https://secure.phabricator.com/book/phabricator/article/remarkup/) should explain how to use ((6)) and ((bug)). It might be worthwhile to hint these on the U6 page itself, e.g. In Remarkup: ((bug)) in the properties? Not sure how useful/cluttered that would look.
- Maybe show aliases on the list at /phurl/?
- Maybe let users search for the link with a particular alias? If I know ((bug)), there's no way for me to actually find the URL object right now. Hovercards would be one fix but just going to Phurl and being able to search for "Alias: bug" is probably good too.
This also seems to work properly on this host, although I hit the "daemons are not running" setup warning once, presumably by racing their restart. If this is an issue we can tweak how that warning works, I think.
Also "Active" in the Object Header should just be the normal color, not green. Our design pattern is "normal" states are plainly colored and exceptional states are actively colored. (red, green, purple).
Oh, transaction publishing from Phurl also currently fails in the daemons:
One possible minor followup to maybe keep on the radar is showing some extra warnings in a few cases:
A couple of notes so far, after poking at this:
The resolution of T7053 should indirectly resolve this.
This is currently difficult to do because it involves bulk editing our entire workboard
I have a use case which is maybe suited for subprojects, but I don't exactly know how you are planning on implementing this...
We run this entire algorithm ourselves and it's pretty simple (basically just looks at indent levels, no language awareness). Should be pretty easy to have it peek at the previous line if it initially finds a line containing only "{" and see if that line is at the same indent level and otherwise suitable.
(We could theoretically fiddle with this and include some time constraints and stuff but I suspect this rule is already the best rule we're really going to get, given how contentious/subjective the subject is and how little complaining we hear about it, relatively.)
Phame should be "mostly reasonable" to test as an internal blog platform. There is more polish to come, but feel free to send feedback along here.

