Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[list] Copying large folders is unreliable

Open
#244 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, javascript
Domain
cli, cloud

Research direction

No files, tests, or entry points are named. Start by tracing large-folder copy handling in da-admin, including the S3 SDK interaction and DA_JOBS relationship; reproduce a copy over 500 items and document what completion and resume behavior should look like.

Written by the indexing model from the issue text.

Description

We have several issues that creates instability with large (> 500 items) folder copies.

  1. Fundamental issues with content integrity we (or S3 SDK) dies on - "empty" or // prefixes
  2. The relationship with DA_JOBS seems brittle. I cannot reliably copy anything of meaningful size.
  3. We are not resilient to "Network changed" errors that may happen on the client. Ideally the client has a way to pick up where they left off. This could be as simple as getting the continuation token and when supplying back da-admin looks at DA_JOBS to see if there's an existing job.
Dominant language
JavaScript
Stars
6
Forks
17
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from adobe/da-admin

All issues in adobe/da-admin

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.