Unable to monitor data for objects, such as pool objects
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- blockchain
Research direction
Start by tracing the Notify object construction and its listen() entry point, using the objects argument and the pool object IDs in the report as the reproduction case. Check how runtime updates for those objects are received and dispatched. Done means changes to the listed pool objects are captured while the listener is running.
Written by the indexing model from the issue text.
Description
bts = BitShares(node='wss://api.btslebin.com/ws')
n = Notify(
objects=['1.19.61', '1.19.48', '1.19.122', '1.19.62', '1.19.69', '1.19.57','1.19.121'],
on_account=pprint,
blockchain_instance=bts
)
n.listen()
It cannot capture object data about the pool when it is updated at runtime.
- Dominant language
- Python
- Stars
- 162
- Forks
- 164
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bitshares/python-bitshares
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
bitshares/python-bitshares#331 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
bitshares/python-bitshares#320 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
bitshares/python-bitshares#316 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
bitshares/python-bitshares#315 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
bitshares/python-bitshares#308 · 6 comments ·
All issues in bitshares/python-bitshares
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·