-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't process new ledgers: The current ETL source is not compatible with the version of the libxrpl Clio is currently using. Please upgrade Clio to a newer version (Version: 2.1.1~26ed78f-1) #1410
Comments
Hi Paul, Clio can't proceed with its ETL side of things if some unknown type arrives from In order to use a custom
The workflow above is basically what is usually required when working on something that is not in Please keep in mind that if you change the If your custom type is in python only, if that's even a possibility at all, then the above will not help. And frankly i don't see a way to even make it work. But hopefully new types can't be added outside of C++. Hope this helps. Let us know if you need more help to get it to work 👍 |
Hey @godexsoft Followed your steps in building custom Clio server, however, when I ran this command:
I received the following error -
P.s. The first command -
Works correctly without any issues. Maybe I need to edit something else ? |
Hi @PaulMoney, I think you also need to change |
@godexsoft Now, the problem is with this command -
When I run, I receive the following error -
This error seems to be logical, as if I build rippled core from this branch - https://github.com/mvadari/rippled/tree/d8e0cd1e6f51b6cdb91a99c4213afaaa35e968b8 It has a new plugin folder, where plugin functionality is being placed. Maybe you have any ideas how to workaround this ? |
@PaulMoney I think this means that the Maybe @thejohnfreeman can give you some more concrete tips on this. I'm not too familiar with the build process of |
My suggestion: build both rippled and clio from source. The packages expect specific compatible versions as dependencies, but you want to use a custom version of rippled that is modified from an older version. In your custom source tree for rippled:
In a source tree for a version of Clio compatible with the base version of rippled that you modified:
|
@thejohnfreeman Thanks for your response. Could you please explain the exact commands I should run in source tree for rippled? For now, I ran only this command -
|
Ok I walked through the process and found two problems in the rippled branch you are using:
I've fixed these problems in a branch in my fork. With that branch, the below script works:
|
FYI I haven't done any work with Clio to make sure that it supports plugins; there's probably a fair amount of work on that front. |
Hey @thejohnfreeman
|
@PaulMoney i had the same issue yesterday when updating my local env to latest Clio develop - delete the build folder and start over from the conan command. Seems like your build is still setup to use the previous libxrpl. Or if you are on a very custom libxrpl/rippled branch then you want to merge latest upstream libxrpl into your branch because they recently changed paths (ripple -> xrpl) |
Issue Description
Hello, currently, I'm running my own small private rippled chain where I'm testing a new rippled plugin feature with a custom transaction type (e.g., TokenSwap). However, when I want to connect Clio to one of my custom rippled nodes, I receive the following error:
I have upgraded Clio to the newest version available as Debian package (2.1.1~26ed78f-1), but the error persists. Also, what I have noticed, is that, if I manually specify start_sequence field in Clio configuration file, it starts extracting ledgers, however on some ledger were was TokenSwap transaction it stops and Clio reports that ledger with that index could not be found.
Is it possible to rebuild or include support for custom transaction types in Clio?
Steps to Reproduce
Expected Result
Clio connects to custom rippled node and saves custom rippled transaction (e.g., TokenSwap).
Actual Result
Clio is unable to process new ledgers because current ETL source is not compatible with the version of the libxrpl Clio is currently using.
Environment
Ubuntu 22.04
The text was updated successfully, but these errors were encountered: