I ran the scheduler on my repo and verified that the file I'm editing is seen by Tabby. However, there is still no custom context in the prompts. I checked the events log at ~/.tabby/events and there is no context logged. How can I investigate this further?
Quentin Mre
Asked on Nov 14, 2023
To investigate the lack of context in Tabby prompts, you can follow these steps:
Check the events log: The events log at ~/.tabby/events logs the prompts being fed to the model. Make sure to verify if any context is being logged.
Verify the scheduler: Ensure that the scheduler is running properly and that the file you're editing is being seen by Tabby. You can use the /v1beta/search endpoint to check if the file is detected.
Set RUST_LOG to debug: Set the RUST_LOG environment variable to debug to enable debug logging. This can help you identify any potential issues or errors related to the context.
Review the proximity algorithm: If the file is being detected by Tabby but still no context is returned, review the proximity algorithm to ensure it is functioning correctly.
By following these steps, you should be able to investigate and identify the cause of the lack of context in Tabby prompts.
