Get status of bulk request#129
Conversation
|
Nice! Seems to work well. One remark: when literally copying and pasting the suggested When I fix that, the next hurdle is that the authentication doesn't match: For me no problem because I know what to do. But I expect there will be some users who may struggle with this. Could we make the printed command resemble the used command a bit more, for the executable ( |
|
I notice that the status information returned by dCache does not show everything. In this example it doesn't show that the command has been a "--stage" or pin. If we think users need that, I could submit a request to the dCache developers for that. |
Done, can you please check if you agree with the implementation? The output given can now be directly copied and executed. |
It may be handy, but not essential as we also store this information in the requests.log |
|
Doesn't seem to work with Shouldn't we look closer to the original command line arguments? If the |
|
Would it be an idea to make the timestamps human readable? A |
|
Oops, in the last commit I wrote "stderr instead of stdin" but of course I meant "stderr instead of stdout". 😅 |
I was thinking in this direction first, but that means we have to go through all the arguments and pick out the ones we need. It sounds simple, but since the way arguments can be passed is very flexible (with or without optional arguments), I didn't see an elegant way to do this (without adding some lines code). I'll have another look. |
I don't know, I think it's more elegant to return directly what dCache API returns. Perhaps this json output changes in the furutre, or users want to do something with it. |
|
Looks good! Let's merge! |
See #86
The command to follow status request is:
Also, changed output of (un)stage request, to help user understand what to do with request URL and ID