MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Recovery_Limits",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "2428": {
                "pageid": 2428,
                "ns": 0,
                "title": "Reading config.log",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "<tt>config.log</tt> is the logfile for <tt>configure</tt>, which is a very long shell script.  When this script fails in unusual ways, it becomes necessary to look into <tt>config.log</tt>.  The file is in several sections:\n\n<pre>\nThis file contains any messages produced by compilers while\nrunning configure, to aid debugging if configure makes a mistake.\n\n....\n\n## --------- ##\n## Platform. ##\n## --------- ##\n\nhostname = euclid\n\n....\n\n## ----------- ##\n## Core tests. ##\n## ----------- ##\n\nconfigure:2815: checking build system type\nconfigure:2833: result: x86_64-unknown-linux-gnu\n\n...\n\n## ---------------- ##\n## Cache variables. ##\n## ---------------- ##\n\nac_cv_build=x86_64-unknown-linux-gnu\nac_cv_c_bigendian=no\nac_cv_c_compiler_gnu=yes\n\n....\n\n## ----------------- ##\n## Output variables. ##\n## ----------------- ##\n\nACLOCAL='${SHELL} /A/b/config/missing --run aclocal-1.10'\nAIX_BACKUP=''\n\n....\n\n## ----------- ##\n## confdefs.h. ##\n## ----------- ##\n\n#define PACKAGE_NAME \"\"\n#define PACKAGE_TARNAME \"\"\n\n....\n</pre>\n\nThe interesting material for a failure is usually at the end of \"Core tests,\" so use your editor to look for \"Cache variables\" and then scroll upward, just as you would scroll upward from the end of any log file."
                    }
                ]
            },
            "1805": {
                "pageid": 1805,
                "ns": 0,
                "title": "Recovery",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "=== Recover MySQL database ===\n\nRecovery of backups is done in two steps:\n\n==== Step 1 ====\n\nIdentify the backup image to be recovered by running a backup report ( ''restore-full-info'' ) that lists all backup images that are available:\n\n        # /usr/bin/mysql-zrm-reporter -show restore-info --where backup-set=dailyrun\n          backup_set  backup_date             backup_level  backup_directory\n          -------------------------------------------------------------------------------------------\n         dailyrun    Sun 10 Sep 2006                      0  /var/lib/mysql-zrm/dailyrun/\n               02:15:23 AM PDT                         20060910021523\n         dailyrun    Sun 17 Aug 2006                      0  /var/lib/mysql-zrm/dailyrun/\n               02:16:43 AM PDT                         20060917021643\n\n==== Step 2 ====\n\nUse [[mysql-zrm]] utility to recover the database from the full backup image.\n\n       # mysql-zrm --action restore --backup-set dailyrun \\\n                          --source-directory /var/lib/mysql-zrm/dailyrun/20060917021643\n       MySQL server has been shutdown. Please restart after verification.\n\nAfter restoring the database or tables in the database, it is important to [[Verifying_Restoration|verify the restored database contents]] before restarting the MySQL server."
                    }
                ]
            }
        }
    }
}