Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Bolt V2 should always support byte arrays

See original GitHub issue

using version 1.7.0, also tried 1.6.x.

Error: Bolt V2 should always support byte arrays
    at Packer.disableByteArrays (/Users/dom/Desktop/bitwars-api/node_modules/neo4j-driver/lib/v1/internal/packstream-v2.js:116:13)
    at InitializationObserver.onCompleted (/Users/dom/Desktop/bitwars-api/node_modules/neo4j-driver/lib/v1/internal/connection.js:559:50)
    at Connection._handleMessage (/Users/dom/Desktop/bitwars-api/node_modules/neo4j-driver/lib/v1/internal/connection.js:336:35)
    at Dechunker._this2._dechunker.onmessage (/Users/dom/Desktop/bitwars-api/node_modules/neo4j-driver/lib/v1/internal/connection.js:204:22)
    at Dechunker._onHeader (/Users/dom/Desktop/bitwars-api/node_modules/neo4j-driver/lib/v1/internal/chunking.js:254:14)
    at Dechunker.AWAITING_CHUNK (/Users/dom/Desktop/bitwars-api/node_modules/neo4j-driver/lib/v1/internal/chunking.js:207:21)
    at Dechunker.write (/Users/dom/Desktop/bitwars-api/node_modules/neo4j-driver/lib/v1/internal/chunking.js:265:28)
    at NodeChannel._this2._ch.onmessage (/Users/dom/Desktop/bitwars-api/node_modules/neo4j-driver/lib/v1/internal/connection.js:199:40)
    at TLSSocket.<anonymous> (/Users/dom/Desktop/bitwars-api/node_modules/neo4j-driver/lib/v1/internal/node/node-channel.js:331:16)
    at emitOne (events.js:115:13)
    at TLSSocket.emit (events.js:210:7)
    at addChunk (_stream_readable.js:266:12)
    at readableAddChunk (_stream_readable.js:253:11)
    at TLSSocket.Readable.push (_stream_readable.js:211:10)
    at TLSWrap.onread (net.js:585:20)

Issue Analytics

State:
Created 5 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

2reactions

ryanmeadorcommented, Jan 17, 2019

I am experiencing the same issue using driver 1.7.2 with Neo4j Community Edition 3.0.8 (on Heroku). The issue went away when I downgraded the driver back to 1.1.0 (I didn’t try any intermediate versions; that’s just what I was using previously). I don’t have time right now to reduce my project to a reproducer, but I’m happy to collect logs or try any other troubleshooting steps you can suggest. Thanks!

0reactions

alexcittadinicommented, May 25, 2019

I am experiencing the same issue using driver 1.7.2 with Neo4j Community Edition 3.0.8 (on Heroku). The issue went away when I downgraded the driver back to 1.1.0 (I didn’t try any intermediate versions; that’s just what I was using previously). I don’t have time right now to reduce my project to a reproducer, but I’m happy to collect logs or try any other troubleshooting steps you can suggest. Thanks!

Thanks mate, you saved me big time. I tried down grading to 1.4.0 and that didn’t work, but 1.1.0 worked for me. No idea what caused it

Top Results From Across the Web

BOLT-LMM v2.4 User Manual - Alkes Group

The BOLT-LMM association testing algorithm supports computation of mixed model association statistics at an arbitrary number of imputed SNPs (with real-valued “ ...

Consider supporting byte arrays in ... - GitHub

Consider: var json = "[1, 2, 3, 128]"; Deserializing this as a byte[] currently fails since the byte[] converter expects a base-64 encoded ......

Concepts - Apache Storm

By default, tuples can contain integers, longs, shorts, bytes, strings, doubles, floats, booleans, and byte arrays. You can also define your own serializers ......

Performance Tips | Photon Engine

By default byte[] data is deserialized to new byte[x] . We must set LoadBalancingPeer.UseByteArraySlicePoolForEvents = true to enable the non-alloc conduit.

Python Bytes, Bytearray - w3resource

Bytes, Bytearray. Python supports a range of types to store sequences. There are six sequence types: strings, byte sequences (bytes objects) ...