Skip to content

Conversation

@akiraveliara
Copy link
Member

it appears that we're running into some length limit, potentially system-specific, here. cc @Aaron2550 does this fix the issue

@akiraveliara akiraveliara added this to the v5.0 milestone Jan 10, 2024
@OoLunar
Copy link
Contributor

OoLunar commented Jan 10, 2024

Stacktraces found here: https://discord.com/channels/379378609942560770/379386901725052928/1194750834005790893

message.txt
message 2.txt
message 3.txt
message 4.txt

Additionally we discussed possibly using CultureInfo.InvariantCulture. Besides that, LGTM.

Copy link
Member

@Plerx2493 Plerx2493 left a comment

Choose a reason for hiding this comment

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

LGTM

@akiraveliara akiraveliara merged commit daa34d3 into master Jan 11, 2024
@akiraveliara akiraveliara deleted the fix-ratelimit-header branch January 11, 2024 13:47
OoLunar pushed a commit that referenced this pull request Oct 3, 2024
…f relative resets (#1718)

* address TimeSpan Too Long errors thrown from using absolute instead of relative resets

* invariant culture too
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.

3 participants