Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
transaction streaming has breaking change in 10.1.0
See original GitHub issueDescribe the bug Streaming transactions no longer works using sdk 10.1.0
What version are you on?
10.1.0
To Reproduce
horizon
.transactions()
.forAccount(pubkeyA)
.stream({
onmessage: recv,
onerror: (e) => {
db.consoleLog('SYSTEM-XLM', `STREAM ERROR: ${e}`);
},
});
In 10.1.0, I get about 7 transactions for address GBIYTJUA6W25EFRVQJE3LNQ6VONUQ4E4TMCK7W5OBDFUQVJUHCZMOBTV, and then the process exits.
Expected behavior
In 10.0.1 I correctly get about 120, and the process continues to listen for new transactions.
Additional context
If this is a breaking change for 10.1.0, some instructions on how to port it would be very much appreciated.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I can confirm that #780 fixes the issue I reported. Thank you.
This is almost certainly related to #772… I will look into this asap. Thank you for the report!