search

openflighthpc / concertim-ansible-playbook

Ansible playbook for building a Concertim appliance
Eclipse Public License 2.0
0 stars 0 forks source link

Vagrant dev workflow - asset changes often not being auto reloaded #66

Closed timalces closed 9 months ago

timalces commented 10 months ago

I've had some inconsistent issues after using the vagrant workflow to build visualiser & set it to dev mode, where changes to css are not being auto reloaded.

I haven't been able to determine what makes it sometimes work and sometimes not. But the vast majority of the time it does not work. I've tried rebuilding multiple times and stopping and restarting visualiser. I've had some success by shutting down the VM, deleting assets/builds/application.css and then restarting, but this is not consistent. There are no errors reported in the ct-vis-app screen. Once it is working it seems to continue working until visualiser is stopped.

I'm not sure if this is due to recent changes to this repo or visualiser itself. This was first experienced on 19th October - I pulled from main on the afternoon of the 18th but I'm not sure how far behind my main branch was before that (/what commits were added, that could be the cause). I'm using dev-2023-10-17

benarmston commented 9 months ago

This should have been fixed in #71. I'm going to close and it can be reopened if it isn't fixed.

Current understanding is that this was due to the memory on the vagrant machine being reduced in https://github.com/alces-flight/concertim-ansible-playbook/commit/15d36990106ad0f6b0d515dc718525dd5098c4ef. This has been changed back to 2048 in #71 (https://github.com/alces-flight/concertim-ansible-playbook/pull/71/commits/5909c00c48a4e915a6a09b2abd554a996fb44b63). #71 also introduced a BOX_MEM environment variable allow specifying the VMs RAM without having to edit the Vagrantfile.