My name is Cary and I work on the Groq developer experience team, mostly working on console.groq.com. I’m always looking to connect with our developers and hear about what you’re building with Groq and how you use the API and Console.
Please reach out with any feedback you might have. What ideas do you have for how we can improve Console. What is missing for you? What frustrations do you have? How can we better enable you to build fast and easy?
We have been using groq for 3 months now and want to applaud you and the team for improving errors that were happening with failed batches cancelling at the last minute, etc. The batching is so smooth now.
we interface with the console with a python script to manage all uploads and downloads so the download of each batch is preserved in its filename. This would be a great feature upload for those manually using the upload batch tool if the batch name when downloaded would be the same or similar to the upload name. This lessens confusion when dealing with several batches in a series.
I’m currently unable to access the Groq console at https://console.groq.com/home . Playground - GroqCloud works as normal.
When I attempt to load the page, I see a brief flash of what looks like a new console UI, but then the page fails to load and remains blank. It feels like I might be part of an A/B test for a new release that isn’t loading correctly.
I’ve opened the developer console and am seeing a critical RangeError followed by several Content-Security-Policy (CSP) violations.
RangeError: date value is not finite in DateTimeFormat.format()
NextJS 11
<anonymous code>:1:147461
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'”. Consider using a hash ('sha256-OQgsi5HyKNbEGQXOOgkh2TZkOkD7tqgfedE8bWVt5Rc=') or a nonce. content-script.js:4819:12
Content-Security-Policy: (Report-Only policy) The page’s settings would block an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'”. Consider using a hash ('sha256-OQgsi5HyKNbEGQXOOgkh2TZkOkD7tqgfedE8bWVt5Rc=') or a nonce. content-script.js:4819:12
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src https://m.stripe.network 'sha256-e357n1PxCJ8d03/QCSKaHFmHF1JADyvSHdSfshxM494=' 'sha256-5DA+a07wxWmEka9IdoWjSPVHb17Cp5284/lJzfbl8KA=' 'sha256-/5Guo2nzv5n/w6ukZpOBZOtTJBJPSkJ6mhHpnBgm3Ls='”. Consider using a hash ('sha256-OQgsi5HyKNbEGQXOOgkh2TZkOkD7tqgfedE8bWVt5Rc=') or a nonce. content-script.js:4819:12
I’ve tried running in incognito, but the issues persist.