See also PHI68.

The bulk of the work here is finished, no plans on approaching a re-design for diffusion home this pass.

Closing out, thanks for all the feedback. Will follow up with individual tasks not addressed.

New search shipping with last week's stable release.

The behavior may have changed, but the change is from "we sometimes silently do the wrong thing" to "we explicitly refuse to do the wrong thing".

Ah, it sounded like a regression from the report. I haven't tried to bisect to determine if that was true.

That is, specifically, it expected that hg commands do not work in Phabricator if it can not determine the version of hg, so this is not a bug. Ignoring the setup warning might mean "we used to do Mercurial stuff but don't anymore, leaving us with some archived Mercurial repositories which we don't really need to look at, so it's okay that hg commands won't be able to run".

The version is strictly required because different versions of hg use different command syntax. If we can not determine which version of hg is installed, we can not run hg commands.

I could totally be imagining that.

it shouldn't have changed, just now a border. I don't know how to update the colors since it some sort of strange math only engineers know.

If it matters, my laptop is actually 13" with 1080, but it's only because the store said they don't have a smaller version.

See Planning for information on planning and timelines.

I'm not sure it's a bug. The error message was surprising; HTTP/1.0 500 Error 1: sudo: a password is required. I see a matching error message in Q261. The solution there seems to be allowing the webserver process owner to have sudo rights. I now found there are docs on the subject diffusion_hosting#configuring-sudo.

If you believe you've found a bug in Phabricator, please follow the instructions in Contributing Bug Reports to file a report.

This might be useful debugging information:

>> export GIT_CURL_VERBOSE=1
>> git clone http://phabricator.internal/diffusion/TRACTORAPI/tractor-api.git
Cloning into 'tractor-api'...
* Couldn't find host phabricator.internal in the .netrc file; using defaults
* About to connect() to phabricator.internal port 80 (#0)
*   Trying 10.11.45.21... * Connected to phabricator.internal (10.11.45.21) port 80 (#0)
> GET /diffusion/TRACTORAPI/tractor-api.git/info/refs?service=git-upload-pack HTTP/1.1
User-Agent: git/2.14.1
Host: phabricator.internal
Accept: */*
Accept-Encoding: gzip
Accept-Language: en-US, *;q=0.9
Pragma: no-cache

This doesn't work again.

11" Macbook breakpoint is 1080 it looks, I think we still do tablet around 960? 1080 is enough space for anything we do. Not sure where @avivey 's laptop actually is. I do want to add more information to blame view though, so the space will be used.

I was joking.

Did you consider increasing the "tablet" breakpoint above the size of an 11" macbook instead?

Just for @avivey and his 11" macbook: D18448

neato!

Yes. In Mercurial, branch heads may be "Open" or "Closed".

That the branch is closed?

What is state here? I don't really remember what this was about, or if it's needed.

Search is now in the header, see rP

@aubort, please use the community forum (see: Discourse) if you'd like to discuss this issue.

+1 the problem is still here. There's no way for a end user to make it right without the need for an admin to go run a command on the server, which is not very good.

I'm just going to merge this into T929, I don't think it's a distinct task. I'll link that to T12824.

adding my vote to @ivo's suggestion.

The new rules on reports are still in flux a bit and extra-muddy for Community members, but I'd generally like to move to a "report + review" model for community reports, something like we currently have for code review. So the general idea is that your bug needs someone to review it and agree with it (e.g., reproduce a bug, or agree that a feature request is a brilliant new idea that makes sense and would be appropriate for the upstream and completely describes a reasonable, generally-experienced root problem) before it comes upstream.

I think this is a real bug. Here's a more complete example of what's going wrong, why it's wrong, and how to reproduce it.

I would open to accepting this as a bug report if I felt it was deliberately designed to work the way you expect, but was not (like a regression). Or if information was presented that all other repository viewers do it this way. Otherwise I think it's more 'nitpick' or 'feature request'. A cursory look at GitHub, seems they show the full diff as well: https://github.com/phacility/phabricator/commit/5c1e4488dedafda08684b33a8a4786cf687d2811

In T12959#230805, @chad wrote:

In general are you aware we no longer take bug reports or feature requests here?

In general are you aware we no longer take bug reports or feature requests here?

In T12959#230799, @chad wrote:

What does "mysterious" mean.

What does "mysterious" mean.

In T8238#218018, @avivey wrote:

A possible mid-term solution is to use something like using refs which aren't "tags" (Like github's /refs/pulls/xxx); I think we've discussed it didn't like it because T8092 is desired for other things too.

Unclear if this is a feature request, bug report, or general question. Going to close out as it's old and not actionable.

In the past there used to be a Browse button at the repository homepage in Diffusion. Clicking on it would show the file tree for the current branch and some extra buttons. You could then click Search to grep the file contents of the current branch.

The simplest way to approach this is probably to do double writes: start writing the new tables, switch readers over, stop writing the old tables.

This is vague and may not actually identify a problem; I don't plan to pursue it.

This seems to mostly be a matter of taste, and we already have behavior similar to the behavior of git, which seems reasonable.

See PHI14 for priority.

I am also seeing this error and am trying to work on a fix.