This is still a shallow ghost of Hypershell, but I successfully deployed secure with it:

We generally don't consider a root problem of "Phabricator lacks feature" as a reason to accept a feature request. We still need to know the underlying problem.

As far as "opt-in", are you mostly concerned about performance?

As far as "opt-in", are you mostly concerned about performance?

(I'm not sure how "Compatibility Mode" and the DOM inspector are interacting, so maybe I'm just using it incorrectly.)

NOTE: Since packages do not own paths exclusively, any user can create a package on / of every repository and be allowed to force-accept every package review because their "everything" package is now a containing package for all other packages. However, they could already just remove the reviewers, so I don't think this is important. We could add options to Owners (e.g., an optional whitelist of "Stronger" packages) or something to prevent this, but I don't plan to do this. Just fire anyone abusing it.

Here's the note in PhabricatorPeopleQuery about this:

I don't think this is worth bringing upstream. It very occasionally saves users one click on an otherwise straightforward workflow, but requires significant complexity and maintenance from the upstream.

According to compatibility mode on my machine (Windows 7, IE 11, in IE10 mode), there is no crumb bug in IE10 if float: left is removed. This isn't consistent with T5902 or with other results I got (e.g., this thing says there is such a bug).

https://msdn.microsoft.com/en-us/library/dn255001(v=vs.85).aspx

why can't you test 8-10? I thought you could do that with the inspection tools?

Are you OK with this plan?

I made some effort to fix this, but without much headway:

just revert the change if you want... or fix

Thanks, Safari

D17374 makes hovercards a little bit more clear too, although that might get some design feedback still (see "Horse" here, for example):

In the future (T550) we plan to allow arc commands to use an SSH key. I'm not sure if that will reduce or increase confusion.

It is somewhat confusing to have both an SSH key access level that allows repo cloning and an arc certificate level of access that enables different features.

Ah, yes -- this is where I got off track. In my head I had conflated being able to clone the repo with having the arc certificate installed. These steps are unrelated, I understand clearly now. As long as the SSH key is added in Phabricator and the Repo is activated in Diffusion, cloning it is no problem. In this case, I thought it was the lack of arc certificate blocking me, when in was actually just that I forgot to activate the repo. Whoops. Thanks for clarifying.

You should be able to can arc install-certificate --conduit-uri=https://whatever to install a certificate for an arbitrary install with no other configuration.

Fwiw, if someone else lands here (which I just did by Googling the same error message), the problem for me was the same as for the original poster -- having not first initialized a repo locally one way or another. My intuition (which is probably wrong) is that there is an interesting order of operations problem here.

SSL Certificate, key and Ca files. Of course they can be saved as SSH keys but I don't want to mix them together.

What is your use case for API access to notes?

D17373 should fix the typo.

We used to have GraphViz support for this, but we shut it down for security reasons - see T9408.

update: We used default mount options in /etc/fstab for the disk containing repositories

noexec,noatime,nodiratime

we fixes the push logs and herald commit content hooks issues by changing it to

noatime,nodiratime

thanks!

Thanks! Your reproduction instructions were extremely clear and made hunting this down straightforward. D17372 should resolve this.

I gave the goat some leaves to eat because maybe goats eat leaves?

Those are old now I guess, I'll file something to see if @chad can fix it because I am not licensed to pixel.

Well by the time you divide false into 3600 pieces you can't have much left!

err, looks like it returns "FALSE on failure", and naturally in PHP, FALSE / 3600 is 0, so we just consider it as "UTC".

This information is obtained from your PHP, using datetimezone.getoffset(), so it's not all in our control.

Thanks, Chad!

We wrote javelin

See LICENSE for license information:

Well, upon browsing more through the source code, it appears that Phabricator is using "Javelin" javascript library which is not free software. Could you please give some more info about this?

If I want to add some code (like a script notice described in chapter 3.2.1 here: https://www.gnu.org/software/librejs/free-your-javascript.html) to the <head> before any script, where's the right place in the Phabricator code to do this?

It looks like a problem with simple JSON String and complex containing maps / array. I noticed it while using the conduit method pages itself seeing the different json syntaxes like:

$ echo '{
  "names": [
    "T1000",
    "T1002"
  ]
}' | arc call-conduit --conduit-uri https://secure.phabricator.com/ --conduit-token <conduit-token> phid.lookup

and

$ curl https://secure.phabricator.com/api/phid.lookup \
    -d api.token=api-token \
    -d names[0]=T1000 \
    -d names[1]=T1002

In addition to that it seems not quite clear which syntax to use with powershell (or other foreign clients) and which content type should be used. So for powershell it seems like there is a limitation (or issue) for JSON strings when using the default context type application/x-www-form-urlencoded.

Recently, we've started seeing a handful of attacks where human users appear to read a discussion, formulate a human-sounding, contextual reply (e.g., discussing the thread topic in what appears to be a human way, just with a very shallow understanding of the issue), and then include a link to a site offering various services (mostly essay writing?) in the footer.

Regarding what modifications I would like to see:

This setting (In the Phabricator web interface) is very old, and should exist in all versions. Ask your admin to configure it (Assuming your admin created the repository).

We migrated phabricator last months just realized somehow "Push Logs" are not generated anymore (the last push log was created just before the migration)
and I guess commit content hooks are somehow related on push logs (?)
May I ask what can I check if the push logs aren't being created?

It sounds like a legitimate bug or feature request ("making conduit calls from powershell"). Did your Ponduit library used to work and then broke when Phabricator changed something?

No unfortunately not. Doing RestAPI like web request with Powershell is a real pain in the as. JSON Strings doesn't work with some structures. Powershell JSON Conduit Discussion.

thanks all your answers

Also, please work with other KDE project members to discuss KDE priorities and needs downstream, then have a single point of contact (nominally, @bcooksley) bring them upstream once there is consensus on the nature and priority of problems. Currently, you, @abika, and @bcooksley are all independently interacting with this upstream.