Pharo-users
By thread
pharo-users@lists.pharo.org
By month
Messages by month
- ----- 2026 -----
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
January 2018
- 82 participants
- 456 messages
Re: [Pharo-users] Problem with Traditional and Simplified Chinese parsing in Pharo
by Guillermo Polito
Are you sure that the file is encoded in utf8? Can you try
stream := ZnCharacterReadStream on: (File named: '...') readStream
encoding: 'utf8'.
stream upToEnd.
?
If that does not work, it could mean that the file is in another encoding...
2018-01-29 18:49 GMT+01:00 Clément Bera <bera.clement(a)gmail.com>:
> Hi,
>
> I am currently parsing lua and JSON-like file in Pharo. They contain both
> Simplified and Traditional Chinese characters for comments and for strings
> displayed in the UI. Lua files are parsed correctly. However the JSON-like
> files aren't.
>
> In attachment I put one of the problematic file with Simplified chinese
> characters (I've also copied the file at the end of the mail). The problem
> can be shown as follow in Pharo:
>
> 'schinese.txt' asFileReference readStream contents
>
> The contents function sends a UTF8InvalidText 'Invalid utf8 input
> detected' error.
> However my text editor correctly displays the file and it is correctly
> parsed by the Lua runtime (The program parsed has been deployed in
> production for years and works fine).
>
> What can I do to parse this file correctly from Pharo ?
>
> Thanks,
>
> Below is the file content, non Chinese people may not have the font to
> display the characters, note that I have no idea what is written in Chinese
> (Please don't hold me responsible if there are offending contents):
>
> "lang"
> {
> "Language" "Schinese"
> "Tokens"
> {
> "text_store_cd" "è´å£³ååºçåå伿¯å¤©éæºå·æ°! 䏿¬¡å·æ°å·å´æ¶é´"
> "text_cannot_huidaoguoqu" "ç°å¨ä¸è½ä½¿ç¨åå°è¿å»~"
> "tips1" "å©ç¨é¼ æ æ»è½®å¯ä»¥è°èè§è§è·ç¦»ï¼æ¹ä¾¿ä½ æ¥çåºå°å
¨è²~"
> "tips2" "éè¿å
¨é¨50å
³ä»¥åä½ è¿å¯ä»¥ç»§ç»æææ´å æé¾åº¦çæ å°½è¯ç¼æ¨¡å¼ï¼"
> "tips3" "æ¯å¤©æ©æ¨è´å£³ååºä¼éæºå·æ°åéæºææï¼çå¿ä½ æ³è¦çååï¼"
> "tips4" "æè¡æ¦çå25åå¯ä»¥è·å¾çå å¥ç« ï¼è±¡å¾çä½ å¨å¡é²æ¸¸æä¸çåè¶æç»©ï¼"
> "tips5" "æ¯10æ³¢æäººä¼æä¸ä¸ªBOSSå
³å¡ï¼å®æ¯æ®éæäººæ´é¾å»æ~"
> "tips6" "é£è¡çæäººä¸ä¼è¢«ç³å¤´é»æ¡ï¼æä»¥ä¸è½å©ç¨è¿·å®«æ¥å¢é¿æªç©ç线路~"
> "tips7" "å¼å±çæ¶åç¹å»å·¦ä¸æ¹çè±é鿩徿 å¯ä»¥æ¥çå¹¶éæ©ä½ æ¥æçè±éï¼"
> "tips8" "é身çæäººå¿
é¡»éè¿èç½ç³»åå¡çç
§æå
ç¯æè½è¢«åç°ï¼"
> "tips9" "ç¹å»å³ä¾§çåæå
¬å¼æé®å¯ä»¥æå¼åæé¢æ¿ï¼äºè§£é«çº§å¡çåæä»¥åå½åé
ä»¶ç¶æ~"
> "tips10" "é请好åä¸èµ·æ¸¸æï¼å¯ä»¥äºç¸åä½å
±å对æå¼ºå¤§çæäººï¼"
> "tips11" "ç³æ¿ä¼å¯¹è¸©ä¸å»çæäººäº§çææï¼æä»¥æå¥½æ¾ç½®å¨æäººå¿
ç»ç路线ä¸~"
> "tips12" "为è±éè´ä¹°ç¾ä¸½çç¹æï¼å½ä½ å¯ä»¥ä¸åååæçæ¶åææé
ä»¶é½ä¼æç¹ææç¤ºï¼"
> "tips13" "æ¯åå伤害æé«çå¡å°ä¼è·å¾æå¤10å±çMVPå
ç¯ï¼å¢å ç©çåéæ³è¾åºï¼"
> "tips14" "æ¯ä¸ªæçæåä¸å¤©æ¯èµå£ç»ç®æ¥ï¼å°ä¼æ ¹æ®ä½ è¿èµå£çæåé¢å丰åçè´å£³å¥å±ï¼"
> "tips15" "妿ä¸ç¥éææ ·é 迷宫ï¼ä½ å¯ä»¥ç¹å»å³ä¾§ç迷宫æåæé®æ¥çæè
å享æ¨èç迷宫~"
> }
> }
>
>
>
> --
> Clément Béra
> Pharo consortium engineer
> https://clementbera.wordpress.com/
> Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq
>
--
Guille Polito
Research Engineer
Centre de Recherche en Informatique, Signal et Automatique de Lille
CRIStAL - UMR 9189
French National Center for Scientific Research - *http://www.cnrs.fr
<http://www.cnrs.fr>*
*Web:* *http://guillep.github.io* <http://guillep.github.io>
*Phone: *+33 06 52 70 66 13
Jan. 29, 2018
Problem with Traditional and Simplified Chinese parsing in Pharo
by Clément Bera
Hi,
I am currently parsing lua and JSON-like file in Pharo. They contain both
Simplified and Traditional Chinese characters for comments and for strings
displayed in the UI. Lua files are parsed correctly. However the JSON-like
files aren't.
In attachment I put one of the problematic file with Simplified chinese
characters (I've also copied the file at the end of the mail). The problem
can be shown as follow in Pharo:
'schinese.txt' asFileReference readStream contents
The contents function sends a UTF8InvalidText 'Invalid utf8 input detected'
error.
However my text editor correctly displays the file and it is correctly
parsed by the Lua runtime (The program parsed has been deployed in
production for years and works fine).
What can I do to parse this file correctly from Pharo ?
Thanks,
Below is the file content, non Chinese people may not have the font to
display the characters, note that I have no idea what is written in Chinese
(Please don't hold me responsible if there are offending contents):
"lang"
{
"Language" "Schinese"
"Tokens"
{
"text_store_cd" "è´å£³ååºçåå伿¯å¤©éæºå·æ°! 䏿¬¡å·æ°å·å´æ¶é´"
"text_cannot_huidaoguoqu" "ç°å¨ä¸è½ä½¿ç¨åå°è¿å»~"
"tips1" "å©ç¨é¼ æ æ»è½®å¯ä»¥è°èè§è§è·ç¦»ï¼æ¹ä¾¿ä½ æ¥çåºå°å
¨è²~"
"tips2" "éè¿å
¨é¨50å
³ä»¥åä½ è¿å¯ä»¥ç»§ç»æææ´å æé¾åº¦çæ å°½è¯ç¼æ¨¡å¼ï¼"
"tips3" "æ¯å¤©æ©æ¨è´å£³ååºä¼éæºå·æ°åéæºææï¼çå¿ä½ æ³è¦çååï¼"
"tips4" "æè¡æ¦çå25åå¯ä»¥è·å¾çå å¥ç« ï¼è±¡å¾çä½ å¨å¡é²æ¸¸æä¸çåè¶æç»©ï¼"
"tips5" "æ¯10æ³¢æäººä¼æä¸ä¸ªBOSSå
³å¡ï¼å®æ¯æ®éæäººæ´é¾å»æ~"
"tips6" "é£è¡çæäººä¸ä¼è¢«ç³å¤´é»æ¡ï¼æä»¥ä¸è½å©ç¨è¿·å®«æ¥å¢é¿æªç©ç线路~"
"tips7" "å¼å±çæ¶åç¹å»å·¦ä¸æ¹çè±é鿩徿 å¯ä»¥æ¥çå¹¶éæ©ä½ æ¥æçè±éï¼"
"tips8" "é身çæäººå¿
é¡»éè¿èç½ç³»åå¡çç
§æå
ç¯æè½è¢«åç°ï¼"
"tips9" "ç¹å»å³ä¾§çåæå
¬å¼æé®å¯ä»¥æå¼åæé¢æ¿ï¼äºè§£é«çº§å¡çåæä»¥åå½åé
ä»¶ç¶æ~"
"tips10" "é请好åä¸èµ·æ¸¸æï¼å¯ä»¥äºç¸åä½å
±å对æå¼ºå¤§çæäººï¼"
"tips11" "ç³æ¿ä¼å¯¹è¸©ä¸å»çæäººäº§çææï¼æä»¥æå¥½æ¾ç½®å¨æäººå¿
ç»ç路线ä¸~"
"tips12" "为è±éè´ä¹°ç¾ä¸½çç¹æï¼å½ä½ å¯ä»¥ä¸åååæçæ¶åææé
ä»¶é½ä¼æç¹ææç¤ºï¼"
"tips13" "æ¯åå伤害æé«çå¡å°ä¼è·å¾æå¤10å±çMVPå
ç¯ï¼å¢å ç©çåéæ³è¾åºï¼"
"tips14" "æ¯ä¸ªæçæåä¸å¤©æ¯èµå£ç»ç®æ¥ï¼å°ä¼æ ¹æ®ä½ è¿èµå£çæåé¢å丰åçè´å£³å¥å±ï¼"
"tips15" "妿ä¸ç¥éææ ·é 迷宫ï¼ä½ å¯ä»¥ç¹å»å³ä¾§ç迷宫æåæé®æ¥çæè
å享æ¨èç迷宫~"
}
}
--
Clément Béra
Pharo consortium engineer
https://clementbera.wordpress.com/
Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq
Jan. 29, 2018
Re: [Pharo-users] P3 library - setting database in url?
by Sven Van Caekenberghe
> On 29 Jan 2018, at 15:45, Ben Coman <btc(a)openinworld.com> wrote:
>
> On 29 January 2018 at 22:40, Ben Coman <btc(a)openinworld.com> wrote:
>> On 29 January 2018 at 22:32, Sven Van Caekenberghe <sven(a)stfx.eu> wrote:
>>> Ben,
>>>
>>>> On 29 Jan 2018, at 15:27, Ben Coman <btc(a)openinworld.com> wrote:
>>>>
>>>> Hi Sven,
>>>>
>>>> I'm using your P3 library
>>>> https://github.com/svenvc/P3
>>>>
>>>> to connect to TimescaleDB set up like this tutorial...
>>>> http://docs.timescale.com/v0.8/tutorials/tutorial-hello-nyc
>>>
>>> Cool.
>>>
>>>> but the following doesn't work unless I un-comment the second line...
>>>> (P3Client new url:
>>>> 'psql://postgres:password@localhost:5432/nyc_data') in: [ :client |
>>>> [ " client database: 'nyc_data'. "
>>>> client query: 'SELECT date_trunc(''day'', pickup_datetime)
>>>> as day, avg(fare_amount)
>>>> FROM rides
>>>> WHERE passenger_count > 1 AND pickup_datetime < ''2016-01-08''
>>>> GROUP BY day ORDER BY day;'
>>>> ] ensure: [ client close ]
>>>> ].
>>>>
>>>> Is it supposed to work without the second line,
>>>> just with the database set in the url ?
>>>
>>> Yes, it is supposed to work like that. Did you try with the latest #reset patch (split settings/properties) ?
>>
>> Yes. This occurs after I tested the #reset patch. I "think" it was
>> occurring prior but my memory is not sure.
>
> Just checked, its the same behaviour prior to updating to the #reset patch.
For me,
(P3Client new url: 'psql://postgres:password@localhost:5432/nyc_data') database.
=> 'nyc_data'
You'll have to trace how it fails, see #startupMessage where #database is used setting up the connection.
>> cheers -ben
>>
>>>
>>> Sven
>>>
>>>> cheers -ben
>>>>
>>>>
>>>> P.S. TimescaleDB looks like cool tech...
>>>> https://blog.timescale.com/time-series-data-why-and-how-to-use-a-relational…
>>>>
>>>> Some notes for anyone wanting to try tutorial-hello-nyc...
>>>> a. Postgresql >9.6.3 is required, for which the default install on
>>>> Ubuntu 16.04 had a problem with libpq not being recent enough. I
>>>> needed to follow these steps...
>>>> https://askubuntu.com/questions/831292/how-to-install-postgresql-9-6-on-any…
>>>>
>>>> b. Downloading the sample data errored using the given "https" url,
>>>> but plain "http" worked...
>>>> http://timescaledata.blob.core.windows.net/datasets/nyc_data.tar.gz
Jan. 29, 2018
Re: [Pharo-users] P3 library - setting database in url?
by Ben Coman
On 29 January 2018 at 22:40, Ben Coman <btc(a)openinworld.com> wrote:
> On 29 January 2018 at 22:32, Sven Van Caekenberghe <sven(a)stfx.eu> wrote:
>> Ben,
>>
>>> On 29 Jan 2018, at 15:27, Ben Coman <btc(a)openinworld.com> wrote:
>>>
>>> Hi Sven,
>>>
>>> I'm using your P3 library
>>> https://github.com/svenvc/P3
>>>
>>> to connect to TimescaleDB set up like this tutorial...
>>> http://docs.timescale.com/v0.8/tutorials/tutorial-hello-nyc
>>
>> Cool.
>>
>>> but the following doesn't work unless I un-comment the second line...
>>> (P3Client new url:
>>> 'psql://postgres:password@localhost:5432/nyc_data') in: [ :client |
>>> [ " client database: 'nyc_data'. "
>>> client query: 'SELECT date_trunc(''day'', pickup_datetime)
>>> as day, avg(fare_amount)
>>> FROM rides
>>> WHERE passenger_count > 1 AND pickup_datetime < ''2016-01-08''
>>> GROUP BY day ORDER BY day;'
>>> ] ensure: [ client close ]
>>> ].
>>>
>>> Is it supposed to work without the second line,
>>> just with the database set in the url ?
>>
>> Yes, it is supposed to work like that. Did you try with the latest #reset patch (split settings/properties) ?
>
> Yes. This occurs after I tested the #reset patch. I "think" it was
> occurring prior but my memory is not sure.
Just checked, its the same behaviour prior to updating to the #reset patch.
>
> cheers -ben
>
>>
>> Sven
>>
>>> cheers -ben
>>>
>>>
>>> P.S. TimescaleDB looks like cool tech...
>>> https://blog.timescale.com/time-series-data-why-and-how-to-use-a-relational…
>>>
>>> Some notes for anyone wanting to try tutorial-hello-nyc...
>>> a. Postgresql >9.6.3 is required, for which the default install on
>>> Ubuntu 16.04 had a problem with libpq not being recent enough. I
>>> needed to follow these steps...
>>> https://askubuntu.com/questions/831292/how-to-install-postgresql-9-6-on-any…
>>>
>>> b. Downloading the sample data errored using the given "https" url,
>>> but plain "http" worked...
>>> http://timescaledata.blob.core.windows.net/datasets/nyc_data.tar.gz
>>>
>>
>>
Jan. 29, 2018
Re: [Pharo-users] P3 library - setting database in url?
by Ben Coman
On 29 January 2018 at 22:32, Sven Van Caekenberghe <sven(a)stfx.eu> wrote:
> Ben,
>
>> On 29 Jan 2018, at 15:27, Ben Coman <btc(a)openinworld.com> wrote:
>>
>> Hi Sven,
>>
>> I'm using your P3 library
>> https://github.com/svenvc/P3
>>
>> to connect to TimescaleDB set up like this tutorial...
>> http://docs.timescale.com/v0.8/tutorials/tutorial-hello-nyc
>
> Cool.
>
>> but the following doesn't work unless I un-comment the second line...
>> (P3Client new url:
>> 'psql://postgres:password@localhost:5432/nyc_data') in: [ :client |
>> [ " client database: 'nyc_data'. "
>> client query: 'SELECT date_trunc(''day'', pickup_datetime)
>> as day, avg(fare_amount)
>> FROM rides
>> WHERE passenger_count > 1 AND pickup_datetime < ''2016-01-08''
>> GROUP BY day ORDER BY day;'
>> ] ensure: [ client close ]
>> ].
>>
>> Is it supposed to work without the second line,
>> just with the database set in the url ?
>
> Yes, it is supposed to work like that. Did you try with the latest #reset patch (split settings/properties) ?
Yes. This occurs after I tested the #reset patch. I "think" it was
occurring prior but my memory is not sure.
cheers -ben
>
> Sven
>
>> cheers -ben
>>
>>
>> P.S. TimescaleDB looks like cool tech...
>> https://blog.timescale.com/time-series-data-why-and-how-to-use-a-relational…
>>
>> Some notes for anyone wanting to try tutorial-hello-nyc...
>> a. Postgresql >9.6.3 is required, for which the default install on
>> Ubuntu 16.04 had a problem with libpq not being recent enough. I
>> needed to follow these steps...
>> https://askubuntu.com/questions/831292/how-to-install-postgresql-9-6-on-any…
>>
>> b. Downloading the sample data errored using the given "https" url,
>> but plain "http" worked...
>> http://timescaledata.blob.core.windows.net/datasets/nyc_data.tar.gz
>>
>
>
Jan. 29, 2018
Re: [Pharo-users] P3 library - setting database in url?
by Sven Van Caekenberghe
Ben,
> On 29 Jan 2018, at 15:27, Ben Coman <btc(a)openinworld.com> wrote:
>
> Hi Sven,
>
> I'm using your P3 library
> https://github.com/svenvc/P3
>
> to connect to TimescaleDB set up like this tutorial...
> http://docs.timescale.com/v0.8/tutorials/tutorial-hello-nyc
Cool.
> but the following doesn't work unless I un-comment the second line...
> (P3Client new url:
> 'psql://postgres:password@localhost:5432/nyc_data') in: [ :client |
> [ " client database: 'nyc_data'. "
> client query: 'SELECT date_trunc(''day'', pickup_datetime)
> as day, avg(fare_amount)
> FROM rides
> WHERE passenger_count > 1 AND pickup_datetime < ''2016-01-08''
> GROUP BY day ORDER BY day;'
> ] ensure: [ client close ]
> ].
>
> Is it supposed to work without the second line,
> just with the database set in the url ?
Yes, it is supposed to work like that. Did you try with the latest #reset patch (split settings/properties) ?
Sven
> cheers -ben
>
>
> P.S. TimescaleDB looks like cool tech...
> https://blog.timescale.com/time-series-data-why-and-how-to-use-a-relational…
>
> Some notes for anyone wanting to try tutorial-hello-nyc...
> a. Postgresql >9.6.3 is required, for which the default install on
> Ubuntu 16.04 had a problem with libpq not being recent enough. I
> needed to follow these steps...
> https://askubuntu.com/questions/831292/how-to-install-postgresql-9-6-on-any…
>
> b. Downloading the sample data errored using the given "https" url,
> but plain "http" worked...
> http://timescaledata.blob.core.windows.net/datasets/nyc_data.tar.gz
>
Jan. 29, 2018
P3 library - setting database in url?
by Ben Coman
Hi Sven,
I'm using your P3 library
https://github.com/svenvc/P3
to connect to TimescaleDB set up like this tutorial...
http://docs.timescale.com/v0.8/tutorials/tutorial-hello-nyc
but the following doesn't work unless I un-comment the second line...
(P3Client new url:
'psql://postgres:password@localhost:5432/nyc_data') in: [ :client |
[ " client database: 'nyc_data'. "
client query: 'SELECT date_trunc(''day'', pickup_datetime)
as day, avg(fare_amount)
FROM rides
WHERE passenger_count > 1 AND pickup_datetime < ''2016-01-08''
GROUP BY day ORDER BY day;'
] ensure: [ client close ]
].
Is it supposed to work without the second line,
just with the database set in the url ?
cheers -ben
P.S. TimescaleDB looks like cool tech...
https://blog.timescale.com/time-series-data-why-and-how-to-use-a-relational…
Some notes for anyone wanting to try tutorial-hello-nyc...
a. Postgresql >9.6.3 is required, for which the default install on
Ubuntu 16.04 had a problem with libpq not being recent enough. I
needed to follow these steps...
https://askubuntu.com/questions/831292/how-to-install-postgresql-9-6-on-any…
b. Downloading the sample data errored using the given "https" url,
but plain "http" worked...
http://timescaledata.blob.core.windows.net/datasets/nyc_data.tar.gz
Jan. 29, 2018
Re: [Pharo-users] Download pillar image -> Error 403: Forbidden
by Guillermo Polito
On Mon, Jan 29, 2018 at 6:52 AM, Hernán Morales Durand <
hernan.morales(a)gmail.com> wrote:
> 2018-01-28 18:55 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>:
> > Hernan
> >
> > what we can also do is the following: I set up the pillar project on
> > github with travis and bintray and when you commit
> > the book is automatically built.
> >
>
> Ok, I would try that way.
>
> >
> >> Tried both options, 1) downloading pre-compiled and 2) building from
> >> sources+setting up environment.
> >> 1) Nothing happened after "pillar archetype build", exit without
> >> error, no stdout output, no _result folder
> >
> > this is super strange. We should check the AppVeyor because it should
> > tell us what is not working on windows.
> >
> >> 2) I got confused with this:
> >>
> >> mv pillar ~/.pillar
> >
> > the idea was that once you get pillar on linux/mac we move the
> > donwloaded version into ~./pillar
> > so that after we have only one pillar installation for all the books
> > (contrary to what is done in Pillar 50 and 60).
> >
> > here is what I get in my .pillar
> >
> > cd build
> >
>
> A-ha, that's the thing. My build/ is created one level up and not
> inside .pillar/
>
> > ~/.pillar/build(newpipeline*) » ls
> > Pharo.changes mustache pharo-ui pillar-db
> > Pharo.image pharo pharo-vm pillar-dev-upgrade
> > archetypes pharo-local pillar pillar-upgrade
> >
>
> Another difference, you seem to have the wrapper scripts in build/
>
> ~/.pillar/build (newpipeline) $ ls
> pharo* Pharo.changes Pharo.image PharoDebug.log pharo-local/
> pharo-ui* pharo-vm/ stderr stdout
>
>
> > and
> >
> > cd pillar
> >
> > ~/.pillar/pillar(newpipeline*) » ls
> > LICENSE README.md archetypes scripts src
> >
>
> ~/.pillar (newpipeline) $ ls
> archetypes/ build/ LICENSE README.md scripts/ src/
>
>
> >> because now I have two directories: the .pillar in HOME and the build/
> >> directory separated. And no "pillar" shell script so should I copy the
> >> one from 1) ?
> >
> >
> >
> >
> >
> >
> >> I will re-check tomorrow maybe I'm reading this the wrong way.
> >>
>
> So I checked, and discovered that the build image hasn't installed
> Pillar because there wasn't installed any command handler for
> introspect
> Invalid arguments: "pillar introspect
> --baseDirectory=C:/Users/mvs/.pillar mainDocument" [
>
> The build.sh installs Pillar as follows through a magic variable:
>
> Metacello new
> baseline: 'Pillar';
> repository:
> 'filetree:///c/MySmalltalkProjects/Pillar/Latest/pillar/scripts/../src';
> load.
>
> But gives a SubscriptOutOfBounds: 2 because
> WindowsStore>>printPath:on: expects "c:"
> (I would love a better error description in stdout file "Invalid
> arguments" is not that informative)
>
> Another load error is that BaselineOfPillar is installing OSSubprocess
> and it doesn't work on Windows (#externalCallFailed).
>
> Should I open issue?
>
And that, is because I was holding windows support from integration in a
separate branch.
https://github.com/pillar-markup/pillar/pull/183
I did not want to integrate it yet because for some reason AppVeyor builds
were failing the integration tests in pharo 61 and I couldn't grasp why nor
reproduce it locally (but strangely enough they work on pharo 50).
So, I'm going to wait the CI to finish and then integrate it. That should
add support for ProcessWrapper and several path fixes in windows.
>
>
> >>> so that I can see if this is working.
> >>> I know that guille worked on windows and AppVeyor support but he got
> >>> distracted by the github refactoring.
> >>> We hope to come back this week to Pillar. We plan to release a version
> >>> (still with Magritte) but with a full documentation.
> >>>
> >>
> >> Cool, I will test because I have several chapters ready to publish.
> >>
> >>> Stef
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> On Sat, Jan 27, 2018 at 4:47 PM, Hernán Morales Durand
> >>> <hernan.morales(a)gmail.com> wrote:
> >>>> Hi Stef
> >>>>
> >>>> 2018-01-27 9:30 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>:
> >>>>> Hi Hernan
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Thu, Jan 25, 2018 at 10:30 PM, Hernán Morales Durand
> >>>>> <hernan.morales(a)gmail.com> wrote:
> >>>>>> I am following the Publishing Pillar Booklet guide from here
> >>>>>> https://github.com/SquareBracketAssociates/Booklet-
> PublishingAPillarBooklet
> >>>>>
> >>>>> pay attention it is not public because it is in flux because we were
> >>>>> working on Pillar 70.
> >>>>>
> >>>>> Now if you follow the readme of pillar-markup/pillar/ it should work
> >>>>> since I used it yesterday.
> >>>>>
> >>>>> $ wget https://raw.githubusercontent.com/pillar-markup/pillar/
> master/download.sh
> >>>>>> $ chmod +x download.sh
> >>>>>> $ ./download.sh
> >>>>>
> >>>>>>./pillar archetype book
> >>>>> make book.
> >>>>>
> >>>>>
> >>>>> What you should know is that the stable version sucks at the
> >>>>> infrastructure level (relying on too many servers + silent failures
> in
> >>>>> bash files).
> >>>>>
> >>>>> Can you retry and let me know?
> >>>>
> >>>> Ok I tried again using MinGW in Windows 8.1
> >>>> Image is downloaded ok but final step gives an error:
> >>>>
> >>>> $ make book
> >>>> support/makefiles/prepare.mk:1: *** Undefined setting
> OUTPUTDIRECTORY (Directory
> >>>> for build products). Stop.
> >>>>
> >>>> I replaced the expanded shell variables in main.mk from using := to =
> >>>> and it seems to "solve" this problem, though someone else should check
> >>>> why this happens
> >>>>
> >>>> MAIN = $(shell ./pillar introspect mainDocument)
> >>>>
> >>>> OUTPUTDIRECTORY = $(shell ./pillar introspect outputDirectory)
> >>>> LATEXTEMPLATE = $(shell ./pillar introspect latexTemplate)
> >>>> LATEXCHAPTERTEMPLATE = $(shell ./pillar introspect
> latexChapterTemplate)
> >>>> HTMLTEMPLATE = $(shell ./pillar introspect htmlTemplate)
> >>>> HTMLCHAPTERTEMPLATE = $(shell ./pillar introspect htmlChapterTemplate)
> >>>> CHAPTERS = $(shell ./pillar introspect chapters)
> >>>>
> >>>> $ make book
> >>>> make: *** No rule to make target `/.pdf', needed by `pdfbook'. Stop.
> >>>>
> >>>> I am using
> >>>> $ make --version
> >>>> GNU Make 3.81
> >>>>
> >>>>
> >>>>> BTW why do you want to compile Booklet-PublishingAPillarBooklet/
> >>>>> If you want just create your own repo and do
> >>>>>
> >>>>> wget https://raw.githubusercontent.com/pillar-markup/pillar/
> master/download.sh
> >>>>> chmod +x download.sh
> >>>>> ./download.sh
> >>>>> ./pillar archetype book
> >>>>> make book.
> >>>>>
> >>>>
> >>>> Thanks, I just followed the install instructions.
> >>>>
> >>>> Hernán
> >>>>
> >>>>>
> >>>>> Stef
> >>>>>
> >>>>>
> >>>>>> $ git clone git@github.com:SquareBracketAssociates/Booklet-
> PublishingAPillarBooklet.git
> >>>>>> $ cd Booklet-PublishingAPillarBooklet/
> >>>>>> $ wget https://raw.githubusercontent.com/pillar-markup/pillar/
> master/download.sh
> >>>>>> $ chmod +x download.sh
> >>>>>> $ ./download.sh
> >>>>>>
> >>>>>> --2018-01-25 17:56:32-- http://get.pharo.org/vm50
> >>>>>> Resolving get.pharo.org (get.pharo.org) 164.132.235.17
> >>>>>> Connecting to get.pharo.org (get.pharo.org)|164.132.235.17|:80...
> connected.
> >>>>>> HTTP request sent, awaiting response... 200 OK
> >>>>>> Length: 5819 (5.7K)
> >>>>>> Saving to: 'STDOUT'
> >>>>>>
> >>>>>> 0K ..... 100%
> 371K=0.02s
> >>>>>>
> >>>>>> 2018-01-25 17:56:33 (371 KB/s) - written to stdout [5819/5819]
> >>>>>>
> >>>>>> Downloading the latest pharoVM:
> >>>>>> http://files.pharo.org/get-files/50/pharo-win-stable.zip
> >>>>>> pharo-vm/Pharo.exe
> >>>>>> Downloading PharoV50.sources:
> >>>>>> http://files.pharo.org/get-files/50/sources.zip
> >>>>>> Creating starter scripts pharo and pharo-ui
> >>>>>> --2018-01-25 17:57:21--
> >>>>>> https://github.com/pillar-markup/pillar/releases/
> download/50/Pillar-deployment50.zip
> >>>>>> Resolving github.com (github.com) 192.30.253.112, 192.30.253.113
> >>>>>> Connecting to github.com (github.com)|192.30.253.112|:443...
> connected.
> >>>>>> HTTP request sent, awaiting response... 302 Found
> >>>>>> Location: https://github-production-release-asset-2e65be.s3.
> amazonaws.com/41843105/f4ea97f0-e63b-11e7-9012-
> edab5af1a547?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=
> AKIAIWNJYAX4CSVEH53A%2F20180125%2Fus-east-1%2Fs3%
> 2Faws4_request&X-Amz-Date=20180125T205723Z&X-Amz-
> Expires=300&X-Amz-Signature=9ecb9c284b9a92c8dbae0c15d8e490
> 324f0fc7ea3cbe98104080f99c4573e1d6&X-Amz-SignedHeaders=host&
> actor_id=0&response-content-disposition=attachment%3B%20filename%3DPillar-
> deployment50.zip&response-content-type=application%2Foctet-stream
> >>>>>> [following]
> >>>>>> --2018-01-25 17:57:23--
> >>>>>> https://github-production-release-asset-2e65be.s3.
> amazonaws.com/41843105/f4ea97f0-e63b-11e7-9012-
> edab5af1a547?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=
> AKIAIWNJYAX4CSVEH53A%2F20180125%2Fus-east-1%2Fs3%
> 2Faws4_request&X-Amz-Date=20180125T205723Z&X-Amz-
> Expires=300&X-Amz-Signature=9ecb9c284b9a92c8dbae0c15d8e490
> 324f0fc7ea3cbe98104080f99c4573e1d6&X-Amz-SignedHeaders=host&
> actor_id=0&response-content-disposition=attachment%3B%20filename%3DPillar-
> deployment50.zip&response-content-type=application%2Foctet-stream
> >>>>>> Resolving github-production-release-asset-2e65be.s3.amazonaws.com
> >>>>>> (github-production-release-asset-2e65be.s3.amazonaws.com)
> >>>>>> 54.231.115.35
> >>>>>> Connecting to github-production-release-
> asset-2e65be.s3.amazonaws.com
> >>>>>> (github-production-release-asset-2e65be.s3.amazonaws.com)
> |54.231.115.35|:443...
> >>>>>> connected.
> >>>>>> HTTP request sent, awaiting response... 200 OK
> >>>>>> Length: 18482449 (18M) [application/octet-stream]
> >>>>>> Saving to: 'imageLn5zD.zip'
> >>>>>>
> >>>>>> imageLn5zD.zip 10%[=> ] 1.88M 502 B/s
> in 8m 7s
> >>>>>>
> >>>>>> 2018-01-25 18:15:45 (3.94 KB/s) - Read error at byte
> 1966661/18482449
> >>>>>> (Bad file descriptor). Retrying.
> >>>>>>
> >>>>>> --2018-01-25 18:15:46-- (try: 2)
> >>>>>> https://github-production-release-asset-2e65be.s3.
> amazonaws.com/41843105/f4ea97f0-e63b-11e7-9012-
> edab5af1a547?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=
> AKIAIWNJYAX4CSVEH53A%2F20180125%2Fus-east-1%2Fs3%
> 2Faws4_request&X-Amz-Date=20180125T205723Z&X-Amz-
> Expires=300&X-Amz-Signature=9ecb9c284b9a92c8dbae0c15d8e490
> 324f0fc7ea3cbe98104080f99c4573e1d6&X-Amz-SignedHeaders=host&
> actor_id=0&response-content-disposition=attachment%3B%20filename%3DPillar-
> deployment50.zip&response-content-type=application%2Foctet-stream
> >>>>>> Connecting to github-production-release-
> asset-2e65be.s3.amazonaws.com
> >>>>>> (github-production-release-asset-2e65be.s3.amazonaws.com)
> |54.231.115.35|:443...
> >>>>>> connected.
> >>>>>> HTTP request sent, awaiting response... 403 Forbidden
> >>>>>> 2018-01-25 18:15:47 ERROR 403: Forbidden.
> >>>>>>
> >>>>>>
> >>>>>> Also the download speed was super slow.
> >>>>>>
> >>>>>> Any ideas?
> >>>>>>
> >>>>>> Cheers,
> >>>>>>
> >>>>>> Hernán
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >
>
>
--
Guille Polito
Research Engineer
Centre de Recherche en Informatique, Signal et Automatique de Lille
CRIStAL - UMR 9189
French National Center for Scientific Research - *http://www.cnrs.fr
<http://www.cnrs.fr>*
*Web:* *http://guillep.github.io* <http://guillep.github.io>
*Phone: *+33 06 52 70 66 13
Jan. 29, 2018
Re: [Pharo-users] Iceberg and resource files
by Christophe Demarey
Hi Ken,
> Le 27 janv. 2018 à 15:38, kmo <voxkmp(a)gmail.com> a écrit :
>
> I don't understand how iceberg handles resource files that you might also
> like to version along with the pharo code.
For now, Iceberg do not really handle these files but it is planned in a next future.
> Say I have an CSV file and a text file that my pharo application uses. How
> do I include these in the iceberg commit/push? How do I see changes made in
> these files from version to version?
Currently, you cannot do anything related to this through the UI.
What you could do is to call directly Iceberg API to commit ressources to the git repository:
1/ write the resource content in git working copy (std file system). There is a utility method: IceRepository>>#saveContent: aString inWorkingCopyFile: aRelativePathString
2/ add these files to git index through: IceRepository>>addFilesToIndex: aListOfPaths
3/ commit :
iceRepository
commitIndexWithMessage: commitMessage
andParents: { iceRepository headCommit }
You can also read ressources by suing IceRepository>>#contentOfFileNamed: aPathString commit: aCommitId
Christophe.
> Does iceberg only handle pharo code? Generally git clients don't care about
> the file type - and it it is any kind of text you can see the actual
> differences between each commit.
>
> Ken
>
>
>
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>
Jan. 29, 2018
Re: [Pharo-users] Download pillar image -> Error 403: Forbidden
by Guillermo Polito
On Sun, Jan 28, 2018 at 8:51 AM, Hernán Morales Durand <
hernan.morales(a)gmail.com> wrote:
> Hi Stef,
>
> 2018-01-28 4:15 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>:
> > Ok I see. I think that I never tried this version of Pillar on windows.
> > And I hate make because it is impossible for me to debug it. I will
> > check with Damien
> > because I do not get make.
> >
> > Now we removed the dependency to make in the dev branch
> > Could you try the following:
> > https://github.com/pillar-markup/pillar/blob/newpipeline/README.md
> >
>
> Tried both options, 1) downloading pre-compiled and 2) building from
> sources+setting up environment.
> 1) Nothing happened after "pillar archetype build", exit without
> error, no stdout output, no _result folder
> 2) I got confused with this:
>
> mv pillar ~/.pillar
>
> because now I have two directories: the .pillar in HOME and the build/
> directory separated. And no "pillar" shell script so should I copy the
> one from 1) ?
> I will re-check tomorrow maybe I'm reading this the wrong way.
>
Ah! the instructions are not right :) Sorry for that.
Actually, the instructions are written so you execute the build script from
within the pillar repository. Something like this.
$ git clone git@github.com:pillar-markup/pillar.git -b newpipeline
$ cd pillar
$ ./scripts/build.sh
that is why the next lines are
$ mv pillar ~/.pillar
and
$ export PILLAR_HOME="$HOME/.pillar/build"$ export PATH="$PATH:$PILLAR_HOME"
Now, to fix your setup, you can try:
$ mv build ~/.pillar/
and that should make the pillar launcher scripts available.
We changed these scripts with stef a couple of weeks ago to keep not only
the build directory but also the git repository, and so be able to upgrade
pillar. But a docbug slipped in ^^.
Can you check it like that?
> > so that I can see if this is working.
> > I know that guille worked on windows and AppVeyor support but he got
> > distracted by the github refactoring.
> > We hope to come back this week to Pillar. We plan to release a version
> > (still with Magritte) but with a full documentation.
> >
>
> Cool, I will test because I have several chapters ready to publish.
>
> > Stef
> >
> >
> >
> >
> >
> > On Sat, Jan 27, 2018 at 4:47 PM, Hernán Morales Durand
> > <hernan.morales(a)gmail.com> wrote:
> >> Hi Stef
> >>
> >> 2018-01-27 9:30 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>:
> >>> Hi Hernan
> >>>
> >>>
> >>>
> >>> On Thu, Jan 25, 2018 at 10:30 PM, Hernán Morales Durand
> >>> <hernan.morales(a)gmail.com> wrote:
> >>>> I am following the Publishing Pillar Booklet guide from here
> >>>> https://github.com/SquareBracketAssociates/Booklet-
> PublishingAPillarBooklet
> >>>
> >>> pay attention it is not public because it is in flux because we were
> >>> working on Pillar 70.
> >>>
> >>> Now if you follow the readme of pillar-markup/pillar/ it should work
> >>> since I used it yesterday.
> >>>
> >>> $ wget https://raw.githubusercontent.com/pillar-markup/pillar/
> master/download.sh
> >>>> $ chmod +x download.sh
> >>>> $ ./download.sh
> >>>
> >>>>./pillar archetype book
> >>> make book.
> >>>
> >>>
> >>> What you should know is that the stable version sucks at the
> >>> infrastructure level (relying on too many servers + silent failures in
> >>> bash files).
> >>>
> >>> Can you retry and let me know?
> >>
> >> Ok I tried again using MinGW in Windows 8.1
> >> Image is downloaded ok but final step gives an error:
> >>
> >> $ make book
> >> support/makefiles/prepare.mk:1: *** Undefined setting OUTPUTDIRECTORY
> (Directory
> >> for build products). Stop.
> >>
> >> I replaced the expanded shell variables in main.mk from using := to =
> >> and it seems to "solve" this problem, though someone else should check
> >> why this happens
> >>
> >> MAIN = $(shell ./pillar introspect mainDocument)
> >>
> >> OUTPUTDIRECTORY = $(shell ./pillar introspect outputDirectory)
> >> LATEXTEMPLATE = $(shell ./pillar introspect latexTemplate)
> >> LATEXCHAPTERTEMPLATE = $(shell ./pillar introspect latexChapterTemplate)
> >> HTMLTEMPLATE = $(shell ./pillar introspect htmlTemplate)
> >> HTMLCHAPTERTEMPLATE = $(shell ./pillar introspect htmlChapterTemplate)
> >> CHAPTERS = $(shell ./pillar introspect chapters)
> >>
> >> $ make book
> >> make: *** No rule to make target `/.pdf', needed by `pdfbook'. Stop.
> >>
> >> I am using
> >> $ make --version
> >> GNU Make 3.81
> >>
> >>
> >>> BTW why do you want to compile Booklet-PublishingAPillarBooklet/
> >>> If you want just create your own repo and do
> >>>
> >>> wget https://raw.githubusercontent.com/pillar-markup/pillar/
> master/download.sh
> >>> chmod +x download.sh
> >>> ./download.sh
> >>> ./pillar archetype book
> >>> make book.
> >>>
> >>
> >> Thanks, I just followed the install instructions.
> >>
> >> Hernán
> >>
> >>>
> >>> Stef
> >>>
> >>>
> >>>> $ git clone git@github.com:SquareBracketAssociates/Booklet-
> PublishingAPillarBooklet.git
> >>>> $ cd Booklet-PublishingAPillarBooklet/
> >>>> $ wget https://raw.githubusercontent.com/pillar-markup/pillar/
> master/download.sh
> >>>> $ chmod +x download.sh
> >>>> $ ./download.sh
> >>>>
> >>>> --2018-01-25 17:56:32-- http://get.pharo.org/vm50
> >>>> Resolving get.pharo.org (get.pharo.org) 164.132.235.17
> >>>> Connecting to get.pharo.org (get.pharo.org)|164.132.235.17|:80...
> connected.
> >>>> HTTP request sent, awaiting response... 200 OK
> >>>> Length: 5819 (5.7K)
> >>>> Saving to: 'STDOUT'
> >>>>
> >>>> 0K ..... 100%
> 371K=0.02s
> >>>>
> >>>> 2018-01-25 17:56:33 (371 KB/s) - written to stdout [5819/5819]
> >>>>
> >>>> Downloading the latest pharoVM:
> >>>> http://files.pharo.org/get-files/50/pharo-win-stable.zip
> >>>> pharo-vm/Pharo.exe
> >>>> Downloading PharoV50.sources:
> >>>> http://files.pharo.org/get-files/50/sources.zip
> >>>> Creating starter scripts pharo and pharo-ui
> >>>> --2018-01-25 17:57:21--
> >>>> https://github.com/pillar-markup/pillar/releases/download/50/Pillar-
> deployment50.zip
> >>>> Resolving github.com (github.com) 192.30.253.112, 192.30.253.113
> >>>> Connecting to github.com (github.com)|192.30.253.112|:443...
> connected.
> >>>> HTTP request sent, awaiting response... 302 Found
> >>>> Location: https://github-production-release-asset-2e65be.s3.
> amazonaws.com/41843105/f4ea97f0-e63b-11e7-9012-
> edab5af1a547?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=
> AKIAIWNJYAX4CSVEH53A%2F20180125%2Fus-east-1%2Fs3%
> 2Faws4_request&X-Amz-Date=20180125T205723Z&X-Amz-
> Expires=300&X-Amz-Signature=9ecb9c284b9a92c8dbae0c15d8e490
> 324f0fc7ea3cbe98104080f99c4573e1d6&X-Amz-SignedHeaders=host&
> actor_id=0&response-content-disposition=attachment%3B%20filename%3DPillar-
> deployment50.zip&response-content-type=application%2Foctet-stream
> >>>> [following]
> >>>> --2018-01-25 17:57:23--
> >>>> https://github-production-release-asset-2e65be.s3.
> amazonaws.com/41843105/f4ea97f0-e63b-11e7-9012-
> edab5af1a547?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=
> AKIAIWNJYAX4CSVEH53A%2F20180125%2Fus-east-1%2Fs3%
> 2Faws4_request&X-Amz-Date=20180125T205723Z&X-Amz-
> Expires=300&X-Amz-Signature=9ecb9c284b9a92c8dbae0c15d8e490
> 324f0fc7ea3cbe98104080f99c4573e1d6&X-Amz-SignedHeaders=host&
> actor_id=0&response-content-disposition=attachment%3B%20filename%3DPillar-
> deployment50.zip&response-content-type=application%2Foctet-stream
> >>>> Resolving github-production-release-asset-2e65be.s3.amazonaws.com
> >>>> (github-production-release-asset-2e65be.s3.amazonaws.com)
> >>>> 54.231.115.35
> >>>> Connecting to github-production-release-asset-2e65be.s3.amazonaws.com
> >>>> (github-production-release-asset-2e65be.s3.amazonaws.com)
> |54.231.115.35|:443...
> >>>> connected.
> >>>> HTTP request sent, awaiting response... 200 OK
> >>>> Length: 18482449 (18M) [application/octet-stream]
> >>>> Saving to: 'imageLn5zD.zip'
> >>>>
> >>>> imageLn5zD.zip 10%[=> ] 1.88M 502 B/s
> in 8m 7s
> >>>>
> >>>> 2018-01-25 18:15:45 (3.94 KB/s) - Read error at byte 1966661/18482449
> >>>> (Bad file descriptor). Retrying.
> >>>>
> >>>> --2018-01-25 18:15:46-- (try: 2)
> >>>> https://github-production-release-asset-2e65be.s3.
> amazonaws.com/41843105/f4ea97f0-e63b-11e7-9012-
> edab5af1a547?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=
> AKIAIWNJYAX4CSVEH53A%2F20180125%2Fus-east-1%2Fs3%
> 2Faws4_request&X-Amz-Date=20180125T205723Z&X-Amz-
> Expires=300&X-Amz-Signature=9ecb9c284b9a92c8dbae0c15d8e490
> 324f0fc7ea3cbe98104080f99c4573e1d6&X-Amz-SignedHeaders=host&
> actor_id=0&response-content-disposition=attachment%3B%20filename%3DPillar-
> deployment50.zip&response-content-type=application%2Foctet-stream
> >>>> Connecting to github-production-release-asset-2e65be.s3.amazonaws.com
> >>>> (github-production-release-asset-2e65be.s3.amazonaws.com)
> |54.231.115.35|:443...
> >>>> connected.
> >>>> HTTP request sent, awaiting response... 403 Forbidden
> >>>> 2018-01-25 18:15:47 ERROR 403: Forbidden.
> >>>>
> >>>>
> >>>> Also the download speed was super slow.
> >>>>
> >>>> Any ideas?
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Hernán
> >>>>
> >>>
> >>
> >
>
>
--
Guille Polito
Research Engineer
Centre de Recherche en Informatique, Signal et Automatique de Lille
CRIStAL - UMR 9189
French National Center for Scientific Research - *http://www.cnrs.fr
<http://www.cnrs.fr>*
*Web:* *http://guillep.github.io* <http://guillep.github.io>
*Phone: *+33 06 52 70 66 13
Jan. 29, 2018