DirtyHairy/async-mutex

Issues

• Suggestion: Shared lock

  #81 opened 6 months ago by jlherren
  0

• The new priority feature is not documented for `Mutex.runExclusive()`, only `Semaphore.runExclusive()`

  #80 opened 6 months ago by NoahAndrews
  0

• Request: Priority Queue

  #73 opened 9 months ago by dmurvihill
  4

• Cancel specific pending lock

  #64 opened 2 years ago by AndreMaz
  5

• Semaphore with negative count (suggestion)

  #71 opened a year ago by mh-joneydi
  0

• Java ReentrantLock implementation (Suggestion)

  #70 opened 2 years ago by hdkrus
  0

• Cancel doesn't work as expected

  #67 opened 2 years ago by ivstiv
  1

• DELETE ME

  #69 opened 2 years ago by david-christ
  1

• Would it always be `locked` if we initialize the semaphore with a negative integer?

  #62 opened 2 years ago by AkatQuas
  1

• 0.4.0 not downloadable?

  #65 opened 2 years ago by JiriTrecak
  1

• 0.4 Changelog

  #61 opened 2 years ago by KilianB
  1

• Can `waitForUnlock` be affected by `withTimeout` decorator?

  #53 opened 2 years ago by CMCDragonkai
  3

• mutex.waitForUnlock() bug?

  #52 opened 2 years ago by ricardojosegomezulmke
  3

• Please don't deprecate release() function

  #50 opened 2 years ago by Aryk
  7

• Clarify in docs that the release function returned by acquire can be called multiple times

  #38 opened 2 years ago by ztane
  3

• Feature: increase semaphore's value

  #23 opened 2 years ago by Mavahu
  2

• Communicate value to waiting code

  #60 opened 2 years ago by cryptofomo1
  0

• TypeError: objMutex.waitForUnlock is not a function

  #58 opened 2 years ago by uranik777
  3

• what is the limit of thread safe queue limit of asyn-mutex module?

  #56 opened 3 years ago by rajendraspringer
  1

• Timing bug inside semaphore for `isLocked()`

  #54 opened 3 years ago by CMCDragonkai
  7

• Is there a way to implement a RWLock ontop of async-mutex?

  #48 opened 3 years ago by CMCDragonkai
  8

• Bug: Bad execution time for large number of calls on Mutex.runExclusive

  #51 opened 3 years ago by Zomono
  3

• Why can't I release a semaphore?

  #49 opened 3 years ago by adamburgess
  2

• Possible to have blocking version of isLocked?

  #46 opened 3 years ago by JasonGore
  0

• Race condition when using runExclusively

  #44 opened 3 years ago by trajano
  3

• Locking a specific value

  #42 opened 3 years ago by anton-johansson
  4

• withTimeout missing a clearTimeout

  #33 opened 4 years ago by cantoine
  2

• Types not compatible

  #32 opened 4 years ago by hasezoey
  1

• Question about Usage

  #25 opened 4 years ago by jenna-h
  2

• feat: add force release mode to release all held locks

  #19 opened 4 years ago by snowyu
  4

• Option to empty the queue?

  #28 opened 4 years ago by itayganor
  5

• Feature request: mutex.tryLock()

  #31 opened 4 years ago by marco-a
  2

• thank you!

  #30 opened 4 years ago by iambumblehead
  1

• Alternate release API seems broken

  #27 opened 4 years ago by jlherren
  1

• Mutex guarantees FIFO?

  #26 opened 4 years ago by mannharleen
  1

• Not work on express app

  #22 opened 4 years ago by tinytortoise-dev
  4

• NPM documentation improvement

  #20 opened 4 years ago by shasaur
  1

• Add lock by key

  #18 opened 4 years ago by gajus
  3

• Error: Package subpath './package.json' is not defined by "exports"

  #17 opened 4 years ago by malikbenkirane
  2

• Weird warning

  #14 opened 4 years ago by cristianoccazinsp
  7

• Different release lock interface

  #15 opened 4 years ago by moredrowsy
  2

• Optional acquire timeout?

  #9 opened 5 years ago by cristianoccazinsp
  5

• Add an ES module entrypoint

  #11 opened 5 years ago by rubys
  5

• Limit concurrency with Mutex?

  #12 opened 5 years ago by joerick
  6

• Using async mutex across NodeJS processes

  #10 opened 5 years ago by lucas-rudd
  1

• A small improvement

  #2 opened 8 years ago by ironbone
  4

• Wrong documantation

  #1 opened 8 years ago by ironbone
  1