Skip to content

Releases: rdkcentral/Thunder

Wait for the WebSocket to be open (i.s.o. the TCP connection)

31 Jul 15:37
@pwielders pwielders
R4.3.3
950c4ea
Compare
Choose a tag to compare
Wait for the WebSocket to be open (i.s.o. the TCP connection) Pre-release
Pre-release

Now the SmartLinkType<> waits till the WebSocket included the upgrade exchange before reporting that it is open.

In the past the Open would already return if the TCP connection was established, however, the socket is than not yet fully open, it first has to request the upgrade. If, before the socket was fully opened, the first messages where to be exchanged, they got lost.

Assets 2

QuickFix

25 Jul 13:08
@pwielders pwielders
R4.3.2
be42eba
Compare
Choose a tag to compare
QuickFix Latest
Latest

In R2, the LinkType<> template to communicate with Thunder over JSONRPC, used a maxium timeout of 100ms to wait for the channel to open before to continue. This was set to 0ms as the assumption was that the SmartLinkType would be used for this purpose and the SmartLinkType waits for the Opened Event before submitting notifications/invokes.

However some application still use theLinkType<> and expect the Channel to be open after the construction (trickey, not advised but it is code out there). Restored the waittime now to at least 1S.

Assets 2

Bug fixes on R2

26 Jul 17:53
@MFransen69 MFransen69
R2-v1.7
b5e7127
Compare
Choose a tag to compare
Bug fixes on R2 Pre-release
Pre-release

Minor bug fixes on R2-v1.6
Introduction of Unavailable state

Assets 2

Bug fixes on R2

24 May 06:26
@pwielders pwielders
R2-v1.6
8478dc9
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Bug fixes on R2 Pre-release
Pre-release

Major focus of this release is verbosity. Try to report as much as possible if exceptional shutdowns occure.

Assets 2

Minor bug fixes on R2

23 Mar 16:09
@MFransen69 MFransen69
R2-v1.5
b5900cf
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Minor bug fixes on R2

Minor bug fixes on R2-v1.4

Assets 2

Minor bug fixes on R2

05 Mar 13:44
@MFransen69 MFransen69
R2-v1.4
32cbc79
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Minor bug fixes on R2

Minor bug fixes on R2-1.3

Assets 2

Minor bug fixes on R2

02 Feb 13:40
@pwielders pwielders
R2-v1.3
071c003
Compare
Choose a tag to compare
Minor bug fixes on R2

See commit log for changes.

Assets 2

Fixes on R2

18 Jan 09:20
@pwielders pwielders
R2-v1.2
ce0d0e5
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Fixes on R2 Pre-release
Pre-release

This is a maintenance release that has no new functionality but has several fixes found during integration testing at a customer site.

Assets 2

Bug fixes

16 Dec 15:01
@pwielders pwielders
R2-v1.1
6b71595
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Bug fixes Pre-release
Pre-release

Bug fixes and minor changes.

  1. JSON parsing now supports larger messages than 64K
  2. JSON Variant parsing now allows for
  3. Process names spawned by WPEProcess will be associated with a subname equal to the callsign.
Assets 2

R2 v1.0- Release

10 Dec 08:51
@Divya-563 Divya-563
R2-v1.0
22a04bc
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
R2 v1.0- Release

Functional Testing of R2 was performed and no Blockers were reported.
Only outstanding issue is related to Netflix playback which is being investigated.
Here is the summary of our testing :

Summary:
Successfully launched and validated Thunder along with various plugins

Playready protected content and Cobalt playback was successful

Test Scope:

Focussed testing on various plugins available in Thunder including Cobalt and Netflix.

Stability testing of Thunder was out of scope.

Please find the attached detailed test report

Assets 3