jmzkchain / jmzk Goto Github PK

[ 90%] Building CXX object libraries/chain/CMakeFiles/evt_chain.dir/address.cpp.o
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See http://bugzilla.redhat.com/bugzilla for instructions.
make[3]: *** [libraries/chain/CMakeFiles/evt_chain.dir/address.cpp.o] Error 4
make[2]: *** [libraries/chain/CMakeFiles/evt_chain.dir/all] Error 2
make[1]: *** [programs/evtwd/CMakeFiles/evtwd.dir/rule] Error 2
make: *** [evtwd] Error 2

There has been one issue introduced since EVT 3.0. Sometimes the incoming symbol may not be the same as expected one. Like 5,S#123, 6,S#123. Currently only the symbol id is checked, but the precision is not checked.

WARNING: Target "chainbase_test" requests linking to directory "/usr/include/openssl". Targets may link only to libraries. CMake is dropping the item.
CMake Error at libraries/utilities/CMakeLists.txt:22 (add_library):
CXX_STANDARD is set to invalid value '17'

CMake Error at libraries/appbase/CMakeLists.txt:45 (add_library):
CXX_STANDARD is set to invalid value '17'

CMake Error at libraries/appbase/examples/CMakeLists.txt:1 (add_executable):
CXX_STANDARD is set to invalid value '17'

CMake Error at libraries/rocksdb/CMakeLists.txt:160 (add_library):

When query PEVT detail by /evt/get_fungible API, server will return: There's no balance left in EVT0000009HVUEuxxnwTzKUUHMwXscMC3UjLoGrB3h55n1Ak53xRd with sym id: 5,S#2.

Current implementation is to hack the backup process of token database, but it will cause some bugs and not independent of RocksDB. Consider re-implement it via scan all keys and backup in binary format.

Currently we only support transfer permission in NFT domain not in FT. We'd like to add transfer permission to FTs for better flexibility. And due to this flexibility, users may not notice there's a chance that the issuer of FT can change the transfer permission at any time. Additional reserved meta field .disable-set-transfer will be added for explicit declaration of cannot setting transfer permission.

I would like to point out that identifiers like “__internal” and “__prepare_register” do not fit to the expected naming convention of the C++ language standard.
Would you like to adjust your selection for unique names?

1. Support partition in postgres (uses pg_pathman).
   • Build pg_pathman into postgres docker image. Currently we use image from bitnami, maybe we need to build our one.
   • Update sql to create partition.
2. Improve query performance
   • Analysis current query sql to find the complex queries and add necessary indexes.
   • Analysis partition performance impact.
3. Support all the actions: Currently postgres_plugin don't support all the actions(e.g. lock, bonus, suspend) processing.

Two extra null pointer checks are not needed in the function “token_database_impl::close”.

It's needed to add multisig addresses on everiToken. An address is not belongs to one person but a group of people manages it together for safety. Since group is the fundamental mechanism of multisig control in everiToken, we'll add one called group generated addresses.
The address is made up of (.group, name, integer) and the owner permission of this address will be refer to the permission of the group itself.

breakpad is used to produce minicore file when encountering crash and debug symbols will be uploaded to S3 when building Docker image. It's needed to have one script to support the whole process when a crash is produced:

1. Use breakpad client to get the hash of crashed evtd program.
2. Download the debug symbols from S3 according to the hash.
3. Use breakpad to produce the detail crash stack.

Crash code:

** 57  	                    auto n2 = *(uint128_t*)key.data();

    0x10060711a <+666>:  movq   -0x230(%rbp), %rax
    0x100607121 <+673>:  movq   %rax, -0x108(%rbp)
    0x100607128 <+680>:  movq   -0x108(%rbp), %rax
    0x10060712f <+687>:  movq   (%rax), %rax
    0x100607132 <+690>:  movq   (%rax), %rcx
    0x100607135 <+693>:  movq   0x8(%rax), %rax
    0x100607139 <+697>:  movq   %rax, -0x248(%rbp)
    0x100607140 <+704>:  movq   %rcx, -0x250(%rbp)

** 58  	                    auto n = *(name128*)key.data();
   59  	                    (void)n2;

    0x100607147 <+711>:  movq   -0x230(%rbp), %rax
    0x10060714e <+718>:  movq   %rax, -0x110(%rbp)
    0x100607155 <+725>:  movq   -0x110(%rbp), %rax
    0x10060715c <+732>:  movq   (%rax), %rax
->  0x10060715f <+735>:  movaps (%rax), %xmm0
    0x100607162 <+738>:  movaps %xmm0, -0x260(%rbp)

ERROR: Volume evtwd-data-volume declared as external, but could not be found. Please create the volume manually using docker volume create --name=evtwd-data-volume and try again.

Currently we build a mixed of runtime and persist rollback feature in token database based on the RocksDB snapshot feature. In order to trace the operations it's need to store the key and value updated.
But for some keys, the size of values is small and the size of key is large. Like assets (address -> property) and bonus receiver(address only). So when facing frequent updating and adding much of these key-values, the overhead of these feature cannot be ignored.
So it need to build one more write cache for the large-key-small-value in memory for fast lookup, rollback and use less memory.

Current in our API tests, the /history/get_transactions is not passed. And after digging into this issue, it's confirmed that the keys signed on trx which inserted into Postgres is not correct.

Currently we've used cache in the layer of RocksDB of token database. The cache in RocksDB is called block cache which stores some pieces of SST table data into memory. But it's needed to have an objects cache which stores the instances at token database level. Because when reading object from token database, it needs to deserialize binary data into object data. And it takes some time especially for the complex type like passive_bonus.

{"code":500,"message":"Internal Service Error","error":{"code":13,"name":"St9exception","what":"bad any_cast","details":[]}}
why I get this error when using issuefungible api.?

Bonus is one of main features will added to the v3.0. And there're two parts: passive bonus and active bonus. Passive bonus will be first implemented.

Token database has been refactored recently and mainly APIs has been changed. Current unittests cannot be compiled and need to be rewritten.

[ 64%] Built target rocksdb
[ 64%] Building CXX object libraries/fc/CMakeFiles/fc.dir/src/uint128.cpp.o
In file included from /root/evt/evt/libraries/fc/include/fc/uint128.hpp:6:0,
from /root/evt/evt/libraries/fc/src/uint128.cpp:1:
/root/evt/evt/libraries/fc/include/fc/exception/exception.hpp:8:20: fatal error: optional: No such file or directory
#include
^
compilation terminated.
make[3]: *** [libraries/fc/CMakeFiles/fc.dir/src/uint128.cpp.o] Error 1
make[2]: *** [libraries/fc/CMakeFiles/fc.dir/all] Error 2
make[1]: *** [programs/evtd/CMakeFiles/evtd.dir/rule] Error 2
make: *** [evtd] Error 2