On a weekly basis, customer report issues around the 15 second timeout. This problem manifests as Exceptions and looks like a timeout.

We need to offer a more robust guidenance around Async / Long-Running operations. This guidenance likley takes the form of:

1. Your bot responds very quickly.
2. Do Needed Processing()
3. Send the result to the user as a Async / Proactive message.

There

https://github.com/dart-lang/sdk/blob/master/docs/process/experimental-flags.md#flag-format-for-cli-based-tools

Our docs show:

dart --enable-experiment super-mixins

This format does not work on the VM. It should be:

dart --enable-experiment=super-mixins

The links on the FAQ page in the wiki still point to the old wiki, which seems to be deprecated.

No big thing, but there is a small difference between the code in readme against the cpp file.

Line 37: filter_options(const std::string name, rs2::filter& filter);
in https://github.com/IntelRealSense/librealsense/blob/master/examples/post-processing/rs-post-processing.cpp

filter_options(const std::string name, rs2::process_interface& filter);
https://github.com/IntelRealSens

Currently to create a command it must be a class with the same name like the command + "Command" in the command directory.
e.g.:
Command -> /foobar
Class -> FooBarCommand

But if you want to start a command with a number or an spezialchar in the commandname you can't create this command.

The idea is that you can set a list of classes and in this class you have a property

According to the documentation in ChatMember class

@method string getStatus() (Optional). The member's status in the chat. Can be “creator”, “administrator”, “member”, “left” or “kicked”

getStatus() should return the member's status, but actually there is a conflicting getStatus() in BaseObject that returns the status of the request.

As a workaround, get('status') re