v2.1.2
This release slightly extends an interface of mtglib.Logger, adds a new option AllowFallbackOnUnknownDC and relevant configuration option allow-fallback-on-unknown-dc.
This option defines how mtg should behave if client requests unknown DC. Each time when client establishes a connection to a proxy, it sends a number of DC that it wants to connect to. This DC defines a number of the cluster: media, messages, channels and so on. But sometimes clients may issue a number mtg knows nothing about. It may be due to the bugs (#208) or because new cluster is present but a version of mtg is old enough to know about it. Telegram works in a way that each cluster may server any request (latency is an issue though). So, if you want a media, you can ask for that from messages cluster and vice versa. You'll get a response but with poor performance.
This option defines if mtg should reject unknowns (default behaviour for running with config and inverse for simple-run) or choose any known DC for that.
What's Changed
- Fallback to another DC if given is unknown by @9seconds in #210
- Bump docker build timeout to 20 minutes by @9seconds in #211
- Fix windows build by @9seconds in #213
- Add new BindJSON method to a logger by @9seconds in #214
- Update Actions permissions by @9seconds in #215
- Add configuration option allow-fallback-on-unknown-dc by @9seconds in #216
- golangci-lint 1.42.1 by @9seconds in #217
Full Changelog: v2.1.1...v2.1.2
