You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
../codon/tmp/cache/go-path/pkg/mod/github.com/pion/[email protected]/track.go:342:33: cannot use mtu (type int) as type uint16 in argument to rtp.NewPacketizer
../codon/tmp/cache/go-path/pkg/mod/github.com/pion/[email protected]/track.go:462:33: cannot use mtu (type int) as type uint16 in argument to rtp.NewPacketizer
It wont work, as the interface in Pion/RTP for NewPacketizer switched and Pion/MediaDevices did not keep up.
1.7.0
func NewPacketizer(mtu int, pt uint8, ssrc uint32, payloader Payloader, sequencer Sequencer, clockRate uint32) Packetizer {
1.7.1 made the mtu argument a uint16 - see this e8906ad
So I needed to drop my version of RTP back to 1.7.0
Changing the argument on an exported function in a minor version release - is that a good thing?
It was kinda funny that it all ran on my local machine (mac go 1.17) but a build on Heroku failed.
The text was updated successfully, but these errors were encountered:
Your environment.
Linux/Mac latest, go 1.16 and go 1.17
Pion/webrtc 3.0.32
Pion/[email protected]
What did you do?
Tried to compile go build -a
github.com/pion/mediadevices/pkg/codec
github.com/pion/mediadevices
github.com/pion/mediadevices
../codon/tmp/cache/go-path/pkg/mod/github.com/pion/[email protected]/track.go:342:33: cannot use mtu (type int) as type uint16 in argument to rtp.NewPacketizer
../codon/tmp/cache/go-path/pkg/mod/github.com/pion/[email protected]/track.go:462:33: cannot use mtu (type int) as type uint16 in argument to rtp.NewPacketizer
It wont work, as the interface in Pion/RTP for NewPacketizer switched and Pion/MediaDevices did not keep up.
1.7.0
func NewPacketizer(mtu int, pt uint8, ssrc uint32, payloader Payloader, sequencer Sequencer, clockRate uint32) Packetizer {
1.7.1 made the mtu argument a uint16 - see this
e8906ad
So I needed to drop my version of RTP back to 1.7.0
Changing the argument on an exported function in a minor version release - is that a good thing?
It was kinda funny that it all ran on my local machine (mac go 1.17) but a build on Heroku failed.
The text was updated successfully, but these errors were encountered: