Skip to content

chore: add label - not allowed on host acl#417

Merged
manoranjith merged 2 commits intomainfrom
feat/add-label-not-allowed-on-host-acl
Mar 6, 2026
Merged

chore: add label - not allowed on host acl#417
manoranjith merged 2 commits intomainfrom
feat/add-label-not-allowed-on-host-acl

Conversation

@manoranjith
Copy link
Contributor

No description provided.

@cla-bot cla-bot bot added the cla-signed label Mar 6, 2026
@manoranjith manoranjith force-pushed the feat/add-label-not-allowed-on-host-acl branch from 1dea58b to bd8cf55 Compare March 6, 2026 12:31
@manoranjith manoranjith requested a review from 0xalexbel March 6, 2026 12:32
- The relayer now performs ACL checks directly on the
  host chain and returns not_allowed_on_host_acl on
  HTTP 400 when a check fails

- Previously: this label was unrecognized, causing a
  generic RelayerV2ResponseInvalidBodyError

- Now: label is recognized as a 400 no-details error,
  surfaced via RelayerV2ResponseApiError with the
  actual label and message
@manoranjith manoranjith force-pushed the feat/add-label-not-allowed-on-host-acl branch from bd8cf55 to 5318789 Compare March 6, 2026 15:07
Copy link
Collaborator

@0xalexbel 0xalexbel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@manoranjith manoranjith merged commit f5f4b23 into main Mar 6, 2026
5 checks passed
@manoranjith manoranjith deleted the feat/add-label-not-allowed-on-host-acl branch March 6, 2026 15:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants