after upgrade to 4.0.0-dev, report "Error: Service(Application(LightSyncStateExtensionNotFound))" when i run "mychain-node --dev"

[baidang201]

./mychain-node --dev
2021-10-22 14:16:52 Running in --dev mode, RPC CORS has been disabled.    
2021-10-22 14:16:52 Substrate Node    
2021-10-22 14:16:52 ✌️  version 2.0.0-84e5c9c-x86_64-linux-gnu    
2021-10-22 14:16:52 ❤️  by Parity Technologies <admin@parity.io>, 2017-2021    
2021-10-22 14:16:52 📋 Chain specification: Development    
2021-10-22 14:16:52 🏷 Node name: alert-sheet-6251    
2021-10-22 14:16:52 👤 Role: AUTHORITY    
2021-10-22 14:16:52 💾 Database: RocksDb at /tmp/substrate7zvH4R/chains/dev/db/full    
2021-10-22 14:16:52 ⛓  Native runtime: mychain-node-3 (mychain-node-0.tx2.au10)    
2021-10-22 14:16:52 💸 new validator set of size 1 has been elected for era 0
 
                candidate_delegators: [be5ddb1579b72e84524fc29e78609e3caf42e85aa118ebfe0b0ad404b5bdd25f (5GNJqTPy...)]
                    
2021-10-22 14:16:52 🔨 Initializing Genesis block/state (state: 0x086d…64ed, header-hash: 0x9605…6602)    
2021-10-22 14:16:52 👴 Loading GRANDPA authority set from genesis on what appears to be first startup.    
2021-10-22 14:16:53 ⏱  Loaded block-time = 5s from block 0x9605845f5e39a0d7e1c77f572dac5c0fbc18681342670f2a4b2ea71904f76602    
2021-10-22 14:16:53 👶 Creating empty BABE epoch changes on what appears to be first startup.    
2021-10-22 14:16:53 Using default protocol ID "sup" because none is configured in the chain specs    
2021-10-22 14:16:53 🏷 Local node identity is: 12D3KooWSW8Yi7Yzd2gpwpoWtLCXxxZE2BxMNfRwef7HvKU7yN2N    
Error: Service(Application(LightSyncStateExtensionNotFound))
2021-10-22 14:16:53 📦 Highest known block at #0    
2021-10-22 14:16:53 〽️ Prometheus exporter started at 127.0.0.1:9615   

[nuke-web3]

As you might know the 4.0.0 is not released, -dev implies things are unstable. FYI paritytech/substrate#9684 -- the light client is being removed from substrate. I would expect when this PR is merged and you pull in dependencies past this commit, this issue should be resolved. If it is not, please reopen this issue.

NOTE: you must update your lock file to the new commits for this to occur. Remove the lock file cargo clean and try to build again, that should be the easiest way to get things working again. 🤞