-
Notifications
You must be signed in to change notification settings - Fork 161
incorrect handling of metadata url in some cases #697
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
Comments
Please do not post images in bug reports. Lack of scaling on images can make the text tiny on high res screens (like mine) and i cannot cut and paste from an image. Instead, please cut and paste the text. |
There seem to be at least two issues here, and they do not seem to be well distinguished. The first problem, is that if a The second issue seems to be a failure to parse some URLs. |
It seems like the error with the uniqueness constraint is confounding and confusing the other problems, so I will fix that first. |
Lets find the pool id: select id, view from pool_hash where view = 'pool1l92x52u37neuc2w38wrgeu3esu9qzddmzvkvyuf9vfk5gav8nxl' ;
id | view
-------+----------------------------------------------------------
18067 | pool1l92x52u37neuc2w38wrgeu3esu9qzddmzvkvyuf9vfk5gav8nxl
(1 row) and the select * from pool_metadata_ref where pool_id = 18067 ;
id | pool_id | url | hash | registered_tx_id
-------+---------+-----------------------------+---------------------------------------+------------------
18012 | 18067 | https://blooir.com/MTD.json | \x3f192a9740e983b...7028a25fcc99400dc | 8197291
18015 | 18067 | https://booir.com/MTD.json | \x3f192a9740e983b...7028a25fcc99400dc | 8198428
(2 rows) Did not pick up any select * from pool_offline_fetch_error where pool_id = 18067 ;
id | pool_id | fetch_time | pmr_id | fetch_error | retry_count
----+---------+------------+--------+-------------+-------------
(0 rows) Not sure if there is another error in here somewhere, but the main one is fixed. |
Previously entries would be considered duplicates if the `pool_id` and `hash` were the same, but ignrored any differences in the `url` field, which was wrong. The `url` field *must* be part of the uniqueness constraint. Closes: #697
@erikd ok awesome! can you please push new release into world? with this + rewards, thanks. |
There is one ore thing that needs fixing, before a new release, but that should be done this week. |
Previously entries would be considered duplicates if the `pool_id` and `hash` were the same, but ignrored any differences in the `url` field, which was wrong. The `url` field *must* be part of the uniqueness constraint. Closes: #697
before the pool hash was used in place of actual url, as show by reported errors, eg.: "URL parse error from for pool1zy4arks3chpruyt32p0mhwqu3qpdgyx7nejrw06nqu3uzfuv3aw resulted in : InvalidUrlException "pool1zy4arks3chpruyt32p0mhwqu3qpdgyx7nejrw06nqu3uzfuv3aw" Should complete the fix for #697.
before the pool hash was used in place of actual url, as show by reported errors, eg.: "URL parse error from for pool1zy4arks3chpruyt32p0mhwqu3qpdgyx7nejrw06nqu3uzfuv3aw resulted in : InvalidUrlException "pool1zy4arks3chpruyt32p0mhwqu3qpdgyx7nejrw06nqu3uzfuv3aw" Should complete the fix for #697.
before the pool hash was used in place of actual url, as show by reported errors, eg.: "URL parse error from for pool1zy4arks3chpruyt32p0mhwqu3qpdgyx7nejrw06nqu3uzfuv3aw resulted in : InvalidUrlException "pool1zy4arks3chpruyt32p0mhwqu3qpdgyx7nejrw06nqu3uzfuv3aw" Should complete the fix for #697. Cherry-picked 00c96c2 from master.
Uh oh!
There was an error while loading. Please reload this page.
poolId:
pool1l92x52u37neuc2w38wrgeu3esu9qzddmzvkvyuf9vfk5gav8nxl
if the metadata fails to download several times, it will stop downloading again.
This is fine in a way (but it might be worth repeating once a day anyway, wouldn't it?). however, they will not start re-fetching if the pool updates its poolcert.
Look on screen.
Second thing is, why is this new meta url not saved in DB? He registered first url with typo "BLOOIR" (in db). Then re-registered with fix, but in db is no record about this.
latest version (v10)
The text was updated successfully, but these errors were encountered: