It seems that urfave/cli acts differently handling Description and Usage
depending on whether it is dealing with a command or a subcommand.
This fixes most of these issues, as well as the commands output which was
printing some blank lines.
License: MIT
Signed-off-by: Hector Sanjuan <hector@protocol.ai>
* First draft of test dockerfile build
* Test dockerfile, build works, container runs and cluster tests go through
* Removed fifo for output
* renaming dockerfile
* Adding functionality for test 12
Added scripts and entrypoint mods to the testing docker image to allow for random shut down and startup
(both SIGSTOP and SIGINT) of the ipfs-cluster-service.
* test docker image ready for tests 12 and 13
* Added cluster daemon respawn
to docker image
We were setting a nil Cid on the PinInfo object for errors.
Cleaned up the logic a bit, and added comments
License: MIT
Signed-off-by: Hector Sanjuan <hector@protocol.ai>
* First draft of test dockerfile build
* Test dockerfile, build works, container runs and cluster tests go through
* Removed fifo for output
* renaming dockerfile
* Adding functionality for test 12
Added scripts and entrypoint mods to the testing docker image to allow for random shut down and startup
(both SIGSTOP and SIGINT) of the ipfs-cluster-service.
* test docker image ready for tests 12 and 13
* First draft of test dockerfile build
* Test dockerfile, build works, container runs and cluster tests go through
* Removed fifo for output
* renaming dockerfile
The ReadTimeout for the API was the same as for RPC. So the error
did not have time to be correctly returned to the client.
License: MIT
Signed-off-by: Hector Sanjuan <hector@protocol.ai>
I have attempted to address all of the comments on the original PR.
The sharness tests now make use of prereqs, see test-lib for details
and helper functions.
I have attempted to address all of the comments on the original PR.
The sharness tests now make use of prereqs, see test-lib for details
and helper functions.
Updates dockerfile and entrypoint script to have the same behavior the ipfs-go docker build
moved to in 3477. This fixes a bug where the cluster entrypoint script does not have
sufficient permissions to access /data/ipfs. The entrypoint also now launches a process with
tini
I have updated API endpoints to be /allocations rather than /pinlinst
It's more self-explanatory.
License: MIT
Signed-off-by: Hector Sanjuan <hector@protocol.ai>