- Pharo-dev - lists.pharo.org

Standardized nomenclature for feature requests
by Esteban A. Maringolo Sept. 17, 2018

Sept. 17, 2018

Hi there, Q: Is there a reason why Pharo (as a project) doesn't follow a standardized nomenclature for features/request as other communities does? So for instance something like PFR-005 (Pharo Feature Request) could be "Truly headless images", PFR-006 "Pharo Bootstrapping", etc. I can't really tell whether this would improve to the overall process, but I wanted to know if this was already debated by the board and dismissed, if it is something that wasn't considered at all, of if we have something equivalent and what it is. Regards, Language examples: JSR (Java Specification Requests) https://www.jcp.org/en/jsr/all PEP (Python Enhancement Proposals) https://www.python.org/dev/peps/ RFC (Rust, Request for Comments) https://github.com/rust-lang/rfcs Technologies: BIP (Bitcoin Improvement Proposal) https://github.com/bitcoin/bips EIP (Ethereum Improvement Proposal) https://eips.ethereum.org/ -- Esteban A. Maringolo

1 0

ZnMimePart Disposition-Content spaces
by Ben Coman Sept. 17, 2018

Sept. 17, 2018

Hi Sven, We encountered a ZnMimePart Content-Disposition header problem with a server expecting a space following the "form-data;" string. The diff here... https://www.diffchecker.com/ETIfCUzx * on the left shows the working request from the default command-line tool * on the right shows the non-working request from Pharo. The specifications are really unclear about the requirement or not for a space, so it may be reasonable to consider the fault lies with the server not being permissive enough, but I notice these examples all have space after semi colons... * https://tools.ietf.org/html/rfc7578 * https://www.ietf.org/rfc/rfc2388.txt so I wonder if this scenario might be widespread (and endemic to Rails apps which this was) and maybe its pragmatic to include the extra spaces to cut off potential issues (it took quite a while to isolate with the live service being HTTPS only.) Steps to reproduce are here... https://github.com/exercism/pharo/issues/96#issuecomment-421224203 In the meantime, once isolated it was simple to work around, but it was almost a show stopper, so I'm interested in your thoughts. cheers -ben

1 0

[Pharo 7.0-dev] Build #1252: 22417 Decide about DateAndTimeDosEpochTest>>testToByDo
by ci-pharo-ci-jenkins2＠inria.fr Sept. 17, 2018

Sept. 17, 2018

There is a new Pharo build available! The status of the build #1252 was: FAILURE. The Pull Request #1810 was integrated: "22417 Decide about DateAndTimeDosEpochTest>>testToByDo" Pull request url: https://github.com/pharo-project/pharo/pull/1810 Issue Url: https://pharo.fogbugz.com/f/cases/22417 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1251: 22459-FileReferencecopyTo-deserves-a-much-better-comment
by ci-pharo-ci-jenkins2＠inria.fr Sept. 17, 2018

Sept. 17, 2018

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

1 0

[ANN] New Pharo 6.1 stable VM
by Esteban Lorenzano Sept. 17, 2018

Sept. 17, 2018

Hi, Following what I had in my todo list for when coming back from ESUG, I promoted a new stable VM for Pharo 6.1. This is the VM that has been tested during almost two months for Pharo 7.0, so it should be fine, but let me know if there is any problem. Esteban

1 0

[Pharo 7.0-dev] Build #1249: 22452 Added #labelHeight method.
by ci-pharo-ci-jenkins2＠inria.fr Sept. 16, 2018

Sept. 16, 2018

There is a new Pharo build available! The status of the build #1249 was: FAILURE. The Pull Request #1800 was integrated: "22452 Added #labelHeight method." Pull request url: https://github.com/pharo-project/pharo/pull/1800 Issue Url: https://pharo.fogbugz.com/f/cases/22452 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

2 1

[Pharo 7.0-dev] Build #1250: 22451 Unselecting example from SpecDemo's left list raises an exception
by ci-pharo-ci-jenkins2＠inria.fr Sept. 16, 2018

Sept. 16, 2018

There is a new Pharo build available! The status of the build #1250 was: SUCCESS. The Pull Request #1802 was integrated: "22451 Unselecting example from SpecDemo's left list raises an exception" Pull request url: https://github.com/pharo-project/pharo/pull/1802 Issue Url: https://pharo.fogbugz.com/f/cases/22451 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1248: 22454 Add comments to #presenter:configuredAs: and #presenterProvidedBy:configuredAs: methods of DynamicPresentersListBuilder
by ci-pharo-ci-jenkins2＠inria.fr Sept. 16, 2018

Sept. 16, 2018

There is a new Pharo build available! The status of the build #1248 was: FAILURE. The Pull Request #1801 was integrated: "22454 Add comments to #presenter:configuredAs: and #presenterProvidedBy:configuredAs: methods of DynamicPresentersListBuilder" Pull request url: https://github.com/pharo-project/pharo/pull/1801 Issue Url: https://pharo.fogbugz.com/f/cases/22454 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1247: 22443 Tag and comment ManifestSystemAnnouncements
by ci-pharo-ci-jenkins2＠inria.fr Sept. 14, 2018

Sept. 14, 2018

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

1 0

[Pharo 7.0-dev] Build #1246: 22446 Comment ManifestSpecInspector and ManifestSpecMorphicAdapters
by ci-pharo-ci-jenkins2＠inria.fr Sept. 13, 2018

Sept. 13, 2018

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

1 0