The error is related to that github origin erroneously submitted with a svn visit type.

Github only supports a small subset of svn client commands and svnrdump does not work for github repos.

(swh) anlambert@carnavalet:/tmp$ svnrdump dump https://github.com/cran/SCRABBLE
SVN-fs-dump-format-version: 3

UUID: 72fe256d-5aa7-4cf9-fc0d-ce57b7db7bff

Revision-number: 0
Prop-content-length: 104
Content-length: 104

K 10
git-commit
V 0

K 7
git-ref
V 0

K 10
svn:author
V 0

K 8
svn:date
V 0

K 7
svn:log
V 0

PROPS-END

* Dumped revision 0.
svnrdump: E200007: The requested report is unknown.

Nevertheless, that error should have been detected on the first loading so some adaptation is needed in the svn loader.

Thanks for the heads up ;)

In any case, independently from this, for the monitoring, I was set on modifying the
actual svn origin used to something else not hosted on github. I was of a mind to first
figuring out how to mirror, or at least fork some exising svn repository in our forge
and check that regularly with the monitoring [1]

So this goes in the direction of ridding oneself of such error ^.

[1] The monitoring's purpose being to check the plumbing is ok and not necessarily to
check the time it took to ingest an oversized repository. That's a variable out of our
control and I did not want flip flopping in the monitoring for no good reason...

In any case, independently from this, for the monitoring, I was set on modifying the
actual svn origin used to something else not hosted on github.

That check is now switched to another origin not hosted on github and those are reported
green by icinga.

Nevertheless, that error should have been detected on the first loading so some adaptation is needed in the svn loader.

That's the remaining part for this task to be closed.