Search Results for "back"

GenStage is a specification and set of behaviours for building demand-driven data pipelines on the BEAM. It formalizes the roles of producers, consumers, and producer-consumers, using back-pressure so that fast producers don’t overwhelm downstream stages. Developers implement callbacks like handle_demand and handle_events to control how items are emitted, transformed, and consumed across asynchronous boundaries. Because stages are OTP processes, you gain fault tolerance, supervised restarts, and concurrency tuned via configurable demand and partitioning. ...

...It mounts Svelte components from HEEx templates and wires props and events through a small interop layer, so data flows cleanly between LiveView assigns and Svelte state. The integration supports dispatching client events back to LiveView and pushing updates down to the component without writing custom glue for every case. This makes it straightforward to adopt Svelte for isolated, highly interactive widgets—charts, editors, complex form controls—without abandoning LiveView’s real-time model. The project aims to keep build tooling minimal and predictable, so teams can continue using familiar Phoenix asset pipelines. ...

...The core defines a clear lifecycle and callback API for elements, plus concepts like buffers, events, and capabilities/format negotiation to keep components interoperable and type-safe. Back-pressure, scheduling, and time synchronization are handled by the framework, enabling low-latency streaming and precise playback control without ad-hoc concurrency code. Developers compose pipelines from reusable building blocks and can dynamically add, remove, or switch elements while the system is running.

...Instead of maintainers repeatedly rebasing and merging one PR at a time, bors-ng batches r+-ed PRs, triggers your existing CI (e.g., GitHub Actions), and merges automatically when the batch is green. If a batch fails, it bisects the batch into smaller runs to isolate the culprit, landing the good PRs and kicking only the failing one(s) back for fixes. The bot is implemented as a GitHub App and works alongside—rather than replacing—your CI by reporting commit statuses/checks and acting on PR comments like bors r+ or bors try. It provides a dashboard to watch queue progress, uses separate staging/trying branches for merge/test cycles, and supports both public GitHub and GitHub Enterprise endpoints.

...Easy to deploy using the provided Docker images, Heroku (guide) or Distillery (guide). Can serve assets in production. Keeps stats about defined jobs and comes with a dashboard to monitor them (demo). Can apply exponential back-offs to failing jobs. Reloads code upon change in development. Kitto is a framework to help you create dashboards, written in Elixir / React. Widgets live in widgets/ are compiled using Webpack and are automatically loaded in the dashboards. Assets are rebuilt upon a change in development but have to be compiled for production.