Zwelf
Zwelf
Under further testing, it also gets stuck for me on valid invites
I do get further today. So maybe it is stricter rate limiting on invite link resolving api? I'm still stuck on exporting channel history with many invites (they are all...
I bisected it to be a regression from this commit: 191294b4fe3c2f1ef980472ed738752a0a63b815. Related issue: #649
I see two possible solutions: 1. cache data for invites (because this is triggered here probably only because there are roughly 3750 consecutive invites to the same channel) 2. Add...
So it seems real steps to reproduce include exporting the full invite range ``` dotnet run -- export -c 293493549758939136 --after 2017-07-22T00:00 --before 2017-07-23T00:00 -t ${TOKEN} ```
The problem is that after getting rate limited once, I can't resolve any discord.gg links anymore. As soon as I get to any message containing such a link the export...
I solved it for me by removing the code resolving the discord invite link for exporting the days with the spam. Unfortunately that is not a general solution. Diff to...
Yes, this would need change in teehistorian. And I'd suggest to create a new function to not use `CScore::SaveTeam` for different purposes and that we can have better messaging to...
Could be regression of #8231. I changed integration tests there.
https://github.com/ddnet/ddnet/actions/runs/8859511077/job/24329352870?pr=3994 > Error: near line 1: in prepare, database is locked (5) > [-] Error: no ranks found in database