# console Published articles for console. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Fedora 45 beta drags the Linux console into the 21st century (Register) DevFeed: [Fedora 45 beta drags the Linux console into the 21st century (Register)]() Original publisher: [Read original article]() Author: corbet Published: 2026-09-16T16:24:46Z Content type: news Language: en Sources: [LWN.net]() Topics: [Fedora](), [Linux](), [console](), [legacy](), [Terminal](), [Software]() Tags: [beta](), [console](), [development](), [legacy](), [linux](), [replacement](), [software](), [terminal]() ### AI overview The article reports that Fedora 45 beta replaces Linux's legacy in-kernel console with kmscon, a software-controlled userspace terminal emulator that has been in development for more than a decade. ### Source excerpt The Register looks forward to the upcoming Fedora 45 release. The biggest surprise is that Linux's legacy in-kernel console - the text-mode interface normally hidden beneath the GUI - has been replaced with a software-controlled alternative. The replacement is kmscon, a userspace terminal emulator that has been in development for more than a decade. ## Fedora 45 beta includes Kmscon improvements for GNOME 51 DevFeed: [Fedora 45 beta includes Kmscon improvements for GNOME 51]() Original publisher: [Read original article]() Author: Liam Proven Published: 2026-09-16T15:27:46Z Content type: article Language: en Sources: [www.theregister.com - Articles]() Topics: [Fedora](), [Linux](), [console]() Tags: [console](), [fedora](), [gnome](), [linux](), [red-hat](), [software]() ### AI overview The article discusses Fedora 45 beta and Kmscon improvements beneath GNOME 51, including smoother scaling, richer colors, and better Unicode support. ### Source excerpt Kmscon brings smooth scaling, richer colors, and better Unicode support beneath GNOME 51 ## New in Symfony 8.2: Console sub-commands DevFeed: [New in Symfony 8.2: Console sub-commands]() Original publisher: [Read original article]() Author: Javier Eguiluz Published: 2026-09-16T07:33:00Z Content type: release Language: en Sources: [Symfony Blog]() Topics: [Symfony](), [Command-line interface](), [Code]() Tags: [commands](), [compose](), [console](), [docker-compose](), [git](), [symfony]() ### AI overview Symfony 8.2 adds spaced console sub-commands, allowing command names to form a tree whose levels parse their own options. The update also supports tree-aware help, completion, argument handling, command-chain access, testing, and defining command trees in a single class. ### Source excerpt Symfony console applications group their commands with colon-separated namespaces, such as cache:clear or messenger:consume. Tools like Docker and Git use a different style: spaces separate the levels (docker compose up) and each level parses its own options.... ## How to Orchestrate Multi-Call Conversations with an LLM and Twilio Conversation in Node.js Memory DevFeed: [How to Orchestrate Multi-Call Conversations with an LLM and Twilio Conversation in Node.js Memory]() Original publisher: [Read original article]() Author: Amanda Lange, Dhruv Patel Published: 2026-09-14T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [Node.js](), [Large Language Model](), [Express](), [OpenAI](), [API](), [WebSocket](), [Machine learning]() Tags: [api](), [axios](), [console](), [developer-insights](), [environment-variables](), [express](), [how-to](), [http](), [ide](), [install](), [js](), [json](), [llm](), [ngrok](), [node-js](), [npm](), [openai](), [rest-api](), [sdk](), [visual-studio-code](), [web]() ### AI overview This tutorial shows how to build a Node.js Express service that uses Twilio Conversation Memory, OpenAI, and voice streams to preserve caller context, preferences, and action history across separate inbound calls. It covers project setup, package installation, local webhook exposure with ngrok, and access to Twilio's Conversation Memory REST API. ### Source excerpt Learn how to orchestrate multi-call voice conversations using Node.js, OpenAI, and Twilio Conversation Memory to persist caller context across separate calls. ## Introducing the Affiliates program DevFeed: [Introducing the Affiliates program]() Original publisher: [Read original article]() Author: Aishwari Pahwa Published: 2026-09-11T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Cloud]() Tags: [account](), [analytics](), [announcements](), [cloud](), [console](), [developers](), [program](), [upgrade]() ### AI overview Appwrite introduces an Affiliates program that lets developers create invite links, track referrals, and earn $15 in Appwrite Cloud organization credits when referred users upgrade to Pro. The program includes 180-day attribution and is managed in the Appwrite account and Console. ### Source excerpt Introducing the Affiliates program, a new way to share Appwrite, track referrals, and earn Cloud credits when people you refer upgrade to Pro. ## Emulator control for adaptive app development DevFeed: [Emulator control for adaptive app development]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-31T16:00:00Z Content type: tutorial Language: en Sources: [Android Developers Blog]() Topics: [Android](), [Emulator](), [Command-line interface](), [Large Screen](), [Android Studio](), [Terminal](), [Development]() Tags: [adaptive](), [adb](), [android](), [android-studio](), [app-development](), [command-line](), [commands](), [console](), [development](), [devices](), [emulator](), [layout](), [verify](), [workflow]() ### AI overview A tutorial on using Android Emulator console commands through adb emu to test adaptive app behavior. It covers folding and unfolding devices, rotating them, simulating physical postures, and resizing displays from the terminal. ### Source excerpt Posted by Rob Orgiu, Developer Relations Engineer, Adaptive Apps, Android Adaptive app development is fundamental on Android, but making sure everything looks good and every feature works the way it should require multiple tests on multiple devices. Or does it? Well, yes... and no! While Android Studio is bundled with the Resizable Emulator to let you test layouts manually, there's a faster, more streamlined way to control form factors directly from your terminal. By leveraging fire-and-forget console commands using the adb emu shortcut, you can execute commands that immediately return control to your invoking shell. If you have multiple emulators running at the same time, you can target a specific virtual device by passing in the shortcut's serial: adb -s emu First things first: Fold and unfold To test foldable-specific user journeys and layout configurations, you can fold and unfold your emulated device programmatically. adb emu fold If your foldable emulator is unfolded, you can fold it to display its smaller screen configuration, powering on the (virtual) external display. To unfold the emulator and power on the internal display, simply run: adb emu unfold Now, you can instantly verify that your app preserves its state and that layouts appear exactly as they should on different display sizes. Rotation, rotation, rotation Correctly handling orientation changes is a cornerstone of adaptive app development. You can trigger device rotations programmatically to test how well your app handles configuration changes, including state restoration. The following command rotates the device 90Β° clockwise: adb emu rotate Simulating postures using sensors What about placing the emulator into a specific physical posture, like tabletop mode? The easiest approach is querying for the number of available positions with . First, list all available sensors and their current status: adb emu posture This returns a list of positions similar to the following: ## Custom MFA factor: send a second factor through any channel DevFeed: [Custom MFA factor: send a second factor through any channel]() Original publisher: [Read original article]() Author: Atharva Deosthale Published: 2026-08-14T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [MFA](), [Authentication](), [API](), [Node.js](), [Rust]() Tags: [announcements](), [api](), [authentication](), [backend](), [console](), [mfa](), [node](), [rust](), [security](), [voice](), [whatsapp]() ### AI overview Appwrite introduces a custom MFA factor that generates and verifies authentication codes while allowing applications to deliver them through channels such as WhatsApp, voice calls, or internal providers. The article explains how to retrieve the code through a server-side function and deliver it securely. ### Source excerpt Appwrite now supports a custom MFA factor. Appwrite generates and verifies the code, and your function delivers it through WhatsApp, a voice call, or any provider you choose. ## Pulumi Introduces Notification Center for Pulumi Cloud DevFeed: [Pulumi Introduces Notification Center for Pulumi Cloud]() Original publisher: [Read original article]() Author: Tom King Published: 2026-08-11T00:00:00Z Content type: release Language: en Sources: [Pulumi]() Topics: [Cloud]() Tags: [console](), [email](), [esc](), [features](), [github](), [notifications](), [organization](), [product](), [pulumi](), [pulumi-cloud](), [pulumi-neo](), [real-time](), [review](), [slack]() ### AI overview Pulumi introduces Notification Center, an inbox in the Pulumi Cloud console for task completions, approval requests, and billing alerts. Notifications appear in real time, link directly to the required action, and can be delivered in the console or by email with per-type preferences. ### Source excerpt Plenty happens in a Pulumi organization while you're looking somewhere else. Neo finishes a task you kicked off just before taking lunch. A teammate submits an ESC change request that needs your approval before it can land. Until now, catching any of that meant either keeping the right tab open or hoping the right email reached you. Today we're introducing the Notification Center: a single inbox in the Pulumi Cloud console for the things that actually need you. It lives behind the bell in the sidebar, with a dot when something's waiting. Notifications arrive in real time -- no refresh -- and each one carries exactly one action: Review request, View task, Update billing. Click it and you land on the page where you can do the thing, not on a dashboard where you have to go find it. What you'll hear about We've started with the moments where being a few minutes late actually costs you something: a Neo task that's paused waiting on your approval, a Neo task that's finished, an ESC change request waiting on your sign-off, and billing conditions like a locked organization or a trial that's about to end. Relevant people in your organization will be notified when there's a pending approval, or billing alert. Nobody gets paged for someone else's work. Where you'll hear about it Every notification type can be delivered two ways -- in the console and over email -- and you choose per type, per channel. Organization admins set a sensible baseline for everyone; each person can override it for themselves on their account settings page. What's next The Notification Center is available today. We're starting with this set of notifications and expanding from there. If there's an event you'd rather hear about from the bell than from a colleague on Slack, we'd like to know which one. Join our Community Slack to connect with the Pulumi team and other users, or open an issue on our GitHub repository. ## Introducing Document360's New API Documentation Experience DevFeed: [Introducing Document360's New API Documentation Experience]() Original publisher: [Read original article]() Author: Darshan Sureshkumar Published: 2026-08-07T13:29:10Z Content type: release Language: en Sources: [Knowledge Management Tips, Best Practices and More]() Topics: [API](), [Documentation](), [console](), [Authentication](), [ChatGPT](), [Claude]() Tags: [api](), [api-documentation](), [authentication](), [chatgpt](), [claude](), [console](), [developers](), [documentation](), [interactive](), [product-update](), [release](), [update]() ### AI overview Document360 introduces a redesigned API Reference with a three-pane layout, an interactive Try It! Console, reusable session variables, in-console authentication, and endpoint questions through Eddy AI. The release also expands Global Find & Replace across reusable content and knowledge base elements, and adds documentation-to-ChatGPT or Claude workflows. ### Source excerpt Developers expect API references they can experiment with instantly. Documentation teams need faster ... The post Introducing Document360's New API Documentation Experience appeared first on Document360. ## Building an OpenCode Companion with ESP-BLE-UART and ESP-VoCat DevFeed: [Building an OpenCode Companion with ESP-BLE-UART and ESP-VoCat]() Original publisher: [Read original article]() Author: John Lee Published: 2026-07-14T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Tutorial](), [AI Agent](), [ESP32](), [ESP32-S3](), [Embedded Software Dev](), [Internet of things](), [Hardware]() Tags: [ai-agent](), [blog](), [bluetooth](), [bluetooth-le](), [console](), [esp-idf](), [esp-iot-solution](), [esp-vocat](), [esp32](), [esp32-s3](), [firmware](), [opencode](), [tutorial]() ### AI overview This tutorial explains how to build a physical OpenCode companion with ESP-VoCat. It uses ESP-BLE-UART to send session status and permission prompts to an ESP32-S3 device, whose screen and button support status display and approval or rejection decisions. ### Source excerpt This article shows how to build a physical OpenCode companion with ESP-VoCat. The device displays session status and permission prompts, then sends one-button approval or rejection decisions over BLE UART. ## Metal Default, A New Build Cloud, And A New Format DevFeed: [Metal Default, A New Build Cloud, And A New Format]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-05-29T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [iOS](), [Cloud](), [dashboards](), [GPU](), [ui]() Tags: [cloud](), [console](), [format](), [gpu](), [ios](), [release]() ### AI overview This release post announces that Metal is now the default renderer for iOS builds, the new Build Cloud console is linked from site dashboards, and weekly release posts will use a shorter index format with separate follow-up articles. ### Source excerpt The iOS Metal renderer is now the default, the new Build Cloud console is wired into every Dashboard link on the site, and the weekly release blog is moving to a shorter format with deeper follow-up posts during the week. ## Introducing Fulfillment Dashboard: New artifact requests are now self-serve DevFeed: [Introducing Fulfillment Dashboard: New artifact requests are now self-serve]() Original publisher: [Read original article]() Published: 2026-02-12T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [dashboards](), [chainguard containers](), [chainguard](), [Containers](), [Development]() Tags: [chainguard](), [chainguard-containers](), [chainguard-factory](), [chainguard-images](), [console](), [customers](), [fulfillment-dashboard](), [real-time](), [scale](), [search](), [secure-software](), [self-service](), [self-service-container-images](), [visibility](), [workflows]() ### AI overview Chainguard introduces Fulfillment Dashboard, a self-service console for submitting, tracking, searching, and voting on secure container image requests. It provides lifecycle visibility, target delivery dates, deduplication, and community upvoting to help prioritize fulfillment. ### Source excerpt Fulfillment Dashboard gives Chainguard customers real-time visibility, tracking, and community voting for new secure container image requests. ## Introducing the Spend by Date Range Billing View DevFeed: [Introducing the Spend by Date Range Billing View]() Original publisher: [Read original article]() Author: Rebecca Davis Published: 2025-12-16T21:27:44Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [Digital Ocean](), [Cloud](), [Finance](), [Optimization](), [API](), [CSV]() Tags: [api](), [billing](), [cloud](), [console](), [cost-optimization](), [digitalocean](), [download](), [reporting]() ### AI overview DigitalOcean introduces a custom date range billing view that lets customers analyze cloud spending over specific periods, with daily, weekly, and monthly breakdowns by product. The feature is available globally through the Billing Console, Cloud Console, and API, with CSV report downloads. ### Source excerpt If you've ever stared at an unexpected cloud bill spike and sifted through invoices trying to find the cause, you know how time-consuming cost investigations can be. Until now, identifying cost anomalies often meant waiting for your monthly invoice or manually calculating month-to-date usage. That changes today. All DigitalOcean customers now have access to the new custom date range billing view. This new feature is accessible in the Billing Console by going to Billing -> Insights. Additionally, you can download your report as a CSV so you can view your granular billing insights offline. What's included in this new feature This update gives you clearer, more granular visibility into your cloud costs (segmented into daily, weekly, and monthly spend by product) making budgeting and forecasting far easier. DevOps, Finance, and growing teams can now manage spend proactively instead of reacting after the fact. For all customers, this feature is available globally and fully self-service via the Cloud Console and API. Here is a close look into the features of this new billing view: Custom date range filtering: You are no longer limited to invoices for viewing your spending. Choose any start and end date to view total spend for that exact range. This makes it easy to align cloud costs with development sprints, project timelines, or product launches-and improves internal chargebacks and budgeting accuracy. Daily spend breakdown: Daily granularity is key for surfacing anomalies. Instead of a single aggregated number, you can see how your spend changes day by day. If a deployment three weeks ago caused a spike, you can pinpoint the exact day and correlate it with logs to find the root cause quickly. Cost by product breakdown: See exactly where your money is going with a breakdown of spend across services such as: Droplets Databases Spaces Bandwidth Financial adjustments at a glance: For organization-level reporting, the total costs now clearly include financial adjustments like ## Achieving Fine-Grained Admin Permissions with Keycloak 26.2 DevFeed: [Achieving Fine-Grained Admin Permissions with Keycloak 26.2]() Original publisher: [Read original article]() Author: Vlasta Ramik Published: 2025-05-14T00:00:00Z Content type: tutorial Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Authorization](), [Access Control](), [audit](), [Security](), [console]() Tags: [access-control](), [admin](), [administration](), [audit](), [authorization](), [console](), [idm](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [policies](), [saml](), [scopes](), [security](), [sso]() ### AI overview This article introduces Fine-Grained Admin Permissions V2 in Keycloak 26.2. It explains how FGAP V2 supports delegated administration and more granular management of users, clients, groups, and roles within a realm, with centralized permission management in the Admin Console. ### Source excerpt For years, Role-Based Access Control (RBAC) has been the cornerstone of authorization in many applications. Assigning users to roles provides a simple and effective way to manage access for common use cases. However, as applications become more complex and security requirements more demanding, RBAC alone often falls short. Keycloak is leveling up administrative access control with the release of Fine Grained Admin Permissions V2 a major step towards introducing delegated administration to Keycloak so that server administrators can assign management privileges to other users in a realm. By doing that, you should be able to reduce management costs and effort, and improve the overall efficiency and security of your deployments by authorizing access to specific resources in a realm. Why Fine-Grained Admin Permissions (FGAP) V2? In previous Keycloak versions, administrative access was largely driven by broad roles such as realm-admin or manage-users. While effective for simple setups, these roles often granted more access than necessary and lacked clarity around which actions they allowed. FGAP V2 introduces a cleaner, more deliberate permission model that enables: Granular access control over users, clients, groups, and roles Clear boundaries between operations--no more implicit permissions Easier management of the permissions and policies Better evaluation mechanism to allow authorization administrators audit the model ✨ Key Highlights 🧭 Centralized Permissions Management A new Permissions section in the Admin Console provides a single place to view and manage all fine-grained permissions for a realm. This simplifies navigation and makes it easier to design and audit your permission model. πŸ” Improved Manageability and Evaluation Permissions are now easier to discover, filter, and evaluate. You can inspect which scopes are assigned to which identities--making it more transparent and manageable to build tailored administrative roles. 🎯 Resource-Specific and Global Permissi ## Get started with Firebase using Free Trial credits DevFeed: [Get started with Firebase using Free Trial credits]() Original publisher: [Read original article]() Author: Andrew Peynado; Rachel Saunders Published: 2024-11-04T00:00:00Z Content type: tutorial Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [Cloud](), [Google](), [Google Cloud Platform (GCP)](), [App](), [Development]() Tags: [billing](), [card](), [cloud](), [console](), [develop](), [firebase](), [free](), [full-stack-development](), [google-cloud](), [guide](), [how-to](), [onboarding](), [pricing](), [tutorials](), [upgrade]() ### AI overview This tutorial explains how to claim $300 in Google Cloud Free Trial credits and link the billing account to a Firebase project. The credits last 90 days, require a payment method for billing setup and identity verification, and do not incur charges unless the account is upgraded to a paid account. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Installing NetBSD on Linode DevFeed: [Installing NetBSD on Linode]() Original publisher: [Read original article]() Published: 2024-09-14T19:29:01Z Content type: tutorial Language: en Sources: [Signs of Triviality]() Topics: [Linode](), [Command-line interface]() Tags: [command](), [command-line](), [console](), [how-to](), [install](), [linode]() ### AI overview A tutorial explaining how to install NetBSD on a Linode instance using the command line and serial console. ### Source excerpt Instructions on how to install NetBSD on a Linode instance. All steps are performed via the command-line and serial console. ## Text-UI View backend DevFeed: [Text-UI View backend]() Original publisher: [Read original article]() Author: Nenad Rakocevic (noreply@blogger.com) Published: 2024-06-11T14:02:00Z Content type: release Language: en Sources: [Red]() Topics: [Text-based user interface](), [User Interfaces](), [Red](), [Command-line interface](), [Linux](), [macOS]() Tags: [cli](), [console](), [examples](), [features](), [linux](), [macos](), [ui](), [user-interfaces]() ### AI overview Red/View now includes a usable, though incomplete, text-based user interface backend. The article outlines its supported widgets, drawing commands, keyboard and optional mouse handling, colors, timers, facets, platforms, configuration, and usage examples. ### Source excerpt Last year, qtxie worked on a toy text backend project and submitted a PR for that. After some extra additions and testing recently, it has now been merged even if it is still incomplete, it is usable enough. So, in addition to the shiny GUI backends in Red/View, now we have an old-school text-based user interfaces (TUI) backend for the View engine! The new TUI backend has currently a subset of the GUI backends features. Here is an overview: View styles: base, panel, button, check, radio, field, text, progress, rich-text, image and text-list. Draw commands: text, line, box, triangle, circle, ellipse (block-based for now). Rich-text supported in Draw. Keyboard handling: key-down and key events (which are the same event). Mouse handling: disabled by default. Use system/view/platform/mouse-event?: yes to enable it. Images support Truecolor (24-bit RGB) for image rendering if the terminal supports it, otherwise it falls back to 256 colors. Timers supported through /rate facet. Facets supported: /offset, /size, /text, /image, /color, /data, /enabled?, /visible?, /selected, /flags, /options, /pane, /rate, /para and /draw. Flags supported: password and all-over. Frames drawing using squared or rounded corners ( Limited ANSI escape codes support in /text facet, only Colors / Graphics Mode codes. Uses 256 colors for text. It should works fine on most of the terminals. Works on the big-3 platforms (Linux, macOS and Windows10/11). The pre-built CLI console binaries on our Download page now have View/VID included by default along with the TUI backend. You can use them to test and play with the TUI code examples here and in the TUI folder. To use the TUI backend in your own compiled code, you need to add the two following options in the Red header block: Needs: 'View Config: [GUI-engine: 'terminal] Here are a few examples, starting with a HelloWorld!: view [text "Hello TUI World!"] Hello TUI World! When view is invoked, an event loop is launched. In order to return back to the co ## Developer essentials: JavaScript console methods DevFeed: [Developer essentials: JavaScript console methods]() Original publisher: [Read original article]() Author: brian-smith Published: 2023-11-30T00:00:00Z Content type: article Language: en Sources: [MDN Blog]() Topics: [JavaScript](), [Web Development](), [debug](), [Logging](), [dev-tools]() Tags: [browser](), [code](), [console](), [debug](), [developer](), [developer-tools](), [development](), [display](), [examples](), [firefox](), [javascript](), [learn](), [logging](), [logs](), [production](), [tool](), [web-development]() ### AI overview A practical guide to JavaScript console methods for displaying information, checking whether code works, exploring browser capabilities, and organizing logs by level. It introduces common and lesser-known methods with examples that readers can try in their browser console. ### Source excerpt The JavaScript console is an essential tool for web development. Learn new and fun ways to use the console to display data and debug your code. ## Simple colorful logging in Node.js DevFeed: [Simple colorful logging in Node.js]() Original publisher: [Read original article]() Author: Stanko Published: 2023-04-08T00:00:00Z Content type: tutorial Language: en Sources: [Stanko TadiΔ‡]() Topics: [Node.js](), [Terminal](), [Logging](), [color](), [console](), [Script](), [ASCII]() Tags: [ansi](), [ascii](), [color](), [commands](), [console](), [logging](), [node-js](), [script](), [terminal]() ### AI overview A tutorial showing how to create simple colorful console logs in Node.js with ANSI escape codes, including a small reusable script, recommendations for picocolors and Chalk, and a browser-console alternative using CSS. ### Source excerpt When writing Node.js scripts, I often want to output information to the console in different colors. Usually, it is to get the user's attention and signalize success or error. I could reach for a battle-tested library like Chalk, but I usually don't need all of its features. Instead, I have a tiny script I copy from project to project: const reset = "\x1b[0m"; const log = { green: (text) => console.log("\x1b[32m" + text + reset), red: (text) => console.log("\x1b[31m" + text + reset), blue: (text) => console.log("\x1b[34m" + text + reset), yellow: (text) => console.log("\x1b[33m" + text + reset), }; Then, I can easily log things in color: log.green("This seems like a very successful message"); log.red("Something might have gone wrong"); log.blue("I'm here to inform you of something"); log.yellow("Lemon πŸ‹"); Once executed, it looks like this: How it works # The script uses something called ANSI escape codes. It is a way to give commands to a terminal by passing sequences of bytes, usually starting with an ASCII escape character \x1b. They are mostly used to move the cursor and to change the color or styling of the text. They are standardized, and they should work on any platform. For example, \x1b[31m is an escape sequence that tells our terminal to switch color to red. All text after it will be red, until we pass the reset sequence \x1b[0m, which will revert text to the default color. More robust version # If you need more features, I suggest using an existing library. I usually recommend picking one of these two: picocolors - when I need more robust but still lightweight library Chalk - when I need a fully featured coloring library Browser # As a bonus, let's see how we can use color in a browser's console. Escape sequences are not going to work, but we can actually use CSS. console.log("%cπŸ‹ Lemon", "background: black; color: yellow;"); Everything after %c will be styled using CSS defined in the parameter after it. Open the console in your browser and click on the b ## Writing a Debugger From Scratch - DbgRs Part 2 - Register State and Stepping DevFeed: [Writing a Debugger From Scratch - DbgRs Part 2 - Register State and Stepping]() Original publisher: [Read original article]() Author: Tim Misiak Published: 2023-03-06T16:44:39Z Content type: tutorial Language: en Sources: [TimDbg]() Topics: [debug](), [Processes](), [Windows](), [Code](), [Parsing](), [Rust](), [GitHub]() Tags: [code](), [commands](), [console](), [context](), [debugger](), [error-handling](), [execution](), [github](), [input](), [parsing](), [state](), [windows]() ### AI overview Part 2 of a tutorial on building a debugger from scratch in Rust for Windows. It adds a console command interface, input parsing, register-state reading through GetThreadContext, and basic execution control such as stepping and continuing. ### Source excerpt When we left off last time, we had a basic "debugger" that could launch a Windows process and monitor events that occur in that process, but it's not yet something that you would really call a debugger. Two things that are missing are the ability to examine the state of the process and to control its execution. So that's what we're going to build next. The code for this part is on GitHub as the part2 branch. ## Ruby Delights Built Into The Language DevFeed: [Ruby Delights Built Into The Language]() Original publisher: [Read original article]() Author: Doximity Published: 2022-12-20T16:00:00Z Content type: article Language: en Sources: [Doximity]() Topics: [Ruby](), [Benchmark](), [benchmarking](), [Code](), [Terminal]() Tags: [benchmark](), [benchmarking](), [code](), [console](), [performance](), [ruby](), [terminal]() ### AI overview This article explores Ruby features and examples built into the language and its standard library. It focuses on the Benchmark module, Ruby's IRB benchmarking extension, and other example programs such as a biorhythm calculator and networking utilities. ### Source excerpt BTW, we're ⚑ hiring Infra, SRE, Web, Mobile, and Data engineers at Doximity (see roles) -- find out more about our technical stack. Ruby Delights Built Into The Language The hidden gems that make Ruby a delight are not always... gems. There are so many Ruby features built in to the language itself. In the very first episode of this series, we dove deep into the internals of one such gem bundled with Ruby's standard library: IRB. Keeping on theme, I'd like to take some time to explore some other areas of Ruby's source. So get ready to open up that IRB console you read all about, and we'll explore some incredible Ruby examples provided to you by Ruby itself. Jump To Your Favorites benchmark.rb - Measure performance of Ruby code biorhythm.rb - A biorhythm calculator cal.rb - A simple calendar display cbreak.rb - Supress echo of terminal input using ioctl cgi-session-pstore.rb - A file-based persistence mechanism for tracking the CGI Session as a Hash clnt.rb, svr.rb and tsvr.rb - Start a TCP socket server and connect a client coverage.rb - Simple test code coverage delegate.rb - Delegating methods with ease dir.rb - Directory access DRb - Distributed object system for Ruby (think RPC for OO) dualstack-fetch.rb and dualstack-httpd.rb - A simultaneous multi-threaded IPv4/IPv6 TCP server and client eval.rb - A simple evaluator export.rb - method access example exyacc.rb - Extract BNF from the yacc file fact.rb - A factorial calculator fib.rb - Fibonacci number calculations from.rb - Scan mail spool fullpath.rb - Convert ls -lR to fullpath format iseq_loader.rb - A sample of compiler/loader for binary compiled file less.rb - A front-end for the less command Benchmark source: benchmark.rb Benchmarking can be an incredibly valuable tool, but is quite the rabbit hole of theory vs. pragmatism. The "what", and "how", of benchmarking is fraught with sharp opinions and inconsistent recommendations. For now, we'll throw all that out the window and focus on Ruby's lovely example us ## Apache Airflow 2.5.0 Released with Dataset UI, DAG Testing, and Task Log Improvements DevFeed: [Apache Airflow 2.5.0 Released with Dataset UI, DAG Testing, and Task Log Improvements]() Original publisher: [Read original article]() Author: Apache Airflow Published: 2022-12-02T00:00:00Z Content type: release Language: en Sources: [Apache Airflow Blog]() Topics: [airflow](), [releases](), [dataset](), [debug](), [Docker Image]() Tags: [airflow](), [apache-airflow](), [console](), [dataset](), [debug](), [docker-image](), [release](), [release-notes](), [releases]() ### AI overview Apache Airflow 2.5.0 introduces usability improvements to the Datasets UI, a faster and easier-to-debug airflow dags test command, automatic task-log tailing in Grid view, and further improvements to Dynamic Task Mapping. The release also marks a shorter release cadence than previously used. ### Source excerpt Apache Airflow 2.5 has just been released, barely two and a half months after 2.4! Details: πŸ“¦ PyPI: https://pypi.org/project/apache-airflow/2.5.0/ πŸ“š Docs: https://airflow.apache.org/docs/apache-airflow/2.5.0/ πŸ›  Release Notes: https://airflow.apache.org/docs/apache-airflow/2.5.0/release_notes.html 🐳 Docker Image: docker pull apache/airflow:2.5.0 🚏 Constraints: https://github.com/apache/airflow/tree/constraints-2.5.0 This quicker release cadence is a departure from our previous habit of releasing every five-to-seven months and was a deliberate effort to listen to you, our users, and get the changes and improvements into your workflows earlier. Usability improvements to the Datasets UI When we released Dataset aware scheduling in September we knew that the tools we gave to manage the Datasets were very much a Minimum Viable Product, and in the last two months the committers and contributors have been hard at work at making the UI much more usable when it comes to Datasets. But we aren't done yet - keep an eye out for more improvements coming over the next couple of releases too. Greatly improved airflow dags test command This airflow subcommand has been rethought and re-optimized to make it much easier to test your DAGs locally - the major changes are: a. Task logs are visible right there in the console, instead of hidden away inside the task log files b. It is about an order of magnitude quicker to run the tasks than before (i.e. it gets to running the task code so much quicker) c. Everything runs in one process, so you can put a breakpoint in your IDE, and configure it to run airflow dags test then debug code! Auto tailing task logs in the Grid view Hopefully the headline says enough. It's lovely, go check it out. More improvements to Dynamic-Task mapping In a similar vein to the improvements to the Dataset (UI), we have continued to iterate on and improve the feature we first added in Airflow 2.3, Dynamic Task Mapping, and 2.5 includes dozens of improvement ## Tips and tricks for reversing foreign architecture games DevFeed: [Tips and tricks for reversing foreign architecture games]() Original publisher: [Read original article]() Published: 2022-09-23T00:00:00Z Content type: tutorial Language: en Sources: [mahaloz.re]() Topics: [ctf](), [Tooling](), [console](), [Hacking](), [Software](), [Assembly]() Tags: [console](), [ctf](), [file](), [game-hacking](), [games](), [reversing](), [tooling]() ### AI overview This tutorial presents techniques for reversing software built for unfamiliar architectures, using an 0CTF22 game-hacking challenge involving a Vectrex console and Motorola 6809 architecture as its example. ### Source excerpt Some common techniques used while reversing unknown architectures seen through the lens of an 80's game hacking challenge from 0CTF22 ## New Red binaries DevFeed: [New Red binaries]() Original publisher: [Read original article]() Author: Nenad Rakocevic (noreply@blogger.com) Published: 2022-07-29T16:18:00Z Content type: release Language: en Sources: [Red]() Topics: [Red](), [toolchain](), [Command-line interface](), [GUI](), [Compiler](), [releases]() Tags: [availability](), [binaries](), [cli](), [compiler](), [console](), [download](), [gui](), [releases]() ### AI overview Red introduces separate pre-built binaries for its GUI console, CLI console, and toolchain to reduce first-use delays. The project is temporarily dropping semantic versioning before version 1.0 and will primarily provide binaries for the latest commit. ### Source excerpt Since many years, we are offering pre-built binaries for the Red toolchain, as a more convenient way to use Red, even if it is not strictly needed, as Red can be run from its sources, the toolchain being run by a Rebol2 interpreter. As the Red REPL and toolchain are not run by the same engine, the console (REPL) used to be compiled on first run of the `red` executable (when no arguments was provided or a Red script was passed). This resulted in a significant delay on the first use of the console (both for the GUI and CLI versions). We have now decided to change that by providing separate pre-built binaries for the consoles and toolchain. This is a temporary split until Red gets self-hosted, at which point we can recombine everything into a single binary. Another change is the temporary dropping of the semantic versioning until version 1.0 and related "stable" releases, as it seems to be too confusing to some users (Red being still in alpha stage). This also will remove a tendency from some users to care more about version increments than feature availability and work being done overall. We will now be proposing only pre-built binaries for latest commit, though older binaries will still be available if that can be of any help to anyone. So the pre-built binaries now are: Red GUI : Red interpreter + View + GUI console Red CLI : Red interpreter + CLI console Red Toolchain : Encapper for Red + Red/System compiler We are also considering ways to merge the GUI and CLI consoles into a single binary which can work even if no GUI API is available, falling back on CLI mode. We will also have the console(s) act as a front-end for the toolchain, even downloading it for you in the background when needed. Though for that we need a proper asynchronous `call` function implementation. More news about this soon. In the meantime, enjoy running Red consoles almost instantly from just a click on the Download page! [Next page]()