Pharo-dev

By thread

pharo-dev@lists.pharo.org

March 2020

151 messages

Re: [Pharo-dev] Iceberg Bug? Branches with $/

by Bernhard Pieber

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 <btc(a)openInWorld.com>: > > Even from the command line I find slashes in branch names problematic, > because slashes are as a "remote/branch" separator incites confusion about what is being referenced. > > Other have different problems... > > https://stackoverflow.com/questions/273695/what-are-some-examples-of-common… > "slashes can cause problems. Because branches are implemented as paths, > you cannot have a branch named "foo" and another branch named "foo/bar". This can be confusing for new users." > > "I'm going to start a campaign to never use slashes in git branch naming. The reason for this is that if on a CI for example, > you want to refer to the branch name when packaging code for example, you want to refer to the name of the branch > when building a URI or PATH (for example), perhaps building a URI in a bash script; you will have trouble building the URI due > to the slash adding a URL part. Yes its possible to replace the slash but it is going to take me to much time to sort out." > > > https://news.ycombinator.com/item?id=8872683 > "If you use '/' is branch names you can create path conflicts. I've seen it happen and it took me a day to debug and figure out. > There is some code checking for path conflicts in the git source but it's not invoked via all code paths that create branches. > I recommend against using slashes in branch names unless you know what you are doing. > For example: > $ git branch fireos > $ git branch fireos/feature-branch > error: unable to create directory for .git/refs/heads/fireos/feature-branch > fatal: Failed to lock ref for update: No such file or directory > This happens because creating 'fireos' branch stores the sha1 in file .git/refs/heads/fireos. > But if you later want to create branch 'fireos/feature-branch', git needs to store the sha1 in .git/refs/heads/fireos/feature-branch. > This is impossible because 'fireos' is a file and cannot be a directory. Path conflict. > > It gets even uglier when you don't discover those conflicts until a pull or push. > > cheers -ben > > > > > > > On Tue, 14 Jan 2020 at 07:45, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > As per common Git workflow, I named an issue branch "port/mac-pharo-7". When > trying to load via: > Metacello new > baseline: 'VLC'; > repository: 'github://seandenigris/Pharo-LibVLC:port/mac-pharo-7'; > onConflict: [ :ex | ex allow ]; > load. > > I got: NotFound: Revspec 'port' not found.. > > Bug? > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

March 29, 2020

[Pharo 9.0] Build #198: 6012-Click-outside-of-completion-pop-up-should-close-it

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #198 was: SUCCESS. The Pull Request #6017 was integrated: "6012-Click-outside-of-completion-pop-up-should-close-it" Pull request url: https://github.com/pharo-project/pharo/pull/6017 Issue Url: https://github.com/pharo-project/pharo/issues/6012 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 27, 2020

[Pharo 9.0] Build #197: Queue pending mouse events

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #197 was: SUCCESS. The Pull Request #6039 was integrated: "Queue pending mouse events" Pull request url: https://github.com/pharo-project/pharo/pull/6039 Issue Url: https://github.com/pharo-project/pharo/issues/fix/6003 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 27, 2020

[Pharo 9.0] Build #196: [easy][cleanup] removes a duplicated method

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #196 was: FAILURE. The Pull Request #6030 was integrated: "[easy][cleanup] removes a duplicated method" Pull request url: https://github.com/pharo-project/pharo/pull/6030 Issue Url: https://github.com/pharo-project/pharo/issues/ASTTesting Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 27, 2020

[Pharo 9.0] Build #195: Release test for proper tag casing

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #195 was: SUCCESS. The Pull Request #6018 was integrated: "Release test for proper tag casing" Pull request url: https://github.com/pharo-project/pharo/pull/6018 Issue Url: https://github.com/pharo-project/pharo/issues/2515 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 27, 2020

[Pharo 8.0] Build #1136: 5991-In-place-edition-of-inspector-fails

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1136 was: SUCCESS. The Pull Request #6014 was integrated: "5991-In-place-edition-of-inspector-fails" Pull request url: https://github.com/pharo-project/pharo/pull/6014 Issue Url: https://github.com/pharo-project/pharo/issues/5991 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 27, 2020

[Pharo 9.0] Build #194: 6002-Generate-accessors-on-inst-var-does-not-work

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #194 was: FAILURE. The Pull Request #6026 was integrated: "6002-Generate-accessors-on-inst-var-does-not-work" Pull request url: https://github.com/pharo-project/pharo/pull/6026 Issue Url: https://github.com/pharo-project/pharo/issues/6002 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 27, 2020

[Pharo 9.0] Build #193: fixes: #5883 uses lazy initialization since the initialise since not â¦

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #193 was: SUCCESS. The Pull Request #6027 was integrated: "fixes: #5883 uses lazy initialization since the initialise since not â¦" Pull request url: https://github.com/pharo-project/pharo/pull/6027 Issue Url: https://github.com/pharo-project/pharo/issues/5983 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 27, 2020

[Pharo 9.0] Build #192: [fix] separation between isTemp from the compiler/AST pov

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #192 was: FAILURE. The Pull Request #6013 was integrated: "[fix] separation between isTemp from the compiler/AST pov" Pull request url: https://github.com/pharo-project/pharo/pull/6013 Issue Url: https://github.com/pharo-project/pharo/issues/ASTTesting Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 27, 2020

Today 27/03/2020: Pharo Sprint!

by Guillermo Polito

Hi all, Today we are having a dematerialized Pharo sprint. # What is this sprint thingy? We join. We fix bugs. We discuss about fixing bugs. We add documentation. We review issues and pull requests. We make Pharo better for us and for everybody else :). # How is this sprint thing going on? In discord we have a text and a voice channel dedicated to #sprint. http://pharo.org/community <http://pharo.org/community> Please feel free to join and ask questions # What can I do to help? ## Get some knowledge => Read a couple of issues We have > 500 open issues. Some of them are difficult to reproduce, or the instructions are not clear enough, or maybe were already fixed but the issue was never closed. If everybody takes 3 issues at random and makes a review, we will be in much better shape for the next sprint!! Reviewing an issue is as easy as asking yourself the questions: - are there reproduction instructions? - it is specified the version / commit? - can I reproduce it? If some of those check fails, put a comment :) ## Get some action => Fix an easy issue In this morning (europe time) Iâve taken some time doing a pass on issues, and Iâve identified a list of potentially easy ones. https://github.com/pharo-project/pharo/issues?q=is%3Aissue+is%3Aopen+label%… <https://github.com/pharo-project/pharo/issues?q=is:issue+is:open+label:Easy> Iâve also categorised several of them as bugs, enhancements, new features and cleanups. Within those, youâll see - super-easy (like adding a comment), - medium-easy (like changing some code following the analysis on the issue) and - hard-easy like a cleanup refactoring So if somebody wants to do a contribution for the first time, this list of 26 issues is probably a good place to look at. The info of how to make a PR is in here https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo <https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo> ## Get to know other people involved in Pharo => Discuss with us in discord And have fun :) Guille

March 27, 2020

Jump to page: