Skip to content

hiccups? #3

Description

@caspertone2003

I wonder if it is just a feeling but...
Perhaps there is a rush condition any where or an unexpected delay... sometimes.
For example, renaming a folder or downloading a file. It looks that until something is not refreshed the ack of finishing is delayed ... or perhaps it is a lack of response of the remotes.
I had not this feeling with the kapitainsky previous version.
This fork seems just to solve an issue on top of the other changes already in the afterburner of kapitainsky (so, pending a release).

Anyone has similar feelings?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions