Skip to content

Conversation

@jsoref
Copy link
Contributor

This mostly updates the check-spelling metadata.

It also prepares for the next version (applying newer dictionaries that I hope to eventually switch to).

In general, I'd recommend reviewing starting with changes to expect.txt -- new entries should be considered, they probably indicate changes to patterns or dictionaries. I haven't thought too carefully about all of them, but I'll highlight some.

I'm also tossing in a change to the yarn-install behavior because the workflow in github currently burns >30s installing stuff that it won't use.

^pkg/rancher-desktop/assets/scripts/logrotate-k3s$
^pkg/rancher-desktop/assets/scripts/logrotate-lima-guestagent$
^pkg/rancher-desktop/sudo-prompt/
^pkg/rancher-desktop/utils/processOutputInterpreters/__tests__/assets/trivy-image-postgres
Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

There are a pair of files that had a bunch of things that check-spelling doesn't like, but they're clearly designed as inputs to a test based on real world values, so fixing them doesn't make sense.

ipaddr
IPAM
IPlugin
iptable
Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

I removed a pattern for this because it was the only case covered and it didn't seem worth it for me to carry along the cost while checking all lines in all files.

XVar
xvfb
xwininfo
xyzzy
Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

I'm not quite sure what changed that resulted in this being seen.


# hit-count: 2 file-count: 1
# iSCSI iqn (approximate regex)
\biqn\.[0-9]{4}-[0-9]{2}(?:[\.-][a-z][a-z0-9]*)*\b:[\w.]+
Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

This is slightly extended from the base pattern

Comment on lines 4 to 16
inputs:
skip-electron:
description: Skip Electron
default: ''
required: false
skip-go:
description: Skip Go
default: ''
required: false
skip-python:
description: Skip Python
default: ''
required: false
Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

As noted, these changes allow check-spelling to bootstrap 30s faster

Copy link
Contributor

Choose a reason for hiding this comment

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

And we can probably use them in other workflows too. 👍

(No need to make that change in this PR, of course.)

FEATURE: 'management.cattle.io.feature',
GROUP: 'management.cattle.io.group',
KONTANIER_DRIVER: 'management.cattle.io.kontainerdriver',
KONTAINER_DRIVER: 'management.cattle.io.kontainerdriver',
Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

notable

Copy link
Contributor

Choose a reason for hiding this comment

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

And this will probably get clobbered next time we re-import the file from dashboard (we never use this).

check_file_names: 1
post_comment: 0
use_magic_file: 1
ignore-next-line: spell-checker:disable-next-line
Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

this won't do anything yet. It should be supported in the next version

// builderCacheProcessor implements the details for handling the argument for
// `nerdctl builder build --cache-from=...` and
// `nerdctl builder builder --cache-to=...`
// `nerdctl builder build --cache-to=...`
Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

notable. check-spelling didn't like this, but I don't think nerdctl did either...

@@ -0,0 +1,26 @@
{
Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

This file is used by the workflow (it has no dependencies).

I may end up providing a version of this in the check-spelling repository, as it seems reasonably close to something people might want.... I still need to think about how this should work.

Copy link
Contributor

Choose a reason for hiding this comment

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

This is basically there so yarn installdoesn't actually do much, right?
Is that needed, or can we get away with skipping .github/actions/yarn-install/action.yaml? (Just do setup-node without caching + corepack enable)

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

I have no idea. I didn't write the workflow bits that use it. I figured I could safely skip the bits I found I could skip, but I wasn't really sure whether it was a policy that yarn-install be used everywhere or....

-- I probably should have asked.

Copy link
Contributor

Choose a reason for hiding this comment

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

It was just there because we got tired of copying bits and pieces across different workflows (especially when we added things that were needed). In this case, I think it's fine to not use it.

@@ -0,0 +1,12 @@
# This file is generated by running "yarn install" inside your project.
Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

This corresponds to the package-spelling.json file.

@jsorefjsorefforce-pushed the refresh-check-spelling branch 2 times, most recently from 9479f52 to 8836427CompareDecember 11, 2025 16:42
Copy link
Contributor

@mook-asmook-as left a comment

Choose a reason for hiding this comment

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

I'll need to double check if we can skip the whole alternate package.json thing and just not run yarn install for check-spelling… otherwise it's mainly pretty trivial things.

You may want to just skip the files we import from dashboard though, or make PRs upstream.

I'll approve or request changes depending on how my experiments with package.json go.

\bgitlab\.[^/\s"]*/(?:[^/\s"]+/){2}commits?/[0-9a-f]+\b

# #includes
^\s*#include\s*(?:<.*?>|".*?")
Copy link
Contributor

Choose a reason for hiding this comment

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

Hmm, it would be nice if the patterns could be limited to specific file paths, so #includes only for *.h/*.c/*.hpp/*.cpp/*.cc. Same with uses: only in .github/**/*.yaml.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Yeah... It's a thing that comes up occasionally, but then I'd have to make the file format much more complicated.

\b2006-02-01\b

# Should probably have a trailing `.`
\s([a-z]\.){2,}[a-z]\s
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't see this being hit a lot (a.b.c instead of a.b.c., where all of those things are single-letters), but okay

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

I think the main complaint is a.k.a which should be a.k.a.. I'm not sure how often it'll be hit in general or in any particular repository, but, GitHub has 280k+ hits, so it's definitely worth including in the baseline.


# s.b. macOS or Mac OS X or ...
# Should be `Jira`
\bJIRA\b
Copy link
Contributor

Choose a reason for hiding this comment

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

Unless you're tracking things you are doing to manage Jira within itself. This should be \bJIRA\b(?!-\d+) or something along those lines, to avoid flagging JIRA-12345.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Thanks. I've fixed it in check-spelling/spell-check-this@9d03041 for the baseline.

# hit-count: 739 file-count: 6
# base64 encoded content, possibly wrapped in mime
(?:^|[\s=;:?])[-a-zA-Z=;:/0-9+]{50,}(?:[\s=;:?]|$)
NO_VOWELS:\s+'.+'
Copy link
Contributor

Choose a reason for hiding this comment

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

NO_VOWELS: 'bcdfghjklmnpqrstvwxz2456789',

That's from dashboard and we don't really care.

FEATURE: 'management.cattle.io.feature',
GROUP: 'management.cattle.io.group',
KONTANIER_DRIVER: 'management.cattle.io.kontainerdriver',
KONTAINER_DRIVER: 'management.cattle.io.kontainerdriver',
Copy link
Contributor

Choose a reason for hiding this comment

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

And this will probably get clobbered next time we re-import the file from dashboard (we never use this).

Copy link
Contributor

Choose a reason for hiding this comment

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

All the changes will probably be clobbered next time we re-import from dashboard.

You may be interested in pushing this to https://github.com/rancher/dashboard (specifically https://github.com/rancher/dashboard/blob/master/shell/components/SortableTable/index.vue ) but definitely extra; feel free to ignore.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Hmm, I sent them PRs in 2022. I suppose I could again....

Copy link
Contributor

Choose a reason for hiding this comment

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

Note that we (for the most part) don't actually use and translations; all of the changes here are for dashboard strings.

Comment on lines -199 to +200
// This removes it from the layout of ButtondropDown (so it doesn't render huge for SSR) but
// still allows it to maintain it's dimensions for v-tooltip to calculate the appropriate position.
// This removes it from the layout of ButtonDropDown (so it doesn't render huge for SSR) but
// still allows it to maintain its dimensions for v-tooltip to calculate the appropriate position.
Copy link
Contributor

Choose a reason for hiding this comment

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

I have no idea either, it's been here since the initial PoC stages. I suspect the rules aren't really doing anything useful.

Copy link
Contributor

@mook-asmook-as left a comment

Choose a reason for hiding this comment

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

Poked about it for a bit, and I think I prefer not having an extra package.json lying around.

My experiment was 6e5b6a7

The core is basically:

yq --inplace '.dependencies ={} | .devDependencies ={}' package.json rm -f yarn.lock corepack enable yarn yarn install --no-immutable --mode=skip-build

All that together is <5s, so that should be fine? It just ends up installing nothing (other than yarn itself), and skips the postinstall script to avoid failures. Installing cpanminus takes about 20s, and the spell check itself is about a minute.

jsorefand others added 25 commits December 11, 2025 19:30
Co-authored-by: Mark Yen <[email protected]> Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
jsorefand others added 18 commits December 11, 2025 19:30
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
Co-authored-by: Mark Yen <[email protected]> Signed-off-by: Josh Soref <[email protected]>
@jsorefjsorefforce-pushed the refresh-check-spelling branch from 3a466cd to f509117CompareDecember 12, 2025 01:06
Copy link
Contributor

@mook-asmook-as left a comment

Choose a reason for hiding this comment

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

Thanks for bearing with me on all the nit picks!

I'll note that this does not bump the version of check-spelling we use:

But that's probably a function of not having a release yet, and that's perfectly fine.

@mook-asmook-as enabled auto-merge December 12, 2025 01:24
@mook-asmook-as merged commit aff2928 into rancher-sandbox:mainDec 12, 2025
19 checks passed
@jsorefjsoref deleted the refresh-check-spelling branch December 12, 2025 03:52
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@jsoref@mook-as