I did indeed advise Krzysztof Findeisen to defer fixing problems with BaseRecord.get/set until
DM-8716, but if that means we're not testing much of anything in pipe_base as a result, that implies we also won't really be able to run any full integration tests until DM-8716 is complete, and that might cause enough problems with the timeline that we would be better off finding a workaround. But I still don't want us to put much effort into cleaning up BaseRecord.get/set as they stand now, because they're going to be completely blown away in DM-8716.
Looking back at the original Slack conversation, it seems the main problem was BaseRecord.getL not being present - if that is the only kind of problem we're seeing here, the best workaround may be to replace getL with get (and likewise for other suffixes) in the Python code. The suffixed versions were a workaround for bad performance in BaseRecord.get that should go away in
DM-8716, and prior to that this change should let us run the code even if there's a temporary performance regression. As with the workarounds for DM-9112, though, it'd be good to put those changes on a separate commit so we can revert them easily later if we have to. Will that work?