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

"Critical SFTP Save Failure: Changes Not Persisting on Remote Servers" #1088

Open
1 task done
krypterro opened this issue Dec 1, 2024 · 4 comments
Open
1 task done
Labels
bug Something isn't working

Comments

@krypterro
Copy link

Check for existing issues

  • Completed

Describe the bug / provide steps to reproduce it

Issue Summary:
I use Acode on Android extensively, primarily for managing a large codebase via SFTP across a network of 60+ servers. Most of my work involves editing and creating Python files under the root user account.

Problem Description:
Recently, I have encountered an issue where changes made to files are not being saved to the remote server via SFTP, even though the Acode interface indicates that the save operation was successful. Here's the sequence of events:

  1. I log into a specific server using SFTP and make changes to several Python files.

  2. After editing, I save the files. The yellow dot on the tab disappears, and the local copy in memory reflects the changes.

  3. However, when I log back into the same server later, the changes are missing from the remote files.

This issue seems to have started with recent updates and may be linked to conditions where upload bandwidth is constrained. I often work over a 5G cellular connection, which isn’t always consistent or optimal.

Suspected Cause:
I suspect that the SFTP module in Acode does not have a robust mechanism to confirm successful file uploads to the server. The problem may be exacerbated when upload bandwidth is limited, causing the operation to silently fail while the app assumes the save was successful.

Proposed Solution/Questions:
Could the confirmation mechanism for the SFTP module be improved to ensure that file uploads are reliably verified? For example:

Implementing checksums or hashes to confirm the integrity of uploaded files.

Adding a "retry on failure" mechanism for SFTP uploads.

Displaying a confirmation message or error if the file upload does not succeed.

This is a critical issue for my workflow, and any insight or fixes would be greatly appreciated.

Environment

All servers are Ubuntu 22.04 LTS to 24.04 LTS, and the local client is on a Samsung S23 Ultra running Android 14 with all the latest patches.

Acode version is:
v.1.10.6 (954)

If applicable, add mockups / screenshots regarding your vission

Retry FTP/SFTP when fail, is enabled
Check file changes is disabled

If applicable, attach your Acode.log file to this issue.

Acode.log
@bajrangCoder
Copy link
Collaborator

Sorry for inconvenience 😔

We will try to fix it as soon as possible. Btw as from my testing it seems things are fine.
Please attach your Acode Logs in the issue that will be helpful in debugging.

@bajrangCoder bajrangCoder added the bug Something isn't working label Dec 2, 2024
@krypterro
Copy link
Author

How exactly do I get the Acode logs? I read the instructions here, but I'm not sure where to search for them?

@bajrangCoder
Copy link
Collaborator

How exactly do I get the Acode logs? I read the instructions here, but I'm not sure where to search for them?

In command palette, Ctrl-Shift-P to open command palette

@krypterro
Copy link
Author

I never knew that existed. There's lots of useful things in there, thanks. Log file attached.
Acode.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants