Get a valid certificate or configure your system to trust your self-signed certificate. This is not a problem with Phabricator and I do not plan to support insecure SSL configurations in the upstream.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 11 2016
Jan 10 2016
Jan 9 2016
No. Several organizations maintain private projects on this install which they use to express interest in various features to the Phabricator upstream and keep track of relevant changes and progress. One such organization is interested in this feature. It is now more likely that this feature will see the light of day, as it has a powerful enterprise backing it in some capacity.
Restricted Project means you don't have permissions to view that specific Project.
Does "Restricted project" now mean that this feature is no longer considered for the open source Phabricator?
I think all of this is fixed at HEAD.
Jan 8 2016
For reference, this repository name input:
I think it's correct that we're very conservative about destroying data. It would be incredibly bad to remove something important because a user set repository.default-local-path to something silly like /home/important_files/ and we decided to destroy /home/important_files/CRITICAL/ because it wasn't a repository.
I can't reproduce this, nor do we have reports from other users. See Contributing Bug Reports.
See also "Sticky Accept" here:
The upstream discussion of this issue starts with "Chain of Custody" here: T182#133871
Jan 7 2016
Thanks for your response, and I agree. The rare inconvience of reverting a change that someone put in abusing the system is far less then the annoyance of having to wait for a minor change to complete the review or waiting for reviewers to approve as I make a minor change.
You mean from a Harbormaster Lease Working Copy perspective or a Land Revision perspective (when it comes to nonsensical UI).
Not currently possible. Two quick thoughts.
I actually think failing universally like that is probably fine (you can --skip-staging anyway, as long as the error tells you about it) but the UI behavior in Phabricator itself is frequently nonsensical (we basically guess that the staging area probably exists and proceed blindly).
We have patched around this issue locally with: