-
Notifications
You must be signed in to change notification settings - Fork 385
[Experimental - DO NOT MERGE] CI: Enable scout workflow on master #3629
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
base: master
Are you sure you want to change the base?
Conversation
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Coverage Report@@ Coverage Diff @@
## master rq/enable-scount-on-master +/- ##
==============================================================
+ Coverage 76.55% 76.65% +0.10%
Files 389 389
+ Lines 76684 76960 +276
==============================================================
+ Hits 58704 58991 +287
- Misses 17980 17969 -11
|
WASM runtime size check:Compared to target branchMoonbase runtime: 2120 KB (no changes) ✅ Moonbeam runtime: 2232 KB (no changes) ✅ Moonriver runtime: 2236 KB (no changes) ✅ Compared to latest release (runtime-4101)Moonbase runtime: 2120 KB (+184 KB compared to latest release) Moonbeam runtime: 2232 KB (+196 KB compared to latest release) Moonriver runtime: 2236 KB (+204 KB compared to latest release) |
This reverts commit 99a4056.
Scout Report - Moonbeam - 2026-01-14Summary
Issues found:
ArithmeticOverflow CheckImpact: Critical Issue: Use Description: An overflow/underflow is typically caught and generates an error. When it is not caught, the operation will result in an inexact result which could lead to serious problems. Findings
|
Scout Report - Moonbeam - 2026-01-14Summary
Issues found:
Error HandlingAvoid Panic ErrorImpact: Enhancement Issue: The panic! macro is used in a function that returns Result. Consider using the ? operator or return Err() instead. Description: Using panic! in functions that return Result defeats the purpose of error handling. Consider propagating the error using ? or return Err() instead. Findings
|
Scout Report - Moonbeam - 2026-01-16Summary
Issues found:
Error HandlingAvoid Panic ErrorImpact: Enhancement Issue: The panic! macro is used in a function that returns Result. Consider using the ? operator or return Err() instead. Description: Using panic! in functions that return Result defeats the purpose of error handling. Consider propagating the error using ? or return Err() instead. Findings
|
From the result report below, this will not be very helpful for us until they add the following improvements:
File Locationin findings should be a relative path, just having the file name is not enough;