@compleathorseplayer - thanks for trying to help narrow down where the problem might be. I understand if you don’t have time to pursue this further. Thanks for what you’ve done so far. I wish we could reproduce this.
If someone else has this happen, here’s what I would do to further understand what is going on:
- See if the file content is transferred from the back end. You can look at the network panel in the browser js console, find the network request that contains the filename, and see if the content is in the response, or if it is an empty response. If the response is empty, the problem is likely on the server (see step 2). If the content is there, the problem is likely in the browser (see step 3)
- If the content is not getting to JupyterLab (the content is empty), look for server errors. Is the file utf8-encoded? Is it just one file, or does it happen with every file? What is the file name? We’ve seen problems where adblockers block specific filenames, though I thought that gave errors, not just blank files.
- If the file content is being delivered to the browser, then I would check if there are any javascript errors in the browser js console. Also, I would right-click on the file editor and “Inspect element” to open that particular section of the HTML DOM in the browser js console, and see if the file content appears to be in the DOM.