-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
provider fails to broadcast a bid for orders with mixed count
#149
Comments
are those deployments created via cloudmos or cli? |
CLI - provider-services 0.4.8 (binary from the GH releases page) |
andy108369
added
repo/node
Akash node repo issues
repo/provider
Akash provider-services repo issues
awaiting-triage
P1
and removed
repo/provider
Akash provider-services repo issues
labels
Nov 21, 2023
github-project-automation
bot
moved this to Backlog (not prioritized)
in Core Product and Engineering Roadmap
Nov 21, 2023
brewsterdrinkwater
moved this from Backlog (not prioritized)
to In Progress (prioritized)
in Core Product and Engineering Roadmap
Nov 21, 2023
November 21st, 2023: This requires a network upgrade to Mainnet 9. Upgrade only affects node. Proposal can be found here: https://www.mintscan.io/akash/proposals/238 |
Post Akash Mainnet 9, this has been thoroughly tested, and has been solved. |
brewsterdrinkwater
moved this from In Progress (prioritized)
to Released (in Prod)
in Core Product and Engineering Roadmap
Nov 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The provider encounters a
capabilities mismatch
error when attempting to broadcast a bid for an order request where thecount
for one service is higher than thecount
for another service.Scenarios
scenario 1 - bids (2 in total) 🟢
service foo, count 1
service bar, count 1
scenario 2 - no bid (3 in total) 💥
service foo, count 1
service bar, count 2
scenario 3 - bids (4 in total) 🟢
service foo, count 2
service bar, count 2
scenario 4 - no bid (5 in total) 💥
service foo, count 2
service bar, count 3
scenario 5 - bids (6 in total) 🟢
service foo, count 3
service bar, count 3
scenario 6 - bids (8 in total) 🟢
service foo, count 4
service bar, count 4
scenario 7 - no bids (9 in total) 💥
service foo, count 5
service bar, count 4
scenario 8 - bids (10 in total) 🟢
service foo, count 5
service bar, count 5
scenario 9 - no bids (4 in total, but 3 services now) 💥
service foo, count 1
service bar, count 2
service baz, count 1
scenario 10 - no bids (5 in total, 3 services) 💥
service foo, count 1
service bar, count 2
service baz, count 2
scenario 11 - no bids (6 in total, 3 services) 🟢
service foo, count 2
service bar, count 2
service baz, count 2
scenario 12 - bids (3 in total, 3 services) 🟢
service foo, count 1
service bar, count 1
service baz, count 1
scenario 13 - bids (4 in total, 4 services) 🟢
service foo, count 1
service bar, count 1
service baz, count 1
service qux, count 1
scenario 14 - no bids (5 in total, 4 services) 💥
service foo, count 2
service bar, count 1
service baz, count 1
service qux, count 1
scenario 15 - no bids (6 in total, 4 services) 💥
service foo, count 2
service bar, count 2
service baz, count 1
service qux, count 1
scenario 16 - no bids (7 in total, 4 services) 💥
service foo, count 2
service bar, count 2
service baz, count 2
service qux, count 1
scenario 17 - bids (8 in total, 4 services) 🟢
service foo, count 2
service bar, count 2
service baz, count 2
service qux, count 2
SW
provider & client both
0.4.8
akash node
0.28.2
provider log:
capabilities mismatch
service foo, count 1
service bar, count 2
SDL
The text was updated successfully, but these errors were encountered: