Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remote file Info modified date still wrong 4.3.1 11008 #7236

Closed
cyberduck opened this issue May 10, 2013 · 2 comments
Closed

remote file Info modified date still wrong 4.3.1 11008 #7236

cyberduck opened this issue May 10, 2013 · 2 comments
Assignees
Milestone

Comments

@cyberduck
Copy link
Collaborator

f411c1e created the issue

Hi - I updated Cyberduck this evening to released 4.3.1 11008, which is actually later than the Nightly I had been set for.

This 11008 release fixed a problem with dates on uploaded files so that they are now correct. However, the date in the Info box for the file is still incorrect; essentially zero. I've attached a screenshot so you can see.

I'd like to mention another problem, which was severe on the original 4.3 release, has improved with Nightlies, and still happened once this evening on the previous Nightly release. I haven't seen it yet on this new 11008, but there isn't much experience yet.

This problem is that Cyberduck essentially locks up, apparently on trying to update a directory view unsuccessfully, often after an upload I think. The extra symptom you can notice is that there will be a flickering on the NN Files indication on the lower left corner of the main display.

I thought the flickering was more intermittent on the problem tonight than on the original, but in fact the directory display was still incorrect - not showing a folder that had been uploaded.

You are free to navigate to other folders when this happens, but this fixes nothing. When you go back to the wrongly indicated folder, the folder is still missing. Refreshing with the big curved arrow button does nothing to change this state either.

As mentioned, this was very severe on the initial 4.3 release, but has happened much less often in later 4.3.1 nightlies. There's also the concern that the current release point was a later build than the nightly. Anyway, I presume you know about this and are trying to clear it -- just possibly it has to do with the file/folder modified times bug I am reporting.

I'll update if this problem still shows in 11008 as more experience comes with it. It seems then it should be another ticket. In any case, Cyberduck is great to have; not sure how I got along on Windows without it ;)


Attachments

@cyberduck
Copy link
Collaborator Author

@ylangisc commented

Second issue should be fixed with f49d26e (also refer to #7240).

@cyberduck
Copy link
Collaborator Author

@ylangisc commented

Date issue fixed in ec09a74.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants