You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When generating the scaffold for a new module, the modulegen tool executes multiple commands.
In case one of them fails, it is only reported the step that failed, but the actual error is not reported, as seen in the following output:
Error: >> error synchronizing the dependencies: exit status 1
A more detailed output from the tool would facilitate the debugging of errors. For example:
Error: >> error synchronizing the dependencies: exit status 1
go: finding module for package github.com/testcontainers/testcontainers-go/modules/k6
github.com/testcontainers/testcontainers-go/examples/k6 tested by
github.com/testcontainers/testcontainers-go/examples/k6.test imports
github.com/testcontainers/testcontainers-go/modules/k6: module github.com/testcontainers/testcontainers-go@latest found (v0.24.1, replaced by ../..), but does not contain package github.com/testcontainers/testcontainers-go/modules/k6
The text was updated successfully, but these errors were encountered:
We saw that the docs are a bit misleading, as the first code snippet is for creating an example module (just copy&paste code, no public API) when it should be just the module.
Proposal
When generating the scaffold for a new module, the modulegen tool executes multiple commands.
In case one of them fails, it is only reported the step that failed, but the actual error is not reported, as seen in the following output:
A more detailed output from the tool would facilitate the debugging of errors. For example:
The text was updated successfully, but these errors were encountered: