-
Notifications
You must be signed in to change notification settings - Fork 49
✨ Incident Infrastructure Improvements #232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
0294088
to
77d724e
Compare
76d8d62
to
a65cc0c
Compare
Signed-off-by: Jonah Sussman <[email protected]> Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
…ebugging and tweaking prompts (konveyor#219) * Update targets to match kantra v0.4.0+ * Add ability to trace LLM related data Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
…ariables Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
737f1e9
to
9bfb7be
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
few questions, looks pretty good though and I like all the added tests. A lot of stuff was added to requirements.txt, just want to double check they are all required.
incident to fix: "{{ incident.message }}" | ||
Line number: {{ incident.line_number }} | ||
{% if incident.solution_str is defined %} | ||
{{ incident.solution_str }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there still a way for users to override the templates for the solutions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The get_prompt
still retrieves its prompt from the model provider, with a default of main.jinja
, so that functionality is still there. Right now, there's no way to override the solution_handling
templates though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we want to just pass variables in from the solution handler to the normal template. Could we declare what variables are declared by a handler and what variables are required for a template so that we can fail on start with an invalid config?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think I understand.
get_incident_solution_for_file
will pass the same variables to the user-specified prompt regardless. One of those variables, incident.solution_str
, is generated by solution_consumer
. Each solution consumer expects a Solution
, which is indeed type-checked and uses prompts in the solution_handling
directory. Right now, templates there can't be configured, but the main prompt can.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to look over the rebase with:
- Tracing
- Logging to file
When I attempted to run I hit an exception with Tracing from a recent commit to let tracing follow the configured 'log' directory, looks like in the rebase we changed it up a little to not pass in the config object, but the code is still looking for the config object.
I think there is likely a piece missing for configuring the logging to file as well, when I ran I didn't see the 'logs' directory get created.
Signed-off-by: JonahSussman <[email protected]>
Signed-off-by: JonahSussman <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I run 'run_demo.py' I see:
INFO - 2024-07-24 08:07:12,405 - __main__ - [ run_demo.py:101 - write_to_disk()] - Writing updated source code to ./coolstore/src/main/java/com/redhat/coolstore/rest/RestApplication.java
ERROR - 2024-07-24 08:07:12,405 - __main__ - [ run_demo.py:106 - write_to_disk()] - Failed to write updated_file @ ./coolstore/src/main/java/com/redhat/coolstore/rest/RestApplication.java with error: string indices must be integers, not 'str'
Signed-off-by: JonahSussman <[email protected]>
run_demo.py is now working with @JonahSussman latest fix.
|
Signed-off-by: JonahSussman <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified success running with run_demo.py.
There is a slight tweak with the Trace data that could be addressed in this or a follow up PR
Signed-off-by: JonahSussman <[email protected]>
No description provided.