Skip to content

refactor: use async context manager and improve error handling in reverse_proxy #2339

refactor: use async context manager and improve error handling in reverse_proxy

refactor: use async context manager and improve error handling in reverse_proxy #2339

Triggered via pull request July 12, 2025 11:27
@fazialnjdfazialnjd
opened #1183
Status Failure
Total duration 5s
Artifacts

conventional-prs.yml

on: pull_request_target
title-format
3s
title-format
Fit to window
Zoom out
Zoom in

Annotations

1 error
title-format
No release type found in pull request title "Refactor reverse_proxy to use async context manager and improve error…". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/ Available types: - feat: A new feature - fix: A bug fix - docs: Documentation only changes - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) - refactor: A code change that neither fixes a bug nor adds a feature - perf: A code change that improves performance - test: Adding missing tests or correcting existing tests - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm) - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs) - chore: Other changes that don't modify src or test files - revert: Reverts a previous commit