-
Notifications
You must be signed in to change notification settings - Fork 28.5k
Increased the limit where we start chopping off the end of blurs #168109
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
base: master
Are you sure you want to change the base?
Conversation
It looks like this pull request may not have tests. Please make sure to add tests or get an explicit test exemption before merging. If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix? Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.If you believe this PR qualifies for a test exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group. |
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.
LGTM, with comment nit...
// Chop off the last samples if the radius >= 3 where they account for < 1.56% | ||
// of the result. | ||
// Chop off the last samples if the radius >= 16 where they account for | ||
// < 1.56% of the result. |
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.
Is it still 1.56% if you increase the radius size? I would think that the contribution %age would go way down at that radius.
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 didn't measure it, that's from the article on the lerp hack. I think it's probably still a good rule of thumb, it obviously isn't going to be exact for every radius.
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 updated the comment to reflect it isn't exactly 1.56%
8196ef5
to
dcad843
Compare
autosubmit label was removed for flutter/flutter/168109, because - The status or check suite Mac mac_unopt has failed. Please fix the issues identified (or deflake) before re-applying this label. |
8c807e0
to
a327427
Compare
I'm having a hard time getting this through CI. I'm getting failures in things like |
a327427
to
0df4796
Compare
0df4796
to
6728ad9
Compare
This is failing because of changes to golden images in the bespoke platform view golden tests. |
issue: #165422
Here is the before/after screenshots at sigma = 30
beforeafter.mp4
Pre-launch Checklist
///
).If you need help, consider asking for advice on the #hackers-new channel on Discord.