-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Warning Message for Moving Attached Open Files #10121
Comments
Agreed |
Can i work on this? |
Sure, go ahead :-) |
|
Can I work on this issue? |
Welcome to the vibrant world of open-source development with JabRef! Newcomers, we're excited to have you on board. Start by exploring our Contributing guidelines, and don't forget to check out our workspace setup guidelines to get started smoothly. Having any questions or issues? Feel free to ask here on GitHub. Need help setting up your local workspace? Join the conversation on JabRef's Gitter chat. And don't hesitate to open a (draft) pull request early on to show the direction it is heading towards. This way, you will receive valuable feedback. Happy coding! 🚀 |
I want to grab this issue if it is still open and no one is working on it |
@Simran-Sunil I didn't see any activity for three weeks, thus, I assigned @HrithikPadavala . |
Hi @koppor , I have spotted the corresponding function and added log warning as you can see in the attached picture but unable to instantiate DialogServive/JabRefDialogService variable inside MoveFileCleanup.java to call notify method. Could you please tell me how can I create and call notify method |
Should I call notify from within CleanupAction.java only?? |
Please use the common logging practices: - LOGGER. warn (exception. toString());
+ LOGGER. warn ("Could not move file", exception); |
@HrithikPadavala Use |
Hi @koppor , solved the issue and opened a PR |
@HrithikPadavala The PR doesn't seem to link the this issue (as required in the PR description template). Otherwise, I would see a link to it here. I am on my mobile and cannot check the PR list.... |
Updated everything as required and committed too. Someone please check and confirm. Thanks. |
Please look at the pull request. The automatic checks show errors: See #11438. Scroll down. Click on "details" at each failing test. After you fixed them, we can have a detailed look. Otherwise our brains are too distracted by issues obvious to us. |
Opened another PR with branch other than main this time to resolve merge issues please review |
Please resolve the merge conflicts so that the CI can run. First, all checkstyle issues should be solved. This enables us to focus on the content. |
@koppor Resolved all issues but something related to changelog is not getting resolved. This is the only file need to be reviewed. So that this issue can be closed. |
Please try to keep context in comments. Comments on PR issues should go to PRs. I replied at #11484 (comment). |
Hi, can I work on this issue? Thanks! |
Sure, go ahead. |
Welcome to the vibrant world of open-source development with JabRef! Newcomers, we're excited to have you on board. Start by exploring our Contributing guidelines, and don't forget to check out our workspace setup guidelines to get started smoothly. In case you encounter failing tests during development, please check our developer FAQs! Having any questions or issues? Feel free to ask here on GitHub. Need help setting up your local workspace? Join the conversation on JabRef's Gitter chat. And don't hesitate to open a (draft) pull request early on to show the direction it is heading towards. This way, you will receive valuable feedback. Happy coding! 🚀 |
Hi - it seems like that I cannot recreate the issue in my environment. Is it something to do with how Mac filesystem works? When I tried to cleanup things - even though the file is open somewhere else (e.g. Microsoft Word), it won't throw any IOException, it just moves it effortlessly. Do you think I should try it with a Windows machine? Thanks |
Linux and Mac have different file systems and no atomic lock on the file and if I remember correctly it's Windows only. |
You can "quickly" fire up a Windows 10 VM using Vagrant as described at https://github.com/JabRef/jabref/tree/main/scripts/vms. https://github.com/JabRef/jabref/tree/main/scripts/vms/windows10 proived the |
Suppose that you attach a file to an entry. Then, using a cleanup you want to move that file to the General File Directory of the library. If the attached file is open, the file is not moved but no warning message is shown. It would be nice to have such a message to let the user know what just happened.
The text was updated successfully, but these errors were encountered: