Skip to content

Unhandled excpetions within CASCache on grpc errors

Summary

There are situations where unhandled exceptions could occur from operations within cascache.py

Steps to reproduce

N/A

What is the current bug behavior?

There are a few cases within cascache.py where raise is called within except grpc.RpcError as e: meaning a grpc error could be raised and not handled elsewhere.

What is the expected correct behavior?

These errors should be raised as ArtifactError which are then caught and handled elsewhere within the system.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information