hive issueshttps://gitlab.syncad.com/groups/hive/-/issues2024-03-25T17:01:49Zhttps://gitlab.syncad.com/hive/denser/-/issues/282Add functionality to Advanced Settings in PostForm2024-03-25T17:01:49ZKrzysztof KocotAdd functionality to Advanced Settings in PostFormKrzysztof KocotKrzysztof Kocothttps://gitlab.syncad.com/hive/block_explorer_ui/-/issues/231A time lag of an hour in datatime filter in votes history dialog2024-03-26T12:47:03ZAdam KociubinskiA time lag of an hour in datatime filter in votes history dialogCompare below pictures:<br>
Range time is to 12:30:00<br>You can see 'natubat' user who's time is 11:27:30<br>
![image](/uploads/0f8c06f4c1b69b3b58262ffd3f77c35d/image.png)<br>
but if you change time to the 12:25:00 in the datapicker tha...Compare below pictures:<br>
Range time is to 12:30:00<br>You can see 'natubat' user who's time is 11:27:30<br>
![image](/uploads/0f8c06f4c1b69b3b58262ffd3f77c35d/image.png)<br>
but if you change time to the 12:25:00 in the datapicker that user is not visible<br>
![image](/uploads/10c0ab2142d9cffd709b9ba227ceb741/image.png)<br><br>
It looks like a time lag of an hour in datatime filter.Piotr BerezkaPiotr Berezkahttps://gitlab.syncad.com/hive/denser/-/issues/281Add version hash to sidebar2024-03-19T09:50:22ZDamian JanusAdd version hash to sidebarDamian JanusDamian Janushttps://gitlab.syncad.com/hive/block_explorer_ui/-/issues/230Wrong balances shown for account propetries2024-03-20T06:38:33ZBartek WronaWrong balances shown for account propetriesAccount properties shown formatted balances values, but the format is done wrong it seems. There must be used some different formatting code than WAX asset formatter, since values are not adjusted to asset precision, thus in case of HBD ...Account properties shown formatted balances values, but the format is done wrong it seems. There must be used some different formatting code than WAX asset formatter, since values are not adjusted to asset precision, thus in case of HBD show 1000x bigger quotes.Jakub LachórJakub Lachórhttps://gitlab.syncad.com/hive/hive-account-creator/-/issues/1Change req.body.account to be always lower case2024-03-18T23:31:08ZDamian JanusChange req.body.account to be always lower caseDamian JanusDamian Janushttps://gitlab.syncad.com/hive/denser/-/issues/280Redirect after post creation and change article creation fn to use new wax in...2024-03-19T10:16:28ZDamian JanusRedirect after post creation and change article creation fn to use new wax interfaceDamian JanusDamian Janushttps://gitlab.syncad.com/hive/block_explorer_ui/-/issues/229Changing Explorer backend to a non-functional one doesn't allow further changes2024-03-19T15:04:59ZDan NotesteinChanging Explorer backend to a non-functional one doesn't allow further changeshttps://gitlab.syncad.com/hive/block_explorer_ui/-/issues/228Mismatched blockchain financial props2024-03-20T06:38:42ZBartek WronaMismatched blockchain financial propsIt seems that BE UI shows mismatched values for `Pending rewarded vesting hive` and `Total vesting fund hive`.
![image](/uploads/ca3f478c530833a83b0b774553bddb38/image.png)
Here is part of dgpo response:
```
"pending_rewarded_vesting_...It seems that BE UI shows mismatched values for `Pending rewarded vesting hive` and `Total vesting fund hive`.
![image](/uploads/ca3f478c530833a83b0b774553bddb38/image.png)
Here is part of dgpo response:
```
"pending_rewarded_vesting_hive": {
"amount": "497181782",
"precision": 3,
"nai": "@@000000021"
},
```
and
```
"total_vesting_fund_hive": {
"amount": "173732828858",
"precision": 3,
"nai": "@@000000021"
},
```https://gitlab.syncad.com/hive/block_explorer_ui/-/issues/227Broken paging control when opening account history view2024-03-22T14:25:52ZBartek WronaBroken paging control when opening account history viewBy design all data pages should be displayed in descending order to show latest one as first. UI randomly switches it to the opposite order.
Data has been shown for blocktrades account.
![image](/uploads/6e7d72c9fcdac75f3120d765eb1eda7...By design all data pages should be displayed in descending order to show latest one as first. UI randomly switches it to the opposite order.
Data has been shown for blocktrades account.
![image](/uploads/6e7d72c9fcdac75f3120d765eb1eda7d/image.png)Piotr BerezkaPiotr Berezkahttps://gitlab.syncad.com/hive/block_explorer_ui/-/issues/226Shortened data displayed even data row and view have plenty of space2024-03-20T09:41:15ZBartek WronaShortened data displayed even data row and view have plenty of space![image](/uploads/ae2168b7172621dc75881908f6f6e58b/image.png)![image](/uploads/ae2168b7172621dc75881908f6f6e58b/image.png)https://gitlab.syncad.com/hive/haf_block_explorer/-/issues/73Procedure building images for testing and release purposes should be thersame2024-03-25T14:22:45ZBartek WronaProcedure building images for testing and release purposes should be thersameEven we want to build official image just before push on demand in both cases build should be done the same way. Right now haf_block_explorer and balance_tracker uses different scripts and jobs to do it, what due to bug in:
https://gitla...Even we want to build official image just before push on demand in both cases build should be done the same way. Right now haf_block_explorer and balance_tracker uses different scripts and jobs to do it, what due to bug in:
https://gitlab.syncad.com/hive/common-ci-configuration/-/blob/develop/templates/docker_image_jobs.gitlab-ci.yml?ref_type=heads#L44
which hidden important part of before_script inherited from:
https://gitlab.syncad.com/hive/common-ci-configuration/-/blob/develop/templates/docker_image_jobs.gitlab-ci.yml?ref_type=heads#L9
lead to image build failure.
All or most of code required to build the image should be stored in local scripts, to allow easy local reproducing of potential problems and make code much more readable.
If our image builder needs to be preconfigured somehow, we should extend base image for that (which should be used in all cases) instead of "patching" code by missing statements put into before_script handlers what is hard to maintain and understand.Konrad BotorKonrad Botorhttps://gitlab.syncad.com/hive/hivemind/-/issues/235Try refactor of post tags2024-03-27T21:20:12ZDan NotesteinTry refactor of post tagsInstead of storing an array of tags in hive_posts, create an auxiliary table like with post_id, tag_id columns and a primary key on post_id, plus an index on btree(tag, post_id desc).
For example, for a post id 100 with two tags 5, 10:
`...Instead of storing an array of tags in hive_posts, create an auxiliary table like with post_id, tag_id columns and a primary key on post_id, plus an index on btree(tag, post_id desc).
For example, for a post id 100 with two tags 5, 10:
```
100,5
100,10
```
According to postgres docs (and common sense), search by tag should be faster this way: https://www.postgresql.org/docs/current/arrays.htmlhttps://gitlab.syncad.com/hive/hivemind/-/issues/234Hivemind tables have overridden autovacuum settings that I suspect are non-op...2024-03-27T03:09:20ZDan NotesteinHivemind tables have overridden autovacuum settings that I suspect are non-optimalhttps://gitlab.syncad.com/hive/haf/-/issues/217HAF Indexing fails after replaying with a 1.27.4 block_log2024-03-27T21:35:04ZDeathwinghi@deathwing.meHAF Indexing fails after replaying with a 1.27.4 block_log![image.png](/uploads/4bb701fbb92202e26c8bfc110199a2c5/image.png)
I have had this issue in two nodes now. What happens is that, despite the replay finishing without an issue, these errors pop up on indexing stage and destroy the overall...![image.png](/uploads/4bb701fbb92202e26c8bfc110199a2c5/image.png)
I have had this issue in two nodes now. What happens is that, despite the replay finishing without an issue, these errors pop up on indexing stage and destroy the overall state. No matter how many times its replayed, it does not fix it. A live sync (by deleting the block_log, which is the only file exists anyways) works fine.https://gitlab.syncad.com/hive/hive/-/issues/669HF28 test seems a lititle unstable2024-03-21T14:12:19ZDan NotesteinHF28 test seems a lititle unstableFailed once, but passed when the test was re-run here: https://gitlab.syncad.com/hive/haf/-/pipelines/89724.
If I recall correctly, the fail was due to something being late by one block.Failed once, but passed when the test was re-run here: https://gitlab.syncad.com/hive/haf/-/pipelines/89724.
If I recall correctly, the fail was due to something being late by one block.Krzysztof LeśniakKrzysztof Leśniakhttps://gitlab.syncad.com/hive/block_explorer_ui/-/issues/225Check and upgrade custom formatters for operations2024-03-20T10:22:59ZJakub LachórCheck and upgrade custom formatters for operationsI believe some part of custom formatters code may be extracted to more universal method. Maybe what we have is enough, but it's better to move even part of it into a little more generic methods.I believe some part of custom formatters code may be extracted to more universal method. Maybe what we have is enough, but it's better to move even part of it into a little more generic methods.Piotr BerezkaPiotr Berezkahttps://gitlab.syncad.com/hive/haf/-/issues/216We need tests for get_metadata2024-03-29T08:08:01ZMichal 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/166Improve testing cli framework with features from python 3.122024-03-15T12:33:15ZMarcin SobczykImprove testing cli framework with features from python 3.12There are helper methods of TestingCli like process_savings_deposit or process_savings_withdrawal that are silimar to cli commands "clive process savings deposit", "clive process savings withdrawal" etc). We accept multiple named argumen...There are helper methods of TestingCli like process_savings_deposit or process_savings_withdrawal that are silimar to cli commands "clive process savings deposit", "clive process savings withdrawal" etc). We accept multiple named arguments. This is however not easily extansible (if there are more commands there will be more boilerplate code). In python however 3.12 there is implemented https://peps.python.org/pep-0692/ . This allows adding types to **kwargs argument, as in example:
```
class Movie(TypedDict):
title: str
year: NotRequired[int]
def foo(name, /, **kwargs: Unpack[Movie]) -> None: ...
```
we could define following types for kwargs:
```
class OperationCommon(TypedDict):
profile_name: NotRequired[str]
password: NotRequired[str]
sign: NotRequired[str]
beekeeper_remote: NotRequired[str]
broadcast: NotRequired[bool]
save_file: NotRequired[str]
class TransferCommon(TypedDict):
amount: Required[tt.Asset.AntT]
memo: NotRequired[bool]
from_account: NotRequired[str]
class Transfer(OperationCommon, TransferCommon):
to: Required[str]
```
and define method transfer inside class TestingCli:
```
def transfer(name, /, **kwargs: Unpack[Transfer]) -> Result: ...
```
Benefit is much shorter code, we can also reuse common options as in CliveTyper (where it is done by decorators, we could also use decorators here but this feature from python 3.12 is much simpler) and it will be easy to add more cli commands.
I'm not sure when we will use python 3.12, this will happen when we use ubuntu 24.04 for hive image (python 3.12 is default on ubuntu 24.04)https://gitlab.syncad.com/hive/denser/-/issues/279Improve post editor2024-03-18T17:35:20ZKrzysztof KocotImprove post editorKrzysztof KocotKrzysztof Kocothttps://gitlab.syncad.com/hive/denser/-/issues/278Change arguments to operations fn in transactionService, add missing fn, use ...2024-03-18T11:47:56ZDamian JanusChange arguments to operations fn in transactionService, add missing fn, use new methods from wax for creation comment or articleDamian JanusDamian Janus