Anthony Krivonos

@Myrfion Was losing my mind the past hour trying to figure out what was happening, looks like I'm not alone 🥵

Would love to see progress on this

## ⚠️ Please Reopen Having a similar issue; tried this solution and the many others on the Prisma forum and no luck. I have my `PRISMA_SECRET` configured in a `.env`...

Yep, my generated Prisma constructor looks exactly like this, and I have a `PRISMA_SECRET` set as an environment variable within the project. I've been able to replicate this issue with...

Thanks for the explanation, the `.env` variables are loaded just fine so that's not the issue. I understand the three layers I have for my Prisma server: database < graphql...

Bumping this too, my team would benefit from dynamic bucket functionality as we're storing data in both a public and private bucket. Great work here @DhenPadilla. Sorry to spam but...

@DhenPadilla Thanks for your blessed contribution. We couldn't wait any longer so we [created a fork](https://github.com/toma-so/next-s3-upload) with your changes. ``` yarn add @toma.so/next-s3-upload ```

The company that maintains TypeScript doesn't want to type its own code? Bumping because this is still an issue as 1.18.0 is the latest version.

@Nick8197 Thanks for opening this issue. Are you using a version of the Robinhood API that's unprovided with the repo? In this case, since `stock_portfolio` is a method I added...

Thanks for submitting the issue! I had a similar login error a couple hours ago––the Robinhood Python API uses a [client key](https://github.com/anthonykrivonos/Quantico/blob/master/ext_modules/Robinhood/Robinhood.py) that's shared amongst all users of the API...