hive issueshttps://gitlab.syncad.com/groups/hive/-/issues2024-03-27T06:32:15Zhttps://gitlab.syncad.com/hive/haf/-/issues/216We need tests for get_metadata2024-03-27T06:32:15ZMichal ZanderWe need tests for get_metadataIt seems that "get_metadata" function works incorrectly before HF21It seems that "get_metadata" function works incorrectly before HF21Mariusz TrelaMariusz Trelahttps://gitlab.syncad.com/hive/clive/-/issues/127Test-TUI-Governance-voting for witnesses2024-01-26T14:03:29ZAleksandra GrabowskaTest-TUI-Governance-voting for witnesses### Test cases related to the functionality Voting for witnesses.
##### Preconditions:
1. There is at least 40 witnesses (witness_01, wintess_02...). The first one should have more voted HP than the second, etc (let me know if it is...### Test cases related to the functionality Voting for witnesses.
##### Preconditions:
1. There is at least 40 witnesses (witness_01, wintess_02...). The first one should have more voted HP than the second, etc (let me know if it is impossible).
2. Each user has:
a. a created profile.
b. enough RC to make a transfer.
3. Clive is activated.
There are following users:
- **User 1** hasn't voted for any witnesses.
- **User 2** has voted for two witnesses (witness_02 and witness_03).
- **User 3** has voted for 30 witnesses (witness_01 - witness_30).
The each operation should be done in the following way:
a. Fast broadcast.
b. Finalize transaction.
c. Add to cart and then broadcast.
#### 1. Test cases: Vote for one witness.
1.1. User 1 votes for one witness and then broadcast it (a/b/c).
1.2. User 2 votes for one witness and then broadcast it (a/b/c).
1.3. User 3 tries to vote for one witness - validation doesn't allow it.
#### 2. Test cases: Remove a vote for one witness.
2.1. User 2 removes a vote for one witness and then broadcast it (a/b/c).
2.2. User 3 removes a vote for one witness and then broadcast it (a/b/c).
#### 3. Test cases: Add and remove votes for witnesses.
3.1. User 1 votes for the first 30 witnesses and then broadcast the transaction (a/b/c).
3.2. User 2 votes for two witnesses (witness_04 and witness_05) and removes vote for witness_02 and then broadcast the transaction (a/b/c).
3.3. User 3 removes votes for all witnesses and votes for then witnesses that he hasn't voted before and then broadcast the transaction (a/b/c).
#### 4. Test cases: Pending operations (cart).
4.1. User votes for the witnesses one by one.
##### Steps:
1. User 1 votes for one witness and adds the operation to the cart.
2. User 1 goes back to the Witness View (Check of the operation is pending).
3. User 1 votes for two witnesses and adds the operations to the cart.
4. User 1 broadcasts the transaction with 3 operations.
4.2. User removes an operation from cart.
##### Steps:
1. User 2 votes for two witnesses and adds the operations to the cart.
2. User 2 goes to the cart and removes one of the operation.
3. User 2 goes back to the Witness View (Check of the only one operation is pending).
4. User 2 broadcasts the transaction with 1 operation.
4.3. User removes votes for the witnesses one by one.
##### Steps:
1. User 3 removes votes for two witnesses and adds the operation to the cart.
2. User 3 goes back to the Witness View (Check of the operation is pending).
3. User 3 removes votes for two witnesses and adds the operations to the cart.
4. User 3 goes to the cart and removes one operation.
5. User 3 broadcasts the transaction with three operations.
#### 5. Test cases: Cart and other way of broadcast.
5.1. Cart and fast broadcast - User 2 has operations in the cart and fast broadcast another operations.
##### Steps:
1. User 2 votes for witnesses: witness_04 and witness_05 and adds the operations to the cart.
2. User 2 goes to the Witness View, removes the vote for wintess_02 and fast broadcasts it.
3. To check:
a. Operations vote for wintess_04 and witness_05 are still pending.
b. Operation vote for wintess_02 was broadcast.
5.2. Cart and finalize transaction - User 1 has operations in the cart and then finalize transaction.
##### Steps:
1. User 1 votes for witnesses: witness_04 and witness_05 and adds the operations to the cart.
2. User 1 goes to the Witness View, adds the vote for wintess_02 and finalize transaction.
3. To check:
a. Operations vote for witness_02, wintess_04 and witness_05 were broadcast.
#### 6. Test cases: Check if the sorting is correct.
1. For user 2. The order should be: witness_02, witness_03 and then witness_01 and witness_04 etc.
#### 7. Test cases: Check the pages of the witnesses list - vote for the last witness.
7.1. User 1 votes for the last witness.
##### Steps:
1. User 1 is on the Witness View.
2. User 1 goes to the next page of the list of witnesses.
3. User 1 votes for the witness_40 (the last on the list).
4. User 1 broadcasts the transaction.
#### 8. Test cases: Searching the witnesses.
8.1. User 2: Search 'witness_01' - Should be one result 'witness_01'.
Check that 'Clear' removes the results.
8.2. User 2: Search 'witness_1' - should be 10 results.
#### 9. Test cases: Check if the witness details are displayed
9.1. Check if all information about witness are displayed:
a. Time of the query,
b. url,
c. Created,
d. Missed blocks,
e. price feed,
f. version.MVP - Minimum Viable ProductMarek Kochanowiczmarek@syncad.comMarek Kochanowiczmarek@syncad.comhttps://gitlab.syncad.com/hive/clive/-/issues/110Test -TUI - Savings2024-01-26T14:00:13ZAleksandra GrabowskaTest -TUI - Savings### Test cases - Savings related operations: transfer_to_savings_operation, transfer_from_savings_operation, cancel_transfer_from_savings_operation.
##### Preconditions:
1. There is a created profile.
2. The user has enough funds to...### Test cases - Savings related operations: transfer_to_savings_operation, transfer_from_savings_operation, cancel_transfer_from_savings_operation.
##### Preconditions:
1. There is a created profile.
2. The user has enough funds to make a transfer.
3. The user has enough RC to make a transfer.
4. The user starts on the Dashboard view.
5. Clive is activate.
For each test the following points should be performed:
1. The user an operation in HBD/HIVE with memo (if possible) to own account/another account and Fast broadcasts it.
2. The user an operation in HBD/HIVE without memo (if possible) to own account/another account and finalizes transaction.
3. The user an operation in HBD/HIVE to own account/another account, adds to the cart and then broadcasts it.
4. The user makes two operations to own account/another account, the first in HBD, the second in HIVE, adds them to cart and then broadcasts.
#### [ ] I. Test cases: Transfer to savings.
#### [ ] II. Test cases: Transfer from savings.
#### [ ] III. Test cases: Cancel transfer from savings.
##### Additional preconditions:
6. There is a pending transfer from saving.
Remark:
It would be nice to check that there is a transfer form savings on the screen before canceling a transfer and that there is no transfer from savings after canceling a transfer.MVP - Minimum Viable ProductMarek Kochanowiczmarek@syncad.comMarek Kochanowiczmarek@syncad.comhttps://gitlab.syncad.com/hive/hive/-/issues/617Cleaning `total_votes` from proposal after HIVE_GOVERNANCE_VOTE_EXPIRATION_PE...2023-11-16T14:17:01ZMichał Kudelakudmich@syncad.comCleaning `total_votes` from proposal after HIVE_GOVERNANCE_VOTE_EXPIRATION_PERIOD didnt work.While creating tests, I encountered a problem with clearing `total_votes` from the proposal (after HIVE_GOVERNANCE_VOTE_EXPIRATION_PERIOD time)
Simplified test scenario:
1) Account_A and Account_B
2) Account_A vote for proposal and witne...While creating tests, I encountered a problem with clearing `total_votes` from the proposal (after HIVE_GOVERNANCE_VOTE_EXPIRATION_PERIOD time)
Simplified test scenario:
1) Account_A and Account_B
2) Account_A vote for proposal and witness
3) Account_B set proxy to Account_A
4) wait HIVE_GOVERNANCE_VOTE_EXPIRATION_PERIOD ( mainnet time 365d/ testnet time 5d )
5) Check the vote_power for:
- the proposal: `total_votes` is not clearing - it is a problem,
- the witness: `votes` are cleaned.
Regression test is located: https://gitlab.syncad.com/hive/hive/-/commits/kudmich/regresion-test-for-problem-with-cleaning-proposal-total-votesMariusz TrelaMariusz Trelahttps://gitlab.syncad.com/hive/hive/-/issues/572beekeeper | SIGINT randomly closes with `-2` return code and do not removes t...2023-10-17T06:28:07ZMateusz Żebrakbeekeeper | SIGINT randomly closes with `-2` return code and do not removes the `beekeeper.pid` fileFYI: @Trela
This behavior could be observed in random failing clive tests.
#### In the logs of the failing test, we can observe:
```plaintext
2023-08-31 14:07:33.741 | ℹ️ INFO | clive.__private.core.beekeeper.handle:__start:175 - ...FYI: @Trela
This behavior could be observed in random failing clive tests.
#### In the logs of the failing test, we can observe:
```plaintext
2023-08-31 14:07:33.741 | ℹ️ INFO | clive.__private.core.beekeeper.handle:__start:175 - Starting Beekeeper...
2023-08-31 14:07:33.742 | 🐞 DEBUG | clive.__private.core.beekeeper.notifications:listen:36 - Notifications server is listening on 39353...
2023-08-31 14:07:33.764 | ℹ️ INFO | clive.__private.core.beekeeper.notifications:notify:40 - Got notification: {'value': {'current_status': 'starting without a session'}, 'time': '2023-08-31T14:07:33', 'name': 'hived_status'}
2023-08-31 14:07:33.766 | ℹ️ INFO | aiohttp.web_log:log:206 - 127.0.0.1 [31/Aug/2023:14:07:33 +0000] "PUT / HTTP/1.1" 204 0 "-" "-"
2023-08-31 14:07:33.767 | ℹ️ INFO | clive.__private.core.beekeeper.notifications:notify:40 - Got notification: {'value': {'current_status': 'signals attached'}, 'time': '2023-08-31T14:07:33', 'name': 'hived_status'}
2023-08-31 14:07:33.767 | 🐞 DEBUG | clive.__private.core.beekeeper.notifications:notify:50 - Beekeeper reports to be ready
2023-08-31 14:07:33.768 | ℹ️ INFO | aiohttp.web_log:log:206 - 127.0.0.1 [31/Aug/2023:14:07:33 +0000] "PUT / HTTP/1.1" 204 0 "-" "-"
2023-08-31 14:07:33.768 | ℹ️ INFO | clive.__private.core.beekeeper.notifications:notify:40 - Got notification: {'value': {'address': '0.0.0.0', 'port': 39881, 'type': 'HTTP'}, 'time': '2023-08-31T14:07:33', 'name': 'webserver listening'}
2023-08-31 14:07:33.769 | 🐞 DEBUG | clive.__private.core.beekeeper.notifications:notify:47 - Got notification with http address on: http://127.0.0.1:39881
2023-08-31 14:07:33.769 | ℹ️ INFO | aiohttp.web_log:log:206 - 127.0.0.1 [31/Aug/2023:14:07:33 +0000] "PUT / HTTP/1.1" 204 0 "-" "-"
2023-08-31 14:07:38.756 | 🐞 DEBUG | clive.__private.core.beekeeper.handle:__run_beekeeper:207 - Got webserver http endpoint: `http://127.0.0.1:39881`
2023-08-31 14:07:38.757 | ℹ️ INFO | clive.__private.core.beekeeper.handle:__start:186 - Beekeeper started on http://127.0.0.1:39881.
2023-08-31 14:07:38.763 | ℹ️ INFO | clive.__private.core.beekeeper.handle:_send:147 - Returning model: id_=0 jsonrpc='2.0' result=CreateSession(token='d540aaa8ee678152ad698338c37b111ab5f033387ea7c40b4c67e117207b386a')
2023-08-31 14:07:38.765 | ℹ️ INFO | clive.__private.core.commands.abc.command:_log_execution_info:40 - Executing command: CreateWallet
2023-08-31 14:07:38.769 | ℹ️ INFO | clive.__private.core.beekeeper.handle:_send:147 - Returning model: id_=0 jsonrpc='2.0' result=Create(password='password')
2023-08-31 14:07:38.769 | ℹ️ INFO | clive.__private.core.app_state:activate:33 - Mode switched to ACTIVE.
2023-08-31 14:07:38.771 | ℹ️ INFO | clive.__private.core.beekeeper.handle:close:160 - Closing Beekeeper...
2023-08-31 14:07:38.772 | ℹ️ INFO | clive.__private.core.beekeeper.handle:_send:147 - Returning model: id_=0 jsonrpc='2.0' result=EmptyResponse()
2023-08-31 14:07:38.774 | 🐞 DEBUG | clive.__private.core.beekeeper.executable:close:105 - Beekeeper closed with return code of `-2`.
2023-08-31 14:07:38.775 | 🐞 DEBUG | clive.__private.core.beekeeper.executable:__wait_for_pid_file_to_be_deleted:140 - Beekeeper PID file was deleted in 0.00 seconds.
2023-08-31 14:07:38.775 | 🐞 DEBUG | clive.__private.core.beekeeper.notifications:close:76 - Notifications server closed
2023-08-31 14:07:38.775 | ℹ️ INFO | clive.__private.core.beekeeper.handle:close:166 - Beekeeper closed.
2023-08-31 14:07:38.776 | ℹ️ INFO | clive.__private.core.beekeeper.handle:__start:175 - Starting Beekeeper...
2023-08-31 14:07:38.776 | 🐞 DEBUG | clive.__private.core.beekeeper.notifications:listen:36 - Notifications server is listening on 34353...
2023-08-31 14:07:38.793 | ℹ️ INFO | clive.__private.core.beekeeper.notifications:notify:40 - Got notification: {'value': {'current_status': 'starting without a session'}, 'time': '2023-08-31T14:07:38', 'name': 'hived_status'}
2023-08-31 14:07:38.794 | ℹ️ INFO | aiohttp.web_log:log:206 - 127.0.0.1 [31/Aug/2023:14:07:38 +0000] "PUT / HTTP/1.1" 204 0 "-" "-"
2023-08-31 14:07:38.795 | ℹ️ INFO | clive.__private.core.beekeeper.notifications:notify:40 - Got notification: {'value': {'current_status': 'signals attached'}, 'time': '2023-08-31T14:07:38', 'name': 'hived_status'}
2023-08-31 14:07:38.796 | 🐞 DEBUG | clive.__private.core.beekeeper.notifications:notify:50 - Beekeeper reports to be ready
2023-08-31 14:07:38.796 | ℹ️ INFO | aiohttp.web_log:log:206 - 127.0.0.1 [31/Aug/2023:14:07:38 +0000] "PUT / HTTP/1.1" 204 0 "-" "-"
2023-08-31 14:07:38.797 | ℹ️ INFO | clive.__private.core.beekeeper.notifications:notify:40 - Got notification: {'value': {'address': '0.0.0.0', 'port': 44521, 'type': 'HTTP'}, 'time': '2023-08-31T14:07:38', 'name': 'webserver listening'}
2023-08-31 14:07:38.798 | 🐞 DEBUG | clive.__private.core.beekeeper.notifications:notify:47 - Got notification with http address on: http://127.0.0.1:44521
2023-08-31 14:07:38.798 | ℹ️ INFO | aiohttp.web_log:log:206 - 127.0.0.1 [31/Aug/2023:14:07:38 +0000] "PUT / HTTP/1.1" 204 0 "-" "-"
2023-08-31 14:07:43.790 | 🐞 DEBUG | clive.__private.core.beekeeper.handle:__run_beekeeper:207 - Got webserver http endpoint: `http://127.0.0.1:44521`
2023-08-31 14:07:43.791 | ℹ️ INFO | clive.__private.core.beekeeper.handle:__start:186 - Beekeeper started on http://127.0.0.1:44521.
2023-08-31 14:07:43.797 | ℹ️ INFO | clive.__private.core.beekeeper.handle:_send:147 - Returning model: id_=0 jsonrpc='2.0' result=CreateSession(token='4af7c8b37f24b1c99ba962773f5ba9e8843cfa7cba4ba2c896942c0528a4a4b3')
2023-08-31 14:07:43.801 | ℹ️ INFO | clive.__private.core.beekeeper.handle:_send:147 - Returning model: id_=0 jsonrpc='2.0' result=ListWallets(wallets=[])
2023-08-31 14:07:43.803 | ℹ️ INFO | clive.__private.core.beekeeper.handle:_send:147 - Returning model: id_=0 jsonrpc='2.0' result=EmptyResponse()
2023-08-31 14:07:43.806 | ℹ️ INFO | clive.__private.core.beekeeper.handle:_send:147 - Returning model: id_=0 jsonrpc='2.0' result=ListWallets(wallets=[WalletDetails(name='wallet', unlocked=False)])
2023-08-31 14:07:43.809 | ℹ️ INFO | clive.__private.core.beekeeper.handle:close:160 - Closing Beekeeper...
2023-08-31 14:07:43.811 | ℹ️ INFO | clive.__private.core.beekeeper.handle:_send:147 - Returning model: id_=0 jsonrpc='2.0' result=EmptyResponse()
2023-08-31 14:07:43.813 | 🐞 DEBUG | clive.__private.core.beekeeper.executable:close:105 - Beekeeper closed with return code of `-2`.
2023-08-31 14:07:53.833 | 🐞 DEBUG | clive.__private.core.beekeeper.notifications:close:76 - Notifications server closed
2023-08-31 14:07:53.862 | 🐞 DEBUG | asyncio.selector_events:__init__:54 - Using selector: EpollSelector
2023-08-31 14:07:53.913 | 🐞 DEBUG | asyncio.selector_events:__init__:54 - Using selector: EpollSelector
```
and beekeeper logs
```plaintext
458785ms json_rpc_plugin.cpp:222 initialize ] initializing JSON RPC plugin
458786ms webserver_plugin.cpp:584 plugin_initialize ] initializing webserver plugin
458786ms webserver_plugin.cpp:587 plugin_initialize ] configured with 1 thread pool size
458786ms webserver_plugin.cpp:590 plugin_initialize ] Compression in webserver is disabled
458786ms webserver_plugin.cpp:602 plugin_initialize ] configured http to listen on 0.0.0.0:0
458786ms beekeeper_app_init.cpp:123 initialize_program_o ] initializing options
458787ms notifications.cpp:64 setup ] setting up notification handler for 1 address
458791ms beekeeper_app_init.cpp:166 initialize_program_o ] Backtrace on segfault is enabled.
458792ms webserver_plugin.cpp:290 operator() ] start processing http thread
458792ms webserver_plugin.cpp:305 operator() ] start listening for http requests on 0.0.0.0:44521
463795ms json_rpc_plugin.cpp:439 rpc ] message: {"id":0,"jsonrpc":"2.0","method":"beekeeper_api.create_session","params":{"notifications_endpoint":"127.0.0.1:34353","salt":"139898871443712"}}
463800ms json_rpc_plugin.cpp:439 rpc ] message: {"id":0,"jsonrpc":"2.0","method":"beekeeper_api.list_wallets","params":{"token":"4af7c8b37f24b1c99ba962773f5ba9e8843cfa7cba4ba2c896942c0528a4a4b3"}}
463803ms json_rpc_plugin.cpp:439 rpc ] message: {"id":0,"jsonrpc":"2.0","method":"beekeeper_api.open","params":{"wallet_name":"wallet","token":"4af7c8b37f24b1c99ba962773f5ba9e8843cfa7cba4ba2c896942c0528a4a4b3"}}
463805ms json_rpc_plugin.cpp:439 rpc ] message: {"id":0,"jsonrpc":"2.0","method":"beekeeper_api.list_wallets","params":{"token":"4af7c8b37f24b1c99ba962773f5ba9e8843cfa7cba4ba2c896942c0528a4a4b3"}}
463810ms json_rpc_plugin.cpp:439 rpc ] message: {"id":0,"jsonrpc":"2.0","method":"beekeeper_api.close_session","params":{"token":"4af7c8b37f24b1c99ba962773f5ba9e8843cfa7cba4ba2c896942c0528a4a4b3"}}
463811ms application.cpp:99 handle_signal ] _last_signal_code: 2
463811ms application.cpp:90 generate_interrupt_r ] interrupt requested!
463811ms webserver_plugin.cpp:651 plugin_pre_shutdown ] Shutting down webserver_plugin...
463811ms webserver_plugin.cpp:310 operator() ] http io service exit
463812ms application.cpp:475 finish ] Waiting for logging_thread quit
463812ms application.cpp:477 finish ] logging_thread quit done
```
Here are artifacts from this failing test (job 670337): [failing.tar.gz](/uploads/acd6e05b32d4d2f3263afde254881a24/failing.tar.gz)
#### And while it's green:
```plaintext
2023-08-31 14:05:30.712 | ❌ ERROR | asyncio.base_events:default_exception_handler:1744 - Task was destroyed but it is pending!
task: <Task pending name='Task-84' coro=<RequestHandler.start() done, defined at /builds/hive/clive/venv/lib/python3.10/site-packages/aiohttp/web_protocol.py:462> wait_for=<Future finished result=None>>
2023-08-31 14:05:30.862 | ℹ️ INFO | clive.__private.core.beekeeper.handle:__start:175 - Starting Beekeeper...
2023-08-31 14:05:30.864 | 🐞 DEBUG | clive.__private.core.beekeeper.notifications:listen:36 - Notifications server is listening on 41905...
2023-08-31 14:05:30.884 | ℹ️ INFO | clive.__private.core.beekeeper.notifications:notify:40 - Got notification: {'value': {'current_status': 'starting without a session'}, 'time': '2023-08-31T14:05:30', 'name': 'hived_status'}
2023-08-31 14:05:30.886 | ℹ️ INFO | aiohttp.web_log:log:206 - 127.0.0.1 [31/Aug/2023:14:05:30 +0000] "PUT / HTTP/1.1" 204 0 "-" "-"
2023-08-31 14:05:30.887 | ℹ️ INFO | clive.__private.core.beekeeper.notifications:notify:40 - Got notification: {'value': {'current_status': 'signals attached'}, 'time': '2023-08-31T14:05:30', 'name': 'hived_status'}
2023-08-31 14:05:30.887 | 🐞 DEBUG | clive.__private.core.beekeeper.notifications:notify:50 - Beekeeper reports to be ready
2023-08-31 14:05:30.888 | ℹ️ INFO | aiohttp.web_log:log:206 - 127.0.0.1 [31/Aug/2023:14:05:30 +0000] "PUT / HTTP/1.1" 204 0 "-" "-"
2023-08-31 14:05:30.888 | ℹ️ INFO | clive.__private.core.beekeeper.notifications:notify:40 - Got notification: {'value': {'address': '0.0.0.0', 'port': 34139, 'type': 'HTTP'}, 'time': '2023-08-31T14:05:30', 'name': 'webserver listening'}
2023-08-31 14:05:30.889 | 🐞 DEBUG | clive.__private.core.beekeeper.notifications:notify:47 - Got notification with http address on: http://127.0.0.1:34139
2023-08-31 14:05:30.889 | ℹ️ INFO | aiohttp.web_log:log:206 - 127.0.0.1 [31/Aug/2023:14:05:30 +0000] "PUT / HTTP/1.1" 204 0 "-" "-"
2023-08-31 14:05:35.878 | 🐞 DEBUG | clive.__private.core.beekeeper.handle:__run_beekeeper:207 - Got webserver http endpoint: `http://127.0.0.1:34139`
2023-08-31 14:05:35.879 | ℹ️ INFO | clive.__private.core.beekeeper.handle:__start:186 - Beekeeper started on http://127.0.0.1:34139.
2023-08-31 14:05:35.885 | ℹ️ INFO | clive.__private.core.beekeeper.handle:_send:147 - Returning model: id_=0 jsonrpc='2.0' result=CreateSession(token='b90094a2d0aa2621f1bbe68535a0c7388b62d163641a6e6a3920b06cfe9bc372')
2023-08-31 14:05:35.888 | ℹ️ INFO | clive.__private.core.commands.abc.command:_log_execution_info:40 - Executing command: CreateWallet
2023-08-31 14:05:35.890 | ℹ️ INFO | clive.__private.core.beekeeper.handle:_send:147 - Returning model: id_=0 jsonrpc='2.0' result=Create(password='password')
2023-08-31 14:05:35.891 | ℹ️ INFO | clive.__private.core.app_state:activate:33 - Mode switched to ACTIVE.
2023-08-31 14:05:35.892 | ℹ️ INFO | clive.__private.core.beekeeper.handle:close:160 - Closing Beekeeper...
2023-08-31 14:05:35.894 | ℹ️ INFO | clive.__private.core.beekeeper.handle:_send:147 - Returning model: id_=0 jsonrpc='2.0' result=EmptyResponse()
2023-08-31 14:05:36.108 | 🐞 DEBUG | clive.__private.core.beekeeper.executable:close:105 - Beekeeper closed with return code of `0`.
2023-08-31 14:05:36.110 | 🐞 DEBUG | clive.__private.core.beekeeper.executable:__wait_for_pid_file_to_be_deleted:140 - Beekeeper PID file was deleted in 0.00 seconds.
2023-08-31 14:05:36.111 | 🐞 DEBUG | clive.__private.core.beekeeper.notifications:close:76 - Notifications server closed
2023-08-31 14:05:36.112 | ℹ️ INFO | clive.__private.core.beekeeper.handle:close:166 - Beekeeper closed.
2023-08-31 14:05:36.112 | ℹ️ INFO | clive.__private.core.beekeeper.handle:__start:175 - Starting Beekeeper...
2023-08-31 14:05:36.114 | 🐞 DEBUG | clive.__private.core.beekeeper.notifications:listen:36 - Notifications server is listening on 42591...
2023-08-31 14:05:36.137 | ℹ️ INFO | clive.__private.core.beekeeper.notifications:notify:40 - Got notification: {'value': {'current_status': 'starting without a session'}, 'time': '2023-08-31T14:05:36', 'name': 'hived_status'}
2023-08-31 14:05:36.138 | ℹ️ INFO | aiohttp.web_log:log:206 - 127.0.0.1 [31/Aug/2023:14:05:36 +0000] "PUT / HTTP/1.1" 204 0 "-" "-"
2023-08-31 14:05:36.140 | ℹ️ INFO | clive.__private.core.beekeeper.notifications:notify:40 - Got notification: {'value': {'current_status': 'signals attached'}, 'time': '2023-08-31T14:05:36', 'name': 'hived_status'}
2023-08-31 14:05:36.140 | 🐞 DEBUG | clive.__private.core.beekeeper.notifications:notify:50 - Beekeeper reports to be ready
2023-08-31 14:05:36.141 | ℹ️ INFO | aiohttp.web_log:log:206 - 127.0.0.1 [31/Aug/2023:14:05:36 +0000] "PUT / HTTP/1.1" 204 0 "-" "-"
2023-08-31 14:05:36.142 | ℹ️ INFO | clive.__private.core.beekeeper.notifications:notify:40 - Got notification: {'value': {'address': '0.0.0.0', 'port': 33197, 'type': 'HTTP'}, 'time': '2023-08-31T14:05:36', 'name': 'webserver listening'}
2023-08-31 14:05:36.143 | 🐞 DEBUG | clive.__private.core.beekeeper.notifications:notify:47 - Got notification with http address on: http://127.0.0.1:33197
2023-08-31 14:05:36.143 | ℹ️ INFO | aiohttp.web_log:log:206 - 127.0.0.1 [31/Aug/2023:14:05:36 +0000] "PUT / HTTP/1.1" 204 0 "-" "-"
2023-08-31 14:05:41.129 | 🐞 DEBUG | clive.__private.core.beekeeper.handle:__run_beekeeper:207 - Got webserver http endpoint: `http://127.0.0.1:33197`
2023-08-31 14:05:41.130 | ℹ️ INFO | clive.__private.core.beekeeper.handle:__start:186 - Beekeeper started on http://127.0.0.1:33197.
2023-08-31 14:05:41.136 | ℹ️ INFO | clive.__private.core.beekeeper.handle:_send:147 - Returning model: id_=0 jsonrpc='2.0' result=CreateSession(token='712241ececec2f17484a73ab7d03c4e1eaad25f4242e1c9f8b5ef40ac1d33e4c')
2023-08-31 14:05:41.140 | ℹ️ INFO | clive.__private.core.beekeeper.handle:_send:147 - Returning model: id_=0 jsonrpc='2.0' result=ListWallets(wallets=[])
2023-08-31 14:05:41.143 | ℹ️ INFO | clive.__private.core.beekeeper.handle:_send:147 - Returning model: id_=0 jsonrpc='2.0' result=EmptyResponse()
2023-08-31 14:05:41.145 | ℹ️ INFO | clive.__private.core.beekeeper.handle:_send:147 - Returning model: id_=0 jsonrpc='2.0' result=ListWallets(wallets=[WalletDetails(name='wallet', unlocked=False)])
2023-08-31 14:05:41.148 | ℹ️ INFO | clive.__private.core.beekeeper.handle:close:160 - Closing Beekeeper...
2023-08-31 14:05:41.150 | ℹ️ INFO | clive.__private.core.beekeeper.handle:_send:147 - Returning model: id_=0 jsonrpc='2.0' result=EmptyResponse()
2023-08-31 14:05:41.152 | 🐞 DEBUG | clive.__private.core.beekeeper.executable:close:105 - Beekeeper closed with return code of `-2`.
2023-08-31 14:05:41.153 | 🐞 DEBUG | clive.__private.core.beekeeper.executable:__wait_for_pid_file_to_be_deleted:140 - Beekeeper PID file was deleted in 0.00 seconds.
2023-08-31 14:05:41.153 | 🐞 DEBUG | clive.__private.core.beekeeper.notifications:close:76 - Notifications server closed
2023-08-31 14:05:41.153 | ℹ️ INFO | clive.__private.core.beekeeper.handle:close:166 - Beekeeper closed.
2023-08-31 14:05:41.175 | 🐞 DEBUG | asyncio.selector_events:__init__:54 - Using selector: EpollSelector
2023-08-31 14:05:41.177 | 🐞 DEBUG | asyncio.selector_events:__init__:54 - Using selector: EpollSelector
```
and beekeeper:
```plaintext
336125ms json_rpc_plugin.cpp:222 initialize ] initializing JSON RPC plugin
336125ms webserver_plugin.cpp:584 plugin_initialize ] initializing webserver plugin
336125ms webserver_plugin.cpp:587 plugin_initialize ] configured with 1 thread pool size
336125ms webserver_plugin.cpp:590 plugin_initialize ] Compression in webserver is disabled
336126ms webserver_plugin.cpp:602 plugin_initialize ] configured http to listen on 0.0.0.0:0
336126ms beekeeper_app_init.cpp:123 initialize_program_o ] initializing options
336127ms notifications.cpp:64 setup ] setting up notification handler for 1 address
336134ms beekeeper_app_init.cpp:166 initialize_program_o ] Backtrace on segfault is enabled.
336135ms webserver_plugin.cpp:290 operator() ] start processing http thread
336135ms webserver_plugin.cpp:305 operator() ] start listening for http requests on 0.0.0.0:33197
341134ms json_rpc_plugin.cpp:439 rpc ] message: {"id":0,"jsonrpc":"2.0","method":"beekeeper_api.create_session","params":{"notifications_endpoint":"127.0.0.1:42591","salt":"140566037592720"}}
341139ms json_rpc_plugin.cpp:439 rpc ] message: {"id":0,"jsonrpc":"2.0","method":"beekeeper_api.list_wallets","params":{"token":"712241ececec2f17484a73ab7d03c4e1eaad25f4242e1c9f8b5ef40ac1d33e4c"}}
341142ms json_rpc_plugin.cpp:439 rpc ] message: {"id":0,"jsonrpc":"2.0","method":"beekeeper_api.open","params":{"wallet_name":"wallet","token":"712241ececec2f17484a73ab7d03c4e1eaad25f4242e1c9f8b5ef40ac1d33e4c"}}
341144ms json_rpc_plugin.cpp:439 rpc ] message: {"id":0,"jsonrpc":"2.0","method":"beekeeper_api.list_wallets","params":{"token":"712241ececec2f17484a73ab7d03c4e1eaad25f4242e1c9f8b5ef40ac1d33e4c"}}
341150ms json_rpc_plugin.cpp:439 rpc ] message: {"id":0,"jsonrpc":"2.0","method":"beekeeper_api.close_session","params":{"token":"712241ececec2f17484a73ab7d03c4e1eaad25f4242e1c9f8b5ef40ac1d33e4c"}}
341150ms application.cpp:99 handle_signal ] _last_signal_code: 2
341150ms application.cpp:90 generate_interrupt_r ] interrupt requested!
341150ms webserver_plugin.cpp:651 plugin_pre_shutdown ] Shutting down webserver_plugin...
341150ms webserver_plugin.cpp:310 operator() ] http io service exit
341151ms application.cpp:475 finish ] Waiting for logging_thread quit
341151ms application.cpp:477 finish ] logging_thread quit done
```
Here are artifacts from this test (job 670336): [success.tar.gz](/uploads/2e673695eaddb7ed408afecb6dc47011/success.tar.gz)
Here is a job when such a situation occurs: https://gitlab.syncad.com/hive/clive/-/jobs/670337
In the CI logs, we can observe that a test failed because of \
`Beekeeper PID file /builds/hive/clive/tests/unit/beekeeper/generated_during_test_wallet/test_wallet_open/beekeeper/beekeeper.pid was not deleted in 10.0 seconds.`
and this is happening when beekeeper closes with `-2` (but not always), sometimes this file is deleted though:
```plaintext
2023-08-31 14:05:36.108 | :beetle: DEBUG | clive.\__private.core.beekeeper.executable:close:105 - Beekeeper closed with return code of `0`.
2023-08-31 14:05:36.110 | :beetle: DEBUG | clive.\__private.core.beekeeper.executable:\__wait_for_pid_file_to_be_deleted:140 - Beekeeper PID file was deleted in 0.00 seconds.
2023-08-31 14:05:36.111 | :beetle: DEBUG | clive.\__private.core.beekeeper.notifications:close:76 - Notifications server closed
```
vs
```plaintext
2023-08-31 14:05:41.152 | :beetle: DEBUG | clive.\__private.core.beekeeper.executable:close:105 - Beekeeper closed with return code of `-2`.
2023-08-31 14:05:41.153 | :beetle: DEBUG | clive.\__private.core.beekeeper.executable:\__wait_for_pid_file_to_be_deleted:140 - Beekeeper PID file was deleted in 0.00 seconds.
2023-08-31 14:05:41.153 | :beetle: DEBUG | clive.\__private.core.beekeeper.notifications:close:76 - Notifications server closed
```
vs
```plaintext
2023-08-31 14:07:43.813 | :beetle: DEBUG | clive.\__private.core.beekeeper.executable:close:105 - Beekeeper closed with return code of `-2`.
2023-08-31 14:07:53.833 | :beetle: DEBUG | clive.\__private.core.beekeeper.notifications:close:76 - Notifications server closed
```
and some successful jobs from the same pipeline: https://gitlab.syncad.com/hive/clive/-/jobs/670336 https://gitlab.syncad.com/hive/clive/-/jobs/670335 https://gitlab.syncad.com/hive/clive/-/jobs/670330
This is randomly happening on other tests also, not only the one mentioned above: https://gitlab.syncad.com/hive/clive/-/jobs/670306https://gitlab.syncad.com/hive/hive/-/issues/556v1.27.5 RC review (includes performance testing, etc)2024-03-28T03:00:58ZGandalfv1.27.5 RC review (includes performance testing, etc)Notes:
- [x] `plugin = rc` in `config.ini` (that might be there explicitly specified from previous versions) will no longer work with v1.27.5-rc0Notes:
- [x] `plugin = rc` in `config.ini` (that might be there explicitly specified from previous versions) will no longer work with v1.27.5-rc0GandalfGandalfhttps://gitlab.syncad.com/hive/hive/-/issues/553The Docs: Update and K.I.S.S. Edition v1.282023-08-10T21:57:39ZGandalfThe Docs: Update and K.I.S.S. Edition v1.28[README.md](README.md), and [doc](doc/) contains instructions on how to build and use Hive, but they are:
- inaccurate
- obsolete
- over-complicated
More complex use case scenarios can and should be described on chain. Docs in this repo...[README.md](README.md), and [doc](doc/) contains instructions on how to build and use Hive, but they are:
- inaccurate
- obsolete
- over-complicated
More complex use case scenarios can and should be described on chain. Docs in this repo should be accurate, up to date and dead simple.<br>
Nobody wants to read walls of text, instead those who start their journey with Hive want to read the `README.md` file, figure out what it is.<br>
Then be able to provision hardware resources, configure software prerequisites and run the node for desired use case.<br>
See: [K.I.S.S. principle](https://en.wikipedia.org/wiki/KISS_principle)
Supersedes #60HF-28GandalfGandalfhttps://gitlab.syncad.com/hive/haf/-/issues/107Unexpected exception during reconnectiong api_node with enable sql serializer.2023-02-14T08:31:11ZRadosław MasłowskiUnexpected exception during reconnectiong api_node with enable sql serializer.Scenario:
1. Run init_node and allow to produce blocks.
2. Run api_node connected to initnode and allow to synchronize.
3. Close api_node
4. Enable in api_node SQL serializer end set url to database in config.ini.
5. Rerun api_node.
6. U...Scenario:
1. Run init_node and allow to produce blocks.
2. Run api_node connected to initnode and allow to synchronize.
3. Close api_node
4. Enable in api_node SQL serializer end set url to database in config.ini.
5. Rerun api_node.
6. Unexpected exception
`2023-01-19T14:40:23.543077 data_processor.cpp:194 join ] Caught unhandled exception Dynamic exception type: pqxx::foreign_key_violation
std::exception::what: ERROR: insert or update on table "irreversible_data" violates foreign key constraint "fk_1_hive_irreversible_data"
DETAIL: Key (consistent_block)=(1264) is not present in table "blocks".
CONTEXT: SQL statement "UPDATE hive.irreversible_data SET consistent_block = _block_num"
PL/pgSQL function hive.set_irreversible(integer) line 30 at SQL statement
`Mariusz TrelaMariusz Trelahttps://gitlab.syncad.com/hive/hive/-/issues/429Do research related to extending protobuf library by hive-specific binary ser...2023-01-12T17:20:01ZBartek WronaDo research related to extending protobuf library by hive-specific binary serializationBy extending protobuf library we could make possible cross-language calls creating transactions, resulting in same (and correct) binary serialization.
There were done some very early stage prototype works:
https://gitlab.com/mtyszczak/p...By extending protobuf library we could make possible cross-language calls creating transactions, resulting in same (and correct) binary serialization.
There were done some very early stage prototype works:
https://gitlab.com/mtyszczak/protobuf_fc_fork/-/commit/a757ff935bc79afa91cfa8602024e81f82b14ac4 <br/>
https://gitlab.com/mtyszczak/hive-protocol-buffers/-/blob/main/tests/src/operations/vote_operation_test.cppMarek Kochanowiczmarek@syncad.comMarek Kochanowiczmarek@syncad.comhttps://gitlab.syncad.com/hive/hive/-/issues/313Supplement cli_wallet by support for all existing blockchain operations2022-11-14T13:23:20ZBartek WronaSupplement cli_wallet by support for all existing blockchain operationsAs reference tool, it should be able to execute any blockchain operation.
As an example is missing support for `comment_options_operation`. Complete list should be collected first.As reference tool, it should be able to execute any blockchain operation.
As an example is missing support for `comment_options_operation`. Complete list should be collected first.Aleksandra GrabowskaAleksandra Grabowskahttps://gitlab.syncad.com/hive/hive/-/issues/205Advanced benchmark for RC evaluation2022-07-28T18:08:18ZGandalfAdvanced benchmark for RC evaluationWe need to gather through analysis of resource usage to be able to evaluate current Resource Credit system and for the sake of its future improvements.
I'm using `2c31840a22ff52d430f648a42ba9aa2dd89b6b5a` as to run it per @ABW request
...We need to gather through analysis of resource usage to be able to evaluate current Resource Credit system and for the sake of its future improvements.
I'm using `2c31840a22ff52d430f648a42ba9aa2dd89b6b5a` as to run it per @ABW request
`config.ini` file used:
```
log-appender = {"appender":"stderr","stream":"std_error"} {"appender":"p2p","file":"logs/p2p/p2p.log"}
log-logger = {"name":"default","level":"info","appender":"stderr"} {"name":"p2p","level":"warn","appender":"p2p"}
plugin = block_api
shared-file-dir = "/run/hive"
shared-file-size = 24G
flush-state-interval = 0
```
command line:
`/home/hive/bin/hived-2c31840a22ff52d430f648a42ba9aa2dd89b6b5a --force-replay --validate-during-replay --advanced-benchmark --dump-memory-details --set-benchmark-interval 100000`
Hardware used:<br>
`Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz`<br>
32GB RAM, DDR3, ECC 4x 8GB Kingston<br>
2x480GB Intel SSD DC S3510 (software raid0)<br>
OS: Ubuntu 18.04 LTS<br>GandalfGandalfhttps://gitlab.syncad.com/hive/hive/-/issues/168[cli_wallet] Add support for http/https connections2022-08-18T16:15:54ZGandalf[cli_wallet] Add support for http/https connectionsCurrently `cli_wallet` supports only websocket connections which is fine for local wallet<->node, but it requires cli_wallet user to have their own working node which is not trivial when it comes to requirements and setup time.
Of course...Currently `cli_wallet` supports only websocket connections which is fine for local wallet<->node, but it requires cli_wallet user to have their own working node which is not trivial when it comes to requirements and setup time.
Of course, there are public nodes such as `api.hive.blog` or `api.openhive.network`, etc. but those rarely support direct websocket connection to `hived`. Workaround is to use websocket->http(s) bridge locally or on server-side (such as `lineman`)
<br><br><br>It should work like this:
`cli-wallet -shttps://api.hive.blog`<br>
(Currently it only accepts `-sws://` and `-swss://`)Mateusz TyszczakMateusz Tyszczakhttps://gitlab.syncad.com/hive/hive/-/issues/167[cli_wallet] Support, Maintenance and Development Meta-issue2022-11-24T11:30:39ZGandalf[cli_wallet] Support, Maintenance and Development Meta-issueThis is a meta-issue for cli_wallet that's meant to coordinate work on this useful tool.
<sup>I'm having some deja-vu here, because I already posted similar issue, before The Metadata Oblivion Incident.</sup>
> This piece of software n...This is a meta-issue for cli_wallet that's meant to coordinate work on this useful tool.
<sup>I'm having some deja-vu here, because I already posted similar issue, before The Metadata Oblivion Incident.</sup>
> This piece of software needs more love. For many users, it’s the only software that will ever have access to their privileged keys (Active, Owner). It’s what exchanges, whales, and smart people rely on to sign their transactions.
- [x] #92 Eliminate legacy operations and old condenser_api-like interface from cli_wallet <-> hived communication
- [x] #150 Signing with account authority
- [ ] retain command history (I think issue is gone and has to be revived)
- [ ] #168 Add support for http/https connections
- [x] #169 Add support for offline use
- [ ] #170 non-blocking transactions
- [x] #175 Merge imported wallet file on load instead of replacing it
- [x] #177 `server-rpc-endpoint` option behaves as optional with no `default_value` specified
- [x] #178 Add exit function to the wallet API
- [x] #180 python based regression tests covering offline mode of cli_wallet
- [x] #182 Add ^C signal handler for non-deamon mode
- [x] #183 Add regression tests for exit command
- [x] #185 Extend regression tests to cover help functionality
Minor maintenance work related to internal docs (`gethelp`) - fixes, improvements, enhancements is WIP and usually done within my periodic `g-maintenance` branch, you are welcome to join the effortsGandalfGandalfhttps://gitlab.syncad.com/hive/hivemind/-/issues/125Implement the other community types included in the original design doc2021-03-13T14:38:07ZSergioImplement the other community types included in the original design docAccording to [this doc](https://gitlab.syncad.com/hive/hivemind/-/blob/master/docs/communities.md) there should have been 3 types of communities.
We have the first one, but still missing the second and third option:
1. ~~**Topic**: any...According to [this doc](https://gitlab.syncad.com/hive/hivemind/-/blob/master/docs/communities.md) there should have been 3 types of communities.
We have the first one, but still missing the second and third option:
1. ~~**Topic**: anyone can post or comment~~
2. **Journal**: guests can comment but not post. only members can post.
3. **Council**: only members can post or comment
This has been discussed in this [Hive Dev meeting](https://gitlab.syncad.com/hive/tasks_without_projects_yet/-/issues/29) and I'm opening the ticket to start a discussionHowoHowohttps://gitlab.syncad.com/hive/tasks_without_projects_yet/-/issues/10Add HIVE to SLIP-442020-05-13T06:01:45ZLuke StokesAdd HIVE to SLIP-44This should be coordinated with those with experience working with key derivations from seed phrases on things like the Ledger wallet. Currently STEEM is listed, but HIVE is not. Once an agreed to hexa is selected (maybe the next open on...This should be coordinated with those with experience working with key derivations from seed phrases on things like the Ledger wallet. Currently STEEM is listed, but HIVE is not. Once an agreed to hexa is selected (maybe the next open one: 509 | 0x800001fd?) it should be as simple as submitting a pull request. Comments on other PS say to use the first available number.
https://github.com/satoshilabs/slips/blob/master/slip-0044.mdhttps://gitlab.syncad.com/hive/hive-js/-/issues/2Implement replacements for any data served up by condenser_api that is not av...2020-05-09T23:11:50ZDan NotesteinImplement replacements for any data served up by condenser_api that is not available except by condenser_api now (assuming an app needs it)List in this issue any data that your app currently gets from a condenser_api call that you can't figure out how to get without that call. List the condenser_api call (and the relevant data field that you can't get, if it's not obvious):...List in this issue any data that your app currently gets from a condenser_api call that you can't figure out how to get without that call. List the condenser_api call (and the relevant data field that you can't get, if it's not obvious):
* [ ]?Emmanuel King TurnerEmmanuel King Turner