Michael Bouclas

Results 18 comments of Michael Bouclas

same here, 5.3 broke a lot of packages for me...

I second that. Running composer install right after the first pull is a nightmare in some projects as additional steps might be needed before running this command is safe. Maybe...

true, but i have stumbled upon 2-3 cases where this will not cut it as the "pre-configuration" is a bit more complicated. Sure, you could hack a bunch of scripts...

The same code though works on 4.0x. In any case, it's a cypher query run like so ``` try { res = await this.neo.cypher(query, { ...issue, ...{uuid} }); } catch...

This throws a different error, `Neo4j only supports a subset of Cypher types for storage as singleton or array properties`. It would require quite a rewrite on our part anyways...

After some digging around it looks that it's a driver issue. Same code and payload react differently the moment you change the DB version. So for now it seems upgrading...

I want it to revert to it's previous state, which was not black. Before opening the camera, there was a white background and other stuff on the screen which the...

Having the same issue. Publishes are hit or miss. Sometimes they finish, most times they don't. Here's what a failed attempt looks like ![image](https://user-images.githubusercontent.com/642742/232839786-2c9859be-1384-48ef-9bdb-bb37387bae48.png)

> [email protected] test m:\Work\testing\node-imagemagick-native > tap test/test.js test/test.async.js test/test.streams.js test/test.trim.js not ok test/test.js ..................................... 0/1 Command: "c:\Program Files (x86)\nodejs\node.exe test.js" TAP version 13 not ok 1 test/test.js --- exit: 1...

cheers On 3/10/15, Elad Efrat [email protected] wrote: > Okay, I'll look into it when I get a chance. It's possible that this is due > to a new node. >...