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

Fix group chat history and group embeddings generation #11795

Merged
merged 3 commits into from
Sep 20, 2024

Conversation

InAnYan
Copy link
Collaborator

@InAnYan InAnYan commented Sep 19, 2024

Closes https://github.com/JabRef/jabref-issue-melting-pot/issues/544.

Group chat history wasn't saved. Fixed.

And there was also a problem with embeddings generation for group. One statement should be in JavaFX thread. Fixed.

Mandatory checks

- [ ] Change in CHANGELOG.md described in a way that is understandable for the average user (if applicable)
- [ ] Tests created for changes (if applicable)

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your code currently does not meet JabRef's code guidelines.
We use Checkstyle to identify issues.
The tool reviewdog already placed comments on GitHub to indicate the places. See the tab "Files" in you PR.
Please carefully follow the setup guide for the codestyle.
Afterwards, please run checkstyle locally and fix the issues.

You can check review dog's comments at the tab "Files changed" of your pull request.

@@ -79,7 +80,8 @@ public Void call() throws Exception {
linkedFiles
.stream()
.map(processingInfo -> {
processingInfo.setState(ProcessingState.PROCESSING);
UiTaskExecutor.runInJavaFXThread(() -> processingInfo.setState(ProcessingState.PROCESSING));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the wrong place, see my other PR

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmm, I see.

But I had an exception on this line. Maybe I'll investigate the bug further later. I'll just focus on group chat history in this PR

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The exception comes because we access the UI, but at this point we are in "logic" and we cannot use UI In logic, thus we need to go the point in the UI where the notification is triggered.

@InAnYan
Copy link
Collaborator Author

InAnYan commented Sep 20, 2024

Okay, now group chat history is stored

@InAnYan InAnYan requested a review from Siedlerchr September 20, 2024 05:08
Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your code currently does not meet JabRef's code guidelines.
We use Checkstyle to identify issues.
The tool reviewdog already placed comments on GitHub to indicate the places. See the tab "Files" in you PR.
Please carefully follow the setup guide for the codestyle.
Afterwards, please run checkstyle locally and fix the issues.

You can check review dog's comments at the tab "Files changed" of your pull request.

@Siedlerchr
Copy link
Member

can you address this one as well? https://github.com/JabRef/jabref-issue-melting-pot/issues/542

@Siedlerchr Siedlerchr added this pull request to the merge queue Sep 20, 2024
Merged via the queue into JabRef:main with commit 9eed666 Sep 20, 2024
23 checks passed
@Siedlerchr Siedlerchr deleted the fix-ai-bugs branch September 20, 2024 17:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants