Batch resolve fails if single URI encounters an error #842

Closed
opened 2017-12-11 17:31:04 +01:00 by jackrobison · 3 comments
jackrobison commented 2017-12-11 17:31:04 +01:00 (Migrated from github.com)

@tzarebczan commented on Sun Dec 10 2017

The Issue

In a batched resolution, the entire resolve command fails if one of the URLs errors out. This is happening on the homepage at the moment because of an expired claim in the resolve call.

Steps to reproduce

  1. batch a URI resolution with a known bad URL
  2. observe failure

Expected behaviour

Tell us what should happen

Actual behaviour

Tell us what happens instead

System Configuration

  • LBRY Daemon version: 0.18.2
  • LBRY App version: 0.19rc1
  • LBRY Installation ID:
  • Operating system:

Anything Else

Screenshots


@jackrobison commented on Mon Dec 11 2017

resolve in lbrynet handles these cases, this error must be in the app handling of the response.

@tzarebczan commented on [Sun Dec 10 2017](https://github.com/lbryio/lbry/issues/1024) <!-- 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 Discord at https://chat.lbry.io --> ## The Issue In a batched resolution, the entire resolve command fails if one of the URLs errors out. This is happening on the homepage at the moment because of an expired claim in the resolve call. ### Steps to reproduce 1. batch a URI resolution with a known bad URL 2. observe failure ### Expected behaviour Tell us what should happen ### Actual behaviour Tell us what happens instead ## 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.18.2 - LBRY App version: 0.19rc1 - LBRY Installation ID: - Operating system: ## Anything Else <!-- Include anything else that does not fit into the above sections --> ## Screenshots <!-- If a screenshot would help explain the bug, please include one or two here --> --- @jackrobison commented on [Mon Dec 11 2017](https://github.com/lbryio/lbry/issues/1024#issuecomment-350777582) `resolve` in lbrynet handles these cases, this error must be in the app handling of the response.
deepalimayekar commented 2018-01-04 08:49:10 +01:00 (Migrated from github.com)

In the Python file, check the statuscode of the request after the get call. If r.status_code is not 200, skip the response.

In the Python file, check the statuscode of the request after the get call. If r.status_code is not 200, skip the response.
deepalimayekar commented 2018-01-04 08:51:15 +01:00 (Migrated from github.com)

import requests r = requests.get('fill url) compare r.status_code and if not 200, do not write Thus resolve will not fail if any URL is incorrect.

`import requests r = requests.get('fill url) compare r.status_code and if not 200, do not write Thus resolve will not fail if any URL is incorrect.`
lyoshenka commented 2018-04-19 17:51:21 +02:00 (Migrated from github.com)

closing, as this is a daemon error.

closing, as this is a daemon error.
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#842
No description provided.