Skip to content
Snippets Groups Projects
  1. May 30, 2023
  2. May 20, 2023
  3. May 11, 2023
  4. Apr 19, 2023
  5. Feb 03, 2023
  6. Dec 06, 2022
  7. Oct 03, 2022
  8. Sep 07, 2022
  9. Apr 27, 2022
    • Mark Banner's avatar
      Bug 1766268 - Update eslint-plugin-mozilla's version of estraverse to fix... · 27daf1b0
      Mark Banner authored
      Bug 1766268 - Update eslint-plugin-mozilla's version of estraverse to fix issues with private identifiers. r=mossop
      
      Due to babel still requiring an old version of estraverse, this disables our setup checking for changes
      to modules in the eslint-plugin-mozilla package.json. For now, we'll need to remember to ensure there
      is a top-level update to go with any changes - though that normally happens anyway.
      
      For good measure, this also updates some of the top-level modules to ensure that node_modules is re-installed for everyone.
      
      Differential Revision: https://phabricator.services.mozilla.com/D144758
      27daf1b0
  10. Apr 22, 2022
  11. Mar 25, 2022
  12. Feb 07, 2022
  13. Oct 21, 2021
  14. Aug 18, 2021
  15. May 19, 2021
  16. Apr 16, 2021
  17. Apr 14, 2021
  18. Apr 13, 2021
  19. Apr 04, 2021
  20. Oct 02, 2020
  21. Aug 20, 2020
  22. Jul 24, 2020
  23. Mar 23, 2020
    • Dave Townsend's avatar
      Bug 1622717: When parsing an AST allow the chosen parser to override the... · 6ed37285
      Dave Townsend authored
      Bug 1622717: When parsing an AST allow the chosen parser to override the default scope manager and visitor keys. r=Standard8
      
      There appears to be a bug in babel-eslint where it still uses the old
      `ExperimentalSpreadProperty` and `ExperimentalRestProperty` node types when
      babel itself (and hence the AST visitor keys) have switched to `SpreadElement`
      and `RestElement`. I suspect there isn't much point in filing a babel-eslint
      issue for this, they are currently in the process of working on v11 which does
      fix the issue but is currently only available as a beta release.
      
      There are three alternatives:
      
      1. Use the beta babel-eslint.
      2. Hack the visitor keys to include the old node types.
      3. Traverse the AST changing the nodes from the old types to the new types.
      
      Using a beta version is probably not a great idea so this patch does 2 which is
      the simplest of the other options. It does have the drawback however that if
      any eslint rules we use rely on the new node type names they will fail to work.
      
      Differential Revision: https://phabricator.services.mozilla.com/D66998
      
      --HG--
      extra : moz-landing-system : lando
      6ed37285
  24. Mar 13, 2020
  25. Mar 08, 2020
  26. Jan 21, 2020
  27. Dec 19, 2019
  28. Aug 27, 2019
  29. Aug 21, 2019
  30. Jul 17, 2019
  31. Jun 14, 2019
    • yulia's avatar
      Bug 1494796 - Removing threadClient specifics from DebuggerClient Special case... · 5f77a853
      yulia authored
      Bug 1494796 - Removing threadClient specifics from DebuggerClient Special case resume; r=jdescottes,jlast
      
      The resume case is much more complex than the other events, because we do an
      unsafeSynchronize to send an unsolicited pause. In the old system, the resume response would have
      been ignored, but that is no longer the case. With the new system, we do not want to send a response
      to a resume action if it did not come from the UI. This also update the debugger panel code to
      accept a resume.
      
      Differential Revision: https://phabricator.services.mozilla.com/D32697
      
      --HG--
      extra : moz-landing-system : lando
      5f77a853
    • Narcis Beleuzu's avatar
      Backed out 13 changesets (bug 1494796) for dt failures on browser_dbg-navigation.js . CLOSED TREE · 7d018750
      Narcis Beleuzu authored
      Backed out changeset 5db908b26d50 (bug 1494796)
      Backed out changeset c48f00f0df72 (bug 1494796)
      Backed out changeset 591453b88e8b (bug 1494796)
      Backed out changeset a14e820311bc (bug 1494796)
      Backed out changeset 0e214d450b35 (bug 1494796)
      Backed out changeset 1a4ab8b35a85 (bug 1494796)
      Backed out changeset fe1559f5f1d4 (bug 1494796)
      Backed out changeset 35d967de4223 (bug 1494796)
      Backed out changeset 1d21a55cae15 (bug 1494796)
      Backed out changeset 33eec873a43e (bug 1494796)
      Backed out changeset 25e69c21dc2e (bug 1494796)
      Backed out changeset b900d41c8ae8 (bug 1494796)
      Backed out changeset c2a034e34fa6 (bug 1494796)
      7d018750
    • yulia's avatar
      Bug 1494796 - Removing threadClient specifics from DebuggerClient Special case... · 607a8359
      yulia authored
      Bug 1494796 - Removing threadClient specifics from DebuggerClient Special case resume; r=jdescottes,jlast
      
      The resume case is much more complex than the other events, because we do an
      unsafeSynchronize to send an unsolicited pause. In the old system, the resume response would have
      been ignored, but that is no longer the case. With the new system, we do not want to send a response
      to a resume action if it did not come from the UI. This also update the debugger panel code to
      accept a resume.
      
      Differential Revision: https://phabricator.services.mozilla.com/D32697
      
      --HG--
      extra : moz-landing-system : lando
      607a8359
Loading