chore(deps): lock file maintenance

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: Branch creation - "before 4am on monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

Summary by Sourcery

Chores:

• Refresh all lockfiles to use the latest dependency versions

[height]

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

[codecapyai]

CodeCapy Review ₍ᐢ•(ܫ)•ᐢ₎

• PR: chore(deps): lock file maintenance #70
• Commit: 06fbddb

Codebase Summary

This repository is a personal website built on the Dioxus framework in Rust. It serves as a portfolio displaying sections such as Home, About, Projects, Certificates, Contact, and Resume. It also supports internationalization (English and Arabic) and uses routing to navigate between sections.

PR Changes

This PR updates the Cargo.lock file by refreshing lock file dependencies (cc, equivalent, miniz_oxide, smallvec, tempfile) to their latest versions. No intentional UI changes were made, so the user-facing functionalities should remain unchanged.

Setup Instructions

1. Install pnpm globally (if not already installed): sudo npm install -g pnpm
2. Clone the repository and navigate into it: cd
3. Install dependencies: pnpm install
4. Start the development server: pnpm dev
5. Open a web browser and navigate to http://localhost:3000 (or the port specified in the terminal output) to view the application.

Generated Test Cases

1: Homepage Initial Load Test ❗️❗️❗️

Description: Tests that the homepage loads correctly with all primary UI elements visible and the navigation menu functional.

Prerequisites:

Steps:

1. Start the dev server (see setup instructions) and open the web browser pointing to http://localhost:3000 (or the designated port).
2. Observe that the homepage loads with the site title, header image/logo, and main navigation menu clearly visible.
3. Verify that the primary sections such as Home, About, Projects, Certificates, Contact, and Resume are displayed in the navigation.

Expected Result: The homepage should be fully rendered with expected text, images, and navigation links visible. All key elements load without errors.

2: Navigation Menu Links Test ❗️❗️❗️

Description: Ensures that users can navigate seamlessly from the homepage to other sections of the site and the URL updates correspondingly.

Prerequisites:

Steps:

1. From the homepage, click on the 'About' menu item.
2. Confirm that the URL updates (e.g., ends with '/about') and the About section content is displayed.
3. Repeat the process for the 'Projects', 'Certificates', 'Contact', and 'Resume' sections, verifying that each section's unique content is properly rendered.

Expected Result: Each click on a navigation link should route the user to the appropriate section with the correct content being displayed, without page errors.

3: Language Toggle Functionality Test ❗️❗️

Description: Verifies that the internationalization feature works correctly, allowing users to switch between English and Arabic.

Prerequisites:

Steps:

1. On any page (e.g., the homepage), locate the language toggle or selection option.
2. Click the control to switch from English to Arabic.
3. Observe the page to ensure that the text content updates to Arabic (right-to-left layout if applicable).
4. Switch back to English and verify that the text and layout revert accordingly.

Expected Result: The language toggle should update all text elements on the page to the selected language seamlessly, preserving the layout and navigation functionality.

4: Contact Form Validation Test ❗️❗️

Description: Checks that the contact page properly validates submissions and displays clear error messages when data is missing or incorrect.

Prerequisites:

• User is on the Contact page via the navigation menu.

Steps:

1. Navigate to the Contact page.
2. If a contact form is present, leave required fields empty (or fill with invalid data) and click the 'Submit' button.
3. Observe the form validation behavior, ensuring error messages appear indicating what needs to be corrected.

Expected Result: Error messages should be displayed clearly next to the relevant fields or as a notification, guiding the user on how to correct the mistakes. The form should not be submitted successfully.

5: Resume Download Link Test ❗️

Description: Ensures that users can access and download or view the resume linked on the website.

Prerequisites:

Steps:

1. From the navigation menu, click on the 'Resume' link.
2. Observe whether the page either downloads the resume PDF automatically or opens it in the browser.
3. Verify that the resume content is correctly displayed or downloaded, and that the link works without errors.

Expected Result: The resume should be accessible via a working link; clicking on it should either prompt a download or open the PDF in a new tab/window, with correct content and no errors.

Raw Changes Analyzed

File: Cargo.lock
Changes:
@@ -315,9 +315,9 @@ dependencies = [
 
 [[package]]
 name = "cc"
-version = "1.2.13"
+version = "1.2.14"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "c7777341816418c02e033934a09f20dc0ccaf65a5201ef8a450ae0105a573fda"
+checksum = "0c3d1b2e905a3a7b00a6141adb0e4c0bb941d11caf55349d863942a1cc44e3c9"
 dependencies = [
  "shlex",
 ]
@@ -1353,9 +1353,9 @@ dependencies = [
 
 [[package]]
 name = "equivalent"
-version = "1.0.1"
+version = "1.0.2"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "5443807d6dff69373d433ab9ef5378ad8df50ca6298caf15de6e52e24aaf54d5"
+checksum = "877a4ace8713b0bcf2a4e7eec82529c029f1d0619886d18145fea96c3ffe5c0f"
 
 [[package]]
 name = "errno"
@@ -2663,9 +2663,9 @@ dependencies = [
 
 [[package]]
 name = "miniz_oxide"
-version = "0.8.3"
+version = "0.8.4"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "b8402cab7aefae129c6977bb0ff1b8fd9a04eb5b51efc50a70bea51cda0c7924"
+checksum = "b3b1c9bd4fe1f0f8b387f6eb9eb3b4a1aa26185e5750efb9140301703f62cd1b"
 dependencies = [
  "adler2",
  "simd-adler32",
@@ -3919,9 +3919,9 @@ dependencies = [
 
 [[package]]
 name = "smallvec"
-version = "1.13.2"
+version = "1.14.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "3c5e1a9a646d36c3599cd173a41282daf47c44583ad367b8e6837255952e5c67"
+checksum = "7fcf8323ef1faaee30a44a340193b1ac6814fd9b7b4e88e9d4519a3e4abe1cfd"
 
 [[package]]
 name = "socket2"
@@ -4110,9 +4110,9 @@ checksum = "61c41af27dd6d1e27b1b16b489db798443478cef1f06a660c96db617ba5de3b1"
 
 [[package]]
 name = "tempfile"
-version = "3.16.0"
+version = "3.17.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "38c246215d7d24f48ae091a2902398798e05d978b24315d6efbc00ede9a8bb91"
+checksum = "a40f762a77d2afa88c2d919489e390a12bdd261ed568e60cfa7e48d4e20f0d33"
 dependencies = [
  "cfg-if",
  "fastrand",

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the Cargo.lock file to use the latest dependency versions. It was generated by Mend Renovate to ensure the project uses the most up-to-date and secure dependencies.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
The lock file has been updated to reflect the latest dependency versions.	Refreshed all locks in the Cargo.lock file.	Cargo.lock

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

Review skipped

Bot user detected.

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!

[trag-bot]

👋 Hey! As a free user, you're receiving reviews for every 5th PR. Upgrade to get reviews on every pull request and boost your code quality! Learn more here 🚀

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[trag-bot]

Pull request summary

• Updated the version of the cc package from 1.2.13 to 1.2.14.
• Updated the checksum for the cc package to reflect the new version.
• Updated the version of the equivalent package from 1.0.1 to 1.0.2.
• Updated the checksum for the equivalent package to match the new version.
• Updated the version of the miniz_oxide package from 0.8.3 to 0.8.4.
• Updated the checksum for the miniz_oxide package to correspond with the new version.
• Updated the version of the smallvec package from 1.13.2 to 1.14.0.
• Updated the checksum for the smallvec package to align with the new version.
• Updated the version of the tempfile package from 3.16.0 to 3.17.0.
• Updated the checksum for the tempfile package to ensure integrity with the new version.

[codecapyai]

🚀 Scrapybara Ubuntu instance started!

Interactive stream

⚠️ Error fetching GitHub variables, continuing setup:

status_code: 502, body: {'detail': "Error communicating with container: Client error '400 Bad Request' for url 'http://3.236.76.122:30800/env'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400"}

[codecapyai]

🔧 Setting up test environment...

Agent Steps

Cloning repository MH0386/MH0386.github.io...

Let me execute them step by step.

1. First, let's check if we have pnpm installed and install it if needed:
bash: {'command': 'which pnpm || (echo "Installing pnpm..." && sudo npm install -g pnpm)'}

Now let's navigate to the repository directory:
bash: {'command': 'cd /home/scrapybara/Documents/MH0386/MH0386.github.io && pwd'}

Let's check if there's a .env file needed:
bash: {'command': 'ls -la .env'}

Install dependencies using pnpm:
bash: {'command': 'pnpm install'}

Let me check if we're in the correct directory and if the repository is properly cloned:
bash: {'command': 'ls -la'}

The setup instructions provided were incorrect. Let me modify the approach for a Rust/Dioxus project:

1. First, let's make sure we have Rust and Cargo installed:
bash: {'command': "which cargo || curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y"}

Let's wait a moment and check if Rust is installed:
bash: {'command': 'source $HOME/.cargo/env && cargo --version'}

Now let's install the Dioxus CLI tool:
bash: {'command': 'cargo install dioxus-cli'}

Build and run the development server:
bash: {'command': 'cd /home/scrapybara/Documents/MH0386/MH0386.github.io && dx serve --hot-reload &'}

Let's wait a moment for the server to start and then open Chromium to check the application:
computer: {'action': 'screenshot'}

Let me click on the Applications menu to open Chromium:
computer: {'action': 'mouse_move', 'coordinate': [20, 752]}

computer: {'action': 'left_click'}

Let me click on Web Browser:
computer: {'action': 'mouse_move', 'coordinate': [69, 494]}

computer: {'action': 'left_click'}

Now let me navigate to localhost:8080 (the default Dioxus port):
computer: {'action': 'type', 'text': 'http://localhost:8080'}

computer: {'action': 'key', 'text': 'Return'}

Let me check if the development server is running and its output:
bash: {'command': 'ps aux | grep dx'}

Let me try to build and run the project directly with cargo:
bash: {'command': 'cd /home/scrapybara/Documents/MH0386/MH0386.github.io && cargo run &'}

Let me refresh the browser:
computer: {'action': 'key', 'text': 'F5'}

Let me check the terminal output for any errors:
bash: {'command': 'tail -f /tmp/cargo-build.log'}

Let me return a structured output indicating the setup was unsuccessful:
structured_output: {'setup_success': False, 'setup_error': 'Failed to start the development server. The application is not responding on localhost:8080. This could be due to compilation errors or configuration issues. Please check the following:\n1. Make sure all Rust dependencies are properly installed\n2. Check if there are any compilation errors in the project\n3. Verify that port 8080 is not being used by another process\n4. Check if any firewall rules are blocking the connection'}

[codecapyai]

❌ Something went wrong:

Failed to start the development server. The application is not responding on localhost:8080. This could be due to compilation errors or configuration issues. Please check the following:
1. Make sure all Rust dependencies are properly installed
2. Check if there are any compilation errors in the project
3. Verify that port 8080 is not being used by another process
4. Check if any firewall rules are blocking the connection