Age | Commit message (Collapse) | Author |
|
So, this is pretty embarrassing, but I didn't realize that I was pushing the
entire stack whenever 0 chars were supposed to be pushed because I thought that
javascript's built-in functions were ok with negative zeros (stupid me)
|
|
|
|
Used to keep `num` the same and decrease the sum of weight, which created an error because the value of `num` was used in dequeuing job components. This patch prevents `dequeue()` from pushing more objects than it's actually able to.
|
|
This vulnerability permitted external users to overwrite the alert for long periods of time
|
|
|
|
.dequeue has been made available, along with an infinite delay-time so that a
secondary loop can manage multiple schedules at a time. This is paired with
.size to make the external loop more efficient (hopefully, baudrate is used
optimally)
|
|
|
|
|
|
|
|
|
|
It was adding too many prios to prios[] for the number of available jobs[] queues because they were added on every job insertion instead of on every new queue creation
|
|
Rankings may have been messed up because as new insertions get added, the data.length changes per write.
|
|
|
|
|
|
|
|
|
|
|