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.

Sign up for GitHub

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

Jump to bottom

Shared database: library modification warning without apparent modification #8586

Closed
2 tasks done
m-mauersberger opened this issue Mar 21, 2022 · 5 comments · Fixed by #9216
Closed
2 tasks done

Shared database: library modification warning without apparent modification #8586

m-mauersberger opened this issue Mar 21, 2022 · 5 comments · Fixed by #9216
Labels
component: shared-database status: waiting-for-feedback The submitter or other users need to provide more information about the issue

Comments

@m-mauersberger
Copy link
Contributor

JabRef version

5.5 (latest release)

Operating system

Windows

Details on version and operating system

10

Checked with the latest development build

  • I made a backup of my libraries before testing the latest development version.
  • I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

  1. Log in to shared database (PostgreSQL). Set tick at "automatically save library" and choose a Bibtex file.
  2. Add an entry somewhere or modify something.
  3. A warning appears instantly that modifications by another program has been detected but there was no other program.

JabRef_Issue_220321

This warning appears at every action you take. Dismissing changes have no lasting effect. Reviewing changes exhibits that a comma was removed somewhere, e.g. at the end of the keywords list.

JabRef_Issue_220321

Maybe it would be more convenient to make little changes silently. It is somehow confusing to read that another program was involved.

Thank you for your help!

Appendix

No response
@m-mauersberger m-mauersberger mentioned this issue Mar 21, 2022
Closed
2 tasks
@m-mauersberger
Copy link
Contributor Author

I checked this problem up again and can detail the behavior somewhat:
I changed every entry with trailing comma in the keywords list. As a consquence, these entries were not incoporated anymore in the changed warning.

However, this warning appears if you type in some content in an entry field (e.g. keywords) via keyboard. It seems like only the first character of the typing in is saved "On disk" (right column) while it is compared to the content in JabRef. Maybe it would help when comparison took place after some delay.
JabRef_Issue_220328

@Siedlerchr
Copy link
Member

Thanks for the investigation @koppor This might be hint towards our problem

@Siedlerchr
Copy link
Member

Siedlerchr commented Oct 10, 2022 •
edited
Loading

@m-mauersberger I think we finally found the root cause and fixed it. Can you please test the latest dev version (should be ready in like 30 min)
https://builds.jabref.org/main/

@koppor koppor added the status: waiting-for-feedback The submitter or other users need to provide more information about the issue label Oct 14, 2022
@koppor
Copy link
Member

koppor commented Oct 14, 2022

The fixing PR was #9216

@ThiloteE ThiloteE mentioned this issue Oct 14, 2022
Merged
6 tasks
@m-mauersberger
Copy link
Contributor Author

I can confirm that the problem has been solved. Thank you very much for your efforts!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component: shared-database status: waiting-for-feedback The submitter or other users need to provide more information about the issue
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Opening a file removes duplicate keywords and triggers lib changed JabRef/jabref
4 participants
@Siedlerchr @koppor @m-mauersberger @ThiloteE