Generated a migration for a comment in tenant_account model
Why
Unused assertion logic can take up wasteful LLM calls
Flask application logs were missing for prompt service
How
-
Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)
Ideally no, it has only removed an assertion related logic which is currently disabled from the UI and unused
Database Migrations
Missing migration for a comment related change in some previous PR
Env Config
LOG_LEVEL for prompt service - can be INFO or DEBUG. Defaults to INFO
Relevant Docs
-
Related Issues or PRs
-
Dependencies Versions
-
Notes on Testing
Tried running some prompts in a PS project
Screenshots
Checklist
I have read and understood the [Contribution Guidelines]().
What
Why
How
-
Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)
Database Migrations
Env Config
LOG_LEVEL
for prompt service - can beINFO
orDEBUG
. Defaults toINFO
Relevant Docs
-
Related Issues or PRs
-
Dependencies Versions
-
Notes on Testing
Screenshots
Checklist
I have read and understood the [Contribution Guidelines]().