Skip to content
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

Type Error with newest code #227

Closed
bphinney opened this issue Feb 18, 2015 · 6 comments
Closed

Type Error with newest code #227

bphinney opened this issue Feb 18, 2015 · 6 comments

Comments

@bphinney
Copy link
Contributor

Compiling Cookbooks...

Recipe Compile Error in /var/chef/cache/cookbooks/rabbitmq/libraries/default.rb

TypeError

Chef is not a module

Cookbook Trace:

/var/chef/cache/cookbooks/rabbitmq/libraries/default.rb:19:in `<top (required)>'

Relevant File Content:

/var/chef/cache/cookbooks/rabbitmq/libraries/default.rb:

12: # Unless required by applicable law or agreed to in writing, software
13: # distributed under the License is distributed on an "AS IS" BASIS,
14: # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
15: # See the License for the specific language governing permissions and
16: # limitations under the License.
17: #
18:
19>> module Chef Software
20: # module rabbit
21: module RabbitMQ
22: # This method does some of the yuckiness of formatting parameters properly
23: # for rendering into the rabbit.config template.
24: def format_kernel_parameters # rubocop:disable all
25: rendered = [] # rubocop:enable all
26: kernel = node['rabbitmq']['kernel'].dup
27:
28: # This parameter is special and needs commas instead of periods.

@cmluciano
Copy link

I think this is related to this commit. I believe that my PR#226 should fix this.

@bphinney
Copy link
Contributor Author

On 02/18/2015 11:09 AM, Chris L wrote:

I think this is related to this commit
1823240.
I believe that my PR#226
#226 should fix this.


Reply to this email directly or view it on GitHub
#227 (comment).

I agree.

@cmluciano
Copy link

I take that back, I think there is a nameclash. Opcode is probably not what we want to call it, but I think I should just revert to back to Opscode for now so that the module can be properly included.

@cmluciano
Copy link

Updated PR

@cmluciano
Copy link

@bphinney try the updated code now

@bphinney
Copy link
Contributor Author

@cmluciano - Yes it is working for me now, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants