-
Notifications
You must be signed in to change notification settings - Fork 44
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
Did saving outputs break in 3.10.3 in interactive cells? #713
Comments
I hope not! Looking into this now. |
It seems to work fine for me using one of my own examples https://gist.github.com/sourishkrout/de4bf5ad590a3a48bdce29d321f4d445#file-fixture-01jeeeb593arqe9kdz17f0cef8-md Trying your markdown next. |
Using the notebook below. Do you see any errors in Output->Runme or when you open the Developer Tools in VS Code? |
This is weird; it seems to be happening in one notebook but not others. I'm not sure what's different. I don't see any obvious errors in the Runme window output
|
I'll close this as unreproducible until I can provide more actionable error information. |
I hit this again. In a different notebook. Unfortunately, I can't share the notebook and I don't have any more information on how to reproduce it. I wonder if its an issue with flushing the xterm to populate the notebookdata? I'm looking at the saved output immediately after running the cell. This seems somewhat reminiscent of the issue I had with making the output of interactive cells available to Foyle; (see stateful/vscode-runme#1756). In that issue we need to call addExecInfo in order to flush the data from the terminal widget to the VSCode notebook data structure before serializing it. I think the next step would be to investigate the code path used by session saving to see if/when addExecInfo gets called. |
Okay. I'll do more testing on this. Do you have Foyle running the whole time? I haven't explicitly tested with the AI integration, which might could be a factor. |
Yes; I have Foyle running I'll try to see if I can repro it without Foyle next time it occurs. |
I upgraded to 3.10.3. I have AutoSave Outputs turned on. For interactive cells it doesn't look like the output gets saved
For non-interactive it looks like it gets saved.
Here's an example notebook
testoutputs-01JEE93009ZVJKZVKQXMY9X2TX.md
The text was updated successfully, but these errors were encountered: