-
```
I found a bug in AbstractAbcDeserializer.as as below.
doubles[++i] = _byteStream.readDouble();
This code should be read in little-endian order.
But the byteStream.endian was big-endian.
```
Ori…
-
```
I found a bug in AbstractAbcDeserializer.as as below.
doubles[++i] = _byteStream.readDouble();
This code should be read in little-endian order.
But the byteStream.endian was big-endian.
```
Ori…
-
```
I found a bug in AbstractAbcDeserializer.as as below.
doubles[++i] = _byteStream.readDouble();
This code should be read in little-endian order.
But the byteStream.endian was big-endian.
```
Ori…
-
After extending examples/voltkv in the open source voltdb distribution to use strings as the primary key and double types as the value I attempted to store a value as follows:
```
crypto:start(), ap…
-
At some point this needs to be tested with multiple connected Doubles and users. It should work in theory, which means in practice it won't.
-
-
There are quite a few doubles in foaf:Organization. The URI is different but the labels are the same, or almost the same.
The labels are *exactly* the same: the code should check if an organization …
-
```
I found a bug in AbstractAbcDeserializer.as as below.
doubles[++i] = _byteStream.readDouble();
This code should be read in little-endian order.
But the byteStream.endian was big-endian.
```
Ori…
-
```
I found a bug in AbstractAbcDeserializer.as as below.
doubles[++i] = _byteStream.readDouble();
This code should be read in little-endian order.
But the byteStream.endian was big-endian.
```
Ori…
-
```
I found a bug in AbstractAbcDeserializer.as as below.
doubles[++i] = _byteStream.readDouble();
This code should be read in little-endian order.
But the byteStream.endian was big-endian.
```
Ori…