-
Notifications
You must be signed in to change notification settings - Fork 25
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
New bug in v1.4.0-1, path.lua:501: attempt to concatenate a nil value #110
Comments
@rushikeshz97 on what platform are you experiencing this? Looks to me that issue could only occur on Windows? Have you tried setting up Nginx such that the |
Hmm, a failure example after version bump also found here: https://github.com/Kong/kong/actions/runs/8627721759/job/23648513062?pr=12846 It seems we need a penlight bump to solve the issue? (We might need to pin penlight version in dependency list to >= 1.14.0) |
yes, we'd need that. I have an open PR to check, and then I can probably cut a Penlight release. Are there required timelines? |
@Tieske We'll need this before the feature freeze of 3.7 of Kong gateway which should be 2 weeks later. |
Penlight release PR; lunarmodules/Penlight#472 |
Penlight |
/usr/local/share/lua/5.1/pl/path.lua:501: attempt to concatenate a nil value
stack traceback:
/usr/local/share/lua/5.1/pl/path.lua:501: in function 'expanduser'
/usr/local/share/lua/5.1/resty/aws/config.lua:240: in function 'load_config'
/usr/local/share/lua/5.1/resty/aws/config.lua:289: in function 'get_config'
/usr/local/share/lua/5.1/resty/aws/config.lua:350: in function '__index'
Hi this is a new issue we have encountered in your recent update 1.4.0. Seems to be caused by the change at resty/aws/config.lua:240, where you call pl_path.expanduser(env_vars.AWS_CONFIG_FILE.value).
Regards
Rushikesh
The text was updated successfully, but these errors were encountered: