Video summary
The Hiero SDK Community Call focused primarily on addressing critical updates and deprecations affecting the development ecosystem, with the account balance query deprecation serving as the top priority across all supported platforms. The team discussed the necessary migration from this legacy query to mirror node queries, which requires a consistent approach to handling HTTP retries and timeouts. A significant portion of the meeting was dedicated to finalizing a shared proposal for HTTP transport handling, particularly designed to support environments like Java on Android where standard implementations are unavailable. After receiving minor review suggestions from Hendrick, the team agreed that this design is ready for implementation and will be rolled out in the Java, JavaScript, and Go libraries by the end of the current week.
In addition to the migration efforts, progress was made on integrating TCK tests directly into continuous integration workflows to streamline the testing process across different SDKs. While the C++ SDK requires a longer build time of approximately thirty to forty minutes for these tests, other languages have already been successfully tested against the TCK suite without issues. The team also noted that while some colleagues were previously working on duplication fixes for the Python SDK, further review is needed to ensure all requested changes are properly addressed before merging. This collaborative effort aims to standardize testing procedures and improve the reliability of the SDKs as they evolve.
The meeting concluded with brief updates regarding external events, noting that no specific SDK-related news emerged from the recent HashCon conference, though a security proposal is scheduled for presentation at the upcoming TSC meeting. Attendees were encouraged to review relevant documents in the governance repository if they wish to stay informed about future impacts on the SDKs. With the key technical proposals now aligned and implementation timelines set, the community expressed satisfaction with the progress made and thanked everyone for their participation before ending the call.
Read the full video transcript
Hi Keith. Daniel,
>> should we wait a little bit more for
others to join?
>> Yeah, let's give another minute.
>> Okay.
H.
>> Yeah. 45 minutes.
Okay. Uh, let's get going. Uh, welcome
to the SDK community call. Um,
as always, we'll just talk about all the
latest and greatest things with the Hyro
SDKs.
Um yeah, it seems like our attendance is
quite light today. Um I'm actually just
coming back from travel, so I didn't
have a lot of updates um other than
probably the only things that um are the
major ones on my radar are the um the
account balance query deprecation. And
actually, I think two weeks ago, I went
through and I created issues in all the
repos uh for that deprecation.
Uh so that's to me the number one
priority across all the SDKs. Um I guess
the second priority would be um we still
need to work I need to circle back with
Hendrickk on the design for adding in
the mirror node query um functionality.
Uh so that's another one. Um but yeah
maybe we can go around. Um Deian did you
have any updates from the SDK stuff
you're working on?
>> Yeah it's on the same topic as you
mentioned. So as we migrate away from
the account account balance query to the
mirror node queries we need to have a
consistent handling of the HTTP queries
retries and timeouts across the OSD
case. So uh what you mentioned is we
have a proposal in the cooperation hub.
I'm posting uh a link to it right here
in the chat. So the proposal defines
that the share the shared approach a
shared approach that allows applications
to supply their own HTTP transport. Uh
and this is especially relevant to Java
and on Android where the current
java.net.http
implementation isn't available. So we
implemented this uh from our site and we
passed it away to handle review. He did
a review last week and returned some
suggestions. We're currently addressing
them and uh whenever he's happy with it,
we're going to merge it and start
implementing it on our site. So, and we
we have planned to implement this and
release it on the Java JavaScript and go
live uh libraries, not libraries but
SDKs uh until the end of our week, the
the current week. So this is the most
important from our side.
>> Okay, that that's great. That's amazing
progress. Thank you. Uh so yeah, I guess
the key thing is that Hendrik is um okay
with the design. So it so you said he
reviewed it. Um does he still want
changes or is he okay with it?
>> Uh they're really minor changes
actually. So you can see his comments.
they're already addressed and uh I think
there are minor changes.
>> Okay, that's great.
>> Okay, so let's um yeah, let's finalize
that and then we can um that that can be
the go forward method for all the all
the SDKs.
Um any other updates from your side,
Dian?
>> No. Uh actually uh I have been more
focused on another project and uh um
this is the only main topic that uh I
have planned for this convers for this
meeting.
>> Okay.
All right. Um
Daniel did you have any updates or Noah
any questions or comments? Uh to me on
my side uh in the Python SDK we have a
PR for the duplication for the
duplication of the account balance query
and I think uh the one person working on
it uh we had some changes that we
requested and she has addressed them. So
I think we are going to re review again
and we see whether it's smart.
>> Okay. Which SDK was that that you said?
>> The Python SDK.
>> Python SDK. Okay. Great. Perfect.
>> Just where where where I don't see any
activity. It's these other other
reports. So
>> yeah, I I I think that's something I'll
have to work on this week. U maybe um
pinging some of my colleagues about the
at least the C++ SDK.
Um
okay. Uh any other questions or updates
from anyone?
>> Yeah. Uh I I I have an update. We had uh
something that we have been working on
and uh we were going to present it
tomorrow but I just wanted to give you
heads up. Um
we have uh you know very well we have we
work on the TCK tests TCK implementation
across the SDKs
but uh we were looking in a way on how
we can implement them into the CI.
So we made
we made a separate ripple for the TCK
runner so that we can directly run those
TCK in the CIO workflows.
>> Okay.
>> Yeah.
So in the details uh I can give that in
details but I think we have limited time
today.
But is there any
sorry is there any questions or is there
any blockers from your side?
>> Uh no no it's perfectly fine. It's
perfectly fine and we tested it and it's
working fine. Just just one thing is
that the C++
takes takes time like around 30 to 40
minutes to to build all those TCK runs.
But the rest of the SDKs, we tested it
and uh against the TCK suit, they run
fine.
Okay. Yeah.
Okay. Um I I I'm just actually as we're
talking I'm reading through Deian's
proposal.
Um
uh I didn't have any comments yet.
I I mean DM would you mind just quickly
uh if I share my screen would you mind
quickly just talking through it?
Well this is implemented by dosi
and uh I'm not uh very deep within it as
because as I mentioned I have been moved
to work on the solo parts.
>> Okay. So maybe maybe in the next meeting
we can ask doi to present it.
>> Yeah. And uh you can uh uh I can
schedule you a meeting with Dossi if you
need it or you can a review it and we
can answer any of your questions in in
the chat.
>> Okay. Okay. Sounds good.
>> Perfect.
All right. Did anyone else have any um
issues or comments or things like to
discuss?
>> Uh not on my side. I'm just curious if
there are any any good news from the
hash comp.
>> Um
I don't think we the the topic of SDKs
did not come up
very much that I remember.
Um yeah, so I I don't think there's any
updates for this meeting from ha from
hashcon. Just [clears throat] for those
of you who don't know, hashcon was a a
conference we had last week. Um yeah,
nothing nothing specific for the SDKs I
can think of.
>> I see. Well, I was curious, but thank
you.
>> Um I mean maybe one other topic is that
I I am uh supposed to present the
security proposal at tomorrow's TSC
meeting. Um so yeah, you can find that
in the governance repo if you're
interested.
So that'll maybe just be the Yeah. So
tomorrow at the SDK we'll be probably
presenting stuff that will have an
impact on the SDKs.
>> Okay, with that maybe um I'll give
everyone's time back. So thank you so
much for joining today.
>> Thank you K. Bye.
>> Thank you. Bye
>> bye. Okay.