Skip to content
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

Error: java.io.IOException - Expected a SETTINGS frame but was WINDOW_UPDATE during commit message generation #226

Open
Trileon12 opened this issue Aug 21, 2024 · 11 comments
Assignees
Labels
bug Something isn't working on_hold Issues that are currently on hold.

Comments

@Trileon12
Copy link

First of all, thank you for developing the AICommit plugin! It's been a really helpful tool, but I’ve recently encountered an issue.

When I try to generate a commit message, I get the following error:

java.lang.RuntimeException: java.io.IOException: Expected a SETTINGS frame but was WINDOW_UPDATE

I'm using GoLand 2024.2 on Ubuntu 22.04.
Interestingly, it works fine on Windows 10, but not on Ubuntu.

@Blarc
Copy link
Owner

Blarc commented Aug 21, 2024

Hey @Trileon12, I'm glad you find it useful 😃 . Could you please add the whole stack trace? Thanks 🙏 .

@Trileon12
Copy link
Author

Hey @Blarc
Thanks for the quick reply! I'm not entirely sure what you mean by "stack trace" . I'm not seeing any events in the Tail log when the error happens.

I’ve found a few more details while testing it out:

  • Right after I reload the IDE, the first commit message usually generates without any issues.
  • After that, the error starts popping up more consistently, but oddly enough, sometimes it works again even without a full IDE restart—though that’s less common.

@Blarc
Copy link
Owner

Blarc commented Aug 21, 2024

Where do you see the error that you posted? Edit: Can you post a screenshot as well?

@Trileon12
Copy link
Author

image

I see it in commit message window

@Blarc
Copy link
Owner

Blarc commented Aug 21, 2024

Huh, it seems this error has something to do with http2. A quick google suggests that the problem might be in the size of the data sent. Could you maybe test if this error only appears if the diff is really big?

Furthermore, can you please tell me which LLM client are you using? This might be a bug in langchain4j.

@Blarc Blarc added the bug Something isn't working label Aug 21, 2024
@Blarc Blarc self-assigned this Aug 21, 2024
@Trileon12
Copy link
Author

I think this error definitely doesn't depend on the diff size. I tried using it with a small diff (just one line) and got the same error.
I use the gpt-4o model.

@Blarc
Copy link
Owner

Blarc commented Aug 21, 2024

Could you maybe try with the development version of the plugin from GitHub actions: link.

The plugin should now re-throw the exception and the whole stack trace will be logged by the IDE. This way I'll have more information and be able to open an issue in langchain4j.

You can follow these instructions to install the plugin from zip.

@Trileon12
Copy link
Author

tail_log.txt

I've attached a file with the log for one request.

@Blarc
Copy link
Owner

Blarc commented Sep 4, 2024

I've posted a question about how to force http/1.1 on langchain4j and will try to add this option if possible.

Please update, if anything changes in the meantime @Trileon12.

Thank you 🙏 .

@Blarc
Copy link
Owner

Blarc commented Sep 5, 2024

According to this reply from langchain4j, it is currently not possible to force http/1.1.

@Trileon12
Copy link
Author

Hey Blarc, thanks for keeping me updated! As I understand it, there's currently no way to force HTTP/1.1, but I'll be happy to test it when this feature becomes available. If anything changes on my side, I'll let you know.
Thanks a lot for your work and support!

@Blarc Blarc added the on_hold Issues that are currently on hold. label Sep 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working on_hold Issues that are currently on hold.
Projects
None yet
Development

No branches or pull requests

2 participants