Currently, the work oracle (de facto the OpenCL provider) is created always, regardless of whether labels need to be generated. This is suboptimal and causes issues for users who moved their data to a setup w/o a GPU OpenCL provider (but forgot to remove provider-id configuration).
The proposed solution is to initialize the work oracle lazily, only when it is needed.
Currently, the work oracle (de facto the OpenCL provider) is created always, regardless of whether labels need to be generated. This is suboptimal and causes issues for users who moved their data to a setup w/o a GPU OpenCL provider (but forgot to remove provider-id configuration).
The proposed solution is to initialize the work oracle lazily, only when it is needed.