Closed ErrorEater closed 3 years ago
@aliveli186 what version of truffle are you using? This should have been resolved in v5.3.10 😅 . If you're on a previous version you can upgrade with the following command npm uninstall -g truffle && npm install -g truffle
What could be the problem and how can I compile with "-s ASSERTIONS=1" to get more information?
That output shouldn't be displayed but you can examine the end of the dump, which may have information on the rejected promise or error that caused the issue.
@cds-amal I upgraded, still errors but shows more details.
I added networkCheckTimeout: 1000000
but has no effect.
F:\Projects\Blockchain\node_modules\request\request.js:848
var e = new Error('ETIMEDOUT')
^
Error: PollingBlockTracker - encountered an error while attempting to update latest block:
Error: ETIMEDOUT
at Timeout.<anonymous> (F:\Projects\Blockchain\node_modules\request\request.js:848:19)
at listOnTimeout (internal/timers.js:554:17)
at processTimers (internal/timers.js:497:7)
at PollingBlockTracker._performSync (F:\Projects\Blockchain\node_modules\eth-block-tracker\src\polling.js:51:24)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at runNextTicks (internal/process/task_queues.js:62:3)
at listOnTimeout (internal/timers.js:523:9)
at processTimers (internal/timers.js:497:7)
UnhandledRejections detected
Promise {
<rejected> {
code: -32603,
message: 'ETIMEDOUT',
data: { originalError: [Object] },
stack: 'Error: ETIMEDOUT\n' +
' at Timeout.<anonymous> (F:\\Projects\\Blockchain\\node_modules\\request\\request.js:848:19)\n' +
' at listOnTimeout (internal/timers.js:554:17)\n' +
' at processTimers (internal/timers.js:497:7)'
}
} {
code: -32603,
message: 'ETIMEDOUT',
data: { originalError: { code: 'ETIMEDOUT', connect: true } },
stack: 'Error: ETIMEDOUT\n' +
' at Timeout.<anonymous> (F:\\Projects\\Blockchain\\node_modules\\request\\request.js:848:19)\n' +
' at listOnTimeout (internal/timers.js:554:17)\n' +
' at processTimers (internal/timers.js:497:7)'
}
Promise {
<rejected> {
code: -32603,
message: 'ETIMEDOUT',
data: { originalError: [Object] },
stack: 'Error: ETIMEDOUT\n' +
' at Timeout.<anonymous> (F:\\Projects\\Blockchain\\node_modules\\request\\request.js:848:19)\n' +
' at listOnTimeout (internal/timers.js:554:17)\n' +
' at processTimers (internal/timers.js:497:7)'
}
} {
code: -32603,
message: 'ETIMEDOUT',
data: { originalError: { code: 'ETIMEDOUT', connect: true } },
stack: 'Error: ETIMEDOUT\n' +
' at Timeout.<anonymous> (F:\\Projects\\Blockchain\\node_modules\\request\\request.js:848:19)\n' +
' at listOnTimeout (internal/timers.js:554:17)\n' +
' at processTimers (internal/timers.js:497:7)'
}
Promise {
<rejected> {
code: -32603,
message: 'ETIMEDOUT',
data: { originalError: [Object] },
stack: 'Error: ETIMEDOUT\n' +
' at Timeout.<anonymous> (F:\\Projects\\Blockchain\\node_modules\\request\\request.js:848:19)\n' +
' at listOnTimeout (internal/timers.js:554:17)\n' +
' at processTimers (internal/timers.js:497:7)'
}
} {
code: -32603,
message: 'ETIMEDOUT',
data: { originalError: { code: 'ETIMEDOUT', connect: true } },
stack: 'Error: ETIMEDOUT\n' +
' at Timeout.<anonymous> (F:\\Projects\\Blockchain\\node_modules\\request\\request.js:848:19)\n' +
' at listOnTimeout (internal/timers.js:554:17)\n' +
' at processTimers (internal/timers.js:497:7)'
}
Promise {
<rejected> {
code: -32603,
message: 'ETIMEDOUT',
data: { originalError: [Object] },
stack: 'Error: ETIMEDOUT\n' +
' at Timeout.<anonymous> (F:\\Projects\\Blockchain\\node_modules\\request\\request.js:848:19)\n' +
' at listOnTimeout (internal/timers.js:554:17)\n' +
' at processTimers (internal/timers.js:497:7)'
}
} {
code: -32603,
message: 'ETIMEDOUT',
data: { originalError: { code: 'ETIMEDOUT', connect: true } },
stack: 'Error: ETIMEDOUT\n' +
' at Timeout.<anonymous> (F:\\Projects\\Blockchain\\node_modules\\request\\request.js:848:19)\n' +
' at listOnTimeout (internal/timers.js:554:17)\n' +
' at processTimers (internal/timers.js:497:7)'
}
Promise {
<rejected> {
code: -32603,
message: 'ETIMEDOUT',
data: { originalError: [Object] },
stack: 'Error: ETIMEDOUT\n' +
' at Timeout.<anonymous> (F:\\Projects\\Blockchain\\node_modules\\request\\request.js:848:19)\n' +
' at listOnTimeout (internal/timers.js:554:17)\n' +
' at processTimers (internal/timers.js:497:7)'
}
} {
code: -32603,
message: 'ETIMEDOUT',
data: { originalError: { code: 'ETIMEDOUT', connect: true } },
stack: 'Error: ETIMEDOUT\n' +
' at Timeout.<anonymous> (F:\\Projects\\Blockchain\\node_modules\\request\\request.js:848:19)\n' +
' at listOnTimeout (internal/timers.js:554:17)\n' +
' at processTimers (internal/timers.js:497:7)'
}
Changing the provider configuration to use web sockets solved the problem.
provider: () => new HDWalletProvider(mnemonic, `wss://ropsten.infura.io/ws/v3/${infuraKey}`),
websockets: true
Issue
The command:
truffle migrate --network ropsten
doesn't deploy to the blockchain but prints all byte code and some JavaScript code to the screen with the following error message at the end.I don't have this error when I deploy locally or locally fork ropsten. This is deployment related error, the contract compilation phase completes without errors.
What could be the problem and how can I compile with "-s ASSERTIONS=1" to get more information?
Sample screen output.