Skip to content

Releases: aleph-im/pyaleph

0.5.4

05 Sep 15:23
b858351
Compare
Choose a tag to compare

This new release of the aleph.im Core Channel Node application significantly solve an important error on instances and implements support for more blockchains and tokens.

What's Changed

  • Solve issue with instance messages and requirements empty field by @nesitor in #599
  • Created new version 0.5.4 by @nesitor in #600

Full Changelog: v0.5.3...0.5.4

Upgrade guide

Make sure that your node is running v0.5.1 or later. If that is not the case already, follow the upgrade guide here.

From v0.5.1, simply bump the version of these services:

  • On the docker-compose.yml file, in the pyaleph and pyaleph-api services must use alephim/pyaleph-node:0.5.4.

⚠️ we removed the v in the version number

Then, restart your node: docker-compose pull && docker-compose down && docker-compose up -d.

v0.5.3

26 Aug 12:58
38f8fa7
Compare
Choose a tag to compare
v0.5.3 Pre-release
Pre-release

This new release of the aleph.im Core Channel Node application significantly improves the stability of the nodes solving some bugs and errors.

Key Highlights of the Release:

  1. Core Functionality: Resolved several issues related to core functionalities such as axios headers, dependency management, metric handling, error handling, aggregate filters, sorting, chain writing, and upload.

  2. Data Handling: Addressed problems with data handling, including initial message sync on private CCN, Flow pricing calculations, and volume handling.

What's Changed

  • docs metric name correction by @hoh in #553
  • Improve error handling by @hoh in #550
  • Fix aggregate filter by keys by @aliel in #556
  • Fix sortBy/sortOrder on Message/Post queries by @philogicae in #555
  • Fix: Chain writer failed due to TypeError by @hoh in #549
  • Add CodeCov for code coverage follow up by @hoh in #558
  • Add param to only return the value of an aggregate by its key by @aliel in #557
  • Allow developers to use nix-shell to get started by @hoh in #554
  • Fix upload by @aliel in #559
  • Fix Pydantic alias issue by @aliel in #560
  • Add initial messages sync on private CCN by @nesitor in #561
  • Solve initial sync script issue by @nesitor in #562
  • Solve Flow pricing calculation issues by @nesitor in #566
  • Fix: Upload Endpoints by @1yam in #565
  • doc(README): we don't use mongodb anymore by @Psycojoker in #567
  • doc: add instructions to run tests by @Psycojoker in #569
  • a lot of fixes and improvement for running local tests using nix-shell because it was just broken by @Psycojoker in #570
  • feat: upgrade aleph-message from 0.4.2 to 0.4.8 and fix all mypy issues. by @Psycojoker in #578
  • doc(nix): the database is named aleph for the user aleph by @Psycojoker in #577
  • Fix: nix-shell did not use latest stable channel by @hoh in #579
  • Fix: Wrong usage of node_hash by @1yam in #583
  • Fix: Handle no volume found instead of error 500 by @1yam in #581
  • Use latest Docker RC version by @nesitor in #586
  • Allow to connect postgresql in a passwordless mode and with a unix socket by @Psycojoker in #584
  • doc(docker): fix typo in path by @Psycojoker in #587
  • doc: remove references to MongoDB by @Psycojoker in #585
  • doc: update docker documentation and script to match reality by @Psycojoker in #588
  • Fix: check if requirements exist on message by @1yam in #591
  • Fix: nix-shell raised 'pop_var_context' by @hoh in #594
  • Fix: Update aleph-message package version by @nesitor in #597
  • Create version 0.5.3 by @nesitor in #598

New Contributors

Full Changelog: v0.5.2...v0.5.3

v0.5.3-rc2

30 Jul 10:47
Compare
Choose a tag to compare
v0.5.3-rc2 Pre-release
Pre-release

This new release of the aleph.im Core Channel Node application significantly improves the stability of the nodes solving some bugs and errors.

Key Highlights of the Release:

  1. Core Functionality: Resolved several issues related to core functionalities such as axios headers, dependency management, metric handling, error handling, aggregate filters, sorting, chain writing, and upload.

  2. Data Handling: Addressed problems with data handling, including initial message sync on private CCN, Flow pricing calculations, and volume handling.

What's Changed

  • Implement workaround for axios not passing Content-Length headers in multipart fields by @MHHukiewitz in #537
  • Fix: Dependency aleph-message used an rc, stable available by @hoh in #546
  • Fix: All node metrics were returned by default by @hoh in #547
  • docs metric name correction by @hoh in #553
  • Improve error handling by @hoh in #550
  • Fix aggregate filter by keys by @aliel in #556
  • Fix sortBy/sortOrder on Message/Post queries by @philogicae in #555
  • Fix: Chain writer failed due to TypeError by @hoh in #549
  • Add CodeCov for code coverage follow up by @hoh in #558
  • Add param to only return the value of an aggregate by its key by @aliel in #557
  • Allow developers to use nix-shell to get started by @hoh in #554
  • Fix upload by @aliel in #559
  • Fix Pydantic alias issue by @aliel in #560
  • Add initial messages sync on private CCN by @nesitor in #561
  • Solve initial sync script issue by @nesitor in #562
  • Solve Flow pricing calculation issues by @nesitor in #566
  • Fix: Upload Endpoints by @1yam in #565
  • doc(README): we don't use mongodb anymore by @Psycojoker in #567
  • doc: add instructions to run tests by @Psycojoker in #569
  • a lot of fixes and improvement for running local tests using nix-shell because it was just broken by @Psycojoker in #570
  • feat: upgrade aleph-message from 0.4.2 to 0.4.8 and fix all mypy issues. by @Psycojoker in #578
  • doc(nix): the database is named aleph for the user aleph by @Psycojoker in #577
  • Fix: nix-shell did not use latest stable channel by @hoh in #579
  • Fix: Wrong usage of node_hash by @1yam in #583

New Contributors

Full Changelog: v0.5.2-rc3...v0.5.3-rc2

v0.5.2

24 Jan 17:15
@hoh hoh
cad2d9c
Compare
Choose a tag to compare

This new release of the aleph.im Core Channel Node application significantly improves the performance of the nodes, allowing them to scale the ever increasing usage of the network.

Key Highlights of the Release:

  1. Event-Based Processing: A major shift in this update is the transition to event-based processing for both transactions (TX) and message handling. This change is pivotal in optimizing the flow and handling of information within the network, ensuring more responsive and reliable operations.

  2. Asynchronous Garbage Collector: The deletion of temporary files and files deleted by FORGET messages is now asynchronous and does not block other processes anymore.

  3. New Metrics API endpoint for CRN & CNN: Obtain the metrics of a specific node using /api/v0/core/{node_id}/metrics or /api/v0/compute/{node_id}/metrics from the API of a Core Channel Node.

What's Changed

Full Changelog: v0.5.1...v0.5.2

Upgrade guide

Make sure that your node is running v0.5.1 or later. If that is not the case already, follow the upgrade guide here.

From v0.5.1, simply bump the version of these services:

  • The pyaleph and pyaleph-api services must use alephim/pyaleph-node:0.5.2.

⚠️ we removed the v in the version number

Then, restart your node: docker-compose pull && docker-compose down && docker-compose up -d.

v0.5.2-rc4

24 Jan 16:01
@hoh hoh
cad2d9c
Compare
Choose a tag to compare
v0.5.2-rc4 Pre-release
Pre-release

What's Changed

  • Implement workaround for axios not passing Content-Length headers in multipart fields by @MHHukiewitz in #537
  • Fix: Dependency aleph-message used an rc, stable available by @hoh in #546
  • Fix: All node metrics were returned by default by @hoh in #547

Full Changelog: v0.5.2-rc3...v0.5.2-rc4

v0.5.2-rc3

14 Dec 17:02
@hoh hoh
Compare
Choose a tag to compare
v0.5.2-rc3 Pre-release
Pre-release

What's Changed

  • Fix: Conflict between multiple database migrations by @hoh in #531
  • Filter and sort objects (messages, posts, etc) by confirmation block ID #445 by @MHHukiewitz in #446

Full Changelog: v0.5.2-rc2...v0.5.2-rc3

Upgrade guide

Make sure that your node is running v0.5.1 or later. If that is not the case already, follow the upgrade guide here.

From v0.5.1, simply bump the version of these services:

  • The pyaleph and pyaleph-api services must use alephim/pyaleph-node:0.5.2-rc3.

⚠️ we removed the v in the version number

Then, restart your node: docker-compose pull && docker-compose down && docker-compose up -d.

0.5.1-2

29 Nov 14:32
@hoh hoh
Compare
Choose a tag to compare
0.5.1-2 Pre-release
Pre-release

What's Changed

New Contributors

Full Changelog: v0.5.1...0.5.1-2

v0.5.2-rc2

05 Nov 14:42
cc801d5
Compare
Choose a tag to compare
v0.5.2-rc2 Pre-release
Pre-release

Fixes and revert to Kubo 0.15.0.

What's Changed

Full Changelog: v0.5.2-rc1...v0.5.2-rc2

v0.5.2-rc1

03 Nov 11:58
46fb1b6
Compare
Choose a tag to compare
v0.5.2-rc1 Pre-release
Pre-release

This release tackles several latency issues in the message processing pipeline. It improves the latency of the message and tx processing pipeline when processing new messages/txs after being idle. It also makes the garbage collection process asynchronous as deleting large files in the pipeline directly caused severe latency issues.

Breaking changes

  • Files are now given a grace period after being forgotten, 24 hours by default.

What's Changed

Full Changelog: v0.5.1...v0.5.2-rc1

v0.5.1

20 Oct 13:19
eba0edd
Compare
Choose a tag to compare

New features

  • Full support for instance messages.
  • Balance checks on instances and persistent VMs.
  • Authenticated file upload: the file upload endpoint can now process a file and the corresponding aleph message at the same time.
  • Users can now query the creation/modification date of an aggregate using the new with_info query parameter.

Main bug fixes

  • Fixed the infinite RPC loop encountered by node operators caused by unexpected publishers on the aleph.im smart contract.
  • The stability issues encountered on websockets since v0.5.0 are now resolved.
  • Fixed a recurring exception caused by a breaking change in the ETH/BSC indexer GraphQL API.

Upgrade guide

Make sure that your node is running v0.5.0. If that is not the case already, follow the upgrade guide here.

From v0.5.0, simply bump the version of these services:

  • The pyaleph and pyaleph-api services must use alephim/pyaleph-node:v0.5.1.
  • The p2p-service service must use alephim/p2p-service:0.1.3.

Then, restart your node: docker-compose down && docker-compose up -d.

What's Changed

New Contributors

Full Changelog: v0.5.0...v0.5.1