Online weight update [WIP]

[zhaochenyang20]

Motivation

Modifications

Checklist

• Format your code according to the Contributor Guide.
• Add unit tests as outlined in the Contributor Guide.
• Update documentation as needed, including docstrings or example tutorials.

[zhyncs]

Delete this, it's useless.

[zhyncs]

Delete this, it's useless.

[zhyncs]

Do not use Chinese annotations.

[merrymercy]

You can rebase and add your 2-gpu test here

sglang/.github/workflows/pr-test.yml

Lines 106 to 109 in fa27161

	unit-test-backend-2-gpu-part-1:
	if: github.repository == 'sgl-project/sglang' || github.event_name == 'pull_request'
	runs-on: 2-gpu-runner
	steps:

To fix the problem, we need to ensure that the exception details are not exposed to the user. Instead, we should log the exception details on the server and return a generic error message to the user. This can be achieved by modifying the exception handling block to log the exception and return a generic error message.

• Modify the exception handling block in the get_memory_pool_size function to log the exception and return a generic error message.
• Add the necessary import for logging if it is not already present.

To fix the problem, we need to ensure that detailed exception messages are not exposed to the user. Instead, we should log the detailed error information on the server and return a generic error message to the user. This can be achieved by modifying the exception handling code to log the exception and return a generic error message.

1. Import the traceback module to log the stack trace.
2. Modify the exception handling blocks to log the stack trace and return a generic error message.

To fix the problem, we need to ensure that detailed exception messages are not exposed to the user. Instead, we should log the detailed error message on the server and return a generic error message to the user. This can be achieved by modifying the exception handling code to log the exception and return a generic error message.

1. Import the logging module if not already imported.
2. Modify the exception handling code to log the exception message using the logging module.
3. Return a generic error message to the user.

To fix the problem, we need to ensure that detailed error messages and stack traces are not exposed to the user. Instead, we should log the detailed error information on the server and return a generic error message to the user. This can be achieved by modifying the exception handling code to log the exception and return a generic error message.

• Modify the exception handling code in the generate_request, init_parameter_update_group_request, get_weights_by_parameter_name_request, update_parameter_from_distributed_request, and encode_request functions.
• Use the logging module to log the detailed error message on the server.
• Return a generic error message to the user.

To fix the problem, we need to ensure that detailed exception messages are not exposed to the user. Instead, we should log the detailed error message on the server and return a generic error message to the user. This can be achieved by modifying the exception handling code to log the exception and return a generic error message.

1. Import the logging module if it is not already imported.
2. Replace the return statements that expose the exception message with code that logs the exception and returns a generic error message.