Self hosted vercel instance gives maxDuration warning

[rickstaa]

Describe the bug

When I try to deploy the master branch on my self-hosted vercel instance (i.e. https://github.com/anuraghazra/github-readme-stats#deploy-on-your-own-vercel-instance) I get the following error:

The value for maxDuration must be between 1 second and 10 seconds, in order to increase this limit upgrade your plan: https://vercel.com/pricing

I did some debugging and this error has been present since 81b6593.

Expected behaviour

This error should not be present.

TODO

• We should document why this is happening.

[anuraghazra]

Open the vercel.json file and change the maxDuration to 10.

It's not a bug, it was intentionally reduced to 30s because by default on PRO plan it sets to 1min which is too high and was causing too much memory usage. but for non-pro users the duration can only be <10s thus 30s fails.

[anuraghazra]

There were two other users having the same confusion around this issue.

Maybe we should document that, after forking the repo for self-hosting they should change the duration to 10

[rickstaa]

@anuraghazra I think that is a good idea. I reopened the issue. Can you like the related issues?

[anuraghazra]

#1383
#1393

[rickstaa]

@anuraghazra Do you want me to update the documentation or are you doing it yourself? In the meantime allow me to create a commit that people can cherry-pick. I think it is nice to add this to the documentation.

[rickstaa]

People can cherry-pick 8af4544 to fix this issue.

[rickstaa]

@anuraghazra Ah, maybe you can create this commit on a new branch then remove the branch. In the current form, people have to use my fork. If that is too much work we can just document the behaviour.

[anuraghazra]

@anuraghazra Ah, maybe you can create this commit on a new branch then remove the branch. In the current form, people have to use my fork. If that is too much work we can just document the behaviour.

No there's no need to use your fork, it will create a two level dependency (on my fork -> your fork -> user's fork). We can just document the behaviour and also improve the error msg to exactly say what users have to do to fix the issue.

[anuraghazra]

The value for maxDuration must be between

@rickstaa does the error msg shows up on the rendered card itself or in a custom vercel error page?

[rickstaa]

@anuraghazra There were two places where the error showed up. In the vercel deployment log and as a GitHub notification since I use the github vercel app. The card itself is not displayed since the deployment fails. I temporarily broke my fork again to show the behaviour:

You can view this here.

[anuraghazra]

Oh yeah then we cannot show a custom msg, I thought the error was shown in the rendered card itself that way we could parse and replace the string. but not with this then.

I've added docs only.

[rickstaa]

@anuraghazra Thanks for your pull request! I think it is clear now.