Skip to content

Implement app_v2 wiring #13

@fmorency

Description

@fmorency

Using app_v1 is causing the TestAppImportExport simulation to fail in CosmosSDK v0.50.6.

I see similar behavior in this application.

KV stores are different: 27 key/value pairs in store A and 0 key/value pairs in store B
    sim_test.go:202: 
                Error Trace:    /home/fmorency/dev/tokenfactory/app/sim_test.go:202
                Error:          Not equal: 
                                expected: 27
                                actual  : 0
                Test:           TestAppImportExport
                Messages:       unequal sets of key-values to compare upgrade

The issue doesn't occur when using app_v2 wiring in CosmosSDK. Implement app_v2 wiring in this application and see if it fixes the problem.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions