Jira (PUP-6329) puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename
Title: Message Title Josh Cooper commented on PUP-6329 Re: puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename This is a dup of PUP-1890. URI.parse corrupts the string: (byebug) key "file:/tmp/foo/fo©.txt" (byebug) key.encoding # (byebug) URI.escape(key) "file:/tmp/foo/fo%C2%A9.txt" (byebug) URI.escape(key).encoding # Add Comment
Jira (PUP-6329) puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6329 puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename Change By: Kenn Hussey Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6329) puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename
Title: Message Title Greg Larkin commented on PUP-6329 Re: puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename Hi Ethan Brown, I just tried it again with the same result using version 4.9.4. I should have specified that I originally tested this on my Mac, and I just retested on the same machine. Here is the output: $ puppet apply /tmp/foo/fo©.txt WARN: Unresolved specs during Gem::Specification.reset: hiera (< 4, >= 2.0) WARN: Clearing out unresolved specs. Please report a bug if this causes problems. Notice: Compiled catalog for gregorys-mbp-2 in environment production in 0.11 seconds Notice: /Stage[main]/Main/File[/Users/glarkin/tmp]/ensure: created Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII
Jira (PUP-6329) puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename
Title: Message Title Greg Larkin updated an issue Puppet / PUP-6329 puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename Change By: Greg Larkin Affects Version/s: PUP 4.9.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6329) puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6329 puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename Change By: Ethan Brown Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6329) puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename
Title: Message Title Ethan Brown commented on PUP-6329 Re: puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename I suspect this is no longer a problem - needs repro. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6329) puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6329 puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename Change By: Ethan Brown Labels: i18n utf-8 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6329) puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6329 puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename Change By: Ethan Brown Labels: i18n triaged utf-8 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6329) puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename
Title: Message Title Henrik Lindberg commented on PUP-6329 Re: puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename ping @kylo and Chris Price Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6329) puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename
Title: Message Title
Greg Larkin created an issue
Puppet / PUP-6329
puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename
Issue Type:
Bug
Assignee:
Kylo Ginsberg
Components:
Client
Created:
2016/05/19 3:53 PM
Priority:
Normal
Reporter:
Greg Larkin
I created a file named /tmp/foo/fo©.txt with some text in it. Then I wrote the following manifest and invoked it with puppet apply:
file { '/Users/glarkin/tmp':
source => '/private/tmp/foo',
ensure => directory,
