Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'infeos compile' does not use local changes for compilation #5

Open
dbendt opened this issue Mar 3, 2019 · 3 comments
Open

'infeos compile' does not use local changes for compilation #5

dbendt opened this issue Mar 3, 2019 · 3 comments
Labels
bug Something isn't working

Comments

@dbendt
Copy link

dbendt commented Mar 3, 2019

It appears the docker volume is not bound to the working contracts directory. If a bug causes a compilation error, fixing the error in the contract directory and running infeos compile again will generate the same compilation error. Only running infeos run-node will pull the latest code into the docker container.

Also, when a compilation error occurs, "Successful compilation" appears in the console which is not accurate.

@DimitarSD
Copy link
Collaborator

Hi @dbendt! Thanks for sharing. We are aware of this bug and it's going to be fixed with next version

@DimitarSD DimitarSD added the bug Something isn't working label Mar 4, 2019
@Gammanik
Copy link

Gammanik commented Mar 6, 2019

So to compile the changed contract I need to write infeos run-node every time?
When it is gonna be fixed and the "contract" folder will be a mounted volume.

@memcmp
Copy link

memcmp commented Oct 8, 2019

Any update or workaround for this one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants