Skip to content

feat: log specific message for RequestEntityTooLarge#1185

Merged
giortzisg merged 1 commit intomasterfrom
feat/handle-413
Jan 30, 2026
Merged

feat: log specific message for RequestEntityTooLarge#1185
giortzisg merged 1 commit intomasterfrom
feat/handle-413

Conversation

@giortzisg
Copy link
Contributor

@giortzisg giortzisg commented Jan 29, 2026

Description

Handle the RequestEntityTooLarge (413) response from relay and log a debug message so that users can understand envelope size rejections.

Extracting the httpResponse handling as an extra method for reuse.

Issues

Changelog Entry Instructions

To add a custom changelog entry, uncomment the section above. Supports:

  • Single entry: just write text
  • Multiple entries: use bullet points
  • Nested bullets: indent 4+ spaces

For more details: custom changelog entries

Reminders

@linear
Copy link

linear bot commented Jan 29, 2026

@giortzisg giortzisg self-assigned this Jan 29, 2026
@github-actions
Copy link

github-actions bot commented Jan 29, 2026

Semver Impact of This PR

🟡 Minor (new features)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).


New Features ✨

  • Log specific message for RequestEntityTooLarge by giortzisg in #1185

🤖 This preview updates automatically when you update the PR.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

description = fmt.Sprintf("%s event", event.Type)
}
return fmt.Sprintf("%s [%s]", description, event.EventID)
}
Copy link

Choose a reason for hiding this comment

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

Duplicated event-type-to-description mapping logic

Low Severity

The eventIdentifier function in util.go and EnvelopeIdentifier in internal/util/util.go contain nearly identical logic for mapping event types to human-readable descriptions (error → "error", transaction → "transaction", check-in → "check-in", logs → "%d log events", metrics → "%d metric events"). Both return the same format "%s [%s]". If a new event type is added or the description format changes, both functions must be updated, risking inconsistency.

Additional Locations (1)

Fix in Cursor Fix in Web

@giortzisg giortzisg changed the title feat: log debug message for HTTP 413 response feat: log specific message for RequestEntityTooLarge Jan 30, 2026
@giortzisg giortzisg merged commit 4e2dce9 into master Jan 30, 2026
19 checks passed
@giortzisg giortzisg deleted the feat/handle-413 branch January 30, 2026 10:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

SDK Handling HTTP 413 [Go]

2 participants