- Pharo-dev - lists.pharo.org

ZdcAbstractSocketStream>>peekFor:?
by Alistair Grant March 22, 2019

March 22, 2019

Hi Sven, Unlike most streams that support #peek, ZdcAbstractSocketStream doesn't support #peekFor:. Is this intentional, or an oversight? Thanks, Alistair

3 7

[Pharo 8.0] Build #172: Update issue URL in build report email
by ci-pharo-ci-jenkins2＠inria.fr March 22, 2019

March 22, 2019

There is a new Pharo build available! The status of the build #172 was: SUCCESS. The Pull Request #2985 was integrated: "Update issue URL in build report email" Pull request url: https://github.com/pharo-project/pharo/pull/2985 Issue Url: https://github.com/pharo-project/pharo/issues/Pharo8.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Issue Tracker] installed some robots
by Marcus Denker March 22, 2019

March 22, 2019

Hi, I have added some robots to the github account https://github.com/pharo-project <https://github.com/pharo-project> For for main repository https://github.com/pharo-project/pharo <https://github.com/pharo-project/pharo> I have enabled by adding the required configs to .github/ : Work In Progress: Prevent merging of Pull Requests with "WIP" in the title https://github.com/marketplace/wip No Response: Closes Issues where the author hasn't responded to a request for more information If the tag more-information-needed is set and no answer provided, issue is closed in 14 days. https://probot.github.io/apps/no-response/ Request Info: Requests more info on issues and pull requests with the default title or an empty body. it sets the more-information-needed flag. https://probot.github.io/apps/request-info/ Stale: Close stale Issues and Pull Requests https://github.com/probot/stale Issues: daysUntilStale: 240, daysUntilClose: 60 Pulls: daysUntilStale: 20, daysUntilClose: 10

2 3

[Pharo 8.0] Build #171: Remove incorrect test
by ci-pharo-ci-jenkins2＠inria.fr March 22, 2019

March 22, 2019

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

1 0

[ANN] Next Pharo Sprint: March 29
by Marcus Denker March 22, 2019

March 22, 2019

We will organize a Pharo sprint / Moose dojo March 29, starting at 10:00am. (Local Time Paris). Goals of this sprint: - Pharo 7 backports, Pharo 8, - Check issues from old Issue tracker Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events We have added a (right now empty) Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 Known Local Sprint meetings Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come

1 0

[Pharo 8.0] Build #170: 2972-MailAddressTokenizer-doesnt-handle-non-ascii-characters
by ci-pharo-ci-jenkins2＠inria.fr March 22, 2019

March 22, 2019

There is a new Pharo build available! The status of the build #170 was: SUCCESS. The Pull Request #2973 was integrated: "2972-MailAddressTokenizer-doesnt-handle-non-ascii-characters" Pull request url: https://github.com/pharo-project/pharo/pull/2973 Issue Url: https://pharo.fogbugz.com/f/cases/2972 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #169: 2955-speedup-isAccessedIn-in-BooleanSlot-and-PropertySlot
by ci-pharo-ci-jenkins2＠inria.fr March 22, 2019

March 22, 2019

There is a new Pharo build available! The status of the build #169 was: FAILURE. The Pull Request #2956 was integrated: "2955-speedup-isAccessedIn-in-BooleanSlot-and-PropertySlot" Pull request url: https://github.com/pharo-project/pharo/pull/2956 Issue Url: https://pharo.fogbugz.com/f/cases/2955 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Missing tests for FFI in CI
by Stephan Eggermont March 21, 2019

March 21, 2019

Yesterday, we tracked down a serious issue in 64 bit FFI. After giving up with our own code, we made a fresh start with the latest base image and OSWindows. We were finally able to figure out what went wrong with two simple tests that were failing in 64 bit that worked correctly in 32 bit. FFIConstantHandleType externalType is the wrong size After confirming that and making it work, we were told that a number of FFI fixes were done by Nicolas and Eliot in Squeak that did not get integrated in Pharo. Applying the changes from the latest Squeak FFI resolved the problem, and a few that we were unaware of. Stephan

4 6

How to download a patched file?
by Eliot Miranda March 21, 2019

March 21, 2019

Hi GitHub mavens, how does one download a specific patched file from GitHub? I want to test Pablo's fix here: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/381 platforms/iOS/vm/OSX/sqSqueakOSXOpenGLView.m <https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/381/files#diff-0> I don't want to go through "View File", or clone, or anything else. I just want the file itself. How do I get it? _,,,^..^,,,_ best, Eliot

3 5

Questions about DebugSession>>isContextPostMortem:
by Thomas Dupriez March 21, 2019

March 21, 2019

Hello, While looking at the DebugSession>>isContextPostMortem: method (code below), I got three questions: 1) There is a check for whether the suspendedContext (top context) of the process is nil. Does it even make sense for a process not to have any top context? 2) It seems that all the last 3 lines are doing is to check whether selectedContext is in the context chain of the process. Could they be rewritten into this simpler one-liner? Â `|^ (suspendedContext hasContext: selectedContext) not`| 3) Overall, this method says that a context C is "post mortem" if the process controlled by the DebugSession has a top context and C is not in its context chain. That's the practical definition. Could someone shed some light on the high-level definition of "post mortem"? Because "post mortem" is like "after death", but the death of what? A context that merely belongs to another context chain would be considered "post mortem" by the practical definition, but there's no death in this case... || ``` |DebugSession>>isContextPostMortem: selectedContext "return whether we're inspecting a frozen exception without a process attached" | suspendedContext | suspendedContext := interruptedProcess suspendedContext. suspendedContext ifNil: [ ^ false ]. (suspendedContext == selectedContext) ifTrue: [ ^ false ]. ^ (suspendedContext findContextSuchThat: [:c | c sender == selectedContext]) isNil ``` | Does someone know the answer to some (or all) of these questions? Thomas

3 2