Issue resolving previously uncached URIs / Refreshing cached data #451

Closed
opened 2017-08-07 22:12:59 +02:00 by tzarebczan · 4 comments
tzarebczan commented 2017-08-07 22:12:59 +02:00 (Migrated from github.com)

The Issue

Original issue being separated out from: https://github.com/lbryio/lbry-app/issues/390

After publishing a file and then viewing it via the entire URL (claimname#claimdid): There is an issue where removing the claim id from the url and clicking enter to load the vanity url where the app sometimes returns "there is nothing at this location". Doesn't happen all the time, and if you search for the item, it eventually finds it and resolves. Almost seems like the resolve never happens when the claimid is removed.
Per Jeremy: "I bet it will happen more reliably if you do it on URLs you have never accessed before, or after clearing your app cache."

Steps to reproduce

  1. Publish something then go to the url
  2. Remove the claim id portion of the url to expose the vanity url
  3. Click enter
    4: There is nothing at this location.

Expected behaviour

Vanity URL should resolve

Actual behaviour

Shows nothing at this location

System Configuration

  • LBRY Daemon version: 0.14.2
  • LBRY App version: 0.14.3
  • LBRY Installation ID:
  • Operating system: Windows

Anything Else

2017-07-26 14:01:06,390 INFO     lbrynet.daemon.Daemon:1838: Publish: {'claim_address': None, 'name': u'nothingatthislocation', 'bid': 0.01, 'claim_dict': {'version': '_0_0_1', 'claimType': 'streamType', 'stream': {'version': '_0_0_1', 'metadata': {u'description': u'test', u'license': u'', u'title': u'nothing at this location', u'language': u'en', 'version': '_0_1_0', u'nsfw': False, u'licenseUrl': None}}}, 'file_path': u'C:\\Users\\thoma\\Desktop\\nothing at this location.PNG', 'change_address': None}
2017-07-26 14:01:06,390 INFO     lbrynet.daemon.Publisher:27: Starting publish for nothingatthislocation
2017-07-26 14:01:06,706 INFO     lbrynet.core.server.BlobRequestHandler:151: Sending 1207920d390fdb1b to 113.169.3.228:59256
2017-07-26 14:01:12,509 INFO     lbrynet.core.server.BlobRequestHandler:151: Sending 362ed2ab48027ba5 to 189.71.209.86:55455
2017-07-26 14:01:12,513 INFO     lbrynet.core.server.BlobRequestHandler:151: Sending c5a8adba52c9fe3a to 129.65.24.134:54798
2017-07-26 14:01:12,515 INFO     lbrynet.core.Wallet:822: Resolving lbry://three#b64155f2d44553871dfdb1785aa49d6d3972cd84
2017-07-26 14:01:18,983 INFO     lbrynet.lbry_file.EncryptedFileMetadataManager:246: Saved sd blob hash 3dbb0bc6420a23940ec4c593df4f68eccd2cbe1ba5e1afe2bd81df17afbf2a6873e682002c5f1dfe2145e9cc061450c1 to stream hash 015d47aa723a103fc4ea0deff49f44e05942d6a34e5a245b02c1e07b957fc37283cbc6dfa68dafe0b164836adb653ba2
2017-07-26 14:01:18,986 INFO     lbrynet.core.Wallet:1354: Send claim: nothingatthislocation for 0.01: 080110011a7708011230080410011a186e6f7468696e672061742074686973206c6f636174696f6e2204746573742a00320038004a0052005a001a41080110011a303dbb0bc6420a23940ec4c593df4f68eccd2cbe1ba5e1afe2bd81df17afbf2a6873e682002c5f1dfe2145e9cc061450c12209696d6167652f706e67 
2017-07-26 14:01:21,556 ERROR    lbryum:115: [CoinChooserOldestFirst] change: [(1, 'bYi6fibg2iufnD3A1pY1BJvtC2BSM1Y2t6', 303500)]

2017-07-26 14:01:21,558 ERROR    lbryum:115: [CoinChooserOldestFirst] using 1 inputs

2017-07-26 14:01:21,558 ERROR    lbryum:115: [CoinChooserOldestFirst] using buckets: [u'dc1874b0a0d6f1b720551687fb3e2dbe6b615956f853147e2cfb5364ec646347:0']
2017-07-26 14:01:21,730 ERROR    lbryum:115: adding signature for ff0488b21e000000000000000000b1c759c39f4f70eb4c99e91b5e48d1a1228ea20ec62d0b489f0141d8ba624184030a956c8d0aac626372ed6e26ac48bde116ba7bb1f7e030c895561f862f3f608f0100a300
2017-07-26 14:01:22,214 ERROR    lbryum:115: is_complete True
2017-07-26 14:01:22,430 INFO     lbrynet.core.Wallet:948: Saving metadata for claim 9ce92b159427b419585f73105490968cdc53119c0a0773634b6948f9696ef787 1
2017-07-26 14:01:22,502 INFO     lbrynet.daemon.Daemon:654: Success! Published to lbry://nothingatthislocation txid: 
2017-07-26 14:01:44,664 WARNING  lbrynet.reflector.client.client:87: Stopped reflecting lbry://nothingatthislocation (3dbb0bc6420a2394) after sending 0 blobs
2017-07-26 14:01:44,665 INFO     lbrynet.daemon.Daemon:650: Reflected new publication to lbry://nothingatthislocation
2017-07-26 14:01:44,690 INFO     lbrynet.core.Wallet:822: Resolving lbry://nothingatthislocation#63740416e5fe3f6f682ce0fc0be36df8e670c5df

2017-07-26 14:18:03,351 INFO     lbrynet.core.Wallet:822: Resolving lbry://nothingatthislocation#63740416e5fe3f6f682ce0fc0be36df8e670c5df

^^^^^^^ no mention of resolving lbry://nothingatthislocation when I removed the claimId from the addressbar


******AFTER SEARCHING FOR "NOTHINGATTHISLOCATION"******
2017-07-26 14:21:42,032 INFO     lbrynet.core.Wallet:822: Resolving lbry://nothingatthislocation

2017-07-26 14:21:42,295 INFO     lbrynet.core.Wallet:822: Resolving lbry://lbrynodownload#b8bccfc52e9e7b0a8658ffb00c5ea8c919a7bfa3

2017-07-26 14:22:49,207 INFO     lbrynet.daemon.Daemon:1498: Already have lbry file but missing file in C:\Users\thoma\Downloads, rebuilding it
2017-07-26 14:22:49,207 INFO     lbrynet.core.client.ConnectionManager:38: Connection Manager nothing at this location.PNG initialized
2017-07-26 14:22:49,280 INFO     lbrynet.file_manager.EncryptedFileDownloader:32: lbry://nothingatthislocation (3dbb0b) is unknown

Screenshots

after removing claimid from url

<!-- Thanks for reporting an issue to LBRY and helping us improve! To make it possible for us to help you, please fill out below information carefully. Before reporting any issues, please make sure that you're using the latest version. - App releases: https://github.com/lbryio/lbry-app/releases - Standalone daemon: https://github.com/lbryio/lbry/releases We are also available on Slack at https://slack.lbry.io --> ## The Issue Original issue being separated out from: https://github.com/lbryio/lbry-app/issues/390 After publishing a file and then viewing it via the entire URL (claimname#claimdid): There is an issue where removing the claim id from the url and clicking enter to load the vanity url where the app sometimes returns "there is nothing at this location". Doesn't happen all the time, and if you search for the item, it eventually finds it and resolves. Almost seems like the resolve never happens when the claimid is removed. Per Jeremy: "I bet it will happen more reliably if you do it on URLs you have never accessed before, or after clearing your app cache." ### Steps to reproduce 1. Publish something then go to the url 2. Remove the claim id portion of the url to expose the vanity url 3. Click enter 4: There is nothing at this location. ### Expected behaviour Vanity URL should resolve ### Actual behaviour Shows nothing at this location ## System Configuration <!-- For the app, this info is in the About section at the bottom of the Help page. You can include a screenshot instead of typing it out --> <!-- For the daemon, run: curl 'http://localhost:5279/lbryapi' --data '{"method":"version"}' and include the full output --> - LBRY Daemon version: 0.14.2 - LBRY App version: 0.14.3 - LBRY Installation ID: - Operating system: Windows ## Anything Else <!-- Include anything else that does not fit into the above sections --> ``` 2017-07-26 14:01:06,390 INFO lbrynet.daemon.Daemon:1838: Publish: {'claim_address': None, 'name': u'nothingatthislocation', 'bid': 0.01, 'claim_dict': {'version': '_0_0_1', 'claimType': 'streamType', 'stream': {'version': '_0_0_1', 'metadata': {u'description': u'test', u'license': u'', u'title': u'nothing at this location', u'language': u'en', 'version': '_0_1_0', u'nsfw': False, u'licenseUrl': None}}}, 'file_path': u'C:\\Users\\thoma\\Desktop\\nothing at this location.PNG', 'change_address': None} 2017-07-26 14:01:06,390 INFO lbrynet.daemon.Publisher:27: Starting publish for nothingatthislocation 2017-07-26 14:01:06,706 INFO lbrynet.core.server.BlobRequestHandler:151: Sending 1207920d390fdb1b to 113.169.3.228:59256 2017-07-26 14:01:12,509 INFO lbrynet.core.server.BlobRequestHandler:151: Sending 362ed2ab48027ba5 to 189.71.209.86:55455 2017-07-26 14:01:12,513 INFO lbrynet.core.server.BlobRequestHandler:151: Sending c5a8adba52c9fe3a to 129.65.24.134:54798 2017-07-26 14:01:12,515 INFO lbrynet.core.Wallet:822: Resolving lbry://three#b64155f2d44553871dfdb1785aa49d6d3972cd84 2017-07-26 14:01:18,983 INFO lbrynet.lbry_file.EncryptedFileMetadataManager:246: Saved sd blob hash 3dbb0bc6420a23940ec4c593df4f68eccd2cbe1ba5e1afe2bd81df17afbf2a6873e682002c5f1dfe2145e9cc061450c1 to stream hash 015d47aa723a103fc4ea0deff49f44e05942d6a34e5a245b02c1e07b957fc37283cbc6dfa68dafe0b164836adb653ba2 2017-07-26 14:01:18,986 INFO lbrynet.core.Wallet:1354: Send claim: nothingatthislocation for 0.01: 080110011a7708011230080410011a186e6f7468696e672061742074686973206c6f636174696f6e2204746573742a00320038004a0052005a001a41080110011a303dbb0bc6420a23940ec4c593df4f68eccd2cbe1ba5e1afe2bd81df17afbf2a6873e682002c5f1dfe2145e9cc061450c12209696d6167652f706e67 2017-07-26 14:01:21,556 ERROR lbryum:115: [CoinChooserOldestFirst] change: [(1, 'bYi6fibg2iufnD3A1pY1BJvtC2BSM1Y2t6', 303500)] 2017-07-26 14:01:21,558 ERROR lbryum:115: [CoinChooserOldestFirst] using 1 inputs 2017-07-26 14:01:21,558 ERROR lbryum:115: [CoinChooserOldestFirst] using buckets: [u'dc1874b0a0d6f1b720551687fb3e2dbe6b615956f853147e2cfb5364ec646347:0'] 2017-07-26 14:01:21,730 ERROR lbryum:115: adding signature for ff0488b21e000000000000000000b1c759c39f4f70eb4c99e91b5e48d1a1228ea20ec62d0b489f0141d8ba624184030a956c8d0aac626372ed6e26ac48bde116ba7bb1f7e030c895561f862f3f608f0100a300 2017-07-26 14:01:22,214 ERROR lbryum:115: is_complete True 2017-07-26 14:01:22,430 INFO lbrynet.core.Wallet:948: Saving metadata for claim 9ce92b159427b419585f73105490968cdc53119c0a0773634b6948f9696ef787 1 2017-07-26 14:01:22,502 INFO lbrynet.daemon.Daemon:654: Success! Published to lbry://nothingatthislocation txid: 2017-07-26 14:01:44,664 WARNING lbrynet.reflector.client.client:87: Stopped reflecting lbry://nothingatthislocation (3dbb0bc6420a2394) after sending 0 blobs 2017-07-26 14:01:44,665 INFO lbrynet.daemon.Daemon:650: Reflected new publication to lbry://nothingatthislocation 2017-07-26 14:01:44,690 INFO lbrynet.core.Wallet:822: Resolving lbry://nothingatthislocation#63740416e5fe3f6f682ce0fc0be36df8e670c5df 2017-07-26 14:18:03,351 INFO lbrynet.core.Wallet:822: Resolving lbry://nothingatthislocation#63740416e5fe3f6f682ce0fc0be36df8e670c5df ^^^^^^^ no mention of resolving lbry://nothingatthislocation when I removed the claimId from the addressbar ******AFTER SEARCHING FOR "NOTHINGATTHISLOCATION"****** 2017-07-26 14:21:42,032 INFO lbrynet.core.Wallet:822: Resolving lbry://nothingatthislocation 2017-07-26 14:21:42,295 INFO lbrynet.core.Wallet:822: Resolving lbry://lbrynodownload#b8bccfc52e9e7b0a8658ffb00c5ea8c919a7bfa3 2017-07-26 14:22:49,207 INFO lbrynet.daemon.Daemon:1498: Already have lbry file but missing file in C:\Users\thoma\Downloads, rebuilding it 2017-07-26 14:22:49,207 INFO lbrynet.core.client.ConnectionManager:38: Connection Manager nothing at this location.PNG initialized 2017-07-26 14:22:49,280 INFO lbrynet.file_manager.EncryptedFileDownloader:32: lbry://nothingatthislocation (3dbb0b) is unknown ``` ## Screenshots <!-- If a screenshot would help explain the bug, please include one or two here --> ![after removing claimid from url](https://user-images.githubusercontent.com/8120721/28638179-0cbce35e-7212-11e7-914e-6b0ba59323aa.PNG)
kauffj commented 2017-10-10 19:09:41 +02:00 (Migrated from github.com)

This is likely a much larger issue related to caching in general inside of the app. When, and how often, should we re-resolve a URL that we have data for? This applies to not just URL resolution, but things like file status, which claims are yours, and many other things. Two hard things, etc.

This is likely a much larger issue related to caching in general inside of the app. When, and how often, should we re-resolve a URL that we have data for? This applies to not just URL resolution, but things like file status, which claims are yours, and many other things. [Two hard things](https://martinfowler.com/bliki/TwoHardThings.html), etc.
tzarebczan commented 2018-07-16 15:55:07 +02:00 (Migrated from github.com)

A user ran into this recently, so it's still an issue.

A user ran into this recently, so it's still an issue.
alyssaoc commented 2018-08-21 19:33:18 +02:00 (Migrated from github.com)

@tzarebczan is this still an issue?

@tzarebczan is this still an issue?
tzarebczan commented 2019-09-04 03:00:26 +02:00 (Migrated from github.com)

Closing this, have not run into it in a while.

Closing this, have not run into it in a while.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-desktop#451
No description provided.