Azure / Azure/Synapse-workspace-deployment
Getting an error in @trident/data-access-artifact
- Dominant language
- TypeScript
- Stars
- 29
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
We are encountering an issue when running the github action.
It feels like something changed in an internal node package @trident/data-access-artifact, but I don't really understand what this is about.
```
Run Azure/Synapse-workspace-deployment@V1.9.0
Bundle source : https://web.azuresynapse.net/assets/cmd-api/main.js
Downloading asset file
Asset file downloaded at : /home/***/actions-runner2/_work/***/***/downloads/main.js
Starting export operation
Executing shell command
Command : node /home/***/actions-runner2/_work/***/***/downloads/main.js export "/home/***/actions-runner2/_work/***/***/synapse" synw-***-dev-gwc ExportedArtifacts
Stdout: CmdApiApp: Initializing application.
Resource: synw-***-dev-gwc
RootFolder: /home/***/actions-runner2/_work/***/***/synapse
Stdout: ModelService: synchronize - start
Stdout: ModelService: Dynamic connector - Start registering dynamic connectors
Stdout: DynamicConnectorService: Dynamic connector - Start registering connector: Dataworld
Stdout: DynamicConnectorService: Dynamic connector - Finished registering connector: Dataworld
Stdout: DynamicConnectorService: Dynamic connector - Start registering connector: Asana
Stdout: DynamicConnectorService: Dynamic connector - Finished registering connector: Asana
DynamicConnectorService: Dynamic connector - Start registering connector: Twilio
Stdout: DynamicConnectorService: Dynamic connector - Finished registering connector: Twilio
Stdout: DynamicConnectorService: Dynamic connector - Start registering connector: AppFigures
Stdout: DynamicConnectorService: Dynamic connector - Finished registering connector: AppFigures
Stdout: DynamicConnectorService: Dynamic connector - Start registering connector: GoogleSheets
Stdout: DynamicConnectorService: Dynamic connector - Finished registering connector: GoogleSheets
Stdout: LocalFileUtils: Reading pipeline files at : /home/***/actions-runner2/_work/***/***/synapse/pipeline
Stdout: LocalFileUtils: Reading dataset files at : /home/***/actions-runner2/_work/***/***/synapse/dataset
Stdout: WARNING === LocalFileUtils: Unable to read files for: dataset, error: Error: ENOENT: no such file or directory, scandir '/home/***/actions-runner2/_work/***/***/synapse/dataset'
Stdout: LocalFileUtils: Saving file: /home/***/actions-runner2/_work/***/***/synapse/bigDataPool/sparkpool.json
Stdout: LocalFileUtils: Dir: /home/***/actions-runner2/_work/***/***/synapse/bigDataPool does not exist, creating it....
Stdout: LocalFileUtils: File saved.
Stdout: CmdApiApp: Initializing resource registries...
Stdout: CmdApiApp: Initializing model service...
Stdout: ModelService: Dynamic connector - Finished registering dynamic connectors
Stdout: ModelService: _createAndFetchEntities synchronizeInternal - start
ModelService: _createAndFetchEntities synchronizeInternal - end
Stdout: BaseFileResourceProviderService: populateAllResources - start
Stdout: CmdApiApp: Initializing publish config service...
Stdout: PublishConfigService: _getLatestPublishConfig - retrieving config file.
Stderr: /home/***/actions-runner2/_work/***/***/downloads/main.js:359820
throw ex;
^
ReferenceError: Response is not defined
at Module../node_modules/@trident/data-access-artifact/src/lib/models/http.js (/home/***/actions-runner2/_work/***/***/downloads/main.js:362608:40)
at __webpack_require__ (/home/***/actions-runner2/_work/***/***/downloads/main.js:665765:42)
at Module../node_modules/@trident/data-access-artifact/src/lib/models/index.js (/home/***/actions-runner2/_work/***/***/downloads/main.js:362698:63)
at __webpack_require__ (/home/***/actions-runner2/_work/***/***/downloads/main.js:665765:42)
at Module../node_modules/@trident/data-access-artifact/src/lib/clients/artifact-client.js (/home/***/actions-runner2/_work/***/***/downloads/main.js:361495:65)
at __webpack_require__ (/home/***/actions-runner2/_work/***/***/downloads/main.js:665765:42)
at Module../node_modules/@trident/data-access-artifact/src/lib/clients/index.js (/home/***/actions-runner2/_work/***/***/downloads/main.js:361976:74)
at __webpack_require__ (/home/***/actions-runner2/_work/***/***/downloads/main.js:665765:42)
at Module../node_modules/@trident/data-access-artifact/src/index.js (/home/***/actions-runner2/_work/***/***/downloads/main.js:361472:70)
at __webpack_require__ (/home/***/actions-runner2/_work/***/***/downloads/main.js:665765:42)
Shell execution failed.
Action failed -> Error
```
Contributor guide
Research direction
Start with the failing bundle location and the @trident/data-access-artifact/src/lib/models/http.js module named in the stack trace; determine why Response is unavailable in the GitHub Action runtime. Reproduce the export operation and verify that the action completes without the ReferenceError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, github-actions, node.js, typescript
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100