Sergei Kozelko

Also same crash from nested spoilers: ``` >! >! one !< two >! three !< !< ```

Hi @Docile-Alligator I started looking into this bug and noticed that spoilers behave differently on the website. You can hide spoiler after viewing it in the app but not on...

Solved the problem by setting handlers myself ```python bot = Bot(token=bot_token) storage = RedisStorage2(host=redis_host) dp = Dispatcher(bot, storage=storage) asyncio.get_event_loop().add_signal_handler(signal.SIGTERM, dp.stop_polling) asyncio.get_event_loop().add_signal_handler(signal.SIGINT, dp.stop_polling) await dp.start_polling() await storage.close() await bot.close() await dp.wait_closed()...

> Also worth noting that if you are on an M1 processor you'll want zulu instead, and in fact zulu may be best as a simple default since it's m1-native...

Please clarify, do you want to detect only direct usages of SDK_INT and CompatHelper in tests, or also cases when tests call methods that use them inside?

That's an interesting idea, but looks impossible - there's no way to mock primitive types or observe field accesses. Actually the best option might be lint check similar to `WrongThreadInterproceduralDetector`....

It was a very simple conclusion - I couldn't find anything in the javadocs or on the internet. Actual reason is best described [here](https://stackoverflow.com/a/49086957/3169238). Accessing a static field is a...

Yes, it's a lot easier, but it won't affect third party libraries. This should be fine as we should not be testing their behavior anyways. Another thing to keep in...

I think I fugured it out. It is easier to reproduce on slow internet because you need to do some actions while comments are loading. Prerequisites (it's complicated, but pretty...

> I thought this was fixed in the last release? At least the problem hasn't been occuring for me anymore. It was #953. There are some similarities but the two...