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

Upscale Thumbnail is not work #1016

Closed
wants to merge 1 commit into from

Conversation

peter-gribanov
Copy link
Contributor

@peter-gribanov peter-gribanov commented Nov 28, 2017

Q A
Branch? 1.0
Bug fix? no
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets -
License MIT
Doc PR -

allow_upscale is not work in Thumbnail filter #560

I propose to solve this problem by creating a separate filter #1015, because this filter is already very complex.

@lsmith77
Copy link
Contributor

@antoligy / @robfrawley how do we want to deal with this .. 1.0 or 2.0 ?

@robfrawley
Copy link
Collaborator

Since it is a bug, we should likely fix it in both branches, IMHO.

@robfrawley robfrawley added the Level: Bug 🐞 This item involves a legitimate regression (bug) to existing functionality. label Jan 21, 2018
@lsmith77
Copy link
Contributor

right, I had a bit of a concern that this might be the sort of bug fix, that is a BC break in that people might be relying on the buggy behavior.

@robfrawley
Copy link
Collaborator

Ah, I see where you're coming from; I agree it could be considered a BC break and should therefore not be applied to 1.x.

With that said though, after reacquainting myself with #560 I actually don't believe we should do anything to fix the Thumbnail filter within this project; the issue actually lies in the imagine-library implementation. If we did want to resolve this, we should offer a PR to that library.

@lsmith77 Do you think we should work around imagine-library's internal handling ourselves instead? It seems kind of "hacky" to intentionally alter the behavior of our transformation library, but I guess it may be a solution if this is deemed an important "fix".

I think #1015 on the 2.x branch is the way to move forward.

@robfrawley robfrawley added State: Reviewing This item is being reviewed to determine if it should be accepted. Type: Source Code This item pertains to the source code of this project. Attn: Minor This issue or PR is a minor problem or minor change. labels Jan 21, 2018
@lsmith77
Copy link
Contributor

would be better to try at least to work with upstream to get the bug fixed

@robfrawley
Copy link
Collaborator

robfrawley commented Feb 15, 2018

@peter-gribanov Are you able to work on this with upstream avalanche123/Imagine?

@dbu
Copy link
Member

dbu commented Aug 9, 2019

has the upstream bug been fixed?

@peter-gribanov
Copy link
Contributor Author

I think we can close this PR in favor #1015

@dbu
Copy link
Member

dbu commented Aug 9, 2019

cool!

@dbu dbu closed this Aug 9, 2019
@peter-gribanov peter-gribanov deleted the remove_allow_upscale branch August 9, 2019 09:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Attn: Minor This issue or PR is a minor problem or minor change. Level: Bug 🐞 This item involves a legitimate regression (bug) to existing functionality. State: Reviewing This item is being reviewed to determine if it should be accepted. Type: Source Code This item pertains to the source code of this project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants