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

Fix #627 restyle landing page #628

Merged
merged 2 commits into from
Jan 29, 2025
Merged

Fix #627 restyle landing page #628

merged 2 commits into from
Jan 29, 2025

Conversation

Anchel123
Copy link
Contributor

@Anchel123 Anchel123 commented Jan 26, 2025

PR Type

Enhancement


Description

  • Updated landing page background and layout styling.

  • Replaced LandingPage class with bg-foreground for consistency.

  • Added logo, version, and copyright information to the landing page.

  • Renamed and repurposed CSS gradient class for better clarity.


Changes walkthrough 📝

Relevant files
Enhancement
Header.tsx
Update gradient styling in Header component                           

app/components/Header.tsx

  • Replaced Top class with Gradient for the div element.
  • Updated styling reference for consistency with new CSS changes.
  • +1/-1     
    layout.tsx
    Update body class for layout styling                                         

    app/layout.tsx

  • Replaced LandingPage class with bg-foreground for the body element.
  • Improved layout styling for better visual consistency.
  • +1/-1     
    page.tsx
    Enhance landing page with branding and footer                       

    app/page.tsx

  • Added logo display using Image component.
  • Included version and copyright information at the bottom.
  • Replaced LandingPage class with bg-foreground for the main div.
  • Added gradient footer for visual enhancement.
  • +11/-3   
    globals.css
    Update global CSS for landing page restyling                         

    app/globals.css

  • Removed LandingPage class and its background gradient.
  • Renamed Top class to Gradient and updated its purpose.
  • Simplified CSS for better maintainability.
  • +1/-5     

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

    vercel bot commented Jan 26, 2025

    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 28, 2025 7:23pm

    Copy link
    Contributor

    coderabbitai bot commented Jan 26, 2025

    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.

    Copy link

    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

    Version Display

    The version string template literal appears malformed with extra curly braces. Should verify the version displays correctly.

    <p>Version: {`{${pkg.version}}`}</p>
    Copyright Year

    The copyright year range starts from 2024 instead of using the current year, which may be incorrect if deployed before 2024.

    <p className="text-sm">All Rights Reserved © 2024 - {new Date().getFullYear()} falkordb.com</p>

    Copy link

    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:

    CategorySuggestion                                                                                                                                    Score
    Possible issue
    Fix invalid version string syntax

    The version string template literal contains invalid syntax. Remove the curly braces
    around pkg.version to properly display the version number.

    app/page.tsx [15]

    -<p>Version: {`{${pkg.version}}`}</p>
    +<p>Version: {pkg.version}</p>
    • Apply this suggestion
    Suggestion importance[1-10]: 9

    Why: The current version string template contains redundant curly braces that would cause incorrect version display. This fix is critical for proper version information presentation.

    9
    General
    Add image error handling

    Add error handling for the Image component to gracefully handle cases where the logo
    file is missing or fails to load.

    app/page.tsx [11]

    -<Image priority src="/BrowserLogo.svg" alt="FalkorDB Logo" width={400} height={100} />
    +<Image priority src="/BrowserLogo.svg" alt="FalkorDB Logo" width={400} height={100} onError={(e) => e.currentTarget.style.display = 'none'} />
    • Apply this suggestion
    Suggestion importance[1-10]: 6

    Why: Adding error handling for the Image component improves user experience by gracefully handling logo loading failures, though the issue is not critical for core functionality.

    6

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

    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 test failed in the Settings Tests section when trying to modify the MAX_INFO_QUERIES setting via
    UI validation API. Specifically:

  • The test expected the input value "20" to match the actual value returned from the API
  • The test failed with an equality comparison error on line 123 of settingsConfig.spec.ts
  • The failure occurred in both Chromium and Firefox browsers
  • The test was retried 3 times but failed consistently with the same error

  • Relevant error logs:
    1:  ##[group]Operating System
    2:  Ubuntu
    ...
    
    1544:  - Network:      http://10.1.0.160:3000
    1545:  ✓ Starting...
    1546:  ⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead.
    1547:  ✓ Ready in 371ms
    1548:  Running 191 tests using 1 worker
    1549:  Running 191 tests using 1 worker
    1550:  [next-auth][warn][NEXTAUTH_URL] 
    1551:  https://next-auth.js.org/warnings#nextauth_url
    1552:  TypeError: Cannot read properties of null (reading '1')
    1553:  at t.transformReply (.next/server/chunks/488.js:1:90312)
    1554:  at t.transformCommandReply (.next/server/chunks/488.js:1:89110)
    1555:  at n.commandsExecutor (.next/server/chunks/488.js:1:41157)
    1556:  at async p (.next/server/app/api/user/route.js:1:2243)
    1557:  TypeError: Cannot read properties of null (reading '1')
    1558:  at t.transformReply (.next/server/chunks/488.js:1:90312)
    1559:  at t.transformCommandReply (.next/server/chunks/488.js:1:89110)
    1560:  at n.commandsExecutor (.next/server/chunks/488.js:1:41157)
    1561:  at async p (.next/server/app/api/user/route.js:1:2243)
    1562:  ·  ✓  1 [setup] › auth.setup.ts:12:6 › admin authentication (6.0s)
    1563:  [Error: NOPERM User readwriteuser has no permissions to run the 'acl|getuser' command]
    1564:  [Error: ERR wrong number of arguments for 'graph.QUERY' command]
    1565:  ·  ✓  2 [setup] › auth.setup.ts:36:10 › readwrite authentication (1.9s)
    1566:  [Error: NOPERM User readonlyuser has no permissions to run the 'acl|getuser' command]
    1567:  [Error: NOPERM User readonlyuser has no permissions to run the 'graph.QUERY' command]
    ...
    
    1571:  ·  ✓  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.2s)
    1572:  ·  ✓  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 (21ms)
    1573:  ·  ✓  8 [[Admin] Chromium] › navBar.spec.ts:20:13 › Navbar tests › @admin Verify clicking on FalkorDB logo redirects to specified URL (1.7s)
    1574:  ·  ✓  9 [[Admin] Chromium] › navBar.spec.ts:29:13 › Navbar tests › @admin Verify clicking on Graphs button redirects to specified URL (1.1s)
    1575:  ·  ✓  10 [[Admin] Chromium] › navBar.spec.ts:39:13 › Navbar tests › @admin Verify clicking on Schemas button redirects to specified URL (2.0s)
    1576:  ·  ✓  11 [[Admin] Chromium] › navBar.spec.ts:49:13 › Navbar tests › @admin Verify clicking on help -> Documentation redirects to specified URL (1.2s)
    1577:  ·  ✓  12 [[Admin] Chromium] › navBar.spec.ts:58:13 › Navbar tests › @admin Verify clicking on help -> Support redirects to specified URL (1.3s)
    1578:  ·  ✓  13 [[Admin] Chromium] › navBar.spec.ts:67:13 › Navbar tests › @admin Verify clicking on Settings redirects to specified URL (1.1s)
    1579:  [Error: Failed to set config value MAX_QUEUED_QUERIES to NaN]
    1580:  ·  ✓  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.5s)
    1581:  [Error: Failed to set config value MAX_QUEUED_QUERIES to -3]
    1582:  ·  ✓  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)
    1583:  [Error: Failed to set config value MAX_QUEUED_QUERIES to 0]
    1584:  ·  ✓  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)
    1585:  ·  ✓  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)
    1586:  [Error: Failed to set config value MAX_QUEUED_QUERIES to 0]
    1587:  ·  ✓  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)
    1588:  [Error: Failed to set config value TIMEOUT_MAX to NaN]
    1589:  ·  ✓  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)
    1590:  [Error: Failed to set config value TIMEOUT_MAX to -3]
    1591:  ·  ✓  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)
    1592:  ·  ✓  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)
    1593:  ·  ✓  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)
    1594:  [Error: Failed to set config value TIMEOUT_DEFAULT to NaN]
    1595:  ·  ✓  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)
    1596:  [Error: Failed to set config value TIMEOUT_DEFAULT to -3]
    1597:  ·  ✓  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)
    1598:  ·  ✓  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)
    1599:  ·  ✓  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)
    1600:  ·  ✓  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)
    1601:  [Error: Failed to set config value RESULTSET_SIZE to NaN]
    1602:  ·  ✓  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)
    1603:  ·  ✓  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)
    1604:  ·  ✓  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)
    1605:  ·  ✓  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)
    1606:  ·  ✓  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)
    1607:  [Error: Failed to set config value QUERY_MEM_CAPACITY to NaN]
    1608:  ·  ✓  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)
    1609:  [Error: Failed to set config value QUERY_MEM_CAPACITY to -3]
    1610:  ·  ✓  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)
    1611:  ·  ✓  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)
    1612:  ·  ✓  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)
    1613:  ·  ✓  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)
    1614:  [Error: Failed to set config value VKEY_MAX_ENTITY_COUNT to NaN]
    1615:  ·  ✓  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)
    1616:  [Error: Failed to set config value VKEY_MAX_ENTITY_COUNT to -3]
    1617:  ·  ✓  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)
    1618:  ·  ✓  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)
    1619:  ·  ✓  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)
    1620:  ·  ✓  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)
    1621:  [Error: Failed to set config value CMD_INFO to aa]
    1622:  ·  ✓  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)
    1623:  [Error: Failed to set config value CMD_INFO to -3]
    1624:  ·  ✓  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)
    1625:  [Error: Failed to set config value CMD_INFO to 00-1]
    1626:  ·  ✓  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)
    1627:  [Error: Failed to set config value CMD_INFO to 10s]
    1628:  ·  ✓  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)
    1629:  ·  ✓  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)
    1630:  ·  ✓  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)
    1631:  [Error: Failed to set config value MAX_INFO_QUERIES to NaN]
    1632:  ·  ✓  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)
    1633:  [Error: Failed to set config value MAX_INFO_QUERIES to -3]
    ...
    
    1640:  ·  ✓  56 [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via UI validation via API: Input value: 10 description: modify defaultTimeOut (730ms)
    1641:  ·  ✓  57 [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify RESULTSET_SIZE via UI validation via API: Input value: 20 description: modify resultSetSize (715ms)
    1642:  ·  ✓  58 [[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 (713ms)
    1643:  ·  ✓  59 [[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 (733ms)
    1644:  ·  ✓  60 [[Admin] Chromium] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify CMD_INFO via UI validation via API: Input value: yes description: modify cmdInfo (715ms)
    1645:  ×  ✘  61 [[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 (716ms)
    1646:  ×  ✘  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 (retry #1) (1.1s)
    1647:  F  ✘  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 #2) (1.1s)
    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:  ·  ✓  64 [[Admin] Chromium] › settingsUsers.spec.ts:19:9 › Settings Tests › @admin Add one new user -> validating user exists in the users list (2.7s)
    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:  ·  ✓  65 [[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:  ·  ✓  66 [[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.0s)
    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:  ·  ✓  67 [[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.4s)
    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:  ·  ✓  68 [[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:  ·  ✓  69 [[Admin] Chromium] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: Test123 reason: short password  (2.9s)
    1689:  ·  ✓  70 [[Admin] Chromium] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: Test1234 reason: without special character  (2.9s)
    1690:  ·  ✓  71 [[Admin] Chromium] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: Testtes@ reason: without digits  (3.0s)
    1691:  ·  ✓  72 [[Admin] Chromium] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: TESTES1@ reason: without lowercase letters  (2.9s)
    1692:  ·  ✓  73 [[Admin] Chromium] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: testte1@ reason: without uppercase letters  (2.9s)
    1693:  ·  ✓  74 [[Admin] Chromium] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user:  reason: without password  (3.0s)
    1694:  ·  ✓  75 [[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:  ·  ✓  76 [[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. (738ms)
    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:  ·  ✓  77 [[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. (36ms)
    1705:  Error: Missing parameters
    1706:  at p (.next/server/app/api/user/route.js:1:2208)
    1707:  ·  ✓  78 [[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:  ·  ✓  79 [[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 (13ms)
    1711:  Error: Missing parameters
    ...
    
    1717:  ·  ✓  84 [[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:  ·  ✓  85 [[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 (20ms)
    1719:  ·  ✓  86 [[Admin] Firefox] › navBar.spec.ts:20:13 › Navbar tests › @admin Verify clicking on FalkorDB logo redirects to specified URL (1.6s)
    1720:  ·  ✓  87 [[Admin] Firefox] › navBar.spec.ts:29:13 › Navbar tests › @admin Verify clicking on Graphs button redirects to specified URL (1.1s)
    1721:  ·  ✓  88 [[Admin] Firefox] › navBar.spec.ts:39:13 › Navbar tests › @admin Verify clicking on Schemas button redirects to specified URL (2.0s)
    1722:  ·  ✓  89 [[Admin] Firefox] › navBar.spec.ts:49:13 › Navbar tests › @admin Verify clicking on help -> Documentation redirects to specified URL (1.1s)
    1723:  ·  ✓  90 [[Admin] Firefox] › navBar.spec.ts:58:13 › Navbar tests › @admin Verify clicking on help -> Support redirects to specified URL (1.2s)
    1724:  ·  ✓  91 [[Admin] Firefox] › navBar.spec.ts:67:13 › Navbar tests › @admin Verify clicking on Settings redirects to specified URL (1.0s)
    1725:  [Error: Failed to set config value MAX_QUEUED_QUERIES to NaN]
    1726:  ·  ✓  92 [[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:  ·  ✓  93 [[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:  ·  ✓  94 [[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:  ·  ✓  95 [[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:  ·  ✓  96 [[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:  ·  ✓  97 [[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:  ·  ✓  98 [[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:  ·  ✓  99 [[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:  ·  ✓  100 [[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:  ·  ✓  101 [[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:  ·  ✓  102 [[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:  ·  ✓  103 [[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:  ·  ✓  104 [[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:  ·  ✓  105 [[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:  ·  ✓  106 [[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:  ·  ✓  107 [[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:  ·  ✓  108 [[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:  ·  ✓  109 [[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:  ·  ✓  110 [[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:  ·  ✓  111 [[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:  ·  ✓  112 [[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:  ·  ✓  113 [[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:  ·  ✓  114 [[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:  ·  ✓  115 [[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:  ·  ✓  116 [[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:  ·  ✓  117 [[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:  ·  ✓  118 [[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:  ·  ✓  119 [[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:  ·  ✓  120 [[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:  ·  ✓  121 [[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:  ·  ✓  122 [[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:  ·  ✓  123 [[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:  ·  ✓  124 [[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:  ·  ✓  125 [[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:  ·  ✓  126 [[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:  ·  ✓  127 [[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:  ·  ✓  134 [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify TIMEOUT_DEFAULT via UI validation via API: Input value: 10 description: modify defaultTimeOut (730ms)
    1787:  ·  ✓  135 [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify RESULTSET_SIZE via UI validation via API: Input value: 20 description: modify resultSetSize (730ms)
    1788:  ·  ✓  136 [[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 (751ms)
    1789:  ·  ✓  137 [[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 (727ms)
    1790:  ·  ✓  138 [[Admin] Firefox] › settingsConfig.spec.ts:111:13 › Settings Tests › @admin Modify CMD_INFO via UI validation via API: Input value: yes description: modify cmdInfo (716ms)
    1791:  ×  ✘  139 [[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 (733ms)
    1792:  ×  ✘  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 (retry #1) (1.1s)
    1793:  F  ✘  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 #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:  ·  ✓  142 [[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:  ·  ✓  143 [[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:  ·  ✓  144 [[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:  ·  ✓  145 [[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.5s)
    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:  ·  ✓  146 [[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:  ·  ✓  147 [[Admin] Firefox] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: Test123 reason: short password  (3.0s)
    1835:  ·  ✓  148 [[Admin] Firefox] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: Test1234 reason: without special character  (3.0s)
    1836:  ·  ✓  149 [[Admin] Firefox] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: Testtes@ reason: without digits  (2.9s)
    1837:  ·  ✓  150 [[Admin] Firefox] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: TESTES1@ reason: without lowercase letters  (3.0s)
    1838:  ·  ✓  151 [[Admin] Firefox] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user: testte1@ reason: without uppercase letters  (3.0s)
    1839:  ·  ✓  152 [[Admin] Firefox] › settingsUsers.spec.ts:109:13 › Settings Tests › @admin Enter password for new user:  reason: without password  (2.9s)
    1840:  ·  ✓  153 [[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:  ·  ✓  154 [[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. (767ms)
    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:  ·  ✓  155 [[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. (38ms)
    1851:  Error: Missing parameters
    1852:  at p (.next/server/app/api/user/route.js:1:2208)
    1853:  ·  ✓  156 [[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:  ·  ✓  157 [[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 (13ms)
    1857:  Error: Missing parameters
    ...
    
    1890:  ·  ✓  189 [[Read-Only] - Firefox] › navBar.spec.ts:20:13 › Navbar tests › @readonly Verify clicking on FalkorDB logo redirects to specified URL (1.7s)
    1891:  ·  ✓  190 [[Read-Only] - Firefox] › navBar.spec.ts:29:13 › Navbar tests › @readonly Verify clicking on Graphs button redirects to specified URL (1.1s)
    1892:  ·  ✓  191 [[Read-Only] - Firefox] › navBar.spec.ts:39:13 › Navbar tests › @readonly Verify clicking on Schemas button redirects to specified URL (2.0s)
    1893:  ·  ✓  192 [[Read-Only] - Firefox] › navBar.spec.ts:49:13 › Navbar tests › @readonly Verify clicking on help -> Documentation redirects to specified URL (1.1s)
    1894:  ·  ✓  193 [[Read-Only] - Firefox] › navBar.spec.ts:58:13 › Navbar tests › @readonly Verify clicking on help -> Support redirects to specified URL (1.2s)
    1895:  ·  ✓  194 [[Read-Only] - Firefox] › navBar.spec.ts:67:13 › Navbar tests › @readonly Verify clicking on Settings redirects to specified URL (1.0s)
    1896:  ·  ✓  195 [[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
    ...
    
    1974:  |                                     ^
    1975:  124 |         });
    1976:  125 |     })
    1977:  126 |
    1978:  at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37
    1979:  Slow test file: [[Admin] Firefox] › settingsUsers.spec.ts (44.5s)
    1980:  Slow test file: [[Admin] Chromium] › settingsUsers.spec.ts (44.0s)
    1981:  Consider splitting slow test files to speed up parallel execution
    1982:  2 failed
    1983:  [[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 
    1984:  [[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 
    1985:  189 passed (5.5m)
    1986:  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 
    1987:  Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m
    ...
    
    1991:  122 |             await apiCall.modifySettingsRole(roles.queryMemCapacity, "0") // update to default values   
    1992:  > 123 |             expect(value === input).toBe(expected)
    1993:  |                                     ^
    1994:  124 |         });
    1995:  125 |     })
    1996:  126 |
    1997:  at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37
    1998:  Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
    1999:  Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m
    ...
    
    2008:  126 |
    2009:  at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37
    2010:  attachment #1: trace (application/zip) ─────────────────────────────────────────────────────────
    2011:  test-results/settingsConfig-Settings-Te-9ddaf-ption-modify-maxInfoQueries--Admin-Chromium-retry1/trace.zip
    2012:  Usage:
    2013:  npx playwright show-trace test-results/settingsConfig-Settings-Te-9ddaf-ption-modify-maxInfoQueries--Admin-Chromium-retry1/trace.zip
    2014:  ────────────────────────────────────────────────────────────────────────────────────────────────
    2015:  Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
    2016:  Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m
    ...
    
    2020:  122 |             await apiCall.modifySettingsRole(roles.queryMemCapacity, "0") // update to default values   
    2021:  > 123 |             expect(value === input).toBe(expected)
    2022:  |                                     ^
    2023:  124 |         });
    2024:  125 |     })
    2025:  126 |
    2026:  at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37
    2027:  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 
    2028:  Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m
    ...
    
    2032:  122 |             await apiCall.modifySettingsRole(roles.queryMemCapacity, "0") // update to default values   
    2033:  > 123 |             expect(value === input).toBe(expected)
    2034:  |                                     ^
    2035:  124 |         });
    2036:  125 |     })
    2037:  126 |
    2038:  at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37
    2039:  Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
    2040:  Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m
    ...
    
    2049:  126 |
    2050:  at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37
    2051:  attachment #1: trace (application/zip) ─────────────────────────────────────────────────────────
    2052:  test-results/settingsConfig-Settings-Te-9ddaf-ption-modify-maxInfoQueries--Admin-Firefox-retry1/trace.zip
    2053:  Usage:
    2054:  npx playwright show-trace test-results/settingsConfig-Settings-Te-9ddaf-ption-modify-maxInfoQueries--Admin-Firefox-retry1/trace.zip
    2055:  ────────────────────────────────────────────────────────────────────────────────────────────────
    2056:  Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
    2057:  Error: �[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoBe�[2m(�[22m�[32mexpected�[39m�[2m) // Object.is equality�[22m
    ...
    
    2063:  |                                     ^
    2064:  124 |         });
    2065:  125 |     })
    2066:  126 |
    2067:  at /home/runner/work/falkordb-browser/falkordb-browser/e2e/tests/settingsConfig.spec.ts:123:37
    2068:  Slow test file: [[Admin] Firefox] › settingsUsers.spec.ts (44.5s)
    2069:  Slow test file: [[Admin] Chromium] › settingsUsers.spec.ts (44.0s)
    2070:  Consider splitting slow test files to speed up parallel execution
    2071:  2 failed
    2072:  [[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 
    2073:  [[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 
    2074:  189 passed (5.5m)
    2075:  ##[error]Process completed with exit code 1.
    ...
    
    2093:  [command]/usr/bin/git config --local --name-only --get-regexp core\.sshCommand
    2094:  [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' || :"
    2095:  [command]/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
    2096:  http.https://github.com/.extraheader
    2097:  [command]/usr/bin/git config --local --unset-all http.https://github.com/.extraheader
    2098:  [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' || :"
    2099:  Print service container logs: ff77ff12e6f44cf8a807399556f1a53e_falkordbfalkordblatest_b4ce6b
    2100:  ##[command]/usr/bin/docker logs --details e8af3e94ae8d52823de54bc0d001fe6f666d84213db244544c95160a3e827447
    2101:  11:C 26 Jan 2025 10:13:29.383 # 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.
    

    @Anchel123 Anchel123 merged commit 5d7b554 into staging Jan 29, 2025
    8 checks passed
    @Anchel123 Anchel123 deleted the restyle-landing-page branch January 29, 2025 10:17
    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.

    Change landing page
    3 participants