I think this behavior is reasonable as-is.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Dec 11 2015
See Contributing Feature Requests. If you're aren't sure what we mean by a "root problem", see Describing Root Problems.
No idea how to reproduce, no other reports.
Dec 10 2015
This behavior should be more reasonable at HEAD. In particular:
After D14737, we will now show this information in the UI if it's available. Here are the requirements:
This should be fixed at HEAD. Let us know if we missed anything or if you run into anything else. Thanks for the report!
Someone actually wants this, so I'll configure it during the deploy on Saturday.
Thanks for checking, that's quite helpful.
I don't know how exactly, but this error is related to T1116. Basically, adding this code fixes the described issue:
Ah. Yes, I agree.
I don't think that string is one of ours. Does it appear in flarc?
Hmm, actually... I think this is the fault of a custom extension I am using to upload files to S3.
- -c seems to come from 1.7.2.
- --no-color and --color=never are probably two acceptable alternative methods for writing -c color.ui=never.
- --no-column seems to be an acceptable alternative for writing -c column.ui=never, but may not have existed until 1.7.11.
Wording on this feed story isn't quite right, not sure if that's new or not:
"Close" makes sense to me. And, yeah, I agree that long-term some kind of "All Badges" link that leads to, like:
If you know you had three badges yesterday and then visit your profile and see only two badges, there's no way to figure out what happened (without examining the edit history of every badge), if we completely hide them, is there?
The Git issues have been resolved (see T9657).
This has been live for about a month without any major issues cropping up.
Resolved by D14420.
Broad update here after T9132:
No problem -- it's easier for us to merge duplicates than split tasks apart, so it's not bad to err on the side of filing new tasks.
I'm going to close this out since the infrastructure work it describes is now substantially complete, although a great deal of work remains to be done to bring this infrastructure to all applications and implement the full set of features it enables (mostly described in tasks blocked by this one).
I'm going to merge this into T9491, since that's the existing task covering the primary issue here.
First approaches that come to mind, for whatever that's worth:
Dec 9 2015
To clarify, you want Phabricator to turn you into a sandwich?
I ultimately expanded the scope here into a lot of adjacent work in T9132, but a rough version of "better templating" is now available in HEAD and deployed and configured on this server. There's documentation here:
I think this is probably not something we're going to fix.
mysql> SELECT u.username User, p.name Project, IF(f.id IS NULL, "NO", "YES") "Has MFA" FROM local_user.user u LEFT JOIN local_user.edge ue ON ue.src = u.phid AND ue.type = 14 LEFT JOIN local_project.project p ON ue.dst = p.phid LEFT JOIN local_auth.auth_factorconfig f ON f.userPHID = u.phid WHERE p.name = 'Dog Project'; +------+-------------+---------+ | User | Project | Has MFA | +------+-------------+---------+ | dog | Dog Project | NO | +------+-------------+---------+ 1 row in set (0.00 sec)
Ah, okay. I'm not sure what's going on there. I can't immediately reproduce that.
Nothing happened (was added to the text area)