-
Don’t assume that all method calls succeed and return what you want. Unless a method call can’t possibly fail, test returned values and catch possible exceptions, then fail gracefully.
-
1. Whenever a file is opened, check that it worked. Error/exit else.
2. Same for whenever a file is closed.
-
Nightcrawler - if don't have initiative, Monstrous intuition to hit - so impossible if not Amazing?
-
numpy= 1.26 to work on python 3.12 - ref: https://github.com/numpy/numpy/issues/23808#issuecomment-1722440746
does something here break with numpy >= 1.26, or was this just a defensive version com…
-
## User Story
As a person monitoring dataset harvesting, it would be nice if the harvester did some additional pre-harvest validation to prevent bad data from being imported.
## Acceptance Criteri…
-
Currently there seems to be no good way of testing defensive paths, due to the fact that they call `debug_assert!` under the hood, which panics in testing environment.
The only "solution" to that t…
-
[Build](https://mihubot.xyz/runtime-utils/9a3e6b15ce0d4b03bd59fac50713865e) completed in 27 minutes.
### Diffs
```
Found 258 files with textual diffs.
Summary of Code Size diffs:
(Lower is better)…
-
All of our challenges are in the mentality of "here's the application break it", it would be nice to have challenges where the student is given a piece of broken code and they are required to fix it
-
```defence turrets, seeker missiles, robotic guards```
-
We should play around with the idea of incorporating attribute checks before rules run. We could start with functions and move to a feature request in the engine. The idea is, many rules have attribu…