oath | A programmer's oath -

So this is still not ideal, but using "expects.onCall" I can get the output I want

As mentioned by Despicable in comments, when you access the token, the response json conntains a field expires_in. Below is the screenshot of response json when I request for access token, the value of expires_in is 82799 in my side but it may be 3599(1 hour) in your side.

You can use ret_body['expires_in'] in your code to get the field.

============================Update================================

As you can only receive the access token but not any more fields, so you can parse(decode) the access token to get the expire date.

When we parse the token in this page for test, we can find there is a claim exp(in timestamp format) which means the expire date of the token. So we just need to parse the token and get the property exp, then convert it from timestamp to datetime.

Below is part of my code for your reference:

You can use the unnest_tokens() function from tidytext in combination with pivot_wider() from tidyr to get the count for each word in separate columns:

When searching for the word eaabcdgfa in your second board, your depth-first search algorithm:

• starts at the e in the centre, marks it as visited,
• finds an a in the centre-left, marks it as visited,
• finds an a in the bottom-left, marks it as visited,
• doesn't find a b next to the a in the bottom-left, so backtracks to the first a,
• finds another a in the top-left, marks it as visited,
• finds b, c, d, g and f around the edge of the board, marking them all as visited,
• is unable to add the a in the bottom left because it has been marked as visited.

The problem is that the a in the bottom-left was marked as visited despite it not being part of the route traced from the e at the centre to the f at the bottom-centre.

If you want the visited array to record the grid squares that have been visited by the current stack of recursive calls to checkOrder, then you need to mark grid squares as no longer visited before checkOrder ends. You can do this by adding the line

When you want to implement an OAuth2 system with CI4, you're free to making it however you want since nothing is already created to do so in the framework. Here it looks like you're using bshaffer oauth2 lib for PHP (try to read their cookbook. It personally helped me a lot implementing it in a CI4 project : https://bshaffer.github.io/oauth2-server-php-docs/cookbook).

First if you want to make a refresh token with this lib you have to add the refreshtoken grant type to your server.

Before making your call do a File.list to see which files the service account has access to. Doing a file.get on a file that the service account doesn't have access to will result in a file not found error. Remember that the service account is not you, it has its own google drive account. Any files you want to access need to be uploaded to its account or shared with the service account.

If the file.list fails then it would suggest to me that there is something wrong with the authorization and you should ensure that the service account has access to client file maybe its that file it cant find.

Create a directory on your personal google drive account. Take the service account email address, it can be found in the key file you downloaded it has a @ in it. Then share that directory on your drive account with the service account like you would share with any other user.

• Adding files to that directory may or may not give the service account access to them automatically permissions is a pain you may need to also share the file with the service account.
• Remember to have the service account grant your personal account permissions to the file when it uploads it its going to be the owner.

In response to your comment, yes, one table has no tfoot and one table only has a tfoot

Like this (also correcting for the missing <):

The PERL5LIB is a user's environment variable; the system's utility cron knows nothing about it.

Further, what you invoke from crontab mostly runs "out of" your home directory; this can depend on the system but it is generally not from where the script is. So then that place is the script's working directory.

Clearly the module Term::ReadLine::Gnu is installed in a non-standard location and when the script runs via cron it altogether cannot find that module (and perhaps yet others).

There are various ways about this

• Set PERL5LIB right on the command line in the crontab

Why you want to have custom OAuth consent page?

In order for you app to use one of Google's auth servers, your application needs some way to be identified by auth servers and that is where Client ID and Client Secret comes in to play and consent page server as a screen on which you application specific information such as application name, contact info, privacy policy, term of use etc. will be displayed to the user.

What are scopes that you define on consent screen setup?

On consent screen set up you are supposed to include all possible scopes that you application is going to request from Google APIs, but that doesn't mean you app is limited to those scopes only. Scope listed here will be used by Google for application verification purpose and once Google verifies you application, it will no longer display This app isn't verified warning page as long as your app is requesting one of those verified scopes.

Even after verification, if you application completes verification, requesting any scope access which isn't included in this list will still display This app isn't verified warning message.

and clicking on learn more link will open Google Account help page which clearly states once you provide access to application, when you allow third-party apps to access your Google Account, they can copy and save your data on their own servers. Because Google can’t protect the data on another company’s servers, your data may be subject to greater data security and privacy risks.

What is the purpose of having to define an OAuth consent screen and the API scope as a part of it when the app can request an arbitrary scope completely bypassing the scope selected in the OAuth consent screen setup?

The main purpose of the consent screen configuration is to allow app developer to present information about application it's terms and privacy policy during authorization process. And of course not to have warning once application is verified.

Please refer following link to better understand about unverified apps and scope verification:

1. https://support.google.com/cloud/answer/7454865?hl=en
2. https://support.google.com/cloud/answer/9110914
3. https://www.gmass.co/blog/five-annoying-issues-google-oauth-scope-verification/
4. https://support.google.com/accounts/answer/3466521?p=app_notverified&visit_id=637365968258169095-220403864&rd=2#notverified