Weekly Triage meetings: Jan–Dec 2025

[RRosio]

Triage issues in JupyterLab and corresponding projects.

Meeting is typically held at 09:00 US Pacific time on Tuesdays.

Meeting info: https://zoom.us/my/jovyan?pwd%3Dc0JZTHlNdS9Sek9vdzR3aTJ4SzFTQT09

Previous notes:

• Weekly Triage meetings: Jul–Dec 2024 #250 (2024-07 through 2024-12)
• Weekly Triage meetings: Jan–Jun 2024 #228 (2024-01 through 2024-06)
• Weekly Triage meetings: Jul–Dec 2023 #203 (2023-07 through 2023-12)
• Weekly Triage meetings: Jan-Jun 2023 #169 (2023-01 through 2023-06)
• Weekly Triage meetings: Jul-Dec 2022 #151 (2022-07 through 2022-12)
• Weekly Triage meetings: Feb-Jun 2022 #137 (2022-01 through 2022-06)

Goals

Act on long-running, highly demanded, or highly discussed issues to get them ready for development work.

Resources

https://jupyterlab.readthedocs.io/en/latest/developer/contributing.html#submitting-a-pull-request-contribution

Triage Process

All requested information, where applicable, is provided. From the templates in JupyterLab’s issues:

For a bug:

• Description, preferably including screen shots
• Steps to reproduce
• Expected behavior
• Context, such as OS, browser, JupyterLab version, and output or log excerpts

For a feature request:

• Description of the problem
• Description of the proposed solution
• Additional context

The issue should represent real, relevant, feasible work. In short, if a knowledgeable person were to be assigned this issue, they would be able to complete it with a reasonable amount of effort and assistance, and it furthers the goals of the Jupyter project.

• Issues should be unique; triage is the best time to identify duplicates.
• Bugs represent valid expectations for use of Jupyter products and services.
• Expectations for security, performance, accessibility, and localization match generally-accepted norms in the community that uses Jupyter products.
• The issue represents work that one developer can commit to owning, even if they collaborate with other developers for feedback. Excessively large issues should be split into multiple issues, each triaged individually, or into team-compass issues to discuss more substantive changes.

1. Read issues
2. Tag issues
   a. good first issue
   b. bug
   c. feature parity
   d. Tag milestones
3. Identify duplicates
4. Respond to issues
5. Assign another person

Add milestone if you can achieve the goal.

Meetings

Primary focus:

• JupyterLab untriaged issues
• Notebook untriaged issues
• JupyterLab Desktop untriaged issues
• NBClassic untriaged issues

[RRosio]

January 7, 2024

Name	Organization	Username
Michał Krassowski	QuanSight	@krassowski
Andrii Ieroshenko	AWS	@andrii-i
Rosio Reyes	Anaconda	@RRosio
Michael Chin	AWS	@michaelnchin

Before the meeting, 10 issues in JupyterLab needed triage. After the meeting, none remain.

• Jumpled up text in Jupyterlab version 4.3.2  jupyterlab#17073 (needs info)
• Notebook toolbar popup items displayed on top of the notebook widget  jupyterlab#17111 (accepted)
• License download does not work in jupyter lite jupyterlab#17117 (needs info)
• "Error display of code completion for dict key" jupyterlab#17124 (accepted)
• a + Enter doesn't enter cell, stays in command mode jupyterlab#17125 (accepted)
• jupyterlab4.2.X extension proxy bug jupyterlab#17126 (accepted)
• JSON Settings Editor: Error Messages Not Being Displayed jupyterlab#17127 (needs info)
• Cell estimated height override is sometimes incorrectly zero jupyterlab#17131 (accepted)
• Uncaught (in promise) TypeError in jlab_core on chrome console on Windows jupyterlab#17135 (needs info)
• Clicking close All on open tabs will always leave one, not all of them jupyterlab#17140 (needs info)
• New code cells are sometimes inserted in the wrong location jupyterlab#17144 (closed, duplicate of "Add Cell" regression in 4.2.x on Safari jupyterlab#16373)

Before the meeting, 1 issue in Notebook needed triage. After the meeting, none remain.

• 'navigate files and folders with single click' only effective in jupyter lab jupyter/notebook#7538 (accepted)

Before the meeting, 1 issue in Notebook Classic needed triage. After the meeting, 1 remains.

• Arrows are out of functionality jupyter/nbclassic#309 (needs info)

Before the meeting, 1 issue in JupyterLab Desktop needed triage, after the meeting none remain.

• A JavaScript error occured in the main process: Unexpected end of JSON input jupyterlab-desktop#881 (closed)