Page MenuHomePhabricator

Change WikiLambda default configuration to work with docker-compose 2.x rather than docker-compose 1.x
Closed, ResolvedPublicBUG REPORT

Description

List of steps to reproduce (step by step, including full links if applicable):

  • I set up a new Wikilambda installation
  • Go to Special:ApiSandbox, run the first example for wikilambda_function_call

What happens?:

{
  "error": {
      "code": "wikilambda_function_call-not-connected",
      "info": "Could not resolve host 'mediawiki_function-orchestrator_1:6254', probably because the orchestrator is not running. Please consult the README to add the orchestrator to your docker-compose configuration.",
      "*": "See http://localhost:8080/w/api.php for API usage. 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."
  },
  "servedby": "f752be0b440e"
}

What should have happened instead?:
The function should be evaluated.

Software version (if not a Wikimedia wiki), browser information, screenshots, other information, etc:

Event Timeline

Docker lists that machine as mediawiki_function-orchestrator-1:6254 ( - instead of _ ), not sure if that makes a difference. Geno suggested to set it in the local extension json file.

I changed it from _ to - in the extension.json, and the error message changes accordingly but the situation did not improve.

{
  "error": {
      "code": "wikilambda_function_call-not-connected",
      "info": "Could not resolve host 'mediawiki_function-orchestrator-1:6254', probably because the orchestrator is not running. Please consult the README to add the orchestrator to your docker-compose configuration.",
      "*": "See http://localhost:8080/w/api.php for API usage. 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."
  },
  "servedby": "f752be0b440e"
}

Is there a way to check if my orchestrator is up and running at all?

We live-debugged this a bit today; there's a combination of issues, but mostly this is a docker-compose 1.x vs. 2.x config change. Boo.

Jdforrester-WMF changed the task status from Open to In Progress.Oct 14 2021, 4:59 PM
Jdforrester-WMF claimed this task.

Change 730860 had a related patch set uploaded (by Jforrester; author: Jforrester):

[mediawiki/extensions/WikiLambda@master] extension.json: Change docker-compose config for 2.x

https://gerrit.wikimedia.org/r/730860

Jdforrester-WMF renamed this task from Backend not connected on new Wikilambda installation to Change WikiLambda default configuration to work with docker-compose 2.x rather than docker-compose 1.x.Oct 20 2021, 4:18 PM

Change 730860 merged by jenkins-bot:

[mediawiki/extensions/WikiLambda@master] extension.json: Change docker-compose config for 2.x

https://gerrit.wikimedia.org/r/730860

Change 737134 had a related patch set uploaded (by Dr0ptp4kt; author: Dr0ptp4kt):

[mediawiki/extensions/WikiLambda@master] Suggest use of Docker Compose 2

https://gerrit.wikimedia.org/r/737134

Change 737134 merged by jenkins-bot:

[mediawiki/extensions/WikiLambda@master] README: Suggest use of Docker Compose v2

https://gerrit.wikimedia.org/r/737134