David Anthoff
David Anthoff
We save this information _by package_ in our cache. I think that is why each method is stored in the module where it is defined. If the user now uses...
> > If the user now uses a new environment where only package A is part of the env, we wouldn't want to load the method that was defined in...
> presumably you have different caches for different versions of a package? Yes, we have one cache file per version per package. And the goal in the future is to...
I've for now classified this as a bug, because it seems there is still something we need to fix? But I read this issue quickly, just trying to organize our...
Copying some text from a PR here: For the CI runs it is a bit annoying because it is a lot of output that has no information (I only pasted...
One simple way to start would be that we use https://azure.microsoft.com/en-us/services/app-service/static/ for hosting, and I could manually run the initial indexing on my machine, which is pretty beefy. I think...
Ok, that was easy :) The content of https://github.com/julia-vscode/symbolcache is now just available at https://symbolcache.julia-vscode.org/, supposedly completely geo-replicated etc.
For a more automatic thing I thought we could somehow integrate with the bots that already run on the registry. For example, the bot on the registry that is currently...
So we're going to tackle this kind of problem after we release v0.13 of the VS Code extension.
Yeah, we might need a much more fine grained story there... Maybe also differentiate based on what Julia version was used.