bahmutov / bahmutov/netlify-plugin-github-dispatch

Error: function () { [native code] } could not be cloned.

Offen
#5 7 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
bug
Vorherrschende Sprache
JavaScript
Sterne
6
Forks
1
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

Hi @bahmutov this plugin is exactly what we need.

The first error I came across after following your steps was:
```
8:32:52 AM: Configuration error
8:32:52 AM: ────────────────────────────────────────────────────────────────
8:32:52 AM: ​
8:32:52 AM: Error message
8:32:52 AM: Plugins must be installed either in the Netlify App or in "package.json".
8:32:52 AM: Please run "npm install -D netlify-plugin-github-dispatch" or "yarn add -D netlify-plugin-github-dispatch".
```
So I did as the message suggests and ran `npm install -D netlify-plugin-github-dispatch`.

Then I can get further and the Netlify Deploy log returns this message from this plugin:
![image](https://user-images.githubusercontent.com/1033474/147264195-11286cd7-6d41-4ae5-92db-b885d5360733.png)

But the logs then show a second error, which I'm stuck on is:
```
8:35:32 AM: Plugin "netlify-plugin-github-dispatch" internal error
8:35:32 AM: ────────────────────────────────────────────────────────────────
8:35:32 AM: ​
8:35:32 AM: Error message
8:35:32 AM: Error: function () { [native code] } could not be cloned.
8:35:32 AM: ​
8:35:32 AM: Plugin details
8:35:32 AM: Package: netlify-plugin-github-dispatch
8:35:32 AM: Version: 1.1.0
8:35:32 AM: Repository: git+https://github.com/bahmutov/netlify-plugin-github-dispatch.git
8:35:32 AM: npm link: https://www.npmjs.com/package/netlify-plugin-github-dispatch
8:35:32 AM: Report issues: https://github.com/bahmutov/netlify-plugin-github-dispatch/issues
8:35:32 AM: ​
8:35:32 AM: Error location
8:35:32 AM: In "onSuccess" event in "netlify-plugin-github-dispatch" from netlify.toml and package.json
8:35:32 AM: at writeChannelMessage (internal/child_process/serialization.js:82:9)
8:35:32 AM: at process.target._send (internal/child_process.js:814:17)
8:35:32 AM: at process.target.send (internal/child_process.js:712:19)
8:35:32 AM: at internal/util.js:340:30
8:35:32 AM: at new Promise ()
8:35:32 AM: at bound (internal/util.js:339:12)
8:35:32 AM: at sendEventToParent (file:///opt/buildhome/node-deps/node_modules/@netlify/build/src/plugins/ipc.js:123:46)
8:35:32 AM: at handleError (file:///opt/buildhome/node-deps/node_modules/@netlify/build/src/plugins/child/error.js:13:9)
8:35:32 AM: at handleEvent (file:///opt/buildhome/node-deps/node_modules/@netlify/build/src/plugins/child/main.js:45:11)
8:35:32 AM: at processTicksAndRejections (internal/process/task_queues.js:95:5)
8:35:32 AM: ​
8:35:32 AM: Resolved config
8:35:32 AM: build:
8:35:32 AM: base: /opt/build/repo/packages/website
8:35:32 AM: command: npm run deploy
8:35:32 AM: commandOrigin: ui
8:35:32 AM: environment:
8:35:32 AM: - GITHUB_TOKEN
8:35:32 AM: - NODE_VERSION
8:35:32 AM: - SANITY_DATASET
8:35:32 AM: - SANITY_PROJECTID
8:35:32 AM: - SANITY_TOKEN
8:35:32 AM: publish: /opt/build/repo/packages/website/fakedist
8:35:32 AM: publishOrigin: ui
8:35:32 AM: functionsDirectory: /opt/build/repo/packages/website/functions
8:35:32 AM: plugins:
8:35:32 AM: - inputs: {}
8:35:32 AM: origin: config
8:35:32 AM: package: netlify-plugin-github-dispatch
8:35:32 AM: redirects:
8:35:32 AM: - force: true
8:35:32 AM: from: /pdf/*
status: 200
to: /.netlify/functions/file/:splat
```

After this the Netlify Build Completes but my GH Actions workflow is not triggered.

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

Beginne damit, den Netlify Deploy mit netlify-plugin-github-dispatch Version 1.1.0 zu reproduzieren, und untersuche den im Log gezeigten onSuccess-Ereignispfad, insbesondere die Plugin-Konfiguration aus netlify.toml und package.json. Verfolge die Funktion, die über die IPC-Kommunikation des Child-Prozesses von Netlify Build gesendet wird, und überprüfe anschließend, dass der Deploy ohne den Cloning-Fehler abgeschlossen wird und den konfigurierten GitHub Actions-Workflow auslöst.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
github-actions, javascript
Bereich
ci-cd, devops
Issue-Typ
Bug
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.