luajit

expected result:
example.com?param=abc -> will become example.com
example.com/?param=abc -> will stay example.com/

actual result:
example.com?param=abc -> become example.com
example.com/?param=abc -> stays example.com/?param=abc

Description

Hi,
When I use openid-connect plugins with the wrong redirect_uri in Apache APISIX.

Like flow:

 "plugins":{
        "openid-connect":{
              ... 
            "scope":"openid profile",
            "bearer_only":false,
            "introspection_endpoint_auth_method":"client_secret_post",
            "redirect_uri":"http://127.0.0.1:9080/"
             .

Could it be possible to have a warning message when installing a rock that contains a module that is already provided by another rock? Or is there already an option for this and I didn't find it?

At least with Luarocks version 3.2.1 I verified that there are no warnings for this case.

However it seems that Luarocks is aware of the collision and installs the new module under another name and

local t = love.thread.newThread([[
error()
]])
t:start()

The above code doesn't show default love.threaderror as expected (or a custom set love.threaderror). Not a massive bug - but something to be aware of if no error message is given

Language request for Dart.