Nikita
Nikita
Try using the '-d3' argument when compiling and repeat this error again. In theory, it should display information about where this happened (not exactly).
If I were you, I would close the issue if the issue has been resolved. This is confusing when looking at unclosed issues to find a similar situation. Thank you!
I always support any innovations. But I think this is a strange proposal. What's the point of these two callbacks? I have never encountered such a problem and neither have...
> Rassynchrony -> desync > > upd: you've mentioned 1.1.0.2669 as a version you tested it on, but the latest is 1.2.0.2670. I checked and on version **1.2.0.2670** this bug...
> Does this also work without Fixes component as well? Yes, it works the same way without the Fixes component.
I think this is a bit different. `AddServerRule`, `SetServerRule`, `RemoveServerRule` affect the information that is used in `Query`, although they also have limitations, e.g. you can't do anything with rules...