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

Notifications api #847

Merged
merged 18 commits into from
Mar 20, 2023
Merged

Notifications api #847

merged 18 commits into from
Mar 20, 2023

Conversation

robsdedude
Copy link
Member

@robsdedude robsdedude commented Oct 28, 2022

CHANGELOG.md Outdated Show resolved Hide resolved
docs/source/api.rst Outdated Show resolved Hide resolved
docs/source/api.rst Outdated Show resolved Hide resolved
neo4j/_api.py Outdated Show resolved Hide resolved
neo4j/_api.py Outdated Show resolved Hide resolved
neo4j/_api.py Outdated Show resolved Hide resolved
robsdedude and others added 15 commits October 28, 2022 14:45
 * ADR update neo-technology/drivers-adr#56
   * Split filtering into two config options
   * Simplified driver by removing requirement for protocol optimizations
   * Slightly adjusted protocol specs
 * Finalized documentation
Methods forwarded to the wrapped socket need to live on the wrapper object, not
the class.
Methods forwarded to the wrapped socket need to altered on the wrapper object,
not the class.
 * Remove leftover debug code and comments
 * Refine docs
Copy link
Contributor

@bigmontz bigmontz left a comment

Choose a reason for hiding this comment

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

The behaviour of the property category of the ResultSummary is wrong, it should be UNKNOWN when the category is not present in the metadata.

@@ -223,6 +223,7 @@ def apply_unasync(files):
"assert_awaited_once": "assert_called_once",
"assert_awaited_once_with": "assert_called_once_with",
"await_count": "call_count",
"AsyncMock": "MagicMock",
Copy link
Contributor

Choose a reason for hiding this comment

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

Where did MagicMock come from?

Copy link
Member Author

Choose a reason for hiding this comment

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

the mocking library has Mock and MagicMock which behave the same except that the latter also mock magic methods (__xyz__ shaped methods). AsyncMock does always mock magic methods as well (I suppose it has to, to be able to intercept calls to __await__, but that is speculation). Either way, by default the unasync script would turn AsyncMock into Mock which brakes tests that rely on magic methods being mocked.

src/neo4j/_work/summary.py Show resolved Hide resolved
Copy link
Contributor

@bigmontz bigmontz left a comment

Choose a reason for hiding this comment

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

🔢

@robsdedude robsdedude merged commit 721a0f2 into neo4j:5.0 Mar 20, 2023
@robsdedude robsdedude deleted the notifications-api branch March 20, 2023 17:15
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