Please visit the contributing guidelines to learn more on how to translate Qoa's documentation into more languages.

Tons of thank you to everyone for your help and support! ❤️

We would like to be able to make interface and method ‘documentation’ comments available to templates.

For example, we would like to use a method comment to provide hints to a logging decorator about what and how to log specific params and results (avoiding monolithic log output, hiding sensitive data etc)

The documentary comments are readily available in the ast and so could be copied to

pytim.GITIM() might crash because of a segfault in scipy.spatial.Delaunay() on some platforms.

This is likely related to scipy/scipy#9751 and/or scipy/scipy#9858

As a quick workaround, install pytetgen, which is used preferentially by GITIM, if found.

Document why this interfaces implementation is different from others which are already out there.

Implementations to consider for comparing to:

• abc
• zope.interface
• PEP 245 (rejected)
• PEP 544 (draft)

For statically configured sensor setups, it makes sense to have slinkwatch running as a notification-only tool that only logs active set state changes instead of modifying the interface configuration and restarting Suricata. Operations engineers could then use this information to investigate loss of visibility events individually.

• Add custom guides on the artboard
• Make sure there is empty pasteboard space between the artboard and the toolbox
• Drag anything from the toolbx
  While dragging the new element, the artboard gets de-selected and all custom guides are hidden

There are a couple of things that need to be changed in the docs, based on the latest commits on https://github.com/tongoose/TypeScript-Babel-Starter

• User model imports / exports
• console.log the created user
• verify everything works