Tony Edgin

For completion's sake, here is the rule logic for computing checksums using the API PEPs. The PEPs are in [chksum.re](https://github.com/irods/irods/files/9628492/chksum.re.txt), and [json.re](https://github.com/irods/irods/files/9628494/json.re.txt) provides supporting logic for parsing JSON.

Since this won't be an issue in 4.3, I'm happy if you want to close this feature request.

To be clear, I am not asking for `itouch -n` to be able to create replicas of existing data objects.

This issue is a little broader that I originally thought. If I try to use `itouch -n` to create a data object with a replica with a given number, it...

Here's a third case where this happens. When I attempt to use `itouch -R` to create a replica of an existing data object, the error code isn't being propagated back...

> 1. Were these REI files already on the disk (aka scheduled) from before the upgrade? Or are these being scheduled live and then crashing the irodsReServer when 'executed'? The...

I don't think so. It was reproducible with the irodsReServer's worker concurrency set to 1.

I haven't been able to reproduce this in our dev zone, but I did capture an REI file so I could compare it side by side to the one I...

It is very likely that the data object in prod-mapped.txt had multiple replicas. I can't be for certain, since the data object was deleted months ago, but nearly all of...

I triggered a `_bisque_scheduleRm` rule in the dev environment on a replicated data object. irodsReServer did not segfault, nor were any errors logged. The deferred rule execution appears to have...