Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error 'Failed to fetch Noto Sans JP from Google Fonts.' #45080

Closed
1 task done
max-ch9i opened this issue Jan 20, 2023 · 82 comments
Closed
1 task done

Error 'Failed to fetch Noto Sans JP from Google Fonts.' #45080

max-ch9i opened this issue Jan 20, 2023 · 82 comments
Labels
bug Issue was opened via the bug report template. locked

Comments

@max-ch9i
Copy link

max-ch9i commented Jan 20, 2023

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: Ubuntu 20.04.0 LTS Fri Jan 20 2023 09:56:57 GMT+0000 (Greenwich Mean Time)
Binaries:
  Node: 16.14.2
  npm: 7.17.0
  Yarn: 1.22.19
  pnpm: 7.13.6
Relevant packages:
  next: 13.1.3
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

Font optimization (@next/font)

Link to the code that reproduces this issue

https://stackblitz.com/edit/nextjs-qcjltu?file=app%2Fpage.js,package.json

To Reproduce

To reproduce, run npm run build.

Describe the Bug

Font input is

import { Noto_Sans_JP } from '@next/font/google';

const notoSansJapanese = Noto_Sans_JP({
  weight: '400',
  preload: false,
});

results in

Failed to compile.

app/page.js
`@next/font` error:
Failed to fetch `Noto Sans JP` from Google Fonts.

Possibly related to #44594
and 5f2c9d0

Expected Behavior

Compiles successfully.

@max-ch9i max-ch9i added the bug Issue was opened via the bug report template. label Jan 20, 2023
@pandaman64
Copy link

The error happens with other fonts such as Roboto:
https://stackblitz.com/edit/nextjs-xxuvuq?file=app/page.js

@pandaman64
Copy link

pandaman64 commented Jan 25, 2023

It looks like fetchFontFile function is failing with an error:

const arrayBuffer = await fetch(url).then((r: any) => r.arrayBuffer())

FetchError: request to https://fonts.gstatic.com/s/notosansjp/v42/-F62fjtqLzI2JPCgQBnw7HFowwII2lcnk-AFfrgQrvWXpdFg3KXxAMsKMbdN.5.woff2 failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (/path/to/node_modules/next/dist/compiled/node-fetch/index.js:1:65756)
    at ClientRequest.emit (node:events:513:28)
    at ClientRequest.emit (node:domain:489:12)
    at TLSSocket.socketErrorListener (node:_http_client:494:9)
    at TLSSocket.emit (node:events:513:28)
    at TLSSocket.emit (node:domain:489:12)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}

I can access the URL via the browser/curl, so I think it's not the internet connection issue.

@bazhenov
Copy link

Have the same issue with default create-next-app skeleton.

event - compiled client and server successfully in 745 ms (195 modules)
Error [NextFontError]: Failed to fetch `Inter` from Google Fonts.
    at nextFontError (/Users/bazhenov/Developer/foo/my-app/node_modules/@next/font/dist/utils.js:55:17)
    at downloadGoogleFonts (/Users/bazhenov/Developer/foo/my-app/node_modules/@next/font/dist/google/loader.js:87:39)
    at /Users/bazhenov/Developer/foo/my-app/node_modules/next/dist/build/webpack/loaders/next-font-loader/index.js:52:99
    at async Span.traceAsyncFn (/Users/bazhenov/Developer/foo/my-app/node_modules/next/dist/trace/trace.js:79:20)
error - Failed to download `Inter` from Google Fonts. Using fallback font instead.

Seems like a SSL related error. Running npx next dev/npx next build with NODE_TLS_REJECT_UNAUTHORIZED=0, but you should use it at your own risk. It's effectively disable SSL certificate validation ⚠️.

@Shahzad6077
Copy link

Hey @max-ch9i, did you get any workaround I'm also facing the same error.

@max-ch9i
Copy link
Author

@Shahzad6077 I just added font <link/>s into <head/> as instructed by Google Fonts.

@pandaman64
Copy link

pandaman64 commented Feb 1, 2023

Another workaround is downloading the fonts manually and using @next/font/local.

@Shahzad6077
Copy link

Shahzad6077 commented Feb 1, 2023

Yes I have downloaded the fonts locally and use @next/font/local but the font files are approx 27mb 😂

@max-ch9i
Copy link
Author

max-ch9i commented Feb 1, 2023

CSS files provided by Google Fonts (https://fonts.googleapis.com/css2?family=Noto+Sans+JP:wght@400&display=swap) have woff2 files split by unicode ranges. Downloading otf files and using @next/font/local is not an option for CJK.

@cannorin
Copy link

Removing the .next directory fixed the problem for me.

@pandaman64
Copy link

Hmm. The problem still occurs for me after removing .next.

@Dannymx
Copy link
Contributor

Dannymx commented Feb 26, 2023

Removing .next directory didn't fix it for me. Fails with 13.2.2-canary.1 and the new built-in font package.

@cannorin
Copy link

cannorin commented Mar 2, 2023

I've stumbled on this issue again after updating next to 13.2.3, and removing .next did fix the problem.

Here is my code, which, I suspect, should not be too different from anyone still having the problem:

import { Noto_Sans_JP } from "next/font/google";

const noto = Noto_Sans_JP({
  weight: ["400", "700"],
  preload: false, // https://github.com/vercel/next.js/pull/44594
});

So the other files than _app.tsx might be affecting I guess?

@Dannymx
Copy link
Contributor

Dannymx commented Mar 2, 2023

Strange, just a few days after I got the error, I didn't change anything (perhaps removed the .next folder again) but now the error is gone.

Nvm: error is back.

@AdamZajler
Copy link

I still have an issue :| Next 13.2.1

const roboto = Roboto({
  weight: ['300', '500', '700', '900'],
  subsets: ['latin'],
});

@ajdiyassin
Copy link

I have the same issue on: 13.2.4

@emmgfx
Copy link

emmgfx commented Mar 11, 2023

Same on 13.2.3

import { Inter, Yeseva_One } from "next/font/google";

const inter = Inter({
  subsets: ["latin"],
  variable: "--font-inter",
});

const yeseva_one = Yeseva_One({
  subsets: ["latin"],
  variable: "--font-yeseva-one",
  weight: ["400"],
});

And when I run npm run build:

Failed to compile.

src/pages/_app.js
`next/font` error:
Failed to fetch `Inter` from Google Fonts.

src/pages/_app.js
`next/font` error:
Failed to fetch `Yeseva One` from Google Fonts.

@emmgfx
Copy link

emmgfx commented Mar 11, 2023

Mmm... maybe it's a issue with the node version? When running npm run dev after removing the .next folder, I get this error:

ReferenceError: AbortController is not defined

Looking for AbortController, I've found that node includes it since 15.0.0 and I'm using 14.21.1. Which version are you all using?

@ucarno
Copy link

ucarno commented Mar 11, 2023

Which version are you all using?

I am on 18.3.0. Seems like an SSL error as bazhenov said, as NODE_TLS_REJECT_UNAUTHORIZED=0 is the only thing that helps

Edit: for some reason, error is back - even with the flag (which still helps in npm run build tho)

@emmgfx
Copy link

emmgfx commented Mar 11, 2023

Which version are you all using?

I am on 18.3.0. Seems like an SSL error as bazhenov said, as NODE_TLS_REJECT_UNAUTHORIZED=0 is the only thing that helps

Well, for me NODE_TLS_REJECT_UNAUTHORIZED=0 doesn't work, I get the same ReferenceError: AbortController is not defined.

Maybe there are two errors here 🤷

@emmgfx
Copy link

emmgfx commented Mar 14, 2023

Ups. I'm receiving this error again, but now deploying to Vercel.

import { Noto_Sans_Mono, Work_Sans } from "next/font/google";

const notoSansMono = Noto_Sans_Mono({
  subsets: ["latin"],
  variable: "--font-noto-sans-mono",
});

const workSans = Work_Sans({
  subsets: ["latin"],
  variable: "--font-work-sans",
});
ReferenceError: AbortController is not defined
08:48:15.480 | at fetchCSSFromGoogleFonts (/vercel/path0/node_modules/next/dist/compiled/@next/font/dist/google/fetch-css-from-google-fonts.js:34:28)
08:48:15.481 | at nextFontGoogleFontLoader (/vercel/path0/node_modules/next/dist/compiled/@next/font/dist/google/loader.js:76:79)
08:48:15.481 | at /vercel/path0/node_modules/next/dist/build/webpack/loaders/next-font-loader/index.js:72:99
08:48:15.481 | at async Span.traceAsyncFn (/vercel/path0/node_modules/next/dist/trace/trace.js:79:20)
08:48:15.482 | ReferenceError: AbortController is not defined
08:48:15.482 | at fetchCSSFromGoogleFonts (/vercel/path0/node_modules/next/dist/compiled/@next/font/dist/google/fetch-css-from-google-fonts.js:34:28)
08:48:15.482 | at nextFontGoogleFontLoader (/vercel/path0/node_modules/next/dist/compiled/@next/font/dist/google/loader.js:76:79)
08:48:15.482 | at /vercel/path0/node_modules/next/dist/build/webpack/loaders/next-font-loader/index.js:72:99
08:48:15.482 | at async Span.traceAsyncFn (/vercel/path0/node_modules/next/dist/trace/trace.js:79:20)
08:48:21.104 | Failed to compile.
08:48:21.105 |  
08:48:21.105 | pages/_app.js
08:48:21.105 | `next/font` error:
08:48:21.105 | Failed to fetch `Noto Sans Mono` from Google Fonts.
08:48:21.106 |  
08:48:21.106 | pages/_app.js
08:48:21.106 | `next/font` error:
08:48:21.106 | Failed to fetch `Work Sans` from Google Fonts.

@JavierMartinz
Copy link

@emmgfx are you using Node v14 by any chance? It was happening for us till yesterday. I tried with Node v16 and it worked like a charm!

@emmgfx
Copy link

emmgfx commented Mar 14, 2023

@emmgfx are you using Node v14 by any chance? It was happening for us till yesterday. I tried with Node v16 and it worked like a charm!

As I mentioned here, in my local I have node 14.21.1 (which apparently doesn't includes AbortController), but I think it's not the only error, because for me also fails when deploying to Vercel, and I can assume that they're using a node version compatible with his own product :P

@Mohamed-Abbas
Copy link

As mentioned upgrading node version then removing .next folder. Fixed the issue for me.

@jamestrenda
Copy link

Mmm... maybe it's a issue with the node version? When running npm run dev after removing the .next folder, I get this error:

ReferenceError: AbortController is not defined

Looking for AbortController, I've found that node includes it since 15.0.0 and I'm using 14.21.1. Which version are you all using?

Bingo! My code editor reverted back to an old version. running nvm use --lts resolved the issue.

@blazardsky
Copy link

upgrading node and removing .next did not work to me. Neither using lts. I only have this problem while running export not in dev or build alone

@arikchakma
Copy link

Upgrading the node version higher than 14 solved my problem.

@0xradical
Copy link

Upgrading the node version higher than 14 solved my problem.

I was running v18 and this was happening as well, so I wouldn't advise upgrading too far up until this is fixed. I'm now using v14 and the problem is gone.

@2manoj1
Copy link

2manoj1 commented Jun 17, 2023

Same issue in WSL ubuntu after upgrade also. Any fix?

@Rashmi-278
Copy link

For me, unstable internet connection was the issue, it didn't work locally but build passes on Vercel deployments

@dantevicenzo
Copy link

Here is how i managed to fix:

  1. run nvm install --lts
  2. run nvm use --lts
  3. delete .next folder

Done. Now i can run npm run dev without any errors.

kodiakhq bot pushed a commit that referenced this issue Jun 27, 2023
Improve the problems mentioned in #45080.

- Adding error retries (3 attempts) to font fetching. When you have a slow network, it might take >3s to load.
- Improve the error message to tell you that you might have unstable network connection.
- Do not cause build error (caused by missing `AbortController`) in Node 14 (even if we don't support Node 14, better to pass the build instead of hard error).
@shuding
Copy link
Member

shuding commented Jun 28, 2023

This issue will be fixed #51890. We now have retry logic when this fails, CLI errors that tell you about unstable network, and it's no longer depending on AbortController.

Let us know if you have other suggestions!

@thekidnamedkd
Copy link

thekidnamedkd commented Jul 7, 2023

Windows 10: WSL 2 -- Unbuntu 20.04
Node: 16.15.0
npm: 8.5.5
Next: 13.2.4 

I have a pretty reasonable connection, but would continually get this error in development. This seems to be an issue with the size of the fonts you want to use as I was having no problem with IBM-Plex-Mono at ~136kb per weight and lots of problems with Dongle at ~4775kb per weight, according to local file sizes after downloading from Google Fonts. Reconfigured to have Dongle in styles/fonts/ using localFont import from next/fonts/local in 'lib/fonts.ts' after much frustration and inconsistency using the next/fonts/google import and seems to be resolved. Here is my working code with Tailwind CSS vars:

lib/fonts.ts

import { IBM_Plex_Mono } from 'next/font/google';
import localFont from 'next/font/local';

export const plexmono = IBM_Plex_Mono({
  subsets: ['latin'],
  weight: ['100', '200', '300', '400', '500', '600', '700'],
  variable: '--font-plexmono',
});

export const dongle = localFont({
  src: [
    {
      path: '../styles/fonts/Dongle-Light.ttf',
      weight: '300',
      style: 'thin',
    },
    {
      path: '../styles/fonts/Dongle-Regular.ttf',
      weight: '400',
      style: 'normal',
    },
    {
      path: '../styles/fonts/Dongle-Bold.ttf',
      weight: '700',
      style: 'bold',
    },
  ],
  variable: '--font-dongle',
});

pages/_app.tsx

. . . 
<main className={`${dongle.variable} ${plexmono.variable}`}>
     <Layout>
            <Component {...pageProps} />
     </Layout>
</main>
. . . 

tailwind.config.js

theme: {
. . .
    },
    extend: {
      fontFamily: {
        body: ['var(--font-plexmono)'],
        heading: ['var(--font-dongle)'],
      },
. . .
}

@francisceril
Copy link

Was this ever solved?

This is hit and miss for me. Sometimes it just works then all of a sudden it doesn't work. Happens regardless of what font I use or what network I'm on.

If it may help.
node: 18.16.0
next: 13.4.10

@SehajBindra
Copy link

SehajBindra commented Jul 22, 2023

import { Poppins } from "next/font/google";

const poppins = Poppins({
  weight: ["300", "400", "500", "600", "700"],
  subsets: ["latin"],
  preload: false,
  style: ["normal"],

  display: "swap",
});`  

### for me, this worked set preload:false

@khalidmesbah
Copy link

this answer worked for me
https://stackoverflow.com/questions/76478043/next-js-always-fail-at-downloading-fonts-from-google-fonts

@qnrjs42
Copy link

qnrjs42 commented Jul 30, 2023

a temporary expedient

// in _app.tsx

/* eslint-disable react/no-unknown-property */

/* eslint-disable camelcase */
import { useTranslation } from 'next-i18next';
import { Noto_Sans_KR, Inter } from 'next/font/google';
import Head from 'next/head';

import type { LocaleType } from '@interfaces/default';

const notosansKR = Noto_Sans_KR({
  weight: ['100', '300', '400', '500', '700', '900'],
  display: 'auto',
  subsets: ['latin'],
  style: 'normal',
  variable: '--noto-sans_KR',
  preload: true,
});

const inter = Inter({
  weight: ['400', '700', '800'],
  subsets: ['latin'],
  display: 'fallback',
  fallback: ['-apple-system', 'sans-serif'],
});

const GlobalFont = ({ children }: { children: React.ReactNode }) => {
  const { i18n } = useTranslation('');

  const renderFontLink = (currentLocale: LocaleType): JSX.Element | null => {
    switch (currentLocale) {
      case 'ja':
        return (
          <link
            rel='stylesheet'
            href='https://fonts.googleapis.com/css2?family=Noto+Sans+JP:wght@100;300;400;500;700;900&display=swap'
          />
        );
      default:
        return null;
    }
  };

  return (
    <>
      <Head>
        <link rel='preconnect' href='https://fonts.googleapis.com' />
        <link rel='preconnect' href='https://fonts.gstatic.com' crossOrigin='' />

        {renderFontLink(i18n.language)}
      </Head>

      {process.env.NODE_ENV !== 'development' ? (
        <style jsx global>
          {`
            body {
              font-family: ${notosansKR.style.fontFamily}, 'Noto Sans JP', -apple-system, sans-serif;
            }

            .inter-font {
              font-family: ${inter.style.fontFamily};
            }
          `}
        </style>
      ) : null}

      {children}
    </>
  );
};

export default GlobalFont;
// in _app.tsx

import { css, Global } from '@emotion/react';

const GlobalStyles = (
  <Global
    styles={css`
      * {
        font-family: ${process.env.NODE_ENV === 'development'
          ? "'Noto Sans KR', 'Noto Sans JP', -apple-system, sans-serif;"
          : ''};
      }
      .inter-font {
        font-family: ${process.env.NODE_ENV === 'development'
          ? "'Inter', 'Noto Sans KR', sans-serif;"
          : ''};
      }
    `}
  />
);

export default GlobalStyles;

But, There is an issue with warnings in the browser console.

Do not add stylesheets using next/head (see <link rel="stylesheet"> tag with href="https://fonts.googleapis.com/css2?family=Noto+Sans+JP:wght@100;300;400;500;700;900&display=swap"). Use Document instead.

@adbutterfield
Copy link

Tangential to the original issue, but I made a package that nice when you need to work with Japanese fonts: https://www.npmjs.com/package/react-content-font

@Ianduha13
Copy link

Sorry if anyone already mentioned it but i found an interesting workaround trying to solve this problem:

import { Red_Hat_Display as redHatDisplay } from 'next/font/google'

Using the as keyword to rename the font I can forget about the issue

@Joblyn
Copy link

Joblyn commented Aug 6, 2023

This issue will be fixed #51890. We now have retry logic when this fails, CLI errors that tell you about unstable network, and it's no longer depending on AbortController.

Let us know if you have other suggestions!

@SehajBindra this error still persists with Poppins font.
I'm using next 13.4.10

----layout.tsx----

import './globals.scss'
import type { Metadata } from 'next'
import { Poppins } from 'next/font/google'

const poppins = Poppins({
  display: 'swap',
  weight: ['300', '400', '500', '700'],
  style: ['normal'],
  subsets: ['latin']
})

export const metadata: Metadata = {
  title: 'Xchange Next Door',
  description: 'Xchange Next Door'
}

export default function RootLayout ({
  children
}: {
  children: React.ReactNode
}) {
  return (
    <html lang='en'>
      <body className={poppins.className}>{children}</body>
    </html>
  )

----error----

error Failed to download 'Poppins' from Google Fonts. Using fallback font instead.
AbortError: The user aborted a request.

----package.json----

{
 ...
 "dependencies": {
   "@types/node": "20.4.2",
    "@types/react": "18.2.15",
    "@types/react-dom": "18.2.7",
    "autoprefixer": "10.4.14",
    "eslint": "8.45.0",
    "eslint-config-next": "13.4.10",
    "next": "13.4.10",
    "postcss": "8.4.26",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "styled-components": "^6.0.4",
    "swiper": "^10.0.4",
    "tailwind-scrollbar": "^3.0.4",
    "tailwindcss": "3.3.3",
    "typescript": "5.1.6"
 }
 ...
}

@nekofar
Copy link

nekofar commented Aug 10, 2023

I've encountered issues with different fonts bearing various names. This situation has been disrupting my development and continuous integration (CI) workflows. Despite the passage of several months, the most reliable solution I've found is to download the fonts and utilize them locally through next/font/local. 😞

@SehajBindra
Copy link

This issue will be fixed #51890. We now have retry logic when this fails, CLI errors that tell you about unstable network, and it's no longer depending on AbortController.
Let us know if you have other suggestions!

@SehajBindra this error still persists with Poppins font. I'm using next 13.4.10

----layout.tsx----

import './globals.scss'
import type { Metadata } from 'next'
import { Poppins } from 'next/font/google'

const poppins = Poppins({
  display: 'swap',
  weight: ['300', '400', '500', '700'],
  style: ['normal'],
  subsets: ['latin']
})

export const metadata: Metadata = {
  title: 'Xchange Next Door',
  description: 'Xchange Next Door'
}

export default function RootLayout ({
  children
}: {
  children: React.ReactNode
}) {
  return (
    <html lang='en'>
      <body className={poppins.className}>{children}</body>
    </html>
  )

----error----

error Failed to download 'Poppins' from Google Fonts. Using fallback font instead.
AbortError: The user aborted a request.

----package.json----

{
 ...
 "dependencies": {
   "@types/node": "20.4.2",
    "@types/react": "18.2.15",
    "@types/react-dom": "18.2.7",
    "autoprefixer": "10.4.14",
    "eslint": "8.45.0",
    "eslint-config-next": "13.4.10",
    "next": "13.4.10",
    "postcss": "8.4.26",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "styled-components": "^6.0.4",
    "swiper": "^10.0.4",
    "tailwind-scrollbar": "^3.0.4",
    "tailwindcss": "3.3.3",
    "typescript": "5.1.6"
 }
 ...
}

So Next js 13.4.13 recommends variable fonts for better optimization so after reading the the documentation I got the solution so in Poppins font weight prop is required and subsets is required when preload is set to true. So in weight prop you can only add two weight sizes as weight: '100 900' for a variable font.

for further check out the docs : https://nextjs.org/docs/pages/api-reference/components/font

This worked for me !!

const poppins = Poppins({
  weight: ["400", "700"],
  subsets: ["latin"],
});

@KrustyC
Copy link

KrustyC commented Aug 14, 2023

I keep experiencing this issue very intermittently. SOmetimes it loads all fonts, sometimes none, and sometimes only one (I am using 4 different fonts). I initially thought this was due to bad connectivity but I am experiencing this on a decent connection (>40Mbps) so I am sure that can not be the issue.

When I build the app on Vercel I get no issues so it is working fine in production, but in dev it makes it very difficult to work with, because everything looks ugly as it falls back to the default font.

For context I keep on seeing the following message

AbortError: The user aborted a request.
    at abort (/Users/{MAC_USER}/repos/sites/thescrapbookers.blog/node_modules/next/dist/compiled/node-fetch/index.js:1:65190)
    at EventTarget.abortAndFinalize (/Users/{MAC_USER}/repos/sites/thescrapbookers.blog/node_modules/next/dist/compiled/node-fetch/index.js:1:65410)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:731:20)
    at EventTarget.dispatchEvent (node:internal/event_target:673:26)
    at abortSignal (node:internal/abort_controller:308:10)
    at AbortController.abort (node:internal/abort_controller:338:5)
    at Timeout.<anonymous> (/Users/{MAC_USER}/repos/sites/thescrapbookers.blog/node_modules/next/dist/compiled/@next/font/dist/google/fetch-font-file.js:24:51)
    at listOnTimeout (node:internal/timers:564:17)
    at process.processTimers (node:internal/timers:507:7) {
  type: 'aborted'
}

@javierdev0
Copy link

I changed the node version, removed the .next folder and it worked.

My recommendation is to look if you have several versions of node installed and make sure you use the correct version, in this case for me version 18.12.1 worked.

My problem was that when I did node -v in the console, it printed the latest version installed on my computer but when I did an nvm ls, I realized that I was actually using another version and not the latest.

Before
Captura de pantalla 2023-08-16 155359

After
Captura de pantalla 2023-08-16 155455

@gidgudgod
Copy link
Contributor

restarting my internet connection (wi-fi) and deleting .next folder worked for me

@github-actions
Copy link
Contributor

github-actions bot commented Sep 3, 2023

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot added the locked label Sep 3, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template. locked
Projects
None yet
Development

No branches or pull requests