search

ethereum / remix-project

Remix is a browser-based compiler and IDE that enables users to build Ethereum contracts with Solidity language and to debug transactions.
https://remix-ide.readthedocs.io
MIT License
2.36k stars 888 forks source link

remixd just stop running right after access file system #3910

Open ColligenceLabs opened 12 months ago

ColligenceLabs commented 12 months ago

% remixd [INFO] you are using the latest version 0.6.15 [WARN] You can only connect to remixd from one of the supported origins. [WARN] Any application that runs on your computer can potentially read from and write to all files in the directory. [WARN] Symbolic links are not forwarded to Remix IDE

[INFO] Thu Jul 13 2023 15:47:05 GMT+0900 (Korean Standard Time) remixd is listening on 127.0.0.1:65520 [INFO] Thu Jul 13 2023 15:47:05 GMT+0900 (Korean Standard Time) slither is listening on 127.0.0.1:65523 [INFO] Thu Jul 13 2023 15:47:05 GMT+0900 (Korean Standard Time) hardhat is listening on 127.0.0.1:65522 [WARN] You may now only use IDE at https://remix.ethereum.org to connect to that instance setup notifications for /Users/peter/Develop/Talken-Staking/kommune-staking-contracts [WARN] You may now only use IDE at https://remix.ethereum.org to connect to that instance [WARN] You may now only use IDE at https://remix.ethereum.org to connect to that instance Hardhat plugin activated listening on Hardhat compilation... %

Aniket-Engg commented 12 months ago

Can you share your OS?

Aniket-Engg commented 11 months ago

@ColligenceLabs can you try with latest remixd version?

stackdump commented 11 months ago

I'm seeing this w/ 0.6.16 - is there a way to increase logging?

exit code is = 0 when this happens to me

UPDATE: after i removed caches and artifacts from my project - this worked again w/ latest version

kevin-pv01 commented 10 months ago

I got same error after upgrading to 0.6.17, this fixed it:

rm -rf deployments && rm -rf cache && rm -rf artifacts
yarn install && yarn compile --force
kevin-pv01 commented 9 months ago

I got same error after upgrading to 0.6.17, this fixed it:

rm -rf deployments && rm -rf cache && rm -rf artifacts
yarn install && yarn compile --force

this also fixed same issue for me after an upgrade