Pharo 10 locks up when reverting changes in Epicea

[Shaping]

Pharo version: 10 64-bit OS: Windows 10 Pro

I filed in Christian Haider's Values project (translated from VW). The file in last 7 minutes. Many hundreds of classes and probably thousands of methods were successfully filed in and timestamped as shown in Epicea. Two days later I decided to delete these changes. I chose revert from Epicea's context menu after selected all items. There was a latency of about 5 mintues before I saw the image above. No wait curso appeared. A wait cursor should have appeared. When the above shown result occurred the image was still locked up. I could do nothing with it.

I then refreshed Epicea and got this results after many mintues of waiting, again without a wait cursor showing:

That makes more sense, but the result took much too long, and there is not reason for the intermediate result shown above. Why does pharo take 5 minutes to delete a few thousands methods from the image and then another 5 minutes to display a consistent and correct view of the image, instead of the above-shown intermediate state in which object cannot be found. Of course they cannot be found. They were just deleted.

Another refresh of Epicea produces a very long wait and a mostly locked up image with the following new information:

This is the same inconsistent state shown before. Why is Epicea performing so slowly?

Basic behaviors like this that don't scale (delays that are too long for simple operations) are cause for worry. Can this be fixed? Is this a known problem with Epicea. Is someone activity working on a scalable solution, so that he user doesn't wait 5 or 10 or 15 minutes for the Epicea window to update?

For browsing changes, is there a faster alternative?

Why does Epicea not permit the user to delete the change set shown in the left column, especially when it is too large and slow to refresh or edit (do reversions on)?

[astares]

No need to file this in. You can use https://github.com/astares/Pharo-Values

GitHub

GitHub - astares/Pharo-Values: Port of Values to Pharo

Port of Values to Pharo. Contribute to astares/Pharo-Values development by creating an account on GitHub.

[Ducasse]

Epicea is not good for what you wanted. It has to go over all the changes and we should revisit it. Now if you want to remove code just click on the package and delete. Epicea is not a version control tool at package level, it is more a microcommit log.

[Ducasse]

We should really rethink a part of the design of Epicea. Now use iceberg and github. These are the right tools (and they work when github does not change the ground under our feets - I hate the fact that they can change git protocols in a way that we got exposed to their changes). Now when git does not change in non compatible way this is working quite well - we manage all pharo and moose projects and more and it is working for real.