-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test case failure with Pongo run #333
Comments
Know issue with Kong 3.0.0, see Kong/kong#9337 (comment) |
that PR has 2 fixes in it, and after some internal discussion the 2nd fix was removed to keep it clean. But that is exactly the fix we need here. I am pushing to get this fixed though. |
As a workaround place your plugin files inside WSL home folder instead of accessing them on the Windows mount |
Since this issue is still open, I'd like add this here - I'm seeing this behavior in Kong 3.2.2 on macOS 13 using colima. This includes not seeing the issue on Kong 2.3.2. I understand that there's a fix in place since Oct 2022, but has anyone got this working on macOS with a non-Docker Desktop setup? |
@nitinthewiz just to verify, are you seeing this line in your logs;
That would indeed indicate it is the same issue (which hasn't been fixed yet, see my comment above) |
@Tieske Thanks for asking for a clarification. I was tracking multiple issues to find a resolution and "Invalid argument" is not the error I'm seeing. I'm seeing the following error - This seems to have been mentioned here, and by you here. I suppose it is not related to this issue. However, I don't see an issue tracking my error specifically. I suppose just like Vagrant, this needs an absolute path solution for colima on macOS (or perhaps a more generalized solution for macOS?) |
The solution would be to make the Unix socket location configurable, or move it to a more appropriate system based location. (that's a Kong change however, not a Pongo change) |
I was experiencing the same issue on Ubuntu 22.04 with As a temporary workaround, I managed to run kong:
image: ${KONG_TEST_IMAGE:-ignore_if_not_provided}
...
volumes:
- - ${PONGO_WD}:/kong-plugin
+ - /tmp/kong-plugin:/kong-plugin/servroot
+ - ${PONGO_WD}/spec:/kong-plugin/spec
+ - ${PONGO_WD}/kong:/kong-plugin/kong
+ - ${PONGO_WD}/.pongo:/kong-plugin/.pongo
+ - ${PONGO_WD}/.busted:/kong-plugin/.busted
+ - ${PONGO_WD}/.license-scripts:/kong-plugin/.license-scripts
+ - ${PONGO_WD}/kong-plugin-myplugin-0.1.0-1.rockspec:/kong-plugin/kong-plugin-myplugin-0.1.0-1.rockspec |
Based on @antoineauger solution, I've tested some configuration and I only needed the following:
|
@mfbmina Unfortunately, your simpler configuration did not work for my use case/tests. 😿 Some fixtures were not found: 2024/04/17 15:29:13 [error] 780#0: *1302 lua entry thread aborted: runtime error: content_by_lua(...ng_test_custom_inject_http.test.conf:141):2: module 'spec.fixtures.mock_upstream' not found:No LuaRocks module found for spec.fixtures.mock_upstream
no field package.preload['spec.fixtures.mock_upstream']
... |
As @mfbmina said, adding |
When I use the command
pongo run
I get the following errorThe following command
KONG_VERSION=2.3.2 pongo run
the expected outout would be something similar to this.The text was updated successfully, but these errors were encountered: