From da9ca7475e1845c6df9fb5ed2ea223d5aee6fcd8 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 28 Jan 2025 11:57:03 -0400 Subject: [PATCH] comment --- ..._ddc985546fee804733c4ec485253e98f._comment | 29 +++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 doc/todo/compute_special_remote/comment_12_ddc985546fee804733c4ec485253e98f._comment diff --git a/doc/todo/compute_special_remote/comment_12_ddc985546fee804733c4ec485253e98f._comment b/doc/todo/compute_special_remote/comment_12_ddc985546fee804733c4ec485253e98f._comment new file mode 100644 index 0000000000..c05e779876 --- /dev/null +++ b/doc/todo/compute_special_remote/comment_12_ddc985546fee804733c4ec485253e98f._comment @@ -0,0 +1,29 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 12""" + date="2025-01-28T15:39:44Z" + content=""" +My design so far does not fully support +"Request one key, receive many". + +My `git-annex addcomputed` command doesn't handle the case where a +computation generates multiple output files. While the `git-annex-compute-` +command's interface could let it return several computed files, addcomputed +would only adds one file to the name that the user specifies. What is it +supposed to do if the computation generates more than one? Maybe it needs a +way to let a whole directory be populated with the files generated by a +computation. Or a way to specify multiple files to add. + +And here's another problem: +Suppose I have one very expensive computation that generates files foo +and bar. And a second, less expensive computation, that also generates foo +(same content) as well as generating baz. Both computations are run on the +same compute special remote. Now if the user runs `git-annex get foo`, +they will be unhappy if it chooses to run the expensive computation, +rather than the less expensive computation. + +Since the per-special remote state for a key is used as the computation +input, only one input can be saved for foo's key. So it wouldn't really be +picking between two alernatives, it would just use whatever the current +state for that key is. +"""]]