fix: Update device deserialization for components that use local models

[sjrl]

Related Issues

• fixes #issue-number

Proposed Changes:

I would like to be able to specify None or null when deserializin a pipeline that uses:

• SentenceTransfomersTextEmbedder
• SentenceTransfomersDocumentEmbedder
• NamedEntityExtractor
• SentenceTransformersDiversityRanker

Currently I get an error if I try and I'm required to provide a specific device following the ComponentDevice.to_dict() format.

Following implementation that is used for ExtractiveReader to overcome the same problem.

How did you test it?

• added two unit 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:.
• I documented my code
• I ran pre-commit hooks and fixed any issue

[coveralls]

Pull Request Test Coverage Report for Build 9065132032

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 20 unchanged lines in 1 file lost coverage.
• Overall coverage increased (+0.007%) to 90.421%

---

Files with Coverage Reduction	New Missed Lines	%
components/extractors/named_entity_extractor.py	20	68.48%

Totals
Change from base Build 9030307905:	0.007%
Covered Lines:	6532
Relevant Lines:	7224

---

💛 - Coveralls

[anakin87]

Hey, @sjrl!

Can you explain when this is necessary?
Typically, when serializing a Pipeline containing a SentenceTransformersTextEmbedder, the used device is serialized and I don't expect it to be null, but maybe I am overlooking something...

(If needed, please also update the LocalWhisperTranscriber)

[sjrl]

Hey @anakin87! And of course.

This is more to do with deserializing from a YAML file where the pipeline was only generated as a YAML file (no serialization in this case). It's often the case that in dC we will create a pipeline from a YAML file in an editor that does not have access to the hardware we will run it on. Also it's possible as the editor of the pipeline I don't know what hardware this pipeline will run on (e.g. cpu vs gpu) so it's helpful to be able to specify device: null in the yaml file which will let init methods of these components auto detect which hardware to use.

[anakin87]

Thanks for the explanation!

This PR looks good.

• Please add a similar mechanism to LocalWhisperTranscriber.
• Update the release notes.

[anakin87]

👍