You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
When attempting to clone a Git repository using the SSH protocol in Iceberg within Pharo, if the cloning process is interrupted (e.g., by forgetting to load necessary dependencies and closing the windows), Iceberg incorrectly indicates that the repository already exists. However, the repository does not appear in either the Projects or System browsers, preventing further actions or re-cloning.
Steps to Reproduce:
Open Iceberg: Launch the Iceberg interface within the Pharo environment.
Initiate Clone: Attempt to clone a Git repository using the SSH protocol.
Interrupt Clone: After the cloning process, intentionally omit loading necessary dependencies in Pharo and close the Iceberg windows.
Attempt Re-clone: Try to clone the same repository again using Iceberg.
Expected Behavior:
Iceberg should either display the cloned repository in the Projects or System browsers or remove its cached reference to the repository, allowing users to perform a fresh cloning attempt without issues."
Actual Behavior:
Iceberg displays a message indicating that the repository already exists. However, the repository does not appear in the Projects or System browsers, making it impossible to manage or remove the existing (but invisible) repository. This prevents any further actions, including re-cloning the repository.
Pharo is a dynamic reflective pure object-oriented language supporting live programming inspired by Smalltalk. - pharo-project/pharo
omarabedelkader
changed the title
Unable to Re-clone Repository in Iceberg After Interrupted : SSH Clone
[Iceberg] Unable to Re-clone Repository in Iceberg After Interrupted : SSH Clone
Jan 10, 2025
Description:
When attempting to clone a Git repository using the SSH protocol in Iceberg within Pharo, if the cloning process is interrupted (e.g., by forgetting to load necessary dependencies and closing the windows), Iceberg incorrectly indicates that the repository already exists. However, the repository does not appear in either the Projects or System browsers, preventing further actions or re-cloning.
Steps to Reproduce:
Expected Behavior:
Iceberg should either display the cloned repository in the Projects or System browsers or remove its cached reference to the repository, allowing users to perform a fresh cloning attempt without issues."
Actual Behavior:
Iceberg displays a message indicating that the repository already exists. However, the repository does not appear in the Projects or System browsers, making it impossible to manage or remove the existing (but invisible) repository. This prevents any further actions, including re-cloning the repository.
Environment:
The text was updated successfully, but these errors were encountered: