Skip to content

Fix invalid oxend rpc call#2252

Merged
jagerman merged 1 commit into
oxen-io:stablefrom
jagerman:fix-bad-oxend-request
Feb 17, 2025
Merged

Fix invalid oxend rpc call#2252
jagerman merged 1 commit into
oxen-io:stablefrom
jagerman:fix-bad-oxend-request

Conversation

@jagerman

@jagerman jagerman commented Jan 28, 2025

Copy link
Copy Markdown
Member

This call is wrong (and has always been wrong): the field should be set in the top-level parameters, not inside fields.

In current dev lokinet, however, the invalid field becomes an error, because dev tries to parse all fields keys with bool values, and this ends up returning an error to Lokinet instead of a response, which breaks Lokinet's service node updating code when used with oxend 11.

This call is wrong (and has always been wrong): the field should be set
in the top-level parameters, not inside `fields`.

In current dev lokinet, however, the invalid field becomes an error,
because dev tries to parse all `fields` keys with `bool` values, and
this ends up returning an error to Lokinet instead of a response, which
breaks Lokinet's service node updating code.
@jagerman jagerman added this to the 0.9.12 milestone Jan 28, 2025
@jagerman

Copy link
Copy Markdown
Member Author

Also noting in passing: this has been fixed for a while in the WIP code, probably because it encountered the same issue with testnet nodes at some point.

@jagerman jagerman merged commit 6e642d5 into oxen-io:stable Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant