This is because an error during a run "pollutes" the database because the embeddings don't get saved.
This also means file names won't be associated, which is also a problem.
I guess I need to make an option for whether to allow these source-less items to be kept. (Also, as it is checking files, if it can find a broken association, IT SHOULD ADD IT BACK.)
This is because an error during a run "pollutes" the database because the embeddings don't get saved.
This also means file names won't be associated, which is also a problem.
I guess I need to make an option for whether to allow these source-less items to be kept. (Also, as it is checking files, if it can find a broken association, IT SHOULD ADD IT BACK.)
The difficulty is when a file needs to be chunked, this will try to process the whole file and chunks in a non deterministic manner, causing duplication of work.
The result will be shockingly similar to the refresh_sources function itself.
The difficulty is when a file needs to be chunked, this will try to process the whole file and chunks in a non deterministic manner, causing duplication of work.
The result will be shockingly similar to the refresh_sources function itself.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This is because an error during a run "pollutes" the database because the embeddings don't get saved.
This also means file names won't be associated, which is also a problem.
I guess I need to make an option for whether to allow these source-less items to be kept. (Also, as it is checking files, if it can find a broken association, IT SHOULD ADD IT BACK.)
The difficulty is when a file needs to be chunked, this will try to process the whole file and chunks in a non deterministic manner, causing duplication of work.
The result will be shockingly similar to the refresh_sources function itself.
This is done in
470901d9b9.