Skip to content

Releases: iExecBlockchainComputing/iexec-core

v6.4.2

14 Dec 09:44
ecf7a66

Choose a tag to compare

  • #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
8252d86

Choose a tag to compare

  • #465 Fix race condition on replicate attribution.
  • #469 Upgrade Jacoco/Sonarqube reporting and plugins.

v6.4.0

25 Nov 13:41
78d2a30

Choose a tag to compare

  • #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
621135c

Choose a tag to compare

  • #454 Fix concurrent upload requests.
  • #455 Merge abort notifications into a single notification with custom abort cause.

v6.2.0

05 Nov 10:28
69b2ed0

Choose a tag to compare

  • #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
7982717

Choose a tag to compare

  • Fixed Recovering for the Retryable updateReplicateStatus(..) method.

v6.1.5

21 Oct 08:08
1562e09

Choose a tag to compare

  • 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
d32a577

Choose a tag to compare

  • 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
43bc204

Choose a tag to compare

  • Bump iexec-common dependency ([email protected]) featuring socket reuse when sending multiple requests to a blockchain node.

v6.1.2

01 Oct 09:51
b60715f

Choose a tag to compare

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.