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
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:
I log into a specific server using SFTP and make changes to several Python files.
After editing, I save the files. The yellow dot on the tab disappears, and the local copy in memory reflects the changes.
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
The text was updated successfully, but these errors were encountered:
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.
Check for existing issues
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:
I log into a specific server using SFTP and make changes to several Python files.
After editing, I save the files. The yellow dot on the tab disappears, and the local copy in memory reflects the changes.
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
The text was updated successfully, but these errors were encountered: