Smalltalk › Squeak › Squeak - Dev

"Move to" is somehow broken in SqueakSource's Web Interface

‹ Previous Topic Next Topic ›
 
classic Classic list List threaded Threaded
♦
♦
 5 messages Options
marcel.taeumel
Reply | Threaded
Open this post in threaded view
♦
♦
|

"Move to" is somehow broken in SqueakSource's Web Interface

marcel.taeumel
Hi all!

Inbox commits keep on reappearing even after moved to Trunk:


First moved on March 03, then again on November 04, it is now back in the Inbox again.

-.-"

Who has access to SqueakSource and can take a look at it?

Best,
Marcel
marcel.taeumel
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: "Move to" is somehow broken in SqueakSource's Web Interface

marcel.taeumel
I now moved them to Treated. Let's see how this works out...

Best,
Marcel

Am 16.12.2020 11:27:03 schrieb Marcel Taeumel <[hidden email]>:

Hi all!

Inbox commits keep on reappearing even after moved to Trunk:


First moved on March 03, then again on November 04, it is now back in the Inbox again.

-.-"

Who has access to SqueakSource and can take a look at it?

Best,
Marcel
Chris Muller-3
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: "Move to" is somehow broken in SqueakSource's Web Interface

Chris Muller-3
That version exists twice across all repositories, both in /trunk, once as Kernel-ct.1300.2020-11-04.10-39-54, and also as Kernel-ct.1300.mcz.  They both produce the same md5 checksum.

Yes, I can't believe "Move" isn't working, let's pay attention to see if it happens again.



On Wed, Dec 16, 2020 at 5:13 AM Marcel Taeumel <[hidden email]> wrote:
I now moved them to Treated. Let's see how this works out...

Best,
Marcel

Am 16.12.2020 11:27:03 schrieb Marcel Taeumel <[hidden email]>:

Hi all!

Inbox commits keep on reappearing even after moved to Trunk:


First moved on March 03, then again on November 04, it is now back in the Inbox again.

-.-"

Who has access to SqueakSource and can take a look at it?

Best,
Marcel
marcel.taeumel
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: "Move to" is somehow broken in SqueakSource's Web Interface

marcel.taeumel
> Yes, I can't believe "Move" isn't working, let's pay attention to see if it happens again.

Ah, sorry. I meant, that the "delete/cut" part of the "move" operation is not working properly in the long term. Versions keep on re-appearing in the Inbox after a while. Not sure, why. It somewhat impairs manual inbox processing. ^__^

Best,
Marcel

Am 16.12.2020 20:31:43 schrieb Chris Muller <[hidden email]>:

That version exists twice across all repositories, both in /trunk, once as Kernel-ct.1300.2020-11-04.10-39-54, and also as Kernel-ct.1300.mcz.  They both produce the same md5 checksum.

Yes, I can't believe "Move" isn't working, let's pay attention to see if it happens again.



On Wed, Dec 16, 2020 at 5:13 AM Marcel Taeumel <[hidden email]> wrote:
I now moved them to Treated. Let's see how this works out...

Best,
Marcel

Am 16.12.2020 11:27:03 schrieb Marcel Taeumel <[hidden email]>:

Hi all!

Inbox commits keep on reappearing even after moved to Trunk:


First moved on March 03, then again on November 04, it is now back in the Inbox again.

-.-"

Who has access to SqueakSource and can take a look at it?

Best,
Marcel
Chris Muller-4
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: "Move to" is somehow broken in SqueakSource's Web Interface

Chris Muller-4
On Thu, Dec 17, 2020 at 1:33 AM Marcel Taeumel <[hidden email]> wrote:
> Yes, I can't believe "Move" isn't working, let's pay attention to see if it happens again.

Ah, sorry. I meant, that the "delete/cut" part of the "move" operation is not working properly in the long term. Versions keep on re-appearing in the Inbox after a while. Not sure, why. It somewhat impairs manual inbox processing. ^__^

"After a while" may be a clue pointing to the recovery process.  It assumes everything in the project directory (e.g., /inbox) needs to be restored.  If Treating is only "marking" them somehow, but leaving them in there, that could be the cause..

That's definitely counterproductive for them to reappear after they were moved / deleted.  I'll try to look soon.
 
 - Chris
Free forum by Nabble Edit this page