# @autoschedule/queries-scheduler > Queries scheduler Latest version **3.2.3** (published 2018-07-06) · MIT license · 0 weekly downloads ## Install ```sh npm install @autoschedule/queries-scheduler pnpm add @autoschedule/queries-scheduler yarn add @autoschedule/queries-scheduler bun add @autoschedule/queries-scheduler ``` ## Health **Score 30/100 (F)** — status: abandoned. Positive: has types; esm support; no vulnerabilities; high quality score. Warnings: low downloads. Negative: abandoned; low maintenance score. ## Facts | | | |---|---| | Version | 3.2.3 | | Published | 2018-07-06 | | First published | 2017-12-01 | | Weekly downloads | 0 | | License | MIT | | TypeScript types | bundled | | Module format | ESM + CommonJS | | Dependencies | 5 | | Unpacked size | 98.1 KB | | Known vulnerabilities | 0 | | Install scripts | no | | GitHub stars | 0 | | Maintainers | draeken | | Keywords | scheduler, autoschedule | ## Links - npm: https://www.npmjs.com/package/@autoschedule/queries-scheduler - Repository: https://github.com/AutoScheduleJS/queries-scheduler - Homepage: https://github.com/AutoScheduleJS/queries-scheduler#readme - Issues: https://github.com/AutoScheduleJS/queries-scheduler/issues - npm.io page: https://npm.io/package/@autoschedule/queries-scheduler ## Dependencies (5) - [rxjs](https://npm.io/package/rxjs.md) ^6.2.1 - [ramda](https://npm.io/package/ramda.md) ^0.25.0 - [moment](https://npm.io/package/moment.md) ^2.22.2 - [intervals-fn](https://npm.io/package/intervals-fn.md) ^3.0.2 - [@autoschedule/queries-fn](https://npm.io/package/@autoschedule/queries-fn.md) ^6.2.1 ## Recent versions - 3.2.3 (latest) — 2018-07-06 - 1.0.7 (dev) — 2017-12-09 - 3.2.2 — 2018-06-27 - 3.2.1 — 2018-03-23 - 3.2.0 — 2018-03-20 - 3.1.5 — 2018-03-16 - 3.1.4 — 2018-03-14 - 3.1.3 — 2018-03-09 - 3.1.2 — 2018-02-22 - 3.1.1 — 2018-02-19 - 3.1.0 — 2018-02-08 - 3.0.1 — 2018-02-07 - 3.0.0 — 2018-01-25 - 2.3.0 — 2018-01-24 - 2.2.0 — 2018-01-24 - … 12 more at https://npm.io/package/@autoschedule/queries-scheduler/versions ## README # Queries Scheduler > Place queries on a timeline. [![Build Status](https://travis-ci.org/AutoScheduleJS/queries-scheduler.svg?branch=master)](https://travis-ci.org/AutoScheduleJS/queries-scheduler) [![Maintainability](https://api.codeclimate.com/v1/badges/0a18d9fdd27919e0c45f/maintainability)](https://codeclimate.com/github/AutoScheduleJS/queries-scheduler/maintainability) [![Test Coverage](https://api.codeclimate.com/v1/badges/0a18d9fdd27919e0c45f/test_coverage)](https://codeclimate.com/github/AutoScheduleJS/queries-scheduler/test_coverage) [![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier) [![semantic-release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg?style=flat-square)](https://github.com/semantic-release/semantic-release) [![Commitizen friendly](https://img.shields.io/badge/commitizen-friendly-brightgreen.svg)](http://commitizen.github.io/cz-cli/) [![Greenkeeper badge](https://badges.greenkeeper.io/AutoScheduleJS/queries-scheduler.svg)](https://greenkeeper.io/) [![npm version](https://badge.fury.io/js/%40autoschedule%2Fqueries-scheduler.svg)](https://badge.fury.io/js/%40autoschedule%2Fqueries-scheduler) workflow: queries -> schedule needs: - once material is placed, don't replace it. Causes loops. Temporary query instead. (Current behavior is different: potentials and materials streams are re-compute after each mutation and we check for stability. Cause issue: updatePP isn't accurate. Stick to first strategy) operations: - place potentials with most pressure. - When all possible queries are placed and some potentials are left, throw exception. New provider query is pushed (send needer id so provider query can have a direct dependency). Can now be placed thanks to user state potential. - Temp Queries: fixes from agent feedback, placeholder, content with transforms. - two ways to provide: provider depends on needed task; needed task depends on provider. - tasks with zero potential have pressure of -1 instead of +Infinity. - task potential = intersection of query potential (internal constraints) + query dependencies + user state potential + materials. - impossible to place (material time) => throw exception. (conflict) - query that occurs x time before/after state: Link to material that update state -> link field, queries-scheduler module. - How to allow link to a material from another agent ? Could be after the second phase, when agent receive queries's context. (Link to an ID) - Only one exception is permitted: conflict error that needs user. Others are caught (from userstate) with conflict-resolver - providers handle is complex. Use priority list. Can cause side-effect conflict. How to go back to the source of conflict ? How to switch from 1st priority to another ? Simulation with satisfaction threshold for all materials ? heavy cost (recursive and exponential, due to provider sub-dependance to other providers). - Agents -> queries ; conflict-resolver (error): query -> agent ; manage agents as a stream when the stream complete without error, it should be the final timeline. schedule (tasks (materials)): - tasks (potentials) tasks (potentials): - queries - tasks (potentials) - tasks (materials) - user state (potentials) - user state (materials) tasks with needs: - tasks (materials) - agent service Stream: 1. agent queries 2. user interaction 3. [1, 2] queries 4. [3, 5] queries with temp 5. [4, 5, 7] tasks (potential) - use user-state function on tasks (potential & material) 7. [5] tasks (material) 9. [7] needs and fixes, placeholder fill or validate a. Catch errors from [7] => generate new queries at [1]. Module: [1] queries-fn [2, 3] main app [4, 5, 7] queries-scheduler userstate-manager [a] conflic-resolver [b] agent-relay Module a: if provider is impossible to place, either there is no need for it, or there is a conflict. Use user-state to determine. userstate-manager: query + (potential/material) with needs + config + base needs => ranges of possibilities Queries restrictions: - provider (insert/update with 'wait: true' can't specify start/end) -> will prevent correct material placement order. --- _Source: https://npm.io/package/@autoschedule/queries-scheduler · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._