Specify timeout on send methods

[ahmed-safari]

When device is not connected, send functions doesn't return until it is connected again. It waits for an infinite amount of time. Is there a way around this?

[smashah]

@Sp0derDev you might want to try safeMode. It checks the state before making a request to the browser instance

https://docs.openwa.dev/interfaces/configobject.html#safemode

[ahmed-safari]

I tried it, it still doesn't work most of the time. It keeps trying to send.

[smashah]

@github-actions run

⚡ Release! ⚡

```js (async () => { function exec(cmd) { console.log(execSync(cmd).toString()); } // Config const gitUserEmail = "github-actions[bot]@users.noreply.github.com"; const gitUserName = "github-actions[bot]"; exec(`echo "//registry.npmjs.org/:_authToken=$NPM_TOKEN" > .npmrc`); exec(`git config --global user.email "${gitUserEmail}"`); exec(`git config --global user.name "${gitUserName}"`); exec(`npm i`); exec(`npm run release-ci`); //comment on the issue var result = execSync(`npx auto-changelog -o ./tempchangelog.txt --commit-limit false --template ./compact-keepachangelog.hbs --stdout`).toString(); await postComment(result); //create changelog image exec(`npm run release-image`); exec(`git commit -a -m 'updated release-image'`); exec(`git push --force`); })(); ```

[ahmed-safari]

Thank you, do you mind helping with implementing a timeout ?

[smashah]

@Sp0derDev CI server got stuck on the release, going to try fixing then will explain how to do it

[smashah]

Changelog

🚀 Release 3.1.8 (2020-12-11)

• build(deps-dev): bump ava from 3.13.0 to 3.14.0 #1153
• build(deps-dev): bump husky from 4.3.0 to 4.3.5 #1155
• build(deps-dev): bump ts-node from 9.1.0 to 9.1.1 #1154
• build(deps): bump cfonts from 2.8.6 to 2.9.0 #1156
• build(deps): bump socket.io from 3.0.3 to 3.0.4 #1157
• build(deps): bump ini from 1.3.5 to 1.3.7 #1174
• build(deps-dev): bump @types/puppeteer from 5.4.1 to 5.4.2 #1163
• build(deps): [security] bump ini from 1.3.5 to 1.3.7 #1166
• build(deps-dev): bump @types/node from 14.14.10 to 14.14.12 #1169
• build(deps): bump swagger-ui-dist from 3.37.2 to 3.38.0 #1170
• build(deps-dev): bump marked from 1.2.5 to 1.2.6 #1171
• Release 3.1.8 034a9a7
• config: Implemented callTimeout #1152 1c11b16
• implemented: PageEvaluateionTimeout #1152 3a4a9c4
• chore: Improve forceRefocus() documentation f6b5ca8
• updated popup socket dependency to 3.0.4 a8b5f84
• Force update state in safeMode #1152 7617277

[smashah]

@Sp0derDev Ok. In the latest version (3.1.8) there are two major changes that will help you out.

1. safeMode now forces an update to the state of the connection. If it is connected, it will resolve quickly and result in CONNECTED and continue with the desired command. If there are issues with the connection between the device and the session then it will resolve in about 6 seconds and throw a confirmed TIMEOUT state message (or some other undesirable state).

2. You can now set callTimeout in the config (docs). This is the number of milliseconds the client method will wait before timing out. It will throw a PageEvaluateionTimeout error with a generic message. This should free up your process to continue doing other things. Just because you got this error, it does not mean that the desired command failed. It just means your process is no longer waiting for a response so please be careful when using this as some consecutive commands may rely on the resolved value.

I'm sure there will be some teething problems that will need further patches so please report with any feedback/issues. Or just report back if it is working as expected for you so I can close this issue.

Thanks

[smashah]

Closing for now, please report back if there are any further issues. Thanks