got the report generation working after the coding logic was corrected#24
Merged
Conversation
insightbuilder
approved these changes
Apr 24, 2025
Owner
insightbuilder
left a comment
insightbuilder
left a comment
There was a problem hiding this comment.
The code is verified and its working
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📌 Description
There was no issue logged for this PR.
The write_report tool was not writing the file, even though the code was there. The challenge was the AI model was calling the tool, and then making up its own replies. When trying to debug, couldn't write a print statement as the servers don't print the data to CLI.
Then finally debugged it by placing return statements at different location inside the function called by the tool.