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

[bug] Data node editor id mechanism solve #2065

Closed
wants to merge 1 commit into from

Conversation

AdibaNaushad
Copy link

this PR is under #2017

This project implements a locking mechanism for data nodes in a Taipy-based application. It ensures that data nodes cannot be written to or appended to if they are currently being edited by another process. The repository includes:

Enhanced DataNode and FileDataNode classes with lock checks for write(), append(), and _upload() methods. Custom exception handling via DataNodeIsBeingEdited. Unit tests to ensure full code coverage for the locking functionality.

Modified DataNode class: Added locking mechanism to write(), append(), and _upload() methods.

New FileDataNode class: Added lock check to _upload() method.

Test Cases:

test_write_locked_data_node(): Verifies the write() method respects the lock.
test_append_locked_data_node(): Verifies append() method respects the lock.
test_append_non_list_data(): Ensures append() only works on list data.
test_file_data_node_upload_locked(): Verifies _upload() respects the lock.

This project implements a locking mechanism for data nodes in a Taipy-based application. It ensures that data nodes cannot be written to or appended to if they are currently being edited by another process. The repository includes:

Enhanced DataNode and FileDataNode classes with lock checks for write(), append(), and _upload() methods.
Custom exception handling via DataNodeIsBeingEdited.
Unit tests to ensure full code coverage for the locking functionality.
@AdibaNaushad AdibaNaushad marked this pull request as draft October 15, 2024 15:19
@AdibaNaushad AdibaNaushad marked this pull request as ready for review October 15, 2024 15:20
Copy link
Author

@AdibaNaushad AdibaNaushad left a comment

Choose a reason for hiding this comment

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

@jrobinAV take a look on this

@joaoandre-avaiga
Copy link
Collaborator

Hi there!

Thank you so much for your contribution! I noticed that there seems to be a bit of confusion regarding issue #2017. It looks like you've submitted a new file with classes that already exist in Taipy, and the unit tests and feature code are mixed in the same file, which isn't the best practice. For these reasons, I'll be closing this PR.

Feel free to reach out if you'd like any clarification or if you have any questions. We'd love to see your future contributions!

Thanks again! 😊

@AdibaNaushad
Copy link
Author

@joaoandre-avaiga so i need to stop doing further on this project ? . thank you next time i will try best . i might be too inexperience for it , i feel the same

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