adobe / adobe/aio-cli-plugin-app-dev
dev command should run actions in an isolated process
- Langage dominant
- JavaScript
- Étoiles
- 2
- Forks
- 5
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
**Describe the bug**
Currently all action code is executed in the same process, which could potentially lead to errors if any action code is modifying process.env it affects the global space.
**To Reproduce**
write 2 actions where 1 is has a sleep function
```
const sleep = async (ms) => new Promise(resolve => setTimeout(resolve, ms))
// main function that will be executed by Adobe I/O Runtime
async function main (params) {
let before = process.env.__OW_ACTIVATION_ID
console.log('before', before)
await sleep(10000)
let after = process.env.__OW_ACTIVATION_ID
console.log('after', after)
return {
statusCode: 200,
body: {
before,
after,
wasCorrupted: (before !== after)
}
}
}
exports.main = main
```
aio app dev and call this action
while it is running, use curl to call the other action
**Expected behavior**
activationId has not changed when sleeper returns
```
time: 10015 ms
{
"before": "d5afdd731a1d2384c55b8bcdb1a453e6",
"after": "d5afdd731a1d2384c55b8bcdb1a453e6",
"wasCorrupted": false
}
```
**Screenshots**
```
time: 10015 ms
{
"before": "d5afdd731a1d2384c55b8bcdb1a453e6",
"after": "f53548458df5870656339859f7af28e6",
"wasCorrupted": true
}
```
**Desktop (please complete the following information):**
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
**Smartphone (please complete the following information):**
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]
**Additional context**
Add any other context about the problem here.
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par la commande `aio app dev` et le point d’entrée de l’action `main` présenté dans la reproduction. Exécutez deux actions simultanément, y compris l’attente de 10 secondes, et observez si `process.env.__OW_ACTIVATION_ID` change entre `before` et `after`. C’est terminé lorsque les actions simultanées n’affectent plus l’environnement de processus les unes des autres.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- javascript, node.js
- Domaine
- cli
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100