hive issueshttps://gitlab.syncad.com/groups/hive/-/issues2024-03-13T12:40:34Zhttps://gitlab.syncad.com/hive/vessel/-/issues/29Persist window size and position2024-03-13T12:40:34ZBartłomiej GórnickiPersist window size and positionThe application should be able to remember the last size set by the user. The default size should be adjusted to meet popular screen resolutions currently in use.The application should be able to remember the last size set by the user. The default size should be adjusted to meet popular screen resolutions currently in use.https://gitlab.syncad.com/hive/hive/-/issues/667Improve and simplify mirrornet conversion jobs2024-03-12T15:58:57ZBartek WronaImprove and simplify mirrornet conversion jobs1. Move gitlab CI inlined code into dedicated bash script files for better maintenance and simplifed local usage
2. Allow to define `NUMBER_OF_BLOCKS` as 0, what means to peform block_log conversion into to the end of fresh mainnet block...1. Move gitlab CI inlined code into dedicated bash script files for better maintenance and simplifed local usage
2. Allow to define `NUMBER_OF_BLOCKS` as 0, what means to peform block_log conversion into to the end of fresh mainnet block log. Mainnet block log should be incrementally synced from pointed remote ( i.e. https://gtg.openhive.network/get/blockchain/block_log )Konrad BotorKonrad Botorhttps://gitlab.syncad.com/hive/clive/-/issues/165Add `all!` (GenerouosButton) to the `Delegate` TabPane2024-03-12T13:09:47ZJakub ZiebinskiAdd `all!` (GenerouosButton) to the `Delegate` TabPaneAdding `GenerousButton` requires more demanding calculations. Probably some calculations should be added to `wax`. After researching the topic, the button should be added to the `Delegate` TabPane.Adding `GenerousButton` requires more demanding calculations. Probably some calculations should be added to `wax`. After researching the topic, the button should be added to the `Delegate` TabPane.MVP - Minimum Viable Producthttps://gitlab.syncad.com/hive/hive/-/issues/666Review and cleanup boost synchronization primitives usage in hive codebase2024-03-11T15:51:57ZBartek WronaReview and cleanup boost synchronization primitives usage in hive codebaseEspecialy in aspect of fc::thread usecontext.
Related to changes done here: https://gitlab.syncad.com/hive/hive/-/merge_requests/1241Especialy in aspect of fc::thread usecontext.
Related to changes done here: https://gitlab.syncad.com/hive/hive/-/merge_requests/1241Post 1.27.5Krzysztof LeśniakKrzysztof Leśniakhttps://gitlab.syncad.com/hive/clive/-/issues/164Create model for the percent value2024-03-11T14:22:46ZJakub ZiebinskiCreate model for the percent valueThe percent value can be passed with 2 decimal places. Some kind of model for the percentage value should be created, similar to the `Asset` model. It could probably be created at the `schemas` level.The percent value can be passed with 2 decimal places. Some kind of model for the percentage value should be created, similar to the `Asset` model. It could probably be created at the `schemas` level.MVP - Minimum Viable Producthttps://gitlab.syncad.com/hive/block_explorer_ui/-/issues/221Move fetching to HiveChain2024-03-11T09:49:22ZJakub LachórMove fetching to HiveChainWax allows to use API calls there with structural definitions. We should move our communication with BE entirely to Wax in future.Wax allows to use API calls there with structural definitions. We should move our communication with BE entirely to Wax in future.Jakub LachórJakub Lachórhttps://gitlab.syncad.com/hive/beem/-/issues/13Update to use scrypt 0.8.202024-03-10T11:13:31ZBrian of LondonUpdate to use scrypt 0.8.20Can this be updated to install correctly with scrypt 0.8.20 ?
I think there is a 0.8.21 but that isn't built correctly.
```
╰─± poetry add git+https://gitlab.syncad.com/hive/beem.git
Updating dependencies
Resolving dependencies... (0....Can this be updated to install correctly with scrypt 0.8.20 ?
I think there is a 0.8.21 but that isn't built correctly.
```
╰─± poetry add git+https://gitlab.syncad.com/hive/beem.git
Updating dependencies
Resolving dependencies... (0.0s)
Because beem (0.26.0) @ git+https://gitlab.syncad.com/hive/beem.git@HEAD depends on scrypt (0.8.18)
and v4vapp-api-ext depends on scrypt (0.8.20), beem is forbidden.
So, because v4vapp-api-ext depends on beem (0.26.0) @ git+https://gitlab.syncad.com/hive/beem.git, version solving failed.
╭─bol at home-imac in ~/Documents/dev/v4vapp/v4vapp-api-ext on develop✔ using «v4vapp-api-ext-cc3pDiTe-py3.11»
╰─±
```
I also have a specific problem in the `ecdsasig.py` file which which I've fixed in my own git repo forked on github. I'm not able to for on Gitlab here unfortunately.
https://github.com/brianoflondon/beem/commit/38329a231aa6becff374bb2ed3e012bd4ab477bchttps://gitlab.syncad.com/hive/beem/-/issues/12PyPi version is the unmaintained version of Beem2024-03-10T08:56:36ZMarkyPyPi version is the unmaintained version of BeemIt would be great if we could push out tagged releases of this version of Beem rather than leave the 3+ year old abandoned version of Beem on Github as our "official" Python version.It would be great if we could push out tagged releases of this version of Beem rather than leave the 3+ year old abandoned version of Beem on Github as our "official" Python version.https://gitlab.syncad.com/hive/beem/-/issues/11Comment.edit() doesn't work with top level posts2024-03-10T08:54:31ZMarkyComment.edit() doesn't work with top level postsWhen you try to edit a comment (top level post), you get an error "KeyError: 'parent_author'.
```
>>> comment.edit(new_body)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/mal/miniconda3/lib/pytho...When you try to edit a comment (top level post), you get an error "KeyError: 'parent_author'.
```
>>> comment.edit(new_body)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/mal/miniconda3/lib/python3.11/site-packages/beem/comment.py", line 748, in edit
original_post["parent_author"], original_post["parent_permlink"])
~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
File "/home/mal/miniconda3/lib/python3.11/site-packages/beem/blockchainobject.py", line 210, in __getitem__
return super(BlockchainObject, self).__getitem__(key)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
KeyError: 'parent_author'
```
Ultimately, Comment.edit() returns to a call to blockchaininstance.post() which I am able to use directly to work around this issue.https://gitlab.syncad.com/hive/block_explorer_ui/-/issues/218Remove , from block number inputs2024-03-08T12:27:35ZJakub LachórRemove , from block number inputsAll inputs when you can put numbers should be resistant to localizations.All inputs when you can put numbers should be resistant to localizations.Piotr BerezkaPiotr Berezkahttps://gitlab.syncad.com/hive/haf/-/issues/215Examine ideas for APIs and frontend libraries to improve caching performance2024-03-13T23:01:55ZDan NotesteinExamine ideas for APIs and frontend libraries to improve caching performanceCurrent APIs as used aren't great for caching. For example, asking for the last 1000 operations in the blockchain wouldn't match a similar request made 3s before by another client. And requests made after to fetch older data will also no...Current APIs as used aren't great for caching. For example, asking for the last 1000 operations in the blockchain wouldn't match a similar request made 3s before by another client. And requests made after to fetch older data will also not generate cache hits between the clients (i.e. if we ask for the next 1000 operations that occurred before the first request).
But at the expense of two calls for the first fetch, and an assumption about what is a reasonable amount of data to fetch per call, we could develop libraries that made calls to nodes that are efficiently cacheable.
For example, assume we had a chain that currently had 1000132 operations at the moment of the call and we think it is reasonable to fetch 100 items at a time. We could make a library function that asked for the most recent operations up to the nearest 100s place. This call would return items from 1,000,132 to 1,000,100. This first call wouldn't generate a hit with a call made 3s later from another client, of course (the 2nd client would for example might end up fetch 1,000,150 to 1,000,100). But any further calls made by either client to get more data would generate cache hits between each other. In other words, both would fetch 1,000,100 to 1,000,000 next. With many clients using a library that fetches in this manner, cache hits would dramatically increase.https://gitlab.syncad.com/hive/hive-renderer/-/issues/17HtmlDomParser incorrectly build images and links state2024-03-06T23:14:12ZBartłomiej GórnickiHtmlDomParser incorrectly build images and links stateHtmlDomParser after parsing the text, it build the state to keep images and links. It incorrectly uses hardoded youtube regex and ignores other embeds.HtmlDomParser after parsing the text, it build the state to keep images and links. It incorrectly uses hardoded youtube regex and ignores other embeds.https://gitlab.syncad.com/hive/haf_block_explorer/-/issues/70CI rewrite2024-03-12T08:21:32ZKonrad BotorCI rewriteCI needs to be rewritten.
- [ ] Test jobs' code needs to be more unified - especially *after_script* sections (ideally one for all jobs).
- [ ] Fixing Compose project name (should be haf_be, but is btracker).
- [ ] Possible updates afte...CI needs to be rewritten.
- [ ] Test jobs' code needs to be more unified - especially *after_script* sections (ideally one for all jobs).
- [ ] Fixing Compose project name (should be haf_be, but is btracker).
- [ ] Possible updates after hive#648 (although in current form it should *just work* after *copy_data.sh* execution is removed from the entrypoint).
- [ ] Move *psql* Docker image to hive/common-ci-configuration>. Rewrite Composefiles. See also balance_tracker#16.
- [ ] Check if HAF replay and block_log.artifacts are generated in every test job. If so make sure they aren't.
- [ ] Turn off logging `docker pull`.
- [ ] Make the *Running tests...* section uncollapsed by default.
- [ ] Investigate the lack of logs if HAF startup fails.
- [ ] Move larger embedded Bash scripts to separate files.
- [ ] Make a template that can be reused in other projects.
- [ ] Implement #72
See also changes in fddb083f75aa3f6a2dd6607589a4ddd90e8d34a3.Konrad BotorKonrad Botorhttps://gitlab.syncad.com/hive/hive-renderer/-/issues/16Update RendererOptions interface to simplify configuration2024-03-13T14:42:13ZBartłomiej GórnickiUpdate RendererOptions interface to simplify configurationTo make the renderer API simpler and easier to use, we should make most of the options optional with default values when not provided.To make the renderer API simpler and easier to use, we should make most of the options optional with default values when not provided.Bartłomiej GórnickiBartłomiej Górnickihttps://gitlab.syncad.com/hive/clive/-/issues/163Refactor savings screen2024-03-06T07:17:53ZJakub ZiebinskiRefactor savings screenSome elements on the savings screen can be rafactored with some custom clive-widgets. Two the most important:
1. `CliveCheckerboardTable` -> we can use this widget to create a table of pending transfers from savings.
2. `CliveDataTable` ...Some elements on the savings screen can be rafactored with some custom clive-widgets. Two the most important:
1. `CliveCheckerboardTable` -> we can use this widget to create a table of pending transfers from savings.
2. `CliveDataTable` -> this widget can be used to display savings balances.MVP - Minimum Viable ProductJakub ZiebinskiJakub Ziebinskihttps://gitlab.syncad.com/hive/hive-renderer/-/issues/15Link attributes `rel` and `target` incorrectly depends on `isLinkSafeFn`2024-03-06T21:57:42ZBartłomiej GórnickiLink attributes `rel` and `target` incorrectly depends on `isLinkSafeFn`Those attributes should be assigned to external links, not only "phishy" links.Those attributes should be assigned to external links, not only "phishy" links.https://gitlab.syncad.com/hive/hive-renderer/-/issues/14Default localization options should depends on baseUrl2024-03-05T21:59:14ZBartłomiej GórnickiDefault localization options should depends on baseUrlDefault localization message `externalLink` uses `example.com` and should use `baseUrl` provided when initializing the renderer.
Please improve documentation on how to provide custom localization to the renderer for other languages.Default localization message `externalLink` uses `example.com` and should use `baseUrl` provided when initializing the renderer.
Please improve documentation on how to provide custom localization to the renderer for other languages.https://gitlab.syncad.com/hive/hive-renderer/-/issues/13Add `dir` attribute to every paragraph to support right-to-left languages2024-03-05T15:39:53ZBartłomiej GórnickiAdd `dir` attribute to every paragraph to support right-to-left languageshttps://gitlab.syncad.com/hive/imagehoster/-/issues/12Change default format to webp2024-03-04T23:08:09ZDamian JanusChange default format to webpDamian JanusDamian Janushttps://gitlab.syncad.com/hive/haf/-/issues/214Support haf-app based lite accounts2024-03-28T15:10:28ZDan NotesteinSupport haf-app based lite accountsThis is probably best done as a haf app, but creating issue here for now.
Purpose: allow people to use Hive (or other Hive based apps like some games) without a need to create Hive account.
Initial design goals/functionality for furth...This is probably best done as a haf app, but creating issue here for now.
Purpose: allow people to use Hive (or other Hive based apps like some games) without a need to create Hive account.
Initial design goals/functionality for further discussion:
1. App code reuse. It should be possible to embed this app code by 3rd party apps.
Reusing should be done by explicit Lite-Account app integration into parent application code to expose final functionality together with other final app services (i.e provided via REST)
1. While configuring the app, regular Hive account should be used as Hive-blockchain bridge and allow interaction to Hive
1. Lite account identifiers should be unique - to make it possible we need to introduce some namespaces
1. Bridge account name should be used as a namespace holding account identifiers.
1. Only account creation operation is limited to namespace matching the bridge account. All other operations (i.e. property modification) are accepted regardless to matching account namespace and bridge account and are only confirmed by matching a public key associated to LA.
1. Lite-Account should have associated its public key, used to authorize actions performed by LA (i.e. changing its properties)
1. Lite-Account properties can be created/modified/deleted by any bridge account when LA public key is matching
1. All actions specific to Lite-Accounts should be done by using custom operation (custom_binary/custom/custom_json). The internal action embedded into custom operation should be signed by LA private key to proof that given account scheduled given action. Whole Hive transaction containing a custom operation should be signed by bridge account, to match Hive protocol requirements.
1. If Lite-Account would like to perform regular Hive activity (i.e. vote or write a post), it could be possible by preparing (inside single transaction) a custom operation containing required Hive action being signed by LA private key, followed by regular Hive operation finally signed by bridge account.
Above solution will allow to distinguish LA direct Hive activity from bridge account operations.Post-1.27.5