The community member is experiencing a "module not found" error after rebooting Visual Studio Code (VSC). Other community members suggest that the issue may be related to the environment not being activated when running the script. They recommend keeping the environment active while installing and running the script. One community member also had a separate question about the metadata in the indexer, where the "embedding" value is null, and was informed that the embeddings may not be shown in the example due to their large size, but they are still present in the data.
that's interesting, when i ran the file in cmd while env is activated i assume it's a success since it's able to reach print("done"), previously this has not happened to me on VSC so i was pretty baffled.
Every pypi package installed in a env needs the env to be activated when you are running the command. else it will raise import error just like your case