Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>SVN command line errors go to stderr, not stdout, which is why you aren't able to see them. What you want to do is redirect stderr to stdout and then <code>print_r($output)</code> to determine the cause of the error. </p> <pre><code>exec('svn commit &lt;stuff&gt; 2&gt;&amp;1', $output, $returnStatus); if ( $returnStatus ) { print_r($output); } </code></pre> <p>Sample output:</p> <pre><code>Array ( [0] =&gt; svn: Commit failed (details follow): [1] =&gt; svn: '/path/to/&lt;stuff&gt;' is not under version control ) </code></pre> <p>This is not ideal because it mixes stderr with stdout when it would otherwise be unnecessary, but I don't know of another way to get the desired output in this case. If someone else does, please comment.</p> <p><strong>Note:</strong> The third parameter to <a href="http://us3.php.net/manual/en/function.exec.php" rel="nofollow noreferrer">exec(...)</a> is the return <strong>status</strong>, not the error message, so you need to tweak your code accordingly for that as well.</p> <p>If the error output after making the <code>2&gt;&amp;1</code> modification doesn't help solve the root cause of your problem, please post the new output here.</p> <p><strong>Edit after new information:</strong></p> <p>Did you upload this SVN working copy to your server from somewhere else? That would explain this error.</p> <p>If I check out a working copy from my local repository, upload it to my remote server, and then try to commit, I get the same error.</p> <p>If that's the case, you need to execute the "svn checkout" of the working copy <strong>on the server running the PHP script</strong> in order to be able to commit to it. If that server can't communicate with the repository's server, then that's a whole other problem.</p>
    singulars
    1. This table or related slice is empty.
    1. POPHP: exec(svn commit) is not returning any errors nor working
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMichael Moussa
    1. USMichael Moussa
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPHP: exec(svn commit) is not returning any errors nor working
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO@Mike - Thanks for pointing out. you are right,per the manual, the 3rd parameter means "If the return_var argument is present along with the output argument, then the return status of the executed command will be written to this variable."
      singulars
      1. PO
      1. USJay Zeng
    2. COThanks Mike, I was able to toss out a few more fun errors.. Added above.
      singulars
      1. PO
      1. USPetrogad
    3. COIt's strange as the working copy has been checked out already, and I have my gui - Versions - up looking at the file (shows modified). So I'm not sure why it thinks that the hostname can't be found.. I'm uploading a test case to try on a working copy directly on the server as well. Thanks
      singulars
      1. PO
      1. USPetrogad
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload