fix: write summary file before trying to cache it #1205
Merged
Conversation
This file contains 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
- Also give a .md file extension for prettier rendering in Discord
|
code looks good will test later |
odilitime
approved these changes
Dec 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Relates to:
When I used my agent to CHAT_WITH_ATTACHMENTS it always failed to stat the summary file because it had not been created.
Risks
Low. Writes summaries to disk, could become a lot of data if agent writes a lot of summaries.
Background
What does this PR do?
Write summary file before trying to cache it
What kind of change is this?
Bug fix (non-breaking change which fixes an issue)
Why are we doing this? Any context or related work?
Yeah, I'm building a technical support that needs to receive and analyze config files.
Discord username
tobben_dev