SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

Claude Code 2.1.304 Fixes Worktree Bug That Could Delete Branches on Exit

0
·12 views

Claude Code's --worktree option normally asks before removing a worktree that contains work, but a bug could remove it and its branch without prompting. The release note says this happened when HEAD was detached or pointed at a branch other than the one Claude created, which could lose commits. Version 2.1.304, published by Anthropic on October 19, fixes the problem. The article's author notes the affected versions and root cause were not specified, and they did not reproduce the bug. Users who used --worktree are advised to update and check for recently lost commits using git fsck, then save any found commits to a branch.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Testing Google Docs resume PDFs with an open-source parser: ligatures, page breaks and a missing name

A resume template maker tested how a parser reads PDFs exported from Google Docs, aiming to see which fields are extracted correctly. Since no public way exists to test against applicant tracking systems like Workday or Greenhouse, the team used a pinned open-source parser from OpenResume, pdfminer.six for raw text, and python-docx for Word exports. The test automatically downloads each template as PDF and DOCX through Google Docs' public export URL and records file hashes so reruns can confirm the same input. To run OpenResume's parser outside the browser, the team re-implemented the PDF-reading step and stubbed out rendering-only classes. Expected output was built from source content, and comparisons normalize text before matching field by field and bullet by bullet.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Fixing SSH 'Too Many Authentication Failures' With Multiplexing and Config Tweaks

A common SSH problem, 'Too many authentication failures,' often stems from the client's own configuration rather than the server. Connection multiplexing via ControlMaster can cause socket collisions when chaining ProxyJump hosts, which is avoided by giving each hop a distinct ControlPath. Loading several keys into ssh-agent can also trigger the error, since the server may reject attempts before the correct key is tried; IdentitiesOnly with explicit IdentityFile ordering resolves this. Because SSH applies the first matching value for each option, a broad Host * block placed early can silently override more specific host settings, so catch-all defaults belong at the end or in separately included files.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Developer releases zero-dependency i18n toolkit for React Native's New Architecture

A developer has released react-native-i18n-kit, a localization toolkit for React Native written in Kotlin, Swift and strict TypeScript. The library was built to avoid common pain points such as JavaScript-side guessing of locale facts, legacy bridge dependencies, and dependency sprawl. It is implemented as a TurboModule that reads native device locale data, including calendar, time zone, number separators and measurement system. The toolkit supports instant language switching, CLDR-based pluralization, RTL handling, and persistence of the user's chosen language. It also ships no prebuilt native binaries, keeping it compliant with Android's 16 KB page-size requirement.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

How to tell whether a trademark MCP server actually monitors your brand

A trademark MCP server that only searches returns a list of existing marks, with no record of what is new, so it cannot function as a true watch. The key test is whether the tool can report changes since a given date through a stored watch set and a changes-since call. The article stresses that the critical window runs from publication to opposition, so the server should key records on publication date and cover Madrid designations, not just registrations. Buyers should also check which offices are watched and how often, and whether pricing is visible before connecting. The author suggests a checklist of eight questions, with six or more yes answers indicating a real watch, and notes that the test applies to any vendor, including their own product.

0 comments Read more at DEV Community