TRITON-1941: locker.js should be its own module

Details

Issue Type:New Feature
Priority:4 - Normal
Status:Resolved
Created at:2019-10-16T16:19:20.594Z
Updated at:2019-10-28T16:57:32.503Z

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-28T16:57:32.483Z)

Related Issues

Related Links

Labels

linuxcn

Description

locker.js has been copied around between repos, with varying levels of divergence.

The Linux CN port and ports to more modern versions of node will be simpler without a dependency on v8plus, which is needed by node-lockfd, which locker.js uses. In preparation for replacing node-lockfd with something more portable, locker.js should be turned into its own module. node-locker is already taken in the npm registry.

To avoid confusion, this will be called node-qlocker. The "q" is for the queue of pending locks maintained by the module. Bikeshedding welcome.

Comments

Comment by Jira Bot
Created at 2019-10-28T16:22:07.304Z

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

TRITON-1941 locker.js should be its own module (#1)


Comment by Former user
Created at 2019-10-28T16:57:32.499Z

Created node-qlocker, but not used anywhere yet.