mage Update e2e tests for GQLAlchemy 1.8.0

Removed workaround in E2E tests for dropping indices using older versions of gqlalchemy.

Summary by CodeRabbit

Chores
- Updated the gqlalchemy package to version 1.8.0 in test requirements.
- Cleaned up test code by removing obsolete commented-out logic related to index management.

Jun 12 '25 15:06 mattkjames7

Walkthrough

The changes remove obsolete manual index-dropping code from an end-to-end test module, relying instead on updated database cleanup methods. Additionally, the gqlalchemy package version is updated from 1.6.0 to 1.8.0 in the test requirements, reflecting compatibility with newer features or fixes.

Changes

File(s)	Change Summary
e2e/test_module.py	Removed a commented-out loop for manual index removal; now relies solely on `db.drop_indexes()` and `db.ensure_constraints([])`.
python/tests/requirements.txt	Updated `gqlalchemy` version from 1.6.0 to 1.8.0.

Poem

In the garden of tests, old loops are now gone,
With new gqlalchemy, our cleanup moves on.
No more index by index, just a single call—
The database sparkles, constraints stand tall.
🐇✨
Hopping ahead, as the versions grow strong,
Our code stays tidy, where bugs don't belong!

📜 Recent review details

Configuration used: CodeRabbit UI Review profile: CHILL Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 91a2e419c2f2e082450702d1f2cc95671534e1b7 and 67c7c0a93816dd8480b56a3d4df5e40a84c4c561.

📒 Files selected for processing (2)

e2e/test_module.py (0 hunks)
python/tests/requirements.txt (1 hunks)

💤 Files with no reviewable changes (1)

e2e/test_module.py

🔇 Additional comments (1)

python/tests/requirements.txt (1)

12-12: Dependency bump: update gqlalchemy to 1.8.0
This aligns with the removal of the manual index-dropping workaround in your E2E tests, leveraging the improved drop_indexes() behavior in GQLAlchemy 1.8.0. Ensure that version 1.8.0 is available on PyPI and that there are no unexpected breaking changes impacting other tests.

✨ Finishing Touches

[ ] 📝 Generate Docstrings

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Explain this complex logic.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai explain this code block.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and explain its main purpose.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR.
@coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

Jun 12 '25 15:06 coderabbitai[bot]

Description

Removed workaround in E2E tests for dropping indices using older versions of gqlalchemy.

Pull request type

[ ] Bugfix
[ ] Algorithm/Module
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Related issues

Delete if this PR doesn't resolve any issues. Link the issue if it does.

######################################

Reviewer checklist (the reviewer checks this part)

Module/Algorithm

[ ] Core algorithm/module implementation
[ ] Query module implementation
[ ] Tests provided (unit / e2e)
[ ] Code documentation
[ ] README short description

Documentation checklist

[x] Add the documentation label tag
[ ] Add the bug / feature label tag
[x] Add the milestone for which this feature is intended
- If not known, set for a later milestone
[x] Write a release note, including added/changed clauses
- N/A
[ ] Link the documentation PR here
- [Documentation PR link]
[ ] Tag someone from docs team in the comments