This implements a toolforge-side proxy, that should help.

Update: Seems to work now, waiting for completion (it's been slow the last few days)

thanks!

If I change the manual https:// to http:// it works. These things should be clarified in the manual IMHO. Otherwise, this can be closed, works-for-me.

Ah, I understand this only works from within other jobs, not from the normal shell, which is a pity. Anyhow, I tried from a sehll webservice, and it still won't work, albeit with a different error:

tools.mix-n-match@shell-1776351170:~$ curl -v  'https://rustbot:8089/api?action=run_lua&function=PERSON_DATE&entry_id=205975229'
* Host rustbot:8089 was resolved.
* IPv6: (none)
* IPv4: 10.97.159.239
*   Trying 10.97.159.239:8089...
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* Send failure: Broken pipe
* TLSv1.3 (OUT), TLS alert, record overflow (534):
* TLS connect error: error:0A0000C6:SSL routines::packet length too long
* closing connection #0
curl: (35) Send failure: Broken pipe

FWIW I have now moved all my "active" tools from bitbucket to codeberg. Some archived old tools remain on bitbucket, for now

V2 should be fixed now

Oops, I'll fix it in V2

I have added the project.toml file to both my repo root and the tool root. Same thing.

I have implemented the idea of @Mahir256 in both PHP and Rust, and put everything live. Please test. Note that I might not be able to reply until tomorrow.

@Mahir256 Nice idea, let me try this

@VIGNERON The LAST after ADD_FORM referred to the FORM not to the Lexeme. This is indeed confusing, so I changed it to use LAST to refer to the last Lexeme created. Please try again (with a new Lexeme), it should work now. I also changed the docs accordingly.

I have added the required Lexeme fixes to both the PHP and the (back-end) Rust version. Specifics are here (not yet in the official help page). Can someone more familiar with Lexemes give it a whirl please, before I announce it to the general population?

IIRC full Lexeme support was postponed so we can start Lexemes on Wikidata "clean", and not as a mass import from Wiktionary or some copyright-dubious source. If we agree that Lexemes have reached critical mass, I can add Lexeme support to QuickStatements, unless you want to wait for that rewrite (who was doing this? Brasil?)