Fix malformed HTML causing uncaught error#13042
Merged
Conversation
Fix OEmbed preview API leaking existence of private statuses (see #12930)
Gargron
added
bug
Contributor
|
Do you have an example of what's causing the ArgumentError? |
Member
Author
|
@ThibG I do not have a specific example, some status(es) seem to be going around that cause it but I cannot see which ones, however in theory it's just Oh sorry, and the specific |
ClearlyClaire
approved these changes
Feb 4, 2020
Contributor
ClearlyClaire
left a comment
ClearlyClaire
left a comment
There was a problem hiding this comment.
Hm, I agree with the OEmbed part… the reformat part, I'm not too sure about… it seems weird to just have an empty status or bio, even if the original content is probably not good any way… but otherwise, LGTM
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix OEmbed preview API leaking existence of private statuses (see #12930)