# error Published articles for error. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## A Simple MVI Architecture Approach Using LiveData DevFeed: [A Simple MVI Architecture Approach Using LiveData]() Original publisher: [Read original article]() Author: dustin@dustn.dev (Dustin Summers) Published: 2026-09-17T04:13:15.404035Z Content type: opinion Language: en Sources: [Dustin Summers]() Topics: [Android](), [Dagger]() Tags: [architecture](), [architecture-pattern](), [error](), [livedata](), [loading](), [mvi]() ### AI overview A talk from Android Summit 2019 discusses a simple implementation of the MVI architecture pattern using LiveData and the Loading, Content, Error pattern. ### Source excerpt This was a talk provided by myself and Dan Lowe at Android Summit, 2019. In this we discuss a simple approach to the MVI (Model, View, Intent) Architecture Pattern using LiveData and the common Loading, Content, Error Pattern. Link to Dan's blog post is here which is what our talk was based around. ## \[$\] Stabilizing Rust's never type DevFeed: [\[$\] Stabilizing Rust's never type]() Original publisher: [Read original article]() Author: daroc Published: 2026-09-08T13:34:38Z Content type: article Language: en Sources: [LWN.net]() Topics: [Rust](), [Compiler](), [Code](), [function]() Tags: [change](), [code](), [compiler](), [error](), [function](), [maintainers](), [optimize](), [rust]() ### AI overview The article explains Rust's never type, denoted by "!", and reports that it was stabilized after more than two years of work. It discusses the feature's practical benefits for optimizing generic code and its role in type inference, while noting a small breaking change to previous Rust editions. ### Source excerpt A function's return type is supposed to indicate the kind of data that it produces. Rust's "never" type, which is denoted by an exclamation mark ("!"), is the type the language uses to mark a function that never returns and other places where a value can never occur. For a long time, the never type was used internally by the compiler, but was considered an unstable feature. On August 24, after more than two years of work, Rust-compiler-contributor "waffle" finally managed to stabilize the type. It took so long, in part, because it involved a small breaking change to previous Rust editions, which the compiler maintainers needed to ensure did not impact much real code. ## Keep business processes moving by recovering failed steps without restarting DevFeed: [Keep business processes moving by recovering failed steps without restarting]() Original publisher: [Read original article]() Author: Tao Guo Published: 2026-05-11T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Orchestration](), [Processes](), [retry]() Tags: [data](), [error](), [execution](), [state](), [temporal-concepts](), [workflows]() ### AI overview The article explains how to recover failed steps in durable business processes without restarting completed work. It presents a Temporal pattern in which workflows pause on permanent failures, accept corrections from humans or automated agents, and resume from the point of failure. ### Source excerpt Stop restarting broken business processes. See how Temporal Workflows pause on bad data, accept fixes via Signals, and resume without losing progress. ## Why your platform control plane belongs on Temporal DevFeed: [Why your platform control plane belongs on Temporal]() Original publisher: [Read original article]() Author: Joshua Smith Published: 2026-03-31T00:00:00Z Content type: opinion Language: en Sources: [Temporal Blog]() Topics: [control-plane](), [Automation](), [Orchestration](), [Terraform]() Tags: [automation](), [control-plane](), [error](), [infrastructure](), [orchestration](), [platform](), [platform-teams](), [provisioning](), [scripts](), [self-service](), [temporal-voices]() ### AI overview This article argues that Temporal can serve as a durable backbone for platform teams building internal control planes. It describes the difficulty of managing infrastructure across creation, monitoring, upgrades, configuration changes, and decommissioning, and contrasts Temporal's orchestration model with Terraform's declarative provisioning and reconciliation focus. ### Source excerpt Discover why platform teams use Temporal to build resilient internal control planes. Learn how Durable Execution solves brittle infrastructure automation. ## How to fix osm2pgrouting error 'relation "\_\_waysXXXX" does not exist' and speed up the import DevFeed: [How to fix osm2pgrouting error 'relation "\_\_waysXXXX" does not exist' and speed up the import]() Original publisher: [Read original article]() Author: Robin Wilson Published: 2026-01-31T10:33:00Z Content type: tutorial Language: en Sources: [Robin Wilson]() Topics: [import](), [Database](), [Command-line interface](), [Cloud]() Tags: [cloud](), [command-line](), [database](), [error](), [gis](), [how-to](), [import](), [postgres](), [speed]() ### AI overview A practical guide to fixing an osm2pgrouting error involving a missing __waysXXXX relation while importing OpenStreetMap data into PostGIS. It explains that increasing the command's chunk-size parameter can prevent crashes and reduce the import time to about 45 minutes, while requiring substantial RAM. ### Source excerpt I don't seem to have time or energy for long posts these days, but here's another quick post which might save you some time and frustration. Recently, I've been trying to import OpenStreetMap data into a PostGIS database to use with pgRouting. I wanted to import data for the whole of England - which has [...] ## Configurar Fail2Ban para proteger servicios DevFeed: [Configurar Fail2Ban para proteger servicios]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-01-28T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Fail2ban](), [OpenSSH](), [nginx](), [Debian](), [Ubuntu](), [rhel 9]() Tags: [debian](), [error](), [fail2ban](), [internet](), [ip](), [login](), [logs](), [nginx](), [rhel](), [rhel-9](), [ssh](), [ubuntu]() ### AI overview A practical guide to installing and configuring Fail2Ban to protect SSH, Nginx, and other services from brute-force attacks. It covers jail configuration, custom Nginx filters, nftables and iptables actions, status checks, and manually unbanning IP addresses. ### Source excerpt Guía práctica para instalar y configurar Fail2Ban: protege SSH, Nginx y otros servicios contra ataques de fuerza bruta. ## Fix "This video format is not supported" on YouTube TV DevFeed: [Fix "This video format is not supported" on YouTube TV]() Original publisher: [Read original article]() Author: David Walsh Published: 2025-11-17T23:47:34Z Content type: tutorial Language: en Sources: [David Walsh]() Topics: [browser](), [web browser]() Tags: [browser](), [drm](), [error](), [uncategorized]() ### AI overview A troubleshooting guide explains how to resolve YouTube TV's "This video format is not supported" error by enabling Widevine DRM in the browser settings and restarting the browser. ### Source excerpt Setting up a new computer is bliss -- no old, unused apps and the machine performs much better than the previous. Unfortunately, you may encounter new problems based on the new hardware. One such issue I encountered with my new MacBook was a "This video format is not supported" message when I went to YouTube [...] The post Fix "This video format is not supported" on YouTube TV appeared first on David Walsh Blog. ## Announcing a new operation: Workflow Update DevFeed: [Announcing a new operation: Workflow Update]() Original publisher: [Read original article]() Author: Dan Davison Published: 2025-01-14T00:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [async](), [reliability](), [Low Latency]() Tags: [announce](), [async](), [asynchronous](), [blog](), [blog-post](), [design-patterns](), [error](), [product-news](), [reliability](), [update](), [workflow]() ### AI overview Temporal announces that Workflow Update is generally available. The operation lets clients send a message to a Workflow, wait for handling to complete, and receive a result or error. The article explains how Update differs from Queries and Signals, demonstrates executing Activities, and discusses validators and design patterns. ### Source excerpt Discover the latest workflow update designed to simplify operations and boost reliability in Temporal. ## How do I unzip multiple / many files under Linux? DevFeed: [How do I unzip multiple / many files under Linux?]() Original publisher: [Read original article]() Author: Vivek Gite Published: 2024-09-27T19:56:29Z Content type: tutorial Language: en Sources: [nixCraft: Linux Tips, Hacks, Tutorials, And Ideas In Blog Format (RSS/FEED)]() Topics: [Linux](), [Zip](), [Bash](), [Command-line interface](), [Scripting, bash](), [Shell](), [file]() Tags: [bash](), [command-line](), [easy](), [error](), [files](), [how-to](), [images-directory](), [linux](), [shell](), [suse](), [unix](), [wild](), [zip]() ### AI overview A tutorial explains how to extract multiple ZIP archives on Linux and Unix-like systems. It covers why `unzip *.zip` can fail when the shell expands the wildcard, quoting or escaping the wildcard, Bash loops, and a `find`-based method for filenames containing spaces or unusual characters. ### Source excerpt I have lots of files in a directory called /disk2/images/. All files are in zip file format, so I am using the following command to extract zip files: unzip *.zip The command result into an error which read as follows: caution: filename not matched How do I unzip multiple or many zip files under a Linux/Unix-like system? Love this? sudo share_on: Twitter - Facebook - LinkedIn - Whatsapp - Reddit The post How do I unzip multiple / many files under Linux? appeared first on nixCraft. ## Fixing Git's "Cannot rebase onto multiple branches" error DevFeed: [Fixing Git's "Cannot rebase onto multiple branches" error]() Original publisher: [Read original article]() Author: Tom Published: 2024-05-27T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Git](), [Code review]() Tags: [bash](), [best-practices](), [devops](), [error](), [git](), [linux](), [macos](), [review]() ### AI overview A tutorial on resolving Git's "Cannot rebase onto multiple branches" error when using git pull --rebase. It explains the error as Git being unable to determine which branch to rebase onto and recommends configuring a specific default branch. ### Source excerpt A Guide to using git pull --rebase effectively Using git pull --rebase as your default merge strategy offers several benefits, particularly in maintaining a clean and linear commit history, which can simplify collaboration and code review. However, you may occasionally encounter the error "Cannot rebase onto multiple branches". This article explains why this happens and provides a solution to make git pull --rebase work seamlessly. Benefits of git pull --rebase Linear History: Rebasing applies your local commits on top of the upstream changes, creating a straight line of commits without unnecessary merge commits. This makes the project history easier to read and understand. ## The repository 'http://deb.debian.org/debian buster-backports Release' no longer has a Release file. DevFeed: [The repository 'http://deb.debian.org/debian buster-backports Release' no longer has a Release file.]() Original publisher: [Read original article]() Author: Vivek Gite Published: 2024-04-14T20:42:01Z Content type: tutorial Language: en Sources: [nixCraft: Linux Tips, Hacks, Tutorials, And Ideas In Blog Format (RSS/FEED)]() Topics: [apt](), [Linux](), [configuration](), [Security]() Tags: [apt](), [configuration](), [debian](), [debian-linux](), [easy](), [error](), [how-to](), [linux](), [repository](), [security](), [update]() ### AI overview A Debian troubleshooting guide explains why apt reports that the buster-backports repository no longer has a Release file. It identifies outdated or incorrect repository entries and recommends switching the source from deb.debian.org to archive.debian.org, while warning that archived packages may no longer receive security updates. ### Source excerpt When you run the sudo apt update, you may see the following message or error on a Debian Linux: Err:5 http://deb.debian.org/debian buster-backports Release 404 Not Found [IP: 146.75.34.132 80] Reading package lists... Done E: The repository 'http://deb.debian.org/debian buster-backports Release' no longer has a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. Here is how to fix this issue. Love this? sudo share_on: Twitter - Facebook - LinkedIn - Whatsapp - Reddit The post The repository 'http://deb.debian.org/debian buster-backports Release' no longer has a Release file. appeared first on nixCraft. ## Fixing APK Analyzer terminal errors by selecting a compatible Java version DevFeed: [Fixing APK Analyzer terminal errors by selecting a compatible Java version]() Original publisher: [Read original article]() Author: dustin@dustn.dev (Dustin Summers) Published: 2021-12-12T10:26:38Z Content type: tutorial Language: en Sources: [Dustin Summers]() Topics: [APK](), [Java](), [CI/CD Pipeline](), [Android Studio](), [Command-line interface](), [Google]() Tags: [android-studio](), [android-xmlschema-error-apkanalyzer-troubleshooting](), [apk](), [ci-cd](), [command-line](), [error](), [java](), [jdk]() ### AI overview This tutorial addresses an APK Analyzer error encountered when running the tool from a terminal, including in a CI/CD workflow. It explains that Android Studio's bundled JDK may be incompatible and describes selecting another installed Java version, with guidance for making the change permanent. ### Source excerpt Recently, I was tasked with using Google provided tools to decompile an APK in a CI/CD pipeline. This is great, because Google provides a tool called APK Analyzer, and provide tools both within the IDE itself and options to run it via the Command Line. I can talk more about the actual task later. For now, I want to discuss the issue that I first ran into when attempting to run apkanalyzer from the terminal. ## Kotlin Coroutines and Swift, revisited - Russell Wolf DevFeed: [Kotlin Coroutines and Swift, revisited - Russell Wolf]() Original publisher: [Read original article]() Published: 2021-05-28T18:42:45Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin](), [Coroutines](), [kotlin-coroutines](), [Swift](), [iOS](), [Mobile](), [reactive](), [Framework]() Tags: [api](), [architecture](), [article](), [class](), [classes](), [code-generation](), [coroutines](), [error](), [implementation](), [internals](), [interop](), [ios](), [kotlin](), [kotlin-coroutines](), [kotlin-multiplatform](), [mobile](), [patterns](), [reactive](), [stream](), [suspend](), [swift]() ### AI overview Russell Wolf revisits patterns for exposing Kotlin coroutine-based repository code to iOS. The article recommends managing coroutine scope in Kotlin, adding a Swift wrapper to hide Kotlin implementation details, and adapting callback events for RxSwift and Combine. ### Source excerpt An update on patterns for interop between Kotlin coroutines and RxSwift from Russell Wolf, engineer at Touchlab (Kotlin Multipaltform Mobile experts). ## Issues and hurdles when performing the initial upgrade DevFeed: [Issues and hurdles when performing the initial upgrade]() Original publisher: [Read original article]() Author: Mobian team Published: 2021-02-09T12:53:19Z Content type: tutorial Language: en Sources: [Mobian's Blog]() Topics: [upgrade](), [apt](), [Authentication](), [Package manager](), [Mobile](), [Terminal](), [Debian](), [screen]() Tags: [apt](), [authentication](), [changes](), [debian](), [dependencies](), [error](), [installation](), [pitfalls](), [terminal](), [upgrade]() ### AI overview This Mobian post explains pitfalls during the initial upgrade of a PinePhone. It describes a PAM issue that can temporarily prevent PIN unlocking before rebooting and recommends rebooting after the upgrade. It also recommends using a manual terminal update with Debian's apt package manager because the graphical Software application may fail with unmet-dependency errors during the initial update. ### Source excerpt Dear Mobian CE owners, congratulations on receiving your mobile phone. We hope you will like Mobian and we hope that you will be helping us to make it even better. We are writing this post as the initial upgrade is rather tricky and there are a few pitfalls when performing it. We do know that real men and women don't read manuals, but please read this post carefully in order to not lock yourself permanently out of your phone (just an example of what can happen if you don't read this...). Most importantly, we want to inform you, that there is a minor issue with PAM (pluggable authentication module) when upgrading the preflashed image. It was upgraded in an incompatible manner, and when the lockscreen of your phone is invoked after upgrading but before rebooting, it will not accept your PIN anymore (fortunately in most cases, a simple reboot makes it work again). So do not worry, your installation is not broken! Therefore: After upgrading your pinephone for the first time it is highly recommended to reboot the device after the upgrade has finished. And keeping the screen unlocked during the initial upgrade by: touching the screen frequently (get used to the feeling :-)) or temporarily disabling the automatic lockscreen in the settings. Otherwise you run the risk of not being able to unlock your device once the screen has been locked. The second major issue during the initial upgrade is related to the graphical software updater, called "Software". The Software application can usually keep the software on your pinephone up-to-date and will prompt you to reboot after an update. On the initial update with currently more than 600 package changes compared to the factory image, it chokes and struggles, though. You will get some mysterious "Cannot update due to unmet dependencies" error in the software app if you try. So for the initial update, we recommend performing a manual update in the terminal (a great way to familiarize yourself with the terminal and Debian's package man ## Dealing with failure DevFeed: [Dealing with failure]() Original publisher: [Read original article]() Author: Sergey Bykov Published: 2021-01-21T04:00:00Z Content type: opinion Language: en Sources: [Temporal Blog]() Topics: [Remote Procedure Call (RPC)](), [retry](), [HTTP](), [client](), [servers](), [systems]() Tags: [conference](), [distributed-system](), [error](), [how-to](), [http](), [opinion](), [retry](), [rpc]() ### AI overview The article examines how to handle failures in cloud and distributed systems, focusing on request-reply or RPC, persistent queues, and workflows. It explains the simplicity and limitations of RPC, including timeouts, ambiguous outcomes, retries, unavailable systems, and partial failures. ### Source excerpt I recently gave a talk at the CodeMesh conference, and I spent half of it reflecting on the seemingly boring topic of dealing with failures. ## Collect and handle multiple errors in Go DevFeed: [Collect and handle multiple errors in Go]() Original publisher: [Read original article]() Author: Graham King Published: 2020-05-22T17:33:53Z Content type: tutorial Language: en Sources: [Graham King]() Topics: [Go Language](), [Error Handling](), [Code]() Tags: [code](), [dependencies](), [error](), [error-handling](), [go](), [software]() ### AI overview A tutorial on collecting errors from multiple operations in Go and returning them together. It also explains checking whether any collected error matches a given error and discusses minimizing dependencies. ### Source excerpt In Go, how do you run several operations that might return an error, and return those errors at the end? Here's how I do it. ## MacOS Catalina, ruby bad interpreter error DevFeed: [MacOS Catalina, ruby bad interpreter error]() Original publisher: [Read original article]() Author: Stanko Published: 2019-12-11T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [macOS](), [Ruby](), [Homebrew](), [Jekyll](), [Development]() Tags: [bash](), [error](), [homebrew](), [issue](), [jekyll](), [macos](), [rbenv](), [ruby]() ### AI overview This troubleshooting article explains a Ruby "bad interpreter" error that prevented Jekyll from running after upgrading macOS to Catalina. The author found that Ruby gems were installed with the Homebrew Ruby, but the executable binaries were not linked correctly, and resolved the issue by adding the gems/bin directory to PATH. After a later Big Sur update, the author switched to rbenv because the same fix did not work. ### Source excerpt Another Catalina rant, this time about Ruby. As far as I know, on MacOS, it is advisable to leave system Ruby version to the OSFor example users don't have write permission on the system's gems folder. , and install a separate version for development. I had one installed via Homebrew, and never had any issues with it. But after Catalina upgrade, I couldn't run Jekyll. Every time it would fail with the following error: $ jekyll -bash: /usr/local/bin/jekyll: /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby: bad interpreter: No such file or directory I checked my bash profile and run which ruby to make sure I'm using the one installed by brew, and everything seemed to be in order. # .bash_profile export PATH="/usr/local/opt/ruby/bin:$PATH" # bash $ which ruby /usr/local/opt/ruby/bin/ruby After quick internet search I learned a lot of people are having similar problems after system upgrade, but I couldn't find the solution. I've tried reinstalling ruby, setting GEM_HOME, altering PATH in /etc/profile and /etc/bashrc, removing and reinstalling gems, but nothing worked. Then I tried to see which Jekyll binary is used and realized - for some reason gems were installed using the correct ruby version, but binaries weren't linked properly. So the solution was pretty easy at the end, all I had to do is to find gems/bin folder and add it to my path. # Use ruby installed by brew export PATH="/usr/local/opt/ruby/bin:/usr/local/lib/ruby/gems/2.6.0/bin/:$PATH" It looks like a common sense, but it took me a couple of hours to figure it out. Hopefully this will save time people facing the same issue. Big Sur update (December 2020) # I got the same error after updating to Big Sur, but this time I couldn't solve it. I still don't know what I was doing wrong. In the end I started using rbenv to manage ruby installations, and it works flawlessly. ## Encapsulating View State DevFeed: [Encapsulating View State]() Original publisher: [Read original article]() Published: 2019-07-19T16:00:00Z Content type: tutorial Language: en Sources: [Blogs on Ryan Harter]() Topics: [Android](), [business logic](), [Testing](), [App](), [Code]() Tags: [android](), [app](), [app-architecture](), [business-logic](), [code](), [error](), [livedata](), [messages](), [testing](), [viewmodel]() ### AI overview This article presents an approach to encapsulating view state in Android applications with AndroidX ViewModel. It explains how putting business logic and decision-making code in ViewModels can simplify Activities and Fragments and make the valuable code easier to test. ### Source excerpt The AndroidX ViewModel has become a central component in many modern Android apps. They offer a relatively simple abstraction to encapsulate business logic and decision making code which separates it from the platform frameworks, which are often difficult to test. Since ViewModels are easier to test than Framework classes like Activity and Fragment due to their simple lifecycles and lack of external dependencies, it makes sense to try to put as much logic, the complex decision-making code that should be tested, in ViewModels as possible. Ideally we'll be left with a view layer, either Activities, Fragments, or something else, which is so simple that it's not worth testing. ## The "Bug-O" Notation DevFeed: [The "Bug-O" Notation]() Original publisher: [Read original article]() Published: 2019-01-25T00:00:00Z Content type: opinion Language: en Sources: [Dan Abramov]() Topics: [API](), [debugging](), [Code](), [Programming]() Tags: [api](), [code](), [complexity](), [debugging](), [error](), [structure]() ### AI overview The article introduces "Bug-O notation," a way to think about how an API can slow developers down as a codebase grows. It argues that API and language design influence debugging difficulty, using imperative DOM updates and many possible operation orderings as an example. ### Source excerpt What is the 🐞(n) of your API? ## 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. ## localStorage and sessionStorage in Safari's private mode DevFeed: [localStorage and sessionStorage in Safari's private mode]() Original publisher: [Read original article]() Author: Stanko Published: 2017-08-09T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [LocalStorage](), [Code](), [App]() Tags: [code](), [error](), [export](), [ls](), [null](), [object](), [qa](), [quota](), [return](), [safari](), [storage](), [test](), [value](), [version]() ### AI overview This article explains that Safari private mode sets localStorage and sessionStorage limits to zero, preventing writes. It presents a localStorage facade that silently ignores storage operations when storage is unavailable, avoiding application errors. ### Source excerpt If you didn't know, in Safari's private mode both localStorage and sessionStorage are not working. To be exact, Safari sets storage's limit to 0, so you can't write anything to it. I keep forgetting this, until QA people report it at some point. So I quickly wrote a small facade for it, which fails silently in this case. That means it still doesn't work but it won't throw an error and break your application. This is the version for localStorage, just replace it with sessionStorage if you need it. const LS_TEST_KEY = 'ls-test'; let isLocalStorageSupported = typeof localStorage === 'object'; // Try to try { localStorage.setItem(LS_TEST_KEY, 'test'); localStorage.removeItem(LS_TEST_KEY); } catch (e) { isLocalStorageSupported = false; // If we get error that we exceeded storage's quota // but storage is still empty we are in private mode if (e.code === DOMException.QUOTA_EXCEEDED_ERR && localStorage.length === 0) { // Private mode } else { throw e; } } const LocalStorage = { getItem: (key) => { if (isLocalStorageSupported) { return localStorage.getItem(key); } return null; }, setItem: (key, value) => { if (isLocalStorageSupported) { localStorage.setItem(key, value); } }, removeItem: (key) => { if (isLocalStorageSupported) { localStorage.removeItem(key); } }, }; export default LocalStorage; ## Friday Q&A 2017-07-14: Swift.Codable DevFeed: [Friday Q&A 2017-07-14: Swift.Codable]() Original publisher: [Read original article]() Author: Mike Ash Published: 2017-07-14T13:57:00Z Content type: article Language: en Sources: [Mike Ash]() Topics: [Swift](), [Protocol (disambiguation)](), [JSON](), [Boilerplate](), [Objective-C](), [data](), [Mobile](), [Network]() Tags: [2017](), [apis](), [apple](), [apps](), [automatically](), [build](), [c](), [code](), [cross-platform](), [data](), [error](), [format](), [graphs](), [json](), [make](), [mobile](), [mobile-apps](), [protocol](), [q-a](), [swift]() ### AI overview This article explains Swift 4's Codable protocol and its serialization machinery. It describes serialization of values for storage or network transmission, contrasts Codable with earlier Apple ecosystem approaches, and discusses reducing repetitive encoding and decoding code. ### Source excerpt One of the interesting additions to Swift 4 is the Codable protocol and the machinery around it. This is a subject near and dear to my heart, and I want to discuss what it is and how it works today. (Read More) ## Word 2010 support - Weekly report - Part 2: Installation (cont.) DevFeed: [Word 2010 support - Weekly report - Part 2: Installation (cont.)]() Original publisher: [Read original article]() Published: 2016-11-20T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Environment Variables](), [configuration](), [Software](), [Framework]() Tags: [environment](), [environment-variables](), [error](), [failed](), [framework](), [free](), [function](), [installation](), [open-source](), [os](), [react](), [reactos](), [report](), [software](), [win32](), [winapi]() ### AI overview This second weekly report examines Word 2010 installation on ReactOS. It describes missing environment variables affecting the OSPPSVC service, a failed MSI action with error 1603, and a workaround that allowed installation to finish while leaving the underlying failure unresolved. ### Source excerpt In this second report I continue my investigations on the Word 2010 installation. Last time we saw that our services (and in particular the "Office Software Protection Platform" OSPPSVC service) were started without a complete environment block, and as a result some needed environment variables were missing, causing e.g. OSPPSVC to fail opening some of its files. We now analyse what happens after my local fix (NOTE: I have not committed the fix yet, as I validate it in my local installation first). ## The Boosting Margin, or Why Boosting Doesn't Overfit DevFeed: [The Boosting Margin, or Why Boosting Doesn't Overfit]() Original publisher: [Read original article]() Published: 2015-09-21T11:33:00Z Content type: article Language: en Sources: [Jeremy Kun]() Topics: [machine learning overfitting](), [Machine learning](), [generalization in machine learning](), [Occam's razor machine learning](), [Algorithm]() Tags: [algorithm](), [boosting](), [chernoff-bound](), [classficiation](), [complexity](), [conditional-probability](), [error](), [machine-learning](), [margins](), [mathematics](), [model](), [occam-s-razor](), [overfitting](), [training-data](), [vc-dimension]() ### AI overview This article explains why boosting can continue improving generalization after reaching zero training error. It introduces the margin-based theoretical explanation for this behavior and defines the confidence and margin of AdaBoost classifiers. ### Source excerpt There's a well-understood phenomenon in machine learning called overfitting. The idea is best shown by a graph: overfitting Let me explain. The vertical axis represents the error of a hypothesis. The horizontal axis represents the complexity of the hypothesis. The blue curve represents the error of a machine learning algorithm's output on its training data, and the red curve represents the generalization of that hypothesis to the real world. The overfitting phenomenon is marker in the middle of the graph, before which the training error and generalization error both go down, but after which the training error continues to fall while the generalization error rises. [Next page]()