- Pharo-users - lists.pharo.org

Re: [Pharo-users] Mongo-BSON OID LargePositiveInteger increase

by Henrik Johansen

Hi Holger, sorry, I'm not good at responding to unsorted email in a timely manner :/ The comment is inaccurate, the wraparound relates to how the number is used in OID >> #initialize, not the number itself. lp := LargePositiveInteger new: 3. lp at: 1 put: 255; at: 2 put: 255; at: 3 put: 255. lp := lp digitAdd: 1. (ByteArray new: 3) replaceFrom: 1 to: 3 with: lp startingAt: 1; yourself So the number will keep on growing, but for the purposes of our use, it wraps around. Cheers, Henry > On 30 May 2016, at 9:57 , Holger Freyther <holger(a)freyther.de> wrote: > > Hi, > > I tried to reach the author for several weeks but he doesn't seem to respond so I am trying to reach a wider audience to either confirm my suspicion or to be corrected. In > http://smalltalkhub.com/#!/~MongoTalkTeam/mongotalk/diff/Mongo-BSON-HenrikS… > > the following change is done: > > + "digitAdd: wraps around to 0 when result would overflow" > + ^ counter := counter > + ifNil:[self newCounter] > + ifNotNil:[counter digitAdd: 1]! > - ^ counter := (counter + 1) \\ 16rFFFFFF! > > The old code has overflow checking, the new code makes a statement I don't think is true. counter is LargePositiveInteger new: 3 to use three bytes. So given the above code and the experiment (yes I could just add a bigger number) > > | id | > id := LargePositiveInteger. > 1 to: (16777215 + 50) do: [:each | > id := id digitAdd: 1]. > id. > > Given the comment it should overflow and the value be 50? This is not what the result is. So shall the truncation be added again or at least the comment be updated? The code will go from LargePositiveInteger to SmallInteger when overflowing from three to four bytes but luckily > >>> #value > ... > replaceFrom: 1 to: 3 with: self class counterNext startingAt: 1 > > will even work when counterNext returns a SmallInteger. But given the old code and the comment in the new code this is does not seem to function as intended? > > kind regards > holger > > > PS: The other part is that >>#newCounter doesn't seem to be ever executed. On first load >>#initialize will call >>#reset and on >>#shutDown: calls reset. So the code to "randomize" the initial counter doesn't seem to work. > >

May 30, 2016

Re: [Pharo-users] [ANN] LibnotifyBinding: a binding to libnotify 0.7.6 for Pharo

by Julien Delplanque

Good idea, I will have a look at this feature. :-) Julien On 30/05/16 17:07, Denis Kudriashov wrote: > Nice. > > And it would be much nicer if Pharo allows to install it as new > notifications backend (instead of morphic one). > > 2016-05-30 16:50 GMT+02:00 Julien Delplanque <julien(a)tamere.eu>: > >> Hello, >> >> I took the libnotify [0] binding for Squeak [1], adapted it to use the >> Pharo UFFI API and >> enhanced it. It is available here [2] and seems to work well (see attached >> image). >> >> It does not cover all libnotify possibilities (see the README on github) >> but it is already >> usable to display notifications with eventually icons, set urgency, set >> timeout, etc... >> >> It was great to try UFFI, it is really easy to use. Thanks a lot for it! >> :-) >> >> Regards, >> >> Julien >> >> Links: >> [0]: https://developer.gnome.org/libnotify/ >> [1]: http://www.squeaksource.com/libnotify.html >> [2]: https://github.com/juliendelplanque/LibnotifyBinding >>

May 30, 2016

Re: [Pharo-users] Call for feedbacks: Enterprise Pharo ePub version

by Andy Burnett

> > > Hi, > > I created an ePub version of the book Enterprise Pharo for electronic > readers. > It would be great if you could test it and give me feedbacks on everything > that shocks you. > > You can downlod the file here< > http://files.pharo.org/books-ressources/entreprise-pharo/>. > > Thanks, > Thibault > Works very nicely on my iPhone. It would be great to have all the books in this format. Cheers Andy

May 30, 2016

Re: [Pharo-users] [ANN] LibnotifyBinding: a binding to libnotify 0.7.6 for Pharo

by Denis Kudriashov

Nice. And it would be much nicer if Pharo allows to install it as new notifications backend (instead of morphic one). 2016-05-30 16:50 GMT+02:00 Julien Delplanque <julien(a)tamere.eu>: > Hello, > > I took the libnotify [0] binding for Squeak [1], adapted it to use the > Pharo UFFI API and > enhanced it. It is available here [2] and seems to work well (see attached > image). > > It does not cover all libnotify possibilities (see the README on github) > but it is already > usable to display notifications with eventually icons, set urgency, set > timeout, etc... > > It was great to try UFFI, it is really easy to use. Thanks a lot for it! > :-) > > Regards, > > Julien > > Links: > [0]: https://developer.gnome.org/libnotify/ > [1]: http://www.squeaksource.com/libnotify.html > [2]: https://github.com/juliendelplanque/LibnotifyBinding >

May 30, 2016

[ANN] OSSubprocess Bugfix release

by Mariano Martinez Peck

Dear all, I have just released a new bugfix release v0.2.3 for OSSubprocess as you can see in [1]. I recommend everyone to move to this release. Cheers, [1] https://github.com/marianopeck/OSSubprocess/releases/tag/v0.2.3 -- Mariano http://marianopeck.wordpress.com

May 30, 2016

[ANN] LibnotifyBinding: a binding to libnotify 0.7.6 for Pharo

by Julien Delplanque

Hello, I took the libnotify [0] binding for Squeak [1], adapted it to use the Pharo UFFI API and enhanced it. It is available here [2] and seems to work well (see attached image). It does not cover all libnotify possibilities (see the README on github) but it is already usable to display notifications with eventually icons, set urgency, set timeout, etc... It was great to try UFFI, it is really easy to use. Thanks a lot for it! :-) Regards, Julien Links: [0]: https://developer.gnome.org/libnotify/ [1]: http://www.squeaksource.com/libnotify.html [2]: https://github.com/juliendelplanque/LibnotifyBinding

May 30, 2016

Call for feedbacks: Enterprise Pharo ePub version

by Thibault ARLOING

Hi, I created an ePub version of the book Enterprise Pharo for electronic readers. It would be great if you could test it and give me feedbacks on everything that shocks you. You can downlod the file here<http://files.pharo.org/books-ressources/entreprise-pharo/>. Thanks, Thibault

May 30, 2016

Re: [Pharo-users] [ANN] New Pharo Glorp version and Book chapter

by Esteban A. Maringolo

Thanks all. There were several people that helped me along this endeavor and I thank again the Pharo Consortium for pushing this. 2016-05-30 5:04 GMT-03:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > Good job, Esteban. > Now we need good Garage drivers for databases which not lock image. Does > anyone plan to work on Oracle and SQLServer backends? The Garage drivers got hurt by the changes in the FFI API (UFFI), but there are some people working on getting them back for Pharo 5. This is really important, and for those RDBMS you mention in particular, according to a survey [1] I did at the end of last year. We'll get there. Those willing to discuss issues or collaborate on these topics can always use this mailing list, but there is an active community of developers in the Pharo Project Slack team, we have one channel dedicated to database discussion [2]. Also, I copied the latest commit from the SmalltalkHub repo to GitHub in order to use its issue tracker [3] for bug reporting. Regards! [1] https://medium.com/@emaringolo/pharo-rdbms-support-survey-results-9c8f64087… [2] https://pharoproject.slack.com/messages/databases/ [3] https://github.com/DBXTalk/Glorp/issues

May 30, 2016

Re: [Pharo-users] Is lazy evaluation of infinite series possible?

by Hilaire

Did you take a look at Nicolai suggestion regarding the Generator class. There is a fibonacci example in its test case. fibo := GeneratorTest new fibonacciSequence then to access the sequence term: fibo next. Hilaire -- Dr. Geo http://drgeo.eu

May 30, 2016

Re: [Pharo-users] Saving to local git and "Loading all file names from http://...pharo5/inbox"

by Peter Uhnak

I don't see anything actionable in this thread. What can we do to move this forward? Is it only up to Dale to change the behavior? Can we have some workaround? E.g. syncing in the background at regular intervals so when I want to commit I am not blocked by it? Because it doesn't always check the repos, and I don't see what is the actual trigger. Peter On Sun, May 29, 2016 at 02:28:48PM +0200, Thierry Goubier wrote: > Le 29/05/2016 14:04, Peter Uhnak a Ã©crit : > > On Sun, May 29, 2016 at 11:21:21AM +0200, Thierry Goubier wrote: > > > Le 29/05/2016 11:15, Peter UhnÃ¡k a Ã©crit : > > > > > All this is so that my .5 would not conflict with someone else .5 > > > > > > > > How is this a problem? Because it will be "Me.5" and "You.5", so there > > > > can't be any conflict. > > > > > > Me.5 and Me.5 are possible... > > > > > > Think of numbering your own stuff on two different branches. > > > > > > More, Metacello depends on Me.5 5 to be greater than You.5 5 for some of the > > > baselines / configurations to work properly :) > > > > Can't it use the ancestry to decide? > > I suggested that to Dale... Disregard version numbers, only consider as > newer if the other is in the ancestry chain. > > Would also be a lot more precise, because we would then use the package > version UID instead of the name.version number approximation which can leads > to failures or loading the wrong package in some cases. > > > Because my impression is from this that merges are naive, compared to > > git which actually checks the ancestry of both up the common endpoint > > and diffs based on that. > > This does not describe the Monticello merges. Monticello merges do walk the > ancestry chain to find a common ancestor and does a three way merge, as git > does. > > The problem is that the Monticello ancestry chain is often damaged for three > reasons: removing part of it to reduce memory usage (Done for the Pharo3 > release), removing all or part of it because your package ancestry chain is > too long (I remember seeing some packages doing that on purpose?), the > common ancestor doesn't exist anymore in the repositories visible to > Monticello (long-lived packages that have moved between repositories, > typically). > > When Monticello sees a version in the history, it expects the full package > to be available in the repositories; if this package is the common ancestor > of the merge and can't be retrieved, then the merge will fail. > > What GitFileTree/git does there is to ensure that if a version is in the > ancestry, it can be retrieved. Git merge also use that property. Any > GitFileTree-like layer would provide the same property (FossilFileTree, for > example). > > Note: in the git documentation, it is stated that git may create virtual > ancestors in some cases, to simplify/reduce the merge work. In such cases, > if set up, the gitfiletree merge driver will be called for all those merges > (i.e. a single merge in git may trigger multiple merges). > > Obvious, isn't it ;) > > Thierry > > > Peter > > > > > > > > Thierry > > > > > > > > > > > Peter > > > > > > > > On Sun, May 29, 2016 at 10:37 AM, Sven Van Caekenberghe <sven(a)stfx.eu > > > > <mailto:sven@stfx.eu>> wrote: > > > > > > > > > > > > > On 29 May 2016, at 10:28, Holger Freyther <holger(a)freyther.de <mailto:holger@freyther.de>> wrote: > > > > > > > > > > > > > > >> On 29 May 2016, at 09:58, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: > > > > >> > > > > >> > > > > >>> > > > > >>> For some reason the package manager is refreshing all packages. I don't know why it happens, and it's quite annoying (because it slows down commits), but it doesn't cause any actual problems, so don't worry about it too much. > > > > >> > > > > >> As I understand it, what happens is the following: before you commit to your MC repo, you have to find the next version number; a check is then done in all relevant repos; the cached content is not used, but an actual refresh is done. All this is so that my .5 would not conflict with someone else .5 - the chance that this happens is very small, and the check does not really prevent it. > > > > > > > > > > I assumed that but can it be limited to the Repositories that are associated with the package? I am afraid that next time I travel I can not commit to my local repository (and ofcourse the speed part). :) > > > > > > > > We should go one step further: add an option to totally disable this > > > > check to go outside the target repo, it makes little sense. But MC > > > > is a complex beast ... > > > > > > > > > holger > > > > > > > > > > > > > > > > > > > > > > > >

May 30, 2016