LBRYCommunity/spee.ch

Fork 0

publish in a channel does not show up immediately #479

New issue

Closed

opened 2018-06-14 23:16:11 +02:00 by bones7242 · 8 comments

bones7242 commented

2018-06-14 23:16:11 +02:00

(Migrated from github.com)

If a publish is made into a channel, it does not show up until the client refreshes the app. I believe this is because the redux store already retrieved the channel's info, including the list of claims, so it is not making a new request. After a successful publish, the asset record needs to be added to the channel's claims array or else the channel's info needs to be refreshed in full.

kauffj commented

2018-08-06 15:27:14 +02:00

(Migrated from github.com)

@billbitt should this be tagged Osprey? Not sure how important this is

tzarebczan commented

2018-10-10 22:48:39 +02:00

(Migrated from github.com)

@skhameneh this is the issue I mentioned and it's still happening. It may be important to fix for Osprey.

kauffj commented

2018-10-11 21:28:04 +02:00

(Migrated from github.com)

If new publishes don't show up without hitting reload, this probably should be fixed for Osprey.

tzarebczan commented

2018-10-30 00:08:27 +01:00

(Migrated from github.com)

Looks like it doesn't get added until it's confirmed + refreshed.

daovist commented

2018-10-30 00:26:05 +01:00

(Migrated from github.com)

I'm hoping to have a satisfactory solution to this problem for new publishes and updates as part of Osprey but it is tricky with chainquery and unconfirmed claims.

At the very least I will add the data to redux upon publish confirmation but it won't persist.

I'm hoping to have a satisfactory solution to this problem for new publishes *and* updates as part of Osprey but it is tricky with chainquery and unconfirmed claims. At the very least I will add the data to redux upon publish confirmation but it won't persist.

tiger5226 commented

2018-11-04 02:47:55 +01:00

(Migrated from github.com)

@daovist Chainquery has been updated to process mempool transactions. It regularly checks for these every second and processes them. See https://github.com/lbryio/chainquery/issues/59 for added details.

daovist commented

2018-11-05 14:38:30 +01:00

(Migrated from github.com)

Excellent! Thank you @tiger5226

skhameneh commented

2018-11-10 01:08:04 +01:00

(Migrated from github.com)

During testing this gave a very acceptable update time (few seconds); we will actively work on improving times. Closing for now.

This discussion has been locked. Commenting is limited to contributors.

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/spee.ch#479

No description provided.

Rows
Columns