fix: fix deserialization issues in multi-threading environments

[wochinge]

Related Issues

• fixes #issue-number

Proposed Changes:

• importing Python modules at the same time from different threads can lead to issues. We just spend multiple days debugging this. Change is adding a lock to avoid that multiple threads enter this at the same time. There is no impact for single-threaded applications

How did you test it?

• covered by existing tests

Notes for the reviewer

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I added unit tests and updated the docstrings
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test: and added ! in case the PR includes breaking changes.
• I documented my code
• I ran pre-commit hooks and fixed any issue

[coveralls]

Pull Request Test Coverage Report for Build 12373296669

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 39 unchanged lines in 2 files lost coverage.
• Overall coverage increased (+0.005%) to 90.485%

---

Files with Coverage Reduction	New Missed Lines	%
utils/type_serialization.py	7	89.04%
core/pipeline/base.py	32	88.64%

Totals
Change from base Build 12353137414:	0.005%
Covered Lines:	8112
Relevant Lines:	8965

---

💛 - Coveralls

[julian-risch]

LGTM!
Lock is immediately released if a ModuleNotFoundError is raised, so no additional error handling is needed.