[simulate] Support for multi txn in simulated

[WGB5445]

Description

Support for multi in simulated trading

Test Plan

examples/simulate_multi_transaction

Related Links

[gregnazario]

Looks generally fine, could we get a unit test for it?

[WGB5445]

Looks generally fine, could we get a unit test for it?

Sure, let me add to that.

[WGB5445]

It's a bit strange that importing "github.com/aptos-labs/aptos-go-sdk/crypto" causes an error in the Test_Concurrent_Submission test in client_test.

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x102d89404]

goroutine 489 [running]:
github.com/aptos-labs/aptos-go-sdk.concurrentTxnWaiter(0x14001010310, 0x140002e08c0, 0x1400159c030, 0x140015648c0, 0x14000f08610)
        /Users/logan/code/github/aptos-labs/aptos-go-sdk/client_test.go:726 +0xf4
created by github.com/aptos-labs/aptos-go-sdk.Test_Concurrent_Submission in goroutine 284
        /Users/logan/code/github/aptos-labs/aptos-go-sdk/client_test.go:786 +0x3c8
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x102d89404]

@gregnazario

[gregnazario]

It's a bit strange that importing "github.com/aptos-labs/aptos-go-sdk/crypto" causes an error in the Test_Concurrent_Submission test in client_test.

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x102d89404]

goroutine 489 [running]:
github.com/aptos-labs/aptos-go-sdk.concurrentTxnWaiter(0x14001010310, 0x140002e08c0, 0x1400159c030, 0x140015648c0, 0x14000f08610)
        /Users/logan/code/github/aptos-labs/aptos-go-sdk/client_test.go:726 +0xf4
created by github.com/aptos-labs/aptos-go-sdk.Test_Concurrent_Submission in goroutine 284
        /Users/logan/code/github/aptos-labs/aptos-go-sdk/client_test.go:786 +0x3c8
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x102d89404]

@gregnazario

This is, I think an issue involving not limiting the number of concurrent threads. This can cause it to run out of threads, or if you have other things going on, it can cause other issues. Can be very difficult to debug