Skip to content

flutter/packages Palatte can not work #36456

Closed

Description

@lucasjinreal
void imageListener(ImageInfo info, bool synchronousCall) {
      loadFailureTimeout?.cancel();
      stream.removeListener(imageListener);
      imageCompleter.complete(info.image);
    }

    if (timeout != Duration.zero) {
      loadFailureTimeout = Timer(timeout, () {
        stream.removeListener(imageListener);
        imageCompleter.completeError(
          TimeoutException(
              'Timeout occurred trying to load from $imageProvider'),
        );
      });
    }
    stream.addListener(imageListener);

Those code can not work with newest flutter, how to change it?

Activity

  1. stuartmorgan-g commented on Jul 18, 2019

    @stuartmorgan-g
    Contributor

    @tvolkert This is from https://groups.google.com/forum/#!topic/flutter-announce/NWTszrEq9U0

    Is there a standard process for updating first-party packages for breaking changes?

  2. lucasjinreal commented on Jul 19, 2019

    @lucasjinreal
    Author

    @stuartmorgan I think the changes of new api has been made far way, the best way is to update old packages.

    Those code is from flutter/packages palatte_genereator, Does it maintained by flutter team? Why not update it's down usage anyway?

    That is a good package help us get domain color from a single image even a networkimage widget.

    Or, if any instructions how to edit those error warning code is also ok, I can change it myself...

  3. stuartmorgan-g commented on Jul 19, 2019

    @stuartmorgan-g
    Contributor

    Why not update it

    That's exactly what my comment was suggesting.

  4. tvolkert commented on Jul 19, 2019

    @tvolkert
    Contributor

    Is there a standard process for updating first-party packages for breaking changes?

    Right now there's no standard way. Ian has just set up in the past week a way to run non-framework tests as part of framework commits, so we should wire up packages and plugin tests into that system so we get alerted to such breakages.

    In the meantime, this should just be updated by a willing soul, and since I don't like volunteering other people, I guess that willing soul is me 🙂

  5. tvolkert commented on Jul 19, 2019

    @tvolkert
    Contributor
  6. lucasjinreal commented on Jul 19, 2019

    @lucasjinreal
    Author

    @tvolkert Seems willing soul has been resolved this issue, thanks so much! I will update that package!

  7. tvolkert commented on Jul 19, 2019

    @tvolkert
    Contributor

    I haven't merged the fix yet or published a new version, so re-opening.

  8. lucasjinreal commented on Jul 19, 2019

    @lucasjinreal
    Author

    @tvolkert Thanks tvolkert! Hope you can release it soon!

  9. zoeyfan commented on Jan 3, 2020

    @zoeyfan

    Looking at the status of flutter/packages#24, may I assume this has been fixed now, therefore can be closed?

  10. github-actions commented on Aug 24, 2021

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  11. locked as resolved and limited conversation to collaborators on Aug 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    p: palette_generatorPalette generator packagepackageflutter/packages repository. See also p: labels.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions