Please do a new release

Question

Please do a new release

Closed this issue 7 months ago · 10 comments

sloba-byte commented 7 months ago

Hi,

I see some fixes have been integrated - however latest release is from Avg 4 2023, a long time ago.

@adshao is it possible you do a new tag for a release?

Thanks!

Answer 1 · 2024-03-09T16:46:24.000Z

Hey @adshao - yeah please release new version as there was an issue I got using the futures client

it's updated in the Github but the release 2.4.5 has an issue.

Answer 2 · 2024-03-10T10:42:48.000Z

Hi, v3.0.0 has been released, let me know if there is any problem.

Answer 3 · 2024-03-10T11:23:48.000Z

Thank you, @adshao, for such a quick release!

Answer 4 · 2024-03-11T15:10:15.000Z

Hey @adshao - could you please let me know how to upgrade to new version? As it seems you did a tag 3.0.1 but GO says there is no release for version 3.

Answer 5 · 2024-03-16T10:35:12.000Z

Hey @adshao - could you please let me know how to upgrade to new version? As it seems you did a tag 3.0.1 but GO says there is no release for version 3.

Hi, could you try to use v2.5.0 instead?

Answer 6 · 2024-03-16T10:40:21.000Z

Hey @adshao - v2.5.0 works for me, thank you!

BTW, do you have an example of how to handle the futures user data WSS? I can see the code, but not sure how to handle it? I tried to do myself but got the issues with connection retry and multiple instances of the connection after the retries. If you can share your best solution, I would be much appreciated.

Thanks in advance!

Answer 7 · 2024-03-16T15:16:55.000Z

Hey @adshao - v2.5.0 works for me, thank you!

BTW, do you have an example of how to handle the futures user data WSS? I can see the code, but not sure how to handle it? I tried to do myself but got the issues with connection retry and multiple instances of the connection after the retries. If you can share your best solution, I would be much appreciated.

Thanks in advance!

Hi, you could refer to the example of spot and change the package to futures.

Answer 8 · 2024-03-16T15:22:18.000Z

Hi @adshao - thank you for your reply!

Does it handle the WSS reconnection?
How to keep alive the listen key? I can see there is a method, but it seems I need a separate goroutine to keep this triggering every 30 mins. Can you please confirm this?

Answer 9 · 2024-03-17T03:00:55.000Z

Hi @adshao - thank you for your reply!

Does it handle the WSS reconnection?

How to keep alive the listen key? I can see there is a method, but it seems I need a separate goroutine to keep this triggering every 30 mins. Can you please confirm this?

Hi @dlisovsky ,

Yes, I think you should put it in an infinite loop to reconnect automatically.
Yes, this project is just a SDK for binance API, we don't handle the specific logic for each API. For your question, I think it's correct to add a goroutine to refresh the listen key. If you have any problem about binance API, it would be better to discuss it in the telegram group of binance developers.

Answer 10 · 2024-03-19T09:53:38.000Z

Hi @adshao - yeah I understand it's an SKD and you did a great job!
I thought you may have an example with user data WSS that has all the code to keep the listen key alive and also manages the retries, just in case. That would be much appreciated.