munit | Scala testing library with actionable errors | HTTP library

The problem is not with deployment itself, but with the MUnit test case. As you mentioned the Salesforce connector is not mocked and trying to connect. You should mock the subflow or the connector. Use the attributes of to select the right artifact to mock. As shown in the question is trying to mock a flow not shown in the question ("post:\opportunity:application\json:salesforce-system-api-config"). It seems that you really want to mock the Salesforce connector operation.

You could execute the unit test locally, or without trying to deploy to verify it is working first.

You can try using something like this when mocking error for HTTP requests:

Create the following DW file:

httpError.dwl

Python knows a data type called “generators” which is a thing which generates values when asked (similar to an iterator). Very often it is cheaper to have a generator than to have a list produced up front. One example is that zip() function. Instead of returning a list of tuples it returns a generator which in turn would return one tuple after the other:

I think the issue is that haveKey() uses as a parameter a matcher, not a string. Example:

The only problem here is that you are explicitly casting that KafkaContainer.Def to ContainerDef.

The type of container provided by withContianers, Containter is decided by path dependent type in provided ContainerDef,

Basically set some endowed accounts here. https://github.com/paritytech/substrate/blob/master/bin/node/cli/src/chain_spec.rs#L303

Or use root to mint some token in this system. https://github.com/paritytech/substrate/blob/master/frame/balances/src/lib.rs#L314

And there are still a lot of ways to do that. But all of them are done with pallet-balances.

works without any problems for me on macos 12.beta, xcode 13.beta, target ios 15 and macCatalyst. This is the code I used for testing:

As @AlexeyRomanov notes, you likely have an import java.util.List which is shadowing the compiler-injected (thus lower priority) import scala._ (which would pull in scala.List which is a type alias for scala.collection.immutable.List). When importing java.util.List it's generally a good practice to rename the import in some way.

You can only transform a sf object to a new CRS if its current CRS is known. Your df_points has no CRS associated with it, so the transform fails.

If, for example, df_points was in WSG84 (a reasonable guess, but you should make sure with its source) you could then do