DonJayamanne
Follow
Pinned
3,736 contributions in the last year
Less
More
Activity overview
Contributed to
microsoft/vscode-jupyter,
microsoft/vscode-python,
DonJayamanne/vscode-jupyter
and 5 other
repositories
Contribution activity
May 2021
Created 39 commits in 8 repositories
Created 2 repositories
Created a pull request in microsoft/vscode-jupyter that received 4 comments
Re-enable skipped tests
These should have been enabled, these seem to have been disabled due to a merge issue.
+16
−9
•
4
comments
Opened 32 other pull requests in 3 repositories
microsoft/vscode-jupyter
22
merged
6
closed
1
open
- Remove unused code
- Restore run above/below commands
- Give preference to build-vsix
- Remove redundant test
- Fixes to flaky execution tests
- Revert "Revert "Updates to VS Code Proposed API (#5822)" (#5830)"
- Update npm dependencies
- Revert "Updates to VS Code Proposed API (#5822)"
- Fixes & minor cleanup of kernel finder
- Updates to VS Code Proposed API
- Fixes to kernel finding & removal of duplicates
- Modal dialog for prompt to install ipykernel
- Re-enable and Fix interrupt tests
- Fix native notebook tests after upgrading to 1.57 Insiders
- test
- Changes to cell execution task API
- Update CHANGELOG and bump version (#5665)
- Better comparisons of the interpreter paths when starting kernels (#5754)
- Revert "Remove dead code (#5757)"
- test
- Remove dead code
- Better telemetry for languages
- Better comparisons of the interpreter paths when starting kernels
- Disable auto start of native notebooks
- Hide the run above/below buttons in native notebook cells
- Some pull requests not shown.
microsoft/vscode-python
2
merged
microsoft/vscode-notebook-renderers
1
merged
Reviewed 27 pull requests in 1 repository
microsoft/vscode-jupyter 27 pull requests
- Change latestExecutionSummary to executionSummary
- Remove unused code
- Fix remote nonConda test suite
- Fixes to flaky execution tests
- update package.json to new notebook value
- Update npm dependencies
- Port license update to release
- Fixes & minor cleanup of kernel finder
-
Support new
workbench.editorAssociationssetting format - Fixes to kernel finding & removal of duplicates
- Jupyter extension is now fully MIT licensed.
- New API Changes
- Clear native notebook cell check mark and timer on kernel restart
- Re-enable and Fix interrupt tests
- Fix native notebook tests after upgrading to 1.57 Insiders
- Changes to cell execution task API
- Merge release back into main
- Move native notebooks cell toolbar to the left
- Update Jupyter to new notebook preload message api
- print locked issues
- add github action to lock closed issues
- Bump VS Code engine to 1.57-insiders
- Better comparisons of the interpreter paths when starting kernels
- Fix typo in .NET Interactive extension name (#5718)
- Update/reinstall if module was installed or exists
- Some pull request reviews not shown.
Created an issue in microsoft/vscode-jupyter that received 18 comments
Modal dialog for ipykernel installs & better messages
When running a notebook without ipykernel the user will be presented with the same message today, but modal diaglog as follows: Should probably ch…
18
comments
Opened 33 other issues in 3 repositories
microsoft/vscode-jupyter
13
open
4
closed
- What do we do if user does not have kernel installed when running/opening a notebook
- Create tests to to fix starting/picking wrong kernel/interpreter
- Unable to run cells when opening existing notebooks (even after running it before a reload)
- Should jupyter extension wait until a document is opened to fetch kernels
- All IPyWidget tests are now failing in Funcitonal tests (100% of the time)
- Support relative paths for images in markdown/rich output cells (of untitled notebooks)
- Opening a native notebook marks it as being dirty
-
Native Notebook tests are flaky, failing randomly with
'Failed to set notebook controllers' - VS Code should provide a builtin renderer for text/latex outputs
- Attachment metadata is not stored correctly in Jupyter Notebooks
- Unable to view image attachments in Markdown cells
- Run Above/Below running the wrong cells
- Plots rendererd/generated in VS Code are not visible in Jupyter (ipynb portability issue)
- Run Above/Below commands not visible in command palette for Native Notebooks
- Support Workspace Trust
- User getting prompted to select a kernel when running a cell
- Add test for manual test plan for notebooks
microsoft/vscode
6
open
8
closed
- Unable to run cells in Jupyter Notebooks
-
Unable to configure edito associations in settings.json
workbench.editorAssociationsused to be an array - NotebookCellMetadata conflicts with user defined metadata
- Allow renderers to communicate with the extension host
- Independent font setting for notebook output
- Provide a builtin renderer for text/latex outputs
- Determine if extension is running in virtual workspace
- notebook.cell.execute does not support execution of a range of cells, only executes the first cell in range
- Support custom markdown rendering in Notebooks
- Toolbar cell commands do not get current cell but get the selected cell as an argument
- Notebook Renderer communication with extension host
-
Disconnect between user running cell from vscode contributed
Run Celland extension contributedRun Cell Above/Below - Run button disappears when toggling between another notebook
- Preferred kernel not selected by default
microsoft/vscode-python
1
closed
1
open
Joined the Notebook Power Tools organization
33
contributions
in private repositories
May 3 – May 10