miketrebilcock / js-pigpio Goto Github PK

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update dependency chai to v5
• chore(deps): update dependency eslint-config-airbnb-base to v15
• chore(deps): update dependency eslint-plugin-jsdoc to v48
• chore(deps): update dependency jsdoc to v4
• chore(deps): update dependency mocha to v10
• 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• chore(deps): update dependency codecov to v3.7.1 [security]
• chore(deps): update dependency semantic-release to v17 [security]
• chore(deps): update dependency eslint-plugin-import to v2.29.1
• chore(deps): update dependency eslint-config-node to v4
• chore(deps): update dependency mocha-eslint to v7

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency jsdoc to v3.6.11
• chore(deps): update dependency commitizen to v4
• chore(deps): update dependency cz-conventional-changelog to v3
• chore(deps): update dependency docdash to v2
• chore(deps): update dependency eslint to v8
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Hi,
I think in this line
https://github.com/i-am-digital/js-pigpio/blob/master/js-pigpio/_callback.js#L87
you mean
this._notify.remove(this._callback);
rather than notfy

thanks

Since the referenced version of 'put' has a few x86 binaries in it (for regression testing), this causes a hiccup in cross-compiling under buildroot. (It checks for proper architecture on your target)

Bump the dependency for 'put' to 0.0.7 to point to a revision that includes no pre-built binaries.

See: https://github.com/substack/node-put/issues/5

Hi the package.json says version
0.0.0-development
but npm (https://www.npmjs.com/package/js-pigpio) says
1.5.1 is the latest of 9 releases

should they not be consistent ?

I'm working on https://www.npmjs.com/package/node-red-node-pi-gpiod and found some issues regarding the Lock mechanism of this library.

Seems that something went wrong in acquireLock().
You are checking in Line 46 if the lock entry !== undefined what is ok for waiting if it is set, but it isn't set at startup, so the loop "content" will never be called. The result is that it never gets set.

I also ran into some problems with timeout() => was never called, so i used process.hrtime() instead.

Result would be something like:

const start = process.hrtime();

while (_LOCKS[this.host + ':' + this.port] !== undefined) {
    var diff = process.hrtime(start)[1] / (1000000 * 500);
        if (diff >= 1){
            break;
        }
}

if (_LOCKS[this.host + ':' + this.port] === undefined) {
    _LOCKS[this.host + ':' + this.port] = 'Locked';
} else {
    throw new Error('Can not acquire Lock');
}

But now i get errors because of the 2nd connection from _callback.js

So my question is how the lock was intended to work?

Hi, Can i use js-pigpio to access SPI,I2C device ?