Im-in | self daemonizing , pure python reverse shell | Security Testing library

Based on your comment above it sounds like you want to return a list of html links not just one. To do that you need that function to build a list and have it return that list. You have a lot going on in create_html, so for illustration purposes I split that function into two: create_html_link_list and create_html_link.

Surprisingly there's key difference in the way that two given projects retrieving connection and data source details.

For instance it's enough for me to put this into maven project properties to point camunda engine to my db (rest left "as-is"):

You must initialize your mContext variable .

For example :

i:im() is a stepwise debugger (like gdb, lldb, or pdb which allow for setting breakpoints, running a program, pausing execution, etc) based on wxWidgets graphical user interface library. MongooseIM is a server - it does not bundle wxWidgets, because it does not have a graphical interface at all.

Due to the nature of the Erlang VM, where a lot of concurrent activities happen side by side, a stepwise debugger is not the best tool for the job. For example, setting a breakpoint in a process which is called via gen_server:call() would make the call time out, leading to a cascade of errors possibly irrelevant to the problem being debugged.

However, the Erlang VM has a builtin debugging facility more suitable to its concurrent nature - a tracing debugger. Tracing does not allow for breakpoints or pausing execution. Instead, it records (a subset of all) the exact events happening in the system and prints/saves them for a posteriori inspection.

This video and transcript provide a brief introduction to tracing on the Erlang VM (in Elixir syntax), while Mats Cronqvist, one of the Erlang veterans, elaborates on the subject in his Erlang User Conference 2014 talk Taking the printf out of printf debugging.

That being said, MongooseIM ships with two interfaces to the tracing mechanism:

• dbg - the standard OTP interface - this SO post shows its basics - be careful if tracing in production, since dbg does not provide any safety mechanisms, so it's possible to overload a production system,

• recon - a way more user friendly and safe for production tracing library, with outstanding documentation. This is probably your best choice when the ease of applicability and the set of features are considered.

You can use tmux display-message with $TMUX_PANE to show whether the current pane is active/inactive:

$ TMUX_STATUS=$( tmux display-message -p -t $TMUX_PANE -F '#F' ) $ [[ "$TMUX_STATUS" == '*' ]] && echo "window is active" window is active

Firstly, $TMUX_PANE is an environment variable exported by tmux which contains tmux's internal pane ID for the given shell.

The display-message -p command prints its output to STDOUT.

The -t $TMUX_PANE argument uses the $TMUX_PANE variable to query a specific pane (the current one, in this instance).

Finally, -f '#F' tells tmux to print only the "Current window flag" (Refer to the tmux man page, which has a list of character sequences under status-left).

AFAIK, these values are:

*, for the currently active window

-, for the previously selected window

And an empty string for windows which are neither active, nor "previous".

You'll need to poll tmux periodically from inside your program to determine whether focus has changed.