Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Making a dispute results in 500 internal server error #467

Open
LeonStemerdink opened this issue Jan 24, 2024 · 2 comments
Open

Making a dispute results in 500 internal server error #467

LeonStemerdink opened this issue Jan 24, 2024 · 2 comments

Comments

@LeonStemerdink
Copy link

Hi Trunk team!

I attempted to make a dispute/claim for a Pod by posting to "https://trunk.cocoapods.org/disputes".

As a result I expected to be redirected to "https://trunk.cocoapods.org/disputes/thanks".

What happened instead is that I received an 500 "Internal Server Error" response.

Note that the initial form, that posts to "https://trunk.cocoapods.org/disputes/new" works without issue. It is the actual sending of the dispute that results in this error.
From looking at "disputes_controller.rb" I suspect there may be an issue with the Slack integration. However this is hard to say for sure without the actual server logs.

Could this issue please looked into? And could you perhaps clarify whether disputes are still received successfully, even though there is an error, or whether I need to make another dispute when the issue is resolved?

Thank you for your help!

@LeonStemerdink
Copy link
Author

Hello Trunk team,

This issue still exists, preventing us from claiming our pod. Could you please provide some insights on this issue, and the planning for resolving it?

Thank you in advance!

@LeonStemerdink
Copy link
Author

Hello team,

I've noticed this blog post.
Could you please indicate what this means for the dispute flow? Should we expect that the issues reported earlier will never be resolved?

Thank you for a reply!

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

No branches or pull requests

1 participant