These are chat archives for Nethereum/Nethereum

22nd
Jul 2016
slothbag
@slothbag
Jul 22 2016 11:03
:worried: disable the windows updates service.. then you can start the update when you know you'll be away for a week or two
Juan Blanco
@juanfranblanco
Jul 22 2016 11:39
oh.. the isssue was a failure upgrading to the latest build
it would not install at all
but I managed to install an intermediate build using the iso
it was either that or not have pc as it was giving bsods
if not upgrading.. very nice of them ;)
ok just pushed the fixes for your isse let me know how it goes
slothbag
@slothbag
Jul 22 2016 11:49
legend.. i'll check it out now
slothbag
@slothbag
Jul 22 2016 12:30
hmm, no luck on my first test.. just going to inspect the RPC call json and see whats happening
slothbag
@slothbag
Jul 22 2016 13:11
ok, it looks like Parity expects the header Content-Type: application/json, but Nethereum passed Content-Type: text/plain
is that easy to override?
Juan Blanco
@juanfranblanco
Jul 22 2016 13:14
no it wont that is part of the rpc client
slothbag
@slothbag
Jul 22 2016 13:15
damn
Juan Blanco
@juanfranblanco
Jul 22 2016 13:15
but I think I will just move that class to the Nethereum.JsonRpcClient
as we are wrapping it now
for ipcClient
and keep using the core classes
slothbag
@slothbag
Jul 22 2016 13:18
I could always put in an upstream request to edjCase to make the content-type available to be changed
Juan Blanco
@juanfranblanco
Jul 22 2016 13:36
yes I would like both
:)
mainly don't have the dependency, but also keep the work updated
mainly like a small fork of a class
slothbag
@slothbag
Jul 22 2016 13:40
edjCase/JsonRpc#20
Juan Blanco
@juanfranblanco
Jul 22 2016 13:40
the factory can point to the right one depending of the current version
Juan Blanco
@juanfranblanco
Jul 22 2016 13:57
@slothbag have a go now.. it might be other stuff
if that solves it we can use it as reference for the issue
Nethereum/Nethereum@33c0a0c
Juan Blanco
@juanfranblanco
Jul 22 2016 14:58
ok tested with parity and calling is ok with the media type in the rpc client
Juan Blanco
@juanfranblanco
Jul 22 2016 15:04
updated the issue
Juan Blanco
@juanfranblanco
Jul 22 2016 17:36
@mtbitcoin latest commit adds support for a "simpler" decoding of function input, you will need to iterate through the parameterOuputs and use the result objects
each one will need to be casted correctly to access its value (if required) or I assume to string could be valid
each type has a default value to be converted so bytes32 is byte[], any int / uint is BigInteger
usual stuff