Spacy: CORS issue on Interactive matcher explorer

[visini]

How to reproduce the behaviour

Since a few days, I'm running into a CORS issue while accessing the interactive matcher explorer. The issue is persistent on any browser, device, OS, ...

Is this a known issue?

Your Environment

• Operating System: MacOS, Windows
• Browser: Any

[svlandeg]

Thanks for the report, that does look like a bug! We'll look into it.

[visini]

Thanks for the report, that does look like a bug! We'll look into it.

Thank you for your effort. This tool is incredibly useful for adjusting complex match patterns.

Some follow up info: All demos on https://explosion.ai/software#demos seem to be affected. Accessing /*/models (e.g., https://api.explosion.ai/matcher/models) returns 502 Bad Gateway.

Please don't hesitate to let me know what I can do to help in tracking down this issue. Cheers!

[eam17]

Having the same issue.
Is there any way to use the demo meanwhile, maybe locally?

[eam17]

@svlandeg is the code for the matcher on the GitHub too? I couldn't find it

[visini]

I don‘t believe the code for the matcher demo is open source... https://support.prodi.gy/t/rules-gui/2629/4

Any update on a fix, or some way to avoid this issue? Is only a portion of users affected?

[svlandeg]

We're working on a fix, and it's high up the priority list, but obviously not the only thing on that list ;-)

As a "workaround", you can just run the matcher from code: https://spacy.io/usage/rule-based-matching
If you want visualisations, you can run displacy locally with style="ent".

[visini]

I can confirm that the CORS issue is fixed as of today. Thank you very much for your effort!