Daniel Moore

@dworkin - Also, just to be clear, since this issue is in irods/irods instead of http://github.com/irods/irods_capability_indexing, what is the "desired side effect"? a) the creation of an AVU on the...

@dworkin . This rule seems to work and I believe the delay block recognizes the INST_NAME tag. Moreover, at least for me, the command `irule set_avu_f null null `did not...

@dworkin Interesting. What version is your iRODS server?

The problem doesn't appear in the history of 4-2-stable or any of its releases, at least up to the present-day tip of that branch e99cf5579134ee776f6291509b7b03b0b771b5ef

This may be, at its heart, the same issue as what py_remote encounters in this [comment](https://github.com/irods/irods/issues/6461#issuecomment-1176241434) attached to question/issue #6461. It's plausible because both of these are essentially pass-throughs for...

Confirmed as early as iRODS v4.2.8 that this is still an issue. Is my thinking wrong on this, @trel @alanking @korydraughn ? A remote( ) hint would have to have...

@korydraughn - I had noticed that in `rsExecMyRule,` when requested to run the delay part of the rule, the inst_name string is zero length. Ok, I'll see if adding it...

@ll4strw - Try something like the rule below. (I tested as irods with "iput -f VERSION.json".) You are correct - the data object I/O microservices will work regardless of whether...

@ll4strw Your best bet is probably to loop over the desired offsets in the file and to read smaller buffers at at time -- using, for example: ``` offset =...

@ll4strw I'd possibly recommend using `py_remote` (the Python RE Plugin's equivalent to remote(...){...} in the iRODS rule language) to remote-execute a rule directly on the resource server where that physical...