Skip to content

"You are using these overridden dependencies" when starting flutter #5921

Closed
Closed
"You are using these overridden dependencies" when starting flutter#5921
Assignees
pq
Labels
c: regressionIt was better in the past than it is nowtoolAffects the "flutter" command-line tool. See also t: labels.
Milestone
2: Make Early Adopters happy

Description

@Hixie
Hixie
opened on Sep 17, 2016

When you start flutter the first time you now get this warning:

Warning: You are using these overridden dependencies:
^[[35m! ^[[39m^[[1manalyzer^[[0m 0.29.0-alpha.0 from path ../../bin/cache/dart-sdk/lib/analyzer

This is a very confusing message for first-time users (or really anyone except those of us who are privy to the inner workings of the flutter tool) and so we shouldn't show that.

Activity

  1. Hixie
    added
    affects: dev experience
    c: regressionIt was better in the past than it is now
    toolAffects the "flutter" command-line tool. See also t: labels.
    on Sep 17, 2016
  2. Hixie
    added this to the milestone on Sep 17, 2016

  3. abarth commented on Sep 17, 2016

    @abarth
    abarth
    on Sep 17, 2016
    Contributor

    @pq @danrubel

  4. sethladd commented on Sep 17, 2016

    @sethladd
    sethladd
    on Sep 17, 2016
    Contributor

    Good catch.
    On Fri, Sep 16, 2016 at 23:12 Adam Barth [email protected] wrote:

    @pq https://github.com/pq @danrubel https://github.com/danrubel

    —
    You are receiving this because you are subscribed to this thread.
    Reply to this email directly, view it on GitHub
    #5921 (comment),
    or mute the thread
    https://github.com/notifications/unsubscribe-auth/AAAVZ7VdTxOzaUlZo__7kgR5XZAVobeQks5qq4TegaJpZM4J_hO0
    .

  5. pq commented on Sep 17, 2016

    @pq
    pq
    on Sep 17, 2016
    Contributor

    Thanks. Yeah, I noted that in the PR the other day (#5900) and have been playing with a clean way to suppress this. Thanks for opening the issue and keeping me honest! (And sorry for not being more clear about this downside.)

  6. pq
    self-assigned this
    on Sep 19, 2016
  7. pq
    added a commit that references this issue on Sep 19, 2016

    Suppress pub warning of expected analyzer override (flutter#5921).

    6e7eb5f

  8. abarth commented on Sep 21, 2016

    @abarth
    abarth
    on Sep 21, 2016
    Contributor

    This appears to be still happening. Should we revert the change that added this message until we find a solution?

  9. pq commented on Sep 21, 2016

    @pq
    pq
    on Sep 21, 2016
    Contributor

    Yeah. We have a choice to make. The way I see it, we can

    1. back the change out and go back to the last published analyzer and with it back to the 1.20.0-dev.1.0 SDK (or deal with skew),
    2. publish a new (test version constraint friendly) analyzer and update pubspecs accordingly,
    3. embrace some level of pub error suppression, or
    4. go back to calling out to a separate process for flutter analyze and live with analysis getting 2x+ slower

    cc @bwilkerson on the feasibility of 2.
    cc @danrubel for an update on longer term plans to decouple from the analyzer package.

  10. abarth commented on Sep 21, 2016

    @abarth
    abarth
    on Sep 21, 2016
    Contributor

    It sounds like we should do (1) while we sort out the long term plan.

  11. bwilkerson commented on Sep 21, 2016

    @bwilkerson
    bwilkerson
    on Sep 21, 2016
    Contributor

    I don't have a problem with publishing a new version of analyzer as long as it doesn't violate semver in any practical sense. But I do think we'd need to do some work to ensure that.

  12. pq commented on Sep 22, 2016

    @pq
    pq
    on Sep 22, 2016
    Contributor

    I don't have a problem with publishing a new version of analyzer as long as it doesn't violate semver in any practical sense. But I do think we'd need to do some work to ensure that.

    @bwilkerson would you mind looking at this? 1.20.0-dev.1.0 was a loooong time ago.... ;)

  13. pq commented on Sep 22, 2016

    @pq
    pq
    on Sep 22, 2016
    Contributor

    Whoops. Scratch my request @bwilkerson. I think we found away around needing another push (#5991). Thanks all!

  14. abarth commented on Sep 28, 2016

    @abarth
    abarth
    on Sep 28, 2016
    Contributor

    This issue appears to be fixed.

  15. abarth
    closed this as completedon Sep 28, 2016

  16. github-actions commented on Sep 5, 2021

    @github-actions
    github-actionsbot
    on Sep 5, 2021

    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.

  17. github-actions
    locked as resolved and limited conversation to collaborators on Sep 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

c: regressionIt was better in the past than it is nowtoolAffects the "flutter" command-line tool. See also t: labels.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions