Missing Total Commits depending on hide_border[I can't comment...]

[APN-Pucky]

[![Anurag's GitHub stats](https://github-readme-stats.vercel.app/api?username=APN-Pucky&show_icons=true&include_all_commits=true&theme=buefy&hide_border=true)](https://github.com/anuraghazra/github-readme-stats)

produces:

while

[![Anurag's GitHub stats](https://github-readme-stats.vercel.app/api?username=APN-Pucky&show_icons=true&include_all_commits=true&theme=buefy&hide_border=tru)](https://github.com/anuraghazra/github-readme-stats)

produces

The only difference is that the hide_border parameter needs to be misspelled for Total Commits to show up.

Image in case the live version changes:

EDIT: I just realized that this might just be due to some caching from Github.

[rickstaa]

@APN-Pucky Thanks for your question. I checked your syntax and everything seems fine because you use hide_border=tru instead of hide_border=true. Everything seems fine. I, therefore, don't thithe hide_border flag causes itlag. The most likely candidate for causing the commits to display as 0 is the include_all_commits flag. If this flag is enabled, we use the totalCommitsFetcher to get all the commits.

github-readme-stats/src/fetchers/stats-fetcher.js

Lines 68 to 98 in e9c55d9

	const totalCommitsFetcher = async (username) => {
	if (!githubUsernameRegex.test(username)) {
	logger.log("Invalid username");
	return 0;
	}
	// https://developer.github.com/v3/search/#search-commits
	const fetchTotalCommits = (variables, token) => {
	return axios({
	method: "get",
	url: `https://api.github.com/search/commits?q=author:${variables.login}`,
	headers: {
	"Content-Type": "application/json",
	Accept: "application/vnd.github.cloak-preview",
	Authorization: `token ${token}`,
	},
	});
	};
	try {
	let res = await retryer(fetchTotalCommits, { login: username });
	if (res.data.total_count) {
	return res.data.total_count;
	}
	} catch (err) {
	logger.log(err);
	// just return 0 if there is something wrong so that
	// we don't break the whole app
	return 0;
	}
	};

This function uses the Github Rest API instead of GitHub's GraphQl API. If this API throws an error, we return 0.

github-readme-stats/src/fetchers/stats-fetcher.js

Lines 93 to 96 in e9c55d9

	logger.log(err);
	// just return 0 if there is something wrong so that
	// we don't break the whole app
	return 0;

The best thing to do when you see this issue happen is to open the console and check which error is thrown. I hope that solves the problems you were having. Feel free to post the error below if the issue happens again.

[rickstaa]

Discussed in #1968

@rickstaa I edited my issue/discussion, but it is locked so I can't comment, but only edit my texts: I realized that this issues might just be due to some caching from Github.

This issue can be deleted/closed, but I wanted to notify you about this for future issues->discussion.