We truncate these summaries at 80 bytes because the underlying storage column is text80, which is only 80 bytes long when represented using binary collation in older MySQL without utf8mb4 support. We can not store more text in the general case without changing this column size.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Aug 9 2016
The other thing that was confusing was that "Config" didn't actually have all the settings -- some settings are in Config, some user settings are in my "profile", some other settings are in individual apps. It would help to consolidate these into one directory.
I was experiencing this problem too and it works in current stable for me now.
Aug 8 2016
Aug 7 2016
Aug 5 2016
Aug 4 2016
I actually encouter the same problem. Setting autoclose on master only fixed it.
Update past rPa5b26104 (Jul 9).
Sorry I missed the previous notification.
Closing this since we haven't seen a response for about a week, this report didn't follow the instructions by omitting version information, and it's very likely that this is resolved by updating.
Aug 2 2016
If you can identify why sudo was broken and what you did to fix it, we can probably add a setup warning to test for this problem. However, since we haven't seen other users with broken sudo and we couldn't help users resolve the issue with available information even if we did detect it, I don't think pursuing a check in the upstream is worthwhile.
Sounds like this is resolved? Or should we attempt to catch this case?
Jul 31 2016
See also T11401, although this started life as a Pholio task and that's now a code-specific UI task so I don't know if they're actually the same.
See Planning for help understanding timelines and priorities.
Is this still actively being worked on, is there a different solution than View Options->Set Tab Width, or should I apply the patch referenced by raman.rathod?
Jul 29 2016
Jul 24 2016
I ran into the same issue and phabricator-ssh-hook.sh and its parent directory are owned by root and the script have 755 mode. The script was in /root/phabricator/ and vcs-user doesn't have access to that directory (because the /root directory is not accessible). I put the script in /etc/phabricator and it worked.
Jul 21 2016
Jul 18 2016
Jul 16 2016
Per T7047#180833, no idea what the use case is for per-user/per-Herald/per-Mail.
Jul 15 2016
T11335 talks about a hosting system (gitblit) that adds meta-data to refs/meta/ refs, which show up in phabricator as real commits.
Jul 14 2016
Hey guys, where should I hook my custom parser if I need to add any additional behaviour on 'CodeReviewed' keyword in commit message due to parsing from repository?
Actually I need to mark commit as audited when commit message contains previously specified string.
Jul 13 2016
Thanks for listening to my hair-brained schemes. Yeah, the motivation is totally clear to me FWIW, and thinking about it more, I strongly suggest this is related to T9161.
Needs a check for empty and at least a better error message in DiffusionBrowseQueryConduitAPIMethod.php:115
We are seeing this as well when attempting to browse an empty commit: https://phabricator.wikimedia.org/T140236
Jul 12 2016
We could also possibly just drop these commit mails in all cases where no audit triggered. It's easy to write a Herald rule to restore them if you do want them. Possibly involved enough to be adjacent to T10978, though.
A small part of the motivation for this change was to make commits reachable only from Gerrit magic refs (refs/changes/..., similar to refs/pull/...) visible in Diffusion. This didn't really make it into a single upstream task I think, but some of this is scattered across T9726 / T6878. So we have at least one use case where users want these refs to exist and be treated roughly like they were tags/branches.
Jul 10 2016
I deployed that stuff to the affected shard and things look OK now. The original issue described in this task wasn't affected.
This didn't really end up being related to the other issue here (streaming huge diffs into Files) but it's a little late for me to split it out now.
This is largely the result of --find-copies-harder being explosively slow for large result sets in large repositories. With this flag, the runtime rises from <1s to >3m, at which point git itself bails out:
This is actually happening on the cluster/daemon pathway so it's not really related to the original issue here. However, the daemon client is timing out:
I suspended the instance in question since it was a test instance, and continuing to generate web requests for the 5M-line diff and disrupt other processes on the shard.
We had a shard disruption in the cluster this morning that I don't have a clear smoking gun on, but one issue that looks questionable is on this pathway -- I see several requests to generate diffs of an extremely large (5M line) commit coming from the web.
Jul 9 2016
Doesn't reproduce in any mobile browser (Safari, Chrome) I have access to. Presume resolved, but if still occurring please re-open with full reproduction steps.
Jul 8 2016
This is purely hypothetical and it's hard for me to imagine users getting it wrong by accident.
I can't think of any reason it would ask that unless something changed locally. If you have no local changes to phabricator/, just reset to HEAD.
@chad I don't know, I installed phabricator under the direction of doc and then resolved some setup Issues.
Jul 7 2016
You are right, it does not specifically describe or refer to an import button anywhere.
Okay, but the docs don't actually describe or refer to an import button anywhere -- there's no text like "click the import button" that I missed when updating things?
In T11278#184475, @epriestley wrote:Another issue is that when following the user docs, the docs still points towards having the import button on the creation of project.
I can't find where we say this in the documentation. Can you point me at what you're seeing?
Why do you have local changes in your phabricator folder?
Sorry to trouble you @epriestley , I have the same question(T11273) . After your committing rP5ffdb732735c, I tried to update my phabricator under the direction of doc(https://secure.phabricator.com/book/phabricator/article/upgrading/). While I executed git pull,the terminal shows
. So should I commit local changes or checkout them?Jul 6 2016
Another issue is that when following the user docs, the docs still points towards having the import button on the creation of project.
I'm leaning toward just adding a big "Clippy" element to this UI:
I think if you haven't activated the repository and visit URIs, we can show an "Import" type note and call it a day for now.
Yeah, I think it goes away after you push "activate"
Is that text already present and I just missed it?
We can probably start with a text hint on this view:
Another issue is that when following the user docs, the docs still points towards having the import button on the creation of project. I was pretty confused as it clearly wasn't that. Perhaps the page after clicking the 'Create Repository' could have an option of importing, which presets the values to observe a repo.
I was confused at first - from previous workflow I thought I took a wrong step when setting up the repository and landed on a "completed" repository page which I didn't expect without selecting host vs. mirror. I deleted the repository and started again and finally got it after hours of turmoil (maybe more like a minute of prodding).
yeah doesn't import ssh from what I see and they just say to use the command-line importer if you can't use the web tool
Here's what I see -- step 1:
I get this screen:
GitHub's import doesn't seem to work with any repositories that require credentials?
Oh, I was looking at this:
GitHub make this reasonably obvious.
People keep getting stuck on this, so we should look at fixing the UI so we don't have to post the documentation over and over.
Jul 5 2016
Thanks for the report! I believe this should now be resolved in HEAD of master.
Yes, commit/revision and commit/task relationships can now be managed manually from the web UI.
I'm pretty sure this is fixed now with the Edit Related Objects menu awesomeness! Thanks.
Thanks for the quick response. I'll let you know as soon as the change gets merged into stable.
