-
Notifications
You must be signed in to change notification settings - Fork 672
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
feat: implement notifications handling for extension logs #1415
base: main
Are you sure you want to change the base?
Conversation
This is great - lots of people asking about this will help a lot. A couple thoughts:
|
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.
great direction!
|
||
// Set up logging in the default cache directory | ||
println!("Setting up logging for extension {}", config.name()); | ||
let log_path = format!("{}/.cache/goose/logs/{}.log", |
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.
nit: use the etcetera crate like in other logging
|
||
use super::LogMessage; | ||
|
||
pub struct FileLogger { |
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.
nit: i wonder if it would be more consistent/easier to forward to tracing
? please disregard if that adds a lot of complexity, but off the top of my head it might make it easier to control both file and stderr based logging etc
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.
nice! idk if it was just me, but i had a little bit of a hard time tracing. not sure if there's room to simplify?
This will allow developers to view logs from their extensions (servers). For the MCP protocol, logs are emitted as notification-type messages, so this PR expands how we handle server responses to include notifications.