1. 23 Aug, 2021 1 commit
  2. 04 Aug, 2021 1 commit
  3. 28 Jun, 2021 1 commit
  4. 14 Jun, 2021 1 commit
  5. 08 Jun, 2021 1 commit
  6. 27 May, 2021 1 commit
  7. 25 May, 2021 1 commit
  8. 23 Apr, 2021 2 commits
  9. 18 Apr, 2021 1 commit
  10. 17 Apr, 2021 1 commit
  11. 16 Apr, 2021 1 commit
  12. 23 Mar, 2021 1 commit
  13. 12 Mar, 2021 1 commit
  14. 24 Feb, 2021 1 commit
  15. 19 Feb, 2021 1 commit
  16. 11 Feb, 2021 1 commit
  17. 09 Feb, 2021 1 commit
  18. 02 Feb, 2021 1 commit
  19. 27 Jan, 2021 1 commit
  20. 25 Jan, 2021 1 commit
  21. 21 Jan, 2021 2 commits
  22. 13 Jan, 2021 3 commits
  23. 06 Jan, 2021 1 commit
  24. 05 Dec, 2020 1 commit
  25. 20 Nov, 2020 2 commits
  26. 13 Nov, 2020 1 commit
  27. 11 Nov, 2020 1 commit
  28. 10 Nov, 2020 1 commit
  29. 09 Nov, 2020 1 commit
  30. 04 Nov, 2020 2 commits
  31. 27 Oct, 2020 1 commit
    • Jonah Williams's avatar
      [flutter_tools] eagerly set asset directory path, cache flutter views,... · 3300a1bd
      Jonah Williams authored
      [flutter_tools] eagerly set asset directory path, cache flutter views, simplify error handling (#68978)
      
      Performs some small cleanup on the hot reload code path.
      
      - Combines nested try/catch into single try catch, update on clause now that package:vm_service is used and Map does not need to be caught.
      - Cache FlutterViews for the lifetime of the hot reload method handler
      - Set asset directory path once during startup and remove conditional set during hot reload
      3300a1bd
  32. 23 Oct, 2020 1 commit
  33. 13 Oct, 2020 2 commits
    • Jonah Williams's avatar
      [flutter_tools] do not measure progress timeout (#67959) · 9e70180f
      Jonah Williams authored
      Remove "This is taking a long time" progress timeout and TimeoutConfiguration.
      9e70180f
    • Jonah Williams's avatar
      [flutter_tools] attempt to stabilize hot restart benchmark the old fashioned way (#67971) · 5dfe7e6d
      Jonah Williams authored
      A change which sped up hot restart locally caused many of the devicelab measures to regress. I think this is because we do not measure when the isolate is actually "ready", so starting a reload or restart prematurely can cause time spent doing initialization to be registered as part of the reload operation.
      
      A fix for this would be to have the framework include some sort of "initialization complete" event ... but it is not clear what the correct trigger would be. Perhaps after the first frame is successfully registered?
      
      (9a3a0dc1 caused the benchmark regression - possibly since we spend less time syncing files now so we start the restart earlier)
      5dfe7e6d