Coretime Broker on Coretime Chain - Update after Coretime Polkadot release #10947
Conversation
…from the workplan
piggydoughnut
changed the title
| if (parachainId) { | ||
| return load?.filter(({ info }) => info.task === parachainId); | ||
| return data.filter(({ workload }) => !!workload?.filter(({ info }) => info.task === parachainId).length); |
There was a problem hiding this comment.
Wouldn't !!workload here just return a boolean?
There was a problem hiding this comment.
Yes, that is exactly what I am going for :) Coz I need to see if the is a workload with parachainId that I am looking for :) Then I can filter out objects of CoreInfo
export interface CoreInfo {
core: number,
workload: CoreWorkloadType[] | undefined,
workplan: CoreWorkplanType[] | undefined
}
|
|
||
| useEffect(() => { | ||
| setWorkLoad(formatLoad(workloadInfos, leaseMap, reservationMap)); | ||
| }, [workloadInfos, leaseMap, reservationMap]); | ||
| !!workplanInfos && !!workloadInfos && !!coreCount && !!leaseMap && !!reservationMap && |
There was a problem hiding this comment.
I dont think we need the double bangs on any of these values?
There was a problem hiding this comment.
Typescript begs to differ (for some of them) 😊 I might have thrown in some extras just in case 😅
|
I love my double bangs 😆 They leave no room for other interpretation 😊 |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Coretime has been released to the Polkadot Relay chain, but since the data was relying on the
Workloadpallet call, there is not data shown in theNetwork->Coretime broker(Experimental)Tab currently.In the initial sales period (sale 0), the Coretime chain isn't actively driving the relay chain; it's essentially in the same state as it was prior to the transition. During the bootstrapping phase, things operate a bit differently, but after the 28-day period, the workload will align with the current state of the relay chain moving forward.
This PR changes data organization, and takes the
coreCountfrombroker.statuscall as the truth to how many cores are there, instead of relying onWorkloadto provide information about the cores.Other changes:
cores sold/offeredto the summary above the tableMy Coretime notes