- User Since
- Jan 13 2012, 11:20 PM (266 w, 6 d)
Tue, Feb 21
@epriestley The import has finished, but some commits show as importing still?
Sun, Feb 19
We once rendered these renames like this:new/path/to/file.c Moved From: old/path/to/file.c
Personally I like that, I think a compromise to make it easier to consume, would be to try and group the moves together and showing the relation, for example
a -> b -> a <- b <-
a -> a <- b -> b <-
Mon, Feb 6
Fri, Feb 3
Sat, Jan 28
That error makes sense,
Thu, Jan 26
@epriestley you don't want to know what schools teach/accept now-adays... is very scary.
Jan 23 2017
Jan 13 2017
Jan 8 2017
I expect it to work, because it looks like it is supposed to:
Dec 15 2016
Dec 9 2016
Nov 3 2016
Jul 5 2016
Of course! Thanks for poking around!
Jul 4 2016
Im really not sure, when I run restart this is what my daemon page looks like:
Jun 17 2016
May 7 2016
Apr 19 2016
Apr 16 2016
Yea, so I think the path forward is to check the version of WS and to add some docs about it in the aphlict changes, and just the general updating guide.
Apr 15 2016
Fixes the issue on my end! :D
Apr 12 2016
Yea, I definitely would not recommend that,
then again using http instead of https isn't great either (its sent in plaintext anyway, regardless if you include it in the url or not)
I was playing with it and made a "Give me your money for free" Fund and now... I regret that...
Can you try:
We should probably substitute in "Unknown Ghost" then.
Fair enough, I will do that now.
It seems this no longer is working correctly:
Apr 8 2016
Apr 5 2016
Mar 18 2016
I had this same issue, I had to dig into the db to remove the duplicate phids
Mar 7 2016
Ah, makes sense.
Mar 1 2016
Feb 24 2016
Feb 23 2016
I just ran into a fun issue that @avivey helped me figure out,
Dec 22 2015
Dec 9 2015
I can't seem to repro it either, might have been the issue with the edit route you fixed?
Let me clarify,
I can't edit my own task... it 404's
Dec 5 2015
That is hypothetical, but for example, lets say Evan publishes a post with the following:
but really meant for the slug to be
The easiest thing I can think of is simple typos/ bad c&p job
I have a concern about the /blog/<postid>/ignored_post_title/ approach, if the blog is indexed by Google, /blog/<postid>/ignored_post_title/ and /blog/<postid>/derpa/ will have the exact same content which Google penalizes.
Nov 30 2015
When I have some time Ill implement a new DataCacheSpec, I chatted in ##php and asked about the OPCache, its enabled by default (like in PHP 5.5+) and there is currently no other available caching extensions.
Nov 26 2015
You have the path to the library directory twice, print out the variables
that you use in the md5 function.
Nov 25 2015
If you look at the error message and the path you can see what the issue is:
Nov 24 2015
Drupal ran into a similar issue with APC not existing when they try to run APC unit tests.
Re-run arc unit
Nov 23 2015
I wonder if instead of "Comment", "Justification" might have more use in certain cases? (why not both! "Comment/Justification")
Nov 19 2015
I don't think that is going to work here are some things I pulled from the extension migration page (unless we ifdef large blocks of code):
- PHPNG doesn't require any involvement of pointers to pointers to zval. Most occurrences of zval** variables and parameters have to be changed into zval*. The corresponding Z_*_PP() macros that work with such variables should be changed into Z_*_P().
- In many places PHPNG work with zval directly (eliminating need for allocation and deallocation). In these cases corresponding zval* variable should be converted into plain zval, macros that use this variable from Z_*P() into Z_*() and corresponding creation macros from ZVAL_*(var, …) into ZVAL_*(&var, …). Be always careful about passing addresses of zval and & operator. PHPNG almost never require passing address of zval*. In some places & operator should be removed.
- zval allocation macros ALLOC_ZVAL, ALLOC_INIT_ZVAL, MAKE_STD_ZVAL are removed. In most cases their usage indicate that zval* need to be changed into plain zval. Macro INIT_PZVAL is removed as well and its usages in most cases should be just removed.
Nov 18 2015
@epriestley, due to the fact that the Zend APIs for PHP7+ are different than those in PHP5* how should changes to XHProf be submitted so we don't break stuff?
Nov 17 2015
Nov 16 2015
I for-see what @revi stated above as a pretty plausible scenario, even the looking over someones shoulder is a plausible scenario.
Nov 13 2015
So I just did some googling and came across the RFC for MFA, and this is
taken from the RFC:
Yea, im getting the same results as chad, tested on php 5.6, and php7 is super fast.
I think this is more to conform with what everyone else does, I know Google and Apple don't let you re-use tokens even if they are still in the valid timeframe, not sure if there are specific reasons behind that besides the attack you came up with above.
Nov 9 2015
Nov 3 2015
This is probably geared towards more public installs, where short urls could be abused, (such as this one).
Nov 2 2015
I guess the question is:
+1, especially with all the new types in PHP7 this would be awesome.
Oct 30 2015
I really hoped that this allowed the ability to spin memes, but I was disappointed
Oct 29 2015
You can find info on authorizations here: https://secure.phabricator.com/book/phabricator/article/drydock_blueprints/ and here: https://secure.phabricator.com/book/phabricator/article/drydock_security/
That commit is from October 8th, have you tried updating to HEAD?