fix: correct typo 'recieved' to 'received' in log messages

[thecaptain789]

Fixes 5 instances of the typo 'recieved' → 'received' across 4 server files.

[gemini-code-assist]

Summary of Changes

Hello @thecaptain789, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the quality and professionalism of the application's logging output by fixing a common spelling error. It systematically replaces all occurrences of 'recieved' with the correct 'received' in various log messages, ensuring clarity and correctness in system diagnostics.

Highlights

• Typo Correction: Corrected the misspelling of 'recieved' to 'received' in five instances across four server files, improving log message accuracy.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• lightllm/server/api_http.py
  • Corrected 'recieved' to 'received' in a logger info message related to regist_json.
  • Corrected 'recieved' to 'received' in a logger info message related to upkv_status.
• lightllm/server/config_server/api_http.py
  • Corrected 'recieved' to 'received' in a logger info message for registered_pd_master_obj.
• lightllm/server/httpserver/manager.py
  • Corrected 'recieved' to 'received' in a logger info message for incoming request headers.
• lightllm/server/httpserver_for_pd_master/manager.py
  • Corrected 'recieved' to 'received' in a logger info message for incoming request headers.

Activity

• The pull request was created by thecaptain789.
• No human activity (comments, reviews) has been recorded yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request addresses a consistent typo ('recieved' instead of 'received') in log messages across multiple server files. The changes are correct and improve the overall quality and readability of the logs. The fix is applied consistently in all identified locations. The changes are purely cosmetic and have no functional impact. This is a good, clean fix.