manikey123

Results 11 comments of manikey123

Refactoring database_fixture.cpp to remove test case names.

@abitmore plz assign the issue to me

get_collateral_bids_by_account for dashboard page on the UI

Can anyone help assign the issue to me. Research Estimate : 2-3 hrs

Part of #2456 - Don't abuse `get_full_accounts` API

> Just adding some notes here after done some research. > > The [`getAccount()` function](https://github.com/bitshares/bitsharesjs/blob/048452fe7ccb5315cffa747c135a6fd049f1cdf8/lib/chain/src/ChainStore.js#L677) will call `get_full_accounts` API with subscription by default, and call `get_account_history` API. > > ```...

Cannot login via private key option on beet

yes they do match. Tried on the mainnet

beet hackathon demo - If the authorization is removed re-authorization is not done and also no prompt comes up for it.

Please assign to me @sschiessl-bcp

beet hackathon demo - If the authorization is removed re-authorization is not done and also no prompt comes up for it.

OS Linux Ubuntu ~$ npm -v 6.9.0 ~$ node -v v10.14.1 Issue: installation steps need more details for Linux Resolution below: Step 1) Need to do a prebuild for Linux:...

beet hackathon demo - If the authorization is removed re-authorization is not done and also no prompt comes up for it.

#122 is a part of the ticket

beet hackathon demo - If the authorization is removed re-authorization is not done and also no prompt comes up for it.

Re-authentication issue **Steps to reproduce** Step 1) Authenticate beet with a dapp Step 2) Remove the the dapp authentication from the settings page in beet app Step 3) Now if...

Beet hackathon demo - Beet if reopened creates new process ids and the old process ids stay the same (Observed on Linux may be windows users wont face this issue) I needed to manually kill them for the app to work.

Below lines are spawning redundant threads. Resulting in stale UI. That needs to be manually killed. Do suggest recommendation for the below lines. Should they be removed. Then the connection...

Beet hackathon demo - Beet if reopened creates new process ids and the old process ids stay the same (Observed on Linux may be windows users wont face this issue) I needed to manually kill them for the app to work.

Use Linux OS and then start the beet app. Observed that the line keeps frequently repeating.