replica object does not contain size

[kript]

python-irodsclient/irods/data_object.py

Line 59 in 1cc23fc

self.replicas = [iRODSReplica(

One can get every other replica information you can retrieve with ils apart from that (unless I've missed something);

import os
from irods.session import iRODSSession
try:
    env_file = os.environ['IRODS_ENVIRONMENT_FILE']
except KeyError:
    env_file = os.path.expanduser('~/.irods/irods_environment.json')

session = iRODSSession(irods_env_file=env_file)

obj = session.data_objects.get("/seq/home/jc18#Sanger1/irods-resource-4.0.0-64bit.deb")

for replica in obj.replicas:
    print(replica.resource_name)
    print(replica.number)
    print(replica.path)
    print(replica.status)
    print(replica.checksum)

./test_python.py 
root
0
/irods-seq-i23-de/home/jc18#Sanger1/irods-resource-4.0.0-64bit.deb
1
02b7dd912af6e615f4680594fe3e2dc8
Traceback (most recent call last):
  File "./test_python.py", line 19, in <module>
    print(replica.size)
AttributeError: 'iRODSReplica' object has no attribute 'size'

This would help with Issue 3930

[d-w-moore]

Unsatisfactory for general purposes maybe - and only a valid approach if the bad replicas were accessible via OS calls from the local filesystem - but if the goal is to cull the undesired replicas mentioned in 3090 one possibility would be to stat the physical paths of all replicas "labeled as good" ( that is, repl.status == '1') of all DataObjects on the affected resource(s). For those returning zero size( ie., os.stat(repl.path).st_size==0) , you could make a PRC call to remove them. It would require running as the service account user, however, as only that user would has general access to all the local physical paths. I could put together some demo code if you deem this to be at all practical.

[d-w-moore]

Extra note to the above : I'm fairly new in python iRODS client programming myself, but it happens that I've done the above mentioned replica deletion elsewhere with e.g. : "dataObj.unlink(replNum=N)"

[kript]

Thanks @d-w-moore ! We have over 20 iRES in that Zone alone, so its not practical for us to call out an stat call (say over ssh) to remote servers at the moment, partly because not all the IES and iRES servers use the same service account, but worth keeping in the 'back pocket' in case we can't get this sorted in time.