You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
by the first installation of extension, everything is fine, but if I rerun the playbook it failed to reinstall the extension. is there any way to prevent this failure, by using conditioning or a similar solution or workaround? in the python code you used code --install-extension --force as in [executable, --install-extension, --force] but even though I get the error when rerunning my playbook.
failed: [devel_lin] (item=developer: dbaeumer.vscode-eslint) => {"ansible_loop_var": "item", "changed": false, "item": [{"username": "developer"}, "dbaeumer.vscode-eslint"], "msg": "Error
while upgrading extension [dbaeumer.vscode-eslint]: (0) Installing extensions...\nExtension 'dbaeumer.vscode-eslint' is already installed.\nbash: cannot set terminal process group (-1): Inappropriate ioctl for device\nbash: no job control in this shell\n"}
thank you in advance :)
The text was updated successfully, but these errors were encountered:
by the first installation of extension, everything is fine, but if I rerun the playbook it failed to reinstall the extension. is there any way to prevent this failure, by using conditioning or a similar solution or workaround? in the python code you used code --install-extension --force as in [executable, --install-extension, --force] but even though I get the error when rerunning my playbook.
failed: [devel_lin] (item=developer: dbaeumer.vscode-eslint) => {"ansible_loop_var": "item", "changed": false, "item": [{"username": "developer"}, "dbaeumer.vscode-eslint"], "msg": "Error
while upgrading extension [dbaeumer.vscode-eslint]: (0) Installing extensions...\nExtension 'dbaeumer.vscode-eslint' is already installed.\nbash: cannot set terminal process group (-1): Inappropriate ioctl for device\nbash: no job control in this shell\n"}
thank you in advance :)
The text was updated successfully, but these errors were encountered: