./start.sh fails on MacOS

[rickmcgeer]

Describe the bug I'm seeing the following error from start.sh

023-05-22T15:59:04.264Z error: Error loading plugin lively.server/plugins/components-browser.js
2023-05-22T15:59:04.264Z error: Error starting server: (SystemJS) ENOENT: no such file or directory, open '/Users/rick/Projects/lively.next/lively.server/plugins/components-browser.js'
    Error: ENOENT: no such file or directory, open '/Users/rick/Projects/lively.next/lively.server/plugins/components-browser.js'
    Error loading /Users/rick/Projects/lively.next/lively.server/plugins/components-browser.js

I checked on github and indeed there is no components-browser.js in plugins. I did a git pull to ensure I'm up to date, and actually checked to ensure that the latest fix to VideoMorph were in, and they are.

To Reproduce this doesn't happen on other platforms

Setup

• macOS

Version: According to git log, I'm on commit 887a081649d310f7ffd7aa4b5bdce72f13149a0e (HEAD -> video-morph, origin/video-morph)

[linusha]

Is this on a setup that you do not use regularly, e.g. where you pulled a lot of changes right now at once? Is this maybe the same thing as is https://github.com/LivelyKernel/lively.next/issues/505 again?

[merryman]

As pointed out by @linusha please consider running install.sh first and see if the issue persists.

[rickmcgeer]

I did a full pull, ./install.sh, and the same result.

Here's the command history: 528 git checkout main 529 git pull 530 ./install.sh 531 ./start.sh

And the result

2023-05-25T03:44:06.581Z error: Error loading plugin lively.server/plugins/components-browser.js 2023-05-25T03:44:06.582Z error: Error starting server: (SystemJS) ENOENT: no such file or directory, open '/Users/rick/Projects/lively.next/lively.server/plugins/components-browser.js' Error: ENOENT: no such file or directory, open '/Users/rick/Projects/lively.next/lively.server/plugins/components-browser.js' Error loading /Users/rick/Projects/lively.next/lively.server/plugins/components-browser.js

Now, there's no problem, of course; I can simply burn the directory down and just do a fresh clone, which I'm sure will work. But we probably want to understand this, and as you noted this is my secondary machine, so I'll leave it for the moment.

Incidentally, the freezer runs fine from the command line.

[merryman]

@linusha Is there something like a clean install? I'm pretty sure @rickmcgeer is just stuck on an outdated config.js that configures the server with invalid plugins.

[linusha]

@rickmcgeer you can either fixup the file manually, as described in #505 or just delete the config.js file and rerun install.sh should be equivalent and should hopefully fix your issue!

Please report back if it worked (or didn't work).

[rickmcgeer]

I'm sure that's exactly it. The reason I haven't blown stuff away is I want to leave this up to diagnose it. If you guys can think of any experiments to try, let me know

On Thu, May 25, 2023 at 12:15 AM Robin Schreiber @.***> wrote:

@linusha https://github.com/linusha Is there something like a clean install? I'm pretty sure @rickmcgeer https://github.com/rickmcgeer is just stuck on an outdated config.js that configures the server with invalid plugins.

— Reply to this email directly, view it on GitHub https://github.com/LivelyKernel/lively.next/issues/854#issuecomment-1562398784, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFAHA723WMC5VGQVJKDZSTXH4BHXANCNFSM6AAAAAAYKWFF7A . You are receiving this because you were mentioned.Message ID: @.***>

-- Rick McGeer @.*** +15103346004

[merryman]

Can this be closed now?

[rickmcgeer]

We can close it whenever you think you have enough data; as I've said, there's an easy fix for me (just blow away the directory and rebuild) so the only reason this is open is for me to run experiments for you.

On Tue, May 30, 2023 at 9:36 AM Robin Schreiber @.***> wrote:

Can this be closed now?

— Reply to this email directly, view it on GitHub https://github.com/LivelyKernel/lively.next/issues/854#issuecomment-1568742023, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFAHA3PVT7OMI5RJGME2HTXIYOXFANCNFSM6AAAAAAYKWFF7A . You are receiving this because you were mentioned.Message ID: @.***>

-- Rick McGeer @.*** +15103346004

[linusha]

I think there was some kind of misunderstanding, but thanks for caring! You can nuke it from our side, too!