- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #1162: 22245-Package-ReleaseTests-should-be-Release-Tests
by ci-pharo-ci-jenkins2＠inria.fr Aug. 8, 2018

Aug. 8, 2018

There is a new Pharo build available! The status of the build #1162 was: SUCCESS. The Pull Request #1674 was integrated: "22245-Package-ReleaseTests-should-be-Release-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/1674 Issue Url: https://pharo.fogbugz.com/f/cases/22245 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

About the infinite debugger
by Guillermo Polito Aug. 8, 2018

Aug. 8, 2018

Hi all, during today's sprint we have been working with lots of people on the infinite debugger problem (https://pharo.fogbugz.com/f/cases/22085/) We have checked the emails sent in the latest month. Then, together with Quentin, Pablo, Pavel, Yoan we have been discussing and testing hypothesis all day. We have been also comparing the debuggers code between pharo 3/4 (where the bug was is present) and pharo 7, but this was not necessarily straight forward as the code is not the same and there is no easy diff... AAAAND, we have found that the problem may come from a wrong pragma marker. Just removing that pragma gives us back the same behaviour as in Pharo 3/4. :D https://github.com/pharo-project/pharo/pull/1621 I know that the exception handling/debugging has been modified several times in the latest years (some refactorings, hiding contexts...), we unfortunately don't have tests for it, so I'd like some more pair of eyes on it. Ben, Martin could you take a look? Thanks all for the fish, Guille

14 27

Iceberg: Cannot Clone Pharo Repository
by Eric Gade Aug. 7, 2018

Aug. 7, 2018

I am having (new) issues cloning my forked pharo repository in a fresh P7 image for development. Git objects are pulled from the repository successfully, but during the checkout phase the error posted below occurs (I can also provide a fuel dump by request). Here is my current system: OSX 10.13.1 (High Sierra) Pharo 7.0 Build information: Pharo-7.0+alpha.build.1159.sha.65cff7b3c78af7ecf3728abdd2f44bf0cbc8a548 (32 Bit) My fork: https://github.com/darth-cheney/pharo Error Stack: ``` IceUnknownCommit(Object)>>doesNotUnderstand: #adopt IcePharoPlugin>>repositoryWillBeCreated: [ :each | each repositoryWillBeCreated: aRepository ] in IcePluginManager>>repositoryWillBeCreated: in Block: [ :each | each repositoryWillBeCreated: aRepositor...etc... Array(SequenceableCollection)>>do: IcePluginManager>>repositoryWillBeCreated: IceRepositoryCreator>>cloneRepository [ self validate. self isCloning ifTrue: [ self cloneRepository ] ifFalse: [ self addLocalRepository ] ] in IceRepositoryCreator>>createRepository in Block: [ self validate.... BlockClosure>>on:do: IceRepositoryCreator>>createRepository [ ^ IceRepositoryCreator new repository: repository; remote: (IceGitRemote url: self remoteUrl); location: self projectLocation location; createRepository ] in IceTipGitHubRepositoryPanel(IceTipGitRepositoryPanel)>>newRepository in Block: [ ^ IceRepositoryCreator new... [ :bar | bar label: aString. aBlock value ] in MorphicUIManager(UIManager)>>informUser:during: in Block: [ :bar | ... [ :bar | aBlock value: bar ] in MorphicUIManager>>informUserDuring: in Block: [ :bar | aBlock value: bar ] BlockClosure>>cull: [ ^ block cull: self ] in [ self prepareForRunning. CurrentJob value: self during: [ ^ block cull: self ] ] in Job>>run in Block: [ ^ block cull: self ] [ activeProcess psValueAt: index put: anObject. aBlock value ] in CurrentJob(DynamicVariable)>>value:during: in Block: [ activeProcess psValueAt: index put: anObject.... BlockClosure>>ensure: CurrentJob(DynamicVariable)>>value:during: CurrentJob class(DynamicVariable class)>>value:during: [ self prepareForRunning. CurrentJob value: self during: [ ^ block cull: self ] ] in Job>>run in Block: [ self prepareForRunning.... BlockClosure>>ensure: Job>>run MorphicUIManager(UIManager)>>displayProgress:from:to:during: MorphicUIManager>>informUserDuring: MorphicUIManager(UIManager)>>informUser:during: IceTipGitHubRepositoryPanel(IceTipGitRepositoryPanel)>>newRepository IceTipGitHubRepositoryPanel>>newRepository IceTipRegisterRepositoryDialog>>doAccept [ self doAccept. true ] in IceTipRegisterRepositoryDialog(IceTipOptionDialog)>>accept in Block: [ self doAccept.... BlockClosure>>on:do: IceTipRegisterRepositoryDialog(IceTipOptionDialog)>>accept ``` -- Eric

2 3

[Pharo 7.0-dev] Build #1161: Modified the code to be similar to #select:thenDo:.
by ci-pharo-ci-jenkins2＠inria.fr Aug. 7, 2018

Aug. 7, 2018

There is a new Pharo build available! The status of the build #1161 was: SUCCESS. The Pull Request #1651 was integrated: "Modified the code to be similar to #select:thenDo:." Pull request url: https://github.com/pharo-project/pharo/pull/1651 Issue Url: https://pharo.fogbugz.com/f/cases/22282 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1160: Integrating Iceberg v1.2.1
by ci-pharo-ci-jenkins2＠inria.fr Aug. 7, 2018

Aug. 7, 2018

There is a new Pharo build available! The status of the build #1160 was: FAILURE. The Pull Request #1672 was integrated: "Integrating Iceberg v1.2.1" Pull request url: https://github.com/pharo-project/pharo/pull/1672 Issue Url: https://pharo.fogbugz.com/f/cases/22297 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

3 2

Stdio>>#standardIOStreamNamed:forWrite: bug?
by Alistair Grant Aug. 6, 2018

Aug. 6, 2018

Hi Damien, Vincent and Guille, Just a disclaimer: despite having done some work on this, I don't consider myself an expert. If someone else has a better explanation, please jump in. Damien wrote on discord: > is there a notion of standard input/output on windows ? Yes, console applications can use stdio. PharoConsole.exe when run from a command prompt has stdio. (Note that cygwin terminals are different and don't support stdio (since Pharo uses the native windows functions)). > looks like Alistair added the possibility to open files by number, Holger Freyther deserves the credit here. My clumsy git merging left his name out as the author (sorry Holger!). > that's probably what was missing at the time Stdio was introduced I'm not sure that opening files by fd would be useful in this particular case. There are three ways to access files on Windows: file descriptor - posix compatibility FILE* - posix compatibility HANDLE - windows native The VM uses native operations for file i/o on Windows, e.g. Read/WriteConsole() for stdio (including pipe redirection of stdio). Mixing file descriptors and FILE* is possible if you're careful. I don't know how to mix fd / FILE* and HANDLEs. It's probably better to stick with using native windows functions most of the time. We included these functions on Windows since they exist, and there are probably some use cases, but you need to know what you're doing. File class>>stdioHandles calls primitiveFileStdioHandles() which eventually opens the stdio streams (if possible) using the Windows native GetStdHandle() function. > I suspect File needs a nameless variant (I'm not certain how pipes > work in unix but I doubt echo foo | cat ever touches the filesystem) That's my understanding (it doesn't touch the file system). > hmm but the short-term bug is that the TTY logic in Stdio >> > #standardIOStreamNamed:forWrite: fails when all 3 standard streams are > redirected OK, my understanding of what you are saying is that if all 3 io streams are redirected the method incorrectly determines that a console isn't present and so falls back to calling #createStdioFileFor:. More below... > I also don't understand the assumption there Vincent Blondeau added / modified these methods, so he may be able to provide more information. I think the assumption is that if any of the stdio files are connected to a TTY. then it is possible to open all the stdio files. If none are present, then (on Windows) create regular files to act as a substitute. The problem is that it only tests for a TTY, when what we really want is a TTY or a file or a pipe. Assuming I've understood correctly, maybe try modifying (sorry for the loss of formatting, only the last line is changed): File class>>stdioDescriptorIsATTY ^ (0 to: 2) anySatisfy: [ :fdNum | | res | res := self fileDescriptorType: fdNum. res between: 1 and: 3 ] We'd need to rename the method, since it is misleading, but it looks like it better represents the intended use. Cheers, Alistair

4 8

[Pharo 7.0-dev] Build #1159: 22295-Integrate-new-Iceberg-Version
by ci-pharo-ci-jenkins2＠inria.fr Aug. 3, 2018

Aug. 3, 2018

There is a new Pharo build available! The status of the build #1159 was: SUCCESS. The Pull Request #1670 was integrated: "22295-Integrate-new-Iceberg-Version" Pull request url: https://github.com/pharo-project/pharo/pull/1670 Issue Url: https://pharo.fogbugz.com/f/cases/development Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1158: 22294-MCTraitDefinition-is-not-correctly-initialised-in-all-the-constructors
by ci-pharo-ci-jenkins2＠inria.fr Aug. 3, 2018

Aug. 3, 2018

There is a new Pharo build available! The status of the build #1158 was: FAILURE. The Pull Request #1669 was integrated: "22294-MCTraitDefinition-is-not-correctly-initialised-in-all-the-constructors" Pull request url: https://github.com/pharo-project/pharo/pull/1669 Issue Url: https://pharo.fogbugz.com/f/cases/22294 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1157: Fix https://pharo.fogbugz.com/f/cases/22241
by ci-pharo-ci-jenkins2＠inria.fr Aug. 3, 2018

Aug. 3, 2018

There is a new Pharo build available! The status of the build #1157 was: SUCCESS. The Pull Request #1627 was integrated: "Fix https://pharo.fogbugz.com/f/cases/22241" Pull request url: https://github.com/pharo-project/pharo/pull/1627 Issue Url: https://pharo.fogbugz.com/f/cases/development Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1156: changed the comment
by ci-pharo-ci-jenkins2＠inria.fr Aug. 3, 2018

Aug. 3, 2018

There is a new Pharo build available! The status of the build #1156 was: SUCCESS. The Pull Request #1652 was integrated: "changed the comment" Pull request url: https://github.com/pharo-project/pharo/pull/1652 Issue Url: https://pharo.fogbugz.com/f/cases/22144 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0