Skip to content

Fix "token is for a different user" false positive - #8648

Merged
fregante merged 1 commit into
mainfrom
dont-cache-me-bro
Aug 27, 2025
Merged

fregante merged 1 commit into
mainfrom
dont-cache-me-bro

Conversation

@fregante

Copy link
Copy Markdown
Member

@fregante fregante added the bug label Aug 27, 2025
import * as pageDetect from 'github-url-detection';
import mem from 'memoize';

import onetime from '../helpers/onetime.js';

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The core of the change is this. The function is no longer cached on first call. Whichever feature that used to call it before it's ready is still broken, but we'll fix it once that's found and reported.

@fregante
fregante merged commit 4f2fd40 into main Aug 27, 2025
@fregante
fregante deleted the dont-cache-me-bro branch October 13, 2025 11:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

false positive "token is for a different user"

1 participant