Passing an array as a param, getting wrong output

[joeykrug]

So I have two examples here, one that works w/ expected behavior and one that, well, doesn't, and I'm not sure why.

def createMarket(events:arr): return(events[0])
^ is the working example, if called with a number like -37117353667364131058659323780745282444029701754006041568106926382588839136039 it will return -37117353667364131058659323780745282444029701754006041568106926382588839136039.

def createMarket(branch, description:str, alpha, initialLiquidity, tradingFee, events:arr): return(events[0])

^ However, when passed -37117353667364131058659323780745282444029701754006041568106926382588839136039 in the events array ends up returning 191247688059959, when it should be returning -37117353667364131058659323780745282444029701754006041568106926382588839136039

I've made sure the abi description has the second string param set to bytes per usual when dealing w/ strings, so the abi seems correct.

To add to the weirdness --- this works fine in pyethereum, so I don't think it's a serpent issue

[joeykrug]

Also tested with smaller numbers, passing in [-371] for the first element in the array will return 65535 and passing [371] returns 0... very odd

[obscuren]

Could you provide an example? I'd need a minimal test case so I can reproduce the error.

Is this done using the JSON RPC or using the console?

[joeykrug]

Error occurs on both RPC & console
def createMarket(branch, description:str, alpha, initialLiquidity, tradingFee, events:arr): return(events[0])

Calling createMarket and passing in an events array with something like [444] will not return 444

To reproduce:
var address = '0xe95aa1829447058201872db6ae3f04c3785a05b0';

var desc = [{ "name": "createMarket(int256,string,int256,int256,int256,int256[])", "type": "function", "inputs": [{ "name": "branch", "type": "int256" }, { "name": "description", "type": "bytes" }, { "name": "alpha", "type": "int256" }, { "name": "initialLiquidity", "type": "int256" }, { "name": "tradingFee", "type": "int256" }, { "name": "events", "type": "int256[]" }], "outputs": [{ "name": "out", "type": "int256" }] }];

var Contract = web3.eth.contract(desc);

contract = new Contract(address);

contract.call({"from": eth.coinbase}).createMarket(2, "ok", 2, 2, 2, [444]).toNumber();

contract.call({"from": eth.coinbase}).createMarket(2, "ok", 2, 2, 2, [-4443434345]).toNumber();

[tgerring]

Using the above JavaScript on the console, here's what I see:

> contract.call({"from": eth.coinbase}).createMarket(2, "ok", 2, 2, 2, [444]).toNumber();
0

> contract.call({"from": eth.coinbase}).createMarket(2, "ok", 2, 2, 2, [-371]).toNumber();
65535

> contract.call({"from": eth.coinbase}).createMarket(2, "ok", 2, 2, 2, [371]).toNumber();
0

> contract.call({"from": eth.coinbase}).createMarket(2, "ok", 2, 2, 2, [-37117353667364131058659323780745282444029701754006041568106926382588839136039]).toNumber();
44528

> contract.call({"from": eth.coinbase}).createMarket(2, "ok", 2, 2, 2, [-4443434345]).toNumber();
65535

[joeykrug]

Works fine on RPC now, still errors with web3.js calls --- appears to be a web3.js issue, going to dig a bit deeper & end up making a web3.js issue if latest web3.js still errors with this