# import Published articles for import. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## SecretSpec 0.18: Secret lifecycle, four new providers, and Swift DevFeed: [SecretSpec 0.18: Secret lifecycle, four new providers, and Swift]() Original publisher: [Read original article]() Author: domenkozar Published: 2026-08-04T15:41:38Z Content type: release Language: en Sources: [Announcements - NixOS Discourse]() Topics: [Swift](), [SDKs](), [Amazon Web Services](), [Command-line interface](), [Authentication]() Tags: [announcements](), [aws](), [cli](), [import](), [release](), [sdk](), [secrets](), [swift](), [vault]() ### AI overview SecretSpec 0.18 expands secret lifecycle operations, adds four providers, and introduces a Swift SDK. It also adds declaration discovery from additional stores, provider migration safeguards, and several authentication and platform updates. ### Source excerpt 0.18 release expands the secret lifecycle, adds four providers, and introduces a Swift SDK. We have a new logo! Declare, delete, and safely move secrets Declare secrets without hand-editing the manifest: $ secretspec add STRIPE_API_KEY --description "Stripe API access token" ✓ Added secret 'STRIPE_API_KEY' to profile 'default' in secretspec.toml secretspec add preserves the manifest's comments and formatting without asking for or storing a value. secretspec delete removes stored values while keeping their declarations. Provider migrations can remove the source after proving the move succeeded: secretspec import dotenv:~/.config/payments/.env --delete-source SecretSpec verifies each destination value before deleting its source and leaves the source intact when conflicts occur. Discover declarations from existing stores secretspec init --from can now discover declarations from age files, AWS Parameter Store hierarchies, and scoped Bitwarden collections, in addition to dotenv. It writes names and generated descriptions to secretspec.toml, never values. Four new providers SecretSpec now supports 24 providers, including: Bitwarden Password Manager (bw://): read, write, and discover vault items through the bw CLI. Keeper Secrets Manager (keeper://): batched reads, writes, deletion, and existing-record references. AWS Parameter Store (awsps://): KMS-encrypted parameters, versioned references, and bounded discovery. Dashlane (dashlane://): read-only secrets, secure notes, and logins through dcli. Swift SDK and provider authentication The new Swift SDK brings the shared SecretSpec resolver to macOS 12+ on Intel and Apple silicon as a checksummed XCFramework. Vault and OpenBao also gain custom AppRole and JWT mount paths, dotenv paths accept ~, and Linux keyring builds no longer require system libdbus. Read the full announcement: SecretSpec SecretSpec 0.18: Secret lifecycle, Bitwarden, Keeper, AWS Parameter Store,... Declare, discover, migrate, and delete secrets from the CLI ## Migrate CloudFormation to Pulumi with Discovered Stacks DevFeed: [Migrate CloudFormation to Pulumi with Discovered Stacks]() Original publisher: [Read original article]() Author: Alejandro Cotroneo Published: 2026-07-30T00:00:00Z Content type: tutorial Language: en Sources: [Pulumi]() Topics: [Infrastructure as code](), [AWS CloudFormation](), [migration](), [Amazon Web Services](), [VPC](), [Amazon S3](), [DynamoDB](), [AWS IAM]() Tags: [aws](), [cloudformation](), [dynamodb](), [git](), [iac](), [iam](), [import](), [insights](), [kms](), [migration](), [pulumi](), [pulumi-cloud](), [pulumi-neo](), [s3](), [tutorials](), [vpc]() ### AI overview A tutorial shows how to migrate a 61-resource AWS CloudFormation stack to Pulumi using Discovered Stacks in Pulumi Cloud. It explains how to find the stack, review migration status, start the migration, resolve unmatched resources, and verify the result with a zero-diff pulumi preview. ### Source excerpt With Discovered Stacks, Pulumi Cloud does the bookkeeping for a CloudFormation migration: every resource in the stack gets an explicit migration status, and the migration is done when the code provably matches the cloud. In this tutorial, we take one real CloudFormation stack from discovered to migrated and managed by Pulumi IaC, end to end. What we're migrating Our example is payments-api, a CloudFormation stack with 61 resources: a VPC, an Aurora ledger database behind an RDS Proxy, an assets S3 bucket, a DynamoDB ledger table, a Kinesis payment-events pipeline, and the IAM roles, KMS keys, and secrets that wire them together. The plan has five steps: Find the stack in Pulumi Cloud. Review the migration breakdown at a glance. Start the migration. Resolve the stragglers, so every resource is accounted for. Confirm the quality gate: a zero-diff pulumi preview. We'll use Pulumi Neo to do the heavy lifting, but nothing here depends on it. The same flow works with your own coding agent or entirely by hand, because migration status is derived from actual stack state -- however the work gets done, the console shows the same progress. Step 1: Find your stack in Pulumi Cloud Discovered Stacks builds on Discovery, so the only prerequisite is a scanned cloud account -- the AWS account holding your CloudFormation stacks. Once a scan has run, open the Stacks page and turn on Show Discovered Stacks. Your CloudFormation stacks appear alongside your Pulumi stacks. The project name comes from the CloudFormation stack (payments-api), and the stack name encodes the account and region it came from, so the same template deployed to two regions shows up as two distinct discovered stacks. Step 2: Plan the migration at a glance Open the discovered stack's Migration tab. It lays out all 61 resources of payments-api by status, so you can visualize the migration before touching anything: 54 Ready: mapped to a Pulumi type and confirmed to exist -- importable right now. 2 Not found: mapped, but ## Isovalent Networking for Kubernetes 1.19: BGP Route Import, Policy Tiers, and Timescape enhancements DevFeed: [Isovalent Networking for Kubernetes 1.19: BGP Route Import, Policy Tiers, and Timescape enhancements]() Original publisher: [Read original article]() Author: Dean Lewis Published: 2026-07-10T08:58:39Z Content type: release Language: en Sources: [Isovalent - The latest articles covering eBPF-based Networking, Observability, and Security]() Topics: [networking](), [Kubernetes](), [BGP](), [import]() Tags: [bgp](), [import](), [isovalent](), [kubernetes](), [latest](), [networking](), [release]() ### AI overview Isovalent Networking for Kubernetes 1.19 is presented as a release featuring BGP route import, policy tiers, and Timescape enhancements. ### Source excerpt Learn about the latest Isovalent Networking for Kubernetes 1.19 release ## Kubo 0.42.0 release: on-demand CID announcements, partial CAR import and export, and reprovide changes DevFeed: [Kubo 0.42.0 release: on-demand CID announcements, partial CAR import and export, and reprovide changes]() Original publisher: [Read original article]() Author: Ipfs Published: 2026-06-08T00:00:00Z Content type: release Language: en Sources: [IPFS]() Topics: [releases](), [version](), [export](), [import](), [migration](), [Routing (disambiguation)]() Tags: [block](), [export](), [gateway](), [import](), [kubo](), [migration](), [other](), [release-notes](), [releases](), [retries](), [routing](), [store](), [terminal](), [version]() ### AI overview Kubo 0.42.0 adds on-demand CID announcements, supports streaming CIDs from standard input, and introduces partial CAR export and import. It also changes providing semantics, fixes pin operations blocked by reprovide cycles, and improves migration retries for older repositories. ### Source excerpt Just released: Kubo 0.42.0! ## Agentic Nx Import: Let an Agent Drive Your Monorepo Migrations DevFeed: [Agentic Nx Import: Let an Agent Drive Your Monorepo Migrations]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2026-04-30T00:00:00Z Content type: article Language: en Sources: [Juri Strumpflohner]() Topics: [AI Agent](), [Command-line interface](), [Tooling]() Tags: [agent](), [agentic](), [ai](), [ai-agent](), [ai-agents](), [blog](), [cli](), [code](), [git](), [import](), [migrations](), [monorepo](), [nx](), [project](), [skills](), [tests](), [token-efficiency](), [tool](), [verification](), [video]() ### AI overview The article describes an agentic workflow for importing existing projects into an Nx monorepo. The Nx CLI handles deterministic work such as cloning, file moves, plugin detection, setup, and Git history preservation, while an AI agent addresses workspace-specific gaps and performs follow-up verification. ### Source excerpt AI agents make importing existing projects into an Nx monorepo easier: does the heavy lifting while the agent handles workspace-specific gaps. ## Upgrade Cypress To TypeScript v6 DevFeed: [Upgrade Cypress To TypeScript v6]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-04-23T04:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [TypeScript](), [upgrade](), [Webpack]() Tags: [cypress](), [import](), [module](), [products](), [typescript](), [upgrade](), [webpack]() ### AI overview This tutorial explains how to upgrade Cypress projects to TypeScript v6. It recommends using bundler module resolution with Webpack and adjusting transpilation and path-alias options when needed. ### Source excerpt Finally, it has happened. Cypress v15.14 supports TypeScript v6. This is a big deal ## How to bypass SSL for PROJ reprojection DevFeed: [How to bypass SSL for PROJ reprojection]() Original publisher: [Read original article]() Author: Robin Wilson Published: 2026-03-23T16:23:36Z Content type: tutorial Language: en Sources: [Robin Wilson]() Topics: [Geographic Information System](), [Security](), [SSL](), [import](), [Linux](), [osx](), [Windows]() Tags: [academic](), [command](), [computing](), [gis](), [how-to](), [import](), [linux](), [osx](), [remote-sensing](), [security](), [ssl](), [windows]() ### AI overview This tutorial explains how to temporarily disable SSL verification for PROJ during coordinate reprojection when self-signed or misconfigured certificates cause downloads of conversion data to fail. It notes the security trade-off and points to setting a PROJ environment variable. ### Source excerpt A friend was using GDAL's ogr2ogr command to import some data to PostGIS recently, and as part of the import they were doing a reprojection of the data. They got the following error: PROJ: Cannot open https://cdn.proj.org/uk_os_OSTN15_NTv2_OSGBtoETRS.tif: schannel: the certificate or certificate chain is based on an untrusted root They've had various SSL errors on [...] ## 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 [...] ## Blog: GPG Key Rotation for Falco Packages (2026) DevFeed: [Blog: GPG Key Rotation for Falco Packages (2026)]() Original publisher: [Read original article]() Published: 2025-12-12T00:00:00Z Content type: release Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [Security](), [Package manager](), [releases](), [apt]() Tags: [announcements](), [apt](), [falco](), [import](), [installation](), [releases](), [rotation](), [rsa](), [security]() ### AI overview Falco maintainers are rotating the 4096-bit RSA GPG key used to sign official RPM and DEB packages because the existing key expires on January 17, 2026. The transition uses a soft launch followed by a hard cut-over, and existing users should update their keyrings before January 12, 2026. ### Source excerpt The GPG key used to sign official Falco packages (RPM and DEB) is set to expire on January 17, 2026. To ensure the security and continuity of our software distribution, the Falco maintainers will be rotating to a new 4096-bit RSA key. We have designed a two-phase "Soft Launch" strategy to make this transition as smooth as possible, providing a one-month transition window before the old key is retired. The Rotation Plan To avoid immediate disruption, we are rolling out the new key in two distinct phases. You can follow the detailed progress in our tracking issue #3750. Phase 1: Soft Launch (Dec 12, 2025) What happens: The new GPG key has been published and added to our repository configuration. Dev Builds: Will begin using the New Key immediately. Stable Builds: No stable releases are planned for this phase. If any hotfixes are released, they will be signed with New Key as well. Key Bundle: The official key URL has been updated to serve a bundle containing both the Old (valid) and New (valid) keys. Phase 2: Hard Cut-Over (Jan 12-17, 2026) What happens: This is the maintenance window where we fully switch to the new key. Mass Resign: All existing stable packages on download.falco.org will be resigned with the New Key. Revocation: The Old Key will be officially revoked and removed from the active bundle. Impact: If you have not updated your keyring by this date, your package manager (apt or yum) will reject updates with a signature verification error. Action Items for Users We strongly recommend all users update their GPG keyring before January 12, 2026 to avoid interruption. New Users If you are installing Falco for the first time following our Install on a host (DEB,RPM) instructions, no action is required. The installation process will guide you to fetch the new key bundle, ensuring you are ready for both phases. Existing Users If you have an existing Falco installation, you must manually import the new key. We have updated the key file at our standard URL to includ ## Keycloak 26.4.5 released DevFeed: [Keycloak 26.4.5 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2025-11-12T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [changelog]() Tags: [authorization](), [bugs](), [ci](), [docs](), [download](), [email](), [idm](), [import](), [jpa](), [kerberos](), [keycloak](), [keycloak-release](), [ldap](), [migration-guide](), [openid-connect](), [ordering](), [quarkus](), [release](), [saml](), [sso](), [ui]() ### AI overview Keycloak 26.4.5 was released on November 12, 2025. The release page links to downloads and a migration guide and lists resolved issues involving tests, documentation, JPA, email persistence, database migration, authorization policies, attribute ordering, Quarkus builds, URL normalization, and the Admin Console. ### Source excerpt To download the release go to Keycloak downloads. Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Bugs #42601 Flaky test: org.keycloak.testsuite.broker.KcOidcBrokerTest#testPostBrokerLoginFlowWithOTP ci #43212 Document missing artifact dependency for UserStoragePrivateUtil docs #43564 Invalid liquibase check sum for jpa-changelog-2.5.0.xml core #43718 Email Not Persisted During Registration When "Email as Username" is Enabled and User Edit Permission is Disabled user-profile #43793 import does not seem to run db migration import-export #43883 Creating group policy on a client uses "manage-clients" role if FGAP V1 is disabled authorization-services #44010 Ordering attributes will unset the unmanaged attribute policy user-profile #44031 Can't build keycloak 26.4.4 with quarkus.launch.rebuild=true dist/quarkus #44056 Allow only normalized URLs in requests caused a regression in view authz permission details in Admin Consol admin/ui #44117 DockerClientTest failure testsuite ## Apple Photos App Corrupts Images DevFeed: [Apple Photos App Corrupts Images]() Original publisher: [Read original article]() Published: 2025-09-16T23:59:23Z Content type: article Language: en Sources: [Aaron Patterson]() Topics: [App](), [file](), [import](), [debug](), [Image](), [Hardware](), [USB]() Tags: [app](), [camera](), [debug](), [file](), [files](), [hardware](), [images](), [import](), [photo](), [photos](), [trust](), [usb]() ### AI overview The article describes intermittent image corruption in Apple Photos when importing photos from an OM System OM-1 camera. The author reports corrupted JPEG and RAW files, estimates losing about 30% of the images from one event, investigates possible hardware causes, and changes to a different import workflow after losing trust in Photos. ### Source excerpt The Apple Photos app sometimes corrupts images when importing from my camera. I just wanted to make a blog post about it in case anyone else runs into the problem. I've seen other references to this online, but most of the people gave up trying to fix it, and none of them went as far as I did to debug the issue. I'll try to describe the problem, and the things I've tried to do to fix it. But also note that I've (sort of) given up on the Photos app too. Since I can't trust it to import photos from my camera, I switched to a different workflow. Here is a screenshot of a corrupted image in the Photos app: How I used to import images I've got an OM System OM-1 camera. I used to shoot in RAW + jpg, then when I would import to Photos app, I would check the "delete photos after import" checkbox in order to empty the SD card. Turns out "delete after import" was a huge mistake. Getting corrupted images I'm pretty sure I'd been getting corrupted images for a while, but it would only be 1 or 2 images out of thousands, so I thought nothing of it (it was probably my fault anyway, right?) But the problem really got me upset when last year I went to a family member's wedding and took tons of photos. Apple Photos combines RAW + jpg photos so you don't have a bunch of duplicates, and when you view the images in the photos app, it just shows you the jpg version by default. After I imported all of the wedding photos I noticed some of them were corrupted. Upon closer inspection, I found that it sometimes had corrupted the jpg, sometimes corrupted the RAW file, and sometimes both. Since I had been checking the "delete after import" box, I didn't know if the images on the SD card were corrupted before importing or not. After all, the files had been deleted so there was no way to check. I estimate I completely lost about 30% of the images I took that day. Losing so many photos really rattled me, but I wanted to figure out the problem so I didn't lose images in the future. Narrowing down t ## Structured Output with LangChain and Llamafile DevFeed: [Structured Output with LangChain and Llamafile]() Original publisher: [Read original article]() Author: brakmic Published: 2025-06-22T16:50:12Z Content type: tutorial Language: en Sources: [Harris Brakmic - Coding]() Topics: [LangChain](), [llamafile](), [JSON](), [llama.cpp](), [Parser](), [Pydantic]() Tags: [ai](), [code](), [coding](), [cpp](), [how-to](), [import](), [json](), [langchain](), [llama-cpp](), [llamafile](), [llm](), [local](), [local-llm](), [models](), [properties](), [python](), [structured-output]() ### AI overview A tutorial on using LangChain with Llamafile to produce structured JSON output from a local large language model. It uses JsonOutputParser, PromptTemplate, and a Pydantic model because Llamafile does not provide a with_structured_output method. ### Source excerpt Learn how to extend Llamafile with LangChain's JsonParser to produce clean, structured JSON output ## What Does "use client" Do? DevFeed: [What Does "use client" Do?]() Original publisher: [Read original article]() Published: 2025-04-25T00:00:00Z Content type: tutorial Language: en Sources: [Dan Abramov]() Topics: [React](), [client](), [servers](), [Back end](), [Code](), [Front end]() Tags: [backend](), [client](), [code](), [frontend](), [import](), [react](), [server]() ### AI overview This tutorial explains what the React "use client" directive does. It presents client/server directives as a way to express boundaries within the module system and discusses how code can span separate machines despite network and serialization constraints. ### Source excerpt Two worlds, two doors. ## GIMP 3.0 Released With Updated UI, Wayland Support, Improved File Compatibility, and Plugin API Changes DevFeed: [GIMP 3.0 Released With Updated UI, Wayland Support, Improved File Compatibility, and Plugin API Changes]() Original publisher: [Read original article]() Author: Vivek Gite Published: 2025-03-18T03:45:26Z Content type: release Language: en Sources: [nixCraft: Linux Tips, Hacks, Tutorials, And Ideas In Blog Format (RSS/FEED)]() Topics: [Development](), [Linux](), [CSS](), [Wayland](), [API](), [Compression](), [file](), [format](), [export](), [import]() Tags: [api](), [centos](), [compression](), [css](), [debian-linux](), [downloads](), [export](), [file](), [format](), [freebsd](), [gimp](), [import](), [improvements](), [linux](), [linux-news](), [macos](), [new-features](), [open-source](), [plugins](), [release](), [sysadmin](), [unix](), [upgrades](), [version]() ### AI overview GIMP 3.0 was released on March 16, 2025. The release adds a GTK3 interface, HiDPI and tablet improvements, Wayland support, CSS-based themes, updated icons, broader file-format compatibility, painting and text improvements, and updates to the core plugin API. ### Source excerpt Wow! After years of hard work and countless commits, we have finally reached a huge milestone: GIMP 3.0 is officially released! I am excited as I write this and can't wait to share some incredible new features and improvements in this release. GIMP 2.10 was released in 2018, and the first development version of GIMP 3.0 came out in 2020. GIMP 3.0 released on 16/March/2025. Let us explore how to download and install GIMP 3.0, as well as the new features in this version. Love this? sudo share_on: Twitter - Facebook - LinkedIn - Whatsapp - Reddit The post Download of the day: GIMP 3.0 is FINALLY Here! appeared first on nixCraft. ## Effortlessly Import Your Kubernetes Cluster into Rancher DevFeed: [Effortlessly Import Your Kubernetes Cluster into Rancher]() Original publisher: [Read original article]() Author: Abhimanyu Saharan Published: 2025-03-04T00:00:00Z Content type: tutorial Language: en Sources: [Abhimanyu Saharan]() Topics: [Kubernetes](), [rancher]() Tags: [guide](), [import](), [kubernetes](), [management](), [rancher](), [zero-to-hero-rancher]() ### AI overview A step-by-step guide to importing a Kubernetes cluster into Rancher for management. ### Source excerpt Learn to import your Kubernetes cluster into Rancher for seamless management with this detailed, step-by-step guide. ## Import Postgres tables into Tinybird with PostgreSQL Table Function DevFeed: [Import Postgres tables into Tinybird with PostgreSQL Table Function]() Original publisher: [Read original article]() Author: Cameron Archer Published: 2024-07-29T00:00:00Z Content type: release Language: en Sources: [Tinybird]() Topics: [PostgreSQL](), [data](), [Query (disambiguation)](), [systems]() Tags: [etl](), [import](), [pipelines](), [postgres](), [postgresql](), [product-updates]() ### AI overview Tinybird's PostgreSQL table function connects Postgres data directly to Tinybird and enables querying across systems without complex ETL pipelines. ### Source excerpt The PostgreSQL table function connects your Postgres data to Tinybird directly. Query across systems without complex ETL pipelines. ## Announcing Supabase on JSR DevFeed: [Announcing Supabase on JSR]() Original publisher: [Read original article]() Author: Bobbie Soedirgo; Thor Schaeff Published: 2024-07-16T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [JavaScript](), [TypeScript](), [Deno](), [Authentication](), [Web]() Tags: [announce](), [announcement](), [authentication](), [client-library](), [database](), [dependencies](), [developer](), [developer-experience](), [documentation](), [import](), [javascript](), [npm](), [open-source](), [other](), [provenance](), [published](), [real-time](), [registry](), [source](), [storage]() ### AI overview Supabase announces that its JavaScript client library is available on JSR, an open source JavaScript registry. The article describes JSR support for TypeScript source publishing, generated documentation and type definitions, provenance attestation, and npm-like package managers, then outlines installation and use of the client across JavaScript environments. ### Source excerpt Supabase is now available on the open source JavaScript Registry (JSR). ## Fastest Way to Read Excel in Python DevFeed: [Fastest Way to Read Excel in Python]() Original publisher: [Read original article]() Author: Haki Benita Published: 2024-01-02T22:00:00Z Content type: article Language: en Sources: [Haki Benita]() Topics: [Python](), [data](), [CSV](), [parquet]() Tags: [article](), [articles](), [benchmarks](), [compare](), [csv](), [excel](), [generator](), [import](), [memory](), [parquet](), [performance](), [python](), [reading]() ### AI overview This article compares several ways to read Excel files from Python. It benchmarks importing data from a 25 MB XLSX file containing 500,000 rows and considers timing, memory use, generators, and preservation of Excel data types. ### Source excerpt I'm fairly sure that Excel is the most common way to store data, manipulate data, and yes(!), even pass data around. This is why it's not uncommon to find yourself reading Excel in Python. In this article I compare several ways to read Excel from Python. ## garn v0.0.19: Bringing existing flake files into your garn project DevFeed: [garn v0.0.19: Bringing existing flake files into your garn project]() Original publisher: [Read original article]() Published: 2023-12-07T00:00:00Z Content type: release Language: en Sources: [Garnix Blog]() Topics: [import](), [Nix](), [version](), [Internet]() Tags: [existing](), [files](), [import](), [project](), [release](), [repository](), [version]() ### AI overview garn v0.0.19 adds support for importing Nix flakes from the internet and from an existing repository into a garn project. ### Source excerpt Release announcement for garn version v0.0.19, which includes the ability to import Nix flakes from the internet and from your repository. ## Supabase Beta September 2023 DevFeed: [Supabase Beta September 2023]() Original publisher: [Read original article]() Author: Ant Wilson Published: 2023-10-04T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [releases](), [REST API](), [Databases](), [Network](), [WebSocket](), [Open Source]() Tags: [api](), [import](), [ipv4](), [ipv6](), [json](), [jwt](), [new-features](), [releases](), [rest-api](), [websocket]() ### AI overview Supabase's September 2023 beta update highlights REST-based Realtime broadcasts, broader Supavisor connection pooling, an upcoming IPv6 transition for database connection strings, a new Airtable Foreign Data Wrapper, Supabase Studio improvements, and HNSW support in Vecs with pgvector. ### Source excerpt September was packed with so many new features and releases that it might have seemed like another Launch Week, but it wasn't! ## 10x faster python test iteration via fork(2) DevFeed: [10x faster python test iteration via fork(2)]() Original publisher: [Read original article]() Author: raylu Published: 2023-07-20T16:01:45Z Content type: tutorial Language: en Sources: [Benchling]() Topics: [Python](), [Testing](), [SQLAlchemy](), [modules](), [import](), [Code]() Tags: [benchling](), [code](), [dependencies](), [developer-productivity](), [engineering](), [fork](), [import](), [modules](), [python](), [sqlalchemy](), [testing]() ### AI overview This Benchling Engineering article explains how the Build team reduced Python test iteration time in a dependency-heavy codebase. It discusses the limitations of importlib.reload() and describes a fork-based approach that made the second test run start 10 times faster, reducing waiting by 90%. ### Source excerpt It's ideal to get feedback on your code faster -- to make a code change and see the result instantly. But, as projects get larger, reload times get longer. Each incremental dependency or bootstrap code block that adds 200ms feels worth it, but 50 of them later and it takes 10 seconds to see the result of a code change. On the Build team at Benchling, that's where we found ourselves one day. We used 146 packages which pull in 128 transitive dependencies for a total of 274 packages. We also spent a lot of time waiting for SQLAlchemy models to initialize. The result is our test harness took 10 seconds to set up. After making a code change, you'd start the test runner, wait a few seconds, alt+tab to your browser, get distracted for a few minutes, and then find out you had a typo in your code. This is a common challenge for a growing codebase, but it's something we knew we needed to fix. Here's the process we arrived at which allowed the second run of tests to start 10x faster -- 90% less waiting. While it'll work a little differently for your codebase depending on the language, dependencies, etc. you're using, hopefully this can inspire you on your journey to faster feedback and testing. importlib.reload() Since the problem is that we spend so long setting up a bunch of modules just right and then want to see the change in a single file we're editing, the most obvious solution is to use importlib.reload from the standard library. import importlib import sys import test_harness_stuff # takes 10 seconds import tests def rerun_tests(changed_path): for mod in sys.modules.values(): if mod.__file__ == changed_path: importlib.reload(mod) tests.run_tests() break if __name__ == '__main__': setup_file_watcher(rerun_tests) tests.run_tests() This (with some special handling for built-in modules, relative path resolution, and batching to handle editors that perform multiple filesystem operations per save) works alright when the file being changed is a test file (or any other leaf node ## Using Python AST to resolve dependencies DevFeed: [Using Python AST to resolve dependencies]() Original publisher: [Read original article]() Published: 2023-06-30T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's Blog]() Topics: [Python](), [Parsing](), [syntax](), [modules](), [Code]() Tags: [article](), [ast](), [code](), [dependencies](), [how-to](), [import](), [modules](), [object](), [python](), [python-dependencies](), [repository](), [resolver](), [startup](), [syntax](), [tokens](), [trees](), [unit-tests]() ### AI overview This tutorial explains how to use Python's Abstract Syntax Trees to resolve dependencies among objects imported across modules in a complex repository. It proposes recursively analyzing imports and copying required object code and dependencies into a destination folder. ### Source excerpt This article covers how to resolve python dependencies using Python's Abstract Syntax Trees (AST). There are different and maybe better ways to understand the scope of your python dependencies... ## Music Stats with DuckDB DevFeed: [Music Stats with DuckDB]() Original publisher: [Read original article]() Author: Artur Dryomov Published: 2023-06-05T00:00:00Z Content type: article Language: en Sources: [Artur Dryomov]() Topics: [DuckDB](), [data](), [import](), [CSV](), [JSON]() Tags: [csv](), [data](), [duckdb](), [import](), [json](), [music]() ### AI overview The article describes using DuckDB to combine and analyze music scrobbles from sources including Last.fm and Spotify, working with JSON and CSV data in different formats. ### Source excerpt Music! Everyone likes music. Well, I certainly hope so. Stats! Well, not everyone likes stats but I certainly do. In this article I'll describe an approach to work with music scrobbles from different sources and in different formats using DuckDB. DuckDB is a perfect match for such ad-hoc scenarios -- it has a minimal footprint, great performance and useful features. Scrobbles I've been using multiple music sources over the past decade. Fortunately, I had a Last.fm account from the beginning. It allowed me to track almost everything I've listened -- resulting in almost 110+ thousands of scrobbles. Unfortunately, I haven't used it all the time. ## Why You Should Execute jOOQ Queries With jOOQ DevFeed: [Why You Should Execute jOOQ Queries With jOOQ]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-01-18T11:46:25Z Content type: opinion Language: en Sources: [jOOQ]() Topics: [SQL](), [Java](), [Databases](), [Compiler]() Tags: [code-generation](), [crud](), [csv](), [execution](), [export](), [identity](), [import](), [java](), [jdbc](), [jooq](), [jooq-in-use](), [jpa](), [json](), [mapping](), [multiset](), [nested-collections](), [nested-records](), [orm](), [r2dbc](), [sql](), [stored-procedures](), [type-safety](), [udt](), [updatablerecord](), [user-defined-types](), [xml]() ### AI overview The article argues that queries built with jOOQ should generally also be executed with jOOQ. It explains that jOOQ preserves type safety and structured result mapping during execution, whereas extracting SQL and bind values for JDBC-level execution loses compiler knowledge of the result set. It acknowledges limited use cases for executing jOOQ-generated SQL elsewhere, such as a small number of dynamic queries in an otherwise JPA-based application. ### Source excerpt Previously on this blog, I've written a post explaining why you should use jOOQ's code generator, despite the possibility of using jOOQ without it. In a similar fashion, as I've answered numerous jOOQ questions on Stack Overflow, where someone used jOOQ to build a query, but then executed it elsewhere, including on: jOOQ itself isn't ... Continue reading Why You Should Execute jOOQ Queries With jOOQ -> [Next page]()