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

Show logs from pack mock server in console output #69

Open
canny bot opened this issue Jun 26, 2024 · 3 comments
Open

Show logs from pack mock server in console output #69

canny bot opened this issue Jun 26, 2024 · 3 comments

Comments

@canny
Copy link

canny bot commented Jun 26, 2024

Currently, the logs (e.g., a mismatch error and it's diff) of pact mock server are put in pact-mock-service.log.
It's a bit cumbersome if I need to have a look into some other file once the test fails and I only have partial information in the console output.
Even more cumbersome if the failure is on CI and I don't have a way to directly access the file.

https://pact.canny.io/admin/board/feature-requests/p/show-logs-from-pack-mock-server-in-console-output

Copy link
Author

canny bot commented Jun 26, 2024

This issue has been linked to a Canny post: Show logs from pack mock server in console output 🎉

@YOU54F
Copy link
Member

YOU54F commented Jun 27, 2024

Kirill Artamonov - October 25, 2021

See some extra details here: pact-foundation/pact-python#232

@YOU54F
Copy link
Member

YOU54F commented Jun 27, 2024

Matt Fellows - October 25, 2021

Thanks Kirill. Also worth noting the move to the rust core engine (https://github.com/pact-foundation/pact-reference/tree/master/rust) will address this in part, because there is a unified logging infrastructure in place. There are a couple of issues with extracting the provider side which we are working on.
But in the meanwhile, if we can make the Ruby core work then that might be a nice experience.

1 like

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant