v2023.8.10 locks up keyboard in vscode. about djlint-vscode HOT 7 CLOSED

Maybe you are formatting a very large template? I have a template of 1300 lines formatted in 2.5 minutes.

The only change since v2023.8.7 that could have affected this was updating the bundled dependencies.

from djlint-vscode.

The files it's supposed to touch are all small. I did update the static files for the swagger-ui bundle at the time, but that is javascript/css only. And djlint is only configured to touch "django-html". It's all a bit weird. (Also running djlint on "everything" from the command line is rapid all the time.)

from djlint-vscode.

I also forgot to say that if formatting takes more than a few seconds, VSCode shows a message on the bottom right. As far as I understand, you don't have it?

from djlint-vscode.

Even when formatting a large file for a long time, my keyboard doesn't lock up. I have no idea why it happens to you.

from djlint-vscode.

Upgraded to v2023.8.10 again now, and after about a minute it gets stuck again. I get the window saying that it's saving/formatting the 'openapi-ui.html' file (which is the file I'm playing with, and it is 42 lines long).

After leaving it alone for some minutes, I pressed "Cancel" which removed the window. The keyboard stays stuck, regardless, and there is a "Code helper" process running at 100% cpu which keeps on running also after pressing cancel.

When I kill that Code helper process (regular TERM signal), things come unstuck. VScode reports "the extension host terminated suddenly" and it seems to clean up. After this I failed to make things get stuck until restarting VScode again.

I'm not sure, but it may be triggered more reliably if I look at the huge js/css/map files for the swagger-ui before making a change to the template. So maybe the issue is that the plugin hooks into more than it should when starting up?

from djlint-vscode.

To be sure that this extension is related to the Code Helper process, please try the following: https://apple.stackexchange.com/a/393075.

If you kill djLint process, error logs are recorded. To see the logs, run workbench.action.showOutputChannels command in Command Palette and select djLint there.

from djlint-vscode.

showOutputChannels was useful, thanks. I think I can clear djLint of any wrongdoing, what seems to happen is that the NodeService common thing (--utility-sub-type=node.mojom.NodeService) gets bogged down completely, probably due to the js/css/map files. Everything else using it then falls over, including enough to block text input.

Sorry about the false alarm, it was just really confusing here, and showed up while working on a template.

from djlint-vscode.