Bug #54957 [Asn->Csd]: Memleak in alloc_globals_ctor

2011-05-31 Thread dmitry
Edit report at http://bugs.php.net/bug.php?id=54957&edit=1

 ID: 54957
 Updated by: dmi...@php.net
 Reported by:fel...@php.net
 Summary:Memleak in alloc_globals_ctor
-Status: Assigned
+Status: Closed
 Type:   Bug
 Package:Scripting Engine problem
 PHP Version:5.4, trunk
 Assigned To:dmitry
 Block user comment: N
 Private report: N

 New Comment:

This bug has been fixed in SVN.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
 
Thank you for the report, and for helping us make PHP better.




Previous Comments:

[2011-05-31 10:26:55] dmi...@php.net

Automatic comment from SVN on behalf of dmitry
Revision: http://svn.php.net/viewvc/?view=revision&revision=311627
Log: Fixed bug #54957 (Memleak in alloc_globals_ctor)


[2011-05-31 01:56:03] fel...@php.net

Description:

A memory leak happens when using ZTS+USE_ZEND_ALLOC=0 

Test script:
---
$ USE_ZEND_ALLOC=0 valgrind --tool=memcheck --leak-check=yes 
sapi/cli/php -v

==17712== Memcheck, a memory error detector

==17712== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et
al.

==17712== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for
copyright info

==17712== Command: sapi/cli/php -v

==17712== 

PHP 5.5.0-dev (cli) (built: May 30 2011 18:37:59) (DEBUG)

Copyright (c) 1997-2011 The PHP Group

Zend Engine v2.4.0, Copyright (c) 1998-2011 Zend Technologies

==17712== 

==17712== HEAP SUMMARY:

==17712== in use at exit: 604 bytes in 1 blocks

==17712==   total heap usage: 19,354 allocs, 19,353 frees, 1,466,000
bytes allocated

==17712== 

==17712== 604 bytes in 1 blocks are definitely lost in loss record 1 of
1

==17712==at 0x4023F50: malloc (vg_replace_malloc.c:236)

==17712==by 0x8429867: alloc_globals_ctor (zend_alloc.c:2633)

==17712==by 0x83C103F: ts_allocate_id (TSRM.c:255)

==17712==by 0x8429917: start_memory_manager (zend_alloc.c:2654)

==17712==by 0x845D1A4: zend_startup (zend.c:642)

==17712==by 0x83C893A: php_module_startup (main.c:1901)

==17712==by 0x85A479B: php_cli_startup (php_cli.c:414)

==17712==by 0x85A567B: main (php_cli.c:790)

==17712== 

==17712== LEAK SUMMARY:

==17712==definitely lost: 604 bytes in 1 blocks

==17712==indirectly lost: 0 bytes in 0 blocks

==17712==  possibly lost: 0 bytes in 0 blocks

==17712==still reachable: 0 bytes in 0 blocks

==17712== suppressed: 0 bytes in 0 blocks

==17712== 

==17712== For counts of detected and suppressed errors, rerun with: -v

==17712== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 34 from
9)









-- 
Edit this bug report at http://bugs.php.net/bug.php?id=54957&edit=1


Bug #54478 [Opn->Csd]: The pdo_pgsql specific implementation of inTransaction doesn't work as expected

2011-05-31 Thread iliaa
Edit report at http://bugs.php.net/bug.php?id=54478&edit=1

 ID: 54478
 Updated by: il...@php.net
 Reported by:phofstetter at sensational dot ch
 Summary:The pdo_pgsql specific implementation of
 inTransaction doesn't work as expected
-Status: Open
+Status: Closed
 Type:   Bug
 Package:PDO related
 Operating System:   OSX, Linux, likely all
 PHP Version:5.3.6
-Assigned To:
+Assigned To:iliaa
 Block user comment: N
 Private report: N

 New Comment:

This bug has been fixed in SVN.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
 
Thank you for the report, and for helping us make PHP better.




Previous Comments:

[2011-04-06 15:15:40] phofstetter at sensational dot ch

A bit of investigation revealed that the feature was removed in 300464



http://svn.php.net/viewvc?view=revision&revision=300464



I guess the unit test should be removed too, as well as the note in the
manual 

which states "Note that currently only the PostgreSQL driver implements
this 

method."


[2011-04-06 14:59:11] phofstetter at sensational dot ch

Description:

PHP 5.3.3 supposedly brought PDO::inTransaction() with a special
implementation 

for PostgreSQL wich uses libpq's PQtransactionStatus instead of internal


bookkeeping.



According to the test attached with the revision where this was added 

(is_in_transaction.phpt, revision 300351), inTransaction() is supposed
to return 

any of the PGSQL_TRANSACTION_* constants.



Unfortunately that's not the case and inTransaction(), even when used in


conjunction with PostgreSQL only returns boolean and doesn't use the
actual 

transaction status of the connection but just returns true or false
depending on 

whether PDO::beginTransaction() has been called or not.



PHP's own test runner illustrates the problem, which is why I don't
bother 

adding an additional test script - the included is_in_transaction.phpt
is 

enough:



http://gcov.php.net/viewer.php?

version=PHP_5_3&func=tests&file=ext%2Fpdo_pgsql%2Ftests%2Fis_in_transaction.phpt

Expected result:

When running the phpt file, I expect the following output:



Test PDO::PGSQL_TRANSACTION_INTRANS

int(2)

Test PDO::PGSQL_TRANSACTION_IDLE

int(0)

Test PDO::PGSQL_TRANSACTION_INERROR

int(3)

Test PDO::PGSQL_TRANSACTION_IDLE

int(0)



Actual result:
--
When running the phpt file, I (and PHP's webbased test runner) is
getting





Test PDO::PGSQL_TRANSACTION_INTRANS

int(1)

Test PDO::PGSQL_TRANSACTION_IDLE

int(0)

Test PDO::PGSQL_TRANSACTION_INERROR

int(1)

Test PDO::PGSQL_TRANSACTION_IDLE

int(0)








-- 
Edit this bug report at http://bugs.php.net/bug.php?id=54478&edit=1


Bug #54910 [Asn->Csd]: Crash when calling call_user_func with unknown function name

2011-05-31 Thread dmitry
Edit report at http://bugs.php.net/bug.php?id=54910&edit=1

 ID: 54910
 Updated by: dmi...@php.net
 Reported by:aigors at inbox dot lv
 Summary:Crash when calling call_user_func with unknown
 function name
-Status: Assigned
+Status: Closed
 Type:   Bug
 Package:Reproducible crash
 Operating System:   Ubuntu 11.04
 PHP Version:5.3.6
 Assigned To:dmitry
 Block user comment: N
 Private report: N

 New Comment:

This bug has been fixed in SVN.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
 
Thank you for the report, and for helping us make PHP better.




Previous Comments:

[2011-05-31 11:20:53] dmi...@php.net

Automatic comment from SVN on behalf of dmitry
Revision: http://svn.php.net/viewvc/?view=revision&revision=311635
Log: Fixed bug #54910 (Crash when calling call_user_func with unknown
function name)


[2011-05-23 16:18:09] aigors at inbox dot lv

Description:

Firstly the function is_callable(array('B', 'noSuchMethod')) returns
true even 

such static method does not exist. This could be caused by class A
having magic 

method __call (which shouldn't accept static methods though).



Still because of this the code fails with segmentation fault.

Test script:
---
class A

{

public function __call($method, $args)

{

if (stripos($method, 'get') === 0) {

return $this->get();

}



throw new BadMethodCallException("No such method");

}



protected function get()

{

$class = get_class($this);

$call = array($class, 'noSuchMethod');



if (is_callable($call)) {

call_user_func($call);

}

}



}



class B extends A {}



$input = new B();

echo $input->getEmail();



Expected result:

Script should end with no output.

Actual result:
--
Segmentation fault.






-- 
Edit this bug report at http://bugs.php.net/bug.php?id=54910&edit=1


Bug #29500 [Com]: Accessing object elements returns object

2011-05-31 Thread stu at dyndev dot co dot nz
Edit report at http://bugs.php.net/bug.php?id=29500&edit=1

 ID: 29500
 Comment by: stu at dyndev dot co dot nz
 Reported by:lists at cyberlot dot net
 Summary:Accessing object elements returns object
 Status: Wont fix
 Type:   Bug
 Package:SimpleXML related
 Operating System:   Fedora Core 2
 PHP Version:5.0.0
 Block user comment: N
 Private report: N

 New Comment:

This intentional bug is still there, I cannot for the life of me see why
it would be that way or why it's still not documented all these years
later.


Previous Comments:

[2004-08-03 15:39:41] lists at cyberlot dot net

Ok it is impossible to modify the simpleobject once creating which means
you can't add anything to the xml.



Is this a desired affect as well?


[2004-08-03 15:29:03] lists at cyberlot dot net

Im not signed up for that list...

The online docs badly need updating then.



1. To express the need to use typecasting depending on how you access
the variable.



2. That you can no longer "change" the simplexml object like explained
in example 7


[2004-08-03 12:01:13] chr...@php.net

That's by design and was discussed on 

intern...@lists.php.net


[2004-08-03 05:23:22] lists at cyberlot dot net

http://us3.php.net/manual/en/ref.simplexml.php



In trying to get this working I played with the examples from this
page.



Example 7 returns the following error

Fatal error: Objects used as arrays in post/pre increment/decrement must
return values by reference in /root/test.php on line 29


[2004-08-03 05:15:42] lists at cyberlot dot net

Description:

When using simplexml to access a element the returned object it returns
a object instead of a string



Have to type cast it as a (string) to get the information back, Should
not have to typecast.



If a typecast is required it should be specificed in the docs.

Reproduce code:
---
$string = <<



login

Richard



XML;


   

$xml = simplexml_load_string($string);

print_r($xml);

$login = $xml->login;

print_r($login);

$login = (string) $xml->login;

print_r($login);



Expected result:

SimpleXMLElement Object

(

[cmd] => login

[login] => Richard

)

Richard

Richard

Actual result:
--
SimpleXMLElement Object

(

[cmd] => login

[login] => Richard

)

SimpleXMLElement Object

(

[0] => Richard

)

Richard






-- 
Edit this bug report at http://bugs.php.net/bug.php?id=29500&edit=1


Bug #53756 [Opn->Bgs]: Unable to insert serialized objects with private variables in pgsql

2011-05-31 Thread iliaa
Edit report at http://bugs.php.net/bug.php?id=53756&edit=1

 ID: 53756
 Updated by: il...@php.net
 Reported by:admin at webdesignforall dot net
 Summary:Unable to insert serialized objects with private
 variables in pgsql
-Status: Open
+Status: Bogus
 Type:   Bug
 Package:PDO related
 Operating System:   Ubuntu 10.04 32 bit
 PHP Version:5.3.5
 Block user comment: N
 Private report: N

 New Comment:

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php

Serialized content of private/protected properties contain \0 inside the


generated string. This causes truncation, to avoid it you need to change
the 

column type to binary and write data as a binary string.


Previous Comments:

[2011-01-15 11:27:21] admin at webdesignforall dot net

Description:

Using php 5.3.5 with pdo_pgsql and pgsql 9.0.2 when inserting serialized
objects 

that contain private variables the serialized string is truncate as soon
as it 

hits the private variable.



Objects that do not contain private variables work fine.



When using the pdo_mysql driver it also works fine.

Test script:
---
exec('CREATE TABLE test (data TEXT)');

$s=$q->prepare("INSERT INTO test VALUES(?)");

$s->bindValue(1,$foo);

$s->execute();

$s=$q->query("SELECT * FROM test");

var_dump($s->fetchAll(PDO::FETCH_ASSOC),$foo);

Expected result:

array(1) {

  [0]=>

  array(1) {

["data"]=>

string(32) "O:3:"foo":1:{s:9:"foo_var";N;}"

  }

}

string(32) "O:3:"foo":1:{s:9:"foo_var";N;}"



Actual result:
--
array(1) {

  [0]=>

  array(1) {

["data"]=>

string(18) "O:3:"foo":1:{s:9:""

  }

}

string(32) "O:3:"foo":1:{s:9:"foo_var";N;}"








-- 
Edit this bug report at http://bugs.php.net/bug.php?id=53756&edit=1


[PHP-BUG] Bug #54962 [NEW]: either real_connect or ssl_set is not working properly

2011-05-31 Thread sukarna_0 at yahoo dot co dot in
From: 
Operating system: CentOS5.5
PHP version:  5.3SVN-2011-05-31 (snap)
Package:  MySQLi related
Bug Type: Bug
Bug description:either real_connect or ssl_set is not working properly

Description:

I have a code as follows.



$ssl_ca = 'https://rds.amazonaws.com/doc/mysql-ssl-ca-cert.pem';

$mysqli->ssl_set(null, null, $ssl_ca, null, null);

$result = $mysqli->real_connect($location, $usr, $password, $dbname, $port,
null, MYSQLI_CLIENT_SSL);



This code works with PHP 5.3.5 in windowsXP sp3 and never throws any error
even if $ssl_ca contains a wrong path.



And this code always throws error- '(HY000/2026): SSL connection error' in
CentOS 5.5 32bit(PHP 5.3.5)


-- 
Edit bug report at http://bugs.php.net/bug.php?id=54962&edit=1
-- 
Try a snapshot (PHP 5.2):
http://bugs.php.net/fix.php?id=54962&r=trysnapshot52
Try a snapshot (PHP 5.3):
http://bugs.php.net/fix.php?id=54962&r=trysnapshot53
Try a snapshot (trunk):  
http://bugs.php.net/fix.php?id=54962&r=trysnapshottrunk
Fixed in SVN:
http://bugs.php.net/fix.php?id=54962&r=fixed
Fixed in SVN and need be documented: 
http://bugs.php.net/fix.php?id=54962&r=needdocs
Fixed in release:
http://bugs.php.net/fix.php?id=54962&r=alreadyfixed
Need backtrace:  
http://bugs.php.net/fix.php?id=54962&r=needtrace
Need Reproduce Script:   
http://bugs.php.net/fix.php?id=54962&r=needscript
Try newer version:   
http://bugs.php.net/fix.php?id=54962&r=oldversion
Not developer issue: 
http://bugs.php.net/fix.php?id=54962&r=support
Expected behavior:   
http://bugs.php.net/fix.php?id=54962&r=notwrong
Not enough info: 
http://bugs.php.net/fix.php?id=54962&r=notenoughinfo
Submitted twice: 
http://bugs.php.net/fix.php?id=54962&r=submittedtwice
register_globals:
http://bugs.php.net/fix.php?id=54962&r=globals
PHP 4 support discontinued:  http://bugs.php.net/fix.php?id=54962&r=php4
Daylight Savings:http://bugs.php.net/fix.php?id=54962&r=dst
IIS Stability:   
http://bugs.php.net/fix.php?id=54962&r=isapi
Install GNU Sed: 
http://bugs.php.net/fix.php?id=54962&r=gnused
Floating point limitations:  
http://bugs.php.net/fix.php?id=54962&r=float
No Zend Extensions:  
http://bugs.php.net/fix.php?id=54962&r=nozend
MySQL Configuration Error:   
http://bugs.php.net/fix.php?id=54962&r=mysqlcfg



Bug #52924 [Asn->Bgs]: resource type set to empty after bad mcrypt_generic_init call

2011-05-31 Thread iliaa
Edit report at http://bugs.php.net/bug.php?id=52924&edit=1

 ID: 52924
 Updated by: il...@php.net
 Reported by:terrafr...@php.net
 Summary:resource type set to empty after bad
 mcrypt_generic_init call
-Status: Assigned
+Status: Bogus
 Type:   Bug
 Package:mcrypt related
 Operating System:   Windows 7
 PHP Version:5.3.3
 Assigned To:derick
 Block user comment: N
 Private report: N

 New Comment:

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php




Previous Comments:

[2010-09-27 23:54:20] fel...@php.net

According to the code, this is required to prevent possible crash.



See:

result = mcrypt_generic_init(pm->td, key_s, key_size, iv_s);



/* If this function fails, close the mcrypt module to prevent crashes

 * when further functions want to access this resource */

if (result < 0) {

zend_list_delete(Z_LVAL_P(mcryptind));


[2010-09-25 21:51:19] terrafr...@php.net

Description:

Calling mcrypt_generic_init() with bad values changes the resource type
from mcrypt to Unknown.  It seems like what should happen is that the
resource type should remain the same and that mcrypt_generic_init should
simply do nothing.  Maybe output a warning (as it currently does) but
not change the resource type.



A bad call to curl_setopt(), for example, doesn't change the resource
type from curl to Unknown as demonstrated thusly:







Per that it doesn't seem like a bad call to mcrypt_generic_init() ought
to change anything either.

Test script:
---


Expected result:

resource(4) of type (mcrypt)

Actual result:
--
resource(4) of type (Unknown)






-- 
Edit this bug report at http://bugs.php.net/bug.php?id=52924&edit=1


Bug #54832 [Ctl]: unable to connect to mysql

2011-05-31 Thread giorgio dot liscio at email dot it
Edit report at http://bugs.php.net/bug.php?id=54832&edit=1

 ID: 54832
 User updated by:giorgio dot liscio at email dot it
 Reported by:giorgio dot liscio at email dot it
 Summary:unable to connect to mysql
 Status: Critical
 Type:   Bug
 Package:MySQL related
 Operating System:   windows 7 x64 ultimate
-PHP Version:5.4.0-dev
+PHP Version:5.3.7
 Assigned To:cataphract
 Block user comment: N
 Private report: N

 New Comment:

changed version according to what neweracracker at gmail dot com says

thank you in advance for fixing this

byes


Previous Comments:

[2011-05-31 02:38:47] paj...@php.net

Pls check this one as well, regression introduced by the browswer fix
(wondering 

what can cause that in mysql/socket code.)


[2011-05-31 02:21:07] neweracracker at gmail dot com

Yes. I can reproduce the problem.

I am sure devs will fix then when they have time available.


[2011-05-30 21:28:38] giorgio dot liscio at email dot it

can you reproduce the problem?


[2011-05-30 17:19:09] neweracracker at gmail dot com

Hello,



There is a similar bug:

bug #54896



It is related to this commit

svn.php.net/viewvc?view=revision&revision=310691



Thank you.


[2011-05-26 16:47:40] giorgio dot liscio at email dot it

yes i've tried with 127.0.0.1



wireshark can't capture localhost packets due to a windows limitation
:rage:



i have to try in my network, i will update you



thank you




The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

http://bugs.php.net/bug.php?id=54832


-- 
Edit this bug report at http://bugs.php.net/bug.php?id=54832&edit=1


Bug #54617 [Opn->Bgs]: inconsistent enclosure of characters in str_getcsv

2011-05-31 Thread iliaa
Edit report at http://bugs.php.net/bug.php?id=54617&edit=1

 ID: 54617
 Updated by: il...@php.net
 Reported by:mike dot reinstein at freecause dot com
 Summary:inconsistent enclosure of characters in str_getcsv
-Status: Open
+Status: Bogus
 Type:   Bug
 Package:Strings related
 Operating System:   centos, but probably others
 PHP Version:5.3.6
 Block user comment: N
 Private report: N

 New Comment:

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php




Previous Comments:

[2011-04-28 00:57:06] mike dot reinstein at freecause dot com

oops, code for example 2 is wrong. should be:



$input2 = "hey, \"let's\" see how, this works";

$result2 = str_getcsv($input2, ',', '"', '"');

print_r($result2);


[2011-04-28 00:55:20] mike dot reinstein at freecause dot com

Description:

str_getcsv will enclose strings differently depending on the contents of
the input 

string. See the test script below for replication.

Test script:
---
$input = "hey, and\"let's\" see how, this works";

$result = str_getcsv($input, ',', '"', '"');

print_r($result);



$input2 = "hey, \"let's\" see how, this works";

$result2 = str_getcsv($input, ',', '"', '"');

print_r($result2);



Expected result:

Here's the output:



Array

(

[0] => hey

[1] => and"let's" see how

[2] => this works

)

Array

(

[0] => hey

[1] => let's see how

[2] => this works

)





Actual result:
--
Array

(

[0] => hey

[1] => and"let's" see how

[2] => this works

)

Array

(

[0] => hey

[1] => "let's" see how

[2] => this works

)






-- 
Edit this bug report at http://bugs.php.net/bug.php?id=54617&edit=1


[PHP-BUG] Bug #54964 [NEW]: PDO does not use defined class, but instead returns anonymous class

2011-05-31 Thread daveb at bulmore dot net
From: 
Operating system: 
PHP version:  5.3.6
Package:  PDO related
Bug Type: Bug
Bug description:PDO does not use defined class, but instead returns anonymous 
class

Description:

PDO fetch object methods do not use the class defined:



  // not used, but should be

  class User {

public $username;

public $first_name;

public $last_name;

public $created;

  }



  $stmt->setFetchMode(PDO::FETCH_CLASS, 'User');



  $obj = $stmt->fetch(); //returns anonymous class



but instead use a generated anonymous class based on the select statement.

Test script:
---


query('select * from users');



  $stmt->setFetchMode(PDO::FETCH_CLASS, 'User');

  

  foreach ($stmt as $obj)   //or while ($obj = $stmt->fetch())

{

  echo $obj->username, " ",

   $obj->first_name, " ",

   $obj->last_name, " ",

   $obj->role, " ",

   $obj->verified, " ",

   $obj->trusted, " ",

   $obj->created, "\n";

}



  $dbh = null;

?>











Expected result:

Should get an instance of:



  class User {

public $username;

public $first_name;

public $last_name;

public $created;

  }



and an error when trying to access the properties:



   $obj->role

   $obj->verified

   $obj->trusted



Actual result:
--
Returns an anonymous class with anything that's defined in the select
statement.

-- 
Edit bug report at http://bugs.php.net/bug.php?id=54964&edit=1
-- 
Try a snapshot (PHP 5.2):
http://bugs.php.net/fix.php?id=54964&r=trysnapshot52
Try a snapshot (PHP 5.3):
http://bugs.php.net/fix.php?id=54964&r=trysnapshot53
Try a snapshot (trunk):  
http://bugs.php.net/fix.php?id=54964&r=trysnapshottrunk
Fixed in SVN:
http://bugs.php.net/fix.php?id=54964&r=fixed
Fixed in SVN and need be documented: 
http://bugs.php.net/fix.php?id=54964&r=needdocs
Fixed in release:
http://bugs.php.net/fix.php?id=54964&r=alreadyfixed
Need backtrace:  
http://bugs.php.net/fix.php?id=54964&r=needtrace
Need Reproduce Script:   
http://bugs.php.net/fix.php?id=54964&r=needscript
Try newer version:   
http://bugs.php.net/fix.php?id=54964&r=oldversion
Not developer issue: 
http://bugs.php.net/fix.php?id=54964&r=support
Expected behavior:   
http://bugs.php.net/fix.php?id=54964&r=notwrong
Not enough info: 
http://bugs.php.net/fix.php?id=54964&r=notenoughinfo
Submitted twice: 
http://bugs.php.net/fix.php?id=54964&r=submittedtwice
register_globals:
http://bugs.php.net/fix.php?id=54964&r=globals
PHP 4 support discontinued:  http://bugs.php.net/fix.php?id=54964&r=php4
Daylight Savings:http://bugs.php.net/fix.php?id=54964&r=dst
IIS Stability:   
http://bugs.php.net/fix.php?id=54964&r=isapi
Install GNU Sed: 
http://bugs.php.net/fix.php?id=54964&r=gnused
Floating point limitations:  
http://bugs.php.net/fix.php?id=54964&r=float
No Zend Extensions:  
http://bugs.php.net/fix.php?id=54964&r=nozend
MySQL Configuration Error:   
http://bugs.php.net/fix.php?id=54964&r=mysqlcfg



[PHP-BUG] Req #54965 [NEW]: SVN export Should take a URL as from

2011-05-31 Thread cleung at draper dot com
From: 
Operating system: CentOS 5
PHP version:  5.3SVN-2011-05-31 (snap)
Package:  *General Issues
Bug Type: Feature/Change Request
Bug description:SVN export Should take a URL as from

Description:

>From command line, I can perform the following 

"svn export http://url/abc.doc -r5" and it will export abc.doc revision 5
to the 

current directory. So when I attempt to do something like this in php: 

"svn_export('http://url/abc.doc', '/local/tmp/abc.doc', 5)". I get an error


message: Warning: svn_export() [function.svn-export]: svn error(s) occured


155007 (Path is not a working copy directory) 'http://url' is not a working
copy 

2 (No such file or directory) 'http://url' does not exist in 

/home/apache/htdocs/export.php on line xx



Just wondering can the fromString be also a fromURL and check out a 

file/directory from the svn without having the project checked out before
hand. 

The command line for SVN already have this functionality.



---

>From manual page: http://www.php.net/function.svn-export#Description

---




-- 
Edit bug report at http://bugs.php.net/bug.php?id=54965&edit=1
-- 
Try a snapshot (PHP 5.2):
http://bugs.php.net/fix.php?id=54965&r=trysnapshot52
Try a snapshot (PHP 5.3):
http://bugs.php.net/fix.php?id=54965&r=trysnapshot53
Try a snapshot (trunk):  
http://bugs.php.net/fix.php?id=54965&r=trysnapshottrunk
Fixed in SVN:
http://bugs.php.net/fix.php?id=54965&r=fixed
Fixed in SVN and need be documented: 
http://bugs.php.net/fix.php?id=54965&r=needdocs
Fixed in release:
http://bugs.php.net/fix.php?id=54965&r=alreadyfixed
Need backtrace:  
http://bugs.php.net/fix.php?id=54965&r=needtrace
Need Reproduce Script:   
http://bugs.php.net/fix.php?id=54965&r=needscript
Try newer version:   
http://bugs.php.net/fix.php?id=54965&r=oldversion
Not developer issue: 
http://bugs.php.net/fix.php?id=54965&r=support
Expected behavior:   
http://bugs.php.net/fix.php?id=54965&r=notwrong
Not enough info: 
http://bugs.php.net/fix.php?id=54965&r=notenoughinfo
Submitted twice: 
http://bugs.php.net/fix.php?id=54965&r=submittedtwice
register_globals:
http://bugs.php.net/fix.php?id=54965&r=globals
PHP 4 support discontinued:  http://bugs.php.net/fix.php?id=54965&r=php4
Daylight Savings:http://bugs.php.net/fix.php?id=54965&r=dst
IIS Stability:   
http://bugs.php.net/fix.php?id=54965&r=isapi
Install GNU Sed: 
http://bugs.php.net/fix.php?id=54965&r=gnused
Floating point limitations:  
http://bugs.php.net/fix.php?id=54965&r=float
No Zend Extensions:  
http://bugs.php.net/fix.php?id=54965&r=nozend
MySQL Configuration Error:   
http://bugs.php.net/fix.php?id=54965&r=mysqlcfg



Req #54965 [Opn->Bgs]: SVN export Should take a URL as from

2011-05-31 Thread pajoye
Edit report at http://bugs.php.net/bug.php?id=54965&edit=1

 ID: 54965
 Updated by: paj...@php.net
 Reported by:cleung at draper dot com
 Summary:SVN export Should take a URL as from
-Status: Open
+Status: Bogus
 Type:   Feature/Change Request
 Package:*General Issues
 Operating System:   CentOS 5
 PHP Version:5.3SVN-2011-05-31 (snap)
 Block user comment: N
 Private report: N

 New Comment:

Please report pecl's svn bug at http://pecl.php.net/svn


Previous Comments:

[2011-05-31 17:29:03] cleung at draper dot com

Description:

>From command line, I can perform the following 

"svn export http://url/abc.doc -r5" and it will export abc.doc revision
5 to the 

current directory. So when I attempt to do something like this in php: 

"svn_export('http://url/abc.doc', '/local/tmp/abc.doc', 5)". I get an
error 

message: Warning: svn_export() [function.svn-export]: svn error(s)
occured 

155007 (Path is not a working copy directory) 'http://url' is not a
working copy 

2 (No such file or directory) 'http://url' does not exist in 

/home/apache/htdocs/export.php on line xx



Just wondering can the fromString be also a fromURL and check out a 

file/directory from the svn without having the project checked out
before hand. 

The command line for SVN already have this functionality.



---

>From manual page: http://www.php.net/function.svn-export#Description

---









-- 
Edit this bug report at http://bugs.php.net/bug.php?id=54965&edit=1


[PHP-BUG] Bug #54967 [NEW]: missing error constants in DOMException

2011-05-31 Thread giorgio dot liscio at email dot it
From: 
Operating system: Irrelevant
PHP version:  5.3.6
Package:  DOM XML related
Bug Type: Bug
Bug description:missing error constants in DOMException

Description:

hi, 

the exception constants are not defined in DOMException class



here are the dom2 constants:

const unsigned short  INDEX_SIZE_ERR = 1;

const unsigned short  DOMSTRING_SIZE_ERR = 2;

const unsigned short  HIERARCHY_REQUEST_ERR  = 3;

const unsigned short  WRONG_DOCUMENT_ERR = 4;

const unsigned short  INVALID_CHARACTER_ERR  = 5;

const unsigned short  NO_DATA_ALLOWED_ERR= 6;

const unsigned short  NO_MODIFICATION_ALLOWED_ERR= 7;

const unsigned short  NOT_FOUND_ERR  = 8;

const unsigned short  NOT_SUPPORTED_ERR  = 9;

const unsigned short  INUSE_ATTRIBUTE_ERR= 10;

const unsigned short  INVALID_STATE_ERR  = 11;

const unsigned short  SYNTAX_ERR = 12;

const unsigned short  INVALID_MODIFICATION_ERR   = 13;

const unsigned short  NAMESPACE_ERR  = 14;

const unsigned short  INVALID_ACCESS_ERR = 15;






-- 
Edit bug report at http://bugs.php.net/bug.php?id=54967&edit=1
-- 
Try a snapshot (PHP 5.2):
http://bugs.php.net/fix.php?id=54967&r=trysnapshot52
Try a snapshot (PHP 5.3):
http://bugs.php.net/fix.php?id=54967&r=trysnapshot53
Try a snapshot (trunk):  
http://bugs.php.net/fix.php?id=54967&r=trysnapshottrunk
Fixed in SVN:
http://bugs.php.net/fix.php?id=54967&r=fixed
Fixed in SVN and need be documented: 
http://bugs.php.net/fix.php?id=54967&r=needdocs
Fixed in release:
http://bugs.php.net/fix.php?id=54967&r=alreadyfixed
Need backtrace:  
http://bugs.php.net/fix.php?id=54967&r=needtrace
Need Reproduce Script:   
http://bugs.php.net/fix.php?id=54967&r=needscript
Try newer version:   
http://bugs.php.net/fix.php?id=54967&r=oldversion
Not developer issue: 
http://bugs.php.net/fix.php?id=54967&r=support
Expected behavior:   
http://bugs.php.net/fix.php?id=54967&r=notwrong
Not enough info: 
http://bugs.php.net/fix.php?id=54967&r=notenoughinfo
Submitted twice: 
http://bugs.php.net/fix.php?id=54967&r=submittedtwice
register_globals:
http://bugs.php.net/fix.php?id=54967&r=globals
PHP 4 support discontinued:  http://bugs.php.net/fix.php?id=54967&r=php4
Daylight Savings:http://bugs.php.net/fix.php?id=54967&r=dst
IIS Stability:   
http://bugs.php.net/fix.php?id=54967&r=isapi
Install GNU Sed: 
http://bugs.php.net/fix.php?id=54967&r=gnused
Floating point limitations:  
http://bugs.php.net/fix.php?id=54967&r=float
No Zend Extensions:  
http://bugs.php.net/fix.php?id=54967&r=nozend
MySQL Configuration Error:   
http://bugs.php.net/fix.php?id=54967&r=mysqlcfg



Bug #54967 [Opn]: missing error constants in DOMException

2011-05-31 Thread dtajchreber
Edit report at http://bugs.php.net/bug.php?id=54967&edit=1

 ID: 54967
 Updated by: dtajchre...@php.net
 Reported by:giorgio dot liscio at email dot it
 Summary:missing error constants in DOMException
 Status: Open
 Type:   Bug
 Package:DOM XML related
 Operating System:   Irrelevant
 PHP Version:5.3.6
 Block user comment: N
 Private report: N

 New Comment:

Not sure what you're saying is wrong... but they're defined as global
constants:



http://lxr.php.net/opengrok/xref/PHP_5_4/ext/dom/dom_fe.h#56

http://lxr.php.net/opengrok/xref/PHP_5_4/ext/dom/php_dom.c#859



[david@oslo:~]$ php -v

PHP 5.3.7-dev (cli) (built: May 15 2011 18:57:11) (DEBUG)

Copyright (c) 1997-2011 The PHP Group

Zend Engine v2.3.0, Copyright (c) 1998-2011 Zend Technologies

[david@oslo:~]$ php -r 'print_r(get_defined_constants());' | grep -i
'.*\[dom'

[DOM_PHP_ERR] => 0

[DOM_INDEX_SIZE_ERR] => 1

[DOMSTRING_SIZE_ERR] => 2

[DOM_HIERARCHY_REQUEST_ERR] => 3

[DOM_WRONG_DOCUMENT_ERR] => 4

[DOM_INVALID_CHARACTER_ERR] => 5

[DOM_NO_DATA_ALLOWED_ERR] => 6

[DOM_NO_MODIFICATION_ALLOWED_ERR] => 7

[DOM_NOT_FOUND_ERR] => 8

[DOM_NOT_SUPPORTED_ERR] => 9

[DOM_INUSE_ATTRIBUTE_ERR] => 10

[DOM_INVALID_STATE_ERR] => 11

[DOM_SYNTAX_ERR] => 12

[DOM_INVALID_MODIFICATION_ERR] => 13

[DOM_NAMESPACE_ERR] => 14

[DOM_INVALID_ACCESS_ERR] => 15

[DOM_VALIDATION_ERR] => 16

[david@oslo:~]$


Previous Comments:

[2011-05-31 23:21:58] giorgio dot liscio at email dot it

Description:

hi, 

the exception constants are not defined in DOMException class



here are the dom2 constants:

const unsigned short  INDEX_SIZE_ERR = 1;

const unsigned short  DOMSTRING_SIZE_ERR = 2;

const unsigned short  HIERARCHY_REQUEST_ERR  = 3;

const unsigned short  WRONG_DOCUMENT_ERR = 4;

const unsigned short  INVALID_CHARACTER_ERR  = 5;

const unsigned short  NO_DATA_ALLOWED_ERR= 6;

const unsigned short  NO_MODIFICATION_ALLOWED_ERR= 7;

const unsigned short  NOT_FOUND_ERR  = 8;

const unsigned short  NOT_SUPPORTED_ERR  = 9;

const unsigned short  INUSE_ATTRIBUTE_ERR= 10;

const unsigned short  INVALID_STATE_ERR  = 11;

const unsigned short  SYNTAX_ERR = 12;

const unsigned short  INVALID_MODIFICATION_ERR   = 13;

const unsigned short  NAMESPACE_ERR  = 14;

const unsigned short  INVALID_ACCESS_ERR = 15;











-- 
Edit this bug report at http://bugs.php.net/bug.php?id=54967&edit=1