Hangs when try to UploadSaveBigFilePart about mtproto

[blez]

Hello, sorry for pushing you, just interesting if there are any updates for that issue?

[quenbyako]

Hey @blez! Thanks for asking and ping for inactivity!

I researched this issue, Here is whats happen:

So, TL schema has preeeety few types, including only bytestream and a few types of integers and floats (int32, uint32, int64, int128 and int256). Also it support custom crc codes for defining specific objects with specific decoding. See something wrong?

Yyyyeup, no single type for boolean, arrays, nulltype, etc. So, in TL, bool true and false are objects!

What's the problem? bool type cant implement Object interface in any case in go. We try to fix it with adding specific struct InterfacedObject in near future updates (until new year), which contains only interface{} parameter and Unwrap method, which is getting you native object (bool, slice, ar what you want)

P.S. If you want for faster responses, write us in telegram chat.

[quenbyako]

@blez i'll tried to fix this bug, tests passed out, but in real life result ma be different, so i'll not close this issue yet.

If you have a few time, your feedback will be appreciated

[blez]

No, does not work

panic: got invalid response type: bool

goroutine 1 [running]:
github.com/xelaj/mtproto/telegram.(*Client).UploadSaveBigFilePart(0xc0001ef340, 0x47c3f6d0649b4e9, 0x7f00000000, 0xc000380000, 0x80000, 0x3f5e19a, 0x0, 0x0, 0x0)
	/home/paval/go/pkg/mod/github.com/xelaj/[email protected]/telegram/methods_gen.go:9078 +0x20d
main.main()
exit status 2

[quenbyako]

@blez could you please share your code in playground? Just want to understand in which context client panics

[blez]

@quenbyako
Something like this https://play.golang.org/p/zv6WaheNR_Y
But I'm not sure my code is an issue. Your lib can't "parse" bool response

panic: got invalid response type: bool

goroutine 1 [running]:
github.com/xelaj/mtproto/telegram.(*Client).UploadSaveBigFilePart(0xc0001cf380, 0x6ce07ec8745d7a83, 0x7f00000000, 0xc000300000, 0x80000, 0x3f5e19a, 0x0, 0x0, 0x0)
exit status 2