[docs][ci] bump versions of R-package dependencies at RTD

[StrikerRUS]

Fixed #4487.

[jameslamb]

Thanks for doing this, looks good to me! I checked the new docs from this and don't see any issues.

But for my own education...how did you figure out that upgrading the R dependencies was necessary to fix the problem? I don't see anything in the logs from the most recent failed build (https://readthedocs.org/api/v2/build/14324467.txt) that would have led me to that conclusion.

[StrikerRUS]

@jameslamb Yeah, there were no logs because we accumulate stdout and stderr first and then dump the combined result

LightGBM/docs/conf.py

Lines 286 to 301 in fdc582e

	try:
	# Warning! The following code can cause buffer overflows on RTD.
	# Consider suppressing output completely if RTD project silently fails.
	# Refer to https://github.com/svenevs/exhale
	# /blob/fe7644829057af622e467bb529db6c03a830da99/exhale/deploy.py#L99-L111
	process = Popen(['/bin/bash'],
	stdin=PIPE, stdout=PIPE, stderr=PIPE,
	universal_newlines=True)
	stdout, stderr = process.communicate(commands)
	output = '\n'.join([i for i in (stdout, stderr) if i is not None])
	if process.returncode != 0:
	raise RuntimeError(output)
	else:
	print(output)
	except BaseException as e:
	raise Exception(f"An error has occurred while generating documentation for R-package\n{e}")

But due to the time out error we didn't reach "dump" step.

First, I disabled R docs completely to narrow the root cause.
d332460
That build without R docs was successful and took only 100 seconds. After that I was sure that something is wrong with R-package installation or R docs generation process. Then I just started with the simplest idea of upgrading deps because I remember one case when some particular package build had been removed from anaconda.org repo instead of pushing new build number/hash.

[jameslamb]

Then I just started with the simplest idea of upgrading deps because I remember one case when some particular package build had been removed from anaconda.org repo instead of pushing new build number/hash.

ah ok great, thanks for the explanation!

[github-actions]

This pull request has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this.