Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

`include` target folder named `certs` or `certificates` gives a runtime action error

Aperta
  • Qualcosa non va?
#673 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
38/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
javascript
Ambito
cli

Direzione di ricerca

Inizia con le voci include in app.config.yaml e riproduci il problema usando aio app run, aio rt action invoke e aio rt activation get. Confronta il target secrets/ funzionante con certs/ e certificates/, quindi segui l’errore di runtime attraverso services/runner.js; il lavoro è completato quando entrambi i nomi target dei certificati producono un’attivazione riuscita.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug

Describe the bug
Are there any reserved names for the target "folder" when using include to configure a runtime action?
We are experiencing the following behavior:

  • an include declared as this one works
include:
  - ["files/*.p12", "secrets/"]

but these two (targeting to certs and certificates) cause the action to yield an error when invoked

include:
  - ["files/*.p12", "certs/"]

and

include:
  - ["files/*.p12", "certificates/"]

The error we get when calling aio rt activation get XXXXXX is

 "error": "Initialization has failed due to: Error: Cannot find module '/nodejsAction/47jUsebx'\nRequire stack:\n- /nodejsAction/services/runner.js\n- /nodejsAction/services/service.js\n- /nodejsAction/routes/action.js\n- /nodejsAction/app.js\n- /nodejsAction/server.js\n    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:956:15)\n    at Function.Module._load (node:internal/modules/cjs/loader:804:27)\n    at Module.require (node:internal/modules/cjs/loader:1028:19)\n    at require (node:internal/modules/cjs/helpers:102:18)\n    at eval (eval at <anonymous> (/nodejsAction/services/runner.js:76:49), <anonymous>:1:1)\n    at /nodejsAction/services/runner.js:76:49\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)"

To Reproduce
Steps to reproduce the behavior:

  1. Configure a generic runtime action with an include like this in app.config.yaml
include:
  - ["files/*.p12", "certs/"]
  1. Run the application with aio app run
  2. Call the action with aio rt action invoke xxxxxxxx/generic
  3. Get the invocation result with aio rt activation get UUID
    5 In the invocation details the following error can be seen:
"response": {
    "result": {
      "error": "Initialization has failed due to: Error: Cannot find module '/nodejsAction/47jUsebx'\nRequire stack:\n- /nodejsAction/services/runner.js\n- /nodejsAction/services/service.js\n- /nodejsAction/routes/action.js\n- /nodejsAction/app.js\n- /nodejsAction/server.js\n    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:956:15)\n    at Function.Module._load (node:internal/modules/cjs/loader:804:27)\n    at Module.require (node:internal/modules/cjs/loader:1028:19)\n    at require (node:internal/modules/cjs/helpers:102:18)\n    at eval (eval at <anonymous> (/nodejsAction/services/runner.js:76:49), <anonymous>:1:1)\n    at /nodejsAction/services/runner.js:76:49\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)"
    },
    "size": 765,
    "status": "application error",
    "success": false
  },

Expected behavior
A successful rt action activation

Screenshots

Desktop (please complete the following information):

  • OS: macOs
  • Browser: chrome
  • Version
> aio --version
@adobe/aio-cli/9.2.0 darwin-arm64 node-v16.18.1

Smartphone (please complete the following information):
N/A

Additional context
Here's a repo enterprise-integration/client-cert-poc containing

  • a working include in master and
  • a failing include in the ACSP-44-broken-include branch

Here's a slack thread with a discussion about this bug: https://magento.slack.com/archives/C013UDBFBGB/p1684146514658789

Lingua principale
JavaScript
Stelle
28
Fork
41
Merge medio
1g 13h
PR unite (30g)
6

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di adobe/aio-cli-plugin-app

Tutte le issue di adobe/aio-cli-plugin-app

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.