# handling Published articles for handling. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## SSH Key Handling using the macOS keychain and 1Password DevFeed: [SSH Key Handling using the macOS keychain and 1Password]() Original publisher: [Read original article]() Published: 2026-03-18T01:06:07Z Content type: tutorial Language: en Sources: [Signs of Triviality]() Topics: [macOS](), [ssh](), [configuration](), [client]() Tags: [client](), [configuration](), [handling](), [macos](), [ssh](), [using]() ### AI overview A brief tutorial on client-side configuration for handling SSH keys on macOS with the macOS keychain and 1Password. ### Source excerpt Just a few hints on client-side configuration options for handling SSH keys on macOS using the keychain and 1Password. ## Don't Lock the Screen Orientation! Handling Orientation in Compose DevFeed: [Don't Lock the Screen Orientation! Handling Orientation in Compose]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2024-07-22T04:29:54.355000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Compose](), [Android](), [android-apps](), [ui](), [configuration]() Tags: [android](), [compose](), [configuration](), [handling](), [layout](), [orientation](), [screen]() ### AI overview This tutorial explains why Android apps should generally support both portrait and landscape orientations, especially for accessibility and users who cannot rotate their devices. It focuses on Compose layout considerations, testing responsive layouts, and handling configuration changes caused by screen rotation. ### Source excerpt Yes, your app should work in both portrait and landscape modes - unless locked orientation is essential for functionality, like in a piano app. However, for most apps, locked orientation is not an option. Oh, and yes, the functionality should be similar in both modes, not hiding anything when the orientation changes. In this blog post, I'll cover the topic of locked orientation. It's mainly concentrated on Compose things, but there might be something useful for Views, too. I've also included some good articles in the Read More section of the blog post, explaining, e.g., more about orientation locking themes on Views. This blogpost was updated on 22nd of July to add example of using WindowWidthSizeClass. Why Locking Orientation is a Problem? When discussing locked orientation and its problems, we usually refer to locking the orientation to portrait mode. Unfortunately, this is a typical case among Android apps. Why is this a problem, then? Some people prefer to use their phones in landscape mode because it gives them more screen width. A wider screen can make it easier for people who use, e.g., larger font sizes of screen magnification. And some people might have their phones mounted on, e.g., a wheelchair in landscape mode, and can't rotate the phone at all. In these cases, if the app's orientation is locked in portrait mode, using the app might be more complicated or even impossible. That is not what any developer behind the apps wants, right? So, let's talk about how to support different orientations on your app. It's Straightforward From a purely UI point of view, supporting landscape mode is pretty straightforward. You just don't do anything - like prevent the screen rotation. This way, the landscape mode is available. Of course, you need to test that the layouts actually look okay in landscape orientation. With Compose, the layout mostly works if you don't use exact widths for different elements and don't have sticky items that take up some vertical space on th ## Handling Errors Gracefully in Craft CMS DevFeed: [Handling Errors Gracefully in Craft CMS]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2017-10-12T22:10:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Error Handling](), [Content Management System](), [Website](), [Development]() Tags: [cms](), [craft](), [debugging](), [error](), [error-handling](), [errors](), [guide](), [handle](), [handling](), [here-s](), [how-to](), [insights](), [it-s](), [matters](), [practical](), [website]() ### AI overview A practical guide to handling unexpected errors in Craft CMS websites through defensive programming, explicit error checks, null checks, user-friendly error handling, coding standards, and local devMode use. ### Source excerpt Every website can have errors, it's how you handle them that matters. Here's a practical error handling guide for Craft CMS. ## USB stack improvements GSoC - Week 8 DevFeed: [USB stack improvements GSoC - Week 8]() Original publisher: [Read original article]() Published: 2016-07-18T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [USB](), [Concurrency](), [implementation]() Tags: [controllers](), [free](), [gsoc](), [handling](), [implementation](), [improvements](), [mutex](), [open-source](), [os](), [react](), [reactos](), [safety](), [state](), [synchronization](), [usb](), [win32](), [winapi]() ### AI overview A week-eight GSoC progress report describes USB stack work in usbhub, including stability fixes, handling of removal and surprise-removal IRPs, synchronization of the FDO child list with a guarded mutex, and PnP state tracking. ### Source excerpt I have spent this week on improvements of realization and done stability fixes in usbhub PDO/FDO. I have prepared usbhub FDO's handling of removal and surprise-removal IRPs. We'll receive surprise-removal IRP on HUB unexpected removal, or on USB controller removal from PCI port. Here hub should "let know" all its children that their parent is removed and on next removal they also can be removed. For now this code path can't be tested because none of our host controllers can be removed now(they are failing query remove). ## Handling Asynchronism with Promises DevFeed: [Handling Asynchronism with Promises]() Original publisher: [Read original article]() Author: Chris Saylor (christopher.saylor@zumba.com) Published: 2013-11-06T00:00:00Z Content type: article Language: en Sources: [Zumba]() Topics: [async](), [Node.js](), [Library](), [MongoDB]() Tags: [async](), [blocking](), [handling](), [library](), [list](), [mongodb](), [node](), [node-js](), [using]() ### AI overview The article describes using the async library in Node.js to combine multiple MongoDB aggregation queries into one list without blocking the event queue. ### Source excerpt Using the async library in Node.js for combining multiple MongoDB aggregation queries into a single list without blocking the event queue.