aboutsummaryrefslogtreecommitdiff
path: root/tools/schedule.js
AgeCommit message (Collapse)Author
2020-03-26infinite loop fixHolden Rohrer
2020-03-26fixed bug which has been making me tear my hair outHolden Rohrer
2020-02-23removed global variable pollutionHolden Rohrer
2020-02-12removed wacc as predictor for push cap in schedHolden Rohrer
2020-02-11no longer sends `undefined` char with job pad stepHolden Rohrer
2020-02-11no longer sends `undefined` char with job pad stepHolden Rohrer
2020-02-05schedule.js prevents off-by-one error by popping minimum amount in step 3Holden Rohrer
2020-02-05fixed a BIG bugHolden Rohrer
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)
2020-01-31proper mathematical fix in schedulerHolden Rohrer
2020-01-29fixed mathematical model in tools/schedHolden Rohrer
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.
2020-01-24fixed vulnerability in schedHolden Rohrer
This vulnerability permitted external users to overwrite the alert for long periods of time
2020-01-21two minor typo-like bugfixesHolden Rohrer
2020-01-20scheduler built for external accessHolden Rohrer
.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)
2020-01-20scheduler has .pause functionHolden Rohrer
2020-01-19uncaught typo I thought I fixedHolden Rohrer
2020-01-19schedule now rejects empty enqueuesHolden Rohrer
2020-01-18schedule had a glaring errorHolden Rohrer
2020-01-18Schedule bugfixHolden Rohrer
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
2020-01-18Implemented bug fix for maxr in schedule.jsHolden Rohrer
Rankings may have been messed up because as new insertions get added, the data.length changes per write.
2020-01-18queue-compat and bugfix in schedule.js---calls from jarvis still don't workHolden Rohrer
2020-01-17reorg comments in tools/schedule.jsHolden Rohrer
2020-01-17typo in tools/schedule.jsHolden Rohrer
2020-01-17removed extraneous writes var and added commentsHolden Rohrer
2020-01-17finally made schedule.jsHolden Rohrer