Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.ipynb Open Changes in Source Control not working #5280

Closed
giammi56 opened this issue Mar 24, 2021 · 1 comment
Closed

.ipynb Open Changes in Source Control not working #5280

giammi56 opened this issue Mar 24, 2021 · 1 comment
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@giammi56
Copy link

giammi56 commented Mar 24, 2021

Version: 1.54.3
Commit: 2b9aebd5354a3629c3aba0a5f5df49f43d6689f8
Date: 2021-03-15T10:55:24.277Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Linux x64 5.8.0-45-generic snap

Expected behaviour

  1. Source control upon clicking on a staged on .ipyn (or right click Open Changes): side by side staged and last commit with red and green area for the diff.
  2. Sorce control upon clicking on commit in the timeline: same as above.

Actual behaviour

  1. The file opens, shows (index) in the title for a second, then turn into (git) and display the actual file: no diff, no comparison with the previous commit, just one column.
    2.When clicking on a commit in the timeline, SOMETIMES It opens two files side by side with the title "xxxx.ipynb contrast yyyyy.ipynb", but they neither scroll async nor the differences are shown. SOMETIMES shows just one file with title (git).

Steps to reproduce:

  1. With a the jupyter strip installed and configured.
    1.Go to SCM (ctrl+shoft+G)
  2. Stage a .ipynb.
  3. click on the stage file (or right click Open Changes)
  4. as comparison (and to prove git is working fine) open a new terminal in vs code
  5. type git diff --cahced

NOTE: everything works fine for .py scripts. This problem persists for 2 months.

@giammi56 giammi56 added the bug Issue identified by VS Code Team member as probable bug label Mar 24, 2021
@DonJayamanne
Copy link
Contributor

Duplicate of #633

@DonJayamanne DonJayamanne marked this as a duplicate of #633 Mar 25, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

2 participants