/Users/travis/build/ray-project/ray/python/ray/node.py:533: DeprecationWarning: Redis.hmset() is deprecated. Use Redis.hset() instead.
    redis_client.hmset("webui", {"url": self._webui_url})
  /Users/travis/build/ray-project/ray/python/ray/worker.py:358: DeprecationWarning: Redis.hmset() is deprecated. Use Redis.hset() instead.
    "run_on_other_drivers": str(run_on_other_drivers),
  

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

I assume you can do "run something" in the drozer console

# from example module @ https://github.com/mwrlabs/drozer/wiki/Writing-a-Module

module repository enable /path/to/your/repository # I got this working

module install ex.random

# failed attempts
run ex.random.GetInteger
run drozer.modules.Module.ex.random.GetInteger

dz> help drozer.modules.Module
*** No help on drozer.

I'm sorry if I missed this functionality, but CLI version hasn't it for sure (I saw the related code only in generate_code_examples.py). I guess it will be very useful to eliminate copy-paste phase, especially for large models.

Of course, piping is a solution, but not for development in Jupyter Notebook, for example.

Right now, a target name can contain space, comma, /, etc, so it would be a good idea to limit it to alphanumeric + - and _

For example:

diff --git a/BUILD b/BUILD
index 0ad0a46..c71bab2 100644
--- a/BUILD
+++ b/BUILD
@@ -52,3 +52,6 @@ files(
   name = 'pants_pex',
   source = 'pants.pex',
 )
+
+target(
+  name = '123/456')


$ ./pants list :
//:123/456

the documentation stills detail the compilation steps for installation on desktop, which shouldn't be always necessary now, since wheels are provided.
https://pyjnius.readthedocs.io/en/latest/installation.html

while it's good that it details them for those who want to install from source, most people would benefit from a simpler installation process, like the one in README.md.

Expecting: "${gadgetDir}/vscode-cpptools/debugAdapters/bin/OpenDebugAD7.exe"
Actual: "${gadgetDir}/vscode-cpptools/debugAdapters/OpenDebugAD7" -- which is a bash script.

The link for the coala-bears usage further navigates to this which has no information about how to use coala. One can do either of the following:

• Update the link so that it navigates to the coala documentation.

• Add usage information in the README.rst file located here.

Instructions aren't sufficient to deploy as it misses a lot of steps. Actual deployment instructions are mostly the same as https://cloud.google.com/python/django/appengine

(See post on stackoverflow and Issue #67)
As stated in the REAMDE JayDeBeApi implements Python DB-API v2.0. Basically you have to call the execute on a cursor and pass the insert statement.

But you are right. Some more guidance for novic