Jira (PDB-135) Improve warning message for invalid UTF-8 byte sequences

1 view
Skip to first unread message

Robin Bowes (JIRA)

unread,
Dec 18, 2014, 9:42:27 AM12/18/14
to puppe...@googlegroups.com
Robin Bowes commented on New Feature PDB-135
 
Re: Improve warning message for invalid UTF-8 byte sequences

Is anyone actively looking at this?

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Atlassian logo

Matthias (JIRA)

unread,
Jul 8, 2015, 1:11:16 PM7/8/15
to puppe...@googlegroups.com
Matthias commented on New Feature PDB-135

I took a look at this for my manifests. In my catalog, I had two issues: one was a utf-8 arrow in a comment of a config file, the other was a default favicon.ico that was distributed to newly created vhosts.

So, I did not have real problems with this one, but it took me a while to determine this. I will meditate a little about this, but I think it is possible to give better info that just this correct but unhelpful warning.

My idea so far is to extend the terminus so that details are logged into a file. I am leaning towards only keeping the last occurence, since puppet may run a lot and the output may include the better part of a catalog as json. Maybe it is sensible to keep the last occurence of each host. Either way, I would like to have this controllable from some config and note the output-file as another Puppet-warning. I will open a Pull-Request on github in the next days, hopefully.

This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Atlassian logo

Ryan Senior (JIRA)

unread,
Aug 25, 2015, 11:54:10 AM8/25/15
to puppe...@googlegroups.com
Ryan Senior updated an issue
 
PuppetDB / New Feature PDB-135
Change By: Ryan Senior
Sprint: PuppetDB 2015-09-09

Matthias Viehweger (JIRA)

unread,
Aug 26, 2015, 5:33:10 AM8/26/15
to puppe...@googlegroups.com
Matthias Viehweger commented on New Feature PDB-135
 
Re: Improve warning message for invalid UTF-8 byte sequences

should I try to reissue my PR to support you work?

This way, my previous research would not be wasted.

Ryan Senior (JIRA)

unread,
Aug 31, 2015, 2:49:10 PM8/31/15
to puppe...@googlegroups.com

Susan McNerney (JIRA)

unread,
Sep 9, 2015, 11:21:07 AM9/9/15
to puppe...@googlegroups.com
Susan McNerney updated an issue
Change By: Susan McNerney
Sprint: PuppetDB 2015-09-09 , PuppetDB 2015-09-23
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Atlassian logo

Kurt Wall (JIRA)

unread,
Sep 9, 2015, 9:12:05 PM9/9/15
to puppe...@googlegroups.com

Kurt Wall (JIRA)

unread,
Sep 9, 2015, 9:12:06 PM9/9/15
to puppe...@googlegroups.com
Kurt Wall updated an issue
Change By: Kurt Wall
QA Risk Assessment: Low

Kurt Wall (JIRA)

unread,
Sep 9, 2015, 9:13:03 PM9/9/15
to puppe...@googlegroups.com
Kurt Wall updated an issue
Change By: Kurt Wall
QA Risk Assessment Reason: Enhancement

Ryan Senior (JIRA)

unread,
Sep 11, 2015, 12:03:05 AM9/11/15
to puppe...@googlegroups.com
Ryan Senior commented on New Feature PDB-135
 
Re: Improve warning message for invalid UTF-8 byte sequences

Matthias Viehweger I have a PR up on this here. While digging into the problem, I found that we were generating that error message more times than we needed to. In the case of the arrow character (i.e. valid UTF-8, just not valid ASCII) we should be able to encode that properly and send it to PuppetDB. With my PR that should be happening. In the case of real binary data (your favicon example) we can not. In my PR, I sniff out those binary bytes, display the warning (now including the kind of command and the node it came from) and if you have debug logging enabled, it gives you some context around the binary data (i.e. 100 characters before the unencodable data, 100 characters after).

Would be great if you had some time to test out the fix once it gets merged in.

Ryan Senior (JIRA)

unread,
Sep 11, 2015, 12:03:06 AM9/11/15
to puppe...@googlegroups.com

Matthias Viehweger (JIRA)

unread,
Sep 11, 2015, 3:22:05 AM9/11/15
to puppe...@googlegroups.com
Matthias Viehweger commented on New Feature PDB-135
 
Re: Improve warning message for invalid UTF-8 byte sequences

It is always interesting to see other devs solve problems in a different way. Just from looking at code, your version seems more integrated (and less duck-tapey) than mine. Also, the context generation is more precise.

I will try this out next week. Since we still use puppetdb 2.3, I hope that just changing the terminus is enough.

Kenneth Barber (JIRA)

unread,
Oct 28, 2015, 3:56:08 PM10/28/15
to puppe...@googlegroups.com

Olivier Hanesse (JIRA)

unread,
Dec 11, 2015, 9:40:04 AM12/11/15
to puppe...@googlegroups.com
Olivier Hanesse commented on New Feature PDB-135
 
Re: Improve warning message for invalid UTF-8 byte sequences

Hello Everyone,

I think, there is a regression with PR #1640.
Indeed, using puppetdb-termini 3.2 (which includes this PR), puppetserver is "hanging" when sending catalog to PuppetDB. Catalog Compilation is working.

My catalog contains a binary file (a kerberos keytab in fact), that is the cause of the hanging.
If I use the "char_encoding.rb" file from version 3.1, sending catalog to puppetdb is working again.

Do you want me to open a new ticket ?

This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Atlassian logo

Kenneth Barber (JIRA)

unread,
Dec 11, 2015, 9:53:04 AM12/11/15
to puppe...@googlegroups.com
Kenneth Barber commented on New Feature PDB-135

Olivier Hanesse if you can open a new bug on the problematic version, that would be optimal. That way we can focus on the particular problem, this current ticket description and problems it solves are pretty generic. We'll probably want to see the binary file also, so we can replicate it, if thats at all possible, plus any exception thrown in the terminus that you might see.

Olivier Hanesse (JIRA)

unread,
Dec 13, 2015, 7:35:03 AM12/13/15
to puppe...@googlegroups.com

Claudia Petty (Jira)

unread,
Jun 21, 2023, 10:56:09 AM6/21/23
to puppe...@googlegroups.com
Claudia Petty updated an issue
 
Change By: Claudia Petty
Labels: new-feature redmine
This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages