Fix #634 fix canvas resize #626

Anchel123 · 2025-01-26T10:07:30Z

PR Type

Bug fix

Description

Fixed canvas resize handling using ResizeObserver.
Removed redundant useEffect for force graph configuration.
Improved cleanup logic for event listeners and observers.

Changes walkthrough 📝

Relevant files

Bug fix

ForceGraph.tsx `Refactored canvas resize handling and cleanup` app/components/ForceGraph.tsx Replaced `resizeObserver` with `ResizeObserver` instance. Added `ResizeObserver` to handle canvas resizing. Removed redundant `useEffect` for force graph configuration. Improved cleanup logic for event listeners and observers.	+7/-15

Need help?
Type /help how to ... in the comments thread for any questions about Qodo Merge usage.
Check out the documentation for more information.

vercel · 2025-01-26T10:07:36Z

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
falkordb-browser	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 29, 2025 10:19am

coderabbitai · 2025-01-26T10:07:38Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

🪧 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.
- Generate unit testing code for this file.
- 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 generate unit testing code for this file.
- @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 generate unit testing code.
- @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.

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. (Beta)
@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.

qodo-merge-pro · 2025-01-26T10:07:49Z

Qodo Merge was enabled for this repository. To continue using it, please link your Git account with your Qodo account here.

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Recommended focus areas for review Missing Initial Size The initial size of the canvas is not set since the handleResize() is not called immediately after component mount. This could cause rendering issues until the first resize event occurs. useEffect(() => { const handleResize = () => { if (!parentRef.current) return setParentWidth(parentRef.current.clientWidth) setParentHeight(parentRef.current.clientHeight) } window.addEventListener('resize', handleResize) const observer = new ResizeObserver(handleResize) if (parentRef.current) { observer.observe(parentRef.current) } return () => { window.removeEventListener('resize', handleResize) observer.disconnect() } }, [parentRef]) Force Configuration The force graph configuration (d3Force settings for link distance, charge strength, etc.) was removed. This could affect the graph layout and behavior if these configurations were necessary. useEffect(() => { const handleResize = () => { if (!parentRef.current) return setParentWidth(parentRef.current.clientWidth) setParentHeight(parentRef.current.clientHeight) } window.addEventListener('resize', handleResize) const observer = new ResizeObserver(handleResize) if (parentRef.current) { observer.observe(parentRef.current) } return () => { window.removeEventListener('resize', handleResize) observer.disconnect() } }, [parentRef])

qodo-merge-pro · 2025-01-26T10:08:03Z

Qodo Merge was enabled for this repository. To continue using it, please link your Git account with your Qodo account here.

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	Initialize canvas dimensions on mount Call `handleResize` immediately after setting up the observer to initialize the canvas dimensions, otherwise the canvas will start with 0x0 dimensions until the first resize event. app/components/ForceGraph.tsx [62-66] const observer = new ResizeObserver(handleResize) if (parentRef.current) { observer.observe(parentRef.current) + handleResize() // Initialize dimensions immediately } Apply this suggestion Suggestion importance[1-10]: 8 Why: The suggestion addresses a significant functional issue where the canvas would start with zero dimensions until a resize event occurs. Adding immediate initialization ensures proper initial rendering.	8
General	Improve cleanup order in useEffect Move the observer cleanup to execute before the event listener cleanup to ensure proper order of cleanup operations and prevent potential memory leaks. app/components/ForceGraph.tsx [68-71] return () => { + observer.disconnect() window.removeEventListener('resize', handleResize) - observer.disconnect() } Apply this suggestion Suggestion importance[1-10]: 3 Why: While the suggestion promotes a more organized cleanup approach, the order of cleanup operations in this case has minimal practical impact since both cleanup operations are independent.	3

qodo-merge-pro · 2025-01-26T10:15:46Z

Qodo Merge was enabled for this repository. To continue using it, please link your Git account with your Qodo account here.

CI Feedback 🧐

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: test
Failed stage: Run Playwright tests with detailed reporting [❌]
Failed test name: settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API
Failure summary: The action failed due to test failures in the Settings Tests suite: The test "@admin Modify MAX_INFO_QUERIES via UI validation via API" failed in both Chromium and Firefox browsers The test expected the input value "20" to match the actual value but they were not equal (value === input).toBe(expected) failed The test was retried 3 times but failed consistently There was also a flaky test failure for "Modify MAX_INFO_QUERIES via API validation via UI" with input value "0"
Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 1543: - Network: http://10.1.0.107:3000 1544: ✓ Starting... 1545: ⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead. 1546: ✓ Ready in 359ms 1547: Running 191 tests using 1 worker 1548: Running 191 tests using 1 worker 1549: [next-auth][warn][NEXTAUTH_URL] 1550: https://next-auth.js.org/warnings#nextauth_url 1551: TypeError: Cannot read properties of null (reading '1') 1552: at t.transformReply (.next/server/chunks/488.js:1:90312) 1553: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1554: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1555: at async p (.next/server/app/api/user/route.js:1:2243) 1556: TypeError: Cannot read properties of null (reading '1') 1557: at t.transformReply (.next/server/chunks/488.js:1:90312) 1558: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1559: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1560: at async p (.next/server/app/api/user/route.js:1:2243) 1561: · ✓ 1 [setup] › auth.setup.ts:12:6 › admin authentication (6.0s) 1562: [Error: NOPERM User readwriteuser has no permissions to run the 'acl\|getuser' command] 1563: [Error: ERR wrong number of arguments for 'graph.QUERY' command] 1564: · ✓ 2 [setup] › auth.setup.ts:36:10 › readwrite authentication (1.9s) 1565: [Error: NOPERM User readonlyuser has no permissions to run the 'acl\|getuser' command] 1566: [Error: NOPERM User readonlyuser has no permissions to run the 'graph.QUERY' command] ... 1570: · ✓ 6 [[Admin] Chromium] › graph.spec.ts:50:13 › Graph Tests › @admin Create graph -> click the Export Data button -> verify the file has been successfully downloaded (1.3s) 1571: · ✓ 7 [[Admin] Chromium] › graph.spec.ts:61:13 › Graph Tests › @admin Query Test: Create a graph via api -> run a query via api and validate that the response data is correct (24ms) 1572: · ✓ 8 [[Admin] Chromium] › navBar.spec.ts:20:13 › Navbar tests › @admin Verify clicking on FalkorDB logo redirects to specified URL (1.7s) 1573: · ✓ 9 [[Admin] Chromium] › navBar.spec.ts:29:13 › Navbar tests › @admin Verify clicking on Graphs button redirects to specified URL (1.1s) 1574: · ✓ 10 [[Admin] Chromium] › navBar.spec.ts:39:13 › Navbar tests › @admin Verify clicking on Schemas button redirects to specified URL (2.0s) 1575: · ✓ 11 [[Admin] Chromium] › navBar.spec.ts:49:13 › Navbar tests › @admin Verify clicking on help -> Documentation redirects to specified URL (1.1s) 1576: · ✓ 12 [[Admin] Chromium] › navBar.spec.ts:58:13 › Navbar tests › @admin Verify clicking on help -> Support redirects to specified URL (1.2s) 1577: · ✓ 13 [[Admin] Chromium] › navBar.spec.ts:67:13 › Navbar tests › @admin Verify clicking on Settings redirects to specified URL (1.0s) 1578: [Error: Failed to set config value MAX_QUEUED_QUERIES to NaN] 1579: · ✓ 14 [[Admin] Chromium] › settingsConfig.spec.ts:21:13 › Settings Tests › @admin Modify MAX_QUEUED_QUERIES via API validation via UI: Input value: aa description: invalid input - character (2.4s) 1580: [Error: Failed to set config value MAX_QUEUED_QUERIES to -3] 1581: · ✓ 15 [[Admin] Chromium] › settingsConfig.spec.ts:21:13 › Settings Tests › @admin Modify MAX_QUEUED_QUERIES via API validation via UI: Input value: -3 description: invalid input - negative number (2.2s) 1582: [Error: Failed to set config value MAX_QUEUED_QUERIES to 0] 1583: · ✓ 16 [[Admin] Chromium] › settingsConfig.spec.ts:21:13 › Settings Tests › @admin Modify MAX_QUEUED_QUERIES via API validation via UI: Input value: 00-1 description: invalid input (2.2s) 1584: · ✓ 17 [[Admin] Chromium] › settingsConfig.spec.ts:21:13 › Settings Tests › @admin Modify MAX_QUEUED_QUERIES via API validation via UI: Input value: 1 description: valid input (2.2s) 1585: [Error: Failed to set config value MAX_QUEUED_QUERIES to 0] 1586: · ✓ 18 [[Admin] Chromium] › settingsConfig.spec.ts:21:13 › Settings Tests › @admin Modify MAX_QUEUED_QUERIES via API validation via UI: Input value: 0 description: invalid input - zero value (2.2s) 1587: [Error: Failed to set config value TIMEOUT_MAX to NaN] 1588: · ✓ 19 [[Admin] Chromium] › settingsConfig.spec.ts:33:13 › Settings Tests › @admin Modify TIMEOUT_MAX via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1589: [Error: Failed to set config value TIMEOUT_MAX to -3] 1590: · ✓ 20 [[Admin] Chromium] › settingsConfig.spec.ts:33:13 › Settings Tests › @admin Modify TIMEOUT_MAX via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1591: · ✓ 21 [[Admin] Chromium] › settingsConfig.spec.ts:33:13 › Settings Tests › @admin Modify TIMEOUT_MAX via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1592: · ✓ 22 [[Admin] Chromium] › settingsConfig.spec.ts:33:13 › Settings Tests › @admin Modify TIMEOUT_MAX via API validation via UI: Input value: 30 description: valid input (1.2s) 1593: [Error: Failed to set config value TIMEOUT_DEFAULT to NaN] 1594: · ✓ 23 [[Admin] Chromium] › settingsConfig.spec.ts:44:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1595: [Error: Failed to set config value TIMEOUT_DEFAULT to -3] 1596: · ✓ 24 [[Admin] Chromium] › settingsConfig.spec.ts:44:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1597: · ✓ 25 [[Admin] Chromium] › settingsConfig.spec.ts:44:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1598: · ✓ 26 [[Admin] Chromium] › settingsConfig.spec.ts:44:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via API validation via UI: Input value: 1 description: valid input (1.2s) 1599: · ✓ 27 [[Admin] Chromium] › settingsConfig.spec.ts:44:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via API validation via UI: Input value: 0 description: valid input - zero value (1.2s) 1600: [Error: Failed to set config value RESULTSET_SIZE to NaN] 1601: · ✓ 28 [[Admin] Chromium] › settingsConfig.spec.ts:55:13 › Settings Tests › @admin Modify RESULTSET_SIZE via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1602: · ✓ 29 [[Admin] Chromium] › settingsConfig.spec.ts:55:13 › Settings Tests › @admin Modify RESULTSET_SIZE via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1603: · ✓ 30 [[Admin] Chromium] › settingsConfig.spec.ts:55:13 › Settings Tests › @admin Modify RESULTSET_SIZE via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1604: · ✓ 31 [[Admin] Chromium] › settingsConfig.spec.ts:55:13 › Settings Tests › @admin Modify RESULTSET_SIZE via API validation via UI: Input value: 1 description: valid input (1.2s) 1605: · ✓ 32 [[Admin] Chromium] › settingsConfig.spec.ts:55:13 › Settings Tests › @admin Modify RESULTSET_SIZE via API validation via UI: Input value: 0 description: valid input - zero value (1.2s) 1606: [Error: Failed to set config value QUERY_MEM_CAPACITY to NaN] 1607: · ✓ 33 [[Admin] Chromium] › settingsConfig.spec.ts:66:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1608: [Error: Failed to set config value QUERY_MEM_CAPACITY to -3] 1609: · ✓ 34 [[Admin] Chromium] › settingsConfig.spec.ts:66:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1610: · ✓ 35 [[Admin] Chromium] › settingsConfig.spec.ts:66:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1611: · ✓ 36 [[Admin] Chromium] › settingsConfig.spec.ts:66:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via API validation via UI: Input value: 1 description: valid input (1.2s) 1612: · ✓ 37 [[Admin] Chromium] › settingsConfig.spec.ts:66:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via API validation via UI: Input value: 0 description: valid input - zero value (1.2s) 1613: [Error: Failed to set config value VKEY_MAX_ENTITY_COUNT to NaN] 1614: · ✓ 38 [[Admin] Chromium] › settingsConfig.spec.ts:78:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1615: [Error: Failed to set config value VKEY_MAX_ENTITY_COUNT to -3] 1616: · ✓ 39 [[Admin] Chromium] › settingsConfig.spec.ts:78:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1617: · ✓ 40 [[Admin] Chromium] › settingsConfig.spec.ts:78:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1618: · ✓ 41 [[Admin] Chromium] › settingsConfig.spec.ts:78:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via API validation via UI: Input value: 1 description: valid input (1.2s) 1619: · ✓ 42 [[Admin] Chromium] › settingsConfig.spec.ts:78:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via API validation via UI: Input value: 0 description: valid input - zero value (1.2s) 1620: [Error: Failed to set config value CMD_INFO to aa] 1621: · ✓ 43 [[Admin] Chromium] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1622: [Error: Failed to set config value CMD_INFO to -3] 1623: · ✓ 44 [[Admin] Chromium] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1624: [Error: Failed to set config value CMD_INFO to 00-1] 1625: · ✓ 45 [[Admin] Chromium] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1626: [Error: Failed to set config value CMD_INFO to 10s] 1627: · ✓ 46 [[Admin] Chromium] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: 10s description: invalid input (1.2s) 1628: · ✓ 47 [[Admin] Chromium] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: no description: valid input - no value (1.2s) 1629: · ✓ 48 [[Admin] Chromium] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: yes description: valid input - yes value (1.2s) 1630: [Error: Failed to set config value MAX_INFO_QUERIES to NaN] 1631: · ✓ 49 [[Admin] Chromium] › settingsConfig.spec.ts:100:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1632: [Error: Failed to set config value MAX_INFO_QUERIES to -3] ... 1640: · ✓ 57 [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via UI validation via API: Input value: 10 description: modify defaultTimeOut (745ms) 1641: · ✓ 58 [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify RESULTSET_SIZE via UI validation via API: Input value: 20 description: modify resultSetSize (718ms) 1642: · ✓ 59 [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via UI validation via API: Input value: 20 description: modify queryMemCapacity (745ms) 1643: · ✓ 60 [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via UI validation via API: Input value: 20 description: modify vKeyMaxEntityCount (711ms) 1644: · ✓ 61 [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify CMD_INFO via UI validation via API: Input value: yes description: modify cmdInfo (751ms) 1645: × ✘ 62 [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries (747ms) 1646: × ✘ 63 [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries (retry #1) (1.1s) 1647: F ✘ 64 [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries (retry #2) (1.0s) 1648: TypeError: Cannot read properties of null (reading '1') 1649: at t.transformReply (.next/server/chunks/488.js:1:90312) 1650: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1651: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1652: at async p (.next/server/app/api/user/route.js:1:2243) 1653: · ✓ 65 [[Admin] Chromium] › settingsUsers.spec.ts:19:9 › Settings Tests › @admin Add one new user -> validating user exists in the users list (2.8s) 1654: TypeError: Cannot read properties of null (reading '1') 1655: at t.transformReply (.next/server/chunks/488.js:1:90312) 1656: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1657: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1658: at async p (.next/server/app/api/user/route.js:1:2243) 1659: · ✓ 66 [[Admin] Chromium] › settingsUsers.spec.ts:29:9 › Settings Tests › @admin Add one user -> remove one user -> Validate that the user has been removed (3.1s) 1660: TypeError: Cannot read properties of null (reading '1') 1661: at t.transformReply (.next/server/chunks/488.js:1:90312) 1662: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1663: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1664: at async p (.next/server/app/api/user/route.js:1:2243) 1665: · ✓ 67 [[Admin] Chromium] › settingsUsers.spec.ts:44:9 › Settings Tests › @admin Add one user -> change the role -> Validate that the user role have been changed (4.1s) 1666: TypeError: Cannot read properties of null (reading '1') 1667: at t.transformReply (.next/server/chunks/488.js:1:90312) 1668: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1669: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1670: at async p (.next/server/app/api/user/route.js:1:2243) 1671: TypeError: Cannot read properties of null (reading '1') 1672: at t.transformReply (.next/server/chunks/488.js:1:90312) 1673: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1674: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1675: at async p (.next/server/app/api/user/route.js:1:2243) 1676: · ✓ 68 [[Admin] Chromium] › settingsUsers.spec.ts:59:9 › Settings Tests › @admin Add two users -> change their roles via checkbox -> Validate that the users roles have been changed (6.5s) 1677: TypeError: Cannot read properties of null (reading '1') 1678: at t.transformReply (.next/server/chunks/488.js:1:90312) 1679: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1680: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1681: at async p (.next/server/app/api/user/route.js:1:2243) 1682: TypeError: Cannot read properties of null (reading '1') ... 1687: · ✓ 69 [[Admin] Chromium] › settingsUsers.spec.ts:80:9 › Settings Tests › @admin Add two users -> delete the two users by checkbox -> Validate that the users have been deleted (6.3s) 1688: · ✓ 70 [[Admin] Chromium] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: Test123 reason: short password (3.0s) 1689: · ✓ 71 [[Admin] Chromium] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: Test1234 reason: without special character (3.0s) 1690: · ✓ 72 [[Admin] Chromium] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: Testtes@ reason: without digits (3.0s) 1691: · ✓ 73 [[Admin] Chromium] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: TESTES1@ reason: without lowercase letters (3.0s) 1692: · ✓ 74 [[Admin] Chromium] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: testte1@ reason: without uppercase letters (3.0s) 1693: · ✓ 75 [[Admin] Chromium] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: reason: without password (3.0s) 1694: · ✓ 76 [[Admin] Chromium] › settingsUsers.spec.ts:121:9 › Settings Tests › @admin Attempt to add a user without assigning a role -> Verify that the user has not been added (2.9s) 1695: [Error: ERR The 'default' user cannot be removed] 1696: · ✓ 77 [[Admin] Chromium] › settingsUsers.spec.ts:132:9 › Settings Tests › @admin Attempt to delete the default admin user -> Verify that the user has not been deleted. (748ms) 1697: TypeError: Cannot read properties of null (reading '1') 1698: at t.transformReply (.next/server/chunks/488.js:1:90312) 1699: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1700: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1701: at async p (.next/server/app/api/user/route.js:1:2243) 1702: Error: Missing parameters 1703: at p (.next/server/app/api/user/route.js:1:2208) 1704: · ✓ 78 [[Admin] Chromium] › settingsUsers.spec.ts:140:9 › Settings Tests › @admin API Test:Add user via API -> Validated user existing via API -> Delete user via API. (42ms) 1705: Error: Missing parameters 1706: at p (.next/server/app/api/user/route.js:1:2208) 1707: · ✓ 79 [[Admin] Chromium] › settingsUsers.spec.ts:150:9 › Settings Tests › @admin API Test: without passing a username, Attempt to add a user and validate the user was not added (14ms) 1708: Error: Missing parameters 1709: at p (.next/server/app/api/user/route.js:1:2208) 1710: · ✓ 80 [[Admin] Chromium] › settingsUsers.spec.ts:159:9 › Settings Tests › @admin API Test: without passing a role, Attempt to add a user and validate the user was not added (14ms) 1711: Error: Missing parameters ... 1717: · ✓ 85 [[Admin] Firefox] › graph.spec.ts:50:13 › Graph Tests › @admin Create graph -> click the Export Data button -> verify the file has been successfully downloaded (1.2s) 1718: · ✓ 86 [[Admin] Firefox] › graph.spec.ts:61:13 › Graph Tests › @admin Query Test: Create a graph via api -> run a query via api and validate that the response data is correct (25ms) 1719: · ✓ 87 [[Admin] Firefox] › navBar.spec.ts:20:13 › Navbar tests › @admin Verify clicking on FalkorDB logo redirects to specified URL (1.6s) 1720: · ✓ 88 [[Admin] Firefox] › navBar.spec.ts:29:13 › Navbar tests › @admin Verify clicking on Graphs button redirects to specified URL (1.1s) 1721: · ✓ 89 [[Admin] Firefox] › navBar.spec.ts:39:13 › Navbar tests › @admin Verify clicking on Schemas button redirects to specified URL (2.0s) 1722: · ✓ 90 [[Admin] Firefox] › navBar.spec.ts:49:13 › Navbar tests › @admin Verify clicking on help -> Documentation redirects to specified URL (1.1s) 1723: · ✓ 91 [[Admin] Firefox] › navBar.spec.ts:58:13 › Navbar tests › @admin Verify clicking on help -> Support redirects to specified URL (1.2s) 1724: · ✓ 92 [[Admin] Firefox] › navBar.spec.ts:67:13 › Navbar tests › @admin Verify clicking on Settings redirects to specified URL (1.1s) 1725: [Error: Failed to set config value MAX_QUEUED_QUERIES to NaN] 1726: · ✓ 93 [[Admin] Firefox] › settingsConfig.spec.ts:21:13 › Settings Tests › @admin Modify MAX_QUEUED_QUERIES via API validation via UI: Input value: aa description: invalid input - character (2.4s) 1727: [Error: Failed to set config value MAX_QUEUED_QUERIES to -3] 1728: · ✓ 94 [[Admin] Firefox] › settingsConfig.spec.ts:21:13 › Settings Tests › @admin Modify MAX_QUEUED_QUERIES via API validation via UI: Input value: -3 description: invalid input - negative number (2.2s) 1729: [Error: Failed to set config value MAX_QUEUED_QUERIES to 0] 1730: · ✓ 95 [[Admin] Firefox] › settingsConfig.spec.ts:21:13 › Settings Tests › @admin Modify MAX_QUEUED_QUERIES via API validation via UI: Input value: 00-1 description: invalid input (2.2s) 1731: · ✓ 96 [[Admin] Firefox] › settingsConfig.spec.ts:21:13 › Settings Tests › @admin Modify MAX_QUEUED_QUERIES via API validation via UI: Input value: 1 description: valid input (2.2s) 1732: [Error: Failed to set config value MAX_QUEUED_QUERIES to 0] 1733: · ✓ 97 [[Admin] Firefox] › settingsConfig.spec.ts:21:13 › Settings Tests › @admin Modify MAX_QUEUED_QUERIES via API validation via UI: Input value: 0 description: invalid input - zero value (2.2s) 1734: [Error: Failed to set config value TIMEOUT_MAX to NaN] 1735: · ✓ 98 [[Admin] Firefox] › settingsConfig.spec.ts:33:13 › Settings Tests › @admin Modify TIMEOUT_MAX via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1736: [Error: Failed to set config value TIMEOUT_MAX to -3] 1737: · ✓ 99 [[Admin] Firefox] › settingsConfig.spec.ts:33:13 › Settings Tests › @admin Modify TIMEOUT_MAX via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1738: · ✓ 100 [[Admin] Firefox] › settingsConfig.spec.ts:33:13 › Settings Tests › @admin Modify TIMEOUT_MAX via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1739: · ✓ 101 [[Admin] Firefox] › settingsConfig.spec.ts:33:13 › Settings Tests › @admin Modify TIMEOUT_MAX via API validation via UI: Input value: 30 description: valid input (1.2s) 1740: [Error: Failed to set config value TIMEOUT_DEFAULT to NaN] 1741: · ✓ 102 [[Admin] Firefox] › settingsConfig.spec.ts:44:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1742: [Error: Failed to set config value TIMEOUT_DEFAULT to -3] 1743: · ✓ 103 [[Admin] Firefox] › settingsConfig.spec.ts:44:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1744: · ✓ 104 [[Admin] Firefox] › settingsConfig.spec.ts:44:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1745: · ✓ 105 [[Admin] Firefox] › settingsConfig.spec.ts:44:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via API validation via UI: Input value: 1 description: valid input (1.2s) 1746: · ✓ 106 [[Admin] Firefox] › settingsConfig.spec.ts:44:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via API validation via UI: Input value: 0 description: valid input - zero value (1.2s) 1747: [Error: Failed to set config value RESULTSET_SIZE to NaN] 1748: · ✓ 107 [[Admin] Firefox] › settingsConfig.spec.ts:55:13 › Settings Tests › @admin Modify RESULTSET_SIZE via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1749: · ✓ 108 [[Admin] Firefox] › settingsConfig.spec.ts:55:13 › Settings Tests › @admin Modify RESULTSET_SIZE via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1750: · ✓ 109 [[Admin] Firefox] › settingsConfig.spec.ts:55:13 › Settings Tests › @admin Modify RESULTSET_SIZE via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1751: · ✓ 110 [[Admin] Firefox] › settingsConfig.spec.ts:55:13 › Settings Tests › @admin Modify RESULTSET_SIZE via API validation via UI: Input value: 1 description: valid input (1.2s) 1752: · ✓ 111 [[Admin] Firefox] › settingsConfig.spec.ts:55:13 › Settings Tests › @admin Modify RESULTSET_SIZE via API validation via UI: Input value: 0 description: valid input - zero value (1.2s) 1753: [Error: Failed to set config value QUERY_MEM_CAPACITY to NaN] 1754: · ✓ 112 [[Admin] Firefox] › settingsConfig.spec.ts:66:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1755: [Error: Failed to set config value QUERY_MEM_CAPACITY to -3] 1756: · ✓ 113 [[Admin] Firefox] › settingsConfig.spec.ts:66:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1757: · ✓ 114 [[Admin] Firefox] › settingsConfig.spec.ts:66:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1758: · ✓ 115 [[Admin] Firefox] › settingsConfig.spec.ts:66:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via API validation via UI: Input value: 1 description: valid input (1.2s) 1759: · ✓ 116 [[Admin] Firefox] › settingsConfig.spec.ts:66:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via API validation via UI: Input value: 0 description: valid input - zero value (1.2s) 1760: [Error: Failed to set config value VKEY_MAX_ENTITY_COUNT to NaN] 1761: · ✓ 117 [[Admin] Firefox] › settingsConfig.spec.ts:78:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1762: [Error: Failed to set config value VKEY_MAX_ENTITY_COUNT to -3] 1763: · ✓ 118 [[Admin] Firefox] › settingsConfig.spec.ts:78:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1764: · ✓ 119 [[Admin] Firefox] › settingsConfig.spec.ts:78:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1765: · ✓ 120 [[Admin] Firefox] › settingsConfig.spec.ts:78:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via API validation via UI: Input value: 1 description: valid input (1.2s) 1766: · ✓ 121 [[Admin] Firefox] › settingsConfig.spec.ts:78:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via API validation via UI: Input value: 0 description: valid input - zero value (1.2s) 1767: [Error: Failed to set config value CMD_INFO to aa] 1768: · ✓ 122 [[Admin] Firefox] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1769: [Error: Failed to set config value CMD_INFO to -3] 1770: · ✓ 123 [[Admin] Firefox] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: -3 description: invalid input - negative number (1.2s) 1771: [Error: Failed to set config value CMD_INFO to 00-1] 1772: · ✓ 124 [[Admin] Firefox] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: 00-1 description: invalid input (1.2s) 1773: [Error: Failed to set config value CMD_INFO to 10s] 1774: · ✓ 125 [[Admin] Firefox] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: 10s description: invalid input (1.2s) 1775: · ✓ 126 [[Admin] Firefox] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: no description: valid input - no value (1.2s) 1776: · ✓ 127 [[Admin] Firefox] › settingsConfig.spec.ts:89:13 › Settings Tests › @admin Modify CMD_INFO via API validation via UI: Input value: yes description: valid input - yes value (1.2s) 1777: [Error: Failed to set config value MAX_INFO_QUERIES to NaN] 1778: · ✓ 128 [[Admin] Firefox] › settingsConfig.spec.ts:100:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via API validation via UI: Input value: aa description: invalid input - character (1.2s) 1779: [Error: Failed to set config value MAX_INFO_QUERIES to -3] ... 1786: · ✓ 135 [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via UI validation via API: Input value: 10 description: modify defaultTimeOut (732ms) 1787: · ✓ 136 [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify RESULTSET_SIZE via UI validation via API: Input value: 20 description: modify resultSetSize (731ms) 1788: · ✓ 137 [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify QUERY_MEM_CAPACITY via UI validation via API: Input value: 20 description: modify queryMemCapacity (716ms) 1789: · ✓ 138 [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify VKEY_MAX_ENTITY_COUNT via UI validation via API: Input value: 20 description: modify vKeyMaxEntityCount (734ms) 1790: · ✓ 139 [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify CMD_INFO via UI validation via API: Input value: yes description: modify cmdInfo (710ms) 1791: × ✘ 140 [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries (719ms) 1792: × ✘ 141 [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries (retry #1) (1.1s) 1793: F ✘ 142 [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries (retry #2) (1.0s) 1794: TypeError: Cannot read properties of null (reading '1') 1795: at t.transformReply (.next/server/chunks/488.js:1:90312) 1796: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1797: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1798: at async p (.next/server/app/api/user/route.js:1:2243) 1799: · ✓ 143 [[Admin] Firefox] › settingsUsers.spec.ts:19:9 › Settings Tests › @admin Add one new user -> validating user exists in the users list (2.8s) 1800: TypeError: Cannot read properties of null (reading '1') 1801: at t.transformReply (.next/server/chunks/488.js:1:90312) 1802: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1803: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1804: at async p (.next/server/app/api/user/route.js:1:2243) 1805: · ✓ 144 [[Admin] Firefox] › settingsUsers.spec.ts:29:9 › Settings Tests › @admin Add one user -> remove one user -> Validate that the user has been removed (3.1s) 1806: TypeError: Cannot read properties of null (reading '1') 1807: at t.transformReply (.next/server/chunks/488.js:1:90312) 1808: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1809: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1810: at async p (.next/server/app/api/user/route.js:1:2243) 1811: · ✓ 145 [[Admin] Firefox] › settingsUsers.spec.ts:44:9 › Settings Tests › @admin Add one user -> change the role -> Validate that the user role have been changed (4.1s) 1812: TypeError: Cannot read properties of null (reading '1') 1813: at t.transformReply (.next/server/chunks/488.js:1:90312) 1814: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1815: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1816: at async p (.next/server/app/api/user/route.js:1:2243) 1817: TypeError: Cannot read properties of null (reading '1') 1818: at t.transformReply (.next/server/chunks/488.js:1:90312) 1819: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1820: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1821: at async p (.next/server/app/api/user/route.js:1:2243) 1822: · ✓ 146 [[Admin] Firefox] › settingsUsers.spec.ts:59:9 › Settings Tests › @admin Add two users -> change their roles via checkbox -> Validate that the users roles have been changed (6.4s) 1823: TypeError: Cannot read properties of null (reading '1') 1824: at t.transformReply (.next/server/chunks/488.js:1:90312) 1825: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1826: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1827: at async p (.next/server/app/api/user/route.js:1:2243) 1828: TypeError: Cannot read properties of null (reading '1') ... 1833: · ✓ 147 [[Admin] Firefox] › settingsUsers.spec.ts:80:9 › Settings Tests › @admin Add two users -> delete the two users by checkbox -> Validate that the users have been deleted (6.4s) 1834: · ✓ 148 [[Admin] Firefox] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: Test123 reason: short password (3.0s) 1835: · ✓ 149 [[Admin] Firefox] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: Test1234 reason: without special character (3.0s) 1836: · ✓ 150 [[Admin] Firefox] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: Testtes@ reason: without digits (3.0s) 1837: · ✓ 151 [[Admin] Firefox] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: TESTES1@ reason: without lowercase letters (3.0s) 1838: · ✓ 152 [[Admin] Firefox] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: testte1@ reason: without uppercase letters (3.0s) 1839: · ✓ 153 [[Admin] Firefox] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: reason: without password (3.0s) 1840: · ✓ 154 [[Admin] Firefox] › settingsUsers.spec.ts:121:9 › Settings Tests › @admin Attempt to add a user without assigning a role -> Verify that the user has not been added (2.9s) 1841: [Error: ERR The 'default' user cannot be removed] 1842: · ✓ 155 [[Admin] Firefox] › settingsUsers.spec.ts:132:9 › Settings Tests › @admin Attempt to delete the default admin user -> Verify that the user has not been deleted. (771ms) 1843: TypeError: Cannot read properties of null (reading '1') 1844: at t.transformReply (.next/server/chunks/488.js:1:90312) 1845: at t.transformCommandReply (.next/server/chunks/488.js:1:89110) 1846: at n.commandsExecutor (.next/server/chunks/488.js:1:41157) 1847: at async p (.next/server/app/api/user/route.js:1:2243) 1848: Error: Missing parameters 1849: at p (.next/server/app/api/user/route.js:1:2208) 1850: · ✓ 156 [[Admin] Firefox] › settingsUsers.spec.ts:140:9 › Settings Tests › @admin API Test:Add user via API -> Validated user existing via API -> Delete user via API. (42ms) 1851: Error: Missing parameters 1852: at p (.next/server/app/api/user/route.js:1:2208) 1853: · ✓ 157 [[Admin] Firefox] › settingsUsers.spec.ts:150:9 › Settings Tests › @admin API Test: without passing a username, Attempt to add a user and validate the user was not added (15ms) 1854: Error: Missing parameters 1855: at p (.next/server/app/api/user/route.js:1:2208) 1856: · ✓ 158 [[Admin] Firefox] › settingsUsers.spec.ts:159:9 › Settings Tests › @admin API Test: without passing a role, Attempt to add a user and validate the user was not added (15ms) 1857: Error: Missing parameters ... 1890: · ✓ 190 [[Read-Only] - Firefox] › navBar.spec.ts:20:13 › Navbar tests › @readonly Verify clicking on FalkorDB logo redirects to specified URL (1.7s) 1891: · ✓ 191 [[Read-Only] - Firefox] › navBar.spec.ts:29:13 › Navbar tests › @readonly Verify clicking on Graphs button redirects to specified URL (1.1s) 1892: · ✓ 192 [[Read-Only] - Firefox] › navBar.spec.ts:39:13 › Navbar tests › @readonly Verify clicking on Schemas button redirects to specified URL (2.0s) 1893: · ✓ 193 [[Read-Only] - Firefox] › navBar.spec.ts:49:13 › Navbar tests › @readonly Verify clicking on help -> Documentation redirects to specified URL (1.1s) 1894: · ✓ 194 [[Read-Only] - Firefox] › navBar.spec.ts:58:13 › Navbar tests › @readonly Verify clicking on help -> Support redirects to specified URL (1.2s) 1895: · ✓ 195 [[Read-Only] - Firefox] › navBar.spec.ts:67:13 › Navbar tests › @readonly Verify clicking on Settings redirects to specified URL (1.1s) 1896: · ✓ 196 [[Read-Only] - Firefox] › signOut.spec.ts:19:13 › @readonly SignOut Test › Sign out Test (2.5s) 1897: 1) [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries 1898: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 1902: 122 \| await apiCall.modifySettingsRole(roles.queryMemCapacity, "0") // update to default values 1903: > 123 \| expect(value === input).toBe(expected) 1904: \| ^ 1905: 124 \| }); 1906: 125 \| }) 1907: 126 \| 1908: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 1909: Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── 1910: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 1919: 126 \| 1920: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 1921: attachment #1: trace (application/zip) ───────────────────────────────────────────────────────── 1922: test-results/settingsConfig-Settings-Te-9ddaf-ption-modify-maxInfoQueries--Admin-Chromium-retry1/trace.zip 1923: Usage: 1924: npx playwright show-trace test-results/settingsConfig-Settings-Te-9ddaf-ption-modify-maxInfoQueries--Admin-Chromium-retry1/trace.zip 1925: ──────────────────────────────────────────────────────────────────────────────────────────────── 1926: Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── 1927: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 1931: 122 \| await apiCall.modifySettingsRole(roles.queryMemCapacity, "0") // update to default values 1932: > 123 \| expect(value === input).toBe(expected) 1933: \| ^ 1934: 124 \| }); 1935: 125 \| }) 1936: 126 \| 1937: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 1938: 2) [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries 1939: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 1943: 122 \| await apiCall.modifySettingsRole(roles.queryMemCapacity, "0") // update to default values 1944: > 123 \| expect(value === input).toBe(expected) 1945: \| ^ 1946: 124 \| }); 1947: 125 \| }) 1948: 126 \| 1949: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 1950: Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── 1951: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 1960: 126 \| 1961: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 1962: attachment #1: trace (application/zip) ───────────────────────────────────────────────────────── 1963: test-results/settingsConfig-Settings-Te-9ddaf-ption-modify-maxInfoQueries--Admin-Firefox-retry1/trace.zip 1964: Usage: 1965: npx playwright show-trace test-results/settingsConfig-Settings-Te-9ddaf-ption-modify-maxInfoQueries--Admin-Firefox-retry1/trace.zip 1966: ──────────────────────────────────────────────────────────────────────────────────────────────── 1967: Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── 1968: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 1972: 122 \| await apiCall.modifySettingsRole(roles.queryMemCapacity, "0") // update to default values 1973: > 123 \| expect(value === input).toBe(expected) 1974: \| ^ 1975: 124 \| }); 1976: 125 \| }) 1977: 126 \| 1978: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 1979: 3) [[Admin] Chromium] › settingsConfig.spec.ts:100:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via API validation via UI: Input value: 0 description: valid input - zero value 1980: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 1986: \| ^ 1987: 107 \| }); 1988: 108 \| }) 1989: 109 \| 1990: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:106:37 1991: Slow test file: [[Admin] Firefox] › settingsUsers.spec.ts (44.4s) 1992: Slow test file: [[Admin] Chromium] › settingsUsers.spec.ts (44.3s) 1993: Consider splitting slow test files to speed up parallel execution 1994: 2 failed 1995: [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries 1996: [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries 1997: 1 flaky 1998: [[Admin] Chromium] › settingsConfig.spec.ts:100:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via API validation via UI: Input value: 0 description: valid input - zero value 1999: 188 passed (5.6m) 2000: 1) [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries 2001: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 2005: 122 \| await apiCall.modifySettingsRole(roles.queryMemCapacity, "0") // update to default values 2006: > 123 \| expect(value === input).toBe(expected) 2007: \| ^ 2008: 124 \| }); 2009: 125 \| }) 2010: 126 \| 2011: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 2012: Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── 2013: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 2022: 126 \| 2023: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 2024: attachment #1: trace (application/zip) ───────────────────────────────────────────────────────── 2025: test-results/settingsConfig-Settings-Te-9ddaf-ption-modify-maxInfoQueries--Admin-Chromium-retry1/trace.zip 2026: Usage: 2027: npx playwright show-trace test-results/settingsConfig-Settings-Te-9ddaf-ption-modify-maxInfoQueries--Admin-Chromium-retry1/trace.zip 2028: ──────────────────────────────────────────────────────────────────────────────────────────────── 2029: Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── 2030: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 2034: 122 \| await apiCall.modifySettingsRole(roles.queryMemCapacity, "0") // update to default values 2035: > 123 \| expect(value === input).toBe(expected) 2036: \| ^ 2037: 124 \| }); 2038: 125 \| }) 2039: 126 \| 2040: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 2041: 2) [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries 2042: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 2046: 122 \| await apiCall.modifySettingsRole(roles.queryMemCapacity, "0") // update to default values 2047: > 123 \| expect(value === input).toBe(expected) 2048: \| ^ 2049: 124 \| }); 2050: 125 \| }) 2051: 126 \| 2052: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 2053: Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── 2054: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 2063: 126 \| 2064: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 2065: attachment #1: trace (application/zip) ───────────────────────────────────────────────────────── 2066: test-results/settingsConfig-Settings-Te-9ddaf-ption-modify-maxInfoQueries--Admin-Firefox-retry1/trace.zip 2067: Usage: 2068: npx playwright show-trace test-results/settingsConfig-Settings-Te-9ddaf-ption-modify-maxInfoQueries--Admin-Firefox-retry1/trace.zip 2069: ──────────────────────────────────────────────────────────────────────────────────────────────── 2070: Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── 2071: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 2075: 122 \| await apiCall.modifySettingsRole(roles.queryMemCapacity, "0") // update to default values 2076: > 123 \| expect(value === input).toBe(expected) 2077: \| ^ 2078: 124 \| }); 2079: 125 \| }) 2080: 126 \| 2081: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37 2082: 3) [[Admin] Chromium] › settingsConfig.spec.ts:100:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via API validation via UI: Input value: 0 description: valid input - zero value 2083: Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m ... 2089: \| ^ 2090: 107 \| }); 2091: 108 \| }) 2092: 109 \| 2093: at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:106:37 2094: Slow test file: [[Admin] Firefox] › settingsUsers.spec.ts (44.4s) 2095: Slow test file: [[Admin] Chromium] › settingsUsers.spec.ts (44.3s) 2096: Consider splitting slow test files to speed up parallel execution 2097: 2 failed 2098: [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries 2099: [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via UI validation via API: Input value: 20 description: modify maxInfoQueries 2100: 1 flaky 2101: [[Admin] Chromium] › settingsConfig.spec.ts:100:13 › Settings Tests › @admin Modify MAX_INFO_QUERIES via API validation via UI: Input value: 0 description: valid input - zero value 2102: 188 passed (5.6m) 2103: ##[error]Process completed with exit code 1. ... 2121: [command]/usr/bin/git config --local --name-only --get-regexp core\.sshCommand 2122: [command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' \|\| :" 2123: [command]/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader 2124: http.https://github.com/.extraheader 2125: [command]/usr/bin/git config --local --unset-all http.https://github.com/.extraheader 2126: [command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' \|\| :" 2127: Print service container logs: 55d206587f4c4beb9b0d4e0adff068ea_falkordbfalkordblatest_0b033c 2128: ##[command]/usr/bin/docker logs --details 45b1237aa9a5baebe99f9c9d0ce574edce70d9f2c9f90ecae0cc6aa6f282e2ba 2129: 11:C 26 Jan 2025 10:07:48.452 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.

commit

86d6fea

Anchel123 linked an issue Jan 26, 2025 that may be closed by this pull request

Canvas resize don't work as excepted #634

Open

Merge branch 'staging' into fix-resize

6bfe542

vercel bot deployed to Preview January 28, 2025 19:22 View deployment

Anchel123 changed the title ~~Fix # fix canvas resize~~ Fix #634 fix canvas resize Jan 29, 2025

barakb approved these changes Jan 29, 2025

View reviewed changes

Merge branch 'staging' into fix-resize

14a7850

vercel bot deployed to Preview January 29, 2025 10:19 View deployment

Anchel123 merged commit 62c52ef into staging Jan 29, 2025
8 checks passed

Anchel123 deleted the fix-resize branch January 29, 2025 10:28

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix #634 fix canvas resize #626

Fix #634 fix canvas resize #626

Anchel123 commented Jan 26, 2025 •

edited by qodo-merge-pro bot

Loading

vercel bot commented Jan 26, 2025 •

edited

Loading

coderabbitai bot commented Jan 26, 2025

Review skipped

Chat

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (`.coderabbit.yaml`)

Documentation and Community

qodo-merge-pro bot commented Jan 26, 2025

qodo-merge-pro bot commented Jan 26, 2025

qodo-merge-pro bot commented Jan 26, 2025

Fix #634 fix canvas resize #626

Fix #634 fix canvas resize #626

Conversation

Anchel123 commented Jan 26, 2025 • edited by qodo-merge-pro bot Loading

PR Type

Description

Changes walkthrough 📝

vercel bot commented Jan 26, 2025 • edited Loading

coderabbitai bot commented Jan 26, 2025

Review skipped

Chat

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (.coderabbit.yaml)

Documentation and Community

qodo-merge-pro bot commented Jan 26, 2025

PR Reviewer Guide 🔍

qodo-merge-pro bot commented Jan 26, 2025

PR Code Suggestions ✨

qodo-merge-pro bot commented Jan 26, 2025

CI Feedback 🧐

Anchel123 commented Jan 26, 2025 •

edited by qodo-merge-pro bot

Loading

vercel bot commented Jan 26, 2025 •

edited

Loading

CodeRabbit Configuration File (`.coderabbit.yaml`)