jussi issueshttps://gitlab.syncad.com/hive/jussi/-/issues2020-11-26T11:32:10Zhttps://gitlab.syncad.com/hive/jussi/-/issues/3JUSSI - Update documentation to switch from Steem to Hive2020-11-26T11:32:10ZarcangeJUSSI - Update documentation to switch from Steem to HiveI noticed the documentation references Steem, steemd and `api.steemitdev.com`
Now that we have moved away and renamed steemd to hived, we should update it to match new names.
This is also valid for the Hive dev portal (http://developer...I noticed the documentation references Steem, steemd and `api.steemitdev.com`
Now that we have moved away and renamed steemd to hived, we should update it to match new names.
This is also valid for the Hive dev portal (http://developers.hive.io/services/#services-jussi)https://gitlab.syncad.com/hive/jussi/-/issues/5better cache for blocks2023-12-19T22:01:13ZGandalfbetter cache for blocks```
{"e":"TypeError(\"'>' not supported between instances of 'NoneType' and 'int'\",)","lirb":81172157,"request_string":"{\"id\":1,\"jsonrpc\":\"2.0\",\"method\":\"block_api.get_block\",\"params\":{\"block_num\":81172159}}","jsonrpc_resp...```
{"e":"TypeError(\"'>' not supported between instances of 'NoneType' and 'int'\",)","lirb":81172157,"request_string":"{\"id\":1,\"jsonrpc\":\"2.0\",\"method\":\"block_api.get_block\",\"params\":{\"block_num\":81172159}}","jsonrpc_response":{"jsonrpc":"2.0","result":{},"id":1},"event":"Unable to cache using last irreversible block","logger":"jussi.cache.utils","level":"warning"}
```
Jussi might not know what the actual irreversible block is.
FYI @bwrona @danhttps://gitlab.syncad.com/hive/jussi/-/issues/4better logging control and better logging needed2021-05-02T17:13:28ZGandalfbetter logging control and better logging needed```
{"e":"KeyError('accounts_blacklist',)","jid":"000820282724845709","event":"using empty accounts_blacklist","logger":"jussi.validators","level":"warning"}
```
such messages should go away to debug level
etc.```
{"e":"KeyError('accounts_blacklist',)","jid":"000820282724845709","event":"using empty accounts_blacklist","logger":"jussi.validators","level":"warning"}
```
such messages should go away to debug level
etc.https://gitlab.syncad.com/hive/jussi/-/issues/2JUSSI enabled nodes failed to process `network_ broadcast_ api.broadcast_ tra...2020-11-30T19:31:35ZoflyhighJUSSI enabled nodes failed to process `network_ broadcast_ api.broadcast_ transaction`.I accidentally found that JUSSI enabled nodes could not process `network_ broadcast_ api.broadcast_ transaction`.
To reproduce:
#### Step 1
Make an API Call to https://api.hive.blog (JUSSI enabled)
>`curl -s --data '{"jsonrpc":"2.0", ...I accidentally found that JUSSI enabled nodes could not process `network_ broadcast_ api.broadcast_ transaction`.
To reproduce:
#### Step 1
Make an API Call to https://api.hive.blog (JUSSI enabled)
>`curl -s --data '{"jsonrpc":"2.0", "method":"network_broadcast_api.broadcast_transaction", "params":{"trx":{"ref_block_num":1097,"ref_block_prefix":2181793527,"expiration":"2016-03-24T18:00:21","operations":[{"type":"vote_operation","value":{"voter":"hiveio","author":"alice","permlink":"a-post-by-alice","weight":10000}}],"extensions":[],"signatures":[]},"max_block_age":50}, "id":1}' https://api.hive.blog`
Check the response:
>{"jsonrpc":"2.0","id":1,"error":{"code":-32603,"message":"Internal Error","data":{"error_id":"b39f68b2-729c-4a3d-8c0e-3a55d3ae0559","jussi_request_id":"000136681014195215"}}}
#### Step 2
Make API Call to https://api.anyx.io (without JUSSI)
>`curl -s --data '{"jsonrpc":"2.0", "method":"network_broadcast_api.broadcast_transaction", "params":{"trx":{"ref_block_num":1097,"ref_block_prefix":2181793527,"expiration":"2016-03-24T18:00:21","operations":[{"type":"vote_operation","value":{"voter":"hiveio","author":"alice","permlink":"a-post-by-alice","weight":10000}}],"extensions":[],"signatures":[]},"max_block_age":50}, "id":1}' https://anyx.io`
Check the response:
>{"error":{"code":-32000,"data":{"code":3030000,"message":"missing required posting authority" ...
#### Conclusion
We expect the two nodes to return the same information (step 2 is correct), but step 1 returns:"Internal Error".
In my opinion, for an API call, ***whether or not the node is JUSSI enabled, the result should be consistent***. So, I think this may be a BUG of JUSSI.
#### Notes
`condenser_api.broadcast_transaction` works correctly whether the node is JUSSI enabled or not.