YouCompleteMe freezes when used with python-mode - vim

When I type self. a popup will automatically select the first one and will never change no matter what input is given. For example, match 1 of 52 is shown.
After <Esc> is used to return to normal mode and enter insert mode again then YouCompleteMe works correctly again. It will show Back at Original and automatically updates with different input.
OS: Kubuntu 13.04
Vim version: 7.4.5
Possibly related plugin: ultisnips
Log:
~/vimConf  ± master ●  2014-02-12 16:37:37,251 - DEBUG - Global extra conf not loaded or no function YcmCorePreload
serving on localhost:
2014-02-12 16:37:38,931 - INFO - Received health request
2014-02-12 16:37:38,935 - INFO - Received event notification
2014-02-12 16:37:38,935 - DEBUG - Event name: BufferVisit
2014-02-12 16:37:39,012 - INFO - Received event notification
2014-02-12 16:37:39,013 - DEBUG - Event name: FileReadyToParse
2014-02-12 16:37:39,013 - INFO - Adding buffer identifiers for file: /home/kamel/vimConf/my_configs.vim
2014-02-12 16:37:39,086 - INFO - Received event notification
2014-02-12 16:37:39,087 - DEBUG - Event name: BufferVisit
2014-02-12 16:37:39,147 - INFO - Received event notification
2014-02-12 16:37:39,148 - DEBUG - Event name: BufferVisit
2014-02-12 16:37:39,149 - INFO - Received event notification
2014-02-12 16:37:39,150 - DEBUG - Event name: FileReadyToParse
2014-02-12 16:37:39,150 - INFO - Adding buffer identifiers for file: /home/kamel/vimConf/my_configs.vim
2014-02-12 16:37:50,482 - INFO - Received event notification
2014-02-12 16:37:50,483 - DEBUG - Event name: BufferVisit
2014-02-12 16:37:50,533 - INFO - Received event notification
2014-02-12 16:37:50,534 - DEBUG - Event name: BufferVisit
2014-02-12 16:37:50,545 - INFO - Received event notification
2014-02-12 16:37:50,545 - DEBUG - Event name: FileReadyToParse
2014-02-12 16:37:50,546 - INFO - Adding buffer identifiers for file: /home/kamel/labola/src/app/mixin/alert.py
2014-02-12 16:37:50,711 - INFO - Received event notification
2014-02-12 16:37:50,712 - DEBUG - Event name: BufferVisit
2014-02-12 16:37:50,748 - INFO - Received event notification
2014-02-12 16:37:50,749 - DEBUG - Event name: BufferVisit
2014-02-12 16:37:50,750 - INFO - Received event notification
2014-02-12 16:37:50,752 - DEBUG - Event name: FileReadyToParse
2014-02-12 16:37:50,752 - INFO - Adding buffer identifiers for file: /home/kamel/labola/src/app/mixin/alert.py
2014-02-12 16:37:57,893 - INFO - Received completion request
2014-02-12 16:37:57,894 - DEBUG - Using filetype completion: False
2014-02-12 16:37:58,055 - INFO - Received completion request
2014-02-12 16:37:58,056 - DEBUG - Using filetype completion: False
2014-02-12 16:37:58,184 - INFO - Received completion request
2014-02-12 16:37:58,184 - DEBUG - Using filetype completion: False
2014-02-12 16:37:58,297 - INFO - Received completion request
2014-02-12 16:37:58,298 - DEBUG - Using filetype completion: False
2014-02-12 16:39:37,853 - INFO - Received event notification
2014-02-12 16:39:37,853 - DEBUG - Event name: FileReadyToParse
2014-02-12 16:39:37,853 - INFO - Adding buffer identifiers for file: /home/kamel/labola/src/app/mixin/alert.py
Screenshot:
Fixed:
It is due to the python-mode autocomplete. When
let g:pymode_rope_complete_on_dot = 0
is set in the .vimrc, it is solved!

It is due to the conflict with python-mode autocomplete.
let g:pymode_rope_complete_on_dot = 0
in the .vimrc, it is solved!
As it is not recommended to use auto completion of pymode and YouComplateMe at the same time, use the following to command to cancel the pymode completion totally.
let g:pymode_rope_completion = 0

Related

Problems pushing images to lightsail containers registry

I'm starting to deploy an app in Lightsail Containers. I've created the service from the console and ran custom images from public repositories.
Now, I'm trying to push my own image from my host using the aws cli, but when I run push-container-image no results are shown in the console. No error, no successful response
Command:
aws lightsail push-container-image --region us-east-1 --service-name container-service-1 --image mystaticwebsite --profile rg --label mystaticwebsite --debug
Debug log:
2021-08-17 17:37:01,238 - MainThread - awscli.clidriver - DEBUG - CLI version: aws-cli/2.2.29 Python/3.8.8 Linux/5.4.0-80-generic exe/x86_64.ubuntu.20
2021-08-17 17:37:01,238 - MainThread - awscli.clidriver - DEBUG - Arguments entered to CLI: ['lightsail', 'push-container-image', '--region', 'us-east-1', '--service-name', 'container-service-1', '--image', 'mystaticwebsite', '--profile', 'rg', '--label', 'mystaticwebsite', '--debug']
2021-08-17 17:37:01,244 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function add_s3 at 0x7f86ddab7ee0>
2021-08-17 17:37:01,244 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function add_ddb at 0x7f86ddc784c0>
2021-08-17 17:37:01,245 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <bound method BasicCommand.add_command of <class 'awscli.customizations.configure.configure.ConfigureCommand'>>
2021-08-17 17:37:01,245 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function change_name at 0x7f86ddc99ee0>
2021-08-17 17:37:01,245 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function change_name at 0x7f86ddca1ee0>
2021-08-17 17:37:01,245 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function alias_opsworks_cm at 0x7f86ddac7940>
2021-08-17 17:37:01,245 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function add_history_commands at 0x7f86ddc41280>
2021-08-17 17:37:01,245 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <bound method BasicCommand.add_command of <class 'awscli.customizations.devcommands.CLIDevCommand'>>
2021-08-17 17:37:01,245 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function add_waiters at 0x7f86ddabfb80>
2021-08-17 17:37:01,245 - MainThread - botocore.loaders - DEBUG - Loading JSON file: /usr/aws-cli/v2/2.2.29/dist/awscli/data/cli.json
2021-08-17 17:37:01,247 - MainThread - botocore.hooks - DEBUG - Event top-level-args-parsed: calling handler <function resolve_types at 0x7f86ddb6bdc0>
2021-08-17 17:37:01,247 - MainThread - botocore.hooks - DEBUG - Event top-level-args-parsed: calling handler <function no_sign_request at 0x7f86ddb71940>
2021-08-17 17:37:01,247 - MainThread - botocore.hooks - DEBUG - Event top-level-args-parsed: calling handler <function resolve_verify_ssl at 0x7f86ddb718b0>
2021-08-17 17:37:01,247 - MainThread - botocore.hooks - DEBUG - Event top-level-args-parsed: calling handler <function resolve_cli_read_timeout at 0x7f86ddb71a60>
2021-08-17 17:37:01,247 - MainThread - botocore.hooks - DEBUG - Event top-level-args-parsed: calling handler <function resolve_cli_connect_timeout at 0x7f86ddb719d0>
2021-08-17 17:37:01,247 - MainThread - botocore.hooks - DEBUG - Event top-level-args-parsed: calling handler <built-in method update of dict object at 0x7f86dd9e0e40>
2021-08-17 17:37:01,248 - MainThread - botocore.session - DEBUG - Setting config variable for profile to 'rg'
2021-08-17 17:37:01,248 - MainThread - botocore.session - DEBUG - Setting config variable for region to 'us-east-1'
2021-08-17 17:37:01,248 - MainThread - awscli.clidriver - DEBUG - CLI version: aws-cli/2.2.29 Python/3.8.8 Linux/5.4.0-80-generic exe/x86_64.ubuntu.20 prompt/off
2021-08-17 17:37:01,248 - MainThread - awscli.clidriver - DEBUG - Arguments entered to CLI: ['lightsail', 'push-container-image', '--region', 'us-east-1', '--service-name', 'container-service-1', '--image', 'mystaticwebsite', '--profile', 'rg', '--label', 'mystaticwebsite', '--debug']
2021-08-17 17:37:01,248 - MainThread - botocore.hooks - DEBUG - Event session-initialized: calling handler <function add_timestamp_parser at 0x7f86ddab9550>
2021-08-17 17:37:01,248 - MainThread - botocore.hooks - DEBUG - Event session-initialized: calling handler <function register_uri_param_handler at 0x7f86de4d6e50>
2021-08-17 17:37:01,248 - MainThread - botocore.hooks - DEBUG - Event session-initialized: calling handler <function add_binary_formatter at 0x7f86dda280d0>
2021-08-17 17:37:01,248 - MainThread - botocore.hooks - DEBUG - Event session-initialized: calling handler <function no_pager_handler at 0x7f86de552280>
2021-08-17 17:37:01,248 - MainThread - botocore.hooks - DEBUG - Event session-initialized: calling handler <function inject_assume_role_provider_cache at 0x7f86de4be940>
2021-08-17 17:37:01,249 - MainThread - botocore.utils - DEBUG - IMDS ENDPOINT: http://169.254.169.254/
2021-08-17 17:37:01,251 - MainThread - botocore.credentials - DEBUG - Skipping environment variable credential check because profile name was explicitly set.
2021-08-17 17:37:01,251 - MainThread - botocore.hooks - DEBUG - Event session-initialized: calling handler <function attach_history_handler at 0x7f86ddc41160>
2021-08-17 17:37:01,251 - MainThread - botocore.hooks - DEBUG - Event session-initialized: calling handler <function inject_json_file_cache at 0x7f86ddc763a0>
2021-08-17 17:37:01,259 - MainThread - botocore.loaders - DEBUG - Loading JSON file: /usr/aws-cli/v2/2.2.29/dist/botocore/data/lightsail/2016-11-28/service-2.json
2021-08-17 17:37:01,282 - MainThread - botocore.hooks - DEBUG - Event building-command-table.lightsail: calling handler <function inject_commands at 0x7f86dda28ee0>
2021-08-17 17:37:01,282 - MainThread - botocore.hooks - DEBUG - Event building-command-table.lightsail: calling handler <function add_waiters at 0x7f86ddabfb80>
2021-08-17 17:37:01,288 - MainThread - botocore.hooks - DEBUG - Event building-command-table.lightsail_push-container-image: calling handler <function add_waiters at 0x7f86ddabfb80>
2021-08-17 17:37:01,289 - MainThread - botocore.hooks - DEBUG - Event load-cli-arg.custom.push-container-image.service-name: calling handler <awscli.paramfile.URIArgumentHandler object at 0x7f86dd1a1c10>
2021-08-17 17:37:01,289 - MainThread - botocore.hooks - DEBUG - Event process-cli-arg.custom.push-container-image: calling handler <awscli.argprocess.ParamShorthandParser object at 0x7f86de498160>
2021-08-17 17:37:01,289 - MainThread - botocore.hooks - DEBUG - Event load-cli-arg.custom.push-container-image.image: calling handler <awscli.paramfile.URIArgumentHandler object at 0x7f86dd1a1c10>
2021-08-17 17:37:01,289 - MainThread - botocore.hooks - DEBUG - Event process-cli-arg.custom.push-container-image: calling handler <awscli.argprocess.ParamShorthandParser object at 0x7f86de498160>
2021-08-17 17:37:01,289 - MainThread - botocore.hooks - DEBUG - Event load-cli-arg.custom.push-container-image.label: calling handler <awscli.paramfile.URIArgumentHandler object at 0x7f86dd1a1c10>
2021-08-17 17:37:01,289 - MainThread - botocore.hooks - DEBUG - Event process-cli-arg.custom.push-container-image: calling handler <awscli.argprocess.ParamShorthandParser object at 0x7f86de498160>
Any idea on why this is not working?
Regards!
I had this exact issue on Ubuntu 20.04 just now. After running strace on the command, it turned out that this was due to an EACCES (Permission Denied) error when running the lightsailctl plugin which wasn't making it to the console output.
11067 execve("/usr/local/bin/lightsailctl", ["lightsailctl", "--plugin", "--input-stdin"], 0x557d454e91c0 /* 68 vars */) = -1 EACCES (Permission denied)
I resolved the issue by making the lightsailctl plugin executable like so:
chmod +x /usr/local/bin/lightsailctl
I was also facing the same issue, but somehow I figured and able to push image on lightsail and able to deploy the container:-
aws lightsail push-container-image --region ap-west-1 --service-name invent --label inventory --image invent_app:latest
I have this step in Github Action:
run: |
curl "https://s3.us-west-2.amazonaws.com/lightsailctl/latest/linux-arm64/lightsailctl" -o "/usr/local/bin/lightsailctl"
sudo chmod +x /usr/local/bin/lightsailctl
The push command returns nothing, even with debug option, So I added lightsailctl --version, and got an error
/usr/local/bin/lightsailctl: cannot execute binary file: Exec format error
turn out I use the wrong binary, should be amd64 instead arm64

Zookeeper Leader Auto Failover

We are using spark standalone cluster 3 zookeepers in HA mode.I am seeing this issue in zookeeper.log.
Exception causing close of session 0x0 due to java.io.IOException: Len error 1195725856
Closed socket connection for client /10.23...... (no session established for client)
Zookeeper leader is getting auto failed over from one server to another server and hence followed by this, spark master is getting auto failed over
Also Some clients are getting continually disconnected/reconnected with this error.
How to fix
Full Log:
[myid:3] - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn#354] - Exception causing close of session 0x0 due to java.io.IOException: Len error 1195725856
[myid:3] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn#1001] - Closed socket connection for client /10....... (no session established for client)
[myid:3] - ERROR [LearnerHandler-/159.1.......:LearnerHandler#562] - Unexpected exception causing shutdown while sock still open
[myid:3] - WARN [LearnerHandler-/159.1......:LearnerHandler#575] - ******* GOODBYE /159.1..... ********
[myid:3] - INFO [WorkerReceiver[myid=3]:FastLeaderElection#542] - Notification: 1 (n.leader), 0x29000000ed (n.zxid), 0xa (n.round), LOOKING (n.state), 1 (n.sid), 0x29 (n.peerEPoch), LEADING (my state)
[myid:3] - INFO [LearnerHandler-/159........:LearnerHandler#263] - Follower sid: 1 : info : org.apache.zookeeper.server.quorum.QuorumPeer$QuorumServer#e144103
[myid:3] - INFO [LearnerHandler-/159.......LearnerHandler#318] - Synchronizing with Follower sid: 1 maxCommittedLog=0x29000000ed minCommittedLog=0x2800000007 peerLastZxid=0x29000000ed
[myid:3] - INFO [LearnerHandler-/159.......:LearnerHandler#395] - Sending DIFF

Titan error when one of the connected Cassandra nodes comes down

We have Titan setup with Cassandra as it's storage.backend. We have a cluster of 3 Cassandra nodes. We are seeing the following error when one of the Cassandra nodes fail/shutdown.
This is the error that gets logged. Any help on this will be really appreciated.
INFO CountingConnectionPoolMonitor:194 - AddHost: 10.76.54.7
ERROR ConnectionPoolMBeanManager:74 - com.netflix.MonitoredResources:type=ASTYANAX,name=KeyspaceTitanConnectionPool,ServiceType=connectionpool
ERROR ConnectionPoolMBeanManager:74 - com.netflix.MonitoredResources:type=ASTYANAX,name=ClusterTitanConnectionPool,ServiceType=connectionpool
INFO GraphDatabaseConfiguration:1518 - Generated unique-instance-id=3217005b14357-titan-m21e
INFO ConnectionPoolMBeanManager:53 - Registering mbean: com.netflix.MonitoredResources:type=ASTYANAX,name=ClusterTitanConnectionPool,ServiceType=connectionpool
INFO CountingConnectionPoolMonitor:194 - AddHost: 10.76.54.44
INFO CountingConnectionPoolMonitor:194 - AddHost: 10.76.54.57
INFO CountingConnectionPoolMonitor:194 - AddHost: 10.76.54.7
INFO ConnectionPoolMBeanManager:53 - Registering mbean: com.netflix.MonitoredResources:type=ASTYANAX,name=KeyspaceTitanConnectionPool,ServiceType=connectionpool
INFO CountingConnectionPoolMonitor:194 - AddHost: 10.76.54.44
INFO CountingConnectionPoolMonitor:194 - AddHost: 10.76.54.57
INFO CountingConnectionPoolMonitor:194 - AddHost: 10.76.54.7
INFO Backend:459 - Configuring index [search]
INFO plugins:151 - [Donald Ritter] loaded [], sites []
INFO ElasticSearchIndex:354 - Configured remote host: 10.76.54.15 : 9300
INFO ElasticSearchIndex:354 - Configured remote host: 10.76.54.24 : 9300
INFO ElasticSearchIndex:354 - Configured remote host: 10.77.170.171 : 9300
INFO Backend:176 - Initiated backend operations thread pool of size 16
INFO KCVSLog:730 - Loaded unidentified ReadMarker start time 2016-02-16T23:45:27.539Z into com.thinkaurelius.titan.diskstorage.log.kcvs.KCVSLog$MessagePuller#49f59d47

How to execute gremlin query with mogwai

Im trying to query a titan db 0.5.4 via mogwai, but when I run the following script i get the error: rexpro.exceptions.RexProScriptException: transaction is not open
and I found the same question here
P.S there is no tag for mogwai
script:
#!/usr/bin/env python3
from mogwai.connection import execute_query, setup
con = setup('127.0.0.1', graph_name="bio4j", username="re", password="re")
results = execute_query("2 * a",params={"a":2}, connection= con)
print(results)
results = execute_query("bio4j.E",params={}, connection= con)
print(results)
log:
$ ./bin/rexster.sh --start
0 [main] INFO com.tinkerpop.rexster.Application - .:Welcome to Rexster:.
93 [main] INFO com.tinkerpop.rexster.server.RexsterProperties - Using [/Users/Phoenix/Dropbox/Graph4Bio/Titan/rexhome/config/rexster.xml] as configuration source.
102 [main] INFO com.tinkerpop.rexster.Application - Rexster is watching [/Users/Phoenix/Dropbox/Graph4Bio/Titan/rexhome/config/rexster.xml] for change.
730 [main] INFO com.thinkaurelius.titan.graphdb.configuration.GraphDatabaseConfiguration - Generated unique-instance-id=0a69045d1736-AngryMac-local1
804 [main] INFO com.thinkaurelius.titan.diskstorage.Backend - Initiated backend operations thread pool of size 8
905 [main] INFO com.thinkaurelius.titan.diskstorage.log.kcvs.KCVSLog - Loaded unidentified ReadMarker start time Timepoint[1455128079919000 μs] into com.thinkaurelius.titan.diskstorage.log.kcvs.KCVSLog$MessagePuller#302c971f
908 [main] INFO com.tinkerpop.rexster.RexsterApplicationGraph - Graph [bio4j] - configured with allowable namespace [tp:gremlin]
932 [main] INFO com.tinkerpop.rexster.config.GraphConfigurationContainer - Graph bio4j - titangraph[berkeleyje:/Users/Phoenix/Dropbox/Graph4Bio/Bio4j/bio4j] loaded
939 [main] INFO com.tinkerpop.rexster.server.metrics.HttpReporterConfig - Configured HTTP Metric Reporter.
941 [main] INFO com.tinkerpop.rexster.server.metrics.ConsoleReporterConfig - Configured Console Metric Reporter.
2058 [main] INFO com.tinkerpop.rexster.server.HttpRexsterServer - HTTP/REST thread pool configuration: kernal[4 / 4] worker[8 / 8]
2060 [main] INFO com.tinkerpop.rexster.server.HttpRexsterServer - Using org.glassfish.grizzly.strategies.LeaderFollowerNIOStrategy IOStrategy for HTTP/REST.
2160 [main] INFO com.tinkerpop.rexster.server.HttpRexsterServer - Rexster Server running on: [http://localhost:8182]
2160 [main] INFO com.tinkerpop.rexster.server.RexProRexsterServer - Using org.glassfish.grizzly.strategies.LeaderFollowerNIOStrategy IOStrategy for RexPro.
2160 [main] INFO com.tinkerpop.rexster.server.RexProRexsterServer - RexPro thread pool configuration: kernal[4 / 4] worker[8 / 8]
2162 [main] INFO com.tinkerpop.rexster.server.RexProRexsterServer - Rexster configured with [DefaultSecurity].
2163 [main] INFO com.tinkerpop.rexster.server.RexProRexsterServer - RexPro Server bound to [0.0.0.0:8184]
2177 [main] INFO com.tinkerpop.rexster.server.ShutdownManager - Bound shutdown socket to /127.0.0.1:8183. Starting listener thread for shutdown requests.
152568 [Grizzly(2) SelectorRunner] INFO com.tinkerpop.rexster.protocol.EngineController - ScriptEngineManager has factory for: ECMAScript
152568 [Grizzly(2) SelectorRunner] INFO com.tinkerpop.rexster.protocol.EngineController - ScriptEngineManager has factory for: gremlin-groovy
152568 [Grizzly(2) SelectorRunner] INFO com.tinkerpop.rexster.protocol.EngineController - Registered ScriptEngine for: gremlin-groovy
152569 [Grizzly(2) SelectorRunner] INFO com.tinkerpop.rexster.protocol.EngineHolder - Initializing gremlin-groovy engine with additional imports.
153259 [Grizzly(2) SelectorRunner] INFO com.tinkerpop.rexster.protocol.EngineHolder - ScriptEngine initializing with a custom script
154074 [Grizzly(2) SelectorRunner] INFO com.tinkerpop.rexster.protocol.EngineController - ScriptEngineManager has factory for: Groovy
154076 [Grizzly(2) SelectorRunner] INFO com.tinkerpop.rexster.protocol.session.RexProSessions - RexPro Session created: a2b416ce-75ea-4ecb-9835-b287162c90cb
154354 [Grizzly(4)] INFO com.tinkerpop.rexster.protocol.session.RexProSessions - Try to destroy RexPro Session: a2b416ce-75ea-4ecb-9835-b287162c90cb
154355 [Grizzly(4)] INFO com.tinkerpop.rexster.protocol.session.RexProSessions - RexPro Session destroyed or doesn't otherwise exist: a2b416ce-75ea-4ecb-9835-b287162c90cb
154356 [Grizzly(5)] INFO com.tinkerpop.rexster.protocol.session.RexProSessions - RexPro Session created: 5b8a669f-615d-4f84-9d1e-2d10624347f0
154525 [Grizzly(7)] WARN com.tinkerpop.rexster.protocol.server.ScriptServer - Could not process script [bio4j.E] for language [groovy] on session [[B#6634722f] and request [[B#68f38099]
154527 [Grizzly(8)] INFO com.tinkerpop.rexster.protocol.session.RexProSessions - Try to destroy RexPro Session: 5b8a669f-615d-4f84-9d1e-2d10624347f0
154527 [Grizzly(8)] INFO com.tinkerpop.rexster.protocol.session.RexProSessions - RexPro Session destroyed or doesn't otherwise exist: 5b8a669f-615d-4f84-9d1e-2d10624347f0
154529 [Grizzly(1)] INFO com.tinkerpop.rexster.protocol.session.RexProSessions - Try to destroy RexPro Session: 00000000-0000-0000-0000-000000000000
154529 [Grizzly(1)] INFO com.tinkerpop.rexster.protocol.session.RexProSessions - RexPro Session destroyed or doesn't otherwise exist: 00000000-0000-0000-0000-000000000000
Maintainer of mogwai here.
What version of mogwai are you using? in 0.7.7 there is no return value for setup method and the connection object should not be passed around. In fact when you call setup it creates a connection pool (a synchronous rexpro connection pool since there was no concurrency option specified). So in general, just call setup once for the life of your app and you can use execute query without any references.
Also this message in particular stands out:
154525 [Grizzly(7)] WARN com.tinkerpop.rexster.protocol.server.ScriptServer - Could not process script [bio4j.E] for language [groovy] on session [[B#6634722f] and request [[B#68f38099]
Is your graph configured with a graph name of "bio4j"? The default titan graph name is "graph" and the default graph object name mogwai uses is "g". If you have a graph name of "bio4j" you wouldn't reference this directly, you'd use the graph object name associated to the transaction. You can think of a graph-name as a database name in a SQL database, and the graph object being the transactional reference to said database. This is configured in the xml configuration file when starting titan. Particularly:
<graphs>
<graph>
<graph-name>graph</graph-name>
....
</graph>
</graphs>
So assuming you changed that from "graph" to "bio4j" and left the default graph_obj_name in the setup function as "g", then your query should read "g.E".

Removing Standard Output Messages from Console Window

I'm using vstest to execute tests on local.
"C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow\vstest.console.exe\" "C:\Debug\Solution.dll /Tests:VerifyTest1,VerifyTest2 /Logger:trx"
And over console i receive output something like this -
Passed VerifyTest1
Failed VerifyTest2
Standard Output Messages:
TestContext Messages:
1/29/2016 21:50:00 - START - START : [VerifyTest2]
1/29/2016 21:50:00 - INFO - Operating System - Microsoft Windows 10 Enterprise
1/29/2016 21:50:00 - INFO - Test Environment - Test1
1/29/2016 21:50:00 - INFO - Test Environment - Test1
1/29/2016 21:50:00 - INFO - File updated
1/29/2016 21:50:02 - INFO - Login Complete! via UI API's
1/29/2016 21:50:03 - INFO - eb481527-49f6-49bc-a9ca-9ccf4e10d12a submitted successfully.
1/29/2016 21:50:11 - PASS - Return created through UI
1/29/2016 21:50:11 - INFO - Checking Process launched or NOT
1/29/2016 21:50:11 - INFO - Process: My.CommonUIFramework.Shell is launched
1/29/2016 21:50:11 - INFO - Terminating the Process: My.CommonUIFramework.Shell
1/29/2016 21:50:11 - INFO - Checking Process launched or NOT
1/29/2016 21:50:11 - INFO - Process: My.Xion.DataMigration.UI is NOT launched
1/29/2016 21:50:12 - INFO - Launched the Application : My.CommonUIFramework.Shell
1/29/2016 21:50:12 - INFO - Checking Process launched or NOT
Now, i don't want the debug trace with all the info when a test fails on Console. I just want passed or failed result on Console. Is there a way to do that. I know that i can see the result on trx file but i just wanted to know is there a way to suppress the debug trace or Standard Output Messages on Console.
You May Want to Disable your trace Logs. You can do it thru multiple channels. Try as mentioned in here based on ur VSTS & .Net version. https://msdn.microsoft.com/en-us/library/jj159363(v=vs.120).aspx
0 is the setting for disabling traces.
Using MSTest instead of VSTest solved the purpose of my problem.

Resources