Commit 1403b9bf authored by vipwzw's avatar vipwzw

auto ci

parent 3c9a08ca
...@@ -2,6 +2,8 @@ package executor ...@@ -2,6 +2,8 @@ package executor
import ( import (
"fmt" "fmt"
"math"
"github.com/33cn/chain33/account" "github.com/33cn/chain33/account"
"github.com/33cn/chain33/client" "github.com/33cn/chain33/client"
"github.com/33cn/chain33/common" "github.com/33cn/chain33/common"
...@@ -10,7 +12,6 @@ import ( ...@@ -10,7 +12,6 @@ import (
"github.com/33cn/chain33/types" "github.com/33cn/chain33/types"
et "github.com/33cn/plugin/plugin/dapp/exchange/types" et "github.com/33cn/plugin/plugin/dapp/exchange/types"
"github.com/gogo/protobuf/proto" "github.com/gogo/protobuf/proto"
"math"
) )
// Action action struct // Action action struct
......
...@@ -67,6 +67,7 @@ func calcUserOrderIDPrefix(status int32, addr string) []byte { ...@@ -67,6 +67,7 @@ func calcUserOrderIDPrefix(status int32, addr string) []byte {
key := fmt.Sprintf("%s"+"addr:%s:%d:", KeyPrefixLocalDB, addr, status) key := fmt.Sprintf("%s"+"addr:%s:%d:", KeyPrefixLocalDB, addr, status)
return []byte(key) return []byte(key)
} }
//matchOrderIndex,用来解决同一笔交易中存在key重复得情况,这样设计保证了key得唯一性 //matchOrderIndex,用来解决同一笔交易中存在key重复得情况,这样设计保证了key得唯一性
func calcUserOrderIDKey(status int32, addr string, index int64) []byte { func calcUserOrderIDKey(status int32, addr string, index int64) []byte {
key := fmt.Sprintf("%s"+"addr:%s:%d:%022d", KeyPrefixLocalDB, addr, status, index) key := fmt.Sprintf("%s"+"addr:%s:%d:%022d", KeyPrefixLocalDB, addr, status, index)
......
...@@ -28,12 +28,15 @@ It has these top-level messages: ...@@ -28,12 +28,15 @@ It has these top-level messages:
*/ */
package types package types
import proto "github.com/golang/protobuf/proto"
import fmt "fmt"
import math "math"
import ( import (
fmt "fmt"
proto "github.com/golang/protobuf/proto"
math "math"
context "golang.org/x/net/context" context "golang.org/x/net/context"
grpc "google.golang.org/grpc" grpc "google.golang.org/grpc"
) )
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment