Jira (PUP-6979) Puppet Module List fails in code page 65001 on ja-JP windows

[Erick Banks (JIRA)]

Erick Banks created an issue

Puppet / PUP-6979 Puppet Module List fails in code page 65001 on ja-JP windows Issue Type: Bug Assignee: Unassigned Created: 2016/12/06 5:53 PM Environment: vmpooler win-2012r2-ja-x86_64 beaker 2.52.0 Labels: i18n windows Priority: Normal Reporter: Erick Banks Started a puppetlabs-dsc acceptance test run and RDP'd into the machine. Launched cmd and entered "> chcp 65001" then "puppet module list" Expect: a list of installed modules on the agent Actual: 661 puppet/face/module/search.rb 662 C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/terminal.rb 663 puppet/face/module/uninstall.rb 664 puppet/face/module/upgrade.rb 665 C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/face/module.rb   [NOTE] You may have encountered a bug in the Ruby interpreter or extension libraries. Bug reports are welcome. For details: http://www.ruby-lang.org/bugreport.html     This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information." Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Ethan Brown (JIRA)]

Ethan Brown commented on PUP-6979

Re: Puppet Module List fails in code page 65001 on ja-JP windows Could you include a full stack trace? There are a number of things that you have to do on Windows to get terminals to behave properly (including setting fonts, etc). So I want to make sure we're seeing bad Ruby / Puppet behavior, and not bad Windows behavior. Also, what happens in the normal codepage chcp 932? If this is deemed a critical issue, it should be added to PUP-6718. Otherwise, it probably belongs in PUP-6719

Add Comment

[Ethan Brown (JIRA)]

Ethan Brown updated an issue

Puppet / PUP-6979

Puppet Module List fails in code page 65001 on ja-JP windows

Change By: Ethan Brown Sprint: AP Triage

Add Comment

[Erick Banks (JIRA)]

Erick Banks commented on PUP-6979

Re: Puppet Module List fails in code page 65001 on ja-JP windows Thanks for looking at this Ethan Brown. I'm not familiar with terminal behavior and fonts, is there a confluence page or some other resource I can look at to come up to speed here? After which I can provide more context and the full stack trace if the problem is still reproducible while using the terminal with the correct font/setting. Using the default code page of 932 I get the expected results, it lists the modules correctly.

Add Comment

[Geoff Nichols (JIRA)]

Geoff Nichols updated an issue

Puppet / PUP-6979

Puppet Module List fails in code page 65001 on ja-JP windows

Change By: Geoff Nichols Sprint: AP Triage

Add Comment

[Erick Banks (JIRA)]

Erick Banks updated an issue

Puppet / PUP-6979 Puppet Module List fails in code page 65001 on ja-JP windows

Change By: Erick Banks Attachment: puppet module list japanese

Add Comment

[Erick Banks (JIRA)]

Erick Banks commented on PUP-6979

Re: Puppet Module List fails in code page 65001 on ja-JP windows Attached the full output for a "puppet module list --debug" while in code page 65001

Add Comment

[Ethan Brown (JIRA)]

Ethan Brown commented on PUP-6979

Re: Puppet Module List fails in code page 65001 on ja-JP windows

Erick Banks what you attached is a Ruby segfault. I didn't look too closely, but it's probably the same thing as PUP-5717 . What was the host OS?

Add Comment

[Erick Banks (JIRA)]

Erick Banks commented on PUP-6979

Re: Puppet Module List fails in code page 65001 on ja-JP windows

win-2012r2-ja-x86_64

Add Comment

[Ethan Brown (JIRA)]

Ethan Brown updated an issue

Puppet / PUP-6979

Puppet Module List fails in code page 65001 on ja-JP windows

Change By: Ethan Brown Sprint: Agent 2017-03-22

Add Comment

[Ethan Brown (JIRA)]

Ethan Brown commented on PUP-6979

Re: Puppet Module List fails in code page 65001 on ja-JP windows Ah yes, thanks Erick Banks... sorry I missed that in the environment info you had already entered. I wasn't initially sure if you were using vmpooler or a custom box.

Add Comment

[John Duarte (JIRA)]

John Duarte updated an issue

Puppet / PUP-6979

Puppet Module List fails in code page 65001 on ja-JP windows

Change By: John Duarte QA Risk Assessment: Needs Assessment Automate

Add Comment

[John Duarte (JIRA)]

John Duarte updated an issue

Puppet / PUP-6979 Puppet Module List fails in code page 65001 on ja-JP windows

Change By: John Duarte Labels: i18n  pmt  windows

Add Comment

[Geoff Nichols (JIRA)]

Geoff Nichols commented on PUP-6979

Re: Puppet Module List fails in code page 65001 on ja-JP windows Any chance this could be related to https://bugs.ruby-lang.org/issues/7758 ? /cc Josh Cooper

Add Comment

[Kenn Hussey (JIRA)]

Kenn Hussey updated an issue

Puppet / PUP-6979

Puppet Module List fails in code page 65001 on ja-JP windows

Change By: Kenn Hussey Sprint: Agent 2017-03-22 , Agent 2017-04-05

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper commented on PUP-6979

Re: Puppet Module List fails in code page 65001 on ja-JP windows Yep, definitely looks like the same issue I reported 4 years ago.

Add Comment

[Geoff Nichols (JIRA)]

Geoff Nichols updated an issue

Puppet / PUP-6979

Puppet Module List fails in code page 65001 on ja-JP windows

Change By: Geoff Nichols Sprint: Agent 2017-03-22, Agent  2017-04-05  Ready for Engineering

Add Comment

[John Duarte (JIRA)]

John Duarte updated an issue

Puppet / PUP-6979 Puppet Module List fails in code page 65001 on ja-JP windows

Change By: John Duarte Labels: i18n pmt  triaged  windows

Add Comment

[Josh Cooper (Jira)]

Josh Cooper commented on PUP-6979

Re: Puppet Module List fails in code page 65001 on ja-JP windows Given current priorities I'm going to close this as won't fix.

Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)