Another question, our frontend developers experience: after running the `npm run yves:watch` , for s

U01DE320SN6

Another question, our frontend developers experience: after running the npm run yves:watch , for some reason, all slots are stopping to render (which is generally makes page to become pretty much blank with only a few components on it). Restarting the docker container fixes the issue, still. How can we solve that, since it looks like restarting containers takes a lot of their time?

Yuriy Gerton

@ULYHPR789

sprymiker

Hello,

Restarting what container?

U01DB8526TF

and docker/sdk up

sprymiker

How do you run npm run yves:watch this command?
Do you use docker-sync?

U01DB8526TF

docker/sdk cli and inside npm run yves:watch

sprymiker

1. Try to switch to mutagen deploy.dev.yml: docker: mount: mutagen:
2. OR Run watch on host.

giovanni.piemontese

Hi @ULYHPR789 how it works mutagenand how it looks then docker: mount in yml file? Just so as example:

docker:
    mount:
        native:
            platforms:
                - linux

        docker-sync:
            platforms:
                - windows

        mutagen:
            platforms:
                - macos

sprymiker

yep - that would work

giovanni.piemontese

Hi @ULYHPR789
After change my deploy.dev.yml to mutagen (and installed mutagen locally ->

https://mutagen.io/documentation/introduction/installation

brew install mutagen-io/mutagen/mutagen

)

i got some errors in bootstrap and up command:

Bootstrap

/Users/gpiemontese/Projects/el-online.loeffelhardt.local/project/docker/deployment/_tmp/bin/lib/version.sh: line 9: 0011008000: value too great for base (error token is "0011008000")
/Users/gpiemontese/Projects/el-online.loeffelhardt.local/project/docker/deployment/_tmp/bin/sdk/mount/mutagen.sh: line 79: [: : integer expression expected

Up

Error: unknown command "compose" for "mutagen"
Run 'mutagen --help' for usage.

sprymiker

Agree, not so good error messages. We will take care why it does not work as expected.

sprymiker

brew install mutagen-beta

giovanni.piemontese

ok, i will try

sprymiker

and than boot and up again

sprymiker

Bootstrap should give you an instruction how to install mutagen.

sprymiker

Probably a bug there.

giovanni.piemontese

with mutagen-beta

Pulling mutagen (mutagenio/sidecar:latest)...
latest: Pulling from mutagenio/sidecar
df20fa9351a1: Already exists
a80d4c3b4a17: Pull complete
bc1054a75dd8: Pull complete
Digest: sha256:bfd5ad9bf08db16a05da6cb0089f5839727777c609f071ad9e22651b594cd405
Status: Downloaded newer image for mutagenio/sidecar:latest
Creating spryker_b2b_dev_mutagen_1 ... done
Error: unable to reconcile Mutagen sessions: unable to connect to Mutagen daemon: client/daemon version mismatch (daemon restart recommended)

sprymiker

Check if mutagen daemon is running

sprymiker

If not, please, refer to docs: mutagen.io

giovanni.piemontese

maybe i have to uninstall mutagen (i just run brew unlink mutagen) and installed mutagen-beta and started daemon..

I will check again

giovanni.piemontese

after mutagen daemon stop, then register and then again start now sdk up is running and is now Forcing synchronization cycle for session sync_trnArW9KSJ7qBgo6nVcTheWnAY0NAoT5R

It looks that works... I will give u a feedback if everything works as expected when up is finished

giovanni.piemontese

it works, but the sync seems to be very slow...

just wrote a dump('hello') in a controller.. it takes ca. 30 sec to sync..
removed it, after ca. 30sec is yet there my dump..

Is it normal about u?

sprymiker

Super. Thanks.

sprymiker

It works perfectly for me.

giovanni.piemontese

ok..

sprymiker

But still it is file sync so anyway latency.

giovanni.piemontese

yes i see.. i think is ca. 2-3 sec latency.. by u too?

giovanni.piemontese

i think that it looks about changes every 10 sec..
mutagen list --long

--------------------------------------------------------------------------------
Name: spryker-b2b-dev-dev-codebase
Identifier: sync_trnArW9KSJ7qBgo6nVcTheWnAY0NAoT5RCz9npmfz9M
Labels:
    io.mutagen.compose.daemon.identifier: SASK_3QB2_JZK7_IT5P_DV3H_2DMM_7G2S_4ZA5_7VTP_JLB6_YAJT_4BG6
    io.mutagen.compose.project.name: spryker_b2b_dev
Configuration:
    Synchronization mode: Two Way Resolved
    Maximum allowed entry count: Default (2⁶⁴−1)
    Maximum staging file size: Default (18 EB)
    Symbolic link mode: POSIX Raw
    Ignore VCS mode: Default (Propagate)
    Ignores:
        /.git*
        .idea
        .DS_Store
        /.nvmrc
        /.scrutinizer.yml
        /.travis.yml
        /newrelic.ini
        .unison*
        .docker-sync
        /docker
        node_modules
Alpha configuration:
    URL: /Users/gpiemontese/Projects/el-online.loeffelhardt.local/project
    Watch mode: Default (Portable)
    Watch polling interval: Default (10 seconds)
    Probe mode: Default (Probe)
    Scan mode: Default (Accelerated)
    Stage mode: Default (Mutagen Data Directory)
    File mode: 0666
    Directory mode: 0777
    Default file/directory owner: Default
    Default file/directory group: Default
Beta configuration:
    URL: <docker://spryker_b2b_dev_mutagen_1/volumes/spryker_b2b_dev_dev_data_sync>
    Watch mode: Default (Portable)
    Watch polling interval: Default (10 seconds)
    Probe mode: Default (Probe)
    Scan mode: Default (Accelerated)
    Stage mode: Default (Mutagen Data Directory)
    File mode: 0666
    Directory mode: 0777
    Default file/directory owner: id:1000
    Default file/directory group: id:1000
Alpha:
    Connection state: Connected
Beta:
    Connection state: Connected
Status: Watching for changes

sprymiker

It is not so straight. Mutagen uses fsevents and initiate the sync immediately.
Sometimes it can take a few seconds.

Also opcache adds +2 seconds.

sprymiker

Do you experience 10 seconds each time?

sprymiker

docker/sdk sync logs to watch mutagen status