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
Hi there,
when using DockerKit along with ScalaTest's async test suites there's a conflict between the implicit ExecutionContext defined both in AsyncTestSuite and DockerKit traits:
Error:(27, 55) ambiguous implicitvalues:
both method executionContext in traitAsyncTestSuite of type=> scala.concurrent.ExecutionContext
and lazy value dockerExecutionContext in traitDockerKit of type=> scala.concurrent.ExecutionContextmatch expected typescala.concurrent.ExecutionContext
...
I was wondering if DockerKit could avoid declaring that dockerExecutionContext: ExecutionContext as implicit in order to avoid such conflict.
Thanks
PS: I'm happy to submit a PR if you reckon that might be useful as I do
The text was updated successfully, but these errors were encountered:
classTestSpecextendsAsyncWordSpecwithMatcherswithDockerTestKitwithDockerMySQLService {
"A test" should {
"succeed" in {
Future.successful(true).map(res => res shouldBe true)
}
}
}
DockerMySQLService is a trait that extends DockerKit with DockerKitDockerJava
Hi there,
when using DockerKit along with ScalaTest's async test suites there's a conflict between the implicit ExecutionContext defined both in
AsyncTestSuite
andDockerKit
traits:I was wondering if DockerKit could avoid declaring that
dockerExecutionContext: ExecutionContext
as implicit in order to avoid such conflict.Thanks
PS: I'm happy to submit a PR if you reckon that might be useful as I do
The text was updated successfully, but these errors were encountered: