Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Pact publication failed due to windows file path limit exceeded #1116

Closed
3 tasks done
SamLeachSky opened this issue Sep 19, 2023 · 2 comments
Closed
3 tasks done
Labels
bug Indicates an unexpected problem or unintended behavior wontfix Indicates that work won't continue on an issue, pull request, or discussion

Comments

@SamLeachSky
Copy link

SamLeachSky commented Sep 19, 2023

I have enabled the long file paths in windows already. This issue does not happen on mac.

If I move the code to a folder with a shorter path, it does not error

Software versions

  • OS: Windows 10 22H2
  • Consumer Pact library: 12.1.0
  • Provider Pact library: 12.1.0
  • Node Version: v18.17.0

Issue Checklist

Please confirm the following:

  • I have upgraded to the latest
  • I have the read the FAQs in the Readme
  • I have triple checked, that there are no unhandled promises in my code and have read the section on intermittent test failures
  • [] I have set my log level to debug and attached a log file showing the complete request/response cycle
  • [] For bonus points and virtual high fives, I have created a reproduceable git repository (see below) to illustrate the problem

Expected behaviour

Published successfully

Actual behaviour

Error: Pact publication failed with non-zero exit code. Full output was:
The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.

❯ ChildProcess. node_modules/.pnpm/@pact-foundation[email protected]/node_modules/@pact-foundation/pact-core/src/publisher.ts:129:27
❯ Object.onceWrapper node:events:629:26
❯ ChildProcess.emit node:events:526:35
❯ ChildProcess.cp.emit node_modules/.pnpm/[email protected]/node_modules/cross-spawn/lib/enoent.js:34:29

Steps to reproduce

Run on Windows with long file path

Relevant log files

@SamLeachSky SamLeachSky added bug Indicates an unexpected problem or unintended behavior triage This issue is yet to be triaged by a maintainer labels Sep 19, 2023
@mefellows
Copy link
Member

It's a known issue with Ruby, and is documented in several open issues (search this project and pact-core repos).

The current bundled Ruby core uses version 3.2.0, and the fix for long path was introduced in 3.0.2, so there's not much else we can do to support this if Ruby doesn't.

Would you mind checking you followed the instructions in this link to see if it works?

Also, the logs above aren't super helpful in determining that this is indeed the issue, is that all there is? I've not seen the "side by side" error before.

Can you please also confirm that the same issue is present with npm?

@mefellows mefellows added the awaiting feedback Awaiting Feedback from OP label Sep 21, 2023
@mefellows
Copy link
Member

Closing as wontfix. There are other options for publication and the windows long path issue is well known.

@github-project-automation github-project-automation bot moved this from New Issue to Closed in Pact Triage (not yet in use) May 16, 2024
@mefellows mefellows added wontfix Indicates that work won't continue on an issue, pull request, or discussion and removed awaiting feedback Awaiting Feedback from OP triage This issue is yet to be triaged by a maintainer labels May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates an unexpected problem or unintended behavior wontfix Indicates that work won't continue on an issue, pull request, or discussion
Projects
Status: Closed
Development

No branches or pull requests

2 participants