- User Since
- Apr 21 2015, 7:13 PM (204 w, 3 d)
Oct 30 2015
Thanks for your reply, the detailed description really helps. The build system works now, and even though the "Lease Working Copy" step doesn't really make sense for us, I'm really glad everything works :-).
Thanks, I set "Also Clone" to a random repository and that solves the exception I pasted. I got my builds working again. For future generations: this is how I configured Almanac/Drydock/Harbormaster now:
Oct 29 2015
Alright, I've managed to upgrade Phabricator and fix the storage schemata issues. I've also reconfigured Almanac, Drydock, and Harbormaster to reflect the latest changes regarding blueprint authorizations. My Harbormaster build step is authorized on the Drydock blueprint, so that looks good.
Upgrading Phabricator to the latest HEAD, and running ./bin/storage upgrade results in this error:
Thanks, I'll read those. However, I'd still like to know why Drydock leases suddenly stopped working, and why I can't cancel them to free up the daemons, and there's no way to cancel or remove the build tasks from the daemons, too. They just keep retrying forever.
I have, a week or so ago. However, around October 12 "Blueprint Authorizations" were added to Drydock and those changes broke our entire build setup. There was no documentation on how to work with these Authorizations at the time (or I couldn't find it), so I rolled back to the last commit before those changes.
Jul 6 2015
While I agree that making the browser window narrower is a good work around for things like Phriction and Maniphest, it does get annoying when using Diffusion/Differential/Audit, to review code diffs. In those cases, you kind of need the horizontal space to be able to read the code easily. That means I would have to constantly resize my browser window when switching apps/context in Phabricator.
Jun 24 2015
Jun 23 2015
@epriestley: this task being fixed might be an easier solution than writing our own Doorkeeper integration (as discussed on Conpherence today). I already have an application that receives feed data via POST; can I help test this change so we can get it merged?
Additionally, the font family of the preview seems to differ from the rendered result.
@chad: I'm not sure if this has been mentioned before but it seems title tags (<h1>, <h2>, ...) render differently in the preview. Compare these screenshots from Phriction:
Jun 20 2015
That's an awesome feature, @epriestley. I'm don't even need it myself, but I really love how Phabricator tries to be a tool for anyone to use, without getting in their way. We're about to move our entire company off of Github and onto Phabricator and it's things like this that reassure me we've made the right choice :-).
Jun 19 2015
Would it be possible to support both fixed and fluid layouts? Or is that
going to be a pain to support for all the different apps?
Jun 15 2015
May 29 2015
Yes, that solves it. Thanks!
May 21 2015
Thanks @epriestley, just deployed this and can confirm that it's fixed.
Addition: the error disappears when we disable syntax highlighting in the file browser.
Not a maintainer, but maybe I can help; I had the same issue.
May 1 2015
Apr 24 2015
Sorry, those commit hashes are not correct. Issue seems to have been introduced in rPf64ca87bfea01a355f3fbf4fa03c460995b5da99
This breaks the built-in "Authored" and "All Tasks" queries.
Apr 23 2015
Bump; I'd like to see this added as well. Additionally, is there a way to get the actual comment text from "new comment" feed items? As far as I can see that is not possible now, and is not added in this revision.