I followed the documentation to integrate Shibboleth 4.3 to use AzureAD as its proxy / IdP and everything redirects / responds as it should, but in the attribute resolver / claims rules, it is not picking up the attributes in the response back from Azure. I can see in the logs it is going through the individual attributes / claims, which are mapped in the azureClaims.xml / resolver, but is not picking things to do the passthrough down to my servicer provider.
Below are the log entries in shibboleth:
2023-01-30 23:12:10,735 - 10.254.252.105 - INFO [net.shibboleth.idp.saml.saml2.profile.impl.ValidateSAMLAuthentication:511] - Profile Action ValidateSAMLAuthentication: No transcoding rule for Attribute (Name 'http://schemas.microsoft.com/identity/claims/tenantid', NameFormat: 'urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified')
2023-01-30 23:12:10,735 - 10.254.252.105 - INFO [net.shibboleth.idp.saml.saml2.profile.impl.ValidateSAMLAuthentication:511] - Profile Action ValidateSAMLAuthentication: No transcoding rule for Attribute (Name 'http://schemas.microsoft.com/identity/claims/objectidentifier', NameFormat: 'urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified')
2023-01-30 23:12:10,735 - 10.254.252.105 - INFO [net.shibboleth.idp.saml.saml2.profile.impl.ValidateSAMLAuthentication:511] - Profile Action ValidateSAMLAuthentication: No transcoding rule for Attribute (Name 'http://schemas.microsoft.com/identity/claims/displayname', NameFormat: 'urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified')
2023-01-30 23:12:10,735 - 10.254.252.105 - INFO [net.shibboleth.idp.saml.saml2.profile.impl.ValidateSAMLAuthentication:511] - Profile Action ValidateSAMLAuthentication: No transcoding rule for Attribute (Name 'http://schemas.microsoft.com/identity/claims/identityprovider', NameFormat: 'urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified')
2023-01-30 23:12:10,735 - 10.254.252.105 - INFO [net.shibboleth.idp.saml.saml2.profile.impl.ValidateSAMLAuthentication:511] - Profile Action ValidateSAMLAuthentication: No transcoding rule for Attribute (Name 'http://schemas.microsoft.com/claims/authnmethodsreferences', NameFormat: 'urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified')
2023-01-30 23:12:10,735 - 10.254.252.105 - INFO [net.shibboleth.idp.saml.saml2.profile.impl.ValidateSAMLAuthentication:511] - Profile Action ValidateSAMLAuthentication: No transcoding rule for Attribute (Name 'http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname', NameFormat: 'urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified')
2023-01-30 23:12:10,735 - 10.254.252.105 - INFO [net.shibboleth.idp.saml.saml2.profile.impl.ValidateSAMLAuthentication:511] - Profile Action ValidateSAMLAuthentication: No transcoding rule for Attribute (Name 'http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname', NameFormat: 'urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified')
2023-01-30 23:12:10,735 - 10.254.252.105 - INFO [net.shibboleth.idp.saml.saml2.profile.impl.ValidateSAMLAuthentication:511] - Profile Action ValidateSAMLAuthentication: No transcoding rule for Attribute (Name 'http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress', NameFormat: 'urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified')
2023-01-30 23:12:10,735 - 10.254.252.105 - INFO [net.shibboleth.idp.saml.saml2.profile.impl.ValidateSAMLAuthentication:511] - Profile Action ValidateSAMLAuthentication: No transcoding rule for Attribute (Name 'http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name', NameFormat: 'urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified')
2023-01-30 23:12:10,735 - 10.254.252.105 - DEBUG [net.shibboleth.idp.saml.saml2.profile.impl.ValidateSAMLAuthentication:482] - Profile Action ValidateSAMLAuthentication: Incoming SAML Attributes mapped to attribute IDs: []
2023-01-30 23:12:10,735 - 10.254.252.105 - INFO [net.shibboleth.idp.saml.saml2.profile.impl.ValidateSAMLAuthentication:326] - Profile Action ValidateSAMLAuthentication: SAML authentication succeeded for '<my_azure_email>'
2023-01-30 23:12:10,735 - 10.254.252.105 - DEBUG [net.shibboleth.idp.saml.saml2.profile.impl.ValidateSAMLAuthentication:361] - Profile Action ValidateSAMLAuthentication: Added translated AuthnContext Principals: [urn:oasis:names:tc:SAML:2.0:ac:classes:Password]
2023-01-30 23:12:10,735 - 10.254.252.105 - DEBUG [net.shibboleth.idp.saml.saml2.profile.impl.ValidateSAMLAuthentication:300] - Profile Action ValidateSAMLAuthentication: Resetting authentication time to proxied value: 2023-01-31T00:58:45.582Z
2023-01-30 23:12:10,782 - 10.254.252.105 - DEBUG [net.shibboleth.idp.authn.impl.PopulateSubjectCanonicalizationContext:75] - Profile Action PopulateSubjectCanonicalizationContext: Installing 3 canonicalization flows into SubjectCanonicalizationContext
2023-01-30 23:12:10,782 - 10.254.252.105 - INFO [Shibboleth-Audit.SSO:338] - 2023-01-31T04:12:10.782744400Z|urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect|_2a73955fd5a49d06c9567eb52a05cd99|https://sts.windows.net/f42c8e55-f934-4f2c-b0ce-a1e403fd1b9d/|http://shibboleth.net/ns/profiles/saml2/sso/browser|https://<idp_url>/idp|urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST|_60d95c36-51de-45d7-bbcd-25539e822daf||urn:oasis:names:tc:SAML:2.0:ac:classes:Password||<my_azure_email>|_75101b2a-a777-485e-ab76-c816ff9f4301|
2023-01-30 23:12:10,813 - 10.254.252.105 - DEBUG [net.shibboleth.idp.authn.impl.SelectSubjectCanonicalizationFlow:100] - Profile Action SelectSubjectCanonicalizationFlow: Checking canonicalization flow c14n/attribute for applicability...
2023-01-30 23:12:10,813 - 10.254.252.105 - DEBUG [net.shibboleth.idp.authn.impl.SelectSubjectCanonicalizationFlow:83] - Profile Action SelectSubjectCanonicalizationFlow: Selecting canonicalization flow c14n/attribute
2023-01-30 23:12:10,860 - 10.254.252.105 - DEBUG [net.shibboleth.idp.attribute.resolver.impl.AttributeResolverImpl:251] - Attribute Resolver 'ShibbolethAttributeResolver': Initiating attribute resolution with label: c14n/attribute
2023-01-30 23:12:10,860 - 10.254.252.105 - DEBUG [net.shibboleth.idp.attribute.resolver.impl.AttributeResolverImpl:469] - Attribute Resolver 'ShibbolethAttributeResolver': Resolving dependencies for 'passthroughAttributes'
2023-01-30 23:12:10,860 - 10.254.252.105 - DEBUG [net.shibboleth.idp.attribute.resolver.impl.AttributeResolverImpl:478] - Attribute Resolver 'ShibbolethAttributeResolver': Finished resolving dependencies for 'passthroughAttributes'
2023-01-30 23:12:10,860 - 10.254.252.105 - DEBUG [net.shibboleth.idp.attribute.resolver.impl.AttributeResolverImpl:424] - Attribute Resolver 'ShibbolethAttributeResolver': Resolving data connector passthroughAttributes
Eventually, this errors saying nothing can be mapped when building this out. Anything anyone has seen in terms of mapping this out that could have been missed? Have gone through all the mappings a number of times and not seeing where this could have been missed.
Thanks
Nick
Related
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
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".
I have a problem similar to jhipster hot reload failed to register liquibase changelog directory.
This has worked in the past, but I have never been able to get entity creation working correctly: "old" entities (from before the last restart) would fail through a missing table, and "new" entities becuase there was no service (Did not find handler method for [/app/rest/foo3s])
I think I have all the latest versions (generator-jhipster 0.18.1 and <jhipster-loaded.version>0.11</jhipster-loaded.version>. I am running Oracle Java 7 within a Docker container on Debian Testing.
I can build and run the sample app (from /jhipster), but when I try:
yo jhipster:entity foo5
I get:
The entity foo5 is being created.
appPath: src/main/webapp
appPath: src/main/webapp
appPath: src/main/webapp
create src/main/java/petemiller/domain/Foo5.java
create src/main/java/petemiller/repository/Foo5Repository.java
create src/main/java/petemiller/web/rest/Foo5Resource.java
create src/main/webapp/views/foo5s.html
create src/main/webapp/scripts/foo5/router_foo5.js
create src/main/webapp/scripts/foo5/controller_foo5.js
create src/main/webapp/scripts/foo5/service_foo5.js
create src/test/java/petemiller/web/rest/Foo5ResourceTest.java
jhipster#a3c758365d1b:/jhipster$
But there is no db-changelog-00x.xml file generated in the changelog folder, so of course, nothing else works.
Hot Reload seems to be ok, as on startup I get:
[INFO] io.github.jhipster.loaded.JHipsterReloaderAutoConfiguration - Spring Loaded is running, registering hot reloading features
[DEBUG] io.github.jhipster.loaded.reloader.JacksonReloader - Hot reloading Jackson enabled
[DEBUG] io.github.jhipster.loaded.reloader.LiquibaseReloader - Hot reloading JPA & Liquibase enabled
[DEBUG] io.github.jhipster.loaded.reloader.SpringReloader - Hot reloading Spring Beans enabled
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/i18n' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/templates' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/config' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/config/liquibase' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/config/liquibase/changelog' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/mails' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/mails/messages' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller/repository' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller/domain' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller/domain/util' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller/web' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller/web/filter' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller/web/filter/gzip' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller/web/rest' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller/web/rest/dto' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller/web/propertyeditors' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller/config' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller/config/locale' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller/config/apidoc' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller/config/metrics' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller/config/audit' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller/security' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller/aop' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller/aop/logging' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller/service' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller/service/util' will be monitored for changes
[DEBUG] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Directory : 'target/classes/petemiller/async' will be monitored for changes
[INFO] petemiller.Application - Started Application in 19.546 seconds (JVM running for 20.322)
I have done a Maven clean and everything else I can think of, like checking permissions, etc
Suggestions for next steps, anyone?
I am attempting to migrate to Android Studio from Eclipse and have newly installed v0.8.0 (updated to v0.8.2) Android Studio. I cannot get Gradle to finish syncing. I have tried restarting the application and reading various answers everywhere including here on StackOverflow.
I have included a idea.log below, I'm not sure if it is useful. There's more but I couldn't paste the whole thing.
>
2014-08-05 10:40:55,922 [ 94335] INFO - .manage.ContentRootDataService - Importing excluded root 'source_root(C:/Users/XXX/SkyDrive/workspace/BaseGameUtils/build)' for content root 'file://C:/Users/XXX/SkyDrive/workspace/BaseGameUtils' of module 'BaseGameUtils'
2014-08-05 10:40:55,923 [ 94336] INFO - .manage.ContentRootDataService - Importing content root 'C:/Users/XXX/SkyDrive/workspace/google_play_services_froyo/libproject' for module 'libproject'
2014-08-05 10:40:55,923 [ 94336] INFO - .manage.ContentRootDataService - Importing excluded root 'source_root(C:/Users/XXX/SkyDrive/workspace/google_play_services_froyo/libproject/.gradle)' for content root 'file://C:/Users/XXX/SkyDrive/workspace/google_play_services_froyo/libproject' of module 'libproject'
2014-08-05 10:40:55,923 [ 94336] INFO - .manage.ContentRootDataService - Importing excluded root 'source_root(C:/Users/XXX/SkyDrive/workspace/google_play_services_froyo/libproject/build)' for content root 'file://C:/Users/XXX/SkyDrive/workspace/google_play_services_froyo/libproject' of module 'libproject'
2014-08-05 10:40:56,415 [ 94828] INFO - indexing.UnindexedFilesUpdater - Indexable files iterated in 275 ms
2014-08-05 10:40:56,416 [ 94829] INFO - indexing.UnindexedFilesUpdater - Unindexed files update started: 0 files to update
2014-08-05 10:40:56,416 [ 94829] INFO - indexing.UnindexedFilesUpdater - Unindexed files update done in 0 ms
2014-08-05 10:46:40,477 [ 438890] INFO - api.vfs.impl.local.FileWatcher - Change requests:16384, filtered:8176
2014-08-05 10:54:08,569 [ 886982] INFO - api.vfs.impl.local.FileWatcher - Change requests:32768, filtered:16967
2014-08-05 10:54:36,414 [ 914827] INFO - api.vfs.impl.local.FileWatcher - Change requests:49152, filtered:27454
2014-08-05 10:55:08,059 [ 946472] INFO - api.vfs.impl.local.FileWatcher - Change requests:65536, filtered:37942
2014-08-05 10:55:57,283 [ 995696] INFO - api.vfs.impl.local.FileWatcher - Change requests:81920, filtered:48317
2014-08-05 10:56:29,933 [1028346] INFO - api.vfs.impl.local.FileWatcher - Change requests:98304, filtered:58698
2014-08-05 10:57:00,543 [1058956] INFO - api.vfs.impl.local.FileWatcher - Change requests:114688, filtered:69077
2014-08-05 11:00:09,281 [1247694] INFO - api.vfs.impl.local.FileWatcher - Change requests:131072, filtered:78600
2014-08-05 11:01:34,618 [1333031] INFO - api.vfs.impl.local.FileWatcher - Change requests:147456, filtered:88166
2014-08-05 11:02:34,206 [1392619] INFO - api.vfs.impl.local.FileWatcher - Change requests:163840, filtered:98057
2014-08-05 11:03:51,512 [1469925] INFO - api.vfs.impl.local.FileWatcher - Change requests:180224, filtered:107389
2014-08-05 11:05:06,966 [1545379] INFO - api.vfs.impl.local.FileWatcher - Change requests:196608, filtered:116798
2014-08-05 11:06:16,132 [1614545] INFO - api.vfs.impl.local.FileWatcher - Change requests:212992, filtered:126086
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