| ../irclogs/#mantishelp.2009-11-11.log | ||
| --- scribe started --- | 00:00 | |
| dhx_m | nuclear_eclipse: why wouldn't we want to escape '/' as part of a path? The second option to preg_quote appends additional characters to the list PHP has built in already. (http://php.net/manual/en/function.preg-quote.php) | 06:48 |
|---|---|---|
| nuclear_eclipse | dhx_m: because the second parameter to preg_quote specifies the PCRE delimiter, which in those two cases is "@", not "/" | 13:33 |
| dhx_m | I'm somewhat confused... it escapes that character throughout the string? | 13:36 |
| dhx_m | btw Google Wave is going to be fun... | 13:37 |
| dhx_m | someone has already made a Rickroll bot | 13:37 |
| dhx_m | add it to a conversation and a Rickroll video starts playing as soon as someone opens a thread | 13:38 |
| nuclear_eclipse | dhx_m: the point of preg_quote is to escape any characters that PCRE will see as special or control characters, such as ^, $, \, etc | 13:47 |
| dhx_m | forward slash is one of those however? | 13:48 |
| nuclear_eclipse | however, PCRE regexes can use any character as the start/end delimiter; / is not always needed for that, and in the cases of paths, it's always a good idea to use a different delimiter | 13:49 |
| dhx_m | ah so it takes the first character in the string and uses that as the end delimiter? | 13:49 |
| nuclear_eclipse | other than when acting as a delimiter, / has no special meaning to PCRE | 13:49 |
| nuclear_eclipse | right | 13:49 |
| dhx_m | aha gotcha | 13:49 |
| dhx_m | makes sense now :) | 13:49 |
| nuclear_eclipse | in most of Mantis, we use / as the delimiter, but for paths and URL matching, we use other characters instead, usually @ | 13:50 |
| dhx_m | yep | 13:54 |
| nuclear_eclipse | so anywho, sup? :P | 13:59 |
| dhx_m | playing with Google Wave at the moment | 14:03 |
| nuclear_eclipse | me too :P | 14:03 |
| dhx_m | I recon it's going to get abused big time | 14:03 |
| dhx_m | with the free roaming bot capabilities | 14:04 |
| dhx_m | assuming of course people engage in public waves | 14:04 |
| dhx_m | it seems you can't get two bots talking to each other forever :) | 14:05 |
| nuclear_eclipse | I didn't even realize that there were such a thing as public waves... | 14:06 |
| dhx_m | type with:public in the search bar in your inbox | 14:08 |
| kirillka | hi all | 17:41 |
| kirillka | thraxisp need invite to google wave? | 17:41 |
| kirillka | nuclear_eclipse: what version of your wordpress? | 17:48 |
| nuclear_eclipse | kirillka: for leetcode.net? | 18:13 |
| kirillka | nuclear_eclipse: yes | 18:16 |
| nuclear_eclipse | it's WordPress MU 2.8.5.2 | 18:19 |
| kirillka | nuclear_eclipse: strange. I have simple WP 2.8.5, but my site work slowly | 18:22 |
| nuclear_eclipse | I have the PHP-APC extension installed -- it makes PHP run about 10-20 times faster | 18:23 |
| kirillka | where I can read about this extension? | 18:23 |
| nuclear_eclipse | http://php.net/manual/en/book.apc.php | 18:24 |
| nuclear_eclipse | http://pecl.php.net/apc | 18:24 |
| kirillka | nuclear_eclipse: thanks | 18:24 |
| nuclear_eclipse | kirillka: if you're running debian/ubuntu linux, there's a package `php-apc` that installs it for you | 18:25 |
| kirillka | not. ASP Linux | 18:25 |
| kirillka | for now I change to CentOS | 18:25 |
| nuclear_eclipse | CentOS/Fedore/RHEL probably have a package for it as well | 18:25 |
| kirillka | nuclear_eclipse: can you test? https://sp.vester.ru/blog/ | 18:40 |
| nuclear_eclipse | "Forbidden" | 18:42 |
| nuclear_eclipse | You don't have permission to access /blog/ on this server. | 18:42 |
| kirillka | And now? | 18:44 |
| nuclear_eclipse | it's taking a while to load... | 18:45 |
| nuclear_eclipse | still loading... | 18:45 |
| kirillka | :( I don't understand why | 18:47 |
| nuclear_eclipse | kirillka: first, make sure you load the extension in your php.ini | 18:48 |
| kirillka | I add to /etc/php.d/apc.ini | 18:49 |
| nuclear_eclipse | second, try setting the apc settings in your php.ini like: | 18:49 |
| nuclear_eclipse | apc.shm_size = 64 | 18:49 |
| nuclear_eclipse | apc.shm_segments = 1 | 18:49 |
| kirillka | Version 3.1.3p1 | 18:51 |
| kirillka | MMAP Support Enabled | 18:51 |
| kirillka | MMAP File Mask no value | 18:51 |
| kirillka | Locking type pthread mutex Locks | 18:51 |
| kirillka | Revision $Revision: 286798 $ | 18:51 |
| kirillka | Build Date Nov 11 2009 20:32:23 | 18:51 |
| kirillka | apc.enabledOn | 18:52 |
| nuclear_eclipse | try visiting the apc.php page? | 18:52 |
| nuclear_eclipse | https://admin.leetcode.net/apc.php | 18:52 |
| kirillka | nuclear_eclipse: I have this page? | 18:53 |
| nuclear_eclipse | if anything, you can get it from the PEAR download | 18:54 |
| nuclear_eclipse | for me, it was available is /usr/.../php-apc/ as installed by the ubuntu package | 18:54 |
| nuclear_eclipse | /usr/share/doc/php-apc/apc.php.gz | 18:54 |
| kirillka | one sec | 18:56 |
| kirillka | https://sp.vester.ru/apc.php | 18:58 |
| kirillka | Misses: 89% | 18:59 |
| nuclear_eclipse | well, a high number of misses is expected at first, because APC starts with an empty cache | 19:00 |
| kirillka | may be. I never use cache | 19:00 |
| nuclear_eclipse | the 364 misses on my APC info page are all from right after I reloaded Apache; since then, I've had 490k hits because the pages stay in cache | 19:01 |
| CIA-9 | Mantisbt: s.mazeland * r3564e3f79008 / (16 files in 4 dirs): Merge branch 'master' of git://mantisbt.org/mantisbt | 19:03 |
| CIA-9 | Mantisbt: s.mazeland * r7fabc22be26c / (19 files in 2 dirs): Localisation updates from translatewiki.net (2009-11-11) | 19:03 |
| CIA-9 | Mantisbt: s.mazeland * r4a6f03b982f0 / (4 files in 2 dirs): Remove hard coded colon | 19:23 |
| wolog | hello, I've installed the source-integration plugin, and I've 2 warnings on top of each pages: "APPLICATION WARNING #2400: Event "EVENT_ACCOUNT_PREF_UPDATE_FORM" has not yet been declared." | 21:06 |
| nuclear_eclipse | wolog: update your mantis installation | 21:07 |
| wolog | is there a git public repository to pull from ? I only found the gitweb (but maybe I've not serched enough | 21:21 |
| nuclear_eclipse | git://mantisbt.org/mantisbt.git | 21:22 |
| * nuclear_eclipse thought that was listed somewhere... | 21:22 | |
| * nuclear_eclipse could be wrong | 21:22 | |
| daryn | http://www.mantisforge.org/dev/manual/en/developers/dev.contrib.clone.html | 21:23 |
| nuclear_eclipse | wolog: master-1.2.x is the current stable branch | 21:23 |
| nuclear_eclipse | daryn: I meant somewhere besides that | 21:23 |
| daryn | :) | 21:23 |
| nuclear_eclipse | I wouldn't expect most users to look there for info on how to pull from out git repo :P | 21:24 |
| daryn | that is linked from the mantisbt.org/development.php page though | 21:24 |
| daryn | well...not exactly...the dev guid is | 21:24 |
| wolog | I use a 1.2.0a3, but we have patched it quite a lot, still need to sort what should be reported upstream, and what is only usefull for us | 21:24 |
| nuclear_eclipse | perhaps we should be listing our public repo URI on the download page... | 21:24 |
| wolog | http://www.mantisbt.org/development.php | 21:24 |
| daryn | nuclear_eclipse: not a bad idea | 21:25 |
| wolog | the git url could be mentioned here ^ | 21:25 |
| daryn | you can get to it from there following the Mantis Bug Tracker Development Guide link but it certainly could be more obvious | 21:26 |
| wolog | +1 for the download page also, more and more I tend to use git instead of archive download, even when I not plan (at first) to hack the source | 21:27 |
| paulr | dhx_m: nuclear_eclipse moo | 22:08 |
Generated by irclog2html.py