Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Publishing issues on latest version

See original GitHub issue

The Issue

Looks like a couple minor issues arise when publishing on the latest version. Seems to happen with/without a channel being involved, but most of my testing was without a channel. See below for the summary of issues:

  1. After publishing, Publishes Page does not refresh after the file is confirmed (stays in pending confirmation)
  2. After clicking on the newly published file, it shows 0% Complete in the status
  3. After removing the claim id from the url and loading the vanity url, somtimes it returns “there is nothing at this location”. Doesn’t happen all the time, and if you search for the item, it eventual finds it and resolves.
  4. Have to Open the file by clicking the thumbnail in order for it to show “complete”

Steps to reproduce

  1. Publish something, wait patiently at the Publishes screen
  2. After 5 minutes, click the claim. Notice that it still says “pending confirmation”
  3. Claim shows 0% complete
  4. Remove the claimid from the address bar, click enter.
  5. Sometimes this leads to a “nothing at this location”, but other times it works (can’t nail this one down).
  6. Click on the thumbnail to complete the file and have the screen show “Open”.

Expected behaviour

Publishing status should update while sitting on Publishes page. After clicking on the item, it should show “Open”. Entering the vanity URL should resolve the claim if its the top bid.

Actual behaviour

File never shows that it completed confirmation. Shows 0 % Complete, vanity does not resolve sometimes.

System Configuration

  • LBRY Daemon version:0.14.2
  • LBRY App version: 0.13.0 (internal testing build)
  • LBRY Installation ID:6wGYry1eNtRZuvLjUpSkk6JQVhPcyh2X8KKZvQoyJhATBH6nNv1QuzkPzMMdjNLw2e
  • Operating system: Win 10

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
2017-07-26 14:01:12,509 INFO     lbrynet.core.server.BlobRequestHandler:151: Sending 362ed2ab48027ba5 to
2017-07-26 14:01:12,513 INFO     lbrynet.core.server.BlobRequestHandler:151: Sending c5a8adba52c9fe3a to
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
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


then updates with claim id 0percent after removing claimid from url after typing in name and opening the file

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

kauffjcommented, Aug 7, 2017

@tzarebczan can 1, 3, and 4 be made separate tickets?

Guessing 3 requires navigating to a URL that is currently resolving. I bet it will happen more reliably if you do it on URLs you have never accessed before, or after clearing your app cache.

tzarebczancommented, Aug 7, 2017
Read more comments on GitHub >

github_iconTop Results From Across the Web

Publishing issues - Play Console Help - Google Support
If you're already using the latest version of your browser, here are some solutions to common issues: Clear your browser's cache and cookies....
Read more >
Don't update latest when the published version is not ... - GitHub
A possible workaround which I did not try yet: In the git branch for the old major version, update package.json and add "publishConfig":...
Read more >
How to troubleshoot a damaged publication in Publisher
Lists the possible symptoms of a damaged publication and the methods that you can use after you restart the computer in Safe Mode...
Read more >
How to Fix the WordPress Updating Failed and Publishing ...
There are a few different causes of the “Publishing Failed” error, but one in particular is linked to the Block Editor. The new...
Read more >
Wix Editor: Publishing Issues | Help Center |
Error messages displayed · You're logged out. This message is displayed when you are attempting to publish your site while logged out of...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found