-
Notifications
You must be signed in to change notification settings - Fork 15
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
"fee" parameter misbehaving #59
Comments
Does not happens with new reposts, only old ones. |
Was this query directed to (python) hub? There is a possible related bug for the (go) herald #75 |
Would agree that the problem lies with reposts. However, I found an old repost (Nov 2020) on the channel (@DistributedBarbecue:3) that is returned even when fee_amount >= 0 is the query. Older repost (Nov 2020): https://explorer.lbry.com/claims/045681bd7662a777575452ce0475aafc1b030d27 Newer repost (Jul 2022): https://explorer.lbry.com/claims/38ca5fed5863705b97acd6f3c299ba7eae159b25 Query:
The problematic claims (9 reposts + 1 stream) span this range of block heights:
|
In Jun:
In July:
Most recently:
The phenomenon seems to exist in many periods of time, and might be going away due to some software change. There has been work to add more fields to reposts, but I don't see the python hub being updated for this yet. Use this to get a baseline for range of heights: Compare with: |
How to reproduce (July 11, spv19, the channel is probably not important):
Looks like reposts are gone? Not sure if only reposts are affected
The text was updated successfully, but these errors were encountered: