-heroku | ps：记住把下面命令中的第一条中的you2php改成您的Github用户名， | Platform As A Service library

I am developing a NextJS application using next-auth with Google Oauth 2 as its authentication provider. The production build is running on Heroku. When attempting to sign in on my production build, Google OAuth is giving me "Error 400: redirect_uri_mismatch". Normally this would be an easy fix, except the exact uri is already registered in Cloud Console.

.

I have also tried added many different permutations of my uri, but this did not help.

This issue not solved by 11485271 or 69151061.

Error in question:

Error 400: redirect_uri_mismatch

You can't sign in to this app because it doesn't comply with Google's OAuth 2.0 policy.

If you're the app developer, register the redirect URI in the Google Cloud Console.

Request Details If you’re the app developer, make sure that these request details comply with Google policies. redirect_uri: https://middcourses2.herokuapp.com/api/auth/callback/google

And here is a link to the list of authorized domains in GCP.

I have a Heroku app that uses a psycopg server-side cursor together with a LEFT JOIN query running on Heroku PG 13.5.

The query basically says “fetch items from one table, that don’t appear in another table”.

My data volume is pretty stable, and this has been working well for some time.

This week these queries stopped returning. In pg_stat_activity they appeared as active indefinitely (17+ hours), similarly in heroku pg:ps. There appeared to be no deadlocks. All the Heroku database metrics and logs appeared healthy.

If I run the same queries directly in the console (without a cursor) they return in a few seconds.

I was able to get it working again in the cursor by making the query a bit more efficient (switching from LEFT JOIN to NOT EXISTS; dropping one of the joins).

My questions are:

• Why might the original query perform fine in the console, but not return with a psycopg server-side cursor?
• How might I debug this?
• What might have changed this week to trigger the issue?

I can say that:

• However I write the query (LEFT JOIN, Subquery, NOT EXISTS), the query plan involves a Nested Loop Anti Join
• I don’t believe this is related to the Heroku outage the following day (and which didn’t affect Heroku PG)
• Having Googled extensively, the closest thing I can find to a hypothesis to explain this is a post on the PG message boards from 2003 entitled left join in cursor where the response is “Some plan node types don't cope very well with being run backwards.”

Any advice appreciated!

I'm trying to use Gmail api in python to send email but I cant get past importing the Google module despite using "pip install --upgrade google-api-python-client" or "pip install google".

However pip freeze shows:

I'm trying to upload my first django app and I've been struggle with this issue for sometime, help is appreciated.

I already set up my project to be on heroku, I followed this tutorial: https://www.youtube.com/watch?v=6DI_7Zja8Zc in which django_heroku module is used to configure DB, here is the link to library https://pypi.org/project/django-heroku/

The app throws the error on login as if user tables didn't exist but I already create a super user using the heroku bash feature, after apply migrations using "heroku run python manage.py migrate". When I run "ls" command on heroku bash this is my directory:

manage.py Procfile requirements.txt runtime.txt smoke staticfile

"smoke" is my folder app, should I could see the db in this directory? if the db was not created how could I create a superuser using heroku bash feature?

This is the DB configuration that django gives me on server:

I have built a small app that I deployed to heroku. Locally, the whole thing is working as expected. But when deployed, the Network.webSocketFrameReceived event is never triggered. It is a node app that runs on express with a minimal websocket server. The goal of the app is to open some url using headless chrome (i am using puppeteer here), record the websocket frames and parse them if they contain some specific fields, close connection when successful. Then move to next url.

Gitlab fails to deploy to heroku when I push.

When I first encountered the issue I referred to this link for configuration guidance. however when I push gitlab throws a RuntimeError that "ensure adapter! ": An attempt to run a request with a Faraday:: Connection without adapter has been made. In the process of trying to fix the issue I landed on this repo. Can anyone enlighten me on this?

My CI/CD on gitlab deploy code on heroku using dpl. It have been working like a charm until a new version of faraday (I guess it is the reason) is fetch.

Here is what I had in my gitlab CI terminal when it worked (yesterday) :

I spent all day trying to use spaces to delivery static assets.

Tutorial1 with Cloudfront

Tutorial2 with Cloudfront

And it took me only 5 minutes to make it work on Cloudfront without any configuration except the domain name ... (l). Here is the configuration file on Cloudfront.

So I have gone through the forums in search for an answer but haven't found one that works for me. I am using Windows machine and my Django application works on Localhost but when I try to deploy the same application to Heroku it gives me this error.