Two children with the same key - console error #798

Closed
opened 2017-11-29 16:25:45 +01:00 by tzarebczan · 2 comments
tzarebczan commented 2017-11-29 16:25:45 +01:00 (Migrated from github.com)

The Issue

The console is throwing an error/warning about the lbry://sideshow claim. Probably happening because it appears in both the Trending section and LBRY Originals?

bundle.js:279 Warning: flattenChildren(...): Encountered two children with the same key, `sideshow1#5fe4ffe595b37b11050c1ea9a12dd2a74ad9473a`. Child keys must be unique; when two children share a key, only the first child will be used.
    in div (created by FeaturedCategory)
    in div (created by FeaturedCategory)
    in div (created by FeaturedCategory)
    in FeaturedCategory (created by DiscoverPage)
    in main (created by DiscoverPage)
    in DiscoverPage (created by Connect(DiscoverPage))
    in Connect(DiscoverPage) (created by Router)
    in Router (created by Connect(Router))
    in Connect(Router) (created by App)
    in div (created by App)
    in div (created by App)
    in App (created by Connect(App))
    in Connect(App)
    in div
    in Provider

Steps to reproduce

  1. Open LBRY app
  2. Check console

System Configuration

  • LBRY Daemon version: 0.18.0
  • LBRY App version: 0.18.2
  • LBRY Installation ID:
  • Operating system: Windows

Anything Else

Screenshots

<!-- 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 live chat at https://chat.lbry.io --> ## The Issue The console is throwing an error/warning about the lbry://sideshow claim. Probably happening because it appears in both the Trending section and LBRY Originals? ``` bundle.js:279 Warning: flattenChildren(...): Encountered two children with the same key, `sideshow1#5fe4ffe595b37b11050c1ea9a12dd2a74ad9473a`. Child keys must be unique; when two children share a key, only the first child will be used. in div (created by FeaturedCategory) in div (created by FeaturedCategory) in div (created by FeaturedCategory) in FeaturedCategory (created by DiscoverPage) in main (created by DiscoverPage) in DiscoverPage (created by Connect(DiscoverPage)) in Connect(DiscoverPage) (created by Router) in Router (created by Connect(Router)) in Connect(Router) (created by App) in div (created by App) in div (created by App) in App (created by Connect(App)) in Connect(App) in div in Provider ``` ### Steps to reproduce 1. Open LBRY app 2. Check console ## 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' --data '{"method":"version"}' and include the full output --> - LBRY Daemon version: 0.18.0 - LBRY App version: 0.18.2 - LBRY Installation ID: - Operating system: Windows ## 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 -->
kauffj commented 2017-11-29 16:37:10 +01:00 (Migrated from github.com)

Hmm, is it possible the trending area is returning the same thing twice? I think this would only happen if they were both in the same category.

Hmm, is it possible the trending area is returning the same thing twice? I think this would only happen if they were both in the same category.
tzarebczan commented 2017-11-29 16:52:14 +01:00 (Migrated from github.com)

You are right, there are only 9 items shown in the trending section. Closing this and tracking via https://github.com/lbryio/internal-apis/issues/154

You are right, there are only 9 items shown in the trending section. Closing this and tracking via https://github.com/lbryio/internal-apis/issues/154
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#798
No description provided.