Skip to content
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

Issue with Intersect #574

Open
Crypto2099 opened this issue Apr 4, 2023 · 1 comment
Open

Issue with Intersect #574

Crypto2099 opened this issue Apr 4, 2023 · 1 comment

Comments

@Crypto2099
Copy link

I'm getting the following error when adding a source.intersect value to my config.toml

ERROR: invalid type: sequence, expected unit variant IntersectArg::Origin

Command:

oura daemon --config nfts.toml

Oura Version:

~$ oura --version
oura 1.8.1

Config:

[source]
type = "N2N"
address = ["Tcp", "preprod-node.world.dev.cardano.org:30000"]
magic = "preprod"

[source.intersect]
type = "Origin"

[source.mapper]
include_transaction_details = true

[[filters]]
type = "Selection"

[filters.check]
predicate = "all_of"

[[filters.check.argument]]
predicate = "variant_in"
argument = ["Transaction"]

[[filters.check.argument]]
predicate = "metadata_label_equals"
argument = "721"

[sink]
type = "Webhook"
url = "https://webhook.site/XXXXX"
timeout = 30000
error_policy = "Exit"

[sink.headers]
"webhook-auth-token" = "abc"

[sink.retry_policy]
max_retries = 30
backoff_unit =  5000
backoff_factor = 2
max_backoff = 100000

[cursor]
type = "File"
path = "/home/ubuntu/nfts.cursor"

[metrics]
address = "0.0.0.0:9186"
endpoint = "/metrics"

The most odd part about this is the exact same config works fine in other environments. Oura was installed from release binaries and works fine if the source.intersect argument is removed from the config.

@latheesan-k
Copy link

latheesan-k commented Apr 4, 2023

Another interesting behaviour I've observed is, when I created a cursor file put a specific absolute slot, block hash in there I want to sync from and started the oura indexer with metrics, works perfectly fine on my local dev machine (ubuntu)

When I deploy the same setup on my AWS lightsail instance (also ubuntu), its not doing anything and the metric is stuck on:

# HELP chain_tip the last detected tip of the chain (height)
# TYPE chain_tip gauge
chain_tip 0
# HELP rollback_count number of rollback events occurred
# TYPE rollback_count counter
rollback_count 0
# HELP sink_current_slot last slot processed by the sink of the pipeline
# TYPE sink_current_slot gauge
sink_current_slot 0
# HELP sink_event_count number of events processed by the sink of the pipeline
# TYPE sink_event_count counter
sink_event_count 0
# HELP source_current_height last height (block #) processed by the source of the pipeline
# TYPE source_current_height gauge
source_current_height 0
# HELP source_current_slot last slot processed by the source of the pipeline
# TYPE source_current_slot gauge
source_current_slot 0
# HELP source_event_count number of events processed by the source of the pipeline
# TYPE source_event_count counter
source_event_count 0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants