Skip to content

defaultStackFilter and/or tests need updating for causal async stacks #8128

Closed

Description

@rmacnak-google

@Hixie @johnmccutchan

Trying to roll the engine, I see that a few tests are failing because the new causal async stacktraces include new frames the tests don't expect. There's a tension between the defaultStackFilter trying to reduce verbosity and causal async stack trying to provide context.

Activity

  1. abarth commented on Feb 14, 2017

    @abarth
    Contributor

    Sorry, that test is over testing. Feel free to change the test.

  2. Hixie commented on Feb 14, 2017

    @Hixie
    Contributor

    Please feel free to change the test, as @abarth suggests, but I'd like to review the change before checkin.

    Also, the stack trace in https://travis-ci.org/flutter/flutter/builds/201356918 is crazy, what is going on there?

  3. rmacnak-google commented on Feb 14, 2017

    @rmacnak-google
    ContributorAuthor

    For a program like

    baz() async => throw "XYZ";
    bar() async => await baz();
    foo() async => await bar();
    main() async => await foo();
    

    the stack trace used to be

    #0      baz.<baz_async_body> (file:///Users/rmacnak/dart1/sdk/a.dart:2:16)
    #1      Future.Future.microtask.<anonymous closure> (dart:async/future.dart:184)
    #2      _microtaskLoop (dart:async/schedule_microtask.dart:41)
    #3      _startMicrotaskLoop (dart:async/schedule_microtask.dart:50)
    #4      _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:96)
    #5      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:149)
    

    but now is

    #0      baz (file:///Users/rmacnak/dart1/sdk/a.dart:2:16)
    <asynchronous suspension>
    #1      bar (file:///Users/rmacnak/dart1/sdk/a.dart:3:22)
    <asynchronous suspension>
    #2      foo (file:///Users/rmacnak/dart1/sdk/a.dart:4:22)
    <asynchronous suspension>
    #3      main (file:///Users/rmacnak/dart1/sdk/a.dart:5:23)
    <asynchronous suspension>
    #4      _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:261)
    #5      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:148)
    
  4. added a commit that references this issue on Feb 15, 2017
  5. Hixie commented on Feb 28, 2017

    @Hixie
    Contributor

    @rmacnak-google Can you clarify what needs changing here?

  6. added this to the milestone on Feb 28, 2017
  7. added
    frameworkflutter/packages/flutter repository. See also f: labels.
    on Nov 26, 2019
  8. zoeyfan commented on Jan 3, 2020

    @zoeyfan

    @rmacnak-google since there hasn't been a response since 2017, I am going to close the issue. If this is still relevant, please reopen and provide more information.

  9. github-actions commented on Aug 8, 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.

  10. locked as resolved and limited conversation to collaborators on Aug 8, 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

    c: contributor-productivityTeam-specific productivity, code health, technical debt.frameworkflutter/packages/flutter repository. See also f: labels.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions