Stream: shorthand
Topic: Sushi problem
Grahame Grieve (Apr 07 2020 at 04:55):
@Chris Moesel :
Sushi: (node:30500) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, copyfile 'C:\Users\graha\AppData\Roaming\npm\node_modules\fsh-sushi\dist\ig\files\_updatePublisher.bat' -> '_updatePublisher.bat' (00:01.0904)
Grahame Grieve (Apr 07 2020 at 04:56):
that's the A/V kicking in. it hates on that batch file - do you really need it in sushi?
Chris Moesel (Apr 07 2020 at 13:07):
Ah. Well... we thought it would be helpful to our users if we provided those for them. Otherwise they need to go dig them up in the sample-ig and manually copy them over. So, does SUSHI need it? No? But it seems like a helpful feature for users... We haven't heard anyone else report this issue -- is your A/V just a lot more stringent than others?
Grahame Grieve (Apr 07 2020 at 13:19):
it's just bit-defender. But I can't really fault it - a batch file using a windows activex control to download a jar file from the web... smells.
Grahame Grieve (Apr 07 2020 at 13:19):
I could surely work around it, yes.
Grahame Grieve (Apr 07 2020 at 13:20):
but why would I be the only one getting this problem?
Grahame Grieve (Apr 07 2020 at 13:20):
so we're trying to solve differently - there's a special github repo with those files now, I think. @Lloyd McKenzie
Lloyd McKenzie (Apr 07 2020 at 15:12):
We have a proposal to grab them from the sample-ig. Need to find a good time to test w/ @Grahame Grieve to make sure it works w/ his A/V software
Grahame Grieve (Apr 07 2020 at 21:25):
well, whenever then
Lloyd McKenzie (Jun 11 2020 at 17:55):
@Eric Haas - wrong thread?
Eric Haas (Jun 11 2020 at 18:13):
yes wrong thread - deleted
Grahame Grieve (Mar 03 2021 at 03:44):
My system has suddenly stopped being able to run sushi. (Windows 10). I had fsh installed correctly (npm install) but I'm sure it's because the system path is screwed up, but I don't know what it should have in it.
Grahame Grieve (Mar 03 2021 at 03:46):
npm runs OK, but not sushi...
Jose Costa Teixeira (Mar 03 2021 at 08:59):
what do you mean with system path being screwed up?
Jose Costa Teixeira (Mar 03 2021 at 09:03):
windows path? (my path contains C:\Program Files\nodejs\ and C:\Users\Jose\AppData\Roaming\npm)
Jose Costa Teixeira (Mar 03 2021 at 09:04):
but I think that as long as your %AppData%\npm contains sushi and fsh-sushi folders (and the sushi command lines are also there), should work
Grahame Grieve (Mar 03 2021 at 19:23):
thanks
Chris Moesel (Mar 03 2021 at 20:31):
I don't have Windows, so my ability to help is limited, but if Jose's pointers didn't get you on the track, and you're still having problems, please let us know. Specific error messages and/or stack traces are helpful.
Chris Moesel (Mar 03 2021 at 20:32):
Usually, if npm is installed correctly, then worst case removing and re-adding usually works:
npm remove -g fsh-sushi
npm install -g fsh-sushi
(Also remember that the npm package name is actually fsh-sushi, not sushi).
Grahame Grieve (Mar 04 2021 at 18:38):
that didn't work. The npm installation itself was the problem. I just had to re-add that appdata path to my system path
Last updated: Apr 12 2022 at 19:14 UTC
