ā If you like what I do, buy Stoke a brew ā
We all know the knife in the heart that is 'git pull' with Automatic1111 š®āšØš„š.
The double edge sword of wanting the latest updates versus risking the 'core error' (can't think of the proper console output). So last night I was merging the new Stoked Reality model and everything was running perfectly. I installed a couple of addons and left 'Merge Board' to work its magic šŖ.
I check the console this morning and my new merge is working a treat. Then I remembered about those addon installs, so I exit Auto1111 via the big exit button. All is still good with the world.
# Automatic1111 install directory
$ git pull
$ ./webui.sh --update-all-extensionsMy console loads as usual up until just after 'ADetailer' then the dreaded error message shows "webui.sh: unexpected arguement '@'" (the error looks something like this, I was more interested in fixing the problem than taking notes) and the startup script exits.
First attempt at fixing the error was editing the line of code mentioned.
# Automatic1111 install directory
$ nano webui.shThen I searched for the '@' symbol mentioned in the error console output, there were two entries at the end of the code.
So I changed this in both locations...
"${LAUNCH_SCRIPT}" "$@"to...
"${LAUNCH_SCRIPT}" "$"Well that didn't work, so then I tried...
"${LAUNCH_SCRIPT}" ""Still no use, so I changed everything back the way it was.
Think Stoke, think! š¤āš”
Try putting EVERYTHING back the way it was. So I used Filezilla (I access old rig with SD via my laptop) to delete the last addons I installed: FABRIC, Webpage close confirmation dialogue, sd-wav2lip-uhq.
While I am using Filezilla you can just use the file manager of your choice, it isn't important. Then I navigated to Auto1111/extensions/ and deleted the above mentioned addons.
I then deleted all the cache files as I find this is a good fix for 'core dumped' errors. Navigate to your Automatic1111 folder and run a search for folders with the name '__pycache__'.
Let it finish, time taken is dependant on the amount you have installed obviously. Once the scan has finished 'select all' to select every '__pycache__' folder, then hit the 'delete' button. That is it ā .
Rebooted after this, and all is good with the world again, Ahhh (happy sound) āØšāØ
This is just a simple fix, but I am aware that we are all on different rungs of the ladder we slap against the learning curve. Simply deleting all the pycache files is often the easiest starting point in any git pull fault finding expedition š.
As I said a simple fix, but hopefully this helps someone š.