Skip to content

build: [Snyk] Upgrade @mui/material from 5.16.7 to 5.16.8 (#3348) #6570

build: [Snyk] Upgrade @mui/material from 5.16.7 to 5.16.8 (#3348)

build: [Snyk] Upgrade @mui/material from 5.16.7 to 5.16.8 (#3348) #6570

GitHub Actions / Test Results succeeded Jan 6, 2025 in 0s

All 8 tests pass in 2m 2s

1 files   -  2  10 suites   - 100   2m 2s ⏱️ +27s
8 tests  - 32   8 ✅  -  24  0 💤 ±0  0 ❌  -  8 
8 runs   - 92   8 ✅  -  78  0 💤 ±0  0 ❌  - 14 

Results for commit 90739e1. ± Comparison against earlier commit d22ae76.

Annotations

Check notice on line 0 in .github

See this annotation in the file changed.

@github-actions github-actions / Test Results

8 tests found

There are 8 tests, see "Raw output" for the full list of tests.
Raw output
Should allow different accounts associated in the same HbarSpendingPlan to contribute to the same budget ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests HBAR Rate Limit For Different Spending Plan Tiers @hbarlimiter-batch2 Preconfigured Tiers EXTENDED Tier Should allow different accounts associated in the same HbarSpendingPlan to contribute to the same budget
Should allow different accounts associated in the same HbarSpendingPlan to contribute to the same budget ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests HBAR Rate Limit For Different Spending Plan Tiers @hbarlimiter-batch2 Preconfigured Tiers PRIVILEGED Tier Should allow different accounts associated in the same HbarSpendingPlan to contribute to the same budget
Should eventually exhaust the hbar limit for EXTENDED user and still allow another EXTENDED user to make calls ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests HBAR Rate Limit For Different Spending Plan Tiers @hbarlimiter-batch2 Preconfigured Tiers EXTENDED Tier Should eventually exhaust the hbar limit for EXTENDED user and still allow another EXTENDED user to make calls
Should eventually exhaust the hbar limit for PRIVILEGED user and still allow another PRIVILEGED user to make calls ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests HBAR Rate Limit For Different Spending Plan Tiers @hbarlimiter-batch2 Preconfigured Tiers PRIVILEGED Tier Should eventually exhaust the hbar limit for PRIVILEGED user and still allow another PRIVILEGED user to make calls
Should increase the amount spent of the spending plan by the transaction cost ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests HBAR Rate Limit For Different Spending Plan Tiers @hbarlimiter-batch2 Preconfigured Tiers EXTENDED Tier Should increase the amount spent of the spending plan by the transaction cost
Should increase the amount spent of the spending plan by the transaction cost ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests HBAR Rate Limit For Different Spending Plan Tiers @hbarlimiter-batch2 Preconfigured Tiers PRIVILEGED Tier Should increase the amount spent of the spending plan by the transaction cost
should create a BASIC spending plan for a new user and use the same plan on second transaction and different plan on third transaction from another user ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests HBAR Rate Limit For Different Spending Plan Tiers @hbarlimiter-batch2 BASIC Tier should create a BASIC spending plan for a new user and use the same plan on second transaction and different plan on third transaction from another user
should eventually exhaust the hbar limit for a BASIC user after multiple deployments of large contracts ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests HBAR Rate Limit For Different Spending Plan Tiers @hbarlimiter-batch2 BASIC Tier should eventually exhaust the hbar limit for a BASIC user after multiple deployments of large contracts