Installer can't open pom.xml

Open
#755 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
devtools

Research direction

Start by examining MavenInstaller.installAgent in built/cmds/agentInstaller/mavenInstaller.js and the write path in built/encodedFile.js, using the reported Windows project and pom.xml failure as the reproduction case. Trace why the installer cannot open pom.xml, then verify that installation completes successfully for the affected Maven projects.

Written by the indexing model from the issue text.

Description

bug

In a few projects we got the following install-agent:failure

Error: UNKNOWN: unknown error, open 'C:\Users\test\CRFAutomationGitLab\oneSite\pom.xml'
    at Object.openSync (node:fs:594:3)
    at Object.writeFileSync (node:fs:2207:35)
    at EncodedFile.write (C:\Users\test\AppData\Local\npm-cache\_npx\3007b677135bbf3c\node_modules\@appland\appmap\built\encodedFile.js:35:22)
    at MavenInstaller.installAgent (C:\Users\test\AppData\Local\npm-cache\_npx\3007b677135bbf3c\node_modules\@appland\appmap\built\cmds\agentInstaller\mavenInstaller.js:116:21)
    at AgentInstallerProcedure.run (C:\Users\test\AppData\Local\npm-cache\_npx\3007b677135bbf3c\node_modules\@appland\appmap\built\cmds\agentInstaller\agentInstallerProcedure.js:57:30)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async _handler (C:\Users\test\AppData\Local\npm-cache\_npx\3007b677135bbf3c\node_modules\@appland\appmap\built\cmds\agentInstaller\install-agent.js:133:17)
    at async Object.handler (C:\Users\test\AppData\Local\npm-cache\_npx\3007b677135bbf3c\node_modules\@appland\appmap\built\cmds\agentInstaller\install-agent.js:222:35)
Dominant language
TypeScript
Stars
53
Forks
18
Avg merge
3d 18h
Merged PRs (30d)
8

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getappmap/appmap-js

All issues in getappmap/appmap-js

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.