-
Notifications
You must be signed in to change notification settings - Fork 104
feat(processor): Playstation endpoint #4555
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
feat(processor): Playstation endpoint #4555
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add integration test, make sure we assert the current behaviour.
// TODO: Check if this even has an effect since we will always have a multipart message. | ||
// Looking at the minidump endpoint seems like multipart bypasses this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might have misunderstood what this is trying to achieve since it seems to only set the limit for an individual file in the multipart form. That is if I set it to -1 the size of a file (in the tests I have a test for that) it fails but sending the file twice with different names in the multipart form does not trigger this if the limit is size of the individual file +1.
Co-authored-by: David Herberth <[email protected]>
Co-authored-by: David Herberth <[email protected]>
Co-authored-by: David Herberth <[email protected]>
Some initial logic for the new playstation endpoint.
Fixes: #95