TRITON-1942: node-qlocker should not use node-lockfd

Details

Issue Type:New Feature
Priority:4 - Normal
Status:Resolved
Created at:2019-10-16T16:30:49.931Z
Updated at:2019-10-30T11:53:56.568Z

People

Created by:Former user
Reported by:Former user
Assigned to:Former user

Resolution

Fixed: A fix for this issue is checked into the tree and tested.
(Resolution Date: 2019-10-30T11:53:56.550Z)

Related Issues

Related Links

Labels

linuxcn

Description

node-qlocker (aka locker.js) uses node-lockfd. node-lockfd brings in v8plus, which complicates ports to newer versions of node and ports to operating systems that are not derived from Solaris. node-fs-ext also provides fcntl-based file locking without the v8plus baggage.

Comments

Comment by Jira Bot
Created at 2019-10-30T11:52:52.240Z

node-qlocker commit ec3c5323e4070fa83b39508f7199efab4e6d055b (branch master, by Mike Gerdts)

TRITON-1942 node-qlocker should not use node-lockfd (#2)


Comment by Former user
Created at 2019-10-30T11:53:56.566Z

Fixed in https://github.com/joyent/node-qlocker/commit/ec3c5323e4070fa83b39508f7199efab4e6d055b via https://github.com/joyent/node-qlocker/pull/2