- 15 Nov, 2014 2 commits
-
-
Brian Tiger Chow authored
@jbenet @mappum Yeah, there's some duplicated work. But there's also a separation of concerns. In one case, we check to determine where the command should run. In the other case, we check to determine which hooks should run. Having these actions separated reduces complexity in a nice way. License: MIT Signed-off-by: Brian Tiger Chow <brian@perfmode.com>
-
Brian Tiger Chow authored
License: MIT Signed-off-by: Brian Tiger Chow <brian@perfmode.com> impl errorf License: MIT Signed-off-by: Brian Tiger Chow <brian@perfmode.com> return a debug error License: MIT Signed-off-by: Brian Tiger Chow <brian@perfmode.com>
-
- 14 Nov, 2014 38 commits
-
-
Juan Batiz-Benet authored
-
Matt Bell authored
-
Juan Batiz-Benet authored
-
Brian Tiger Chow authored
License: MIT Signed-off-by: Brian Tiger Chow <brian@perfmode.com>
-
Brian Tiger Chow authored
not immediately useful, but nice to have tagging you to make sure i didn't make a mistake here @jbenet License: MIT Signed-off-by: Brian Tiger Chow <brian@perfmode.com>
-
Juan Batiz-Benet authored
This commit adds the pretty-complicated decision function to check whether a command should run on the daemon. @maybebtc @mappum double check the logic?
-
Brian Tiger Chow authored
Discovered this quirk about interfaces. @whyrusleeping @mappum @jbenet License: MIT Signed-off-by: Brian Tiger Chow <brian@perfmode.com>
-
Matt Bell authored
-
Juan Batiz-Benet authored
Also: - map[cmds.EncodingType]cmds.Marshaller -> MarshalMap cc @mappum @maybebtc
-
Matt Bell authored
-
Matt Bell authored
-
Matt Bell authored
-
Matt Bell authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
Attention @maybebtc @mappum I cleaned up + simplified the main flow. Now, all printing is contained inside main itself! (:cheer:). I do this with the help of a cmdInvocation struct that has both a Parse and Run. The only major clunkiness left is that the "CallCommand" is still its own function. But *shrug*. Please test it works as we would expect. i changed much of the flow, so likely that i missed a complicated edge case. main roadmap: - parse the commandline to get a cmdInvocation - if user requests, help, print it and exit. - run the command invocation - output the response - if anything fails, print error, maybe with help
-
Matt Bell authored
-
Brian Tiger Chow authored
@mappum License: MIT Signed-off-by: Brian Tiger Chow <brian@perfmode.com>
-
Brian Tiger Chow authored
-
Juan Batiz-Benet authored
-
Matt Bell authored
-
Juan Batiz-Benet authored
-
Brian Tiger Chow authored
-
Matt Bell authored
-
Matt Bell authored
-
Matt Bell authored
-
Matt Bell authored
-
Matt Bell authored
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
* bring debug checking back to top level so we have more control over CPU profiling. * bring help text up to top level so we can exit from the program at the top level instead of within an arbitrary function
-
Brian Tiger Chow authored
-