[MAGNOLIA-7098] special characters can sometimes lead to ReaderExceptions in YAML bootstrap Created: 25/Jul/17  Updated: 23/Aug/17  Resolved: 25/Jul/17

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.5.5
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Unassigned
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File readerexception.png    
Issue Links:
Relates
relates to MAGNOLIA-7118 YAML import uses platform encoding in... Closed
causality
relation
is related to MAGNOLIA-6683 Offer YAML as alternative format for ... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

It does not happen for everyone. However the boostrap file found here MGNLDEMO-219 can cause problems for some.



 Comments   
Comment by Cass Weber [ 25/Jul/17 ]

Solution

Edit ~/.profile and add:

export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8

To check, in Terminal type in:
locale

It should return:
LANG="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_CTYPE="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_ALL="en_US.UTF-8"

Comment by Richard Gange [ 25/Jul/17 ]

The issue was related to underlying UTF-8 settings on the machine. The JVM will use these settings as default.

Comment by Philip Mundt [ 23/Aug/17 ]

This clearly needs to be documented, cmeier wdyt?

Comment by Christoph Meier [ 23/Aug/17 ]

Sure, pmundt I can / will document it.
However, i'm, astonished that UTF-8 as default settings is not "sufficient" ... is that a bug in the snake-yaml parser?

Comment by Christoph Meier [ 23/Aug/17 ]

I have added a note to docs see https://goo.gl/nJ62k5

Generated at Mon Feb 12 04:20:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.