Results for contextualize

LLM prompt/context preparation utility

contextual output encoding for xss defense and safe literal embedding, inspired by the owasp java encoder

CKB verification contextual

A Rust library for contextual multi-armed bandits

Utility crate to deal with data in context

This crate provides wrappers around contextualIdentities Web API

This crate provides WebAssembly bindings to contextualIdentities Web API

A widget library built for Bevy, in Bevy.

A simple library enabling contextual debugging

Type-level witness wrapper for carrying validated invariants.

Rewrite Debug output to replace long opaque values with short human-friendly aliases.

A client for generating embeddings and reranking with Voyage AI

Preserving contextual coherence among trace data from concurrent tasks

Add and remove behaviors defined in modules depending on context an object operates in

This is an experiment to try and make logging more flexible and more consumable. Plain text logs are bullshit, let's emit structured and contextual logs. Metrics, too!

Contextual global variables

Scoped and contextual method definition for use in writing more expressive DSLs without screwing defintions in other pieces of code

Context is a contextual UI framework. It is based on the Model View Presentor model. The idea is that you have model objects that represent the core data in your application. You also have views that represent the user interface input and output. Finally you have "contexts" that represent a user situation in the application. The logic that ties the models and views resides in the contexts. The main advantages to this model are that you can easily write UI unit tests and you can easily create bridge patterns for supporting multiple widget sets (although only GTK+ is supported at the moment). Context is intended to be extremely minimal. Only the top level abstract classes are included. It is *not* a widget set! You have to write your own models, views and contexts.

Online logging solution (like [Datadog](https://www.datadoghq.com)) have drastically transform the way we log. An app will nowdays logs dozen (hundred) of logs per requests. The issue is often to correlate this logs, with the initiating request (or job) and add shared metadata on this logs. Here come `ContextualizedLogs`. The main idea is to enhance your logs from your controller (including `ContextualizedController`, which use a before action), which will add the params to your logs (and some metadata about the request itself, like `request.uuid`). This metadata are stored in a `ActiveSupport::CurrentAttributes` which is a singleton (reset per request). Each subsequent logs in this thread (request) will also be enriched with this metadata, making it easier to find all the logs associated with a request (`uuid`, `ip`, `params.xxx`). On top of this, logs can also be enriched by the ActiveRecord model they use (`create` or `find`) (models including `ContextualizedModel`). So any time a contextualized model is created or find, some metadata related to the model (`id`, ...) will also be added to the logs. Allowing you to find all logs which "touched" this models.

A logger that silently collects information in the background and when an error is raised, logs a hash either out to the System or pushes the log to a service such as Loggly. The log hash contains information such as the backtrace, any logs from calling classes and methods, and configurable contextual information.

Contextual authorization for your Rails (3+) application

Logger that provides some control over how the log messages are being displayed with conditionally enable and disable certain log messages from showing based on configurations

Enable Guice-like dependency injection and contextual object interactions.

Wye provides users of ActiveRecord 3.2 with scopes and block methods for contextual execution of database queries on alternative database connections. Wye's patterns are most useful to applications making use of either replicated or federated databases.

No description provided.

No description provided.

No description provided.