Skip to content

Test status indicator is duplicated #4384

Closed

Description

@incendial

Describe the bug
Noticed that the test status indicator (play button or spinner) got duplicated for the whole line length of the test.

To Reproduce
No steps. This is a new test file and I noticed that it's too much of the visual noise.

Expected behavior
Only one indicator.

Screenshots
Screenshot 2023-02-13 at 16 51 53

Screen.Recording.2023-02-13.at.16.48.25.mov

Please complete the following information:

  • Operating System and version: macOS 12.6
  • VS Code version: 1.75.1
  • Dart extension version: 3.58
  • Dart/Flutter SDK version: Dart SDK version: 2.19.0 (stable) (Mon Jan 23 11:29:09 2023 -0800) on "macos_x64"
  • Target device (if the issue relates to Flutter debugging): -

Activity

  1. DanTup commented on Feb 14, 2023

    @DanTup
    Member

    I'm not able to reproduce this. Can you reproduce in a new file? Are there any specific steps?

  2. added
    awaiting infoRequires more information from the customer to progress
    on Feb 14, 2023
  3. incendial commented on Feb 15, 2023

    @incendial
    Author

    Unfortunately, no, I don't have any steps either. Feel free to close this one if without the steps it's useless. If I see this again I'll get back.

  4. DanTup commented on Feb 15, 2023

    @DanTup
    Member

    If you see it again, could you also get a screenshot of what the Test Explorer tree looks like for this file?

    I'll leave this open for now with the awaiting-info tag. If you see it again post back, and otherwise the bot will close it in ~30 days. Thanks!

  5. github-actions commented on Mar 8, 2023

    @github-actions

    This issue has been marked stale because it is tagged awaiting-info for 20 days with no activity. Remove the stale label or comment to prevent the issue being closed in 10 days.

  6. incendial commented on Mar 12, 2023

    @incendial
    Author

    Got this problem again
    Screenshot 2023-03-12 at 13 53 08

  7. incendial commented on Mar 12, 2023

    @incendial
    Author

    Test explorer:
    Screenshot 2023-03-12 at 13 53 33

  8. incendial commented on Mar 12, 2023

    @incendial
    Author

    I was able to repro it in one go, but then it stopped appearing 😞
    Investigating...

  9. incendial commented on Mar 12, 2023

    @incendial
    Author

    As you can see, I'm waiting for the icon to appear before writing the body.

    repro.mov
  10. DanTup commented on Mar 13, 2023

    @DanTup
    Member

    @incendial I can repro with those steps, thank you!

  11. added
    in testingRelates to test execution of Dart/Flutter tests for end users
    and removed
    awaiting infoRequires more information from the customer to progress
    on Mar 13, 2023
  12. 1 remaining item

  13. added
    in editorRelates to code editing or language features
    on Mar 13, 2023
  14. DanTup commented on Mar 13, 2023

    @DanTup
    Member

    I think at least part of this is a VS Code bug, I've filed microsoft/vscode#176951. I'm still trying to figure out if there's more to it though (and if there is, whether it's an issue here or there).

  15. DanTup commented on Mar 13, 2023

    @DanTup
    Member

    I think this might be entirely a VS Code issue. I was able to adapt their sample to have the full issue (not just duplicated icons, but them not disappearing on the next update - which is what we're seeing here). I've added some notes to microsoft/vscode#176951 (comment).

    Hopefully once that issue is fixed there, it'll be good here. I'll keep this issue open to track it until it's resolved though.

  16. incendial commented on Mar 13, 2023

    @incendial
    Author

    Interesting that no one else had spotted it 😅. Thank you!

    I think this might be entirely a VS Code issue.

    Interesting that I had never had it with TS, for example 🤔.

  17. DanTup commented on Mar 13, 2023

    @DanTup
    Member

    I think it depends on some specifics:

    1. The "range" of the test covers the whole line, so VS Code will "expand" it when you're pressing <enter> inside it
    2. We update the existing test (don't remove/add a new one) when you make changes
    3. We compute exactly the same range when we update the test as the one that VS Code expanded to (which I think is causing VS code to short-cut some work, which doesn't re-generate the icons)

    So for example the sample test provider they had always truncated the test at the end of the first line, so although the issue showed up briefly when you pressed <enter>, the update "fixed" it by replacing the test range which triggers VS Code replacing the duplicated icons.

    (there's a lot of assumptions there though, we'll see what they say when it's looked at :-))

  18. modified the milestones: v3.62.0, v3.64.0 on Mar 30, 2023
  19. modified the milestones: v3.64.0, v3.66.0 on Apr 19, 2023
  20. modified the milestones: v3.66.0, v3.68.0 on May 25, 2023
  21. DanTup commented on Jun 13, 2023

    @DanTup
    Member

    This was fixed in the latest VS Code.

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

    in editorRelates to code editing or language featuresin testingRelates to test execution of Dart/Flutter tests for end usersis bug

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions