Releases: iExecBlockchainComputing/iexec-core
Releases · iExecBlockchainComputing/iexec-core
v6.4.2
14 Dec 09:44
Compare
Sorry, something went wrong.
No results found
#475 Fix task status deadlock. Chances to reach RUNNING task status for given states of replicates are now increased.
v6.4.1
30 Nov 15:13
Compare
Sorry, something went wrong.
No results found
#465 Fix race condition on replicate attribution.
#469 Upgrade Jacoco/Sonarqube reporting and plugins.
v6.4.0
25 Nov 13:41
Compare
Sorry, something went wrong.
No results found
#457 #461 Consume blockchain configuration on iexec-blockchain-adapter-api & expose its URL for iexec-worker
#464 Upgrade artifacts publishing
#463 Enable local import of iexec-common
#459 Upgrade to Gradle 6.8.3
#462 Upgrade to JUnit5
v6.3.0
16 Nov 11:18
Compare
Sorry, something went wrong.
No results found
#454 Fix concurrent upload requests.
#455 Merge abort notifications into a single notification with custom abort cause.
v6.2.0
05 Nov 10:28
Compare
Sorry, something went wrong.
No results found
#418 Send transactions over a dedicated blockchain adapter micro-service.
#420 Reply gracefully to the worker when a status is already reported.
#427 Abort a TEE task when all alive workers did fail to run it.
#436 Moved task state machine to a dedicated service.
#440 Removed useless internal task statuses belonging to the result upload request stage.
v6.1.6
21 Oct 08:28
Compare
Sorry, something went wrong.
No results found
Fixed Recovering for the Retryable updateReplicateStatus(..) method.
v6.1.5
21 Oct 08:08
Compare
Sorry, something went wrong.
No results found
Added checks before locally upgrading to the INITIALIZED status
Removed 2-blocks waiting time before supplying a new replicate
v6.1.4
14 Oct 14:50
Compare
Sorry, something went wrong.
No results found
Fixed OptimisticLockingFailureException happening when 2 detectors detect the same change at the same time, leading to race updates on a same task
v6.1.3
05 Oct 12:15
Compare
Sorry, something went wrong.
No results found
Bump iexec-common dependency ([email protected] ) featuring socket reuse when sending multiple requests to a blockchain node.
v6.1.2
01 Oct 09:51
Compare
Sorry, something went wrong.
No results found
Bugfix for #425 - Replay fromBlockNumber now lives in a dedicated configuration:
A configuration document did store two different states. Updates on different states at the same time might lead to race conditions when saving to database. Now each state has its own document to avoid race conditions when saving.