GitHub PR 'Copy Link' Button Fails in Arc Browser Due to Clipboard API Restrictions

·1 views

A GitHub user named vovapyc reported that the 'Copy link' button in Pull Requests had been broken for at least a month while using the Arc browser on a MacBook Pro M1 Pro running macOS. Community member hoangperry identified the issue as browser-specific rather than a core GitHub bug, pointing to the browser's Clipboard API requirements around secure context, document focus, and user permissions. Arc browser's advanced features, such as its command-bar and extension layer, can inadvertently steal focus or block clipboard write attempts, causing the button to silently fail. GitHub acknowledged the feedback through an automated response but did not provide an immediate fix or explanation. Developers affected by the issue are advised to troubleshoot browser focus and clipboard permission settings as a workaround.

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)

How to Fix Cloudflare's 'Enable JavaScript and Cookies' Block in Automated Requests

The 'Enable JavaScript and cookies to continue' error is triggered by Cloudflare and similar security proxies when an incoming request fails to meet minimum browser authenticity requirements. It most commonly affects automated tools such as scrapers, bots, and HTTP libraries that do not properly mimic a real browser environment. Developers can bypass the block by supplying complete browser-like headers, enabling cookies, and using tools like Puppeteer with the stealth plugin to avoid fingerprint detection. Cloudflare issues a temporary cookie called cf_clearance after a security challenge is passed, and reusing this token in subsequent requests can help maintain access. For those who control the server, configuring WAF exclusions or using API tokens for internal endpoints offers a more reliable long-term solution.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Five Devs Fixed AI Server 429 Errors by Building a Client-Side Fair Queue

A team of five independent developers sharing a single free AI server experienced escalating latency and HTTP 429 rate-limit errors within days due to uncoordinated access. Each developer ran separate scripts with their own retry logic, which multiplied traffic and triggered a thundering herd effect that effectively made the server unusable by day seven. The root cause was architectural: no shared coordination layer meant every client assumed it was the sole user. The team resolved the problem by implementing a client-side asyncio priority queue that capped concurrent requests at two and routed all calls through a single process. The fix reduced 429 errors from 23 to zero on a 100-request mixed workload by enforcing fair ordering and explicit rejection when the queue reached capacity.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why AI Code Revert Rate Matters More Than Patch Acceptance Metrics

A developer opinion piece argues that AI patch acceptance rate is a misleading quality metric because it only reflects how code looks before merging, not how it performs under real-world conditions. Pre-merge signals like test passes and reviewer approvals can be influenced by well-formatted AI output, even when the underlying logic is flawed. The author contends that revert rate — tracked after deployment — is the only metric that cannot be gamed, since no team deliberately plans a rollback. A five-step git-based workflow is proposed to attribute revert commits to their original patches and compute a per-source revert rate over rolling time windows. The piece recommends freezing any code source whose 30-day revert rate exceeds 8%, and notes it was produced as part of promotional outreach for a product called MonkeyCode.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why Storelift Alerts Only on 10-Spot Rank Drops, Not Every Small Change

App store rank tracking tool Storelift triggers alerts only when an app's ranking drops by 10 or more positions, deliberately ignoring smaller fluctuations. The team behind the product argues that day-to-day ranking jitter — caused by competitor shifts, re-indexing, or sampling timing — makes single-spot alerts essentially meaningless noise. Alerting on every minor move trains users to ignore notifications within days, undermining the entire purpose of the alert system. A 10-spot threshold is designed to be large enough to filter out random noise yet small enough to flag genuine problems while they are still easy to fix. The same rule applies to upward rank jumps, allowing the system to confirm intentional changes like keyword edits with the same mechanism used to detect problems.

0 comments Read more at DEV Community