adobe / adobe/reactor-uploader
Uploading will sometimes report an error even though extension package processing is still occurring on the Launch servers.
- Dominant language
- JavaScript
- Stars
- 10
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
### Expected Behaviour
When uploading an extension package, the packager should more gracefully handle longer-than-expected upload times.
### Actual Behaviour
The uploader uses a retry loop of 50 times, then errors out. Extension processing usually still happens on the Launch servers just fine.
### Reproduce Scenario (including but not limited to)
Unsure
#### Steps to Reproduce
Consult with Launch API team about reasons that an extension package would take a long time to process.
#### Platform and Version
@adobe/reactor-uploaderv5.0.2
#### Sample Code that illustrates the problem
https://github.com/adobe/reactor-uploader/blob/master/bin/monitorStatus.js#L21-L33
#### Logs taken while reproducing problem

Contributor guide
Research direction
Start with bin/monitorStatus.js lines 21–33, which the issue identifies as the sample for the retry loop. The issue suggests consulting the Launch API team to understand why package processing takes longer than expected; the reproduction steps are otherwise unknown. Done means the uploader handles longer processing without reporting an error while the Launch servers are still processing the package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100