Search Results for "what changed" - Page 2

Diffy is a traffic-shadowing and response-diffing tool that helps you validate a new version of a service against a trusted baseline before a full cutover. It acts as a proxy that fans out real production requests to three backends: the current “primary,” a “candidate” (new build), and a “shadow” baseline, then compares responses to detect behavioral differences. By using live traffic rather than synthetic tests, Diffy surfaces edge cases and data-dependent discrepancies that unit tests...

...It represents desired system state in a declarative model and coordinates agents to converge reality with that model, handling steps like install, start, verify, and promote. The system provides auditing and versioning of deployments, so operators can trace what changed, when, and why. A central console and APIs allow visualizing the topology, triggering rollouts, and performing controlled actions such as canaries and rolling updates. Under the hood it coordinates distributed nodes, tolerating partial failures while continuing to drive toward the target state. By separating deployment recipes from environment specifics, glu encourages repeatable, testable releases for multi-service stacks.

Version 1.1.5 - Added: Added the ability to edit the EMV panel - You can change which tags show, and what order they are in - Added: Tag 9F10 (Issuer Application Data) to which also includes CVR (a subtag of 9F10) - Added: Menu link to the homepage (sourceforge) - Fixed: 9F07/AUC had the wrong tag details - Fixed: File>Close now saves notes and config updates before exiting - Fixed: Tag 95/TVR title had a spelling mistake - Fixed: Homepage wasn't populating EMV page names - Fixed: EMV menu would prompt to update even if there was nothing changed - Changed: Removed unused classes, old stuff that isn't used - Changed: Reverted home page image - Changed: Removed some test prints and refactored EMV classes - Changed: No longer prompts to restart after EMV menu change, just changes it - Changed: EMV Navigation Panel button generation (for the dynamic buttons) thetoolbox2013@gmail.com

gvm is a version management tool for the Go programming language, inspired by tools like RVM (for Ruby). It allows you to manage, install, switch between, and uninstall multiple Go versions (including “tip” or weekly snapshots). It also supports “pkgsets” (similar to virtual environments) so you can maintain isolated sets of Go package dependencies associated with specific Go versions or projects. gvm caches cleaned source copies to speed up repeated installs and helps keep your Go workspace...

...I wanted to create an easily expandable tool for the GUI, that will automatically know how to display the various objects for editing. The goal was to make each object "know" how it should be displayed and changed, so that a simple GUI tool can display complex objects, and new objects can be created without having to spend time creating the "widgets" for them. The basic requirements was: - The "GuiObjects" don't know which graphical toolkit (e.g. gtk) will be used to display them. - The objects can be displayed without knowledge of what exactly they are...

...It offers both top-down (mock-based) and bottom-up testing styles, helps ease migration from clojure.test, and promotes graceful syntax for developer-friendly test expression. Midje has loaded the tests and run them for the first time. It's also watching for file changes. When it sees them, it loads the changed files and any dependencies. But notice that you still have a repl prompt. That means you can move rapidly and smoothly among typing at the repl to try out code samples or look up documentation, having your editor send code snippets to the repl to evaluate, and saving source or test files to immediately see what passes or fails.

Script to deploy svn changes to ftp. Deploy only changed files and check if current version are changed on server and ask what to do. Typical use 'sfdeploy d 4 HEAD': deploy svn changed file from version 4 to HEAD.

JDiff is a Javadoc doclet which emits an HTML report of all the packages, classes, methods, and so on, which are different (the "diff" part) when two Java APIs are compared. Great for reporting what has changed between two releases of your product.