'truffle compile' doesn't work properly when using multiple network providers.

Issue

Used truffle 4.1.8 and everything was ok. Updated to the latest (4.1.11). Now it seems it compiles the contracts but I must cancel/stop it manually. Here is my folder: http://dropmefiles.com/7dHdO In the same time tried to compile contracts in another folder - it compiles them successfully.

Steps to Reproduce

Unzip the folder from this link and run truffle compile.

Expected Behavior

Compiling process is finished successfully

Actual Results

It seems that contracts are compiled but I see Writing artifacts to ./build/contracts infinitely.

Environment

• Operating System: OSX 10.13.4
• Ethereum client: none (is not involved)
• Truffle version (truffle version): 4.1.11
• node version (node --version): v9.9.0
• npm version (npm --version): 6.0.1

[cgewecke]

@Gargo

1. Unfortunately the non-function format for the wallet is only reliable if there is a single provider. The docs could use some improvement in that section because it’s not obvious why there are two formats. The ‘function’ form was introduced because the non-function form causes super weird behavior in the provider when there are multiple connections open to Infura. Original bug report at #348.

2. No great answer for this - truffle compile builds the artifacts and networks are one the things we track in that object. At the moment this isn’t very helpful but it will become important when the artifact is refactored for the next major release because it will be possible to specify different compilations for different networks. In the comment above I’m just trying to narrow things a bit so we can figure out what’s going wrong. I know the config is getting loaded - I want to see if there’s a specific issue with connecting remotely or not.

[cgewecke]

@gerchicov-bp Thanks for opening this - have amended the docs to remove the non-function closure examples.

Closing.