You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you call lookup for projects, they come back with a PROJECT_EXPIRED key, and not an EXPIRED key. However, the results from lookup_for_member on projects return an EXPIRED key, and no PROJECT_EXPIRED key. This makes it hard to be agnostic about what calls project data comes from.
After reading the code, the same appears to be true for slices. lookup would use SLICE_EXPIRED (from SA_constants.py) and lookup_for_member would use EXPIRED (hardcoded in SAv1PersistentImplementation.py).
I've added SLICE_EXPIRED or PROJECT_EXPIRED to the offending functions.
I left EXPIRED in as well for backward compatibility with a comment explaining that it is there for backward compatibility because of omni. I hope someday the backward compatibility can be removed.
If you call
lookup
for projects, they come back with aPROJECT_EXPIRED
key, and not anEXPIRED
key. However, the results fromlookup_for_member
on projects return anEXPIRED
key, and noPROJECT_EXPIRED
key. This makes it hard to be agnostic about what calls project data comes from.Sample entry from
lookup_for_member
:Sample entry from
lookup
:The text was updated successfully, but these errors were encountered: