GitLab

Co-authored-by: PengGao <peng.gaoc@gmail.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Yang Yong (雍洋) <yongyang1030@163.com>

update deploy

---------
Co-authored-by: liuliang1 <liuliang1@sensetime.com>
Co-authored-by: qinxinyi <qinxinyi@sensetime.com>
Co-authored-by: Yang Yong(雍洋) <yongyang1030@163.com>

Remove unused ProcessManager and TensorTransporter classes from
utils.py; eliminate request_queue initialization in
TorchrunInferenceWorker.

Co-authored-by: Yang Yong(雍洋) <yongyang1030@163.com>

deploy update

---------
Co-authored-by: liuliang1 <liuliang1@sensetime.com>
Co-authored-by: qinxinyi <qinxinyi@sensetime.com>

…nt task after broadcasting. Handle exceptions when clearing task event.

## Contributing Guidelines

We have prepared a `pre-commit` hook to enforce consistent code
formatting across the project. If your code complies with the standards,
you should not see any errors, you can clean up your code following the
steps below:

1. Install the required dependencies:

```shell
    pip install ruff pre-commit
```

2. Then, run the following command before commit:

```shell
    pre-commit run --all-files
```

3. Finally, please double-check your code to ensure it complies with the
following additional specifications as much as possible:
- Avoid hard-coding local paths: Make sure your submissions do not
include hard-coded local paths, as these paths are specific to
individual development environments and can cause compatibility issues.
Use relative paths or configuration files instead.
- Clear error handling: Implement clear error-handling mechanisms in
your code so that error messages can accurately indicate the location of
the problem, possible causes, and suggested solutions, facilitating
quick debugging.
- Detailed comments and documentation: Add comments to complex code
sections and provide comprehensive documentation to explain the
functionality of the code, input-output requirements, and potential
error scenarios.

Thank you for your contributions!

## Contributing Guidelines

We have prepared a `pre-commit` hook to enforce consistent code
formatting across the project. If your code complies with the standards,
you should not see any errors, you can clean up your code following the
steps below:

1. Install the required dependencies:

```shell
    pip install ruff pre-commit
```

2. Then, run the following command before commit:

```shell
    pre-commit run --all-files
```

3. Finally, please double-check your code to ensure it complies with the
following additional specifications as much as possible:
- Avoid hard-coding local paths: Make sure your submissions do not
include hard-coded local paths, as these paths are specific to
individual development environments and can cause compatibility issues.
Use relative paths or configuration files instead.
- Clear error handling: Implement clear error-handling mechanisms in
your code so that error messages can accurately indicate the location of
the problem, possible causes, and suggested solutions, facilitating
quick debugging.
- Detailed comments and documentation: Add comments to complex code
sections and provide comprehensive documentation to explain the
functionality of the code, input-output requirements, and potential
error scenarios.

Thank you for your contributions!

---------
Co-authored-by: gushiqiao <975033167@qq.com>

Enhance isotropic crop and resize functionality to support both single and multiple frame inputs. Introduce 'fixed_min_side' resize mode for improved aspect ratio handling based on specified resolutions. (#293)