Hi Saogat,
We are using it for handling distribution of test cases in Pharo. It is
based on the Svens Stomp library.
You can take a look there: https://github.com/tesonep/pharo-testWorkers
Cheers,
Vincent
From: saogat.rab--- via Pharo-users
Sent: vendredi, 5 février 2021 17:04
To:
Thanks Esteban, I've just found this thread of Stephane
http://forum.world.st/Cant-add-local-git-repo-to-Iceberg-tp5116836p5117058.html
that explains a bit
Esteban Lorenzano wrote
> Hi,
>
> From what I see, indeed you are missing some concepts of what iceberg is
> and their relation with a pack
> On 5 Feb 2021, at 17:58, Gabriel Cotelli wrote:
>
> You can also take a look at https://github.com/ba-st/ansible
Looks nice, Gabriel, I didn't know about this project.
> On Fri, Feb 5, 2021, 13:04 saogat.rab--- via Pharo-users
> wrote:
> Hi,
>
>
>
> I was wondering if anyone here used
You can also take a look at https://github.com/ba-st/ansible
On Fri, Feb 5, 2021, 13:04 saogat.rab--- via Pharo-users <
pharo-users@lists.pharo.org> wrote:
> Hi,
>
>
> I was wondering if anyone here used RabbitMQ in Pharo. Would like to hear
> about your experience.
>
>
> Kind regards,
>
> Saogat
Hi,
>From what I see, indeed you are missing some concepts of what iceberg is and
>their relation with a package.
1) iceberg is a VCS for Pharo, a frontend for git.
2) an iceberg project stores packages and its versions (commits), but for that
you have to add or create an iceberg project and add
versions are going to stay there, we never even thought on removing that ;)
they will come from Epicea instead the changes file (because yes, we want to
remove the changes file... but this one is a hard one ;) ).
and yes, they will have a timestamp (which is what the in-image versions is
lacking
Anyway Esteban, it's for sure a limit of mine, but It's an hour I'm trying to
set up a local Iceberg for my package and I can't configure it.
Some issue I faced:
1) I opened Iceberg and saw "pharo" had "Local repository missing", I guess
there is a sort of default configuration so I tried to repai
Thank you, Sven! Looks promising!
Kind regards,
Saogat
Hi,
You could use the following:
https://github.com/svenvc/stamp
which is an implementation of STOMP
https://en.wikipedia.org/wiki/Streaming_Text_Oriented_Messaging_Protocol
which works fine with RabbitMQ and Pharo.
Sven
> On 5 Feb 2021, at 17:03, saogat.rab--- via Pharo-users
> wrote:
Hi,
I was wondering if anyone here used RabbitMQ in Pharo. Would like to hear
about your experience.
Kind regards,
Saogat
So, will this remain in the image, and the timestamp will be eventually fixed?
Thanks
We do not lose the history of changes between commits, Noury.
You still have the changes in-image (which was where they were before).
What you do not have anymore in the image is the author information.
But changes are there, version browser still shows all your changes, as before
(just without t
Thanks Esteban for pointing the history tool + reminding the roadmap.
There is something we'll be missing is that we loose the history of changes
between commits.
Often I experiment different implementations or introduce some code just for
debug purpose. I do it between commits. Is there a solut
Thanks
Esteban Lorenzano wrote
> indeed, it will fetch the history of each method that belongs to an
> iceberg repository.
>
> Esteban
> On Feb 5 2021, at 11:50 am, Davide Varvello via Pharo-users <
> pharo-users@.pharo
> > wrote:
>> Hi Esteban,
>> The "history" button in the minitoolbar of ca
indeed, it will fetch the history of each method that belongs to an iceberg
repository.
Esteban
On Feb 5 2021, at 11:50 am, Davide Varvello via Pharo-users
wrote:
> Hi Esteban,
> The "history" button in the minitoolbar of calypso is related to git, right?
> Because it's not shown in every metho
Hi Esteban,
The "history" button in the minitoolbar of calypso is related to git, right?
Because it's not shown in every method
Cheers
Davide
Esteban Lorenzano wrote
> Hi all,
>
> While the timestamp for the in-image change is, indeed, missing and needs
> to be fixed, I want to point that we are
Based on your comments Esteban, I have suggested to close the corresponding
issue 7283. Closer integration to git from within the image sounds
promising.
>
Thanks, Estaban.
I realize that you are not offering a solution. But, you are recognizing the
benefit of one.
On February 5, 2021 12:33:14 AM PST, Esteban Lorenzano
wrote:
>change history for method is already there (as explained in my previous
>mail).
>for class and package level is something
change history for method is already there (as explained in my previous mail).
for class and package level is something I always wanted to implement (class
level is particularly easy to implement, with tonel format) but I didn't find
the time to do it.
Volunteers to implement are welcome! ;)
Est
Hi all,
While the timestamp for the in-image change is, indeed, missing and needs to be
fixed, I want to point that we are abandoning the in-image author tracking by
method and replacing it with the git history (which wive you also authorship
and timestamp by commit).
This method commit history
Oh, yes/ That is one of the things I most love about ENVY and miss in
everything else.
What is the change history of this method, class, package, etc.?
On Thu, Feb 4, 2021 at 10:09 PM Kasper Osterbye
wrote:
> I went in and updated the corresponding github issue (
> https://github.com/pharo-proje
👏
Davide
Kasper Osterbye wrote
> I went in and updated the corresponding github issue (
> https://github.com/pharo-project/pharo/issues/7283). The tool is really
> useful, and it would be nice to have the author and timestamp in place
> again.
>
>>
--
Sent from: http://forum.world.st/Pharo-
22 matches
Mail list logo
