Tue, Jun 22
Mon, Jun 21
Thu, Jun 10
Hmm, I also notice that nothing is working at the moment. We've made a bunch of changes to the orchestrator recently, so I assume that's the reason. I will investigate today.
Wed, Jun 9
Hi, Gilles, a few questions/comments.
A proposal is underway.
Tue, Jun 8
Yes, I was mistaken yesterday. I am using wikilambda_fetch and it does what I need. Closing.
Mon, Jun 7
Yes, agreed. I am just wondering if the fallback instructions in the README can be made more clear.
Two questions on this:
Fri, Jun 4
The patch that fixed this was merged on June 2: https://gerrit.wikimedia.org/r/c/mediawiki/services/function-orchestrator/+/697692
Wed, Jun 2
Tue, Jun 1
Huh. Looks like the buster-node10js images are the culprit: the function-evaluator image isn't building at HEAD, but everything works if I use a different image. I guess that the version of Node packaged in those images doesn't work with some of our dependencies. This should have caused a ruckus and a din in function-evaluator CI. @Jdforrester-WMF, is there a way to get alerts when CI is failing in a repo?
Ignore previous comment :). I have replicated this with the latest builds. Investigating now.
Thu, May 27
Wed, May 26
Tue, May 25
Specifically, it would be very nice if we could influence the MW docker-compose configuration when testing the Wikilambda extension. This way, we could introduce other services (viz. function-orchestrator and function-evaluator) for purposes of integration testing.
May 14 2021
Yes, I think any of the below is fine: