Skip to content

Conversation

aleck7
Copy link

@aleck7 aleck7 commented Aug 14, 2025

Proposed changes

S3 support was outdated and broken

The fix is simply a 2 minutes one by Q dev. Works fine, but surely code review is a must

Checklist

👉 Our coding style can be found here: https://midnight-commander.org/coding-style/ 👈

  • I have referenced the issue(s) resolved by this PR (if any)
  • I have signed-off my contribution with git commit --amend -s
  • Lint and unit tests pass locally with my changes (make indent && make check)
  • I have added tests that prove my fix is effective or that my feature works
  • I have added the necessary documentation (if appropriate)

@github-actions github-actions bot added needs triage Needs triage by maintainers prio: medium Has the potential to affect progress labels Aug 14, 2025
@github-actions github-actions bot added this to the Future Releases milestone Aug 14, 2025
Copy link
Member

@zyv zyv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for updating this to Boto3 and Futures. After integrating the Python 3 update, we didn't have the time or energy to tackle the Boto3 migration.

Is there an easy way to test this without using AWS credentials before merging?

handle_client_error('Unable to list buckets', e)

# Import python timezones (pytz)
try:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Starting with Python 3.9, the standard library includes time zone support. It would be best to try in the following order: 1) the standard library, 2) pytz, and 3) the fallback.

@@ -1,7 +1,7 @@
#! @PYTHON@
#!/usr/bin/env python3
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please leave it as is. It will be replaced during the build.

Comment on lines -35 to -42
# Settings: (should be set via environment)
# Required:
# AWS_ACCESS_KEY_ID : Amazon AWS access key (required)
# AWS_SECRET_ACCESS_KEY : Amazon AWS secret access key (required)
# Optional:
# MCVFS_EXTFS_S3_LOCATION : where to create new buckets: "EU" - default, "USWest", "APNortheast" etc.
# MCVFS_EXTFS_S3_DEBUGFILE : write debug info to this file (no info by default)
# MCVFS_EXTFS_S3_DEBUGLEVEL : debug messages level ("WARNING" - default, "DEBUG" - verbose)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please leave the settings block and update it to reflect the current state?

@zyv zyv modified the milestones: Future Releases, 4.8.34 Aug 14, 2025
@zyv zyv added area: vfs Virtual File System support and removed needs triage Needs triage by maintainers labels Aug 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: vfs Virtual File System support prio: medium Has the potential to affect progress
Development

Successfully merging this pull request may close these issues.

2 participants