Devlog#28 - Greetings Everyone !
TL;DR -
Added proper ollama checking and validation plus a runtime cli. Generation now safely uses fresh persisted repo intelligence instead of re-analyzing the project everytime
Long -
Problems :
so when doing today’s work the problems that i wanted to fix was that the generation workflow was still too dependent on live repo analysis instead of using the persisted intelligence. 2nd there was no way to verify ollama itself is available or not. like ollama runtime and is a model available or not. runtime failures needed to stop generation cleanly and not throw a bunch of error a user neds to debug. we needed to preserve provider behaviour and avoid breaking the previous architecture i built the generation one. also the generation path needed clear boundaries between runtime validation, provider execution and final output and etc etc. It sound much but the implementation was simple as ig for me.
things done today to solve the problems -
-
added ollama runtime inspection to check local runtime and requested model are available
-
added dedicated runtime cli commd for checking the state of the runtime and model independently
-
changed the generation to load persistd repo intellegence insteasd of it everytime doing a fresh analysis as it would be bad for it to make new things for everytime a cli is ran
-
added cache freshness validation so generation refues stale repo intellegence
-
added regression covergae proving that a generation uses the persistent project and doesnt starts the analyzer again
-
made a foundation kinda thing for a clean generationresponse to cli output boundary with remainng output workflow continuing afterwards
-
added test for the features added
Also some of the current changes may not be sen on the github repo bcz i havent comitted some changes as they are a part of a feature and i commit like a feature and the tests related to it for better commits ig .
Now what we did to solve the problems and how i felt when solving them -
. the generation pipeline is now ready to build the dev facing output worflow or like a user workflow on top of these things the previous architecture i made. i found addng the flags to main.py file easy but then adding the cache checking and the regression covergae and the generationresponse to cli output boundary a bit challenging .
So today only this much. Hope u like my project and plz comment for feedback.
also a mention to @CT5 on slack for telling me to added problem and solution section in my devlog for better project experii\ence.
Comments 1
!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Sign in to join the conversation.