Although it's very possible that this is a bug, this state also has a 72-hour internal cache which wasn't written correctly in older versions of Phabricator.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 21 2016
See T11898 for the previous iteration on this.
Please read Contributing Feature Requests carefully before filing a feature request.
Can you show me the <VirtualHost> entry you've added for Phabricator in your Apache config? I suspect you may have omitted the B flag in the RewriteRule.
Phrequent is a prototype, and we don't accept bug reports for prototypes. See User Guide: Prototype Applications for discussion.
Nov 20 2016
Nov 19 2016
General state of the world here:
$ nodejs --version v0.10.25
This should now be fixed in HEAD of master and stable.
Cool. D16901 should fix this properly. Thanks for the report!
Yeah, looks like some credential shenanigans are afoot. I instrumented the user we're actually connecting as and am getting a mixture of what I passed with -u ("trunk") and the default user ("root").
Maybe also: do you have cluster.databases configured?
If you run this from mysql directly, as root, does it work?
Nov 18 2016
I'll strip restricted handles from the "Mentions" lists.
Wow, isy is quite a productive little worker!
I can't reproduce this either. Here's what I did:
Yeah, I tend to agree. I don't really see any approaches we can take here that don't make things a little worse for experienced users who already know what they're looking for, and I'm not sure there's too much of a use case left for less-experienced users.
This is sort of what I was thinking about for the "Search Description" / "Usage Hint" (descriptions / projects are random examples):
Did you follow our installation guide, or did you follow a third-party installation guide (for example, a blog post you found somewhere on the internet)?
Pup was very well behaved while running the errands.
Nov 17 2016
Okay, whew. Losing the opportunity for that joke was really keeping me up last night.
(You could write some similar rules if you want to try something in that vein, although it's a pretty big pain to fork JS/CSS right now.)
Okay well @chad resigned from D16893 as soon as he saw animation in a CSS file so I don't think that one's going anywhere.
Alright, I'm going to try this:
The most-likely-to-work secret magic for "Not in: Wikidata" is not(wikidata):
I caught another case of this: here, "Phacility" should be first, but is not.
Oh, sorry, I meant: if security.alternate-file-domain was configured, that prevented this problem.
I'm reasonably sure that fixes it; let us know if you're still seeing issues after updating.
(This likely would not be reproducible on any instance which has security.alternate-file-domain configured, which is why it wouldn't reproduce here or in the Phacility cluster.)
This reproduces somewhat-reliably for me with Quicksand (Persistent Chat) on.
Too bad too because I was going to write a great joke about soldering port 22 to port 2222 on your motherboard.
Actually, this also means that users can't copy/paste the thing in the web UI, right? They'll need to copy "ssh://secure@secure.phabricator.com/source/phabricator.git" from the web UI, manually edit the URI to have their host alias, then execute the command?
Nov 16 2016
I made the claim that this is the easiest way because my experience is that "have all your users do something" is always harder than "do something yourself", at least in the roles I held at Facebook and here. I'd gladly solder pins on the motherboard if I didn't have to tell users to make a simple configuration change.
Ah. I believe I fixed a simpler version of that case earlier, but not the specific case you describe. D16881 should fix that case.
- D16853 tweaked one issue that I caught.
- T11881 is a followup for restoring code diffs in a small set of scenarios.
- I haven't seen other issues for a while, so I'm going to consider this resolved until they crop up. If you do run into cases where the new algorithm isn't doing a great job, let us know.
- D16877 includes the entire CLDR "windows to the rest of the world" map in things we'll recognize.
- Neither that map or the Microsoft map have "Russian Time", but maybe that's just what the UI shows for zones like "Russia Time Zone 10", and not what actually appears in the ICS file? Otherwise we're going to have to keep digging.
- D16878 fixes the form customization stuff I mentioned above, mostly by preventing quirky/confusing fields from being customized (at least, for now).
- D16879 fixes a rendering bug with "All Day" events that could shift them forward or backwards by a day.
- D16880 uses the same rendering logic for subheaders (which now appears to be correct) and tooltips (which had a different, older copy of very similar logic).
From T11878, these patterns aren't obvious:
It also occurs to me that if I needed multiple and conditions I could make a rule that did nothing but just matched those conditions,
- Editing the EditEngine default form and removing "Host" means that "Host" no longer prefills. This is the same as T10222. A temporary workaround would be to prevent that field from being defaulted. It should be defaultable in the long run, but is probably low-value to assign a default to, so it's probably better to just lock it for now and make it behave a little more sensibly.
Some other stuff:
epriestley's "Another herald rule" condition does not solve the problem.
No, there's no specific support for LFS mirroring yet.
Configure ArcanistTextLinter, which can detect and automatically correct these errors:
Oh, sorry! I added you to Community so you should now have edit power.
Why doesn't this work?
Nov 15 2016
You can already do this with the "Another Herald Rule" condition.
Feature requests require a root problem description (see Contributing Feature Requests and Describing Root Problems). Feel free to file a new feature request completely describing your root problem. If you do, please read all of the documentation carefully first: it lays out exactly what information we need to move forward on a feature request.
It would be great, if this would not be necessary.