I should add that when I am "stuck" in drag mode (no mouse buttons held down, but moving it around scroll me around like I am click-dragging), I can do a fast left-click on an empty spot on the workboard and it becomes unstuck.

Added time markers as it isn't clear what I'm doing with mouse/keyboard without a visual cue.

Thanks for the video, unfortunately I still can't reproduce the issue locally. Everything works for me.

Please see attached .wmv file. I used a technet video capture utility as it was quick and did the job, sorry the quality is not higher but it should do the job.

This the browser I tested:

I can't reproduce the issue you're describing. Maybe make a video to clarify the specific behaviour?

We were able to consistently replicate it on multiple Windows 7 64-bit IE 11.0.9600.17843 (11.0.20) and Windows 7 32-bit IE 11.0.9600.18204 (11.0.28) workstations.

What OS should I be testing?

This is what I was looking for!
Thanks! Works!

Tasks are already re-orderable (to just you) in Maniphest. Not sure what else you want? T5793 might also be of interest.

1. make a private project
2. add tasks you like to it
3. ???
4. profit

@epriestley // Oh, I don't know that. Cuz, OS X preview shows repeating animation.
Thanks Very much : )

The GIF data is set to repeat the animation only once (see circled control in footer):

I don't have access to this server. How your server is set up is more important. What php version and what image library are you using? Is it only this gif or other large gifs as well?

@chad // I update the description, but I can't reopen this issue. Should I make a new bug report?

Please fill in all required information for a bug report. Specifically missing are steps to reproduce and what version of Phabricator you are using.

@cspeckmim Sadly I don't have any Mercurial host that is not Phabricator.

@fcoelho oops sorry about the mixup. I've previously had success by downgrading the client to 3.4 or less.

• (T9516) Use the same copy/paste line number stuff that Paste, Diffusion, etc use.
  • (T10179) Make formatting smarter. For example, the "Run CircleCI Build" plan produces logs that we know to be HTTP headers (which we could format as a table) and (almost always) a JSON blob (which we could format as human-readable JSON).
  • (T8656) Make one of the smart formatters "ANSI".
  • I'd like to style this like other stuff (Paste, Diffusion) and let users pick dark themes globally with T5701 if they prefer.
  • Logic for loading the data is clunky, and fetches much more data than it needs.
  • Clicking pager links affects all build logs on the page, this should probably be JS-ish at some point.
  • Pager logic often feels clunky to me. For example, if a log is exactly 21 lines long, we still show pager controls. If a log is 27 lines long, we should probably show the whole thing. "Show more" would be more consistent with how other pagers work, etc.
  • (T6139) Not sure if this is really the right way to frame it, but we often have information about how useful a build log is and can do a better job of organizing them (e.g., successful build logs are usually uninteresting and could be folded by default).

@hach-que, that plan sounds good to me.

Not directly to your point, but you can remove or shorten the [Differential] token by adjusting metamta.differential.subject-prefix, if you didn't stumble across that already.

Ok, sorry for the noise, a complete re-install of mysql fixed the issue; I assume that I had not removed all traces of a previous installation as thoroughly as I hoped.

Interesting, thanks. I just followed the "Diffusion User Guide" which states that the git user must have access to the repos as the phd-user.

I'm still not really thrilled with where the documentation situation on repositories is, but it's getting a little more manageable.

Here are a few ideas that might shed some light on what's happening:

I can't reproduce this. Here's what I did:

arc diff is supported, but most of these reproduction instructions don't make much sense to me in the context of arc diff -- for example, arc diff does not apply patches.

As I mentioned, we also experience this with arc diff. Is that not supported?

Specifically, any effort to reproduce this in the upstream will meet this grizzly fate on the arc test step:

Yeah, arc test is not part of the upstream.

This is a Bitnami issue, and you should report it to them. See Contributing Bug Reports:

Just throwing my input in here:

(Those two things seem reasonably separate, so this might be better split into two issues, but I'll leave it up to @epriestley to decide that; I just wanted to get better visibility on the discussions that happened around those original code reviews in case any community member wanted to tackle implementing these features with upstream guidance)

• arc patch attempts to apply the patch to the commit the diff was based off; Is that what you were expecting?
• arc test is not a command I have; What is it?

I managed to find the original restart target feedback that @epriestley wrote.

The goals here don't align with upstream, so I've consolidated the general feedback from @epriestley into T10870.

There were also some comments around embedding build plans (with individual build steps being restartable), but I can't find them now. I'd like to pursue these features in the near future, as we're finding Jenkins "multi-configuration projects" don't actually allow you to restart individual builds (which we rely on because AWS is inherently unreliable in it's operations).

This seems reasonably easy to tackle. Roughly:

Maybe also reasonable would be something like this:

One thing we could do to improve this is version daemons in /daemon/, so your "go to sleep" routine could be more like:

I'll start doing this, I guess it makes me a little uncomfortable since the first thing I do is typically make sure nothing is broken once the daemons restart, but then again, nothing has ever been broken during a deployment. So maybe I will assume I am as smart as our past deployments have indicated I am, issue the reload, go to sleep, and then check in the morning.

You can use bin/phd reload -- instead of restart -- to instruct daemons to exit and restart only after completing their current tasks, with no time limit on task completion. The semantics on this are necessarily a little fuzzy, but basically:

@cspeckmim I think you probably confused me with @urzds, I didn't post any logs here yet.

Looks nice! Looking forward to the future plans for it, in the meantime i have a question:
Feature currently seems to assume a certain width for images, and scales images up or down to fit. In order to help my cover-photos avoid scaling and look their best I would like to know what that width is.

Throwing a vote in that this feature would definitely be of great use to us as well.

This document is already large and complex and the source of many configuration mistakes. I worry including basic information like this could cause more harm than good, by making the document even larger and making it easy to miss something important.

I understand - i didn't wanted you to fix my configuration. I think as soon as i have some experience running phabricator in this setup i can try to help improving the setup, if even possible.

That is, we normally navigate complex configuration by verifying every step and just telling you what's wrong and how to fix it (e.g., moving all the MySQL, etc., configuration from documentation to automatic setup issues was a huge step forward), but there's basically no test we can perform on most of this chain.

In general, this configuration is a huge horrible mess but I'm having a hard time coming up with ways to really fix it that don't just tell you to run everything as root.

However, i wouldn't exclude that i misunderstood something about the moving parts of Phabricator.