2015-11-04 20:19:00 +00:00
|
|
|
{- git-annex output messages, including concurrent output to display regions
|
2015-04-03 20:48:30 +00:00
|
|
|
-
|
2020-12-03 17:01:28 +00:00
|
|
|
- Copyright 2010-2020 Joey Hess <id@joeyh.name>
|
2015-04-03 20:48:30 +00:00
|
|
|
-
|
2019-03-13 19:48:14 +00:00
|
|
|
- Licensed under the GNU AGPL version 3 or higher.
|
2015-04-03 20:48:30 +00:00
|
|
|
-}
|
|
|
|
|
|
|
|
module Messages.Internal where
|
|
|
|
|
|
|
|
import Common
|
2015-11-04 18:52:07 +00:00
|
|
|
import Annex
|
2015-04-03 20:48:30 +00:00
|
|
|
import Types.Messages
|
2015-11-05 21:22:45 +00:00
|
|
|
import Messages.Concurrent
|
2018-02-19 18:59:30 +00:00
|
|
|
import qualified Messages.JSON as JSON
|
|
|
|
import Messages.JSON (JSONBuilder)
|
2016-09-09 19:49:44 +00:00
|
|
|
|
2019-11-26 19:27:22 +00:00
|
|
|
import qualified Data.ByteString as S
|
|
|
|
|
2016-09-09 16:57:42 +00:00
|
|
|
withMessageState :: (MessageState -> Annex a) -> Annex a
|
|
|
|
withMessageState a = Annex.getState Annex.output >>= a
|
2015-11-04 18:52:07 +00:00
|
|
|
|
2019-11-26 19:27:22 +00:00
|
|
|
outputMessage :: JSONBuilder -> S.ByteString -> Annex ()
|
2018-02-06 17:03:55 +00:00
|
|
|
outputMessage = outputMessage' bufferJSON
|
|
|
|
|
2019-11-26 19:27:22 +00:00
|
|
|
outputMessage' :: (JSONBuilder -> MessageState -> Annex Bool) -> JSONBuilder -> S.ByteString -> Annex ()
|
2018-02-06 17:03:55 +00:00
|
|
|
outputMessage' jsonoutputter jsonbuilder msg = withMessageState $ \s -> case outputType s of
|
2016-09-09 16:57:42 +00:00
|
|
|
NormalOutput
|
2019-11-26 19:27:22 +00:00
|
|
|
| concurrentOutputEnabled s -> concurrentMessage s False (decodeBS msg) q
|
|
|
|
| otherwise -> liftIO $ flushed $ S.putStr msg
|
2018-02-06 17:03:55 +00:00
|
|
|
JSONOutput _ -> void $ jsonoutputter jsonbuilder s
|
2016-09-09 18:21:06 +00:00
|
|
|
QuietOutput -> q
|
new protocol for transferkeys, with message serialization
Necessarily threw out the old protocol, so if an old git-annex assistant
is running, and starts a transferkeys from the new git-annex, it would
fail. But, that seems unlikely; the assistant starts up transferkeys
processes and then keeps them running. Still, may need to test that
scenario.
The new protocol is simple read/show and looks like this:
TransferRequest Download (Right "origin") (Key {keyName = "f8f8766a836fb6120abf4d5328ce8761404e437529e997aaa0363bdd4fecd7bb", keyVariety = SHA2Key (HashSize 256) (HasExt True), keySize = Just 30, keyMtime = Nothing, keyChunkSize = Nothing, keyChunkNum = Nothing}) (AssociatedFile (Just "foo"))
TransferOutput (ProgressMeter (Just 30) (MeterState {meterBytesProcessed = BytesProcessed 0, meterTimeStamp = 1.6070268727892535e9}) (MeterState {meterBytesProcessed = BytesProcessed 30, meterTimeStamp = 1.6070268728043e9}))
TransferOutput (OutputMessage "(checksum...) ")
TransferResult True
Granted, this is not optimally fast, but it seems good enough, and is
probably nearly as fast as the old protocol anyhow.
emitSerializedOutput for ProgressMeter is not yet implemented. It needs
to somehow start or update a progress meter. There may need to be a new
message that allocates a progress meter, and then have ProgressMeter
update it.
This commit was sponsored by Ethan Aubin
2020-12-03 20:21:20 +00:00
|
|
|
SerializedOutput h -> do
|
|
|
|
liftIO $ outputSerialized h $ OutputMessage msg
|
2020-12-03 18:47:04 +00:00
|
|
|
void $ jsonoutputter jsonbuilder s
|
2016-09-09 18:21:06 +00:00
|
|
|
|
2016-09-09 22:13:55 +00:00
|
|
|
-- Buffer changes to JSON until end is reached and then emit it.
|
2018-02-06 17:03:55 +00:00
|
|
|
bufferJSON :: JSONBuilder -> MessageState -> Annex Bool
|
|
|
|
bufferJSON jsonbuilder s = case outputType s of
|
2020-12-03 18:47:04 +00:00
|
|
|
JSONOutput _ -> go (flushed . JSON.emit)
|
new protocol for transferkeys, with message serialization
Necessarily threw out the old protocol, so if an old git-annex assistant
is running, and starts a transferkeys from the new git-annex, it would
fail. But, that seems unlikely; the assistant starts up transferkeys
processes and then keeps them running. Still, may need to test that
scenario.
The new protocol is simple read/show and looks like this:
TransferRequest Download (Right "origin") (Key {keyName = "f8f8766a836fb6120abf4d5328ce8761404e437529e997aaa0363bdd4fecd7bb", keyVariety = SHA2Key (HashSize 256) (HasExt True), keySize = Just 30, keyMtime = Nothing, keyChunkSize = Nothing, keyChunkNum = Nothing}) (AssociatedFile (Just "foo"))
TransferOutput (ProgressMeter (Just 30) (MeterState {meterBytesProcessed = BytesProcessed 0, meterTimeStamp = 1.6070268727892535e9}) (MeterState {meterBytesProcessed = BytesProcessed 30, meterTimeStamp = 1.6070268728043e9}))
TransferOutput (OutputMessage "(checksum...) ")
TransferResult True
Granted, this is not optimally fast, but it seems good enough, and is
probably nearly as fast as the old protocol anyhow.
emitSerializedOutput for ProgressMeter is not yet implemented. It needs
to somehow start or update a progress meter. There may need to be a new
message that allocates a progress meter, and then have ProgressMeter
update it.
This commit was sponsored by Ethan Aubin
2020-12-03 20:21:20 +00:00
|
|
|
SerializedOutput h -> go (outputSerialized h . JSONObject . JSON.encode)
|
2020-12-03 18:47:04 +00:00
|
|
|
_ -> return False
|
|
|
|
where
|
|
|
|
go emitter
|
|
|
|
| endjson = do
|
2016-09-09 22:13:55 +00:00
|
|
|
Annex.changeState $ \st ->
|
|
|
|
st { Annex.output = s { jsonBuffer = Nothing } }
|
2020-12-03 18:47:04 +00:00
|
|
|
maybe noop (liftIO . emitter . JSON.finalize) json
|
2016-09-09 18:21:06 +00:00
|
|
|
return True
|
2020-12-03 18:47:04 +00:00
|
|
|
| otherwise = do
|
2016-09-09 22:13:55 +00:00
|
|
|
Annex.changeState $ \st ->
|
|
|
|
st { Annex.output = s { jsonBuffer = json } }
|
2016-09-09 18:21:06 +00:00
|
|
|
return True
|
2020-12-03 18:47:04 +00:00
|
|
|
|
2016-09-09 22:13:55 +00:00
|
|
|
(json, endjson) = case jsonbuilder i of
|
|
|
|
Nothing -> (jsonBuffer s, False)
|
|
|
|
(Just (j, e)) -> (Just j, e)
|
2020-12-03 18:47:04 +00:00
|
|
|
|
2016-09-09 22:13:55 +00:00
|
|
|
i = case jsonBuffer s of
|
|
|
|
Nothing -> Nothing
|
|
|
|
Just b -> Just (b, False)
|
2016-09-09 19:06:54 +00:00
|
|
|
|
2018-02-06 17:03:55 +00:00
|
|
|
-- Immediately output JSON.
|
|
|
|
outputJSON :: JSONBuilder -> MessageState -> Annex Bool
|
|
|
|
outputJSON jsonbuilder s = case outputType s of
|
2020-12-03 18:47:04 +00:00
|
|
|
JSONOutput _ -> go (flushed . JSON.emit)
|
new protocol for transferkeys, with message serialization
Necessarily threw out the old protocol, so if an old git-annex assistant
is running, and starts a transferkeys from the new git-annex, it would
fail. But, that seems unlikely; the assistant starts up transferkeys
processes and then keeps them running. Still, may need to test that
scenario.
The new protocol is simple read/show and looks like this:
TransferRequest Download (Right "origin") (Key {keyName = "f8f8766a836fb6120abf4d5328ce8761404e437529e997aaa0363bdd4fecd7bb", keyVariety = SHA2Key (HashSize 256) (HasExt True), keySize = Just 30, keyMtime = Nothing, keyChunkSize = Nothing, keyChunkNum = Nothing}) (AssociatedFile (Just "foo"))
TransferOutput (ProgressMeter (Just 30) (MeterState {meterBytesProcessed = BytesProcessed 0, meterTimeStamp = 1.6070268727892535e9}) (MeterState {meterBytesProcessed = BytesProcessed 30, meterTimeStamp = 1.6070268728043e9}))
TransferOutput (OutputMessage "(checksum...) ")
TransferResult True
Granted, this is not optimally fast, but it seems good enough, and is
probably nearly as fast as the old protocol anyhow.
emitSerializedOutput for ProgressMeter is not yet implemented. It needs
to somehow start or update a progress meter. There may need to be a new
message that allocates a progress meter, and then have ProgressMeter
update it.
This commit was sponsored by Ethan Aubin
2020-12-03 20:21:20 +00:00
|
|
|
SerializedOutput h -> go (outputSerialized h . JSONObject . JSON.encode)
|
2020-12-03 18:47:04 +00:00
|
|
|
_ -> return False
|
|
|
|
where
|
|
|
|
go emitter = do
|
|
|
|
maybe noop (liftIO . emitter)
|
2018-02-06 17:03:55 +00:00
|
|
|
(fst <$> jsonbuilder Nothing)
|
|
|
|
return True
|
|
|
|
|
2015-11-04 17:45:34 +00:00
|
|
|
outputError :: String -> Annex ()
|
2018-02-19 19:28:38 +00:00
|
|
|
outputError msg = withMessageState $ \s -> case (outputType s, jsonBuffer s) of
|
|
|
|
(JSONOutput jsonoptions, Just jb) | jsonErrorMessages jsonoptions ->
|
2018-02-19 19:55:00 +00:00
|
|
|
let jb' = Just (JSON.addErrorMessage (lines msg) jb)
|
2018-02-19 19:28:38 +00:00
|
|
|
in Annex.changeState $ \st ->
|
2018-02-19 19:39:52 +00:00
|
|
|
st { Annex.output = s { jsonBuffer = jb' } }
|
new protocol for transferkeys, with message serialization
Necessarily threw out the old protocol, so if an old git-annex assistant
is running, and starts a transferkeys from the new git-annex, it would
fail. But, that seems unlikely; the assistant starts up transferkeys
processes and then keeps them running. Still, may need to test that
scenario.
The new protocol is simple read/show and looks like this:
TransferRequest Download (Right "origin") (Key {keyName = "f8f8766a836fb6120abf4d5328ce8761404e437529e997aaa0363bdd4fecd7bb", keyVariety = SHA2Key (HashSize 256) (HasExt True), keySize = Just 30, keyMtime = Nothing, keyChunkSize = Nothing, keyChunkNum = Nothing}) (AssociatedFile (Just "foo"))
TransferOutput (ProgressMeter (Just 30) (MeterState {meterBytesProcessed = BytesProcessed 0, meterTimeStamp = 1.6070268727892535e9}) (MeterState {meterBytesProcessed = BytesProcessed 30, meterTimeStamp = 1.6070268728043e9}))
TransferOutput (OutputMessage "(checksum...) ")
TransferResult True
Granted, this is not optimally fast, but it seems good enough, and is
probably nearly as fast as the old protocol anyhow.
emitSerializedOutput for ProgressMeter is not yet implemented. It needs
to somehow start or update a progress meter. There may need to be a new
message that allocates a progress meter, and then have ProgressMeter
update it.
This commit was sponsored by Ethan Aubin
2020-12-03 20:21:20 +00:00
|
|
|
(SerializedOutput h, _) ->
|
|
|
|
liftIO $ outputSerialized h $ OutputError msg
|
2018-02-19 19:28:38 +00:00
|
|
|
_
|
|
|
|
| concurrentOutputEnabled s -> concurrentMessage s True msg go
|
|
|
|
| otherwise -> go
|
2015-11-04 17:45:34 +00:00
|
|
|
where
|
2016-09-09 16:57:42 +00:00
|
|
|
go = liftIO $ do
|
2015-11-04 17:45:34 +00:00
|
|
|
hFlush stdout
|
2016-09-09 16:57:42 +00:00
|
|
|
hPutStr stderr msg
|
2015-11-04 17:45:34 +00:00
|
|
|
hFlush stderr
|
|
|
|
|
2015-04-03 20:48:30 +00:00
|
|
|
q :: Monad m => m ()
|
|
|
|
q = noop
|
|
|
|
|
|
|
|
flushed :: IO () -> IO ()
|
|
|
|
flushed a = a >> hFlush stdout
|
2020-12-03 17:01:28 +00:00
|
|
|
|
new protocol for transferkeys, with message serialization
Necessarily threw out the old protocol, so if an old git-annex assistant
is running, and starts a transferkeys from the new git-annex, it would
fail. But, that seems unlikely; the assistant starts up transferkeys
processes and then keeps them running. Still, may need to test that
scenario.
The new protocol is simple read/show and looks like this:
TransferRequest Download (Right "origin") (Key {keyName = "f8f8766a836fb6120abf4d5328ce8761404e437529e997aaa0363bdd4fecd7bb", keyVariety = SHA2Key (HashSize 256) (HasExt True), keySize = Just 30, keyMtime = Nothing, keyChunkSize = Nothing, keyChunkNum = Nothing}) (AssociatedFile (Just "foo"))
TransferOutput (ProgressMeter (Just 30) (MeterState {meterBytesProcessed = BytesProcessed 0, meterTimeStamp = 1.6070268727892535e9}) (MeterState {meterBytesProcessed = BytesProcessed 30, meterTimeStamp = 1.6070268728043e9}))
TransferOutput (OutputMessage "(checksum...) ")
TransferResult True
Granted, this is not optimally fast, but it seems good enough, and is
probably nearly as fast as the old protocol anyhow.
emitSerializedOutput for ProgressMeter is not yet implemented. It needs
to somehow start or update a progress meter. There may need to be a new
message that allocates a progress meter, and then have ProgressMeter
update it.
This commit was sponsored by Ethan Aubin
2020-12-03 20:21:20 +00:00
|
|
|
outputSerialized :: (SerializedOutput -> IO ()) -> SerializedOutput -> IO ()
|
|
|
|
outputSerialized = id
|
|
|
|
|
|
|
|
emitSerializedOutput :: SerializedOutput -> Annex ()
|
|
|
|
emitSerializedOutput (OutputMessage msg) =
|
|
|
|
outputMessage' nojsonoutputter nojsonbuilder msg
|
|
|
|
where
|
|
|
|
nojsonoutputter _ _ = return False
|
|
|
|
nojsonbuilder = id
|
|
|
|
emitSerializedOutput (OutputError msg) = outputError msg
|
|
|
|
emitSerializedOutput (ProgressMeter sz old new) = undefined -- TODO
|
|
|
|
emitSerializedOutput (JSONObject b) =
|
|
|
|
withMessageState $ \s -> case outputType s of
|
|
|
|
JSONOutput _ -> liftIO $ flushed $ JSON.emit' b
|
|
|
|
SerializedOutput h -> liftIO $
|
|
|
|
outputSerialized h $ JSONObject b
|
|
|
|
_ -> q
|