Tree: 9f76771cbb

acspeed

beta

beta_season3

blackjok3r

dPoW

dPoW2

dev

etomic

fix-mm-build

fix-mnotary_arg

jl777

master

olddPoW

pass-iguana-arg

patch-1

patch-10

patch-11

patch-12

patch-13

patch-14

patch-2

patch-3

patch-4

patch-5

patch-6

patch-7

patch-8

patch-9

quote-mnotaryrun-args

release/v0.1

win-cross

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '9f76771cbb'

${ noResults }

Commit Graph

710 Commits (9f76771cbb7bdf13ae8e068043e63cf474cbf30b)

Author	SHA1	Message	Date
jl777	35794b3367	test	8 years ago
jl777	c17abf407f	fix exit	8 years ago
jl777	b0136f16b8	fix remove file and move file for windows	8 years ago
jl777	82fa535737	fix renaming files in windows to rename instead of delete! The port of rename file was deleting files, which kind of makes creating a bundle difficult! I wrote a mini-test suite to test most of the system specific functions, this can be invoked via command line ../agents/iguana OStests or via compile time -D IGUANA_OSTESTS	8 years ago
jl777	25660ec88e	debug version	8 years ago
jl777	e2e4caebd4	debugging	8 years ago
jl777	8595854a08	jsonQ separated into global and coin specific queues using a mutex to serialize all API requests causes unacceptable latency in some cases. Not serialized can lead to queries into a dataset with unstable state. To fix this, all JSON requests are split into coin specific queues whenever possible and the global queue is only used when the coin can’t be determined from the JSON request. Each coin’s main thread calls the iguana_jsonQ to process that coin’s queue of requests only after all the dataset updates are complete to assure only valid data is returned. Since any previous large latencies were when a specific coin was updating its dataset and the dataset can’t be safely accessed during that time, the delay in processing that coin’s request doesn’t create any additional latency this bug fix is in response to @pbca26 report of “iguana_pkhashbalance: unexpected non-ptr lastpt” which is an error that is most likely caused by accessing the dataset at the wrong time.	8 years ago
jl777	9d2be0b36c	test	8 years ago
jl777	496f812832	active handle gets all coins	8 years ago
jl777	688a6bec70	test	8 years ago
jl777	73262cc1fd	test	8 years ago
jl777	7ac536a474	test	8 years ago
jl777	ce605b72f7	test	8 years ago
jl777	0f28791797	test	8 years ago
jl777	6afe69632b	test	8 years ago
jl777	c1e0af2e8e	test	8 years ago
jl777	a5a64c1de8	test	8 years ago
jl777	536b4d8fb8	test	8 years ago
jl777	9266d1c641	test	8 years ago
jl777	b8ce7833c9	test	8 years ago
jl777	6d704853b8	test	8 years ago
jl777	019acb03b8	test	8 years ago
jl777	fcc65ee3ba	test	8 years ago
jl777	7e0e6f30a5	test	8 years ago
jl777	2e39362dde	test	8 years ago
jl777	681f772843	test	8 years ago
jl777	4b8f4da10c	test	8 years ago
jl777	27fd324636	test	8 years ago
jl777	2f411f119f	test	8 years ago
jl777	295b646282	test	8 years ago
jl777	de97223077	test	8 years ago
jl777	df96e66ac2	test	8 years ago
jl777	b6b6d239c1	test	8 years ago
jl777	6c7f3a6364	fixed https://github.com/jl777/SuperNET/issues/55 problem was “password” field set but “passphrase” wasn’t i put in a workaround to accept either	8 years ago
jl777	b8735b216c	test	8 years ago
jl777	b3ff9b7ec2	test	8 years ago
jl777	25e5941a5e	test	8 years ago
jl777	968d43f9aa	test	8 years ago
jl777	52db5687a9	test	8 years ago
jl777	0949e005c1	test	8 years ago
jl777	dc9211883f	test	8 years ago
jl777	b152d2e085	test	8 years ago
jl777	1221e39ad6	test	8 years ago
jl777	f40199710c	test	8 years ago
jl777	0547baa1f2	test	8 years ago
jl777	9f49ab3c4f	test	9 years ago
jl777	6e63ae4272	test	9 years ago
jl777	ec1dbdf528	test	9 years ago
jl777	8169383164	test	9 years ago
jl777	a2b78dd7cf	test	9 years ago