pics. Thank you for speaking
up! Without you I would not have had the courage to state my view.
Best regards,
Bernhard Pieber
>> and certainly doesn't help building a
>> stronger community.
>>
>> Best regards,
>>
>> Esteban A. Maringolo
>>
>> On Wed, J
Hi everyone,
Is this the right place to report a Pharo 8.0 crash?
I am on a MacBookPro16,4 on macOS Big Sur Version 11.2.3 (20D91) with an
external 30" Apple Cinema Display (2500 x 1600).
Here is what I did:
I downloaded PharoLauncher.
I created a new image using the official distribution
While that may be true, I'd like to note that git-flow [1], one of the most
widely used Git workflows, uses slashes in its default conventions.
Bernhard
[1] https://github.com/petervanderdoes/gitflow-avh
> Am 14.01.2020 um 05:35 schrieb Ben Coman :
>
> Even from the command line I find slashes
Hi,
I followed these instructions for contributing to Pharo:
https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo
During Step 1 Repairing local repository missing I get the following error:
IceGitHubError: API rate limit exceeded
I retried with a new Pharo 7.0 - 64bit
Hi all,
Here is the output:
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
100 237 100 2370 0899 0 --:--:-- --:--:-- --:--:-- 901
bash: line 1: syntax error near
Hi all,
Can somebody please help me get my bugfix from December integrated? For some
reason CI fails and I have no idea how to debug that. :-(
https://github.com/pharo-project/pharo/pull/632
Bernhard
pharo lines and looks in the update
>> pane you will see the updates (but you should pull from pharo to sync
>> your repo).
>>
>> Stef
>>
>> On Tue, Jan 2, 2018 at 10:45 PM, Bernhard Pieber <bernh...@pieber.com> wrote:
>>> I saw that two pull requests
I saw that two pull requests were accepted and merged into the development
branch. I had expected that Iceberg would show me them somewhere. However, in
the branches pane of my repository the status pharo-project/development is
shown as Up to date.
Shouldn't there be some indication that new
I have created another pull request with an implementation for #upToAll: for
ZnCharacterReadStream:
https://github.com/pharo-project/pharo/pull/634
Here is the case: https://pharo.fogbugz.com/f/cases/20905
CI checks are in progress.
Does that make it the first contribution in 2018? ;-)
Let me
And all on one machine?! Wow.
Happy New Year
Bernhard
> Am 31.12.2017 um 14:18 schrieb Norbert Hartl :
>
> I want to second that. It has been another amazing year for pharo. And I
> think things have changed significantly. So 2018 should be really great!
> I matched my
:07 schrieb Sven Van Caekenberghe <s...@stfx.eu>:
>
>> On 31 Dec 2017, at 16:21, Bernhard Pieber <bernh...@pieber.com> wrote:
>>
>> Hi Sven,
>>
>> Thanks for the answer. This is exactly what I was looking for. And it is
>> great that there is als
s currently refactoring, adding many tests to Iceberg internal
> representation.
>
> Stef
>
> On Sat, Dec 30, 2017 at 11:03 AM, Bernhard Pieber <bernh...@pieber.com> wrote:
>> Hi,
>>
>> I wanted to set up a new Pharo 7 image for contributing. I used the
Hi Henrik,
Thanks for the fix. I just saw it today. In the meantime I have created a pull
request with another fix. To be honest, I have just taken the working
implementation from Squeak:
https://github.com/pharo-project/pharo/pull/632
Alas, the CI check failed for some reason I don't
yes, usually latest VMs are *not* for
> production. But this ones have been tested last three months and they work
> fine so yes, *this ones* can be used for production.
>
> Esteban
>
>>
>>>
>>>> On 31 Dec 2017, at 15:56, Bernhard Pieber <bernh...@pieber.c
ook-result/Zinc-Encoding-Meta/Zinc-Encoding-Meta.html
>
> 1.4. Converting Streams
>
>> On 30 Dec 2017, at 13:27, Bernhard Pieber <bernh...@pieber.com> wrote:
>>
>> I just saw that the FileStream hierarchy including MultiByteFileStream is
>> deprecated. Howev
acterWriteStream
> on: outputStream
> encoding: 'utf8')) nextPutAll: aStream contents.
> ].
>
> self inform: 'Filed out to: ', String cr, aFileReference basename
>
>
> self inform: 'Filed out to: ', String cr, fileName.
>
tor imageDirectory / 'test.txt') asFileReference readStreamDo: [ :s
> |
> s converter: UTF8TextConverter new.
> s contents
> ]
>
> 2017-12-30 13:27 GMT+01:00 Bernhard Pieber <bernh...@pieber.com>:
> I just saw that the FileStream hierarchy including MultiBy
These are not for production, right?
Bernhard
> Am 31.12.2017 um 11:58 schrieb Esteban Lorenzano :
>
> wget -O- get.pharo.org/vmLatest70 | bash
> wget -O- get.pharo.org/64/vmLatest70 | bash
>
> Esteban
>
>> On 31 Dec 2017, at 11:48, Sean P. DeNigris
I just saw that the FileStream hierarchy including MultiByteFileStream is
deprecated. However, I can't find what file stream class should be used to read
a UTF-8 encoded file instead. FileReference>>#readStreamDo: also uses
MultiByteFileStream.
Can someone please point me to the right code?
I created an issue for this:
https://pharo.fogbugz.com/f/cases/20898
Bernhard
> Am 30.12.2017 um 12:01 schrieb Bernhard Pieber <bernh...@pieber.com>:
>
> I just checked and the bug in #upToAll: is still there in Pharo 7.
>
> Bernhard
>
>> Am 29.12.2017 um 20:26
I just checked and the bug in #upToAll: is still there in Pharo 7.
Bernhard
> Am 29.12.2017 um 20:26 schrieb Bernhard Pieber <bernh...@pieber.com>:
>
> Hi Henrik,
>
> Thanks for your answer. Sounds like a bug, then. :-/
>
> Cheers,
> Bernhard
>
>>
Hi Henrik,
Thanks for your answer. Sounds like a bug, then. :-/
Cheers,
Bernhard
> Am 28.12.2017 um 20:31 schrieb Henrik-Nergaard :
>
> Hi,
>
> #upTo: works fine.
>
> 'test' asFileReference readStreamDo: [ :stream | stream converter:
> UTF8TextConverter new; upTo: $e ].
Hi all,
I want to stream over a file which is encoded in UTF-8 and have a problem with
upToAll: answering more than it should.
Here is a minimal test:
'ße' readStream upToAll: 'e'.
This answers 'ß' as expected.
I wrote those two characters to a file:
FileStream forceNewFileNamed: 'test' do: [
Hi Esteban,
Thanks for asking. My one and only wish is more stability for the stable
version, i.e. bug fixes for Pharo 6, especially the VMs but also the image.
Thanks for Pharo!
Cheers,
Bernhard
> Am 23.12.2017 um 17:58 schrieb Esteban Lorenzano :
>
> Hi everybody,
>
Hi Sean,
Thanks for taking the time to try to confirm this. Did you use Pharo Launcher?
I just tried it using get.pharo.org and don’t see the corruption. So it seems
to be specific to Launcher somehow. :-/
Bernhard
> Am 06.12.2017 um 01:04 schrieb Sean P. DeNigris :
>
I did the following in Pharo Launcher:
1. Select Official distributions > Pharo 6.1 (stable)
2. Click Create Image
3. Launch created image
4. Browse GLMAccumulator
5. Click on any method, e.g. activeEntity => method source is corrupt, e.g. mp:
‚tg 2/2/2010 22:03'
I tried it twice, also with the
I just found a file named org.pharo.global-identifiers.ston in my preferences
folder. It contains a #secretUUID and a #computerUUID. :-( What is this
information used for? More importantly, how can I turn it off?
Bernhard
I assume that System > Software update can be used to update an Image from
Pharo 6.0 to Pharo 6.1, correct?
When I tried to update a Pharo 6.0 image (Latest update: #60499) using System >
Software update I ran into the following error:
Could not load BaselineOfFileTree-ThierryGoubier.32.mcz:
I ran into an annoying problem using the latest Pharo 6.1 (stable) from Pharo
Launcher. I am on macOS Sierra Version 10.12.6.
Steps to reproduce:
1. Open Pharo Launcher
2. Create new Pharo 6.1 (stable) image from the official distributions, named
Test
3. Launch the Test image
4. Open a File
Hi Stef,
I just found download links on this page:
https://github.com/pharo-project/pharo-launcher
They point to Jenkins build artefacts.
Thank you for implementing the launcher. As a newbie I ran into some questions:
I guess the launcher is not self-updating, right?
If not, how can I find out
I just tripped over a walkback when clicking on the menu item „Store result as
progress reference“ in the Test Runner after having run all tests in a Pharo
6.1 (stable) image created by PharoLauncher 1.0.1 on macOS Sierra 10.12.6. Has
anyone seen this before?
Cheers,
Bernhard
Dear Pharoers,
I encountered a DNU when I ran all tests in a new Pharo 6.1 image created with
PharoLauncher 1.0.1 on macOS Sierra 10.12.6.
Should this work or is it a known issue? What is the Pharo’s policy concerning
SUnit tests for stable releases?
Cheers,
Bernhard
Hi,
What VM would you recommend for a production app on macOS Sierra?
- Pharo 6, right?
- I assume 32-bit because 64-bit is still experimental, right?
- The one I get with „curl get.pharo.org | bash“ has a reproducible crash when
typing
Am 20.01.2017 um 14:12 schrieb Denis Kudriashov :
>
> And this is done. I just upload new stable version:
> - source code shortcuts are managed by Calypso. I found simple hook how to
> achieve this
> - senders/implementors by source code shortcuts in method browser are now
il.com>:
>
>
> 2017-01-09 13:02 GMT+01:00 Bernhard Pieber <bernh...@pieber.com>:
> I just played a bit with Calypso. I love the possibility to easily show the
> inherited methods. I would love to stay in a Calypso browser when I use Cmd-b
> to browse classes referenc
I just saw found the class DAGraphVizGenerator in Tool-DependencyAnalyser. It
references a class GVGraphViz by name. What package do I have to load to get
it? The GraphViz package in the Pharo Project Catalog does not use the GV
prefix.
Cheers,
Bernhard
Happy New Year!
The GraphViz project in the Pharo Project Catalog has the tag Pharo5.0 but
still uses NBMacShell which seems to have been removed in Pharo 5. What is the
right replacement for NBMacShell run: string in newer Pharo versions?
Cheers,
Bernhard
Hi Denis,
I just played a bit with Calypso. I love the possibility to easily show the
inherited methods. I would love to stay in a Calypso browser when I use Cmd-b
to browse classes referenced in method source.
Thanks for your contribution!
Cheers,
Bernhard
> Am 27.12.2016 um 17:12 schrieb
And this is how it works in VA Smalltalk. The default shortcut to expand the
abbreviations used there is Shift-Space. See this excellent video by the late
James Robertson: https://www.youtube.com/watch?v=TY_rJ3G0Tn4
If the same default abbreviations were used as in VA Smalltalk, this would be
entry?
>
> - publish a slice? (press slice + bug number)
>
> Our integration tool and process work this way
>
> Stef
>
> Le 2/7/16 à 21:16, Bernhard Pieber a écrit :
>> Hi,
>>
>> The following code goes into an endless loop:
>> MailAddressParse
Done!
Cheers,
Bernhard
> Am 03.07.2016 um 00:08 schrieb Ben Coman <b...@openinworld.com>:
>
> On Sun, Jul 3, 2016 at 3:16 AM, Bernhard Pieber <bernh...@pieber.com> wrote:
>> Hi,
>>
>> The following code goes into an endless loop:
>> MailAddressPars
Hi,
The following code goes into an endless loop:
MailAddressParser addressesIn: 'romeo@verona.it‘
It’s because of the ampersand. The fix is trivial, because the bug just was a
typo.
Fix and test are in the Pharo50Inbox:
Network-Mail-BernhardPieber.46.mcz
Network-Tests-BernhardPieber.14.mcz
n object, not a string.
>
> Mind you, I haven't tried this yet.
>
> Sven
>
>> On 28 Jun 2016, at 20:26, Bernhard Pieber <bernh...@pieber.com> wrote:
>>
>> I have a web service where I have to use a URL with percent-encoded (URL
>> encoded) special c
I have a web service where I have to use a URL with percent-encoded (URL
encoded) special characters – German Umlauts – but not using UTF8 but
ISO-8859-1. I have been given the following table for the „correct“ encodings:
http://www.degraeve.com/reference/urlencoding.php
I found out that I can
Wow, thanks for the detailed explanation!
Cheers,
Bernhard
> Am 21.04.2016 um 16:48 schrieb Eliot Miranda <eliot.mira...@gmail.com>:
>
> Hi Bernhard,
>
>> On Apr 20, 2016, at 9:56 PM, Bernhard Pieber <bernh...@pieber.com> wrote:
>>
>> Hi Eliot,
>&
:
>
> Hi Bernhard,
>
>
>> On Apr 20, 2016, at 5:26 AM, Bernhard Pieber <bernh...@pieber.com> wrote:
>>
>> Dear Pharoers,
>>
>> I found something strange:
>> Time millisecondsToRun: [ Class allSubInstances size ]. „23617"
&
Dear Pharoers,
I found something strange:
Time millisecondsToRun: [ Class allSubInstances size ]. „23617"
I did this on a new Pharo 5 image
curl get.pharo.org/alpha+vmLatest | bash
Can somebody confirm this on their machine? What might be the reason?
Cheers,
Bernhard
Hi Pierce,
thanks for the information.
Cheers,
Bernhard
> Am 17.04.2016 um 13:49 schrieb Pierce Ng <pie...@samadhiweb.com>:
>
> On Sun, Apr 17, 2016 at 09:54:24AM +0200, Bernhard Pieber wrote:
>> Googling did not bring up any solution so far. Any help would be g
metadata reconciled with the code changes? I
just realized that I just don’t know what information is in the Monticello
metadata, which is not in the code?
Cheers,
Bernhard
> Am 29.01.2016 um 19:12 schrieb Dale Henrichs
> <dale.henri...@gemtalksystems.com>:
> On 01/29/2016 09:
Hi David,
Just for your information, Cuis uses a file-per-package format. It looks really
nice on GitHub and on SourceTree. As far as I can tell, there has not been much
merging going, though. So it is entirely possible that it turns out not to work
as well as the filetree format when merging.
Hi Dale,
I am trying to understand this a little better. If a package containing
metadata would be changed using a dialect which cannot interpret the metadata,
wouldn’t or at least couldn’t it be broken or lost afterwards for a dialect
which tries to interpret the metadata? At least if my
51 matches
Mail list logo