-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Bug description
I ran: lazycommit.
Expected: a conventional commit message to be generated.
Actual: ✖ Groq API Error: 500 - Error
This probably occurred due to the Cloudflare outage.
Nothing much, just that the CLI mentioned to check the API status:

The error seems to originate here: groq.ts line 67
However, it does not work. (https://console.groq.com/status returns a 404)
Maybe update the link to: https://groqstatus.com/
lazycommit version
v1.0.17
Steps to reproduce
- Set up the Groq API.
- Stage some files in your repo.
- Run
lazycommit. - If there’s a server issue, an error will appear.
Environment
System:
OS: Windows 11 10.0.26100
CPU: (16) x64 12th Gen Intel(R) Core(TM) i5-12500H
Memory: 9.08 GB / 23.69 GB
Binaries:
Node: 25.2.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.22 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 11.6.2 - C:\Users\kuros\AppData\Roaming\npm\npm.CMD
pnpm: 10.22.0 - C:\Users\kuros\AppData\Roaming\npm\pnpm.CMD
bun: 1.3.0 - C:\Users\kuros\.bun\bin\bun.EXE
Deno: 2.5.6 - C:\Users\kuros\.deno\bin\deno.EXE
npmPackages:
@neondatabase/serverless: ^1.0.2 => 1.0.2
@studio-freight/lenis: ^1.0.42 => 1.0.42
@tailwindcss/typography: ^0.5.15 => 0.5.19
@types/node: ^22.14.0 => 22.19.0
@types/react: ^19.0.0 => 19.2.2
@types/react-dom: ^19.0.0 => 19.2.2
@types/react-syntax-highlighter: ^15.5.13 => 15.5.13
@vercel/analytics: ^1.3.1 => 1.5.0
autoprefixer: ^10.4.20 => 10.4.22
framer-motion: ^12.23.24 => 12.23.24
next: ^16.0.0 => 16.0.1
next-pwa: ^5.6.0 => 5.6.0
postcss: ^8.4.47 => 8.5.6
react: ^19.2.0 => 19.2.0
react-dom: ^19.2.0 => 19.2.0
react-markdown: 9.0.1 => 9.0.1
react-photo-view: ^1.2.7 => 1.2.7
react-syntax-highlighter: 15.5.0 => 15.5.0
rehype-unwrap-images: ^1.0.0 => 1.0.0
remark-gfm: 4.0.0 => 4.0.0
remark-rehype: ^11.1.2 => 11.1.2
swr: ^2.3.6 => 2.3.6
tailwindcss: ^3.4.1 => 3.4.18
typescript: ~5.8.2 => 5.8.3
vercel: ^48.10.2 => 48.10.2Groq API Configuration
No response
Error logs
Can you contribute a fix?
- I'm interested in opening a pull request for this issue.
- I can help test the fix once it's implemented.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working