Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
P
polkadot-sdk
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
parity
Mirrored projects
polkadot-sdk
Commits
f1bfc080
Unverified
Commit
f1bfc080
authored
1 year ago
by
Adrian Catangiu
Committed by
GitHub
1 year ago
Browse files
Options
Downloads
Patches
Plain Diff
xcmp-queue: remove outdated bridging comment (#2095)
Removed confusing and outdated `TODO`.
parent
c38aae62
Branches
Branches containing commit
No related merge requests found
Pipeline
#407471
passed with stages
in 48 minutes and 19 seconds
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
cumulus/pallets/xcmp-queue/src/bridging.rs
+0
-7
0 additions, 7 deletions
cumulus/pallets/xcmp-queue/src/bridging.rs
with
0 additions
and
7 deletions
cumulus/pallets/xcmp-queue/src/bridging.rs
+
0
−
7
View file @
f1bfc080
...
...
@@ -63,13 +63,6 @@ impl<SiblingBridgeHubParaId: Get<ParaId>, Runtime: crate::Config>
return
true
}
// TODO: https://github.com/paritytech/polkadot-sdk/pull/1556 - once this PR is merged, we may
// remove the following code.
// TODO: the following restriction is arguable, we may live without that, assuming that
// There can't be more than some `N` messages queued at the bridge queue (at the source BH)
// AND before accepting next (or next-after-next) delivery transaction, we'll receive the
// suspension signal from the target parachain and stop accepting delivery transactions.
// It takes some time for target parachain to suspend inbound channel with the target BH and
// during that we will keep accepting new message delivery transactions. Let's also reject
// new deliveries if there are too many "pages" (concatenated XCM messages) in the target BH
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment