hive issueshttps://gitlab.syncad.com/groups/hive/-/issues2024-03-28T22:11:59Zhttps://gitlab.syncad.com/hive/denser/-/issues/292Add edit mode for post and comment2024-03-28T22:11:59ZDamian JanusAdd edit mode for post and commentDamian JanusDamian Janushttps://gitlab.syncad.com/hive/hive/-/issues/672Do we ever want to fix witness_set_properties?2024-03-28T20:11:12ZMahdi YariDo we ever want to fix witness_set_properties?Unlike other operations, [the body of this operation must be serialized](https://gitlab.syncad.com/hive/hive-js/tree/master/doc#build-witness-update-properties). It doesn't make sense why would that be the case. Do we ever want to fix th...Unlike other operations, [the body of this operation must be serialized](https://gitlab.syncad.com/hive/hive-js/tree/master/doc#build-witness-update-properties). It doesn't make sense why would that be the case. Do we ever want to fix this operation in a hardfork so it becomes in line with other operations?
The link provided is just an example and it is not related to hive-js. For other operations we do like:
```
{
url: 'https://testurl'
}
```
but for this operation the body must be serialized:
```
{
url: '0f68747470733a2f2f7465737475726c'
}
```https://gitlab.syncad.com/hive/hivemind/-/issues/240Change "errors" for missing data to "warning" or "info" to avoid postgres log...2024-03-28T18:43:43ZDan NotesteinChange "errors" for missing data to "warning" or "info" to avoid postgres logging themPostgres logs are filled with this type of error message:
```
2024-03-28 17:40:19 UTC [2291]: app=hive_server STATEMENT: SELECT * FROM hivemind_app.condenser_get_content('steemychicken1', 'pglwzhbavs')
2024-03-28 17:40:19 UTC [593]: app...Postgres logs are filled with this type of error message:
```
2024-03-28 17:40:19 UTC [2291]: app=hive_server STATEMENT: SELECT * FROM hivemind_app.condenser_get_content('steemychicken1', 'pglwzhbavs')
2024-03-28 17:40:19 UTC [593]: app=hive_server ERROR: Post travoved/ynsbhlpfgx does not exist
2024-03-28 17:40:19 UTC [593]: app=hive_server CONTEXT: PL/pgSQL function hivemind_app.find_comment_id(character varying,character varying,boolean) line 22 at RAISE
PL/pgSQL function hivemind_app.condenser_get_content(character varying,character varying) line 5 at assignment
2024-03-28 17:40:19 UTC [593]: app=hive_server STATEMENT: SELECT * FROM hivemind_app.condenser_get_content('travoved', 'ynsbhlpfgx')
2024-03-28 17:40:19 UTC [522]: app=hive_server ERROR: Post firulaixcoin/hzqwpsbnxx does not exist
2024-03-28 17:40:19 UTC [522]: app=hive_server CONTEXT: PL/pgSQL function hivemind_app.find_comment_id(character varying,character varying,boolean) line 22 at RAISE
PL/pgSQL function hivemind_app.condenser_get_content(character varying,character varying) line 5 at assignment
```JulyHivemindhttps://gitlab.syncad.com/hive/haf/-/issues/220Dynamic schema selection allows to deploy same application code into separate...2024-03-28T16:33:26ZBartek WronaDynamic schema selection allows to deploy same application code into separate schemasThis (probably) allows to solve the issue related to deploying same application multiple times on same HAF instance. Good example is a balance tracker, which could be deployed together with `haf_be` like also as standalone installation. ...This (probably) allows to solve the issue related to deploying same application multiple times on same HAF instance. Good example is a balance tracker, which could be deployed together with `haf_be` like also as standalone installation. Right now, because balance_tracker code statically defines its deployment schema it is impossible.
Changing `search_path` property at code deployment time and using schemaless notation on object declarations allows to create given objects inside target schema dynamically - each time into schema pointed by search_path property.
```
--- separate schema creation code:
create schema my_test authorization haf_admin;
```
```
--- separate schema selection code:
set search_path=my_test;
```
```
--- separate object definition code:
CREATE OR REPLACE FUNCTION some_fun()
RETURNS boolean
LANGUAGE 'plpgsql'
AS $BODY$
BEGIN
RETURN false;
END
$BODY$;
```
Finally above could be done as:
```
psql -c 'set search_path=my_test;' -f common_app_defs.sql
```
We need further investigation how to simple force correct resolution of identifiers (i.e. inside function definition) to actual schema. Maybe just setting `search_path` at roles specific to the application using given code would be sufficient.https://gitlab.syncad.com/hive/denser/-/issues/291Fix Advanced Settings in Post Form2024-03-28T15:09:41ZKrzysztof KocotFix Advanced Settings in Post FormKrzysztof KocotKrzysztof Kocothttps://gitlab.syncad.com/hive/clive/-/issues/188TUI - the currency should be removed from the right panel with balances2024-03-28T13:55:22ZAleksandra GrabowskaTUI - the currency should be removed from the right panel with balancesIf a user has more than 100000 hive, the currency is shown incorrectly as `HIV`. The currency after amount can be removed, because the field description is `HIVE balance`.
![image](/uploads/10555edb80d4ff19e68e12ec3ef5ce5b/image.png)If a user has more than 100000 hive, the currency is shown incorrectly as `HIV`. The currency after amount can be removed, because the field description is `HIVE balance`.
![image](/uploads/10555edb80d4ff19e68e12ec3ef5ce5b/image.png)10th releasehttps://gitlab.syncad.com/hive/clive/-/issues/187Test - CLI - Transaction2024-03-28T10:40:13ZAleksandra GrabowskaTest - CLI - TransactionThe following commands should be tested:
a. clive process transaction (transfer, savings, governance, hive power management, file format, signed and unsigned)
b. clive show transaction-statusThe following commands should be tested:
a. clive process transaction (transfer, savings, governance, hive power management, file format, signed and unsigned)
b. clive show transaction-statusMVP - Minimum Viable Producthttps://gitlab.syncad.com/hive/clive/-/issues/186Test - CLI - Governance2024-03-28T10:40:43ZAleksandra GrabowskaTest - CLI - GovernanceThe following commands should be tested:
a. `clive process vote-proposal` (add, remove)
b. `clive process vote-witness` (add, remove)
c. `clive process proxy` (clear, set)
d. `clive show proposal`
e....The following commands should be tested:
a. `clive process vote-proposal` (add, remove)
b. `clive process vote-witness` (add, remove)
c. `clive process proxy` (clear, set)
d. `clive show proposal`
e. `clive show proposals` (order-by, order-direction, status, page-size, page-no)
f. `clive show proxy`
g. `clive show witness`
h. `clive show witnesses` (page-size, page-no)MVP - Minimum Viable Producthttps://gitlab.syncad.com/hive/clive/-/issues/184Test - CLI - Transfer2024-03-28T12:23:29ZAleksandra GrabowskaTest - CLI - TransferThe following commands should be tested:
1. `clive process transfer`
2. `clive show balances`The following commands should be tested:
1. `clive process transfer`
2. `clive show balances`MVP - Minimum Viable Producthttps://gitlab.syncad.com/hive/clive/-/issues/183Test - CLI - Chain-id configuration2024-03-28T10:40:43ZAleksandra GrabowskaTest - CLI - Chain-id configurationThe following commands should be tested:
1. `clive configure chain-id`
2. `clive show profile` - the chain-id is shown there.The following commands should be tested:
1. `clive configure chain-id`
2. `clive show profile` - the chain-id is shown there.MVP - Minimum Viable Producthttps://gitlab.syncad.com/hive/clive/-/issues/182Test - CLI - key configuration2024-03-28T10:40:43ZAleksandra GrabowskaTest - CLI - key configurationThe following commands should be tested:
1. `clive configure key` (add, remove)
2. `clive show keys`The following commands should be tested:
1. `clive configure key` (add, remove)
2. `clive show keys`MVP - Minimum Viable Producthttps://gitlab.syncad.com/hive/clive/-/issues/181Test - CLI - node configuration2024-03-28T10:40:43ZAleksandra GrabowskaTest - CLI - node configurationThe following commands should be tested:
1. `clive configure node set`
2. `clive show node`.The following commands should be tested:
1. `clive configure node set`
2. `clive show node`.MVP - Minimum Viable Producthttps://gitlab.syncad.com/hive/clive/-/issues/180Test - CLI - profile configuration2024-03-28T10:40:43ZAleksandra GrabowskaTest - CLI - profile configurationThe following commands should be tested:
1. `clive configure profile` (set, remove, set-default)
- create profile with or without working account
2. `clive configure working-account` (add, remove)
3. `clive configure watched-accoun...The following commands should be tested:
1. `clive configure profile` (set, remove, set-default)
- create profile with or without working account
2. `clive configure working-account` (add, remove)
3. `clive configure watched-account` (add, remove)
4. `clive show profile`
5. `clive show profiles`
6. `clive show accounts`MVP - Minimum Viable Producthttps://gitlab.syncad.com/hive/clive/-/issues/179Test - CLI - list of missing tests2024-03-28T10:40:59ZAleksandra GrabowskaTest - CLI - list of missing tests1. Configure
1.1 Profile & accounts - https://gitlab.syncad.com/hive/clive/-/issues/180
a. Configure (profile, watched-account, working-account)
b. Show (profile, profiles, accounts)
1.2 Node - https://gitlab.syncad.com/hive...1. Configure
1.1 Profile & accounts - https://gitlab.syncad.com/hive/clive/-/issues/180
a. Configure (profile, watched-account, working-account)
b. Show (profile, profiles, accounts)
1.2 Node - https://gitlab.syncad.com/hive/clive/-/issues/181
a. Configure (node)
b. Show (profile)
1.3. Key - https://gitlab.syncad.com/hive/clive/-/issues/182
a. Configure (key)
b. Show (keys)
1.4.Chain-id - https://gitlab.syncad.com/hive/clive/-/issues/183
a. Configure (chain-id)
b. Show (profile)
2. Operations
2.1. Transfer -https://gitlab.syncad.com/hive/clive/-/issues/184
a. Process (transfer)
b. show (balances)
2.2. Savings - https://gitlab.syncad.com/hive/clive/-/issues/185
a. Process (savings deposit, savings withdrawal, savings withdrawal-cancel)
b. Show (pending withdrawals, balances)
2.3. Update authority :heavy_check_mark:
a. Process (update-active-authority, update-owner-authority, update-posting-authority, update-memo-key)
b. Show (active-authority, owner-authority, posting-authority, memo-key)
2.4 Hive power management - tests will be implemented together with functionality
a. Process (delegations, power-down, power-up, withdraw-routes)
b. Show (hive-power, pending power-downs, pending power-ups, pending removed-delegations)
2.5. Governance - https://gitlab.syncad.com/hive/clive/-/issues/186
a. Process (vote-proposal, vote-witness, proxy)
b. Show (proposal, proposals, proxy, witness, witnesses)
3. Transaction - https://gitlab.syncad.com/hive/clive/-/issues/187
a. process Transaction
b. show transaction-statusMVP - Minimum Viable Producthttps://gitlab.syncad.com/hive/block_explorer_ui/-/issues/244Fix and improve mobile layout2024-03-28T10:47:04ZPiotr BerezkaFix and improve mobile layoutPiotr BerezkaPiotr Berezkahttps://gitlab.syncad.com/hive/clive/-/issues/178Tests bekeeper - random fail of test_wallet_blocking_timeout[False] - Asserti...2024-03-28T08:49:58ZMateusz ŻebrakTests bekeeper - random fail of test_wallet_blocking_timeout[False] - AssertionError: Regex pattern did not match.https://gitlab.syncad.com/hive/clive/-/jobs/1076255
Apart from the
```
FAILED tests/functional/beekeeper/api_tests/test_api_create_session.py::test_api_create_session_max_sessions - clive.exceptions.CommunicationTimeoutError: Timeout o...https://gitlab.syncad.com/hive/clive/-/jobs/1076255
Apart from the
```
FAILED tests/functional/beekeeper/api_tests/test_api_create_session.py::test_api_create_session_max_sessions - clive.exceptions.CommunicationTimeoutError: Timeout occurred during communication with: url='http://127.0.0.1:40917'. Exceeded 1 attempts, each of 12.00s.
```
which can be explained as the CI was heavy loaded (and timeout was too low)
there also was a weird error of:
```
FAILED tests/functional/beekeeper/various/test_blocking_unlock.py::test_wallet_blocking_timeout[False] - AssertionError: Regex pattern did not match.
Regex: 'AES error:error during aes 256 cbc decrypt finalrethrow'
Input: 'Out of Range:read datastream of length 143 over by -12fc::array<type,length>Error unpacking field keyserror unpacking beekeeper::plain_keyserror unpacking beekeeper::plain_keysrethrow'
```
which should be checked.Wieslaw KedzierskiWieslaw Kedzierskihttps://gitlab.syncad.com/hive/haf/-/issues/219Simplify docker_entrypoint2024-03-27T17:27:45ZBartek WronaSimplify docker_entrypointDue to work done in https://gitlab.syncad.com/hive/hive/-/merge_requests/1196
we can eliminate part of code specific to dumping `track_after_block` to HAF instance config.ini file:
https://gitlab.syncad.com/hive/haf/-/blob/develop/docker...Due to work done in https://gitlab.syncad.com/hive/hive/-/merge_requests/1196
we can eliminate part of code specific to dumping `track_after_block` to HAF instance config.ini file:
https://gitlab.syncad.com/hive/haf/-/blob/develop/docker/docker_entrypoint.sh?ref_type=heads#L124Post-1.27.5https://gitlab.syncad.com/hive/condenser/-/issues/221Fix bandcamp embed player2024-03-27T14:01:50ZQuoc Huy Nguyen DinhFix bandcamp embed playerRef: https://peakd.com/@gribbles/sa338bRef: https://peakd.com/@gribbles/sa338bhttps://gitlab.syncad.com/hive/condenser/-/issues/220Add support to countdown in posts2024-03-27T14:00:31ZQuoc Huy Nguyen DinhAdd support to countdown in posts* Add an option in the advance settings of the post editor.
* Save the countdown value in json_metadata
* Render a countdown in the post
`json_metadata: {"app":"peakd/2024.3.3","format":"markdown","countdown":"2024-03-19T16:00:00.000Z",...* Add an option in the advance settings of the post editor.
* Save the countdown value in json_metadata
* Render a countdown in the post
`json_metadata: {"app":"peakd/2024.3.3","format":"markdown","countdown":"2024-03-19T16:00:00.000Z","tags":["hive-engine"],"users":[],"image":[]}`
Example:
https://peakd.com/hive-engine/@aicurat/test-posthttps://gitlab.syncad.com/hive/clive/-/issues/177CLI tests random fail2024-03-27T12:11:27ZMateusz ŻebrakCLI tests random failJob: [https://gitlab.syncad.com/hive/clive/-/jobs/1075226](https://gitlab.syncad.com/hive/clive/-/jobs/1075226 "https://gitlab.syncad.com/hive/clive/-/jobs/1075226")
fails because of too lenient assertion, just like `assert amount in ou...Job: [https://gitlab.syncad.com/hive/clive/-/jobs/1075226](https://gitlab.syncad.com/hive/clive/-/jobs/1075226 "https://gitlab.syncad.com/hive/clive/-/jobs/1075226")
fails because of too lenient assertion, just like `assert amount in output`:
```
'234' is contained here:
took: 0.023470s
```Marcin SobczykMarcin Sobczyk