ChefDK 1.2.22 version command is outputting extra data

[martinisoft]

Description

Running chef -v with ChefDK is outputting a lot of extra text plus the version numbers.

ChefDK Version

1.2.22

Platform Version

macOS Sierra 10.12.3

Replication Case

Simply run chef -v

Stacktrace

$ chef -v
Chef Development Kit Version: 1.2.22
chef-client version: (2017-02-02 17:30:04 0600) ... (0 (Took 0.000104 (2017-02-02 17:30:04 0600) 12.18.31
delivery version: master (0b746cafed65a9ea1a79de3cc546e7922de9187c)
berks version: 2017-02-02T17:30:05.465739 50471] 2017-02-02T17:30:05.465888 50471] 2017-02-02T17:30:05.465992 50471] 2017-02-02T17:30:05.466117 50471] 2017-02-02T17:30:05.495658 50471] 2017-02-02T17:30:05.495777 50471] 5.6.0
kitchen version: 1.15.0

I've run via irb some of the internal code which generates the version numbers and the berks version outputs this:

irb(main):004:0> require 'bundler'
=> true
irb(main):005:0> Bundler.with_clean_env { `berks --version` }
=> "W, [2017-02-02T17:34:51.513890 #52068]  WARN -- : You are setting a key that conflicts with a built-in method Hashie::Mash#frozen? defined in Kernel. This can cause unexpected behavior when accessing the key via as a property.You can still access the key via the #[] method.\nW, [2017-02-02T17:34:51.514036 #52068]  WARN -- : You are setting a key that conflicts with a built-in method Hashie::Mash#frozen? defined in Kernel. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method.\nW, [2017-02-02T17:34:51.514139 #52068]  WARN -- : You are setting a key that conflicts with a built-in method VariaModel::Attributes#frozen? defined in Kernel. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method.\nW, [2017-02-02T17:34:51.514232 #52068]  WARN -- : You are setting a key that conflicts with a built-in method VariaModel::Attributes#frozen? defined in Kernel. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method.\nW, [2017-02-02T17:34:51.546347 #52068]  WARN -- : You are setting a key that conflicts with a built-in method VariaModel::Attributes#default defined in Hash. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method.\nW, [2017-02-02T17:34:51.546465 #52068]  WARN -- : You are setting a key that conflicts with a built-in method VariaModel::Attributes#default defined in Hash. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method.\n5.6.0\n"

[stuartpreston]

Just to add this is also seen on Windows 10 with ChefDK 1.2.22

Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\Users\spreston> chef -v
Chef Development Kit Version: 1.2.22
chef-client version: 12.18.31
delivery version: master (0b746cafed65a9ea1a79de3cc546e7922de9187c)
berks version: 2017-02-03T00:03:47.798927 1068] 2017-02-03T00:03:47.798927 1068] 2017-02-03T00:03:47.798927 1068] 2017-02-03T00:03:47.798927 1068] 2017-02-03T00:03:47.861487 1068] 2017-02-03T00:03:47.861487 1068] 5.6.0
kitchen version: 1.15.0
PS C:\Users\spreston>

[oferrigni]

Confirmed on Mac OS 10.11

[lamont-granquist]

issue is with hashie, they're going to engineer a flag to turn it off.

[lamont-granquist]

berkshelf/berkshelf#1668

[lamont-granquist]

berkshelf/berkshelf#1668 should have addressed the problem

[oferrigni]

Don't you need to roll a new version before you can call it fixed?

[coredump]

Nvm. This fixed it:

chef gem install berkshelf

[lamont-granquist]

@oferrigni i did release a new berkshelf gem.

we close issues here when they're fixed, not when they're released, nobody goes back through issues and cleans them up after a release, that would just create litter and issues that were fixed, released and never closed.

[shortdudey123]

Related to berkshelf/ridley#366 and berkshelf/berkshelf#1665 that i created several days ago

[legal90]

chef gem install berkshelf

Sorry, but it doesn't help. The old version 5.6.0 is still using:

$ chef gem list berkshelf

*** LOCAL GEMS ***

berkshelf (5.6.4, 5.6.0)
berkshelf-api-client (3.0.0)

$ chef --version
Chef Development Kit Version: 1.2.22
chef-client version: 12.18.31
delivery version: master (0b746cafed65a9ea1a79de3cc546e7922de9187c)
berks version: 2017-03-31T17:59:21.789341 26234] 2017-03-31T17:59:21.789627 26234] 2017-03-31T17:59:21.789795 26234] 2017-03-31T17:59:21.789922 26234] 2017-03-31T17:59:21.846188 26234] 2017-03-31T17:59:21.846319 26234] 5.6.0
kitchen version: 1.15.0

$ berks --version
$ chef exec berks --version
W, [2017-03-31T18:00:00.097942 #26253]  WARN -- : You are setting a key that conflicts with a built-in method Hashie::Mash#frozen? defined in Kernel. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method.
W, [2017-03-31T18:00:00.098141 #26253]  WARN -- : You are setting a key that conflicts with a built-in method Hashie::Mash#frozen? defined in Kernel. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method.
W, [2017-03-31T18:00:00.098300 #26253]  WARN -- : You are setting a key that conflicts with a built-in method VariaModel::Attributes#frozen? defined in Kernel. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method.
W, [2017-03-31T18:00:00.098452 #26253]  WARN -- : You are setting a key that conflicts with a built-in method VariaModel::Attributes#frozen? defined in Kernel. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method.
W, [2017-03-31T18:00:00.141966 #26253]  WARN -- : You are setting a key that conflicts with a built-in method VariaModel::Attributes#default defined in Hash. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method.
W, [2017-03-31T18:00:00.142150 #26253]  WARN -- : You are setting a key that conflicts with a built-in method VariaModel::Attributes#default defined in Hash. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method.
5.6.0

Seems like "5.6.0" is pinned in ChefDK. The removal doesn't help. Any suggestions?