topic Azure Databricks Workspace Editor - Cursor messed up - cannot edit code in Get Started Discussions

Azure Databricks Workspace Editor - Cursor messed up - cannot edit code

UN — Wed, 27 Sep 2023 09:52:44 GMT

I have been using the Azure Databricks Workspace Editor for a few weeks to put together a python script as well as a notebook.

All was well, until yesterday evening. Since then I suddenly have the following issue

the cursor in the editor is misbehaving. When I type, insert, delete - my input is actioned elsewhere on the same line - e.g. a couple of characters to the right. Its made the editor unusable.

I tried closing the files, and reopening them. I shutdown all computes, logged out of my Databricks account last night.

I logged back in this morning afresh, started the computes, open the same files and still the same cursor issue.

Any ideas on how to reset the cursor behaviour to normal?

thanks

Re: Azure Databricks Workspace Editor - Cursor messed up - cannot edit code

daniel_sahal — Thu, 28 Sep 2023 05:42:18 GMT

@UN Had similiar issue a couple of times. Try to clear the cache of your browser or just temporarily (for testing) switch to another browser.

Re: Azure Databricks Workspace Editor - Cursor messed up - cannot edit code

UN — Thu, 28 Sep 2023 12:52:58 GMT

thanks - I tried that - clearing cookies, cache etc and even a different browser - neither helped.

But then after an hour or so the issue cleares up - within the same session - and then after a few minutes starts happening again.

the latest problem is that my code changes are not being reflected in the task / job runs.

e.g. I remove or amend a line of code that prints out a message - but when I run the job, the old text message still appears.

Re: Azure Databricks Workspace Editor - Cursor messed up - cannot edit code

Chibberto — Mon, 02 Oct 2023 15:15:55 GMT

Changing the zoom level of my browser seemed to help here.

Re: Azure Databricks Workspace Editor - Cursor messed up - cannot edit code

UN — Wed, 04 Oct 2023 11:03:48 GMT

Thanks @Chibberto - I will try the zoom level to see if it makes a difference.

In the meantime, the latest issue is that the Autosave is not kicking in sometimes for several minutes. So, if I make a change and then re-run the job - the latest code is not execute.
I am currently having to force save the change by clicking the Last Edited link at the top and click Save...