-
Hi, I'm getting this error:
```
$ lldb a.out
An error occurred while loading Voltron:
Traceback (most recent call last):
File "/usr/local/lib/python3.5/site-packages/voltron/entry.py", line 43, i…
ghost updated
8 years ago
-
The install.sh uses below code to check the python version used by lldb,
```
PYVER=$(lldb -Qxbo 'script import platform; print(".".join(platform.python_version_tuple()[:2]))'|tail -1)
PYTHON=$(lldb -…
-
In order to support active passive failover we will have to move all state that must survive a promotion event in to a Voltron service that is external to the Ehcache entity itself. The passive entit…
-
I get this - ( on a osx terminal or iterm2 terminal) when on other terminal I've lldb running and stopped at a break point -
$ voltron view stack
Traceback (most recent call last):
File "/usr/local…
-
Just like PEDA does.
-
This bug is blocking us.
**This bug is only in voltron: the passthrough system works fine**
When a client leaves, calls to `IMonitorigProducer.removeNode()` are done first on the client path and th…
-
From server entities, we need to expose management information in the voltron tree, under a specific root.
I.e.: something like this:
```
management / entities / entityType / entityName / capabili…
-
This ticket is an open discussion regarding some improvements we would like to be made regarding the `IStripeMonitoring` interface.
Currently, the monitoring service is using its own [`IStripeMonitor…
-
Updating the `here` global from a thread other than the main GUI/Python REPL thread predictably does not update the view. I'm sure this will be affected by changes for #390.
snare updated
8 years ago
-
Currently, `IMonitoringProducer` accepts data in the form of `Object` instances. This works fine for objects which never leave the address space of the JVM. However, this limits how the data can be …