Christine Draper

The cross-origin error only happens when I am debugging and loading _SpecRunner.html into the browser. For Firefox, it only happens if my baseURL is outside of the spec directory, e.g....

fwiw, here's a simple example. It succeeds when run through Grunt. It gives a syntax error with Mozilla (although the test does succeed). And it fails with Chrome due to...

+1. Although I figured out the workaround of adding vendor: [ '.grunt/grunt-contrib-jasmine/es5-shim.js'] based on #73

The error suggests it has found an existing AMI and is trying to update it (which isn't supported/implemented)

It looks somewhat similar to: https://github.com/chef/chef-provisioning-aws/issues/260 which was caused by a node having an old format driver url stored in its attributes. In your case, it might be that an...

For the record, why-run mode doesnt work when creating or updating machines, at least on vagrant or aws. Looks like it actually tries to do the convergence. It does seem...

The main concern is not exposing internal host info. Its reassuring that you're not aware of IDPs using the information. Either of the approaches you suggest would work for us,...

I have encountered the same problem when running using an in-memory database. However, the composite index seems to work (with some caveats #126) when running against a remote database. (

I am able to :install into 3.2.3, but it doesnt appear as a plugin (because it doesnt implement the Plugin interface). I did: ``` :import org.apache.tinkerpop.gremlin.orientdb.OrientGraphFactory ``` and I seem...

@maggiolo00 will the 3.0 release be compatible with OrientDB 2.2 server?