July 2021 - Pharo-users - lists.pharo.org

Re: How to handle (recover) from a ZnInvalidUTF8: Illegal continuation byte for utf-8 encoding error?

by Sven Van Caekenberghe

> On 20 Jul 2021, at 12:11, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > > >> El 20 jul 2021, a las 11:45, Sven Van Caekenberghe <sven(a)stfx.eu> escribiÃ³: >> >> >> >>> On 20 Jul 2021, at 11:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> Hi Tim, >>> >>> An introduction to this part of the system is in https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… [Character Encoding and Resource Meta Description] from the "Enterprise Pharo" book. >>> >>> The error means that a file that you try to read as UTF-8 does contain things that are invalid with respect to the UTF-8 standard. >>> >>> Are you sure the file is in UTF-8, maybe it is in ASCII, Latin-1 or something else ? >>> >>> It is possible to customise the encoding to something different than the default UTF-8. For non-UTF encoders, there is a strict/lenient option to disallow/allow illegal stuff (but then you will get these in your strings). >>> >>> I can show you how to do that if you want. >> >> '/var/log/system.log' asFileReference readStreamDo: [ :in | in upToEnd ]. >> >> '/var/log/system.log' asFileReference binaryReadStreamDo: [ :in | >> (ZnCharacterReadStream on: in encoding: #ascii) upToEnd ]. >> >> '/var/log/system.log' asFileReference binaryReadStreamDo: [ :in | >> (ZnCharacterReadStream on: in encoding: ZnCharacterEncoder ascii beLenient) upToEnd ]. > > There is also readStreamEncoded:[do:], which is a bit more concise but does the same :) Yes indeed ! >> HTH >> >>> Sven >>> >>>> On 20 Jul 2021, at 10:31, Tim Mackinnon <tim(a)testit.works> wrote: >>>> >>>> Hi - Iâm doing a bit of log file processing with Pharo - and Iâve hit an unexpected error and am wondering what the best way to approach it is. >>>> >>>> It seems that I have a log file that has unexpected characters, and so my readStream loop that reads lines gets an error: "ZnInvalidUTF8: Illegal continuation byte for utf-8 encodingâ. >>>> >>>> For some reason this file (unlike my others) seems to contain characters that it shouldnât - but what is the best way for me to continue processing? Should I be opening my files in a different way - or can I resume the error somehow- Iâm not familiar with this area of Pharo and am after a bit of advice. >>>> >>>> My code is like this (and I get the error when doing nextLine) >>>> >>>> >>>> parseStream: aFileStream with: aBlock >>>> | line items | >>>> [ (line := aFileStream nextLine) isNil ] >>>> whileFalse: [ >>>> items := $/ split: line. >>>> items size = 3 ifTrue: [aBlock value: items]] >>>> >>>> My stream is created like this: >>>> >>>> firmEfs := (pathName , '/' , firmName , '_files') asFileReference. >>>> details parseStream: firmEfs readStream. >>>> >>>> >>>> Should I be opening the stream a bit differently - or can I catch that encoding error and resume it with some safe character? >>>> >>>> Thanks for any help. >>>> >>>> Tim

July 20, 2021

Re: How to handle (recover) from a ZnInvalidUTF8: Illegal continuation byte for utf-8 encoding error?

by Guillermo Polito

> El 20 jul 2021, a las 11:45, Sven Van Caekenberghe <sven(a)stfx.eu> escribiÃ³: > > > >> On 20 Jul 2021, at 11:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Hi Tim, >> >> An introduction to this part of the system is in https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… [Character Encoding and Resource Meta Description] from the "Enterprise Pharo" book. >> >> The error means that a file that you try to read as UTF-8 does contain things that are invalid with respect to the UTF-8 standard. >> >> Are you sure the file is in UTF-8, maybe it is in ASCII, Latin-1 or something else ? >> >> It is possible to customise the encoding to something different than the default UTF-8. For non-UTF encoders, there is a strict/lenient option to disallow/allow illegal stuff (but then you will get these in your strings). >> >> I can show you how to do that if you want. > > '/var/log/system.log' asFileReference readStreamDo: [ :in | in upToEnd ]. > > '/var/log/system.log' asFileReference binaryReadStreamDo: [ :in | > (ZnCharacterReadStream on: in encoding: #ascii) upToEnd ]. > > '/var/log/system.log' asFileReference binaryReadStreamDo: [ :in | > (ZnCharacterReadStream on: in encoding: ZnCharacterEncoder ascii beLenient) upToEnd ]. There is also readStreamEncoded:[do:], which is a bit more concise but does the same :) > > HTH > >> Sven >> >>> On 20 Jul 2021, at 10:31, Tim Mackinnon <tim(a)testit.works> wrote: >>> >>> Hi - Iâm doing a bit of log file processing with Pharo - and Iâve hit an unexpected error and am wondering what the best way to approach it is. >>> >>> It seems that I have a log file that has unexpected characters, and so my readStream loop that reads lines gets an error: "ZnInvalidUTF8: Illegal continuation byte for utf-8 encodingâ. >>> >>> For some reason this file (unlike my others) seems to contain characters that it shouldnât - but what is the best way for me to continue processing? Should I be opening my files in a different way - or can I resume the error somehow- Iâm not familiar with this area of Pharo and am after a bit of advice. >>> >>> My code is like this (and I get the error when doing nextLine) >>> >>> >>> parseStream: aFileStream with: aBlock >>> | line items | >>> [ (line := aFileStream nextLine) isNil ] >>> whileFalse: [ >>> items := $/ split: line. >>> items size = 3 ifTrue: [aBlock value: items]] >>> >>> My stream is created like this: >>> >>> firmEfs := (pathName , '/' , firmName , '_files') asFileReference. >>> details parseStream: firmEfs readStream. >>> >>> >>> Should I be opening the stream a bit differently - or can I catch that encoding error and resume it with some safe character? >>> >>> Thanks for any help. >>> >>> Tim

July 20, 2021

Re: How to handle (recover) from a ZnInvalidUTF8: Illegal continuation byte for utf-8 encoding error?

by Sven Van Caekenberghe

> On 20 Jul 2021, at 11:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi Tim, > > An introduction to this part of the system is in https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… [Character Encoding and Resource Meta Description] from the "Enterprise Pharo" book. > > The error means that a file that you try to read as UTF-8 does contain things that are invalid with respect to the UTF-8 standard. > > Are you sure the file is in UTF-8, maybe it is in ASCII, Latin-1 or something else ? > > It is possible to customise the encoding to something different than the default UTF-8. For non-UTF encoders, there is a strict/lenient option to disallow/allow illegal stuff (but then you will get these in your strings). > > I can show you how to do that if you want. '/var/log/system.log' asFileReference readStreamDo: [ :in | in upToEnd ]. '/var/log/system.log' asFileReference binaryReadStreamDo: [ :in | (ZnCharacterReadStream on: in encoding: #ascii) upToEnd ]. '/var/log/system.log' asFileReference binaryReadStreamDo: [ :in | (ZnCharacterReadStream on: in encoding: ZnCharacterEncoder ascii beLenient) upToEnd ]. HTH > Sven > >> On 20 Jul 2021, at 10:31, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Hi - Iâm doing a bit of log file processing with Pharo - and Iâve hit an unexpected error and am wondering what the best way to approach it is. >> >> It seems that I have a log file that has unexpected characters, and so my readStream loop that reads lines gets an error: "ZnInvalidUTF8: Illegal continuation byte for utf-8 encodingâ. >> >> For some reason this file (unlike my others) seems to contain characters that it shouldnât - but what is the best way for me to continue processing? Should I be opening my files in a different way - or can I resume the error somehow- Iâm not familiar with this area of Pharo and am after a bit of advice. >> >> My code is like this (and I get the error when doing nextLine) >> >> >> parseStream: aFileStream with: aBlock >> | line items | >> [ (line := aFileStream nextLine) isNil ] >> whileFalse: [ >> items := $/ split: line. >> items size = 3 ifTrue: [aBlock value: items]] >> >> My stream is created like this: >> >> firmEfs := (pathName , '/' , firmName , '_files') asFileReference. >> details parseStream: firmEfs readStream. >> >> >> Should I be opening the stream a bit differently - or can I catch that encoding error and resume it with some safe character? >> >> Thanks for any help. >> >> Tim >

July 20, 2021

Re: How to handle (recover) from a ZnInvalidUTF8: Illegal continuation byte for utf-8 encoding error?

by Sven Van Caekenberghe

Hi Tim, An introduction to this part of the system is in https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… [Character Encoding and Resource Meta Description] from the "Enterprise Pharo" book. The error means that a file that you try to read as UTF-8 does contain things that are invalid with respect to the UTF-8 standard. Are you sure the file is in UTF-8, maybe it is in ASCII, Latin-1 or something else ? It is possible to customise the encoding to something different than the default UTF-8. For non-UTF encoders, there is a strict/lenient option to disallow/allow illegal stuff (but then you will get these in your strings). I can show you how to do that if you want. Sven > On 20 Jul 2021, at 10:31, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi - Iâm doing a bit of log file processing with Pharo - and Iâve hit an unexpected error and am wondering what the best way to approach it is. > > It seems that I have a log file that has unexpected characters, and so my readStream loop that reads lines gets an error: "ZnInvalidUTF8: Illegal continuation byte for utf-8 encodingâ. > > For some reason this file (unlike my others) seems to contain characters that it shouldnât - but what is the best way for me to continue processing? Should I be opening my files in a different way - or can I resume the error somehow- Iâm not familiar with this area of Pharo and am after a bit of advice. > > My code is like this (and I get the error when doing nextLine) > > > parseStream: aFileStream with: aBlock > | line items | > [ (line := aFileStream nextLine) isNil ] > whileFalse: [ > items := $/ split: line. > items size = 3 ifTrue: [aBlock value: items]] > > My stream is created like this: > > firmEfs := (pathName , '/' , firmName , '_files') asFileReference. > details parseStream: firmEfs readStream. > > > Should I be opening the stream a bit differently - or can I catch that encoding error and resume it with some safe character? > > Thanks for any help. > > Tim

July 20, 2021

How to handle (recover) from a ZnInvalidUTF8: Illegal continuation byte for utf-8 encoding error?

by Tim Mackinnon

Hi - Iâm doing a bit of log file processing with Pharo - and Iâve hit an unexpected error and am wondering what the best way to approach it is. It seems that I have a log file that has unexpected characters, and so my readStream loop that reads lines gets an error: "ZnInvalidUTF8: Illegal continuation byte for utf-8 encodingâ. For some reason this file (unlike my others) seems to contain characters that it shouldnât - but what is the best way for me to continue processing? Should I be opening my files in a different way - or can I resume the error somehow- Iâm not familiar with this area of Pharo and am after a bit of advice. My code is like this (and I get the error when doing nextLine) parseStream: aFileStream with: aBlock | line items | [ (line := aFileStream nextLine) isNil ] whileFalse: [ items := $/ split: line. items size = 3 ifTrue: [aBlock value: items]] My stream is created like this: firmEfs := (pathName , '/' , firmName , '_files') asFileReference. details parseStream: firmEfs readStream. Should I be opening the stream a bit differently - or can I catch that encoding error and resume it with some safe character? Thanks for any help. Tim

July 20, 2021

Re: Pharo 9.0 vm same-as Pharo 8.0 ?

by tesonep＠gmail.com

Thanks for the report, I will update the page. On Mon, Jul 19, 2021 at 6:34 PM Isaac Gouy via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > On Monday, July 19, 2021, 12:55:08 AM PDT, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > > > > that link is now obsolete in favour of pharo-vm-Linux-[ARCH]-stable.zip. > > > > > That "obsolete" link is still given in the section > > "Pharo standalone" > > on the page > > "https://pharo.org/download" > -- Pablo Tesone. tesonep(a)gmail.com

July 20, 2021

Re: Pharo 9.0 vm same-as Pharo 8.0 ?

by Isaac Gouy

On Monday, July 19, 2021, 12:55:08 AM PDT, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > that link is now obsolete in favour of pharo-vm-Linux-[ARCH]-stable.zip. That "obsolete" link is still given in the section Â Â Â "Pharo standalone" on the page Â Â Â "https://pharo.org/download"

July 19, 2021

Re: How to use Spec 2.0 with GTK in Pharo 9.

by Esteban Lorenzano

Hi Tau, the gtk backend does not comes loaded by default, you need to load it: Metacello new repository: 'github://pharo-spec/Spec-Gtk'; baseline: 'SpecGtk'; onConflict: [ :e | e useIncoming ]; onUpgrade: [ :e | e useIncoming ]; load. and of course, remember you need gtk3 in your system :) check here: https://github.com/pharo-spec/Spec-Gtk cheers! Esteban On Jul 19 2021, at 12:15 am, jbn126859530.7 <tau(a)cedalion.info> wrote: > > Hi. > > I'm learning Spec 2.0 with the help of the book "Building user interface with Spec 2.0". In section 2.17 of the book, the authors make a subclass of SpGtkConfiguration. However, no such class exists, only a SpMorphicConfiguration. Moreover, if I do something like: "app useBackend: #Gtk", I get a NotFound error. Again, "app useBackend: #Morphic" work as intended. As Pharo 9 annonced the availability of a GTK backend, I would like to know how to access it. > > Thanks. > > tau.

July 19, 2021

Re: Pharo 9 released - a brief experience report

by Guillermo Polito

Hi Yanni, Now vms are organised by architecture. The link to get the lastest vm for Darwin x86_64 is now https://files.pharo.org/get-files/90/pharo-vm-Darwin-x86_64-latest.zip Otherwise, we recommend using zeroconf or the pharo launcher, as they detect your machineâs architecture and download the right thing for you regardless of the link. Cheers, G > El 16 jul 2021, a las 18:17, Yanni Chiu <yannix7db(a)gmail.com> escribiÃ³: > > Thanks for updating the release. > > Iâve downloaded again using âcurl -L https://get.pharo.org/64/ | > bashâ, and Pharo 9.0.0 came up without problem. > > BTW, I noticed that the vm it downloaded today, was: > http://files.pharo.org/get-files/90/pharo-vm-Darwin-x86_64-stable.zip > > Yesterday, when I poked around some more, I decided to download: > https://files.pharo.org/get-files/90/pharo64-mac-headless-latest.zip > which looked to be newest available. > It mostly worked, but I got some debuggers when trying the Spec and > Spec2 examples (and even saw the dreaded pane with the X, which Iâve > not seen in years). With todayâs clean update, I only got one debugger > for the Spec âButtonsâ example. (Stack trace below). > ==== > KeyboardKey(Object)>>doesNotUnderstand: #asLowercase > ButtonPresenter>>addShortcutTipFor:on: > ButtonPresenter>>addShortcutTipFor: > ButtonPresenter>>label > MorphicButtonAdapter>>label > PluggableButtonMorph>>update: > PluggableButtonMorph>>on:getState:action:label:icon:menu: > PluggableButtonMorph class>>on:getState:action:label:menu: > MorphicButtonAdapter>>buildWidget > MorphicButtonAdapter(AbstractAdapter)>>adapt: > SpecInterpreter>>actionToPerformWithSelector:arguments: > SpecInterpreter>>performNextSelectorAndIncrementIndex > SpecInterpreter>>interpretASpec:selector: > SpecInterpreter>>interpretASpec:model:selector: > SpecInterpreter class>>private_interpretASpec:model:selector: > SpecInterpreter class>>private_buildWidgetFor:withSpec: > ButtonPresenter(ComposablePresenter)>>privateAdapterFromModel:withSpec: > ButtonPresenter(ComposablePresenter)>>private_buildWithSpec: > ButtonPresenter(ComposablePresenter)>>private_buildWithSpec > SpecInterpreter>>returnInterpretationOf: > SpecInterpreter>>interpretASpec:selector: > SpecInterpreter>>interpretASpec:model:selector: > SpecInterpreter class>>private_interpretASpec:model:selector: > SpecInterpreter>>computeSpecFrom:selector: > SpecInterpreter>>retrieveSpecFrom:selector: > SpecInterpreter>>interpretASpec:selector: > SpecInterpreter>>interpretASpec:model:selector: > SpecInterpreter class>>private_interpretASpec:model:selector: > [ :each | self class private_interpretASpec: each model: model > selector: spec selector ] in > SpecInterpreter>>performNextSelectorAndIncrementIndex in Block: [ > :each | self class private_interpretASpec: each ...etc... > Array(SequenceableCollection)>>collect:

July 19, 2021

Re: Pharo 9.0 vm same-as Pharo 8.0 ?

by Guillermo Polito

Hi Igouy, Kind of, yes. In Pharo9 we now support many different architectures, meaning that vms are not only compiled for 32/64 bits, but for aarch64 or x86-64. This means that link is now obsolete in favour of pharo-vm-Linux-[ARCH]-stable.zip. For example - pharo-vm-Linux-x86_64-stable.zip - pharo-vm-Linux-aarch64-stable.zip Regardless of that, one important point is that all files inside get-files are intended to be private to zeroconf and subject to change. The public download links are (as always) inside: https://files.pharo.org/vm/pharo-spur64/ Where for Pharo9 they are now organised by architecture too. Old versions (pre pharo9) are still there in the old places. G > El 16 jul 2021, a las 20:17, igouy2--- via Pharo-users <pharo-users(a)lists.pharo.org> escribiÃ³: > > Seems like the files from â > > https://files.pharo.org/get-files/90/pharo64-linux-stable.zip > > â are the same as Pharo 8.0 â > > 5.0-202002121043 Wed Feb 12 11:06:45 UTC 2020 gcc 5.4.0 [Production Spur 64-bit VM] > > > > Is that as-intended? >

July 19, 2021