-
Notifications
You must be signed in to change notification settings - Fork 161
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
Merge does not work for some notebooks #690
Comments
I think for 3.2, failing is probably the correct behavior, as we don't currently have a way of letting the user know that there is a conflict on a cell ID (nor does the code know what it means to have a conflict on a field that it doesn't know about). However, I think our failure UX needs a good revamp. I.e. we should better surface the error to the user without it hanging and having the user need to look in the browser webtools. Separately, I think #639 does solve it since it marks the
|
This should now be fixed in master after merging #639. I will leave this issue open for now for visibility, and for considering backporting to lab-3 compatible version. |
As we are in rc now, I'm closing this. Backport can be considered later if needed. |
This was previously reported in #550 (comment). This is the full traceback:
Both versions 3.2 and 4.0 alpha are affected. Manually stripping cell IDs solves the problem for both versions. This can be reproduced by running:
The direct reason for exception is that
id
is not on the whitelist list:nbdime/packages/nbdime/src/merge/model/cell.ts
Lines 154 to 160 in ed70f8d
The exact mechanism in which this gets triggered is not clear to me:
example8
includes added/deleted cells and does not workexample9
includes a single cell works fine despite changed IDsexample10
includes a single cell and does not workIt might be that #639 solves this issue, but ideally all the examples would be covered by an integration test so that we know for sure.
The text was updated successfully, but these errors were encountered: