Tony Edgin

`type` is another symbol that cannot be used as a key without quoting.

_I corrected the iRODS version. I was using 4.2.10 when I discovered this issue._ Yes. In the following example `ownerName` does not need to be quoted. ``` rule { *kvps.ownerName...

`size` and `type` are both builtin functions in the rule language. I'm guessing that's the issue.

I verified that this bug exists in 4.2.10 as well.

Which `pep_api_*` PEPs are triggered when a replica is created or updated? From what I can tell the following operations will likely create or update a replica. The ones preceded...

I figured out how to trigger the following "yes" PEPs. ``` data_obj_copy # icp replica_close # istream replica_open # istream data_obj_put # iput data_obj_rsync # irsync phy_path_reg # ireg touch...

So I need to use python-irodsclient or another client library to trigger the following. ``` pep_api_data_obj_open pep_api_data_obj_create pep_api_data_obj_create_and_stat pep_api_data_obj_close ``` If `iput -b` doesn't trigger `buik_data_obj_put`, how do I use...

I figured out how to trigger `bulk_data_obj_put`. `iput` needs to be called with both the `-b` and `-r` options. I'm guessing that bulk upload isn't used when `-b` is provided...

It looks like `bulk_data_obj_reg` can't be triggered by iCommands. From my understanding the code, This family of API PEPs are called by from the server endpoint `rsBulkDataObjReg`, which are only...

`data_obj_rsync` isn't needed for a checksum calculation rule. These PEPs are triggered by client calls to `rcDataObjRsync`. For syncing from client to server, this function always calls `rcDataObjPut`, which triggers...