Fluence Developer Updates
129 subscribers
2 photos
53 links
Updates, announcements, changes, fixes
Download Telegram
Added a new feature to the marine-rs-sdk-test: services integration testing.

The marine_test macro now allows creating several services and passing data from one to another. It means that testing multi-service applications is now easier and the development may become faster.
See the docs and the example for more information.
Released Aqua compiler 0.3.2

- Experimental feature: now can run Aqua from Aqua CLI

aqua run -i aqua/caller.aqua -f "callFunc(\"arg1\",\"arg2\")"

- Many performance-related updates, compiler now runs faster
- UX improvements for CLI and JS/TS backend

See the full update in changelog
🔔In 10 min: developer community call
Livestream & rec https://youtu.be/uFPHM3JVccs

- intro to AquaVM,
- Q&A,
- project presentations from the community members

📞Via Zoom: https://us06web.zoom.us/meeting/register/tZYtdeytqjwtHNPupTLlURpqIqpKzCeCImJM

🗓Add to your calendar: https://calendar.google.com/calendar/u/0/r?cid=3uo257pe19e8g2vg2910ljcqi0@group.calendar.google.com
marine-rs-sdk-test 0.4.0 was released:
added an option to apply milti-service marine_test macro to a mod to have more flexibility,
added an interface for generating marine_test_env from cargo build scripts, which unblocks IDE support for test
For mode details please see example and docs.
Released the major Aqua version 0.4.0 that targets Fluence-JS 0.14.2, so you need to update both if you want to try them out. The new JS/TS SDK is heavily rewritten to support async service functions declaration. It also embeds a deeply refactored AquaVM. So, there's a lot of changes under the hood.

No code changes in Aqua and JS/TS usage needed to upgrade or downgrade (until you switch to async services on the client side). If anything is not working, please file an issue.
The new Aqua 0.4.1 just arrived. Among refactorings & bugfixes a new language feature comes: closures.

Now you can create Aqua functions (arrows) within Aqua functions, call them immediately or pass further as an argument. Closures capture service resolutions and values available in the definition scope. See documentation for details.

Closures is a part of the effort to make Aqua code more modular and flexible, therefore composable and reusable. This is quite important for big projects and complex algorithms. More features addressing Aqua logic modularization are to come.

Another minor feature that comes with 0.4.1 is the --scheduled CLI flag that makes the compiler produce AIR in the Fluence's Script Storage format. If you have any other idea about how to make Aqua developer's life easier, please file an issue.
Our next community call is scheduled for tomorrow, Thursday, Nov 11 at 18.00 CET (11 am CDT).

We are trying to make these calls helpful, educational, and entertaining for everyone who is getting into Fluence. Sometimes they take longer than we expected so feel free to join or drop off any time.

The preliminary agenda is:

- Updates from Fluence Labs (15 min)
- Apps demos by community members (15 min)
- Q&A, open discussions (15 min)
- Lecture about Marine (45 min)

During the lecture, we'll dive into Marine, our general-purpose Wasm runtime intended to run multi-modules Wasm applications with help of interface-types and shared-nothing linking scheme. We'll talk about the runtime architecture, API, and how it works internally.

Check out previous calls here:
- Recordings on Youtube
- Notes and future topics in Notion
- Add to Calendar
The new minor release of fluence-js has arrived: 0.14.3

Error handling has been improved. Now promises return from aqua call functions will fail early with user-friendly messages if the particle was not successfully sent onto the network.
Also some minor bugfixes delivered.

Please, refer to the changelog for more info.
AsyncVM is finally shipped on Krasnodar

AquaVM 0.15.0 enables service calls parallelization on a single peer, managed by Aqua scripts.

Previously parallelization in Aqua scripts worked only in the case of different machines: within the same peer, be it Rust node of Typescript, `par` / `co` code was actually executed sequentially. Now peer-local parallelism is managed by Aqua, just as expected.

This is not a protocol level change, so previous versions of Fluence peers keep working as expected.

The new AquaVM is now delivered both to the Rust peer and TypeScript peer. In the case of TypeScript, it also enables asynchronous services and callbacks, as AquaVM does not block anymore.
Announcing Aqua 0.5.0. This release fixes the issue with using streams within for loops. Now streams are restricted to the scope of the iteration or of a function, which is much more intuitive. See the documentation updates here.

This is a breaking change: Aqua 0.5 targets the latest AquaVM bundled within FluenceJS 0.15.0+ and Fluence Node v0.0.23+. fldist does not support the new AIR scripts at the moment, so please use aqua --run to run Aqua from CLI.

With Aqua 0.5, we expect no more critical bugs in the compiler. So if you find any, please assume that it is unknown and file an issue.
Added Peer.timeout(delay_ms: u32, message: string): string function to the Fluence Peer's builtins, available in @fluencelabs/aqua-lib v0.2.1.

It enables the timeout pattern between parallel execution branches: wait for some code to be executed, or do a failover if it does not respond in time. See Timeout pattern in the Aqua Book for the usage example.
The new minor release of fluence-js has arrived: 0.15.1

It fixes the bug in service registration functions when the service is implemented as a class.

Now the correct class context is preserved when storing such implementations. Also includes minor bug fixes.

Please, refer to the changelog for more info.
Announcing Aqua 0.5.1. This release adds a lot of features into aqua run command. Now you can pass any arguments as JSON, change log level, print generated air code, etc. Also you can create and pass your secret key. All features you can see in aqua run --help or in new documentation for CLI.

For the more detailed update, refer to the changelog.
Just released the new Aqua 0.5.2. This version contains one new feature: CLI command to upload files to Fluence Peer's companion IPFS, as a part of the effort to sunset fldist and move its logic into Aqua CLI.

Another big change is done under the hood: topology reasoning and transform was completely rewritten, eliminating all the known topology-related issues.
We are proud to announce a holidays present for all Fluence JS users.

Starting from version 0.17.1 all particles are being processed in background thread by default. It gives a massive performance boost especially in applications with lots of aqua code. This is achieved by using AVM runner instead of embedded AVM Interpreter.

The latest version of the package is 0.18.0. It contains the most up to date AquaVM. Please use this one when you upgrade.

Important note: using Fluence JS in browsers now requires additional configuration. See documentation for info.

You can find the full Fluence JS changelog here: https://doc.fluence.dev/docs/fluence-js/changelog
Introducing Aqua 0.5.3. In this version we enrich the language with an explicit join expression, and access to collection elements using non-literal indices:

func collectResponding(peers: []string, n: i16) -> []string:
stream: *string

for p <- peers par:
on p:
stream <<- p

join stream[n]

-- now stream contains at least n+1 elements
<- stream


Follow the links in the changelog to find out the details.
If you are looking to learn how to implement a dedicated signing node with Fluence JS or wrap EVM RPC APIs with Marine and use Aqua to seamlessly compose those services into protocols, look no further than the recently released near-integration examples.