-
Notifications
You must be signed in to change notification settings - Fork 104
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
MCP: The notifications/initialized message is not sent #1186
Comments
@jmartisk do we now have what we need in LangChain4j for this? |
In LC4j, it is fixed. For Quarkus, I have it in my branch that buffers updates that should go in with the next lc4j upgrade |
🙏 |
@jmartisk @langchain4j any idea when LangChain4j will be released? Asking because we ran into this while preparing for a workshop and if possible, we would really like to have a fix some time this week. Thanks! |
+1 to releasing rather soon, I have a quarkus-langchain4j branch that contains updates that will be applied together with the upgrade, but it's getting messy and hard to handle. |
@langchain4j any idea when the next release will go out? Thanks |
I assume that with LangChain4j 1.0.0.Alpha2 we can now fix this, correct? |
It doesn't look it has been released yet |
I guess Twitter isn't accurate 😀 |
In the HTTP transport, which we reimplement on the Quarkus side, we need an equivalent change as in langchain4j/langchain4j#2360
The text was updated successfully, but these errors were encountered: