-
Notifications
You must be signed in to change notification settings - Fork 170
inspec bug in chefdk 4.4.14 #2243
Comments
Not a bug. This was a problem with an invalid name in the directory (the emoji). |
@zmaupin I'd open it back. Nevermind the emojis, the problem probably stems from poor UTF-8 character handling and there might be proper use cases for UTF-8 path names. :) Cheers |
Reopening... |
@zmaupin are you seeing this with the released version of DK 4.4? |
Downloaded the latest Ubuntu Bionic release from https://downloads.chef.io/chefdk#ubuntu
|
This is very interesting that InSpec is the only one having an issue getting its version. Thanks for the report @zmaupin - getting this issue triaged |
@tyler-ball but are the other values coming in from shelling out, or from using constants already loaded? |
I do not have a repro on my side. That could be environment (I'm running inspec directly trying from a directory with an emoji name and with a PS1 that includes pwd) or ... I dunno. ruby versions? I highly highly doubt that's an issue. |
@zmaupin Can you try to update to ChefDK 4.5.0 and see if this still happens on that new release? It has an updated InSpec along with a bunch of other updates. |
Same with ChefDK 4.5.0
|
Description
Unable to use inspec in chefdk 4.4.14
ChefDK Version
Platform Version
chefdk docker container:
Replication Case
Startup container.
Run
chef --version
Or
Run
inspec --version
Or
With inspec verified in kitchen.yml use:
kitchen
with almost any command:Stacktrace
NOTE: CHEFDK BUGS ONLY
This issue tracker is for the code contained within this repo --
chefdk
.The text was updated successfully, but these errors were encountered: