Page Menu
Home
c4science
Search
Configure Global Search
Log In
Files
F91457702
DiffusionSSHMercurialServeWorkflow.php
No One
Temporary
Actions
Download File
Edit File
Delete File
View Transforms
Subscribe
Mute Notifications
Award Token
Subscribers
None
File Metadata
Details
File Info
Storage
Attached
Created
Mon, Nov 11, 07:45
Size
3 KB
Mime Type
text/x-php
Expires
Wed, Nov 13, 07:45 (2 d)
Engine
blob
Format
Raw Data
Handle
22265922
Attached To
rPH Phabricator
DiffusionSSHMercurialServeWorkflow.php
View Options
<?php
final
class
DiffusionSSHMercurialServeWorkflow
extends
DiffusionSSHMercurialWorkflow
{
protected
$didSeeWrite
;
public
function
didConstruct
()
{
$this
->
setName
(
'hg'
);
$this
->
setArguments
(
array
(
array
(
'name'
=>
'repository'
,
'short'
=>
'R'
,
'param'
=>
'repo'
,
),
array
(
'name'
=>
'stdio'
,
),
array
(
'name'
=>
'command'
,
'wildcard'
=>
true
,
),
));
}
protected
function
executeRepositoryOperations
()
{
$args
=
$this
->
getArgs
();
$path
=
$args
->
getArg
(
'repository'
);
$repository
=
$this
->
loadRepository
(
$path
);
$args
=
$this
->
getArgs
();
if
(!
$args
->
getArg
(
'stdio'
))
{
throw
new
Exception
(
"Expected `hg ... --stdio`!"
);
}
if
(
$args
->
getArg
(
'command'
)
!==
array
(
'serve'
))
{
throw
new
Exception
(
"Expected `hg ... serve`!"
);
}
$future
=
new
ExecFuture
(
'hg -R %s serve --stdio'
,
$repository
->
getLocalPath
());
$io_channel
=
$this
->
getIOChannel
();
$protocol_channel
=
new
DiffusionSSHMercurialWireClientProtocolChannel
(
$io_channel
);
$err
=
id
(
$this
->
newPassthruCommand
())
->
setIOChannel
(
$protocol_channel
)
->
setCommandChannelFromExecFuture
(
$future
)
->
setWillWriteCallback
(
array
(
$this
,
'willWriteMessageCallback'
))
->
execute
();
// TODO: It's apparently technically possible to communicate errors to
// Mercurial over SSH by writing a special "\n<error>\n-\n" string. However,
// my attempt to implement that resulted in Mercurial closing the socket and
// then hanging, without showing the error. This might be an issue on our
// side (we need to close our half of the socket?), or maybe the code
// for this in Mercurial doesn't actually work, or maybe something else
// is afoot. At some point, we should look into doing this more cleanly.
// For now, when we, e.g., reject writes for policy reasons, the user will
// see "abort: unexpected response: empty string" after the diagnostically
// useful, e.g., "remote: This repository is read-only over SSH." message.
if
(!
$err
&&
$this
->
didSeeWrite
)
{
$repository
->
writeStatusMessage
(
PhabricatorRepositoryStatusMessage
::
TYPE_NEEDS_UPDATE
,
PhabricatorRepositoryStatusMessage
::
CODE_OKAY
);
}
return
$err
;
}
public
function
willWriteMessageCallback
(
PhabricatorSSHPassthruCommand
$command
,
$message
)
{
$command
=
$message
[
'command'
];
// Check if this is a readonly command.
$is_readonly
=
false
;
if
(
$command
==
'batch'
)
{
$cmds
=
idx
(
$message
[
'arguments'
],
'cmds'
);
if
(
DiffusionMercurialWireProtocol
::
isReadOnlyBatchCommand
(
$cmds
))
{
$is_readonly
=
true
;
}
}
else
if
(
DiffusionMercurialWireProtocol
::
isReadOnlyCommand
(
$command
))
{
$is_readonly
=
true
;
}
if
(!
$is_readonly
)
{
$this
->
requireWriteAccess
();
$this
->
didSeeWrite
=
true
;
}
// If we're good, return the raw message data.
return
$message
[
'raw'
];
}
}
Event Timeline
Log In to Comment