qortal

Commit Graph

Author	SHA1	Message	Date
CalDescent	ef838627c4	Stop asking for hashes from a peer if one fails. This fixes the request looping that occurs on when a peer is unable to serve files.	3 years ago
CalDescent	b8aaf14cdc	Introduced ArbitraryDataFileRequestThread to allow for multiple concurrent file requests. This is likely a short term solution (to allow existing code to be repurposed) until replaced with a task-based approach, as this will allow for a much greater number of threads.	3 years ago
CalDescent	2740543abf	Added "async" and "attempts" parameters to GET /arbitrary/{service}/{name}* endpoints. async = fail immediately with 404 if missing, and request in the background attempts = the number of times to request the data (synchronous mode only for now)	3 years ago
CalDescent	3c526db52e	Fixed bug in build manager which would prevent future builds until the core was restarted.	3 years ago
CalDescent	cfe0414d96	Small rework of invalidUnconfirmedTransactions to specify the expiry time instead of the time added. This allows TIMESTAMP_TOO_OLD transactions to be tracked for a shorter time (10 minutes) than the other invalid transactions (60 minutes). Should reduce network traffic and db load around the time that transactions are expiring, as there is a lag before they are noticed and removed from each node. Due to the variance, it could cause other peers to request them again after deleting. They are now ignored for 10 minutes to avoid request spam.	3 years ago
CalDescent	08e06ba11a	Fixed bugs preventing invalidUnconfirmedTransactions from working as intended.	3 years ago
CalDescent	8c03164ea5	Don't add expired transactions to invalidUnconfirmedTransactions, as there is no need to keep track of these.	3 years ago
CalDescent	0fe2f226bc	Added invalidUnconfirmedTransactions map An incoming invalid unconfirmed transaction will be added to this map if its timestamp is more than 30 minutes old. This should allow enough time and opportunities for it to be imported and included in a block (allowing for re-orgs which could switch its status from invalid to valid). Once added, it will be removed after an hour to allow for another chance to be requested from any peers that still have it. If invalid again, it's added back to the map for another hour. This fixes a 24 hour long loop, where invalid transactions are requested over and over from peers that have already imported them. It could be improved further by periodically removing invalid unconfirmed transactions from the database, but this will be a higher risk. The results of this feature should be less network traffic, and less blockchain locks (which should ultimately increase the responsiveness of the synchronizer).	3 years ago
CalDescent	55b5702158	Invalidate last low weight block signature whenever the previous block data changes.	3 years ago
CalDescent	a4cbbb3868	Moved block minter sleep to later in the process, otherwise it can remain there for longer than expected.	3 years ago
CalDescent	816b01c1fc	Fixed issue in rebase	3 years ago
CalDescent	483e7549f8	Revert "Moved log from INFO to DEBUG, as now the synchronizer is on its own thread it can occur more often than before." This reverts commit `e2e87766fa`.	3 years ago
CalDescent	60d71863dc	Allow 3 seconds for the synchronizer to obtain a blockchain lock, to reduce missed attempts.	3 years ago
CalDescent	170244e679	More work on higher weight chain detection in the block minter. Added 30 second timeout, so that any errors should self correct.	3 years ago
CalDescent	472e1da792	Added debug level logging in higherWeightChainExists() for better visibility.	3 years ago
CalDescent	cbf03d58c8	Made synchronizer method public as it is now also used by the block minter.	3 years ago
CalDescent	ba41d84af9	Initial attempt to avoid an unnecessary block submission if one of our peers already has a higher weight chain.	3 years ago
CalDescent	98831a9449	Break out of the various loops in the cleanup manager if the thread is stopping.	3 years ago
CalDescent	9692539a3f	Don't include fee in balance calculation (it looks like it could be double counting at the moment).	3 years ago
CalDescent	76df332b57	Check for null IP address before notifying of an external IP update.	3 years ago
CalDescent	c6405340bc	minAccountLevelForBlockSubmissions reduced from 6 to 5	3 years ago
CalDescent	775e3c065e	Invalidate ElectrumX transactions cache when switching accounts.	3 years ago
CalDescent	8937b3ec86	Don't allow duplicate transaction in the incoming transactions queue. This should reduce database load slightly, as it won't have to check the same transaction multiple times in each batch.	3 years ago
CalDescent	3fbb86fded	Added indexes, to make looking up name transactions by name around 5x faster.	3 years ago
CalDescent	0cf2f7f254	Missing import from last commit	3 years ago
CalDescent	9e571b87e8	Yet another rewrite of fetchAllTransactionsInvolvingName() - this time over 1000x faster since it doesn't involve joining the Transactions table.	3 years ago
CalDescent	23bafb6233	Removed unused methods	3 years ago
CalDescent	6dec65c5d9	Rewrite of fetchAllTransactionsInvolvingName() to avoid having to load all name transactions into memory.	3 years ago
CalDescent	4e59eb8958	Added unit test to simulate the false association between previous a UPDATE_NAME transaction, and the emoji name with a blank reducedName.	3 years ago
CalDescent	756d5e685a	Added naming tests for blank new names	3 years ago
CalDescent	f52530b848	More thorough approach to fetchAllTransactionsInvolvingName(), to fix an issue found in unit testing.	3 years ago
CalDescent	c2bf37b878	Added transactionV5Timestamp featureTrigger to unit tests	3 years ago
CalDescent	98a2dd04b8	Fixed bug caused by improper handling of UPDATE_NAME transactions, similar to commit `d16663f`.	3 years ago
CalDescent	694ea689c8	Synchronize the loop and break out of it before fetching arbitrary data files. Hopeful fix for ConcurrentModificationException, and maybe a potential deadlock.	3 years ago
CalDescent	618aaaf243	Removed logs used for debugging only	3 years ago
CalDescent	9224ffbf73	Cache transaction list for 2 minutes, and synchronize, to prevent the balance and transactions APIs both requesting at once. This ensures that only a single round of requests (per coin) is used for the wallettransactions and balance APIs. It also speeds up loading on subsequent requests. The 2 minute cache isn't much longer than the foreign block times, so shouldn't cause values to be too out of date.	3 years ago
CalDescent	892612c084	Calculate wallet balances from the transactions (ElectrumX) rather than using bitcoinj. Hopeful fix for incorrect balances in wallets with large numbers of transactions. At the very least, this gives us control of the code that calculates the balance.	3 years ago
CalDescent	077165b807	Modified fetchArbitraryDataFileList() to support requesting only the missing hashes, but it is not yet used. Once GetArbitraryDataFileListMessage is rolled out to the network we can uncomment this code. Needs testnet testing prior to that.	3 years ago
CalDescent	7994fc6407	Rework of onNetworkGetArbitraryDataFileListMessage() to support custom hashes to be optionally supplied. Also simplified the existing logic, to make the code more readable.	3 years ago
CalDescent	d98df3e47d	Added support for file hashes to optionally be included in GetArbitraryDataFileListMessage. Needs testing on testnet, as the majority of nodes need to update before the hashes can be used.	3 years ago
CalDescent	1064b1a08b	Removed duplicate metadata file checks.	3 years ago
CalDescent	0b7a7ed0f1	Added some more debug logging relating to file responses.	3 years ago
CalDescent	114b1aac76	Added arbitrary data file manager thread, which will ensure that all file list responses are tried until we receive the files. Previously we would only try the first response and then discard the others due to being duplicates. They are now added to a queue and retried by the dedicated thread (up to the 60 second timeout).	3 years ago
CalDescent	6d06953a0e	Increased RELAY_REQUEST_MAX_HOPS from 3 to 4, in an attempt to reach more peers.	3 years ago
CalDescent	0430fc8a47	Give up immediately after a synchronization if we are shutting down the synchronizer	3 years ago
CalDescent	7338f5f985	Attempt to acquire a blockchain lock (for up to 5 seconds) before shutting down the repository. This should fix conflicts caused by the synchronizer and controller now being on separate threads. It may also reduce the chances of the database corrupting on shutdown, but this remains to be seen.	3 years ago
CalDescent	640bcdd504	Shutdown/interrupt the synchronizer as early as possible	3 years ago
CalDescent	c9d5d996e5	Increased accuracy of the block weights in the synchronizer logs, as the extra precision is now needed for debugging.	3 years ago
CalDescent	710befec0c	Increased ARBITRARY_RELAY_TIMEOUT from 30 to 60 seconds, so that relay peers remember their mappings for longer.	3 years ago
CalDescent	8ccb158241	Reduce log spam when in DEBUG mode.	3 years ago

... 4 5 6 7 8 ...

2480 Commits (9fdb7c977f7dd570937c15befd50e7e7efa2bda9) All Branches Search

2480 Commits (9fdb7c977f7dd570937c15befd50e7e7efa2bda9)

All Branches