# channel Published articles for channel. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Vercel for Slack now in public beta DevFeed: [Vercel for Slack now in public beta]() Original publisher: [Read original article]() Author: Shilpa Apte Published: 2026-08-19T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Slack](), [Vercel](), [Deployment](), [Pull Request](), [ci](), [Code](), [Authorization]() Tags: [agent](), [channel](), [ci](), [code](), [deployment](), [enterprise](), [logs](), [metrics](), [pricing](), [pull-requests](), [slack](), [vercel](), [work]() ### AI overview Vercel Agent is now available in Slack public beta for Pro and Enterprise teams. It can investigate deployment and runtime issues, help fix build and CI failures, review pull requests, and propose approved changes such as deployment rollbacks or configuration updates. The agent is read-only by default, respects requester permissions, requires approval for changes, and attributes actions to the agent, requester, and approver. ### Source excerpt Vercel Agent is now available in Slack. Mention @Vercel in any channel or thread, and Agent joins the conversation with relevant context from your Vercel projects, including deployments, builds, logs, metrics, configuration, and connected repos. For example, use it to: Investigate incidents: Ask why a deployment failed or what's causing a runtime error. It investigates and explains what it found. Write and review code: Work with your team and Agent to fix build and CI failures, review pull requests with production context, or turn a decision from the thread into a tested PR. Take action with approval: Tell it to make a change, such as rolling back a deployment or updating configuration. Agent drafts a plan and waits for your approval. Once approved, it gets temporary access to carry out the plan, then returns to read-only. Vercel Agent acts through its own identity. It's read-only by default, never exceeds the requester's permissions, and makes no changes without approval. Every action is attributed to Agent, the requester, and the approver. Vercel for Slack follows Vercel Agent pricing. During the beta, a limited number of simple requests are free. Paid work is billed on demand. The public beta is open to Pro and Enterprise teams. Install Agent for Slack from the Vercel Marketplace, read the docs, or see how we use it ourselves. Read more ## Multi-Core Fiber: Several Optical Cores Inside One Strand DevFeed: [Multi-Core Fiber: Several Optical Cores Inside One Strand]() Original publisher: [Read original article]() Author: j2sw Published: 2026-08-18T13:39:00Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [Hardware](), [Networks](), [interface]() Tags: [400g](), [cabling](), [channel](), [connectors](), [data-center](), [fiber](), [fiber-optics](), [internet-architecture](), [multi-core-fiber](), [network-engineering-resources](), [networks](), [optical-networking](), [optics](), [space-division-multiplexing](), [transmission]() ### AI overview This article explains how multi-core fiber places several optical cores inside one standard 125-micron cladding. It distinguishes MCF from high-fiber-count cable, describes aggregate capacity using separate channels and space-division multiplexing, and explains the need for specialized optical interfaces, connectors, splicing, and testing. ### Source excerpt Multi-core fiber places several independent optical cores inside one standard 125-micron cladding. It increases channel density, but it also requires different connectors, splicing methods, and testing procedures. The post Multi-Core Fiber: Several Optical Cores Inside One Strand appeared first on Justin Wilson (j2sw). ## Android Studio Rabbit 1 Canary 1 now available DevFeed: [Android Studio Rabbit 1 Canary 1 now available]() Original publisher: [Read original article]() Author: Android Studio Releaser (noreply@blogger.com) Published: 2026-08-17T14:06:36Z Content type: release Language: en Sources: [Android Studio Release Updates]() Topics: [Android Studio](), [Release notes](), [Android Gradle Plugin](), [bug]() Tags: [android-gradle-plugin](), [android-studio](), [bug](), [channel](), [compose](), [release](), [release-notes](), [screenshot-testing](), [update]() ### AI overview Android Studio Rabbit 1 Canary 1 is available in the Canary channel. The release includes general fixes for Android Studio, Android Gradle Plugin 9.5.0-alpha01, baseline profiles, Compose Preview Screenshot Testing, profilers, and other components. ### Source excerpt Android Studio Rabbit 1 Canary 1 is now available in the Canary channel. If you already have an Android Studio build on the Canary channel, you can get the update by clicking Help > Check for Updates (or Android Studio > Check for Updates on macOS). Otherwise, you can download it here. For information on new features and changes in Android Studio Rabbit 1, see the Android Studio Preview release notes. General fixes and features Below is a list of general fixes in Android Studio Rabbit 1 Canary 1 and Android Gradle Plugin 9.5.0-alpha01. These are a result of your bug reports, which help us to make Android Studio better. If you encounter a problem, let us know by reporting a bug. You can also vote for an existing issue to indicate that it also affects you. Fixed Issues Android Gradle Plugin Issue #533547933 Add a test that validate relocation does not affect task execution Baseline Profiles & ProfileInstaller Issue #543799367 Baseline profile is pulled off the device but never registered in test-result.pb, so collectBaselineProfile finds nothing and copyBaselineProfileIntoSrc deletes the committed profile Compose Preview Screenshot Testing Issue #538484834 Compose Preview Screenshot Testing (alpha15): renderer fails on all previews with IncompatibleClassChangeError: .R and .R$attr disagree on InnerClasses attribute Gemini Issue #540709807 S0 CRITICAL: Data Loss - AI Agent executed malformed shell command deleting drive contents Profilers Issue #347764600 TabbedToolbarTest.noCloseButtonWhenNoListener() broken ## iMessage support for eve agents DevFeed: [iMessage support for eve agents]() Original publisher: [Read original article]() Author: Owen Kephart Published: 2026-08-05T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Deployment]() Tags: [agents](), [channel](), [connectors](), [deployment](), [vercel]() ### AI overview Vercel announces iMessage support for eve agents through a new Photon channel. Each conversation stays in one eve session, incoming webhooks are verified, accepted messages are marked as read, and new messages can steer an in-progress reply. ### Source excerpt eve agents can now connect to iMessage through the new Photon channel. The channel keeps each iMessage conversation in one eve session, verifies incoming webhooks, and marks accepted messages as read. If more messages arrive while the agent is replying, they steer the in-progress reply instead of each getting a separate answer. The onMessage hook filters which messages the agent handles and adds context to a turn. Run eve add channel/photon-imessage to add the channel. iMessage delivery runs through Photon, so the command sets up a Photon project, registers your phone number, and scaffolds the channel: eve uses Vercel Connect to create the connector and configure Photon's webhook. On hosts without Connect support, choose Use portable credentials during setup and the channel reads its credentials from environment variables instead. Read the Photon channel docs to get started, or deploy an agent from a template. Read more ## ESP-IDF tutorial series: PWM DevFeed: [ESP-IDF tutorial series: PWM]() Original publisher: [Read original article]() Author: John Lee Published: 2026-08-03T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [Tutorial](), [Espressif](), [configuration]() Tags: [article](), [blog](), [channel](), [configuration](), [conversion](), [devkit](), [esp-idf](), [espressif](), [generate](), [ledc](), [peripheral](), [pwm](), [signal](), [speed](), [tutorial]() ### AI overview This ESP-IDF tutorial explains pulse-width modulation, including duty cycle, switching frequency, and average voltage. It demonstrates PWM generation with the LEDC peripheral on Espressif devices and describes converting PWM to DC with an RC filter, including ripple and response-speed tradeoffs. ### Source excerpt This article explains what a PWM signal is, and how to generate PWM signal using the ledc peripheral on Espressif devices. It covers the LEDC timer and channel configuration, and shows how to convert a PWM signal into a clean DC value using an RC filter, including the tradeoffs between ripple and response speed. ## Android Studio Quail 4 Canary 2 now available DevFeed: [Android Studio Quail 4 Canary 2 now available]() Original publisher: [Read original article]() Author: Android Studio Releaser (noreply@blogger.com) Published: 2026-07-23T14:08:38Z Content type: release Language: en Sources: [Android Studio Release Updates]() Topics: [Android Studio](), [releases](), [Release notes]() Tags: [android](), [android-studio](), [channel](), [download](), [macos](), [new-features](), [preview](), [release](), [release-notes](), [update]() ### AI overview Android Studio Quail 4 Canary 2 is available in the Canary channel. Existing Canary users can update through the IDE, while others can download it. The article links to preview release notes and closed issues for more details. ### Source excerpt Android Studio Quail 4 Canary 2 is now available in the Canary channel. If you already have an Android Studio build on the Canary channel, you can get the update by clicking Help > Check for Updates (or Android Studio > Check for Updates on macOS). Otherwise, you can download it here. For information on new features and changes in Android Studio Quail 4, see the Android Studio Preview release notes. For details of bugs fixed in each previous release of Android Studio Quail 4, see closed issues. ## Trino 483 introduces the PIVOT clause for SQL queries DevFeed: [Trino 483 introduces the PIVOT clause for SQL queries]() Original publisher: [Read original article]() Author: Martin Traverso Published: 2026-07-18T00:00:00Z Content type: release Language: en Sources: [Trino Blog]() Topics: [SQL]() Tags: [channel](), [feature](), [release](), [sql]() ### AI overview Trino 483 is presented as a release with larger SQL additions, led by the new PIVOT clause. The article explains that PIVOT turns categorical values into columns and supports one or more aggregations. ### Source excerpt Last month we called Trino 482 the summer of grammar release, because it closed so many small gaps in Trino's dialect of SQL at once. Those additions were mostly about breadth: a long list of standard predicates and forms, each a modest convenience on its own. Trino 483 keeps the season going, but the character is different. This release lands a handful of larger, more powerful additions instead of a dozen small gaps. They change the shape of the queries you write rather than just tidying them up. One of them, PIVOT, is big enough to carry the release on its own. As before, every example is live. Hit Run and watch Trino 483 evaluate it. ## How Discord Fans Out One Message to a Million Users DevFeed: [How Discord Fans Out One Message to a Million Users]() Original publisher: [Read original article]() Author: Nikki Siapno Published: 2026-07-07T13:22:26Z Content type: article Language: en Sources: [Level Up Coding System Design Newsletter]() Topics: [Discord](), [Publish-subscribe pattern](), [real-time](), [WebSocket](), [Back end](), [Processes](), [Authorization]() Tags: [backend](), [case-study](), [channel](), [discord](), [engineering](), [permission](), [real-time](), [scale](), [server](), [websocket]() ### AI overview This case study explains how Discord fans out a single message to many online users. It describes a real-time backend built around pub/sub, guild routing processes, permission checks, session processes, and WebSocket delivery. ### Source excerpt A case study in fanout, bottlenecks, and the engineering decisions behind Discord's scale. ## Chat SDK adds Novu support DevFeed: [Chat SDK adds Novu support]() Original publisher: [Read original article]() Author: Ben Sabic Published: 2026-06-22T14:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [SDKs](), [Command-line interface](), [Microsoft Teams](), [Slack]() Tags: [agent](), [bridge](), [channel](), [cli](), [documentation](), [identity](), [mapping](), [microsoft-teams](), [oauth](), [sdk](), [slack](), [support](), [telegram](), [tokens](), [whatsapp]() ### AI overview Chat SDK adds Novu support through a vendor-official adapter, allowing one handler set to connect agents to Slack, Microsoft Teams, WhatsApp, Telegram, and email. Novu manages credentials, identity, delivery, OAuth, and tokens, while a CLI command configures a channel and adds its credentials to the project. ### Source excerpt Chat SDK now supports Novu with the new vendor-official adapter. One handler set puts your agent on Slack, Microsoft Teams, WhatsApp, Telegram, and email. Novu handles credentials, identity, and delivery, keeping OAuth and tokens outside your app and mapping each channel to one user. Your agent always knows who they're talking to. Your agent can also send proactive notifications and handle the replies in the same loop, on whichever channel the customer used. One CLI command connects a real channel to your agent: It signs you in, creates a bridge agent, sets up the channel you pick (e.g., Slack), and adds the credentials to your project. Read the Novu documentation to get started. Read more ## Chat SDK adds AgentPhone support DevFeed: [Chat SDK adds AgentPhone support]() Original publisher: [Read original article]() Author: Vishal Yathish Published: 2026-06-01T14:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [SDKs](), [Bot](), [Chat Bot]() Tags: [building](), [channel](), [documentation](), [guide](), [learn](), [platforms](), [sdk](), [support](), [thread](), [voice]() ### AI overview Chat SDK adds a vendor-official AgentPhone adapter that lets bots handle voice calls and text messages using existing handlers. Calls and messages share one webhook and one conversation thread, preserving context across channels; call transcripts can be delivered as messages for responses through SMS or iMessage. ### Source excerpt Chat SDK now supports AgentPhone with the new vendor-official adapter. Give your bot its own phone number so it can handle voice calls and text messages using the same handlers you already write. When a call ends, the transcript is delivered as a message, allowing your bot to respond via SMS or iMessage. Calls and messages to the same number arrive via a single webhook, so you handle both from a single endpoint rather than a separate pipeline for each channel. They also land in one thread, so your bot maintains context throughout the conversation. Read the AgentPhone documentation to get started. Read more ## How Slack Uses a Three-Channel Context System for AI-Agent Security Investigations DevFeed: [How Slack Uses a Three-Channel Context System for AI-Agent Security Investigations]() Original publisher: [Read original article]() Author: Byte-Sized Design Published: 2026-05-08T07:42:17Z Content type: article Language: en Sources: [Byte-Sized Design]() Topics: [Slack](), [Artificial Intelligence](), [Security]() Tags: [agents](), [ai](), [ai-agents](), [channel](), [context](), [security](), [slack]() ### AI overview The article examines Slack's three-channel context system for a team of AI agents involved in security investigations. ### Source excerpt Inside the three-channel context system behind slack's security investigations ## What does using AI for post-mortems actually mean? DevFeed: [What does using AI for post-mortems actually mean?]() Original publisher: [Read original article]() Author: incident.io Published: 2026-04-23T14:29:00Z Content type: opinion Language: en Sources: [The incident.io Blog]() Topics: [Artificial Intelligence](), [Post Mortem](), [Incident response](), [incident](), [Compression](), [Slack]() Tags: [ai](), [channel](), [compression](), [docs](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [outage](), [post](), [post-mortem](), [slack](), [slack-incident](), [thread]() ### AI overview The article argues that AI can make post-mortems faster by gathering Slack threads, timelines, pull requests, and custom fields into a useful starting point. However, it warns that polished AI-generated documents can become useless if they replace the team's work of understanding what happened, why it happened, and what was learned. It distinguishes compression, which AI can automate effectively, from synthesis, which requires genuine human reasoning. ### Source excerpt Everyone is using AI to help with post-mortems now. We've built AI into our own post-mortem experience, pulling your Slack thread, timeline, PRs, and custom fields together and giving your team a meaningful starting point in seconds. But "AI for post-mortems" can mean very different things. Post-mortems are just one stage of the broader incident response lifecycle, and AI's role varies across all of it. ## Swiss Airlines' AI-Powered Support Chat Prevents Online Flight Rebooking DevFeed: [Swiss Airlines' AI-Powered Support Chat Prevents Online Flight Rebooking]() Original publisher: [Read original article]() Published: 2025-11-17T07:00:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Artificial Intelligence](), [Support](), [Website]() Tags: [ai](), [channel](), [chat](), [support](), [web]() ### AI overview The author argues that replacing airline support with AI can fail when the system does not work and website information is outdated. The article recounts an attempt to rebook a Swiss Airlines flight that was redirected from the website to an AI-powered online chat. ### Source excerpt Remember the vendor consultants who persuasively told you how to use their gear to build a disaster recovery solution with stretched VLANs, even though the only disaster recovery they ever experienced was the frantic attempt to restart their PowerPoint slide deck? Fortunately, I was only involved in the aftermath of their activity when the laws of physics reasserted themselves, and I helped the poor victims rearchitect their network into a somewhat saner state. There's another batch of snake-oil salesmen consultants peddling their warez to the gullible incompetent managers: the AI preachers promising reduction in support costs. Like the other group of consultants, they have never worked in support and have never implemented a working AI solution in their lives, but that never bothered them or their audience. Unfortunately, this time I had the unfortunate "privilege" of having the painful front-row seat. Read more ... ## Discord Update: November 6, 2025 Changelog DevFeed: [Discord Update: November 6, 2025 Changelog]() Original publisher: [Read original article]() Author: Clyde Published: 2025-11-06T00:00:00Z Content type: release Language: en Sources: [Discord Blog]() Topics: [changelog](), [Discord](), [App](), [Emoji](), [Mobile]() Tags: [2025](), [app](), [changelog](), [channel](), [chat](), [desktop](), [discord](), [features](), [images](), [improvements](), [mobile](), [new-features](), [search](), [shop](), [update](), [updates](), [voice]() ### AI overview The November 6, 2025 Discord Changelog describes desktop and mobile app improvements. Updates include easier emoji creation and upload, reorganized desktop settings with search, server voice-channel activity timers, per-server nameplates, mobile Shop purchases and gifts, and new Family Center features. ### Source excerpt Here's the Discord Changelog from November 6, 2025, so you can stay informed on what's new in recent app updates! ## Starting Your First Discord Server DevFeed: [Starting Your First Discord Server]() Original publisher: [Read original article]() Author: Cody Sanchez Published: 2025-08-27T00:00:00Z Content type: tutorial Language: en Sources: [Discord Blog]() Topics: [Discord](), [servers](), [browser](), [Template](), [web browser]() Tags: [app](), [browser](), [channel](), [discord](), [games](), [play](), [server](), [talk](), [voice]() ### AI overview A beginner-friendly guide to creating a Discord server, explaining how servers organize conversations and how to set one up for friends, gaming, and other shared interests. ### Source excerpt Looking to create a new Discord server for the first time? How do you invite your friends to it? What even IS a text or voice channel in Discord? Follow along as we help you start up a new place to talk and play games with your friends. ## Streaming with WebRTC and Mediasoup DevFeed: [Streaming with WebRTC and Mediasoup]() Original publisher: [Read original article]() Published: 2025-08-15T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's Blog]() Topics: [WebRTC](), [Streaming](), [real-time](), [servers](), [WebSocket](), [P2P]() Tags: [channel](), [http](), [server](), [streaming](), [video](), [webcam](), [webrtc](), [websockets]() ### AI overview This tutorial introduces Mediasoup, an open-source server-side WebRTC library that functions as a Selective Forwarding Unit (SFU). It explains SFUs alongside MCU and peer-to-peer alternatives, then outlines a basic producer-consumer setup in NodeJS using a server, a client, WebSockets, and webcam and audio streams. ### Source excerpt . [Streaming with WebRTC and Mediasoup](streaming-with-webrtc-and-mediasoup-cover... ## Scaling Trust Through Partnership: Introducing the Chainguard Partner Program DevFeed: [Scaling Trust Through Partnership: Introducing the Chainguard Partner Program]() Original publisher: [Read original article]() Published: 2025-08-13T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [Open Source](), [open-source-security]() Tags: [amazon](), [aws](), [azure](), [chainguard](), [channel](), [gcp](), [google](), [open-source](), [open-source-artifacts](), [open-source-software](), [partner](), [partnership](), [program]() ### AI overview Chainguard announces a global Partner Program designed to help channel partners deliver trusted open source software to customers. The program includes a two-tier structure, partner incentives, technical enablement, and joint go-to-market support. ### Source excerpt The Chainguard Partner Program is a global initiative to empower our channel partners to deliver trusted open source software to customers around the world. ## Using Clojure channels to increase throughput DevFeed: [Using Clojure channels to increase throughput]() Original publisher: [Read original article]() Author: Abhinav Dubey Published: 2025-05-28T10:07:12Z Content type: tutorial Language: en Sources: [Helpshift]() Topics: [Clojure](), [Concurrency](), [Kafka](), [benchmarking](), [async](), [Grafana]() Tags: [benchmarking](), [channel](), [clojure](), [concurrency](), [core-async](), [grafana](), [kafka](), [multithreading](), [parallelism]() ### AI overview This tutorial explains how to increase throughput in a Clojure-based Kafka consumer by using core.async channels and multiple worker threads. It compares a single-threaded baseline with configurations using three and ten workers, reporting shorter processing times for 1,000 events in the described benchmark. ### Source excerpt When building systems that process large volumes of messages synchronously, performance bottlenecks can quickly become a challenge specially with single-threaded designs. In this post, we'll look at how leveraging worker threads in a Clojure-based Kafka consumer can significantly boost throughput & reduce total processing time. Using simple concurrency primitives, it's possible to achieve parallelism & scale gracefully, all while keeping the codebase clean & maintainable. We'll start with a baseline, introduce worker threads using Clojure's core.async & measure the impact. Setup & Context Kafka & Zookeeper For observability: Grafana Kafka producer: A simple script that sends messages to a Kafka topic at a configurable rate (messages per minute) for a fixed duration. After each event is pushed, a counter metric is emitted Kafka consumer: A simple script that listens to a topic & consumes messages & simulates processing time finding square-root of a number (henceforth, assume that it takes ~1 second to find the square root) . A counter metric is emitted after processing each message The Baseline: Single-Threaded Consumer If each message takes t seconds to process & there are n messages, total processing time becomes n x t seconds. This provides a clean baseline to evaluate the impact of using channel moving forward. Adding workers with core.asyncValues are conveyed on queue-like channels. By default channels require producer and consumer to rendezvous for the transfer of a value through the channel https://clojuredocs.org/clojure.core.async To improve throughput, we introduce parallelism using Clojure's core.async channels. Messages from Kafka are fed into a channel, & multiple worker threads read from this channel to process messages concurrently Here, we used >!! (blocking put) & ) Original publisher: [Read original article]() Published: 2024-11-18T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [Android](), [Coroutines]() Tags: [android](), [channel](), [coroutines](), [kotlin](), [navigation](), [sharedflow](), [stateflow](), [toast](), [viewmodel](), [workshop-learning-programming]() ### AI overview This article compares StateFlow, SharedFlow, and Channel for representing events in an Android ViewModel. It explains why StateFlow can lose events, notes SharedFlow's behavior when no UI observer is present, and discusses using an unlimited-capacity Channel as an event queue. ### Source excerpt What is the best way to represent ViewModel events in Kotlin? ## Coroutine Testing - Never ending tests & backgroundScope DevFeed: [Coroutine Testing - Never ending tests & backgroundScope]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2024-08-30T07:00:45Z Content type: tutorial Language: en Sources: [Kaushik Gopal's Site]() Topics: [Coroutines](), [Unit testing](), [Kotlin](), [Testing](), [Android]() Tags: [android](), [channel](), [coroutine](), [coroutine-testing](), [coroutines](), [flow](), [job](), [kotlin](), [lifecycle](), [stateflow](), [testing](), [tests](), [unit-testing](), [viewmodel]() ### AI overview This tutorial explains why coroutine tests can time out when they collect from non-terminating Channels, SharedFlow, StateFlow, or ViewModel jobs. It presents manual Job cancellation and backgroundScope, which cancels child coroutines when the test body completes. ### Source excerpt series This is part of a series of posts on Coroutine Testing: Picking the right Dispatcher Never ending tests & backgroundscope <- Controlling time Helpful @Junit TestRule extension (coming soon) Full USF example for Android (coming soon) If you've spent some time testing Coroutines this exception should look familiar: After waiting for 1m, the test coroutine is not completing, there were active child jobs This tends to happen when you have a coroutine job in your test, that fails to complete on its own. Let's take a simple example. src on github We use a Channel here which is the proverbial event bus for Coroutines. source: kotlinlang.org Channels don't terminate on their own. So when you run a simple test checking the emission, while the items might get collected correctly per the assert statement in the test, the test itself fails like so: test on github The test here is waiting for that coroutine job to complete, which in turn requires the Channel to, but that never happens and the test times out. Where else would I run into this problem? # Channels aren't the only case you'll run into this problem. For example if you use a "hot" Flow like SharedFlow or StateFlow, they don't terminate on their own, so the onus is on you to complete or cancel their Job in tests. Android developers can frequently run into this problem too if you use ViewModels and have an internal StateFlow providing your "view level data" (what i personally like to call "view state"). You typically use the viewModelScope to launch internal coroutine jobs in a ViewModel. The OS then calls the lifecycle method onClear when the Activity or Fragment no longer needs the ViewModel where all jobs started in the viewModelScope are canceled. But when unit testing these ViewModels, you don't have access to the viewModelScope and shouldn't need it anyway. Solving this problem # There's two ways to solve this problem: 1. Manually cancel the Job ## If you have access to the Job that spawns the never-ending co ## Hacktoberfest 2023 with SvelteKit DevFeed: [Hacktoberfest 2023 with SvelteKit]() Original publisher: [Read original article]() Author: Willow (GHOST) & Braden Wiggins Published: 2023-10-01T00:00:00Z Content type: article Language: en Sources: [Svelte blog]() Topics: [coding](), [Open Source](), [Discord]() Tags: [channel](), [coding](), [community](), [contribute](), [developers](), [discord](), [documentation](), [event](), [getting-started](), [github](), [hacking](), [open-source]() ### AI overview SvelteKit announces its participation in Hacktoberfest, inviting developers to contribute to the open-source project. The article explains how to register, find suitable issues, coordinate contributions, and ask questions through Discord. ### Source excerpt Sveltekit ๐Ÿงก Hacktoberfest We're excited to announce SvelteKit's participation in this year's Hacktoberfest! Hacktoberfest is a global event that takes place every October, during which developers are encouraged to contribute to open-source projects like SvelteKit. The goal is to foster a vibrant open-source community, celebrate shared knowledge, and make the world of coding more accessible to all. You can find other participating repositories by searching the hacktoberfest topic on github. Getting Started The first step is to register for Hacktoberfest. Once you've registered, any PRs submitted to Sveltekit will count towards your participation in the event! Contributing If you need inspiration when looking for an issue to fix, check out the low hanging fruit, contributions-welcome, ready to implement, or documentation tags. It's a good idea to communicate clearly and often about what you're trying to solve or take on. You can do this by commenting on the issues you intend to take on. This helps avoid duplicate work and ensures that your contribution is in line with the project's goals. Nobody likes to have their work rejected, so it's best to ask questions early and often! Join our Discord and ask questions in the dedicated #hacktoberfest channel. We're happy to help you get started! We're excited to see what you've got in store for SvelteKit! Happy hacking! ๐ŸŽƒ ## React Canaries: Enabling Incremental Feature Rollout Outside Meta DevFeed: [React Canaries: Enabling Incremental Feature Rollout Outside Meta]() Original publisher: [Read original article]() Author: Dan Abramov, Sophie Alpert, Rick Hanlon, Sebastian Markbage, and Andrew Clark Published: 2023-05-03T00:00:00Z Content type: article Language: en Sources: [React Blog]() Topics: [React](), [Meta](), [Framework](), [releases](), [Open Source]() Tags: [canary-release](), [channel](), [feature](), [frameworks](), [incremental](), [meta](), [react]() ### AI overview React introduces an officially supported Canary release channel that allows the community and frameworks to adopt individual React features before stable releases. The channel is intended for features considered close to final and provides a supported path for incremental rollout outside Meta. ### Source excerpt We'd like to offer the React community an option to adopt individual new features as soon as their design is close to final, before they're released in a stable version--similar to how Meta has long used bleeding-edge versions of React internally. We are introducing a new officially supported [Canary release channel](/community/versioning-policy#canary-channel). It lets curated setups like frameworks decouple adoption of individual React features from the React release schedule. ## Marketing Attribution: Evaluating The Path to Purchase in the Product Ecosystem DevFeed: [Marketing Attribution: Evaluating The Path to Purchase in the Product Ecosystem]() Original publisher: [Read original article]() Author: Shelly Leal Senior Data Analyst Published: 2022-12-06T00:00:00Z Content type: tutorial Language: en Sources: [Trivago]() Topics: [data](), [App](), [Website](), [dashboards]() Tags: [article](), [behavior](), [business](), [channel](), [data](), [data-science](), [database](), [digital-marketing]() ### AI overview This article explains marketing attribution by modeling chronological user-event paths across product channels. It defines events, channels, paths, and attribution windows, then introduces common attribution models including last-touch attribution and discusses applying a multi-touch model to campaign activation in Business Studio. ### Source excerpt While working with data and analyzing the interactions of our users with the products we have today, it is essential to understand their behaviors by tracking their past actions, such as opening... ## 7 ways teams are using incident.io's Decision Flows DevFeed: [7 ways teams are using incident.io's Decision Flows]() Original publisher: [Read original article]() Author: Anna Debenham Published: 2022-10-24T00:00:00Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [incident](), [Slack](), [App](), [Template]() Tags: [app](), [breach](), [channel](), [data](), [feature](), [flow](), [guide](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [on-call](), [outage](), [post-mortem](), [reports](), [slack](), [slack-incident](), [support](), [third-party](), [workflows]() ### AI overview The article explains how incident.io's Decision Flows help teams make consistent decisions during incidents. Teams can use them to classify incident severity, guide triage and third-party-service checks, decide whether to update an external status page, and manage data-breach response. Decision Flows can be invoked in Slack or triggered automatically through Workflows while retaining a human decision-maker in the loop. ### Source excerpt Decision Flows are a lesser-known but powerful feature in incident.io that help teams resolve incidents faster. We've investigated how teams are using them today, such as to determine an incident's severity and guide engineers through common triage steps. [Next page]()